secco

when I use loadram to load a movie into ram with jit.qt.movie, max is blocked while the object is loading the movie into RAM. Is there any way to avoid that?

loadram-without-pausing

i would do that with loadbang when the patch loads. that way all your movs can be loaded into ram before you start the processing.

i am not aware of another way to avoid the loadram "hang".

definitely. Check out the loadram x y message too, which loads 

portions of your movie, not the whole thing. This along with 

something like poly~ for movies, js_moviebank or similar multiple 

jit.qt.movie handling methodologies will allow you to manage your 

movies, without 'unloading' them from ram, or loading others in its 

On Sep 7, 2007, at 9:32 AM, justin wrote:

> i would do that with loadbang when the patch loads. that way all 

> your movs can be loaded into ram before you start the processing.

> i am not aware of another way to avoid the loadram "hang".

definitely. Check out the loadram x y message too, which loads  
portions of your movie, not the whole thing. This along with  
something like poly~ for movies, js_moviebank or similar multiple  
jit.qt.movie handling methodologies will allow you to manage your  
movies, without 'unloading' them from ram, or loading others in its  
place reintroducing the delay.

>
> i would do that with loadbang when the patch loads. that way all  
> your movs can be loaded into ram before you start the processing.
>
> i am not aware of another way to avoid the loadram "hang".
>
> j

When enabled, the jit.qt.movie object will attempt to asynchronously preroll the next section of the current movie for fast, non-interrupting restart.

Note: use of preroll and asyncread unloads any sections of the current movie loaded into RAM using the loadram method.

never used preroll option before... cheers for the pointer!

but looks like its either loadram or preroll - not both!

Quote: vade wrote on Fri, 07 September 2007 15:47

----------------------------------------------------

> definitely. Check out the loadram x y message too, which loads 

> portions of your movie, not the whole thing. This along with 

> something like poly~ for movies, js_moviebank or similar multiple 

> jit.qt.movie handling methodologies will allow you to manage your 

> movies, without 'unloading' them from ram, or loading others in its 

> also, preroll 1 is quite handy as well.

> On Sep 7, 2007, at 9:32 AM, justin wrote:

> > i would do that with loadbang when the patch loads. that way all 

> > your movs can be loaded into ram before you start the processing.

> > i am not aware of another way to avoid the loadram "hang".

Preroll movie on stop flag (default = 0)
When enabled, the jit.qt.movie object will attempt to asynchronously preroll the next section of the current movie for fast, non-interrupting restart.
Note: use of preroll and asyncread unloads any sections of the current movie loaded into RAM using the loadram method.

never used preroll option before... cheers for the pointer!
but looks like its either loadram or preroll - not both!

Quote: vade wrote on Fri, 07 September 2007 15:47
----------------------------------------------------
> definitely. Check out the loadram x y message too, which loads  
> portions of your movie, not the whole thing. This along with  
> something like poly~ for movies, js_moviebank or similar multiple  
> jit.qt.movie handling methodologies will allow you to manage your  
> movies, without 'unloading' them from ram, or loading others in its  
> place reintroducing the delay.
>
> also, preroll 1 is quite handy as well.
>
> On Sep 7, 2007, at 9:32 AM, justin wrote:
>
> >
> > i would do that with loadbang when the patch loads. that way all  
> > your movs can be loaded into ram before you start the processing.
> >
> > i am not aware of another way to avoid the loadram "hang".
> >
> > j
>
> v a d e //
>
> www.vade.info
> abstrakt.vade.info
>
>
>
>
>
>
----------------------------------------------------


unfortunately all that doesn't help me at all. I checked all that out before (except moviebank and poly).

The main problem is that loadram doesn't seem to be asynchronous, right? I read somewhere in the forum that it shoud be since jitter 1.5. But it doesn't look so (I'm on 1.63 XP).

I can't preload multiple movies because I will have over 50 of them and one takes over 1GB on the Harddisk (Animation Codec 75 perc).

I can't compress them more because I need the alphachannel so I can't use better compressors like H264 or something like that. Or does anybody know a good codec which supports alpha?

Maybe I could load the movie asynchronously into a jit.matrixset? But then it would probably exceed RAM because it will be completely uncompressed, right? So in that case I would need more than 2GB RAM. Probably more than 4GB. Don't know if that is possible to adress anyway?

Is there a certain reason why loadram blocks jitter? unloadram works asynchronously, bang by bang. loadram doesn't:-(

unfortunately all that doesn't help me at all. I checked all that out before (except moviebank and poly).
The main problem is that loadram doesn't seem to be asynchronous, right? I read somewhere in the forum that it shoud be since jitter 1.5. But it doesn't look so (I'm on 1.63 XP).

I can't preload multiple movies because I will have over 50 of them and one takes over 1GB on the Harddisk (Animation Codec 75 perc).
I can't compress them more because I need the alphachannel so I can't use better compressors like H264 or something like that. Or does anybody know a good codec which supports alpha?
Maybe I could load the movie asynchronously into a jit.matrixset? But then it would probably exceed RAM because it will be completely uncompressed, right? So in that case I would need more than 2GB RAM. Probably more than 4GB. Don't know if that is possible to adress anyway?

I don't know how to solve this:-(
Any other suggestions, ideas?

Har, I just send in a patch in the HD playback for jitter which is my 

I use preroll 1, load them, and IMMEDIATELY stop them, :)

so the next time I load them, the initial few frames is in ram for 

Jitter. This ought to work for 50 movies.

> unfortunately all that doesn't help me at all. I checked all that 

> out before (except moviebank and poly).

> The main problem is that loadram doesn't seem to be asynchronous, 

> right? I read somewhere in the forum that it shoud be since jitter 

> 1.5. But it doesn't look so (I'm on 1.63 XP).

> I can't preload multiple movies because I will have over 50 of them 

> and one takes over 1GB on the Harddisk (Animation Codec 75 perc).

> I can't compress them more because I need the alphachannel so I 

> can't use better compressors like H264 or something like that. Or 

> does anybody know a good codec which supports alpha?

> Maybe I could load the movie asynchronously into a jit.matrixset? 

> But then it would probably exceed RAM because it will be completely 

> uncompressed, right? So in that case I would need more than 2GB 

> RAM. Probably more than 4GB. Don't know if that is possible to 

> Is there a certain reason why loadram blocks jitter? unloadram 

> works asynchronously, bang by bang. loadram doesn't:-(

Har, I just send in a patch in the HD playback for jitter which is my  
solution to loading 19 DVCPro HD movies,

so the next time I load them, the initial few frames is in ram for  
Jitter. This ought to work for 50 movies.

>
> Thanks Vade, thanks Justin,
>
> unfortunately all that doesn't help me at all. I checked all that  
> out before (except moviebank and poly).
> The main problem is that loadram doesn't seem to be asynchronous,  
> right? I read somewhere in the forum that it shoud be since jitter  
> 1.5. But it doesn't look so (I'm on 1.63 XP).
>
> I can't preload multiple movies because I will have over 50 of them  
> and one takes over 1GB on the Harddisk (Animation Codec 75 perc).
> I can't compress them more because I need the alphachannel so I  
> can't use better compressors like H264 or something like that. Or  
> does anybody know a good codec which supports alpha?
> Maybe I could load the movie asynchronously into a jit.matrixset?  
> But then it would probably exceed RAM because it will be completely  
> uncompressed, right? So in that case I would need more than 2GB  
> RAM. Probably more than 4GB. Don't know if that is possible to  
> adress anyway?
>
> Is there a certain reason why loadram blocks jitter? unloadram  
> works asynchronously, bang by bang. loadram doesn't:-(
>
> I don't know how to solve this:-(
> Any other suggestions, ideas?
>
> thanks
> secco
>
>

rather, the HD playback for jitter *thread*. So check that out.

> Har, I just send in a patch in the HD playback for jitter which is 

> my solution to loading 19 DVCPro HD movies,

> I use preroll 1, load them, and IMMEDIATELY stop them, :)

> so the next time I load them, the initial few frames is in ram for 

> Jitter. This ought to work for 50 movies.

> On Sep 7, 2007, at 2:22 PM, secco wrote:

>> unfortunately all that doesn't help me at all. I checked all that 

>> out before (except moviebank and poly).

>> The main problem is that loadram doesn't seem to be asynchronous, 

>> right? I read somewhere in the forum that it shoud be since jitter 

>> 1.5. But it doesn't look so (I'm on 1.63 XP).

>> I can't preload multiple movies because I will have over 50 of 

>> them and one takes over 1GB on the Harddisk (Animation Codec 75 

>> I can't compress them more because I need the alphachannel so I 

>> can't use better compressors like H264 or something like that. Or 

>> does anybody know a good codec which supports alpha?

>> Maybe I could load the movie asynchronously into a jit.matrixset? 

>> But then it would probably exceed RAM because it will be 

>> completely uncompressed, right? So in that case I would need more 

>> than 2GB RAM. Probably more than 4GB. Don't know if that is 

>> Is there a certain reason why loadram blocks jitter? unloadram 

>> works asynchronously, bang by bang. loadram doesn't:-(

rather, the HD playback for jitter *thread*. So check that out.
On Sep 7, 2007, at 2:46 PM, vade wrote:

> Har, I just send in a patch in the HD playback for jitter which is  
> my solution to loading 19 DVCPro HD movies,
>
> I use preroll 1, load them, and IMMEDIATELY stop them, :)
>
> so the next time I load them, the initial few frames is in ram for  
> Jitter. This ought to work for 50 movies.
>
> Feel free to use the patch.
>
> On Sep 7, 2007, at 2:22 PM, secco wrote:
>
>>
>> Thanks Vade, thanks Justin,
>>
>> unfortunately all that doesn't help me at all. I checked all that  
>> out before (except moviebank and poly).
>> The main problem is that loadram doesn't seem to be asynchronous,  
>> right? I read somewhere in the forum that it shoud be since jitter  
>> 1.5. But it doesn't look so (I'm on 1.63 XP).
>>
>> I can't preload multiple movies because I will have over 50 of  
>> them and one takes over 1GB on the Harddisk (Animation Codec 75  
>> perc).
>> I can't compress them more because I need the alphachannel so I  
>> can't use better compressors like H264 or something like that. Or  
>> does anybody know a good codec which supports alpha?
>> Maybe I could load the movie asynchronously into a jit.matrixset?  
>> But then it would probably exceed RAM because it will be  
>> completely uncompressed, right? So in that case I would need more  
>> than 2GB RAM. Probably more than 4GB. Don't know if that is  
>> possible to adress anyway?
>>
>> Is there a certain reason why loadram blocks jitter? unloadram  
>> works asynchronously, bang by bang. loadram doesn't:-(
>>
>> I don't know how to solve this:-(
>> Any other suggestions, ideas?
>>
>> thanks
>> secco
>>
>>
>
> v a d e //
>
> www.vade.info
> abstrakt.vade.info
>
>
>

god, sorry. let me try explaining that one more time. Im a bit out of 

load the movie, start it and immediately stop it. it becomes cued and 

ready to play without a pause (thus, uh, prerolled)

just send 'start' when you want it to play.

> rather, the HD playback for jitter *thread*. So check that out.

> On Sep 7, 2007, at 2:46 PM, vade wrote:

>> Har, I just send in a patch in the HD playback for jitter which is 

>> my solution to loading 19 DVCPro HD movies,

>> I use preroll 1, load them, and IMMEDIATELY stop them, :)

>> so the next time I load them, the initial few frames is in ram for 

>> Jitter. This ought to work for 50 movies.

>> On Sep 7, 2007, at 2:22 PM, secco wrote:

>>> unfortunately all that doesn't help me at all. I checked all that 

>>> out before (except moviebank and poly).

>>> The main problem is that loadram doesn't seem to be asynchronous, 

>>> right? I read somewhere in the forum that it shoud be since 

>>> jitter 1.5. But it doesn't look so (I'm on 1.63 XP).

>>> I can't preload multiple movies because I will have over 50 of 

>>> them and one takes over 1GB on the Harddisk (Animation Codec 75 

>>> I can't compress them more because I need the alphachannel so I 

>>> can't use better compressors like H264 or something like that. Or 

>>> does anybody know a good codec which supports alpha?

>>> Maybe I could load the movie asynchronously into a jit.matrixset? 

>>> But then it would probably exceed RAM because it will be 

>>> completely uncompressed, right? So in that case I would need more 

>>> than 2GB RAM. Probably more than 4GB. Don't know if that is 

>>> Is there a certain reason why loadram blocks jitter? unloadram 

>>> works asynchronously, bang by bang. loadram doesn't:-(

god, sorry. let me try explaining that one more time. Im a bit out of  
it, Apologies for list spam.

load the movie, start it and immediately stop it. it becomes cued and  
ready to play without a pause (thus, uh, prerolled)

> rather, the HD playback for jitter *thread*. So check that out.
> On Sep 7, 2007, at 2:46 PM, vade wrote:
>
>> Har, I just send in a patch in the HD playback for jitter which is  
>> my solution to loading 19 DVCPro HD movies,
>>
>> I use preroll 1, load them, and IMMEDIATELY stop them, :)
>>
>> so the next time I load them, the initial few frames is in ram for  
>> Jitter. This ought to work for 50 movies.
>>
>> Feel free to use the patch.
>>
>> On Sep 7, 2007, at 2:22 PM, secco wrote:
>>
>>>
>>> Thanks Vade, thanks Justin,
>>>
>>> unfortunately all that doesn't help me at all. I checked all that  
>>> out before (except moviebank and poly).
>>> The main problem is that loadram doesn't seem to be asynchronous,  
>>> right? I read somewhere in the forum that it shoud be since  
>>> jitter 1.5. But it doesn't look so (I'm on 1.63 XP).
>>>
>>> I can't preload multiple movies because I will have over 50 of  
>>> them and one takes over 1GB on the Harddisk (Animation Codec 75  
>>> perc).
>>> I can't compress them more because I need the alphachannel so I  
>>> can't use better compressors like H264 or something like that. Or  
>>> does anybody know a good codec which supports alpha?
>>> Maybe I could load the movie asynchronously into a jit.matrixset?  
>>> But then it would probably exceed RAM because it will be  
>>> completely uncompressed, right? So in that case I would need more  
>>> than 2GB RAM. Probably more than 4GB. Don't know if that is  
>>> possible to adress anyway?
>>>
>>> Is there a certain reason why loadram blocks jitter? unloadram  
>>> works asynchronously, bang by bang. loadram doesn't:-(
>>>
>>> I don't know how to solve this:-(
>>> Any other suggestions, ideas?
>>>
>>> thanks
>>> secco
>>>
>>>
>>
>> v a d e //
>>
>> www.vade.info
>> abstrakt.vade.info
>>
>>
>>
>
> v a d e //
>
> www.vade.info
> abstrakt.vade.info
>
>
>

I can't preload multiple movies because I will have over 50 of 

>> I can't compress them more because I need the alphachannel so I

How about using two movies instead of one? Matte and fill. One for picture, the other for alpha channel? Might be able to compress the alpha movie much more in photo-jpeg? just black and white. could use 50% or less....Then recombine using jit.pack?

might be a few sync issues,but worth a go. not sure about h264 though. intra-frame codec not good for compositing.

I've loaded a 5gb movie into ram, but it appears to take up more like 10 gb of ram. (on Mac OSX)

In matrixset, max limit appears to be 2gb, due to 32-bit memory addressing.....

I can't preload multiple movies because I will have over 50 of 
>> them and one takes over 1GB on the Harddisk (Animation Codec 75 
>> perc).
>> I can't compress them more because I need the alphachannel so I 

>> does anybody know a good codec which supports alpha?
>> Maybe I could load the movie asynchronously into a jit.matrixset? 
>> But then it would probably exceed RAM because it will be 
>> completely uncompressed, right? So in that case I would need more 
>> than 2GB RAM. Probably more than 4GB. Don't know if that is 
>> possible to adress anyway?

In matrixset, max limit appears to be 2gb, due to 32-bit memory addressing.....


On Sep 8, 2007, at 8:19 PM, marcus lyall wrote:

> I've loaded a 5gb movie into ram, but it appears to take up more 

> I've loaded a 5gb movie into ram, but it appears to take up more  
> like 10 gb of ram. (on Mac OSX)

if the movie filesze is 5 gb, it will take more RAM than its filesize, since it's compressed. As I recall, loadram message decompressed the movie?

if the movie filesze is 5 gb, it will take more RAM than its filesize, since it's compressed.  As I recall, loadram message decompressed the movie?

Well, I found out that that isnt the case, that it doesnt decompress, 

but, I meant that Max is addressing more than 2 gigs of ram.

On Sep 10, 2007, at 5:10 PM, pnyboer wrote:

> if the movie filesze is 5 gb, it will take more RAM than its 

> filesize, since it's compressed. As I recall, loadram message 

Well, I found out that that isnt the case, that it doesnt decompress,  
but, I meant that Max is addressing more than 2 gigs of ram.

> if the movie filesze is 5 gb, it will take more RAM than its  
> filesize, since it's compressed.  As I recall, loadram message  
> decompressed the movie?

In theory, loadram loads the compressed media into memory. Since 

there's no low-level control of what loadram really does, though, 

it's impossible to say for certain that there's _no_ decompression 

In theory, loadram loads the compressed media into memory. Since  
there's no low-level control of what loadram really does, though,  
it's impossible to say for certain that there's _no_ decompression  
involved.

> if the movie filesze is 5 gb, it will take more RAM than its  
> filesize, since it's compressed.  As I recall, loadram message  
> decompressed the movie?


It was an uncompressed movie, a 4 min music video captured from a Blackmagic card.

We were trying to see how many clips could be stored in ram, or whether one big one would do the job.

And it appeared to load the 5gb whole movie in, but took up 10gb or so of space, according to activity monitor.

We were trying to see how many clips could be stored in ram, or whether one big one would do the job. 

And it appeared to  load the 5gb whole movie in, but took up 10gb or so of space, according to activity monitor.


Can max loadram a movie that large? Isnt there a memory addressing 

On Sep 11, 2007, at 5:20 AM, marcus lyall wrote:

> It was an uncompressed movie, a 4 min music video captured from a 

> We were trying to see how many clips could be stored in ram, or 

> And it appeared to load the 5gb whole movie in, but took up 10gb 

> or so of space, according to activity monitor.

Can max loadram a movie that large? Isnt there a memory addressing  
limit of 2 GB?

>
> It was an uncompressed movie, a 4 min music video captured from a  
> Blackmagic card.
>
> We were trying to see how many clips could be stored in ram, or  
> whether one big one would do the job.
>
> And it appeared to  load the 5gb whole movie in, but took up 10gb  
> or so of space, according to activity monitor.
>
>
>
>

Go figure... must be a low-level Quicktime thing.

> Can max loadram a movie that large? Isnt there a memory addressing 

> On Sep 11, 2007, at 5:20 AM, marcus lyall wrote:

>> It was an uncompressed movie, a 4 min music video captured from a 

>> We were trying to see how many clips could be stored in ram, or 

>> And it appeared to load the 5gb whole movie in, but took up 10gb 

>> or so of space, according to activity monitor.

Max can't... JKC said so recently.
Go figure... must be a low-level Quicktime thing.

> Can max loadram a movie that large? Isnt there a memory addressing  
> limit of 2 GB?
>
> On Sep 11, 2007, at 5:20 AM, marcus lyall wrote:
>
>>
>> It was an uncompressed movie, a 4 min music video captured from a  
>> Blackmagic card.
>>
>> We were trying to see how many clips could be stored in ram, or  
>> whether one big one would do the job.
>>
>> And it appeared to  load the 5gb whole movie in, but took up 10gb  
>> or so of space, according to activity monitor.
>>
>>
>>
>>
>
> v a d e //
>
> www.vade.info
> abstrakt.vade.info
>
>
>


Ok, that whole thing was a long winded way of say, *you did not load 

Unless Ive fundamentally misunderstood something, you are limited to 

2GB for all of Max/Jitter, so this must be a mistake.

On Sep 11, 2007, at 12:05 PM, evan.raskob [lists] wrote:

> Go figure... must be a low-level Quicktime thing.

> On Sep 11, 2007, at 2:12 PM, vade wrote:

>> Can max loadram a movie that large? Isnt there a memory addressing 

>> On Sep 11, 2007, at 5:20 AM, marcus lyall wrote:

>>> It was an uncompressed movie, a 4 min music video captured from a 

>>> We were trying to see how many clips could be stored in ram, or 

>>> whether one big one would do the job.

>>> And it appeared to load the 5gb whole movie in, but took up 10gb 

>>> or so of space, according to activity monitor.

Ok, that whole thing was a long winded way of say, *you did not load  
a 5GB movie into ram*.

Unless Ive fundamentally misunderstood something, you are limited to  
2GB for all of Max/Jitter, so this must be a mistake.

> Max can't... JKC said so recently.
> Go figure... must be a low-level Quicktime thing.
>
>
> On Sep 11, 2007, at 2:12 PM, vade wrote:
>
>> Can max loadram a movie that large? Isnt there a memory addressing  
>> limit of 2 GB?
>>
>> On Sep 11, 2007, at 5:20 AM, marcus lyall wrote:
>>
>>>
>>> It was an uncompressed movie, a 4 min music video captured from a  
>>> Blackmagic card.
>>>
>>> We were trying to see how many clips could be stored in ram, or  
>>> whether one big one would do the job.
>>>
>>> And it appeared to  load the 5gb whole movie in, but took up 10gb  
>>> or so of space, according to activity monitor.
>>>
>>>
>>>
>>>
>>
>> v a d e //
>>
>> www.vade.info
>> abstrakt.vade.info
>>
>>
>>
>

same movie. 5gb uncompressed pal qt from blackmagic. 

activity monitor said max was using 16.77 gb RAM and 3.5 gb virtual memory.

then I moved the jit.window from one screen to another and got a catastrophic crash that froze the whole machine.

same movie. 5gb uncompressed pal qt from blackmagic. 
used loadram. it loaded the whole thing.

Wow. Maybe this is being addressed at the QT level. Thats awesome. I 

On Sep 26, 2007, at 7:19 PM, marcus lyall wrote:

> same movie. 5gb uncompressed pal qt from blackmagic.

> used loadram. it loaded the whole thing.

> activity monitor said max was using 16.77 gb RAM and 3.5 gb virtual 

> it was running fine. but still jerky....

> then I moved the jit.window from one screen to another and got a 

> catastrophic crash that froze the whole machine.

Wow. Maybe this is being addressed at the QT level. Thats awesome. I  
did not expect that at all. Badass!
On Sep 26, 2007, at 7:19 PM, marcus lyall wrote:

>
> same movie. 5gb uncompressed pal qt from blackmagic.
> used loadram. it loaded the whole thing.
>
> activity monitor said max was using 16.77 gb RAM and 3.5 gb virtual  
> memory.
>
> it was running fine. but still jerky....
>
> then I moved the jit.window from one screen to another and got a  
> catastrophic crash that froze the whole machine.
>
> 8core. 16gb ram installed.
>
> what can i say?
>
>

loadram without pausing