Vegas 10 not reading Neoscene Cineform files

[Bill Mash]

Having exactly the same problem after upgrading from 8.x to 10.x. I’m stuck using both versions as a work-around. As you probably already know/understand it won’t recognize them in a veggie file either.

-Just because you can doesn’t mean you should-

[Frank Rizzo]

So I can’t create a veggie file in Vegas 9 and then work with it in 10? Yikes. So is the only workaround that if I want to use Cineform I need to stay in 9. Not a great solution at all. Seems like I’m going to have either pull away from Cineform or Vegas 10 for awhile. Since I took advantage of the cheap upgrade to 10, I guess I won’t go past the trial on Cineform. Unless there’s a better idea out there — if so I’d love to hear it.

[John Rofrano]

You need to upgrade Cineform to the version that supports Vegas Pro 10. For NeoScene that’s 5.2. I use Cineform in Vegas Pro 10 both 32-bit and 64-bit without any problems.

~jr

http://www.johnrofrano.com
http://www.vasst.com

[Frank Rizzo]

Wonderful. Thanks for the info.

BTW, do you still use the 32-bit version because there are some elements still missing from the 64-bit version? I used to the 32-bit version for 9 when I first got it, but now it seems as if the 64-bit version has all the same rendering templates. Do I still need the 32-bit version?

[John Rofrano]

[frank rizzo] “BTW, do you still use the 32-bit version because there are some elements still missing from the 64-bit version?”

If you still use 32-bit plug-ins like Magic Bullet, then you still need the 32-bit version. It all depends on what plug-ins you use.

~jr

http://www.johnrofrano.com
http://www.vasst.com

[Lance Bachelder]

Where did you read that 5.2 supports Vegas 10? I’m a long time Cineform user and use NeoScene and Neo4K and have the latest installs on both my workstations – neither which work in Vegas 10. Yes you can read the files but you cannot create a custom render using Cineform codec – the pulldown is grayed out.

Lance Bachelder
Southern California

[John Rofrano]

[Lance Bachelder] “Where did you read that 5.2 supports Vegas 10?”

I originally read it from David Newman, CTO of CineFormon on the Sony forums where he posted to let us know that 10.0 needs NeoScene 5.1 and 10.0a needs NeoScene 5.2. Once I installed NeoScene 5.2 it started working again with Vegas Pro 10.a. So I didn’t just read that it works… I know that it works because it’s working on my PC.

[Lance Bachelder] “Yes you can read the files but you cannot create a custom render using Cineform codec – the pulldown is grayed out.”

If you are talking about the “Configure” button, Sony is aware of this and admitted that they ran out of time and will enable it in a future update to 10. It is hard codec to render at FilmScan quality right now.

~jr

http://www.johnrofrano.com
http://www.vasst.com

[Dave Haynie]

My PC, and the Cineform people, told me.

You need V5.20b277 or later.

What I don’t understand — why the need for special support. This is, after all, an AVI file… supported under the Video for Windows or DirectShow subsystem. In previous version of Vegas, it just worked. Cineform just loaded or wrote, just as pretty much any other CODEC added under the Windows or Quicktime multimedia subsystems will. For example, the same Avid DNxHD CODEC I had installed for Vegas 9 worked for Vegas 10.

The one obvious difference here: Sony explicitly mentions support for Cineform. They have some level of integrate support for Neo3D:

Vegas Pro 10 provides integrated support for CineForm
Neo3D files. After the CineForm Neo3D product is installed,
Vegas Pro can read and write files including smart rendering
for I-frame AVI only CineForm content.

So is that it? If so, you’d think there would be a check-box to disable the pseudo-integrated support (“pseudo”, in that you still need Neo3D installed, they’re not enabling that out of the box stand-alone) and just use VfW/DirectShow for import. Cineform didn’t stop working in other applications when I installed Vegas 10.

With that said, I was in a hurry to get back to work, so I bough the Neo 5 upgrade. It works as well as ever, now.

-Dave

[John Rofrano]

[Dave Haynie] “What I don’t understand — why the need for special support. This is, after all, an AVI file… supported under the Video for Windows or DirectShow subsystem. In previous version of Vegas, it just worked. Cineform just loaded or wrote, just as pretty much any other CODEC added under the Windows or Quicktime multimedia subsystems will. For example, the same Avid DNxHD CODEC I had installed for Vegas 9 worked for Vegas 10.”

Nope! What you’re missing is that in Vegas Pro 10, Sony is now using the Cineform SDK so it is handling Cineform in a completely different and more efficient way now. That’s why the need for an upgrade to match the SDK version. It’s not just another VFW codec anymore.

~jr

http://www.johnrofrano.com
http://www.vasst.com

[Dave Haynie]

Yeah… ok. Once again, “why the need for special support”. Ok, they’re using Cineform’s private SDK. That still shouldn’t have prevented the use of older versions via VfW/DirectShow. I mean, in the old days, I could use the Sonic Foundry/Sony DV CODEC, but wasn’t locked into using a standard one from VfW/DirectShow.

What’s the point in this — what do we get in return? While I did buy the NeoScene upgrade, Cineform pretty much just worked before. Now, it’s flakey… I was trying to render from the timeline just tonight, and it crashes. First time I ever had Cineform crash on me (yeah, it’s Cineform… rendered the same to Sony Lossless and to MP4, no worries). I’m all for real progress, but not unnecessary complexity that actually runs retrograde.

-Dave