[Jimmy Brunger]

GULP. It might have to come to that John..

Yeah – I was using 6.4 DL driver before and everything was rosy…I don’t understand! The driver is the ONLY software for the card, so that’s been totally uninstalled and re-installed with various combinations of Quicktime to try get it working again, but no joy.

Hadn’t thought of re-installing Premiere, could work I suppose. Would I have to re-install the whole production suite or just Prem do you reckon?

Oh btw – I got rid of the disc drive error – seemed to be a corrupt project that wasn’t letting me render. I use the same ‘capture/playout’ project almost all the time…maybe it’d taken a hammering!? Or maybe this Decklink thing ahs screwed it.

That said – the ‘not playing blank space in timeline’ problem still remains, even with a fresh project. John – in your experience is not being able to play a space before your first clip normal? I definitely used to be able to do it!

*Production Studio Premium CS2 / *Combustion 3 / Mocha v1
————————————-
Win XP Pro SP2 / Intel P4 3GHz / 2GB RAM / GeForce FX5200 / DeckLink Pro / Roland DS-5 monitors / Sony BVM-20G1E / DVS SDI Clipstation / Wacom Intuos 3 A4 / 110GB boot/80GB media/600GB RAID-0

[Jimmy Brunger]

Answer: NOPE.

Same problems as 6.6.0

Good god this is getting ridiculous.

*Production Studio Premium CS2 / *Combustion 3 / Mocha v1
————————————-
Win XP Pro SP2 / Intel P4 3GHz / 2GB RAM / GeForce FX5200 / DeckLink Pro / Roland DS-5 monitors / Sony BVM-20G1E / DVS SDI Clipstation / Wacom Intuos 3 A4 / 110GB boot/80GB media/600GB RAID-0

[Jimmy Brunger]

OK….6.4 driver works with QT 7.3, but subsequent drivers not working properly.

DL 6.3, 6.4 , 6.5.1 & 6.6 don’t seem to work with QT 7.2 which is odd (especially for 6.3 seeing as that was the current version at the time of release I believe.)

Anyway – I hope some of that is useful in you finding the culprit and fixing the later drivers.

I am looking at a HD card in the near future, but I’ve got to say for stability I might have to opt for AJA.

*Production Studio Premium CS2 / *Combustion 3 / Mocha v1
————————————-
Win XP Pro SP2 / Intel P4 3GHz / 2GB RAM / GeForce FX5200 / DeckLink Pro / Roland DS-5 monitors / Sony BVM-20G1E / DVS SDI Clipstation / Wacom Intuos 3 A4 / 110GB boot/80GB media/600GB RAID-0

[Jimmy Brunger]

Hi Kristian,

OK – I’ve been stepping back through the drivers and found out that this resizing/tearing at bottom problem is from DL driver 6.5.1.

6.4 works fine in PPro2…

..Only problem is that 6.4 won’t play with AE7 with QT 7.2!!?!
Everytime I fire up AE it says ‘can’t find quicktime component’.

Come on guys…this is using up valuable time re-installing all your drivers and is something you should really be doing yourselves.

I’ll try 6.3 and see if it all works…

*Production Studio Premium CS2 / *Combustion 3 / Mocha v1
————————————-
Win XP Pro SP2 / Intel P4 3GHz / 2GB RAM / GeForce FX5200 / DeckLink Pro / Roland DS-5 monitors / Sony BVM-20G1E / DVS SDI Clipstation / Wacom Intuos 3 A4 / 110GB boot/80GB media/600GB RAID-0

[Jimmy Brunger]

This is very weird…

OK – I capture via Decklink Capture
file format: Uncompressed 8-Bit (4:2:2 YUV)

I export movie as follows…
File Type: Uncompressed Microsoft AVI
Compressor: 8-bit YUV (4:2:2 YUV)
25fps PAL 720×576 UFF with Optimise Stills checked.
——————-

These are the same capture and render settings I’ve always used.

Since 6.6 driver I now get this mess at the bottom of screen either when rendering out a movie and then playing it back in Premiere, or when sending the original captured file to Media Encoder OR (strangle one this…) when I select motion for a clip in the effect controls. I don’t even have to scale it, but just highlighting ‘motion’ adds this mess at the bottom.

I’m going to have to go back to my previous driver (6.0) until this is fixed.

Please let me know what you find.

*Production Studio Premium CS2 / *Combustion 3 / Mocha v1
————————————-
Win XP Pro SP2 / Intel P4 3GHz / 2GB RAM / GeForce FX5200 / DeckLink Pro / Roland DS-5 monitors / Sony BVM-20G1E / DVS SDI Clipstation / Wacom Intuos 3 A4 / 110GB boot/80GB media/600GB RAID-0

[Jimmy Brunger]

Hi Kristian,

I uninstalled Decklink drivers from control panel and then rendered same clip from premiere and it worked fine…now reinstalled DL 6.6 and the problem is back.

Interestingly it only does this on captured footage. When I did some premiere test renders on some motion gfx clips originated from AE the problem wasn’t there…if that helps?!?

The other thing is – since I originally install 6.6 my output to b/cast monitor has not been showing up in AE prefs and so not working. After re-installing it now appears twice as “Blackmagic Video Output 2”. Is that normal? I’m just using the original one for now, but both work…is that a new feature or have I got some remnants that didn’t uninstall properly?

Thanks..this render problem is fairly urgent though I have a client in tomorrow and this could be a big problem.

*Production Studio Premium CS2 / *Combustion 3 / Mocha v1
————————————-
Win XP Pro SP2 / Intel P4 3GHz / 2GB RAM / GeForce FX5200 / DeckLink Pro / Roland DS-5 monitors / Sony BVM-20G1E / DVS SDI Clipstation / Wacom Intuos 3 A4 / 110GB boot/80GB media/600GB RAID-0

[Jimmy Brunger]

Is that right? I’ve heard of many people running XP32 with 4GB RAM and AE using either 2 or 3GB of that (depending on the switch) with the OS and other open apps eating up the rest.

Never heard of 3GB being the limit that XP32 can see…?

I understand 512mb+ will be used by OS and PCI-E black hole, etc. But I thought that’s what the 4th GB was for – so you have 3GB to use for all your other apps…

Can someone confirm/deny any of this please, cos I’m about to buy some more RAM and new procs/gfx card and don’t want to get it wrong!

Thanks.

*Production Studio Premium CS2 / *Combustion 3 / Mocha v1
————————————-
Win XP Pro SP2 / Intel P4 3GHz / 2GB RAM / GeForce FX5200 / DeckLink Pro / Roland DS-5 monitors / Sony BVM-20G1E / DVS SDI Clipstation / Wacom Intuos 3 A4 / 110GB boot/80GB media/600GB RAID-0

[Jimmy Brunger]

Exactly..you can lock individual comp windows to certain comps and also select one to always be the output to your broadcast monitor (the ‘final’ or ‘master’ comp presumably)

UBER twirl or whatever would be awesome though..like grouping layers in Photoshop.

*Production Studio Premium CS2 / *Combustion 3 / Mocha v1
————————————-
Win XP Pro SP2 / Intel P4 3GHz / 2GB RAM / GeForce FX5200 / DeckLink Pro / Roland DS-5 monitors / Sony BVM-20G1E / DVS SDI Clipstation / Wacom Intuos 3 A4 / 110GB boot/80GB media/600GB RAID-0

[Jimmy Brunger]

Can Combustion now import 3D objects natively then?

Other than that I think your only options for true 3D obj import are Eyeon Fusion (

[Jimmy Brunger]

Yeah, I reckon you could still get a better result with reshape or liquify..try splitting the different obvious shapes/groups into diff layers and morph like for like pieces, rather than the whole thing as one.

You might be able to pick up Elastic Reality by Avid on Ebay cheap secondhand..they don’t make it anymore, but it was the forerunner to Re:Flex and is still very good. With this you can employ several groups of boundaries that will freeze certain areas, but pull others the way you want them to go and you can start different parts of the morph staggered, whilst keeping it all one ‘layer’ if you like.

*Production Studio Premium CS2 / *Combustion 3 / Mocha v1
————————————-
Win XP Pro SP2 / Intel P4 3GHz / 2GB RAM / GeForce FX5200 / DeckLink Pro / Roland DS-5 monitors / Sony BVM-20G1E / DVS SDI Clipstation / Wacom Intuos 3 A4 / 110GB boot/80GB media/600GB RAID-0