Michael Phillips
1
COW Coin
Forum Replies Created
-
There are not. ☹
Michael
-
I would try separate AAF for picture and sound. I have never had good luck with audio workflows and AAF between NLE’s other than the MC<->ProTools route which one would expect.
With the audio-only AAF. make sure to use relink to selected and chose TapeID or whatever column has the common metadata between the clips in the timeline from the AAF and the actual media that you are relinking to.
Michael
-
Yes, that is normal and has been this way since the original Avid/1 Media Composer released in December of 1989. It is only an icon representing the fact that it is an audio-only clip (and for historical trivia, the waveform is the word f**k) and has no bearing on the actual waveform presentation of the clip at that point in time. It has been a really long-time feature request to do more, even something like what is available in Source Settings, but no change yet. Switching the source/record is the workaround as you’ve discovered.
Michael
-
Ah – I thought that was the case back in September but my eyes skipped right over it this time reading it. Shouldn’t you be out ringing in the new year? Have a happy one!
Michael
-
This one?
https://www.avid.com/press-room/2019/09/avid-delivers-video-editing-workflowsIt refers to ProResRAW decode on Windows in Media Composer and DNxHD/HR decoders as part of Apple Pro Video package download.
Michael
-
Rather than using AutoSync to marry V and A tracks, use group clip. You’ll end up with a .grp clip but can edit with it the same way and if I remember correctly, you should be able to trim past the boundaries. The one downside is I don’t believe you will see frame offsets in the timeline if slipping out of sync, but that needs to be tested as well.
Michael
-
It is strange that in a non-film project that the .sync has this behavior. It would seem to me that it should be able to trim to the end of the track’s respective sub/master clip. Basically behave like a subclip in a non-film project. I can think of a few ways for this to work in the digital age allowing the user to define behavior.
Group clips “might” be a workaround for you.
Michael
-
You are correct, and it’s coming back to me… in a non-film project you can trim past the boundaries of a subclip but you cannot trim past the boundaries of the .sync clip. Avid would have to explain why in this scenario.
Michael
-
I’m aware of that, but what project type did you create? A film project still supported digital cameras, but the subclips are still hard subclips.
Michael
-
Are you in a film project (35mm or 16mm)? Those projects have “hard subclips” in order to protect metadata that may be different – although that was more of a Keykode protection issue with early film workflows and transfers and is less of an issue in non-film based workflows.
But the “hard subclip” concept still remains in a film project preventing a user from trimming past the boundary of its subclip start-end. If not a film project, it may be something else but I would have to test some scenarios to know for sure. I tend to work in film 35mm projects to have 1/4 frame sync capabilities with translation to Pro Tools when turning over sound.
Michael