MXF in vegas + raylight (possible bug?)

E

earthcubed

Member
I would just like to know if anyone else has had the same problem that I have....

Rendering pro50 MXF files to mpeg2 for dvd, the problem i have is that the file will render about 2xrealtime for 20,30 80% (depending on the length of the project) of the project and then just slow down to about 3 frames p/sec.

I tried many diff settings and lengths of projects, in the end i had to render out the project in 25min sections.

Does anyone know of any problems with raylight and vegas7 that would cause this, I tried with 7d & e and raylight 2 & 3.

thanks
Nick
 
Are there differences in the timeline? Meaning, do you have few or no effects added toward the beginning, then color correction or other FX later on? Especially Magic Bullet?
 
Nope there are no effects at all, just raw footage no fades etc...
I'm running a quad core intel with 4gb ram so my workstation is def upto the task.

I got to the point that I thought it may be a problem with my machine so I reinstalled the OS and all apps but had the same problem.

My tech guy said that the counter in Raylight might be 16bit something so it might only beable to address a 16bit number ( not to sure about the tech talk), maybe someone from raylight can explain if it is the case.

Nick
 
There are no frame counters or output file pointers in Raylight becasue it's actually Vegas, not Raylight, that is creating the mpeg file. Raylight just provides the frame data.

I would watch your "commit charge" while rendering. If it gets close to 2GB then the memory swapping starts and everything slows down. If that's the problem contact DVFilm Support and we can help determine if the problem is in Vegas, Raylight, or the mpeg2 encoder.

Another test you can try yourself to isolate it, is render a 720 x 480 23.976P Microsoft AVI (uncompressed) and see if it slows down there as well.
 
Last edited:
my commit charge goes to 1.6gb and stays there, I also tried going into the internal menu to lift the ram preview amount from 1024 to 2024 ( i thought that might help ) my commit charge then stayed at 2.6gb. ( i have 4gb )

I also tried doing the same renders to Matrox pro50 and uncomp avi, both had the same issue when rendering from the MXF's, but not from the DV footage that I tried.

I also tried putting the 4 25min mpegs back onto a new timeline to create one 100min mpeg, the render had no issues, same render speed from start to finish
with a commit charge of 1.6gb

Could the problem be with XP64bit?

Thanks
Nick
 
You must log in or register to reply here.
Back
Top