John Rofrano
3
COW Coins
Forum Replies Created
-
I don’t think I follow you. How did you re-render the original files if they are not on your computer? VirtualDub doesn’t “use” files. It makes “copies” of them in a different format. The end result is two (2) files.
What you should do is open the original file in VirtualDub and save as another filename. Now you should have two copies of the same file. One as the original name and one as the new name. That’s what you need to do. Then check the newname file and make sure it doesn’t have a 4CC of DivX (it should be DIB) and that it is much, much, larger in size than the original. This will tell you that you successfully converted the file to uncompressed.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
I don’t know. It’s impossible. Rendering uncompressed removes the codec. The DivX 4CC should not be there. What is the size of the original file and the uncompressed version?
~jr
http://www.johnrofrano.com
http://www.vasst.com -
Since Sony has a free trial of VMSP 9, I’d recommend that you download it and see for yourself. It does say AVCHD support so it might contain the Sony AVC render which supports H.264 encoding from PSP memory stick to Blu-ray discs in Vegas Pro 8.
Like Steve, I also use Vegas Pro 8 so I really can’t say what the new VMSP 9 can do (sorry).
~jr
http://www.johnrofrano.com
http://www.vasst.com -
Yup, that’s exactly what you were supposed to do. Are you sure you are using the saved files? While in VirtualDub, go to Video | Compression… (Ctrl+P) and make sure (Uncompressed RGB/YCbCr) is highlighted. Then make sure Video | Full Processing Mode is checked. Finally, select Save as AVI…. Now check the resulting file. It should be a LOT larger than the DivX version in size. It should NOT have a FourCC of DivX because it is uncompressed.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
Many codecs only support specific resolutions, therefore you will get errors if you try and render to a resolution that they don’t support. For Vegas 6, I would start a project using the HDV 720-25p (1280×720, 25.000 fps) template. Then render using the Windows Media Video V9 (*.wmv) format with the 5 Mbps HD 720-25p Video template and see how your playback device handles it.
I have found that while these devices claim to support mpeg4, HD DIVX, and H264, it is hit and miss to find the proper render settings for this to work. WMV seems to be much easier to get working so that’s where I would start. I have also found that some of these playback devices only support 720 and not 1080 so that also makes 720 a good starting place for success.
I also recommended 720p because it’s progressive and your images are progressive. If you want to use 1080 instead, start with the HD 1080-50i (1920×1080, 25.000 fps) template and change the Field order to None (progressive). All of the 1080 project templates in Vegas are interlaced and you don’t wan to interlace images so keep them progressive.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
Cameras that record MPEG2 to a hard drive is probably an excellent idea! That eliminates the AVI to MPEG conversion entirely. That would drop right into DVD Architect and burn very quickly.
I think that’s the ticket. I was considering something like a Focus FS-4 portable recorder but you could pick up an MPEG HDD camera for less money and burn right to DVD.
Since you can’t buy DVD Architect without buying Vegas and they don’t have a need for Vegas, you might want to just get them Vegas Movie Studio. That will be a whole lot cheaper and you still get DVD Architect Studio which is more than enough for their needs.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
Did you use VirtualDub to create uncompressed AVI files? If you check them with the FourCC program, the Description Code should be DIB and the Used Codec should have nothing in it! (because uncompressed files don’t use codecs) Is that what you saw?
The clip that you posted looks exactly like what happens when Vegas tries to render DivX files. I’ve seen it before and I can’t believe that happened with an uncompressed file.
Please check that the files on the Vegas timeline are uncompressed (i.e., right-click | properties, check that Format: Uncompressed) and that they don’t have this jerky problem.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
No. I can composite 10 tracks with 3D Source Alpha without any problems. Maybe it has to do with what is on those tracks and how much resources they take up? 10 tracks of 8 megapixel still images might be a problem.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
Interesting operation. I would start by capturing direct to disk. You can use a program like On Location (formerly DV Rack) or you could buy a hard disk recording unit for the camera. This eliminates capture entirely.
Forget about adding the session to previous sessions as one movie. Why bother? Keep each session as it’s own movie on the DVD and you NEVER have to re-render ANYTHING. You don’t even need Vegas, just DVD Architect. If you keep each DVD project on a RAID, you just drop the new session directly onto project folder (which is now instantly captured). Then open the existing project in DVD Architect and drop the new captured file onto the menu and render. On a Quad-core system the DV to MPEG2 conversion for 15-minute session should take about 5 minutes (~3x faster than real-time).
This works because DVD Architect is smart enough to re-use the rest of the video that was already on the disc without re-rendering it. Then burn 2 copies from the DVD folders. I agree using regular DVD’s (not rewritable) will give you much faster burn rates and time is money.
Using just a hard disc recorder and DVD Architect you could hand the patient their DVD before they leave (they would have maybe a 15 minute wait). All original recording footage is archived on the RAID in the project folder. So in the time it use to take to capture the tape, you could be handing the customer a finished DVD!
~jr
http://www.johnrofrano.com
http://www.vasst.com -
This is something that Sony has to fix in Vegas and unfortunately they have not. For me, it is the single biggest feature request for Vegas Pro 9. They could do nothing else but fix the plug-in API I and would be perfectly happy with it. All plug-in are affected by this limitation.
Some plug-ins, like Mercalli, have tried to get around it by secretly rendering the clip so that it has access to the video. It’s unfortunate that they have to resort to these kinds of workarounds. Because of this, anything that requires motion has to be done in the Standalone version of Boris FX / RED 🙁
This is a definite productivity impact but not a reason to stop using Boris. What would you use? Nothing else plug-ins in any better because it’s Sony’s problem. Until enough people complain to Sony to get it fixed, it’s probably going to stay that way. So don’t just walk away… please complain to Sony about it. Tell them you want the plug-in API fixed so that plug-ins can integrate better. (hold on while I step down from my soap box)
~jr
http://www.johnrofrano.com
http://www.vasst.com