Shane Ross
Forum Replies Created
-
Good thought…and one that makes sense. FCP couldn’t do that either, nor Avid when it linked to masters. But I’m only linked to Proxies when it comes to the camera masters, and those aren’t GOP. But I am sure some of the camera masters are GOP formats…so good call. Those I might just have to supply ALL the camera masters for the online.
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
CLARIFY the number. is this 59.94i? Or 59.94p? 1080i59.94 is the standard naming convention for 1080i running at 29.97fps…and this can cause a LOT of confusion. So verify, are they talking 60fps…or 30fps?
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
[Peter Garaway] “1. Copying to full drive (nearly full drive)”
Empty 4TB hard drive.
[Peter Garaway] ” Spanned clips in the project”
Not linking to those. Proxies only, and stock footage. Tried many things, even MM only camera proxies…only stock footage…same error. Tried a 3 min section…same error. Tried ONE CLIP! Same error. NO, this is something else.
[Peter Garaway] “3. Enabling “Include Preview Files” “
Turned off that, and the other things it generates. Same issue
[Peter Garaway] “4. Copying to a long destination/file path and/or name”
Source path: EVO>Projects>ANL
Destination path: ANL ONLINE[Peter Garaway] “5. If the audio has been modified via Modify > Audio Channels”
Nope…no modifications.
So I’m going to have to manually move only what’s in the project..except that we have to move all of the camera masters. Total pain, but whatever…chalking it up to NLE quirkyness. Stuff like this happens all the time…works fine, then at one point, doesn’t.
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
Red means that the audio files are offline…missing. Are the NEW ones Red, or the old ones? Typically from ProTools one exports audio stems to bring into Avid…not AAF round trip
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
Should be able to. Not much different between those two versions that might prevent it. DUPLICATE the project first, just in case.
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
How about VLC? Other players. If it works there, then QTX is the problem.
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
[Richard Steele] “whether my FCP6 or 7 projects will run smoothly in 10…”
Well, you need to buy an app to convert the project from FCP 7 to FCX…it’s not convertable without that.
But there’s always Premiere Pro. Export XML of whole project from FCP 7, import that into Premiere…it all comes in. Whole Project…no outside app needed
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
[Ryan Dundas] “Could you be a little more specific about what you mean by output to another computer? Do you mean send the video signal from the avid timeline out of an AJA card via SDI to another computer with an AJA card then capture it like tape?”
Yes. I have two machines, one with an AJA card and one with BMD, and I output from one and capture in the other.
[Ryan Dundas] “We don’t have an AJA recorder but we have some Atomos Blade and Flame recorders that I believe will do the pulldown and record in 60i. I’ve never tried feeding them a signal from the NLE on my computer.”
That should work…worth testing before you commit.
[Ryan Dundas] “It’s already enough of a pain to time out the show in 29.97 drop frame when we are working in 23.98 non drop.”
Actually, this is easy. Just set your sequence timecode to display 30i. Then it’ll be timed just fine. I do this all the time.
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
Well, my suggestion is NOT tape, but something similar. Shoot and edit 23.98, but then output either to another computer or to an AJA KiPro Plus or similar as 29.97…60i. This will create a digital file, and add the proper pulldown, just like tape.
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
What hard drive is this footage stored on? The SSD?
H.264 MPEG-4…isn’t DNxHR. Those are two different codecs, so your sequence settings and clip settings don’t match. Not that it matters, just saying they are different. H.264 takes a bit to decode on the fly.
Perhaps the driver for the GPU is more up to date on the Windows side?
Shane
Little Frog Post
Read my blog, Little Frog in High Def