[Wickham Strub]

Hi Jaeson,

I’m sorry I can’t say for sure right now (I’m at home on my couch) but I seem to recall that QT 7.6 didn’t quite ‘fix’ our problems on Tiger-based systems.

There’s absolutely no harm in trying it. If it goes badly (pink frams in bins is likely the worst it will get) you can simply follow the recipe to back up to QT 7.5 found here.

[Wickham Strub]

Hi Fermin,

There’s an extremely slim chance that 13.0.2 will solve your problem because we did add some code to ensure that you’ve got the real ProRes codec installed and not just the decoder. However, it sounds like you may have something else going on as this is not a complaint we’ve heard.

I suggest you start a new thread titled something like “Problems importing Apple ProRes” along with details about your Mac hardware, OS, Installed codecs, I/O hardware and Media 100 version. Also let us know the source of your imported media and what codec you’re importing to.

~Wick

[Wickham Strub]

Olof,

Sorry about that. You’re right, the way I wrote that sentence can be read to mean that we can now use XDCAM codecs “natively”. Because that’s not what I meant, I just hadn’t read it in that way.

What I meant was: Media 100 can now properly handle more XDCAM sources than it did before. Specifically, there is a 1080p30 format that is really 29.97p that was confusing Media 100 and creating media that wouldn’t play back inside the application even though the resulting media will play just fine in QT Player and FCP.

[Wickham Strub]

Floh’s right (again).

There’s absolutely no harm in trying them all and comparing. You shouldn’t need to actually re-digitize in Avid to tell if something’s not the way you want it.

Having said that, I’d try CMX 3600 first. Only because that seemed to be the one I settled on over the years and was most familiar with if I needed to manually edit it.

[Wickham Strub]

Good suggestion Jason, but…

I remember that your Mac was a new (at the time) Mac Pro 8-Core and, yes, we found that those Macs needed to have the AJA cards in Slot 2 in order to play nice with everything else. So…

Jeremy, it can’t hurt to try, it’s either going to work or not.

If it’s still a no-go, try the following:

Running Media 100 via Apple’s Terminal Utility

• Locate the “Media 100” application in: Applications > Media 100 Folder
• Right+Click (or Control+Click) on the “Media 100” application and choose “Show Package Contents”
• Open the “Contents” folder
• Open the “MacOS” folder
• Double-click on the icon named “Media 100” (note: an alias of this icon can be placed on the desktop for easier access in the future)
• Media 100 will now launch from within the Terminal utility
• If / when a problem occurs, error information should appear in the Terminal window
• Copy the info from the Terminal window and paste it into a response to this email

[Wickham Strub]

OK…that makes a little more sense. I wasn’t sure how the problem you were complaining about jived with the config in the signature in your posts.

If you’re using Producer, I assume the config does NOT match that which is your signature.

What are the specs in this situation?

Computer:
OS version:
Producer version:
QT version:
Sony XDCAM Transfer version:

Also, what does Sony XDCAM Transfer say about the file (Information>Video) as compared to the FrameSize/FrameRate/Codec (put bin in list view) when it gets into Media 100?

~Wick

[Wickham Strub]

OK, I’m with you. That doesn’t sound right to me. I’ll see what I can find out when I’m back in the office (I’m out Monday the 16th).

In the mean time… you should try exporting busses as separate tracks. What’s the workflow? Where is this file going from here? Is it possible to run a short test to ensure that you’ll get what you need at the other end of the workflow?

~Wick

[Wickham Strub]

Hey Greg,

I just re-read your post after seeing Floh’s response. Are you saying that you get ONLY bus number 1 when you choose “Stereo Mix”?

If so, that’s different, and it’s news to me.

~Wick

[Wickham Strub]

Hi Tom,

The truth is that there are more than a few things that don’t work right when you choose “Other:” while exporting. It’s on our list of “things that would be nice to fix” (if we can), but it usually gets pushed back for new features or show-stopping bugs. Because of this, exporting a Self-Contained or By-Reference movie and then running THAT through QuickTime Pro is the most reliable way (for now) IF you want letterboxing in your exported file.

Having said that… if I understand what you’re doing correctly, I’m not so sure you really DO want the letterbox in your exported file.

If you’re working on an HD Program, which is 16×9, and you want to send a small, compressed version of it for the client to see on their computer, why not export a movie in a 16×9 aspect ratio so it just opens up in QuickTime player at the correct aspect ratio?

This has a few of advantages:

– You don’t need to involve another application.
– You only need to export once.
– You aren’t adding to the file size with black bars top and bottom.
– It looks cool when it opens up 16×9.

Using your mention of 352×288 as a guide, I just tried the following and thought it looked pretty good:

– Other: QuickTime Movie
– Click “Options”
– Set “Size…” to 480 x 270 (leave everything else alone)
– I set my compressor to H.264 and set the Key Frames to Every 300 frames (10 times the frame rate)

[Wickham Strub]

Weird, I couldn’t find the driver all day. Every time I went to their site it was still v6.0.2. And yes, I refreshed my browser AND checked it on another computer.

Anyway, we knew this one was coming and have had reason to believe that it should be harmless to us.

Now that it’s made it all the way across the internet to our computers, we’ll give it a spin tomorrow just to be sure and I’ll let everyone know in a fresh thread.