Bill Portune
Forum Replies Created
-
I’m using 6.0.1 and restore DV50 footage from many different version of FCP including 5.1.4 and haven’t had any problems at all.
-
This has been an annoying on-going problem for me since moving to Boris with FCP. The “jaggy edges” are most noticeable when using italics. EVERY time I use text I have to use a blur filter to help smooth the edges. When I need high quality text I use Motion…
-
I agree with the initial scenario! From my point of view, it seems the only major advantage of the Io/HD doing the compression onboard is on capture (enough compression to send an HD signal down the FW800). Otherwise I think there may be a disadvantage since your CPU(s) must recompress to pro-res before sending it back down the FW800 to the Io/HD for output. This may indeed cause less RT playback than a PCI-E card. – FWIW
-
[Bill Portune] “NTSC issue”
…any SD interlaced format.
-
This isn’t a RED problem, it’s an NTSC issue and has been for many years on any box that rolls credits – as I said above: add space between your titles (effecively making the roll longer so it will run faster in the same time) and make sure the 1:2:1 filter is clicked on the in the title container render tab.
-
Try adding some space between lines to make the roll quicker and make sure the 1:2:1 deflicker is clicked on in the render tab of the title container.
-
I use my Io to feed analog to my K2 – works very well.
I had to send my scope to be repaired and when using the FCP scopes and the Io proc amp to set levels you have to flip back and forth. Not a huge issue, but FCP has those great controls in the capture tool that have never been enabled with the Io… -
It has yet to implemented on any other AJA product…
-
My understanding is that you will be able to select it as you would any other codec (DV25, DV50, Uncompressed) and it will encoded as it is captured through your Io.
-