Hey Jean Paul, thanks for your reply!
This is clear to me.
I think you should implement an error message when a user tries to load a video that is too long. This could be dependent on the RAM capacity, although when we programmed something similar at Ableton, we set a hard-coded limit based on smaller RAMs, because of course you want a Live set you made on a powerful machine to be able to open on one with less capacity (obviously there are limits to that philosophy, too). Anyway, something to think about…I mentioned the LFOs because I thought maybe it matters if i’m scrubbing outside of the video or something 
For this particular use case it would be perfect to use Simpler slice mode instead of chopping manually. I was using MIDI notes with a little bit of randomization to play back a part of the video every 16th note. It looks super cool until it crashes 
I’ll look into HAP! Or try to cut my video to match my RAM capacity (although, it is 96 GB while my video is only 3.7 GB…so that’s kind of weird…)
…After writing this message I repeated my activities while watching memory usage on the Activity Monitor. When I loaded the 1hr video and then maxed out the end time it was VTDecoderXPCService which started using more and more and more RAM…Going up to reading 150GB before I shut down Live to prevent the crash. For my own understanding I’m very curious why so much RAM is needed?