[Job Ter burg]

This indicate that somewhere in your sequence, there is a small piece of DNxHD175, maybe a title or a render, even on a lower track. I’ve had this in the past, and found MC always exports to the highest codec in the sequence.

You can try and hunt down the DNxHD175 clip by opening the bin, choose Bin->Set Bin Display and choose “reference clips”. This will show all clips used in the sequence.

Or you can open the Media Tool, search for precomputes and delete (or hide) any media that is DNxHD175.

[Job Ter burg]

AutoSync window has an option that lets you set the range of audio tracks you want to include in the sync clip.

[Job Ter burg]

What happens if you just do a classic File->Import?

[Job Ter burg]

Hi Christoph, hope you’re doing well (we met when you were in Amsterdam, working on White Light, assuming you are that same Christoph).

The new version is going to be released today. It was announced at NAB in April. Even though we move up a full version, there are no new features for now, only a new licensing model. No need for existing users to upgrade for now. New features are expected in an update to v8 that is likely going to appear in the course of this quarter.

[Job Ter burg]

Check the pannings. If you are center panning a pair of tracks that is meant for stereo playback, levels will be summed.

[Job Ter burg]

Could it have been a sync clip rather than a subclip?

[Job Ter burg]

Wherever matchframe takes you, that’s where the sequence has been constructed from.

[Job Ter burg]

You misread my test. One of my three workflows does precisely that. Just link and export. i did perform the same est with an Alex file, but cannot share the results because I don’t own the rights to those clips.

Simply put: I cannot reproduce the issue you are describing.

[Job Ter burg]

Actually, the fact that it is a native codec implies that nothing would at any point need to be modified in any way. The v5 workflow you describe implies a fully QT-based export (with a re-transcode).

Also, you mention “Send to QT”, which is something very different than what I was talking about. If you use that “Send to” command, you are using some type of export preset.

When I wrote about “Same as Source”, I am not talking about selecting the same codec as your source is. I am talking about using File->Export, selecting Quicktime Movie, and clicking the “Same As Source” radio button.

I did a small test and I simply cannot see any difference between source and result, not in MC and not in QT Player afterwards. What I did was:
– create a 1080p24 RGB709 project in MC
– Do a Fast Import of a ProRes 4444 source file (Fast Import meaning that MC asks me to preserve the resolution of the source file when importing, and I acknowledge).
– Do an AMA-link to that same ProRes 4444 source file into the same project
– Consolidate a copy of that AMA-linked clip in MC (so consolidating into Avid MXF Media)

I edited each of these into a sequence of their own, then chose File->Export, Selected the Same As Source button, chose ‘601/709’ as the color space, and exported. I don’t see any difference at any point.
Here are the results as well as the originals: https://www.terburg.com/EVEN/140507b_APR4444_Test.zip

Further thinking also made me wonder if there can be interlaced/progressive issues at play, since you mention noticing quality issues on lines in a frame leader and text. Is your source file progressive or interlaced, and when you bring things into MC, is it a P or an I project, and what does it think the source is: P or I? Are you seeing any motion adapters?

[Job Ter burg]

In 5.x, ProRes was not a native codec, so it cannot have been the same workflow.