Dr. Dropout
Forum Replies Created
-
Did you use file>import>DVD camcorder disc?
-
Please before rolling back your Windows service pack try Vegas 6.0c. We have some fixes in this update specifically for some older Sony decks like the DSR-30.
-
Your best bet is to export an image sequence (.png) from a 23.976 (24p)Vegas timeline, open that in AE, make your adjustments, render out as a new 23.976 png image sequence, and reimport into your Vegas 24p timeline.
-
Re-Rendering in Premiere or using any other app or utility to try to “fix” this problem is not going to work. Sorry to say I think the best thing to do is get new downconverts. The “agony” you go through in a re-do of the critical prep phase (preparing new dubs for offline) will be much less painful than the massively expensive post production trauma you will experience when you show up with an EDL with every singe edit completely wrong.
I guess you could cut in Premiere- although I have no idea how accurate their EDLs are especially wrt to cutting 24p using downconverts.
Before proceeding any further though, we have a whitepaper describing the steps you need to follow if you want to use DV for HDCAM offline in Vegas:
https://www.sonymediasoftware.com/download/step2.asp?DID=513
Make sure you are completely clear on all the steps- assume any substitutions of processes or gear will put you back in the exact same spot you are in now. If you have further questions about this you could contact me at dr.dropoutATSYMBOLsonypictures.com
-
These are separate codecs, Sony YUV was written “in-house” specifically for Vegas and works both for SD and HD i/o.
In Vegas, the BMD codec can be used as a source file, but you’d need to convert to the Sony codec before printing to tape within Vegas.
-
If your drive array is up to the task you can capture and output Digibeta with a Decklink + Vegas – works very well. You could also consider having a dub made from a well-done DV master to Digibeta- many people have done this and it looks and sounds great (an SDI transfer is ideal).
-
If you can capture HDV in some other app, that means the driver is loaded on the box and you can capture HDV with Vegas 6 (6.0b is as of this writing the current version).
When you invoke the HDV/SDI capture app, under the capture app’s prefs>device choose IEEE/1394 MPEG-2TS (you should see the name of the camera or deck also). The issue at hand could simply be that Decklink is selected as the capture device rather than the HDV device.
-
What deck are you using? What Decklink model & driver are you using?
-
“Oh forgot to mention. If you have to re-install V6.0b, you would lose the updated files.
You can either re-install DVDA3 after installing V6.0b or make a copy of shared plug-ins>file formats>MCMPEG and then restore it after installing V6.0b ”
Not True- reinstalling Vegas 6.0b (or any earlier version of Vegas or DVD Architect) will not overwrite the MPEG components installed by DVD Architect 3.0a. Our MPEG components are shared between apps, and are versioned so the newest always overwrite anything older.
-
Re reducing the thread count to 1: this will make Vegas 6 tax the system similarly to Vegas 5 during rendering, and as such might help diagnose the render failure being reported. Maybe there’s a heat problem (just as an example) that gets exposed by using multiple render threads.
Render times and HT:
Hyperthreading is, as you know, very different from a true dual proc. HT is cool, there is some benefit, I run an HT system, but the future is (for both AMD and Intel) multicore, and it is with dual and multicore rigs that you’ll see the most benefits from the multithreaded rendering enhancements made to Vegas 6. We do have test projects that show render time improvements with HT… but true dual and especially multicore systems is where the threading changes really shine.