Jeremy Rasnic
Forum Replies Created
-
Try this and see if it works- change the file extension from M2T to mpg.
j razz
-
The page file usage is denoted as PF and it should be located right below your cpu usage graph.
Instead of rendering to a new track, try “File”–>”Render As” and then choose your settings there.
j razz
-
I think (but could be wrong) that it is limited to M2T files. That is why I recommended utilizing Vegas pro 8’s 30 day free trial to see if my assumption is correct.
j razz
-
I am unsure if the platinum version is capable of dealing with AVCHD files currently. I know that Vegas pro can. Download the trial of pro8 and see if it recognizes the files that you currently have on your machine from your camera. It is a free 30 day trial.
About the issue of it not seeing the camera, apparently it used to correct- as you stated that you had previously downloaded files on your system. What has changed between then and now? You should be able to just copy the files over to your hard drive from the camera nd drag them into Vegas. You do not want Vegas to edit of your cameras hard drive.
j razz
-
What format are you encoding to for output? Attempt doing an encode in an avi wrapper so that you can pick up the encode where it left off and then continue. I think the issue may lie with the mov files but I am unsure. Using the juicer, is there a way to export them as avi files with alpha channel? I haven’t used the juicer in a long time.
Also, based on the file types, masking and amount of items on the 30 second timeline, it does not suprise me that it is taking a while to encode. You may be running into ram issues. If you are willing to try it again, watch your pagefile usage under the task manager and see if the level climbs and plateaus at your maximum page file usage when the encode hangs.
Let us know.
j razz
-
Yes. You can install the programs elsewhere. I doubt you will see much of a difference. However, I would recommend that you encode/render to another drive other than the OS drive or the source file drive (drive that contains your unedited original footage the Vegas is pooling from).
j razz
-
Remove any 3rd party audio plugins (take them out of the sony folder and place them elsewhere. If it starts up after the removal then place them back in one by one until you find the culprit.
j razz
-
What is the error code in device manager associated with the 1394 device (or are firewire devices even showing up)? Of course, 64 bit OS’s are not supported currently but it does not make any sense why you cannot get firewire to be recognized on your xp 32 system. Have you tried uninistalling the firewire card and reinstalling it via device manager?
Firewire can burn out your firewire port on your cam and card as its ground is not like the ground in the USB. The USB grounds first then makes contact with the other leads. You may have burnt it out. Can you hook up your camera to anything else to see if it is recognizable?
Any more details you can provide?
j razz
-
Take another look at your keyframes. Make sure they are how you initially set them up. Scrub through them and see where the issue starts and you may want to delete the keyfram that is there and replace it with a copy of another and place the arrow where you want.
Hope that helps.
j razz
-
I just got a westinghouse 26″ LCD HD monitor. I got it for under $400 after the rebate and a good deal from dealnews.com. It is a good monitor and westinghouse has come a long way. You could easily get two of them for well under your desired price. Now, with that said, I would not depend on them for color correction, but for viewing the footage and editing, they work just fine. Also, it does not have dvi but hdmi (it comes with an hdmi to DVI cord and a VGA cord). It also has speakers built in that I do not use so I cannot even comment on the quality of that.
j razz