Any More Workarounds for the NEO-HD/Vegas8 Bug?

MH_Stevens wrote on 3/6/2008, 10:38 AM
There is a well known incompatibility between CineForm NEO HD and Vegas8. CineForm says the bug is in Vegas, SONY as usual is out of site or in denial. For me, I am dead in the water as I can open no Vegas project with any CineForm files within as Vegas just simply stops working. HOWEVER, I know that Bob Grant, Serena Steuart and Bill Ravens have devised workarounds. However none of the these workarounds work for me and I'm desperate. So I'm asking if there is anyone else who has not found a workaround for this problem or who may have a new work-around to suggest. The workarounds I have tried are converting to mxf files to the Hard Drive with ClipBrowser and then converting or opening a regular mxf project with ClipBrowser and then rendering to a new track with the CineForm codec, but as I said neither of there work for me.

Comments

Bill Ravens wrote on 3/6/2008, 10:54 AM
Mike..

you sure your footage isn't corrupt?
what about trying it on another computer?
MH_Stevens wrote on 3/6/2008, 11:19 AM
I will go now and shoot new footage but footage works fine with ClipBrowser so I don't think so. I suppose I could get the trials on a different computer to try if new footage gives same result. Transferring the real licenses to a different computer is a nightmare!!!!!
StormMarc wrote on 3/6/2008, 11:24 AM
Mike,

I'm using Vegas 8.0 and Neo on a massive project with no issues other than some render crashes here and there. I captured everything and converted on the fly in HDLink. Since the latest version of Vegas and not using any JPEGs things have gotton much better for me. All footage was from Z1s.
Bill Ravens wrote on 3/6/2008, 11:50 AM
DON'T transfer your licenses. I know what that's like!
If the second computer has never had cineform on it, d/l the trial version.
johnmeyer wrote on 3/6/2008, 12:01 PM
no issues other than some render crashes here and there ...

Wow, if you don't classify "render crashes" as an "issue," then I don't know what an "issue" is.

Crashing during rendering is 100% unacceptable, under all scenarios, and if it is happening to you, send a trouble report to Sony. It shouldn't happen at all. Ever.

Cheno wrote on 3/6/2008, 12:06 PM
I tried the trial version of NEO HD and when it expired, did some weird stuff and I was unable to access the footage converted with it. Installing NEO player worked though and although I don't have NEO HD any longer, I have the updated Codec in Vegas to used as an intermediate. I just don't have the options that having the Cineform software allows.

I've heard of a few issues with Cineform and Vegas but not as many as just plain old problems with Vegas 8, so I'd consider it a blessing that Cineform is at least providing a good workaround for me, especially with Canon .m2ts

MH_Stevens wrote on 3/6/2008, 12:29 PM
Cheno: That is not working for me on my Laptop. Rendering within Vegas with the CineForm codec is failing just like using HDLink. Even the Prospect codec fails for me.

Bill Ravens wrote on 3/6/2008, 1:12 PM
how big is your file, Mike? Can you put it on a server where I can D/L it? I'll see if it works on my machines.
StormMarc wrote on 3/6/2008, 2:04 PM
"Wow, if you don't classify "render crashes" as an "issue," then I don't know what an "issue" is. "

While I agree that Vegas should be 100% stable, I went from constant crashing throughout the workday to every once in a while depending on how big the project gets. My main point was that Neo seems to work fine for me whereas the poster does not seem to be even be able to get the files to show up.

I think the problem is a combination of HDV, possible hardware combos and instability of Vegas that's obviously getting better. With DV I have not had any problems.
MH_Stevens wrote on 3/6/2008, 2:06 PM
UPDATE*************************************************

As I expected, the two trials worked perfectly, no need for a workaround, on my old slow laptop with the same SxS card and old clips.

So what's the difference in machines?
Both run Vista Home Premium but machine that fails is 64 bit.
Failing machine has GeForce 8700M GT card while old machine has 8600M GS
Failing machine is 2.5 GH T9300 and old machine is 2.0GHz T7300.
Failing machine is 4MB of 2x333Mhz old is 2MB
Any clues here?
Failing machine has Vegas and CineForm on the system partition so I may split drive, old machine has data on separate drive
farss wrote on 3/6/2008, 2:30 PM
I shot 1 hours and 10 mins with my EX1, double headed the audio at 24/48. The clip browser stitched the mp4s together just fine despite me forgetting to switch TC from Clock. Now that's something FCP/OSX can't do, he, he!
Dropped big mxf and .wav into V8, synced audio and encoded overnight to mpeg-2 for SD DVD. Took 6 hours, no crashes, no FXs, no cuts, apart from trimming the head and tail, all vanilla 8bit.

This was on a 2.4GHz Core Duo, not even a Core 2.

I'll repeat again what The Teacher told me. Vegas will not run on a Quad Core, commit charge will keep increasing and it will crash. I was told this with such certainty that further discussion on this point would have been a waste of time. The addition of The Mixer in V8 is far more important to sales of V8 as is the rework of SF. My protestations to The Teacher that SF9 is now so screwed up as to render it useless to those who've used it since day one seemed quite irrelevant as it's now more user friendly, easier to learn and easier to sell.

One doesn't have to join many dots to realise that the SCS ship has changed course. There's more money to be made selling boxes to school kids and mums and dads. That level of user doesn't make you spend serious resources getting things like SDI cards to work, they don't stress your code trying to render movies for the Silver Screen. They don't come to this forum and expect it to work.

The sale of a copy of a NLE to a kid wanting to make a skateboard movie makes more money than the sale of an upgrade to pains in the butts that expect everything to just work like most of us here. Do the same maths as any CFO would do, in many ways the stratergy makes perfect sense.

And again I really hope I'm wrong, so far the lack of any input to the contrary isn't encouraging.

Bob.


Bill Ravens wrote on 3/6/2008, 2:39 PM
sad, sad, sad
I'm gone to edius
there's no less than 2 full time GV moderators helping people on their forum
JJKizak wrote on 3/6/2008, 2:55 PM
1.....Shut off "DEP"
2.....Shut off "Defender"
3.....Always install the Cineform Neo after V8.0B
4.....Remove all drive indexing
5.....Shut off XP restore
6.....Shut off Windows firewall
7.....Remove all the cutsey windows stuff except "thumbnails" and "blend" fonts.
8.....Remove Norton if you have it and get something else.
9.....Your video card, motherboard, processor, sound card, burner, and monitor must be HDCP compliant.
10....Try to reduce your IRQ usage---if you don't use the serial or parallel port shut them off in the bios.
11....If it is possible do not use the media manager.
12....If your motherboard has built in sound and you use a sound card make sure the motherboard sound is shut off in the bios.
13....Vegas 8.0B is not supposed to work in Vista 64. (Mine does)
14....64 bit drivers are required profusely.
15....You can't have enough hard drives to split the loads up and get them off "C" drive.
16....New memory specifications have not been totally solidified and you might have to try different memory . (Straight from Gigabyte)
That's one reason why you might have to pull off the heat sinks to get them to fit into the slots.
17....My Cineform Neo works OK most of the time Vista 64 recognizes it but sometimes it doesn't and you have to turn on Neo again maybe several times then it works fine capturing from the Z1. Older Cineform projects also worked fine when assimilated into V8.0b.
18....Are you overclocking?
19....Are there any Air Force or Navy high power radars aiming through your house?
20....Are there any ham radio operators aiming through your house?
21....What do your power supply voltages read?
22....Did your processor retainer break a snap and is it overheating?
23....Is the processor fan runing?
24....Do you have a trojan horse on board?
25....Do you have a bad plug on your power supply?
26....Do you have any loose connectors on anything?
27....Do you have a small screw stuck behind the motherboard?
28....Are all the cards seated properly?
29....OOOPPSS. I have to boogie. Just got my new Cineform latin stuff.
JJK
MH_Stevens wrote on 3/6/2008, 3:51 PM
Some of the above make good housekeeping sense, but all those apps and processes are running on the slow machine that has no problem. The 64 bit and the dual drive is all that seems relevant. I'll go patrician and get back.

BrianAK wrote on 3/7/2008, 11:53 AM
Mike,

I am about as confused as you are right now. I had Vegas 8 and was capturing from an FX1 using Neo HDLink without any significant problems. Then I had a virus on my computer and had to wipe it clean. Fresh format, XP install, Vegas 8b install, Neo install (Neo changed to the latest version).

I have not been able to get my system running consistantly again, Vegas shuts down quite often. One difference as I mentioned is I updated to the latest verion of Neo on the reinstall, but I *can't* say thats the issue.

Quite frankly, Im not sure what has changed.

I am going to experiment with:

1) footage captured previously with older Neo/HDLink version
2) footage recaptured with current Neo/HDLink version
3) footage recaptured as m2t

If none of these work well with V8b, Ill switch back to V7d and try again. Ill post my findings.

Brian
MH_Stevens wrote on 3/7/2008, 5:47 PM
I'm looking into Nero also. The machine that fails has Nero8 while the old machine that does just fine is still running Nero7. I won't know until CineForm put build 158 up for download just to keep my new install as clean as possible.
JJKizak wrote on 3/8/2008, 6:33 AM
My guru buddy burned two Verbatim DVD+R DLs with chapter points using Nero 7.1 and when I play it back with Nero 8.1 I get hang ups at the chapter points intermittantly and then it will start up and skip about 3 chapters. I have the same performance with my Toshiba HDA-35 so I assume it is Nero 7.1 with the chapter problem. Have had no problems with DVD-A 4.0
JJK
Darren Powell wrote on 3/8/2008, 12:46 PM
I was posting about the NEO problem in Vegas Pro 8 months ago ... lots of people on the forum tried to help but with no luck. I couldn't render any NEO HDV stuff from my Quadcore ... fortunately I had a Dual XEON machine sitting right next to my Quad and copied my whole Cineform feature film onto a 2TB drive, opened it in Vegas Pro 8 on the Dual XEON box and was able to render m2t's from the Cineform source (still lots of render problems on the Dual XEON but it was much more stable than the Quad) ...

since then I've transferred the project back to the Quad ... broken it down into 10 minute chunks ... and have been able to work sort of ... and render out .wmv's for distributors and m2t's for checking in my local cinema ... but ANY project over about 1.2GB's in size as indicated by Task Manager will cause Vegas to lock up or crash when rendering. I had a nice long chat to Sony in the US yesterday (1 hour on the phone from Sydney Australia ... this Vegas problem is sending me broke ... and it's giving me the SHITS!) ... see what the very helpful customer service person at Sony said to me in my next post on the forum.

Darren Powell
Sydney Australia
MH_Stevens wrote on 3/8/2008, 2:07 PM
My probelem is now SOLVED.....................

I'm not sure just why but this is what I did:

Installed the latest NEO-HD build 158
Removed Nero8 Ultra
Put data files on a seperate partition with a page file

Mike