Vegas Pro 9- NAB

Just downloaded the trial of Vegas 9, and was LOVING that I could work with the native RED files we just shot over the last two weekends ... SO glad I don't have to have someone on a Mac with FCP do it ... however, now the thing won't render the project, with only 9 tracks (6 video, four of which are used for text overlay & timecode), and less than 5 minutes total project length. Trying to get it down to a 720P 4.8MB/sec WMV.

Sent Sony the automated error report upon crash. Sigh...
 
try rendering using a different code... Like some type of avi. Then use the windows media encoder stand alone version that you can download from ms... for some reason Sony Vegas does not like .wmv file too much.. Imagine that. I have had wmv work in vegas, but did have a problem before and this was my work around.. if your on 64bit os there is a 64 bit standalone wmv encoder also on the ms site..
 
Thanks, will check it out. Just tried the AVI option prior to seeing this, and now it has an error saying not enough system resources/memory. I only had Firefox open in the background, and I've got 4GB of ram, even though I've heard XP only recognizes up to 3GB ... anyway, going to restart my system & try again.
 
Cool, will check it out. I'm getting an error with EVERY render I try & do, whether it be to Quicktime, AVI, etc. They're all saying system resources are low, and that not enough available memory. I do a control+alt+del to check my task manager, and the memory which WAS running around 2GB to process (quad processor averaging 25% on all cores), is suddenly pegged out at a rediculous 6.2GB! Odd....
 
Norm Sanders said:
Just downloaded the trial of Vegas 9, and was LOVING that I could work with the native RED files we just shot over the last two weekends ... SO glad I don't have to have someone on a Mac with FCP do it ... however, now the thing won't render the project, with only 9 tracks (6 video, four of which are used for text overlay & timecode), and less than 5 minutes total project length. Trying to get it down to a 720P 4.8MB/sec WMV.

Sent Sony the automated error report upon crash. Sigh...
Click to expand...

Norm,

Been following your trial with great interest. Could the 'render' problem be because you're using a trial version?

Thanks for keeping us posted. I'll be very interested to find out how the native RED process works using Vegas 9.

Best of luck!:thumbsup:
 
Hey Robert, if it IS because it's the trial version, then that certainly doesn't bode confidence in me to buy the actual full license version ... would be nice to know it works for sure BEFORE I buy it! :)

I went ahead & packed up the eSata drive to send back to the producer. I spent all day yesterday trying different renders (MOV, WMV, AVI) with different sizes each ... every time, same result.

I can continue to play around with any sample footage that RED has available on their site, but I'm done trying to do it on this project. He can only pay about $300 to have all three projects edited (each one 5+ minutes in finished length), and I'm not desperate to resolve the solution at the moment for that price, as I've got other things I have to focus on at the moment.
 
RED SUPPORT!!!!!!!!!! YYYYYYYYYYYYESSSSSSSSSSSSSSSSSSSSSSSSSSSSSS!!!!!!!!!!!!!

I dont need to buy a mac now!!!!!!!!!!!!!1
 
Norm Sanders said:
Hey Robert, if it IS because it's the trial version, then that certainly doesn't bode confidence in me to buy the actual full license version ... would be nice to know it works for sure BEFORE I buy it! :)
Click to expand...

Certainly agree! It just doesn't make sense that nothing could be rendered and I was hopeful that you would have a good report. :)

Norm Sanders said:
I went ahead & packed up the eSata drive to send back to the producer. I spent all day yesterday trying different renders (MOV, WMV, AVI) with different sizes each ... every time, same result.
Click to expand...

Obviously frustrating, but thank you for updating your progress (or lack thereof).


Norm Sanders said:
I can continue to play around with any sample footage that RED has available on their site, but I'm done trying to do it on this project. He can only pay about $300 to have all three projects edited (each one 5+ minutes in finished length), and I'm not desperate to resolve the solution at the moment for that price, as I've got other things I have to focus on at the moment.
Click to expand...

Did you mention that you reported the problem to SCS? I'll be curious to see what they have to say and/or anyone else on this forum that has experience with Vegas 9 and RED files.

Thanks Norm!:beer:
 
Norm -

Try the following settings to get it to render:

Options>Preferences>Video

Change Dynamic ram preview to 750 Mb
Maximum number of threads to 3 (if you have a Quad core machine, otherwise 1).

Try render as wmv first.
 
Tried just as you suggested (Sony suggested the same thing in the response ticket), on rendering a 720P WMV file. Didn't even appear to get past 0% render, and got the same message. Even had the RAM Preview down to 24, and the threads down to 1.
 
Ducatimark said:
Norm -

Try the following settings to get it to render:

Options>Preferences>Video

Change Dynamic ram preview to 750 Mb
Maximum number of threads to 3 (if you have a Quad core machine, otherwise 1).

Try render as wmv first.
Click to expand...

Would this be the optimal settings for a machine running XP-32 with 4GB of RAM and a Quad (non-Nahalem)?
 
That's exactly what I've got going in my system, USLatin, and still no dice. In fact, Sony suggested setting the RAM preview all the way down to a rediculous 24 or 48 (I tried 24), and still didn't work. They've now sent me another response that I'll try tonight ... I'll paste it here:

Thank you for contacting Sony Creative Software.

As a troubleshooting step, please disable any anti virus applications that are currently running, as well as start up and background applications according to the directions provided below.

Press Ctrl+Alt+Del at the same time and you will see a list of the programs currently running (some users will have to hit the "Task Manager" button). Move over to the Processes Tab and click the "Image Name" heading at the top left of this window to view these items in alphabetical order. Close everything showing on that list except for the items listed below. To end a process, highlight it and click the End Process button at the bottom of the window.

End every process except for:

alg.exe
ccmexec.exe
csrss.exe
explorer.exe
lsass.exe
MsPMSPSv.exe
services.exe
smss.exe
spoolsv.exe
svchost.exe (there may be more than one of these, you can leave them all running)
System Idle Process
System
taskmgr.exe
winlogon.exe
wmiprvse.exe

You may have other Users logged into the system and displayed on this list, but make sure you log them off and close down their processes as well.
Please disable Startup applications and Background Services. To disable these items from starting, you can go to the Start menu and select Run. Then type msconfig into the field provided and press Enter or OK. In Windows Vista, there is a field at the bottom of the Start menu that you can type directly into.

Open the Startup tab, press the “Disable All” button and then Apply. Then go into the Services Tab, check the box next to “Hide All Microsoft Services” at the bottom of the window and choose Disable All. Then press Apply and OK and reboot the computer.

** Note: This measure is for testing purposes. If you are disabling these services, none of these services are critical for your computer to start or function. We recommend this troubleshooting step to remove as many variables from the problem as possible; though you may also be disabling desired services like anti-virus or portable device recognition services like iPod Service, etc. If this solves your issue, you may want to repeat the steps above to open the MSCONFIG dialog so that you can re-enable most of these services. You may want to spend some time re-enabling these one at a time until you find the culprit. Most likely there are just one or two services that are causing the conflict.
 
My reply to Sony today (sigh):

Again, I've done everything as directed in your latest response/instructions, and still getting the same exact result.

I previously had over 45 processes going, and would on average be running about 850-900MB of RAM. After following the instructions, it was down to 25 processes, and 650MB of RAM usage. Even after starting Vegas 9.0, it was only at 750MB of usage on the RAM.

When I came back, and saw the SAME error message (not enough resources, etc.), the RAM was all the way up to 2GB. It's as if Vegas is bleeding out some how. When I initially start Vegas, it's only showing it's using 100+MB of system resources .... everytime after the crash, it's always between 500-600MB. This time, it wouldn't even close out properly, and I had to end program.
 
Hi Norm, i was struggling with the same problem today - tried to render to wmv but stuck at 0% with 0% cpu usage.

From using vegas 8.0 alot i know that when i get crashes due to rendering then a trick that seems to work every time is to create a new vegas 9.0 project with same settings, do a select all in the old project and paste it in the new one. Obviously you loose any track or master settings (like fx, volume etc), but they can be easily recreated. Anyway, give it a go and try rendering wmv in the new project.
 
Thanks, alrooga. In addition to trying your step, I first tried the one they suggested ... neither of which worked (tried yours AFTER changing registry as they suggested below). I've updated & let them know.

SONY REPLY:

Hi Norm,

Thank you for contacting Sony Creative Software.

In most cases, a memory leak can be the direct result of a permissions issue in the registry.

Go to Start > Run and enter REGEDIT.

Within the Registry go to HKEY_CURRENT_USER\Software\, find the Sony Media Software folder (for older Sonic Foundry applications you would find the Sonic Foundry folder instead).

Right click on the folder and choose Permissions.

Make sure that Administrators, System, and any user account you log in with are all listed at the top. When you highlight each one they should have the Full Control and Read checkboxes turned on. If not, check each of those. Click Apply and Ok.

Do the same for the HKEY_LOCAL_MACHINE\Software\Sony Media Software\ folder.

The registry folders our software may create entries in are as follows:

HKEY_CURRENT_USER\Software\Sonic Foundry
HKEY_CURRENT_USER\Software\Sony Media Software
HKEY_CURRENT_USER\Software\Sony Creative Software

HKEY_LOCAL_MACHINE\SOFTWARE\Sonic Foundry
HKEY_LOCAL_MACHINE\SOFTWARE\Sony Media Software
HKEY_LOCAL_MACHINE\SOFTWARE\Sony Creative Software

If you still have a follow-up question on this particular incident, please feel free to update it. If you have a completely different question, please create a new incident.
 
This is a little disheartening as I had hoped Sony would have come out of the starting blocks bug free.


But I do want to thank you guys for being first to try it and keeping us up-to-date on any possible issues.


I may be wrong but I believe the free trials from Sony are the same as their full versions so what we see here could be par for the course.
 
I agree that I would likely be having the same exact problems if I had purchased it, because I THINK the only difference between full & trial is licensing/expiration.

The latest reply for me today was to create a new user account within Windows, and try installing Vegas 9 there, fresh. Personally, I think that's WAY too much work to get a program to work, but I'll go ahead & give it a shot just for giggles, to see if it works or not. Keep you posted.
 
You must log in or register to reply here.
Back
Top