[Bill Clark]

Whoops – discovered my own problem – didn’t like an extended network link. copied everything to the new hard drive and it worked fine….

Panic of Rutland.

Bill Clark
Origami Films
Slate612

[Bill Clark]

Did you get this fixed – I just moved to a new HP 8600 and have the same problem – probably another QT nasty…

Bill Clark
Origami Films
Slate612

[Bill Clark]

I’ve had this problem too when exiting Avid Express Pro. I didn’t get it on the last version only when I upgraded to 5.7. I’ve reinstalled twice and styill have the problem. Running on AMD Opterons 3 gig ram 3 TB drives etc – so memory / performance isn’t a problem. Any more ideas?

[Bill Clark]

Thanks – clears things up in my mind – I’ll stick with 25i…

Bill

[Bill Clark]

Thanks – sound advice – god i love this site….

[Bill Clark]

Thanks for this – sorry I didn’t get back sooner – been away. I think I’m running the most recent Xpress Pro 5.2.4, upgraded it around march – on dual opteron 250s with 3gig Ram and a Tyan Thunder board. nVidia quatro card and three separate 1394 cards.

The edit house digitised the media at 1:1 via Adrenaline on to a Lacie and I brought it home and pluggede it in. Avid saw it was there but said it was unsupported and I should transcode it. So I tried that but it didn’t happen – I’m not sure now what the problem was. Anyway, I ran out of time and went back to digitising the rushes via the DV clones I’d had made in case of such an eventuality. I think the mojo was a red herring – as I understand it its main use would be in playback to a monitor – which I don’t use anyway…

I have a big shoot starting in 10 days and I’ve been looking at buying a firestore – but I’m not suree if it digitises at 1:1.

Any advice would help and be appreciated.

Thanks

Bill

[Bill Clark]

Thanks for this – the transcode idea is a good one. Hadn’t thought of that. Avid Express could see the media – just labelled it in compatible format – but I thought it could read 1:1

[Bill Clark]

Just to let you know that I did contact Gridiron. They identified the problem and they are now creating an updated version of Nuclear pro to fix it. Very, very impressed.

[Bill Clark]

Generally I can see the potential – it has crashed a few times on larger – up to 10 layers of precomposites – but I agree the nuclear pro support team are very on the case and are really trying to help. Specifically I have one big problem – on background renders – the first lot go through fine – but subsequently added bg renders cause it grief and it quits with an “error 10” – meaningless message.

Anybody else had this?

[Bill Clark]

I had it and it turned out to be a memory problem. Check your available memory – maybe increase the size of your cache – purge all… Just a thought.