[Wickham Strub]

I recall that there were growing pains in regards to media drives when moving from OS 9 to OS X. Actually, I seem to remember odd behavior when only moving from 10.2 to 10.3. I don’t have any notes on this but I’m almost certain that my media drives (and those of several Tech Support customers) just wouldn’t play nice after updating to Panther (10.3) until the drives were re-formatted.

If you’re drives went from OS 9 (9.2.2 I assume) to OS X (10.4.11* at the absolute most) without a reformat, I’m amazed, AMAZED!… that they even mount on the desktop.

No promises here, but I’d say it’s definitely worth a try to back them up and reformat them.

*any OS above v10.4.3 was never officially tested with Media 100 i

[Wickham Strub]

Are you talking about DVD menus?

Chapter Marks and Compression Marks can be set in the Media 100 timeline. Those marks can be included as metadata in exports. The marks can then be used by DVD Studio Pro or iDVD to automatically create menus.

[Wickham Strub]

Hi Eric,

Since you’ve already expressed your commitment to Media 100, I suppose it won’t sound too self-promoting for me to say, “Give us a call.”

Our Sales guys walk customers through exactly these sort of decisions every day.

Call 800-832-8188 and ask for Matt.

~Wick

[Wickham Strub]

Hi Greg,

Take a look at the Mac-compatible choices on this chart.
https://en.wikipedia.org/wiki/Comparison_of_remote_desktop_software

I can personally comment on “GoToMyPC” and “Chicken of the VNC”. COTVNC requires some sort of “server” running on the system that’s being accessed remotely. I’ve used “Vine Server”.

Both of the one’s I’ve used will get you what you’re looking for but video playback is VERY sluggish and choppy.

~Wick

[Wickham Strub]

We haven’t seen any of the problems you’re describing related to OS 10.5.5 but I must admit we are full into v13 testing right now.

As this QT 7.5.5 thing has been playing out, I’ve talked to a few users for whom the “fix” got botched somehow and they had to try again. “Get Info” on your QT Player app to ensure that it is, indeed, reporting as v7.5. If it still says v7.5.5, the something didn’t take right when you tried to back up. If that’s the case, take a look at my recent post below for the most complete set of steps and links to date.

~Wick

[Wickham Strub]

Max,

Since we have no record of a sale to you in our database, I can only assume that the delivery you are awaiting is from an eBay purchase (or something similar). That’s fine with us… I just want to point you in the right direction to avoid a lot of unnecessary static on the forum.

First things first… if you’re getting v8.2.x, you should also be getting an 8.2.x system key, a 20 digit number that unlocks the software for the particular piece of hardware. If you don’t have that magic number, then all you really bought was the hardware.

IF you’ve got a number that works with v8.2.1, then that number will also work with v8.2.3a, and THAT is the version you should be using.
You can download it here: https://www.media100.com/support/downloads.php
Just click on the “Media 100 i” link a the bottom of the page.

You should also run on Mac OS Tiger. We only tested M100i as far as OS 10.4.4, but anecdotal evidence suggests it’s OK up to 10.4.11 if you hold back on QT. Which brings us to the next item…

QuickTime. I wouldn’t recommend going any farther than QT v7.3.x.
Apple has a QT v7.3.1 for Tiger installer here: https://www.apple.com/support/downloads/quicktime731fortiger.html

Stick to these guidelines and you SHOULD be alright.

~Wick

[Wickham Strub]

“…a lot has changed between 2003 and now.”
Floh, as you know, that may be the understatement of the century.

J, please, Please, PLEASE call 800-922-3220, press “1” for Sales and ask to speak to Matt. If you end up in voice-mail (because we’re busy) PLEASE leave a message with your name and number so he can call you back. He can explain what your options are. I believe you will find them to be MUCH more affordable than they were 4 years ago.

Regards,
Wickham H. Strub
Product Manager for Edit Systems
Boris FX – Media 100

[Wickham Strub]

No, sorry. M100 doesn’t currently do any frame rate conversion.

I seem to recall hearing that the latest version of Compressor does a fair job of this, but I haven’t tryed it myself.

[Wickham Strub]

I’m pretty sure this is because, for some strange reason, “DVCPROHD720p60” is the actual name of the codec. The name of the codec, of course, has nothing to do with the frame rate of the clip(s).

You can double-check my theory a couple of ways…

1 – Open any movie file in QT Pro and start to export it. In the “Movie to Quicktime Movie” choices, see if the codec shows up with “60” at the end of it.

2 – Dig into the CONTENTS folder on your P2 volume and find the folder called “Clip” or “Clips”. In there will be a bunch of .xml files. One of them should have the same name as the clip you’re having trouble with. Open it in TextEdit and look for the frame rate. I suspect you will find that it reports the file(s) as the same frame rate that’s coming up in M100.

[Wickham Strub]

I’m going to be BRUTALLY honest with you. Don’t take this wrong way. I’m NOT trying to say, “We don’t care about Media 100 i.” I’m just trying to explain why we no longer have all the answers about Media 100 i.

Media 100 i is ancient history for us. The only reason we still support it in the least is because we have customers with current systems that still use it. Also, Media 100 i users, like yourself, represent a potential market for our new systems. So…for those reasons, we do our best to help, but we don’t knock ourselves out ’cause we’re far more worried about making the new stuff better.

Now the answer to your question. I’m not sure that you CAN keep that erroneous error (dept. of redundancy dept?) from popping up.

The best thing you can do is ensure you’re running v8.2.3a. That is not just the latest version of Media 100 i, it’s the LAST version of Media 100 i. So if the error still pops up there, then we didn’t take it out, and it’ll keep popping up as long as the app runs out of memory. Which leads us the the real question here…

Why is the application running out of memory? Is there a specific task you’re performing when this error pops up? How much memory DO you have installed in the machine?

~Wick