MainConcept mp4 works unreliably for me. It's becoming hit or miss; when I start getting the unknown error message in 64 bits, I have to switch to 32 -- when it won't work there anymore, I go back to 64. Merely quitting and reopening the same bit version doesn't fix anything so I have to keep switching between the two; sometimes none of them work and I have to find another codec -- I've wasted too much time with this and have become irritable. .

<Have you applied the fix mentioned on this site or the cineform site? >

Which fixes are those?

I'll check it out now. Thanks.

Sorry, I am at a loss -- I can't find the "fix". The web page is a mystery to me. Could you please give me a link?
Tanks in advance.

See thread

http://www.sonycreativesoftware.com/forums/ShowMessage.asp?MessageID=794932&Replies=19

I think my problem is of a different ilk. I uninstalled Vegas 32 and so far all is OK... maybe a little too early to know for sure.

There should be no Black frame now, but both the latest Vegas and the latest CineForm components fix a number of issues. The new GoPro CineForm Studio Premium and Profession tools have these fixes (read more on new tools here http://www.studiodaily.com/main/news/13637.html.) We will be update NeoScene and the decoder only package next week to have these fixes.

You can new the new decoders now if you are not running Studio Premium or Professional:

software.gopro.com.s3.amazonaws.com/beta/NewDecoder762b618.zip?AWSAccessKeyId=AKIAJ2OHNE77HOUYJB6A&Expires=1328657233&Signature=JmfG/Q2vwWeyx/2QlBak7hv%2B3Cw%3D

To install:

Close any application that might be using CineForm files.
Unzip and copy over the older decoders here:
C:\Program Files (x86)\CineForm\Tools (64-bit systems)
or
C:\Program Files\CineForm\Tools (32-bit systems.)

The two files are CFHDDecoder.dll and CFHDDecoder64.dll and they will have a Jan 5th, 2012 build date. If the DLLs are in use (can't copy over them) rename them like to CFHDDecoderOld.dll and now the new files can be copied.

Trying to figure should I go to GO PRO or continue with NeoScene 5.54. Is GO PRO that much better? Just wondering if the old Cineform files will still function inV11 if I update to GO PRO.
JJK

Thanks Dave for the quick reply. As frustrated as I've been with various Vegas issues, it's always great to have a quick response from Cineform. I wish someone at SCS was doing the same... making their loyal Vegas users feel like their issues mattered. SCS has NEVER made me feel like my issues were important to them. All it would take is ONE person from SCS consistently perusing this forum and giving people some feedback. My one experience with SCS's ticket support system was a nightmare and took forever. I've never wasted my time issuing a support ticket again.

11b 525? where did you find that, the download site had 11(no letter) 521.
Just askin ;-)

The B is short for "build" and the 525 should be 520/521 I think. (Or perhaps 425?)

JJK & all NeoScene users,

The GoPro CineForm Studio (free) version is an awesome addition to your workflow. NeoScene is codec and basic conversion utility only for a good range of camera, whereas Studio convers only MP4/MOV H.264 files yet it adds real-time image corrections (Color, white-balance, reframing and 3D for GoPro HD cameras.) So NeoScene + Studio get the the sum of both. While this is not all the way toward a Premium license, it is a nice first step.

David I have neoscene so this update should work with it as well correct? I see there was a few name changes .Thanx

Sorry, I don't understand the question. NeoScene and GoPro CineForm Studio can be used together. Currently as NeoScene is the older of the two utilities install the new software last. We will have a new NeoScene build sometime next week.

Unfortunately, my problems with Vegas and Cineform continue (although this might solely be a Vegas problem). With David's fix I no longer get black renders for Cineform clips, but I'm still getting garbled renders. I have a project with about a 100 cineform clips... about 50% of the time at least one of them will render corrupted.... weird static sections.... vertical bands of colored noise. David had mentioned that Vegas has issues with high bitrate video data. Is this what's happening? If so, how can I fix it?

Right now, it's very frustrating to wait 2 hours for a render, and then have to look through the entire file for garbled sections... and find one and be forced to rerender.

Van,

One workaround you might consider is to render to a new track (Ctrl + M). That way when you find a problem you can just cut out that area and render a small section. I do this all the time because I sometimes need to make a slight change. As soon as I have everything the way I want it I smart render the track to a new Cineform file and it does so without having to recompress so it's fairly quick and does not compromise quality.

Hope this helps, Marc

I've done this before as well, but it doesn't seem to help with render times for the WMV files I'm creating. Even if the source is WMV, the render times are the same so it doesn't save me any time.