Rob Alexander
Forum Replies Created
-
the whole project and media is in prores 422.
I suppose one of the real problems here is that almost nothing (and I mean simple resizes and speed effects) is seen is a full res realtime effect for output and so has to be rendered – the prores codec is clearly very clever but appears to place a massive hit on the processors.
-
These people on the street – sped up?
-
I don’t know whether it’s fair to call the Harding a con. It’s just testing to standards laid down by OFCOM – and these haven’t changed in a long time. Problem is (and that’s why so many more programmes are getting caught out) that the Harding’s much better at testing to these standards than it’s predecessor the GORDON box!
I’m afraid off the top of my head I can’t remember the numbers but it detects an x percent luminance change over x percent of the frame – more than 6 of these in 2 seconds and you fail. A classic example is paparazzi at a premiere, all those flashes going off even though they don’t white out the entire frame is enough to trigger the Harding, it’s not flash frames or fast cutting necessarily. And as mentioned above repetitive patterns can trigger it too.
The chances of a fit being caused by any of these may be remote but these are litigious times and the broadcasters are protecting their arses.
-
Can you describe the shots that you’re failing on. Often it’s something that you don’t necessarily think of as a flash – for example a close up of flickering flames.
-
Thanks but I’m sure I’ve heard that you can set up Qmaster to use the processors much more efficiently by creating multiple instances of compressor – or something like that!
-
when it slows down try turning your video output off
and see if things go back to normal. This may be a blackmagic thing. -
Beth,
from what you describe you ARE editing the SxS natively – the SxS is the card, XDCAM EX is the format.
You don’t mention whether you’re using any video cards (blackmagic/AJA etc). If you are I’d suggest uninstalling the drivers then reinstalling. Also trying to play your sequences with external video off to see if it makes a difference. You should try trashing your FCP preferences too.
The suggestion to drop your EX footage into a DVCPRO HD sequence will work as long as you render all the clips, if you’re still editing then you’re going to be rendering every time you make a change and will end up with a huge amount of render files. Leaving the clips unrendered will likely INCREASE the load on your processor. However to convert your EX clips to DVCPRO HD you should select them and then use media manager to transcode to DVCPRO HD, then work in DVCPRO HD sequences. As stated before, the demands on your FW400 connection will be higher but seeing as you’re using DVCPRO HD from your P2 cards without issue should be OK.
RAM does look like the probable cause of this though.
-
I’ve read bad things about the input lag on the Dell displays, any thoughts? Also are they HDMI 1.2 compliant?
Thanks
-
small correction – going to master 50i so I guess the sequence will be 50i, however wise words about putting interlace material into a progressive sequence would be useful still.
-
Carsten,
did connecting analogue component sort out the problem?