I have tried several video clips with Videosync and it normally crashes as soon as playback begins.
I checked the logs:
[22820] [22820:17296:20240920,134834.731:ERROR filesystem_win.cc:128] GetFileAttributes C:\Users\Ben\AppData\Roaming\Showsync\Videosync\sentry\attachments\627e50a9-db7b-4512-a186-4aa3da31cc46: The system cannot find the file specified. (2)
Doesn’t make much sense, it is able to find the appropriate video dimensions before crashing.
Is there a workaround? I’d really like to use videosync for a gig later today but if this isn’t resolved quickly I won’t be able to. Thanks
@benwiley4000 - I have an alpha version that contains a potential fix for the crashes you’re seeing. I would love to send it to you to see if this indeed solves the issue. Would you be willing to test it out?
I guess what im trying to do with video sync isn’t what it was designed to do. I try to load long-form videos into video simpler and have like 12 of them in a drum rack so I can toggle between them using my midi keyboard. The long form videos seem to take forever to load, and then usually my CPU spikes beyond comprehension and then I have a frozen computer.
Simpler loads the uncompressed frames into RAM. The video size on your hard drive is the compressed size, so it’s expected that loading the file in Simpler requires much more RAM than what you’d expect when looking at the original file.
You can do some napkin math to roughly figure out how much RAM you need for a given file. You can multiply the resolution by 32 bits (RGBA) to know the size of each frame: 3840 x 2160 x 32 = 265420800 bits = 33 MB per frame. 33 MB * 24 fps = 792 MB per second. 792MB * 120 seconds = 95 GB of RAM.
If you’re on macOS, you can consider converting the file to HAP which streams the video rather than preloading all frames in RAM. This is generally recommended if you try to load large/long video files in Simpler, since the RAM option is mostly intended for small and short video fragments.