[Michael Hanish]

I’ve been using that driver with my Kona3 card, the latest version of M100, and Mountain Lion, no problems.
best,
Michael

[Michael Hanish]

Hey Andy,

This may sound confusing, and I hope I get this right. Since going to Mountain Lion, I have been using Content Browser to copy BPAV folders from cards to hard drives, and that seems to be working fine. But to actually import XDCAM footage, and I just double checked this in Media 1000 v 2.1.3, what is used, called by Media100 when you pick Import XDCAM from the file menu, and still works is XDCAM Transfer. Mine seems to be v 2.13. I rtemember a few bits of versions ago, making the assumption that the Content Browser would handle all that stuff (copying and import) but found that Media 100 didn’t reach for the new app but the older one, so I had to reinstall it.

So, it seems odd, but I think Media 100 support didn’t give a full answer or didn’t explain themselves well.

That said, I have taken to often using Premiere Pro as a front end for reviewing and doing some initial corrections to all footage I intend to import into M100, including XDCAM, rendering them all to ProRes, which is what I usually wind up editing in. Which is to say that there are other ways to do the XDCAM workflow.

Hope this helps,
all the best,
Michael

[Michael Hanish]

Glad it helped!!!
Send me an email at michael@freelunchmedia.com and let’s take this forward….

best,

Michael

[Michael Hanish]

It’s not a codec issue, nothing to copy. It’s a transcoding issue, export from Premiere as ProRes, or whatever you usually work with in M100. In other words, I don’t think you can play .mts (AVCHD) files in M100 with out changing them to something else.

hope this helps

[Michael Hanish]

Michael,

I’m sorry to say I have found exactly the same thing with 10.8.2. With the previous 10.8.1 it seemed to come and go (audio not encoded though the log says so). I haven’t had time to try this lately, but sometimes it used to work and encode video and audio both when the destination was a different drive from the source. It is indeed very frustrating and the developers of BitVice don’t seem to be in a position at the moment to do any sort of updates. There are hints that they may re-emerge sometime soon, and I hope so but there is no way of knowing. What I have been doing sometimes is to use BitVice for the video and another encoder to make the ac3, but mostly lately I just use Adobe Media Encoder, which has been pretty satisfactory.

Hope this helps,
best,
Michael

[Michael Hanish]

So, what is it that you are trying to do? Perhaps someone here can help.

I would guess that many of us around here have figured out various work-arounds to frustrating or non-functional workflow bits with Media100 over the years.

best,
Michael

[Michael Hanish]

I’ve had something similar for ages, but it only occurs in V1 and above tracks, and other than being a visual PITA, seems harmless, no corruption, no crashes. It is usually there in the same magnification after a restart. Zooming in makes it worse, zooming out, way out, makes it go away. It hasn’t changes with OS updates/upgrades, but has gotten progressively worse and more persistent. Scrubbing makes the result shown, the fake parts get slowly scrubbed away. Here’s the image:

[Michael Hanish]

Thanks Floh!!!

[Michael Hanish]

Gerry,

You need to use an earlier version of the Kona driver as specified in the release notes, I think 9.05 or 9.06, until a Media100 update allows use of newer Kona drivers. MAke sure you uninstall the Kona software using the Uninstaller, restart, then install the correct version.

Hope this helps,

[Michael Hanish]

Thanks Dave!