Nigel O'neill
Forum Replies Created
-
One thing to consider is that AVCHD is highly compressed video and requires substantial compute power to playback smoothly on the timeline. SVP12’s native proxy editing only works effectively in draft and preview though… .
My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 12 (x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6
-
[John Rofrano] “Your video will become a little soft because of the stretching.”
John, you just answered a question I have been trying to solve for years! People have noticed my output was not as crisp as they were expecting, and I have been trying to determine why.
I think I have posted several times on this forum seeking an answer.
I’ll deselect the stretch setting and do a comparison now. Thanks!
My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 12 (x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6
-
It could be a driver issue or a hardware issue. Hopefully it is a driver issue.
Please update your signature with your system specs including Vegas version. It will help to diagnose the issue.
It is also possible the onboard firewire circuit in the camera has been damaged if other devices are being recognised but not the 1000P. I had a couple of Sony FX1’s get damaged this way. One was replace under warranty. Sony refused to replace the other. The board (then) cost over $1000 to replace.
Has this camera ever worked before with this computer?
Are you using a DV line protector between your PC and the camera?
My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 12 (x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6
-
The first pass analyzes the video, the second pass actually does the rendering and maximizes the quality:size ratio by lowering the bit rate for less intense sections and raising it for the more intense sections. So a 2 pass variable bit rate render should increase quality for a given file size.
-
Use these bit rate settings to fit your content onto 1 DVD with 2 Pass VBR encoding.
The calculator is freely available on the Internet.
-
I would love to use 12 but for the weird skipping I am seeing in the video in my output, be it WMV, M2T and 1080i. I reported it to Sony, and the moment they released an update, they closed my ticket.
Might be time for a machine rebuild.
-
Will, it’s unfair to rubbish Vegas just yet when the main consumer market out there probably still deals mainly in DVD. Many of my clients still want DVD’s, but expect the quality of bluray. They want delivery via web, but don’t have the appetite or bandwidth for the downloads at HD quality. It’s a catch 22 situation.
We also all saw what happened in the Betamax versus VHS war. It then got repeated in the laser disc vs Bluray vs HD video war. Unless consumers drive the uptake, the superior technology does not necessarily come out on top. Who knows, RED, 4K and 6K could become the format of choice for niche videographers, but Sony and companies like it don’t make money off a select few.
They would prefer to fleece the masses 🙂
-
[John Rofrano] “You should be creating DV Widescreen proxies. “
Ah, therein lies my problem. I was selecting the Render Video Preview check box in the Quadcam tab and clicking on apply, not the Render tab, plus I noticed the template defaults to NTSC, and in my case, has to be set to PAL DV WS proxies.
-
[heinz melus] “What do you exactly: you put your rendered piece into DVDA and set it up in PREPARE DVD. What method of the second layer do you use? Parallel or opposite. “
I don’t. I just create my chapters in the DVDA timeline and then make up my menus. I have never been asked once to place a marker for the split. My version of DVDA (5.2) has never asked for it.
I also don’t use DVDA’s fit to disc, instead I use Mark’s bit rate calculator to work out the correct bit rate in Vegas for the render process.
-
I’ll post my response in parts:
When the booktype field (bitsetting) is changed to DVD-ROM then DVD players are fooled and will think the user has put in a DVD-ROM disc instead of a DVD+R disc and will read it accordingly. This results in an increased chance that the player is able to read the disc and that’s why the ability to change the booktype field (bitsetting) is essential to a lot of users. Certainly owners of a DVD player that requires this field to be set to DVD-ROM, in order to work properly, will prefer a DVD recorder that supports setting the booktype field.
The Book Type is a field of four bits at the start of every DVD (in the physical format information section of the control data block) that indicates what the physical format of the disc is. Many devices will use this “Book Type Field” to determine how the disc should be treated. One common cause of compatibility problems is when a device does not recognize the Book Type of the disc that has been loaded, most likely as a result of the device being manufactured before that particular Book Type has been defined (e.g., most DVD playback devices made before mid-2004 will not recognize the relatively new DVD+R DL Book Type). For DVD+R, DVD+RW, and DVD+R DL discs, it is possible to change the Book Type field value to the value for DVD-ROM (or in some rare and unorthodox cases, even the value for DVD-R) in order to fool older devices that do not recognize newer Book Type Field values (this process is known as bitsetting).
Change Your DVD+R/DVD+RW/DVD+R DL Media to DVD-ROM using Nero Burning ROM
This assumes that you have a working compilation to burn
Put in a Blank disk into your DVD Burner
Open up the Nero SmartStart
Click on “Recorder” > “Choose Recorder”.
Select your DVD Burner
Then click on “Options”, then on “Book Type Settings”, set to “DVD-ROM” and click “OK”
Now whenever you use Nero to burn Media, it will use the BookType or BitSet to DVD-ROMNote: You will need to change it back to automatic once you are done.
