Shane

This is an issue I've been dealing with for a long time. It rears its ugly head whenever a patch gets large but it's trigger is unknown. Currently I have 3 video players using viddll on windows 10. A player gets a file and after I see "read....(filename)" pop out the dumpout I loadram. The cache is 1.5 gb and I never load a movie longer than 18 seconds. I'm loading h.264 and h.265 encoded movies. The crash happens most often after letting things run for a while and not loading a new movie, then upon loading a new movie it crashes. I have 16 gb of RAM and 8GB video Ram. I'm well under running out of memory with 4.5 GB allocated across the 3 jit.movies.

1. I don't need to dispose or unload ram on the jit.movie object inbetween loading as the ram is not dedicated for that movie file but rather that jitter object. 

2. When I see "file....etc" pop out the dumpout the movie is loaded and available to loadram and I'm not interrupting anything. 

3. Jit.movie ignores frame messages while loading the file and loading it into ram and that's not messing it up somehow.

Here is the playback engine. Only the top left is likely relevant just to see order of messages.

ezdac~

dropfile

loadmess

outlet

inlet

message

change

number

gate

toggle

textbutton

live.tab

cos~

rate~

triangle~

comment

selector~

flonum

gate~

route

phasor~

jit.fpsgui

snapshot~

slider

button

timer

print

prepend

jit.movie

This is an issue I've been dealing with for a long time. It rears its ugly head whenever a patch gets large but it's trigger is unknown. Currently I have 3 video players using viddll on windows 10.  A player gets a file and after I see "read....(filename)" pop out the dumpout I loadram. The cache is 1.5 gb and I never load a movie longer than 18 seconds. I'm loading h.264 and h.265 encoded movies. The crash happens most often after letting things run for a while and not loading a new movie, then upon loading a new movie it crashes. I have 16 gb of RAM and 8GB video Ram. I'm well under running out of memory with 4.5 GB allocated across the 3 jit.movies. 

I am operating on some assumptions. 
1. I don't need to dispose or unload ram on the jit.movie object inbetween loading as the ram is not dedicated for that movie file but rather that jitter object. 
2. When I see "file....etc" pop out the dumpout the movie is loaded and available to loadram and I'm not interrupting anything. 
3. Jit.movie ignores frame messages while loading the file and loading it into ram and that's not messing it up somehow. 

Here is the playback engine. Only the top left is likely relevant just to see order of messages. 

This is an issue I've been dealing with for a long time. It rears its ugly head whenever a patch gets large but it's trigger is unknown. Cur

loadram-crashing

Current tests showing the issue may be related to @autostart 1 and @automatic 1 rather than the loadram. With both @ set to 0 I'm seeing improvements as once the file is loaded I can loadram and do not observe a freeze / pause / stutter which always feels unstable to me.

Although I don't get the stutter in the other videos I think this was due to h.264 trying to autostart. Its nice to not have that, but I'm now getting constant crashing on loading videos then loading to ram. The timing and order on queries and if jit.movie gets render bangs has a great impact on this.

Loadram crashing