Mactrix
Forum Replies Created
-
Did you understand the Lumiere HD-workflow?
It will convert the footage, so you must only choose a format
that is supported by BMD … -
First solution: Sell the SD-card and expand your HD-card with a multibridge to get more I/O-options.
Second solution: Sell the SD-card and buy an AJA Io. You can use them together on one system and
the analoge converts are a bit better. Also with FireWire you are very flexible to use it on several stations. -
The luma/chroma-shifting is a huge problem that occurs with BMD-cards
since a while. Yet in 2004 I had that problem – not with FCP (4.5) but in
After Effects and only inside a 16-Bit project using 10-Bit footage. When
rending out in 10-Bit again there was a luma/chroma-shifting. The image
was much more brighter and also the saturation of colors changed.Since a while the problem occurs in FCP.
First scenario: 10-Bit BMD sequence, only in rendered files.
Solution: Turn off HDR-Rendering (high-precision YUV) in FCP and use
8-Bit YUV-Rendering instead.Second scenario: Other codecs are effected (like DV, DVCPRO HD).
Solution: Kick off the BMD QuickTime codec-component out of the Library
folder.
Alt-Solution: Try to change White and Super-White-Settings for your
sequence.There is also still a problem when working in After Effects with BMD
10-Bit footage in 16-Bit project. The picture gets vertical lines and
the colors are totally wrong (like red becomes violett). Change the
project-settings to 8-Bit than. You can also move the BMD-component
out of the QuickTime folder and use AJA HD-codec component instead
inside a 16-Bit project. But you will still have a chroma/luma-shifts
when rendering out to other codecs than the original one (like Microcosm
when you want to preserve an alpha-channel).If you work only in SD try to not use BMD-codecs. Move them out of the
QuickTime folder in the System Library. Use only Apples uncompressed
codecs instead. For HD there is no solution because the Apple codecs are
not for HD.It seems that with AJA cards and AJA-codecs (for HD) this problem does
not occur. If using AJA but with installed BMD-codecs (QuickTime component)
the problem occurs also with AJA.Difficult to say at his point if it’s a BMD or Apple/QuickTime/FCP-Bug. It has
something to do with Gamma-Settings and there are reports that QuickTime
changes Gamma-values in general … but for what reasons? -
Someone here can say for sure that FCP is doing always
a proper insert edit back to tape without worrying to get
black frames or an offset? I know so many people who
start praying when inserting back to tape, no matter if
AJA or BMD. And yes, it’s PAL …– all settings are correct
– everything synchronized
– problem does not always occur …… but for insert edits there can’t be sometimes or mostly.
It must work always, it must be proper and accurat. You
could destroy your master tape … -
Why not making a MPEG-2-Loop inside DVD Studio Pro
and taking a 30 USD DVD-Player instead … -
Like the description “anamorphic” says, 16:9 is a squeezed 4:3 image.
It is stored on tape like this, the pixel resolution is the same than
4:3 and you edit it like this – there are no codecs for anamorphic.The only thing FCP – or your BMD-settings – can do is to unsqueeze
the image on you computer display. On your videomonitor you have
to press the ‘aspect’ or ’16:9′-button.Open the item properties (apple + 9) to see if the checkbox for
‘Anamorphic’ is checked. -
Animation is a compressed codec as well.
The compression is lossless with quality set to 100%.
Animation is 8-bit.PNG uses a lossless compression no matter which filtering
is used. The prefiltering is just a analyse of pixels for
optimizing the compression.
PNG ist 16-bit in general but the quicktime-codec seems
to be limited to 8-bit -
Your DVD-Player must set to play back PCM-Audio
trough the digital outputs. 5.1 won’t work with the
AJA Io or the G5 optical input.