[Jimmy Brunger]

Bizarrely I’ve just gone back in to PPro to recreate the problem with GPU on and it’s not doing it now!?!

However I am now getting a ‘Error compiling movie. Unknown error’ message when trying to export from AME again!

IT just gets weirder…..

——————————-
Production Premium CS5.5 – Mocha v1.5
MacPro 3,1 8-core 3.2GHz / 32GB RAM / NVidia Quadro 4000 / OSX 10.6.8
Decklink Extreme+ 3D / 3TB RAID-0 local / 6TB XServe + United Digital RAID on 10GbE

[Jimmy Brunger]

Will do! Thanks for your help Jon.

——————————-
Production Premium CS5.5 – Mocha v1.5
MacPro 3,1 8-core 3.2GHz / 32GB RAM / NVidia Quadro 4000 / OSX 10.6.8
Decklink Extreme+ 3D / 3TB RAID-0 local / 6TB XServe + United Digital RAID on 10GbE

[Jimmy Brunger]

Hi Jon,

Thanks for your speedy reply!

Just tried what you suggested (new sequence @720×300 square pix > drop HD seq in + scale to frame size)…..

I am now getting the ‘tearing’ problem in the preview of timeline. HOWEVER – when I select the motion tab in effect controls – i.e: select the clip’s transform handles – it looks as it should. As soon as I deselect Motion it goes back to nasty white noise!

I then switched off Mercury GPU acceleration and then rendered the now red work area – all fine!?!

So looks like a Mercury/CUDA/Quadro problem?

Anyone had this before? The quadro has been amazing for me throwing multiple formats together and editing/scaling/messing with clips on the fly, so ideally don’t want to have to go back to rendering every time I want to view an output.

——————————-
Production Premium CS5.5 – Mocha v1.5
MacPro 3,1 8-core 3.2GHz / 32GB RAM / NVidia Quadro 4000 / OSX 10.6.8
Decklink Extreme+ 3D / 3TB RAID-0 local / 6TB XServe + United Digital RAID on 10GbE

[Jimmy Brunger]

Ah ok, good to know! Thanks for the reply Petros. I’ll settle with messy labels for now then!

[Jimmy Brunger]

Seems I can only label in timeline if there is linked audio present. If I have clips with no audio I can’t colour them up – is this normal?

Thanks.

[Jimmy Brunger]

Hi Brian,

Yep that actually seems to be working! Odd, as I’ve only had CS5.5 install for a week or so – not sure how the prefs could get ‘clogged up’ that quick, but hey ho we’ll see if that keeps it running smooth.

Cheers,
James.

[Jimmy Brunger]

Hi Edward,

Is this a feature that is being looked at for further .point versions do you know?

DoF seems to have ‘some’ effect on the ZW layer as a whole (it softens it slightly) but doesn’t seem to be manipulable. Should I be able to see DoF on the *whole* layer, for instance if it was way back from the camera (but not ‘across’ the layer) or is it just not supported full stop?

Thanks,
Jim.

[Jimmy Brunger]

Hi Edward,

Yes it is literally when I select the layer. It seems to flick between 2 of the 3 ZW layers I have in this particular comp depending on how many times AE crashes/reboots.

Interestingly (possibly?) when I remove the lights from the comp and reduce the project down the problem seems to go away. Obviously not ideal but thought that might help you guys troubleshooting bugs…

How far away is 5.0.6 do you know? I’ve got a few options for how I could tackle the 3D text for this project, but I need to make a jump one way or another in the next few days.

Cheers,
Jim.

[Jimmy Brunger]

Thanks guys,

I think what I’d done was install the drivers the wrong way round or something – the GPU driver wasn’t registering for some reason. Appears to be working now.

Quadro is ripping through everything I throw at it now! No more waiting for renders just because I scale a clip up by 1%! Joy.

However I have had a couple of mac ‘screens of death’ since installing it. Rebooted just now and seems to be ok touch wood. I wonder could it be anything to do with me having my Radeon x1900T running at the same time? I can’t get the Quadro to see my Cinema Display, so just using it as a GPU slave and running monitor off the ATI…is this a bad idea? Also, I’ve noticed that the ATI card will only run 1 display at a time when Quadro is installed (it used to run a 30″ ACD on DVI and then a 720p plasma via VGA).

Does this sound like an ATI/Nvidia conflict to you guys?

Last thing – Timewarp missing from PPro CS5!? What is the alternative now? A bit frustrating that when I open up an existing CS4 project in CS5 it just deletes any reference to timewarped clips with no warning – so I couldn’t even try to recreate the warps with Twixtor or the clunky time remapping in PPro.

Is there a work around for this?

Cheers,
Jim.

[Jimmy Brunger]

Good to see that more and more people are coming onboard the Premiere Pro train. Hopefully this will encourage more pro edit studios and freelancers to embrace it and Adobe to keep ontop of weeding out any remaining bugs and keeping support top notch!

Is this the end of FCP’s supposed reign in the Pro field then? Seems like Apple have just consciously given up and happy to pass the torch over!?!