-
A few questions re: proxy editing, large video/project, and a weird blac preview screen problem (Windows PC – Vegas Pro 12)
-
[Blake Gibson] “Not printing to film. Going to web, and a larger master on disc. It might just be me be crazy but I tested CF High and it didn’t look as good as Filmscan 2.”
So what’s you disc subsystem like? Are you using RAID? Could it be that these large files are performing poorly because they are constrained by your disc I/O?
[Blake Gibson] “I’m a bit hesitant to upgrade as I always read horror stories of Vegas randomly crashing for no apparent reason, I believe mine is pretty stable at the moment apart from this crash.”
Then you’ll need to deal with all of the bugs that were fixed between Build 367 and Build 770. I can’t help you there.
Just so you understand the magnitude of this decision… you will be dealing with the bugs that are fixed in Build 394, 486, 563, 670, 710, 714, 726, & 770. Sony has issued 8 patches that you don’t have yet. Those 8 patches represent 141 bugs that were fixed!!! You can read about it here: Vegas Pro 12.0 Release Notes
BTW, If you are running a business you should have daily incremental backups of your system. This way if an update causes things to fail you can always get back to the state you had the day before. Anything less, IMHO, is playing with fire.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
Damn, it doesn’t work for me either.
The file imports and shows up fine as the source but when I encode it says something like “Handbrake can’t read the file” or something, I’ll double check again later when I’m at home.
-
I just read through all the bug fixes, thanks.
This one caught my eye:
“Fixed a bug that could cause a crash when rendering some very large projects to QuickTime format.”
I’m guess they only mean specifically TO Quicktime FROM non quicktime files? Like AVCHD to DNXHD or something?
That said, wouldn’t the 32bit memory limit apply because its using quicktime?
-
[Blake Gibson] “I’m guess they only mean specifically TO Quicktime FROM non quicktime files? Like AVCHD to DNXHD or something?”
That said, wouldn’t the 32bit memory limit apply because its using quicktime?
I think they mean rendering to Quicktime. Which means one output file, and the problem being only on large/long projects. The sources are not likely relevant.
On the front end of Vegas you have the file decoders. In the middle you have the video engine. On the back end you have the file encoder (render as). The file encoder has no clue what is going on in the video engine and no clue about the decoders.
-
OK thanks.
I stumbled across this thread in my travels, it looks interesting, this guys basically found an app that lets you use more than 2gb memory on 32bit exe/dll’s… apparently it only works to get around the crashing during render issue in Vegas. I wonder if it would work for the fileiosurrogate.exe:
https://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=4&MessageID=650217
-
[Blake Gibson] “The file imports and shows up fine as the source but when I encode it says something like “Handbrake can’t read the file” or something”
Do you have the CineForm codec installed? You need CineForm to read CineForm. I have the free GoPro Studio installed and it works fine for me.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
[Blake Gibson] “That said, wouldn’t the 32bit memory limit apply because its using quicktime?”
Yes, the 2GB limit due to QuickTime being 32-bit is still in effect. Let’s just say that Vegas Pro would not be my first choice of editor if I had to work with QuickTime files.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
I would not start messing with executables. If it were that easy, don’t you think the Sony developers wold have set that flag when they compiled the code? Something must not have worked for them to not make their 32-bit programs Large Address Aware since hey could have done this themselves.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
I installed Gopro studio the same day you recommended it and I’ve been exporting to Cineform just fine from Vegas in all flavours so I assume everything should be fine.
Just tested in Handbrake again and the error is “must first scan a source” even though when I open a cinfeform file it scans (it even says scanning showing a percentage, finishes and the filename is up in the source section, weird. I just noticed there’s an update available so I’ll try that tomorrow (currently on version 0.9.9.5530 64 bit)
-
Yeah thats true. I might have a play with I’ve got nothing I need done.
Reply to this Discussion! Login or Sign Up