You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello. I encountered the following error while playing a simple pipeline with a single video and a trigger enabled in the end. The message pops up when the trigger (or end of video file) in the timeline is reached.
The exact same project file produces this error for versions 3.0.4-3.0.6 that I tested, while in version 3.0.3 it's OK.
As long as the error is triggered, the video window gets stuck and no video output is produced if restarted. After the first error is triggered, the same message can be triggered again in the setting for the Graphics API, e.g. changing from OpenGL to Vulkan as shown below. I think that it falls in a weird graphics error state.
OS: Ubuntu 21.04
The text was updated successfully, but these errors were encountered:
hummm weird, here it doesn't do that. Could you send my your score file and ideally your video file through e.g. wetransfer ?
In fact in another setup I had (score 3.0.5) I thought that it was the video, because I downloaded one from youtube, got this error, but then I downloaded from the same source as you had in the tutorial (beeple videos) and voila it worked. I currently don't have access in that setup, maybe in few days to test the exact same score file I attach.
So the video I tested is this: https://vimeo.com/238083470 (original resolution) and the score file is here untitled.zip. It's not the same video as in the screenshot but the same happens.
Maybe it is a transient issue, or maybe it has to do with the "random" placement of the video on the timeline?
Hello. I encountered the following error while playing a simple pipeline with a single video and a trigger enabled in the end. The message pops up when the trigger (or end of video file) in the timeline is reached.
The exact same project file produces this error for versions 3.0.4-3.0.6 that I tested, while in version 3.0.3 it's OK.
As long as the error is triggered, the video window gets stuck and no video output is produced if restarted. After the first error is triggered, the same message can be triggered again in the setting for the Graphics API, e.g. changing from OpenGL to Vulkan as shown below. I think that it falls in a weird graphics error state.
OS: Ubuntu 21.04
The text was updated successfully, but these errors were encountered: