MEDIA 100 Suite2.1 Won’t Open

[Floh Peters]

That´s a strange error message. I would suggest re-installing Media 100, in case you haven’t tried that. This should be pretty painless, so at least it is worth a try.

[Rich Johnson]

Floh,
Thanks for responding so quickly as always. Yes, I tried reinstalling several times. Each removing more and more files including invisible ones. I did the same with RED5 and other 3rd party plugs as well as uninstalled everything after the crash occurred but QTpro, the pro codecs apps and iTunes

It’s really got to be there. Seems every issue stems from QT or FONTS in Media100.
My next step is try installing QTpro 7.6.6 again although I cant recall the safest way to do this. I used a 3rd party App a few years back… or since QTX is the system app can I just delete Pro? I found nothing useful on the Apple site.
The only puzzling issue is it only effects Media100 (which explains my nearly half-dozen un-reinstall attempts)

FCPX works fine along with all the Adobe products.
Thanks

Thanks,

OnePlace Media, llc
Suite 2.1-LHe
OS10.6.8/7.2

[Floh Peters]

Can you post a screenshot of the error message? I am not sure which part of the system produces it, maybe the dialog box will tell me something.

[Rich Johnson]

Here’s the top portion and the very bottom listing CRASH– but doesn’t make any sense to me.
Let me know if you need the entire thing. Thankfully this is on my laptop and not on a main system. So please don’t rush or put yourself out. I really appreciate the help!
Thanks for the help.

Process: Media 100 Suite [3025]
Path: /Applications/Media 100 Folder/Media 100 Suite.app/Contents/MacOS/Media 100 Suite
Identifier: com.Media100.Media100Suite
Version: 2.1 (2.1)
Code Type: X86 (Native)
Parent Process: launchd [266]

Date/Time: 2012-02-29 00:02:12.989 -0500
OS Version: Mac OS X 10.7.3 (11D50)
Report Version: 9

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000

Application Specific Information:
objc[3025]: garbage collection is OFF
terminate called throwing an exception
abort() called

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x901069c6 __pthread_kill + 10
1 libsystem_c.dylib 0x973c7f78 pthread_kill + 106
2 libsystem_c.dylib 0x973b8bdd abort + 167
3 libc++abi.dylib 0x975c1921 abort_message + 94
4 libc++abi.dylib 0x975bf1bc default_terminate() + 36
5 libc++abi.dylib 0x975bf1fe safe_handler_caller(void (*)()) + 15
6 libc++abi.dylib 0x975bf1ef __cxxabiv1::__terminate(void (*)()) + 14
7 libc++abi.dylib 0x975bf562 __cxa_call_terminate + 58
8 libc++abi.dylib 0x975bf9da __gxx_personality_v0 + 158
9 libunwind.dylib 0x9c6c87b5 unwind_phase2 + 243
10 libunwind.dylib 0x9c6ce558 _Unwind_Resume + 74
11 com.Media100.Media100Suite 0x00337c5c TPrefsDlg::~TPrefsDlg() + 52
12 com.Media100.Media100Suite 0x003326a1 AppPrefsDialog(short, unsigned char) + 432
13 com.Media100.Media100Suite 0x0005b6f7 InitAppPrefsMenu() + 26
14 com.Media100.Media100Suite 0x000575a7 Dan::IDan() + 2235
15 com.Media100.Media100Suite 0x0004b309 main + 489
16 com.Media100.Media100Suite 0x00045ca1 start + 53
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x975c2330 ecx: 0xbfffed6c edx: 0x901069c6
edi: 0xacb942c0 esi: 0x00000006 ebp: 0xbfffed88 esp: 0xbfffed6c
ss: 0x00000023 efl: 0x00000246 eip: 0x901069c6 cs: 0x0000000b
ds: 0x00000023 es: 0x00000023 fs: 0x00000000 gs: 0x0000000f
cr2: 0x02dec000
Logical CPU: 0

Thanks,

OnePlace Media, llc
Suite 2.1-LHe
OS10.6.8/7.2

[Jaeson Koszarsky]

When did this start happening?

Was Media100 working ok with OSX10.7.3 previously? I’ve only gone as far as 10.7.2.

Are you able to use time machine to go back to a known period of Media100 functionality?

Jaeson

[Rich Johnson]

To make a long and exhausting story short and not go over the allowed character count for this message-
I went as far as I could along with a dozen of the finest techs and mac savvy-types from around the globe at apple, Boris and beyond who had it their personal mission to solve, only to agree later to fdisk it when they ran out of options…

It turned out to be the first place you look and thought I’d covered but the issue ws not in Media 100- or QT rather an invisible corrupt pref in BORIS RED that would not uninstall or be deleted easily that was linked linked to Media100 suite and an old Futura Bold font! Which also give me intermittent freezing issues when hitting the check mark to return back to the Media100 timeline.

So I don’t know how or what had happened but for now the problem is gone. Media Suite 2.1 loads and I’m creating titles again without with freezes. And Futura bold no where to be found on my drive or any of other of my 5 macs. I wonder if this message will put more Futura’s in the trash? futura STD seems to be ok for those who are wondering.
-10.7.3

Thanks,

OnePlace Media, llc
Suite 2.1-LHe
OS10.6.8/7.2

[Jaeson Koszarsky]

I had inexplicable font problems when using 10.6.7. It wasn’t limited to Media100/RED though, all apps were affected. When we upgraded to 10.7.2, the problem resolved itself and all fonts (at least those uses so far) are available & working again.

I have noticed that the new QuickTime player (10.1) isn’t as solid as the old QuickTimePro 7.6.6. Some MOVs playback with random glitches in 10 than never appear when using Pro7. I wonder if that explains some random glitches I continue to see in M100 title track renders.

Jaeson

[Floh Peters]

[Jaeson Koszarsky] “I have noticed that the new QuickTime player (10.1) isn’t as solid as the old QuickTimePro 7.6.6. Some MOVs playback with random glitches in 10 than never appear when using Pro7. I wonder if that explains some random glitches I continue to see in M100 title track renders. “

No, definitely not. The reason for having a QuickTime X and QuickTime 7 player is that there are 2 different foundations on which there are built on. The “old” QuickTime foundation used in QuickTime 7 player, Media 100, Final Cut Pro 7 and other applications, and the new “AV Foundation”, which is more or less the base for iOS media playback, which got ported back into MacOS X, which is very capable in terms of “new” formats like H.264 and others, but does not support all the legacy things the old QuickTime foundation does provide (e.g. playback of a wide range of QuickTime codec files, export,…). QuickTime X falls back to the old QuickTime foundation if it needs to access these kind of features (codecs) or simply does not allow some tasks the old QuickTime Player (Pro) did provide

[Jaeson Koszarsky]

The MOVs that I see playback glitching in QT10 are using H264 codec. The same MOV plays cleanly in QTPro7. These are MOVs exported from M100 Suite 2.1.

Here’s an example from this morning. The top image is QT10, the bottom is QTPro7. Both players using the same H264 MOV file. QTPro7 does not exhibit the playback glitches that I frequently see with QT10 playback.

Jaeson