Wickham Strub
Forum Replies Created
-
While importing, checking the “Scale Out-of-Range RGB Values” checkbox should accomplish this.
-
I just tried it with v1.0.1 and the reel name came in as the default “CONTENTS”. I then changed it to something unique and it honored that as well. So…
Any more details you can offer on this one?
-
Doh! (smacks hand to forehead) I missed the fact that I MUST import audio first and THEN try to eject. Sorry about that. Completely mea cupla.
We can totally reproduce it. It’s likely related to changes we made to import more audio types from XDCAM and P2. It’s on the list, hopefully it will be an easy one.
-
So… methinks I’ve solved the mystery. The 2.1.5 beta is for the MXO, not the MXO2. That would explain why we didn’t know about it, ’cause it doesn’t apply to us.
-
Okay, I’m officially green-lighting the M100 v13.0.4 on OS 10.5.8 config.
Of course, you know… now that I’ve gone on record like this one of you will find some “major” problem with it 😉
-
Okay, try this…
Copy your file to another drive volume and then import it from there. Simply duplicating the file on the same drive isn’t enough.
Try that and let us know what happens.
~Wick
-
Strange,
I am having no trouble importing the file that you provided for us to to test with (the tracking shot outside the fort — 003805).
However, I DID see the problem you describe (mostly green screen with a small frame of the image in the corner) with an in-house build of M100 while we were working out the problem. Perhaps your install of M100 is in some sort of limbo between v1.0 and 1.0.1?
I’ll run another test and report back soon.
~Wick
-
Hmmm… with a MacBook you are almost certainly using external drives, most likely FireWire. Try eliminating those drives and do a test with the internal drive only.
I’m NOT suggesting this is the answer to your problems, but it may help us figure out where the break is happening.
-
Sorry for the delay on this. I expect to have a real answer tomorrow.
-
John,
What version of Media 100 are you running?