Liam Kennedy
Forum Replies Created
-
Sounds a bit like the “sync cursor with RAM preview issue”…. but I don’t think that problem happened unless you were trying to do a ram preview. The issue is whenever you have the sync cursor enabled (in V5 definitely) and you tried to select a loop and then do a RAM preview it would only ever display 2 frames of the selected loop (sound familiar?). The solution was to turn off Sync Cursor and then do your RAM preview. This seems to be fixed in V6b.
-
720 x 480 is far too small if you really need to do any panning/zooming. I regularly have images on my timelines that are 2000 pixles wide. This allows for quite extensive zooming. 7000pixels wide IS pushing it. You just needed a compromize between that and 720×480.
-
1) Vegas does not edit MPEG videos very well.. the sort of thing you are seeing is a pretty common “issue”.
2) Editing MPEG is not a very good idea… as it quicky degrades in picture quality when you render (as it re-compresses).
3) If you really do want to edit… the best answer is to simply capture the DVD into Vegas as DV AVI via a firewire video device (like a camera with passthru).
4) If the above does not seem a good solution for you… then you can download various FREE software that will convert MPEG (DVD) files into DV AVI. Do a search for DVD2AVI. There are many other ways to do this – a search on the web for something like VOB convert AVI will likely yeild some good examples.
-
Sounds like you are using the nested Veg feature of V6?
That does exactly what is says… nests an entire Veg within another Veg. If you don’t want the entire Veg… then you will have to create another Veg with just the bit you want. Or else… simply trim the Veg that you nested to the exact section you wanted (although you got the whole nested Veg on your timeline you can treat it like any other contiguos event and split it, trim it, re-size it, etc etc etc).
-
It only renders those W64 files if you do a PTT from the timeline (and it doesn’t take all that long to do that anyway). If you do your PTT from within the VidCap program it does not render the W64 files and directly outputs whatever DV AVI files you tell it to.
-
I had this error a long time ago when I was using my Firewire/USB drives in Firewire mode. Since I switched to USB mode… never had the problem again. So… just wanted to give yet another example of this to prove there really are 10,000 reasons for this.
In nmy experience USB drives have been far more reliable for capture/editing than firewire. Not sure why.
-
Do a search for posts by Chanimal over on the Sony forum. Click on his “name” in the search results and you’ll get to his account profile… then click on his highlighted “name” aagin in his profile and you can submit a question directly to him.
-
When you prepare a new DVDA project ready for burning you have to tell DVDA where you want it to place the files that you will eventually burn to DVD. If you tell it to use the same place as for a previous project… then it will happily overwright those previous files (it will give you a warning first).
Bottom line is… you need create a new folder for each of your projects.. you can do this easily when you are preparing your files for burning (there is a “new folder” button you can press).
I usually name my prepare folders so they are eaily recognizable for each project. Don’t just call the folder “DVD” as that way lies confusion and upset (as you have already found I think).
-
The PD170 does not shoot in
progressive mode. It just combines the interlaced frames in the camera…. so in my opinion it really isn’t of any significant use over recording in regular interlaced mode and then converting to progressive post-capture. -
I’ve heard that you don’t get scene detection when capturing HDV (post on another forum)…. it was quite a shock to me when I heard this. It will be interesting to find if ther is a third-party solution to this (for instance something like the optical scene selection in Scenealyzer Live – that could be applied at post capture). I have a feeling it has something to do with the MPEG m2t structure coming from the camera… but I am far from an expert in this.