Keith Koby
Forum Replies Created
-
yes.
I’ve heard that it may be fixed in 6.0.2. I haven’t tried it yet. If you set an in point any where in the timeline before the 1:00:00;00 mark, you’ll run into this. Set it after, and you’ll be fine. The bug affected all codecs.
kk
-
Sounded to me as if he was going to crop 16:9 to 4:3. He’ll still need an edge of video marker for 4:3. You can obviously make your own, but this tool looks handy.
-
We’ve been thinking about buying this…
https://www.digital-heaven.co.uk/fcplugins/dh_widesafe.php
kk
-
Or insert the Final Cut Studio 2 disc in the computer and install the codecs by running the Qmaster render node package. You don’t have to enter a serial and you don’t have to make the machine available as a render node.
kk
-
no purging scheduled.
There are multiple accounts, but the same editors on the same accounts have been giving me the “no audio” reports.
the night guys would be capturing embedded audio as well, so I don’t see why they would change it (plus they are logged on as different user accounts). The editors are smart, but sometimes can’t remember where that setting even is to change it to begin with, so I doubt that they are sabotaging themselves.
thanks for all of your input!
kk
-
Thanks Bob.
That’s what I’ve been doing. There are no aes input feeds and nothing pluged into the kona break out box, but for some reason, I keep getting calls down the hall that they have no audio when trying to capture. I get on remote desktop and set the input back to embedded…
I’m not sure why, but it seems to default back to AES. I doubt that the editors would be changing the setting themselves – they are smart and have no reason to mess with the setting since there are no aes in feeds to the edit suites. We are using the aes out for monitoring.
This is why I’m puzzled… I need to know if I need to create a preset in order for it to stick or somehting.
kk
-
cool! Glad I could help!
-
Thanks.
-
Don’t know much about windows land. Sounds like a ref problem or a routing/feedback problem.
-
We’ve been experieincing this problem since upgrading a month or so ago. I originally thought that it only affected media captured with 5.1.4 and imported into 6. I now doubt that, whereas, I believe we have now encountered the problem with media captured in 6.0.1.
I have also encountered a similar problem in nesting timelines. Option clicking a nest to play it back in the viewer has the same strobed playback problem as one of the exported-reimported files described above. Also has the same pixel aspect ratio and frame size errors.
Having said that, I’m thinking it has more to do with FCP than QT.
off topic: we’ve seen the following problem with nests as well as duplicate sequences. see below link. And we saw this problem between ppc and intel long before FCP 6. Could the above and below all be render file related issues?
https://docs.info.apple.com/article.html?artnum=306068