32 or 64 bit, benefits?

Cedric Cornell · February 3rd, 2010, 02:32 AM

Ok, I've upraded to W7 64, 8mb ram and 2 more hard drive (media and render) All seem to work well and render speed seem quicker, but will have to do some larger timelines for a proper test.

Even if there aren't big improvements, going to W7 was a good thing. So much nicer than Vista. At last folder/files in explorer show the way I want them, not how Vista randomly wants to show me!

Cedric Cornell · February 3rd, 2010, 02:03 PM

Hmmmm, getting a ton of artifacts when rendering. Didn't have this prob with my old 32bit sys :-(

Off to test the 32 bit version....

Edward Troxel · February 3rd, 2010, 04:02 PM

Make sure your render settings match what you were using before.

Cedric Cornell · February 4th, 2010, 01:14 PM

Aaaaah!
My mistake. Before I was rendering @ 1280x720 and my "aritfact" render was at 1920x1080. I think the artifacts/blocky come from too low bit rate for the higher resolution. I just tried 135mill max and 50mill avrage and it came out ok.

All the above done in MainConcept AVC

What are recomended bitrates for good veiwing on a pc??

Thanks

Adam Stanislav · February 4th, 2010, 03:04 PM

Quote:

Originally Posted by Duane Adam

Has anyone figured how to use 64 bit without the red picture issue? I went back to 32 bit until that's resolved.

The red picture is not an issue, and it has nothing to do with 32 bits vs. 64 bits. It is a tool for plug-in developers to see they have a bug in their code. Whenever a plug-in writes to an area of memory that is off bounds for it, Sony Vegas displays the red picture (assuming the plug-in does not crash Vegas altogether). Theoretically, an end user should never see the red picture since, theoretically, plug-in developers would see it before releasing their plug-ins and fix their own code.

If you are seeing the red picture in the 64-bit version and not in the 32-bit version, some plug-in has a bug that does not appear in the 32-bit version (of the plug-in) but does manifest in the 64-bit version. This is quite possible, as a lot of coding mistakes are not considered mistakes in the 32-bit environment, but bite after moving to 64 bits. You should note when the red picture happens and which plug-in is causing it, then inform the developer(s) of the plug-in, so he/they can fix it.

Mike Kujbida · February 4th, 2010, 05:51 PM

Adam, I have to disagree with you on the red frame issue.
There's on on-going discussion on the Sony Vegas forum called video events are sometime RED that you might be interested in reading.

Here's the response one guy got from Sony support when he filed a support ticket.

Yes, it does sound like yours is the same issue since you are seeing red and black frames when using high-definition *.jpg files in Vegas Pro 9.0c. There hasn't been any word of a Vegas Pro 9.0d release date yet. Please check back with us at sonycreativesoftware.com in a few weeks to see if there is any new information. I apologize for any inconvenience this may have caused, but do appreciate your understanding.

Adam Stanislav · February 5th, 2010, 12:20 AM

Interesting. Though I have only seen it in the 32-bit version and only when I was writing outside the proper memory area. As soon as I fixed my code, the red frame disappeared.

By the time I was compiling the 64-bit version my code was fixed, so I never saw the problem again.

At any rate, what I said and what the Sony tech support said is not necessarily a contradiction. It is possible some of Sony's own effects have bugs in them. And whether they are built into the executable or are in external plug-ins, the result would be the same.

February 3rd, 2010, 02:32 AM	#16
Cedric Cornell Regular Crew Join Date: Jan 2010 Location: Sætre, Norway Posts: 27	Ok, I've upraded to W7 64, 8mb ram and 2 more hard drive (media and render) All seem to work well and render speed seem quicker, but will have to do some larger timelines for a proper test. Even if there aren't big improvements, going to W7 was a good thing. So much nicer than Vista. At last folder/files in explorer show the way I want them, not how Vista randomly wants to show me! __________________ http://vimeo.com/no66 http://www.youtube.com/user/no66

February 3rd, 2010, 02:03 PM	#17
Cedric Cornell Regular Crew Join Date: Jan 2010 Location: Sætre, Norway Posts: 27	Hmmmm, getting a ton of artifacts when rendering. Didn't have this prob with my old 32bit sys :-( Off to test the 32 bit version.... __________________ http://vimeo.com/no66 http://www.youtube.com/user/no66

February 3rd, 2010, 04:02 PM	#18
Edward Troxel Sponsor: JET DV Join Date: Dec 2001 Location: Southern Illinois Posts: 7,953	Make sure your render settings match what you were using before. __________________ Edward Troxel [SCVU] JETDV Scripts/Scripting Tutorials/Excalibur/Montage Magic/Newsletters

February 4th, 2010, 01:14 PM	#19
Cedric Cornell Regular Crew Join Date: Jan 2010 Location: Sætre, Norway Posts: 27	Aaaaah! My mistake. Before I was rendering @ 1280x720 and my "aritfact" render was at 1920x1080. I think the artifacts/blocky come from too low bit rate for the higher resolution. I just tried 135mill max and 50mill avrage and it came out ok. All the above done in MainConcept AVC What are recomended bitrates for good veiwing on a pc?? Thanks __________________ http://vimeo.com/no66 http://www.youtube.com/user/no66

February 4th, 2010, 05:51 PM	#21
Mike Kujbida Inner Circle Join Date: May 2005 Location: Windsor, ON Canada Posts: 2,770	Adam, I have to disagree with you on the red frame issue. There's on on-going discussion on the Sony Vegas forum called video events are sometime RED that you might be interested in reading. Here's the response one guy got from Sony support when he filed a support ticket. Yes, it does sound like yours is the same issue since you are seeing red and black frames when using high-definition *.jpg files in Vegas Pro 9.0c. There hasn't been any word of a Vegas Pro 9.0d release date yet. Please check back with us at sonycreativesoftware.com in a few weeks to see if there is any new information. I apologize for any inconvenience this may have caused, but do appreciate your understanding.

February 5th, 2010, 12:20 AM	#22
Adam Stanislav Trustee Join Date: Oct 2009 Location: Rhinelander, WI Posts: 1,258	Interesting. Though I have only seen it in the 32-bit version and only when I was writing outside the proper memory area. As soon as I fixed my code, the red frame disappeared. By the time I was compiling the 64-bit version my code was fixed, so I never saw the problem again. At any rate, what I said and what the Sony tech support said is not necessarily a contradiction. It is possible some of Sony's own effects have bugs in them. And whether they are built into the executable or are in external plug-ins, the result would be the same.