[Floh Peters]

This can be done relatively easily, but not automatically. You can drag a clip onto another one while holding CTRL and Command to get the optons what to replace. You would want to replace audio media only.
The approach would be: double-click your clip on the timeline, Copy the Mark In TC, double click the new clip and paste mark in. Then Command-drag on the old clip on the timeline. Move to next clip…

[Floh Peters]

[Peter DeArmond] “Question: Does 1.6 also support AVCHD (the lower bit rate) as well as AVC-Intra? “

AVCHD is supported since Version 1.5 via ClipWrap; although only as a slow import (conversion into a supported codec). The difference is that AVCHD uses an interframe compression, creating groups of pictures sharing the same compression data, while AVC Intra is a intraframe compression, where each frame contains the whole image. Supporting interframe compressed material like HDV and AVCHD natively seems to be difficult inside the Media 100 software environment.

[Floh Peters]

Ah, and make sure that the drive your files are on is actually a mac drive. It somewhat sounds like you had a HD crash, and sometimes these data recovery companies put the files on a Windows drive which cannot be used (or at least should not) with Media 100.

[Floh Peters]

If there are not many folders on the new drive the search should be pretty fast there. One thing you could try is to manually import one of the files (e.g. by dragging it on the Media 100 app icon). Perhaps copying the file on your startup drive as a backup could be a good idea.
Does it import correctly then? Can you play it back in Media 100?

[Floh Peters]

I would try the relink first. IF the files are really okay and complete (containing all original data) they should relink even with different names. Media 100 looks for some ID it writes into the file headers, and in case the headers are okay it should relink.
Otherwise this could get a lot more difficult.

[Floh Peters]

You can do one of the 2 options. If you use the “Add” command you should not have to relink. And if you relink the correct folders will be added automatically. I´d try the relink, and it should not matter if the footage is from P2 or something else.

[Floh Peters]

[Susi Feinbein] “2. choose a codec of your choice in M100-codec-settings and export “self-contained””

Self-contained files can contain – like by reference files – mixed codecs, since they are pretty similar. While a by reference file refers back to the original media files, a self contained export copies (data-wise) the parts from the referring quicktimes into a single file, but without recompression. It keeps the original compression of your source files and copies the used parts into a new QuickTime file.
The only way to make sure your exported file contains only one codec is to do a Quicktime export, using a codec of your choice. Luckily this is pretty fast these days.

[Floh Peters]

This is the usual problems with mixed codecs in by reference files. You use one codec for acquire (e.g. ProRes or DV), and another one for rendering (e.g. Media 100), and you get these jumps in the by ref or self contained exports. This is a underlying QuickTime codec issue, there is nothing Media 100 can do about that. If you see this problem you should export to QuickTime into a codec and colorspace of your choice.

[Floh Peters]

This probably is related to a transcoding issue; when exporting a QuickTime you can select either full RGB0-255 range or video RGB16-235 range. Unfortunately you cannot do that for file imports, so all incoming files will be treated as if they have a 16-235 range. Since you are feeding in a 0-255 image you get too much contrast. This is for conversions only, though, so all files that do fast-import come in correctly.

[Floh Peters]

This sounds as if the media file is damaged. Maybe this one is the reason for your crashes…