Several important fixes in this build.

Build 5.2.2.281
Added: Affect Effects CS5 AVI exporter (NeoHD or greater.)
Added: 64-bit DirectShow encoder (NeoHD or greater.)
Enhanced: YUV dyanmic range of clip undergoing FirstLight enhancements. (NeoHD or greater.)
Enhanced: Updated the PDF manual.
Fixed: Black dots that could appear in Vegas (v9 or earlier) clips with extreme highlights.
Fixed: Very old (pre-metadata) CineForm clips could crash older versions of Vegas.
Fixed: XDCAM EX conversions of audio (NeoHD or greater.)

Neo3D http://cineform.com/downloads/Neo3Dv522b281-101103.zip
Neo4K http://cineform.com/downloads/Neo4Kv522b281-101103.zip
NeoHD http://cineform.com/downloads/NeoHDv522b281-101103.zip
NeoScene http://cineform.com/downloads/NeoSceneV522b281-101103.zip

Please report any finding that are peculiar to this build here, otherwise use regular support channels.

Thank you.

Not to leave out Mac users. These builds address different bugs/features then the PC versions, but brings out the same new codec revision v6.7.8

Neo3D -- http://www.cineform.com/downloads/Neo3DMacV5027b158-101103.zip
Neo4K -- http://www.cineform.com/downloads/Neo4KMacV5027b158-101103.zip
NeoHD -- http://www.cineform.com/downloads/NeoHDMacV5027b158-101103.zip
NeoScene -- http://www.cineform.com/downloads/NeoSceneMacV5027b158-101103.zip

I just refresh the Mac links (5 minutes ago) as the Panasonic AG-3DA1 support libraries where wrong. Please download again if you are using that camera.

Hi David,

I updated my Neoscene to the new Beta version 5.2.2 build 281 I then tried to render a clip that was captured with the neoscene and the result was no audio and video.

I did the render with Vegas 8c

Regards
Matthew


.

For what it's worth, the same bug from a previous build re-surfaced with this new one, where some of my clips in my timeline show up with lines through it. It's not a media linking issue (although that occured on one or two clips as well actually).

When I rolled back to the previous Cineform build and opened up my project again all media files were read properly in the time-line, as well as a couple clips that needed re-linking no longer needed re-linking.

Just thought I'd add that in case it helped the bug fixin'

Matthew & Craig,

Sorry, I'm not sure what either of your reports mean.

Matthew,
What are you rendering from or to? My testing to and from CineForm AVIs is working fine in Vegas I didn't test 8C, but uses the same components as Vegas 9 which worked fine. However, I'm checking on an encode issue with 10.0 64-bit.


Craig,
What are this lines to refer to? What NLE are they occurring in?

I converted an interlaced video with the new beta version and it makes the interlacing worse. I will PM you a link to the file.

I love to see that file, as I doubt it. We've done a lot to improve interlaced handling, it is better in this version than all previous releases. You didn't say what source was or product used or how you are viewing this interlaced badness. I will need the source and possibly a small sample of the conversion.

I guess I should've taken a screen cap while I was running that build.
I am using Premiere Pro CS5. All my media footage is the same, 1440x1080 1.33PAR.
It is an older project and media that was converted to CFHD quite some time ago, but still, it seems to work fine by rolling back to previous build.

Essentially the image in my timeline will not display and I only get a black screen. Instead of the thumbnail in the timeline, I just get diagonal lines to represent the image. Which is why it's not a linking problem, it seems to be not reading the file/codec correctly.

I remember experiencing this with that build from a while back that had a few glitches. I think it was in the original build switch to 4.2, but I'm not entirely certain.
If it helps I can install the new one again and take a screen cap, I don't mind.

Craig, CS5 is working fine, so please try again. If particular footage is not work, please send me (or support) a sample via yousendit.com.

Hi David,

Here is the steps that I take in Vegas 8c.


Clip: CFHD was captured with cineform

Project Template: HDV 60i ( 1440X1080 )
Render output: AVI
Template: 1080-60i intermediate
Video Formate: Cineform V6.7.8
Cineform Configure: Encoding High HD
Video Format: Auto
Pixel Ratio Auto

The Result is that I get an AVI without any audio or video.

Regards
Matthew

Anyone else that still has Vegas 8, please try Matthew's test.

Matthew,

I gather you mean the clip is black, as AVI without video or audio is not an AVI file. Can you confirm you got a valid file with black frames and muted audio?

David

I want to report that I just uninstalled and re-installed the Neoscene and everything is working well.

Thanks again
Matthew

So far we've fixed 64-bit encoding with Vegas 10 -- please redownload to get the *281a-setup.exe installer if you are a Vegas 10 user.

The interlaced conversion is working correctly, however CS5 interpreting the footage as progressive, need to look at that.

CS5 is fine, it is just displays both fields when is shouldn't, but it renders correctly. It is mostly cosmetic so it will not hold up this build, but should be fixed. I think this has been there for a while, I guess it is a sign that most customers have switched to progressive (thank you, I'm there with you.)

I have refreshed all the download link to 281b -- just use the link on the first page to get the latest. There was a problem for all 64-bit applications using the SDK, Vegas 10 and CS5. CS5 was falling back to using the VFW codec, so it still seemed okay, but it wasn't quite correct (interlacing issues above.) There are a few other fixes and patch in this, hopefully last beta release before 5.2.2 is gold. So this is the build to get.

- NeoHD 5.2.2 281b
- Windows 7 64b
- Vegas 10 - 64 & 32b


Still have the same "bug" with cineform files :

When original files ( AVCHD, MXF etc... ) are displayed at sRGB levels, cineform files are at Computer RGB.

Ok, I know...Why not, after all, .....
The problem is that it becomes very complicated to mix several codecs !

Didier,

That is actually now a Sony responsibility. Sony has taking over all the file I/O and decoding through our SDK. It is an SDK control to set whether vsRGB or cgRGB is output, and they haven't set this within 10.0a. It is an easy fix, so place encourage them to fix this in 10.0b. I have also reported this to Sony. If Sony is not able to address this soon, we do have a hack to override the decoder defaults, however that impacts all CineForm decodes, not just the ones in Vegas, so it is not our desired solution.

David, Thanks for your support.

However, they perfectly know that many of their customers use CineForm.
Is it a deliberate attempt to push us towards their "MXF"? ;-)

Next time I'll send them a payment, I will explain that the last 4 digits will be available on my next visa "10B".

Could you please tell me where 281a-setup.exe is. I tried the Beta with Vegas 10 and it messes up my mouse.

We are on ..281b-setup.exe now. We will have no influence over the mouse (nor could we), so that might be a question for Sony.

Thanks David. Strange then about the mouse, when I took out the beta the problems with the mouse went away.I will keep looking to see what I can come up with.

I'm also running Vegas 10 no my home PC, so what does the mouse does differently?

The mouse was getting stuck in a window. I uninstalled the mouse and the cineform beta and reinstalled, now no problems. The audio track was breaking up before the Beta now renders out fine.
Thanks, Dennis

All sounds like a fluke, as Vegas doesn't use any audio components from CineForm either. Happy it is now working.

You can say that again! It's amazing to me that any of this Video stuff works with all the programs having to work together. Vegas 10a is definitely very temperamental at best. I can't wait to see the fixes in 10b ASAP. Thanks for your help.

I click "Load to Multiple", it then tells me to select multiple files in the bin. I do this, then click the load button. Only the active video gets the snapshot. The others remain unchanged. Periodically when I do this, FLViewer will crash inside of First Light, but not always.

I havent updated in a while (been using 5.07b267) having just recently finished a project. So I decided to try the new beta (Neo4K version) and I noticed in the pulldown menu in the capture card Preview window some formats were missing or possibibly just labeled incorrectly.

For 720p profiles which I use often I'm seeing three 60p Overcranked profiles labeled:

HD720 5p 8-bit 4:2:2 (Overcranked 60p)
HD 5.99p 8-bit 4:2:2 (Overcranked 60p)
HD720 6p 8bit 4:2:2 (Overcranked 60p)

What happened to HD720 59.94fps 8-bit 4:2:2 profile? 60p 8bit? and 50p 8bit (overcranked)? I'm assuming these are just labelled incorrectly? since I never heard of 5p, 5.99p or 6p

I went back and downgraded to previous subsequent versions (which I downloaded but never installed) and this omission seem to have started around 5.11b270, at least with Neo4K packages, not sure about the others.

Added: Affect Effects CS5 AVI exporter

What does this mean? Should we be able now to export 12-bit files?

Yes you are export using deeper precision with a native AE exporter.

I installed the new updated recently but haven't use it yet.

b4 the v5.0 neoscene, we would restart the computer, which takes about a min, and then open the project to render out.

I couldn't play the guessing game anymore. can't even predict when the clip will black out.