[Jaeson Koszarsky]

Are you trying to open the back-up files stored on back-up drives?
Since drives are different, you should check/change your media destinations & locations. Relink might not be finding all the files needed.

If your 2nd Media100/G4 has a different version of Mac OS & QuickTime player installed, some video files may not be playable. At various times, a QuickTime upgrade would break something and require either another patched upgrade or a downgrade to a previous compatible version.

If your 2nd Media100/G4 has a different version of Media100 installed then you could run into some problems.

On occasion, certain Media100 crash problems could be resolved by deleting the preference files on the system drive. Save a copy of any files before deleting just in case you delete the wrong one.

When rebuilding a Media100/G4 system, note how the cards were installed in the original working system. If you re-order the card placement, you can run into problems. The documentation for your version of the Media100 boards should indicate a best slot placement.

[Jaeson Koszarsky]

I encounter this problem with Media100 & RED on a daily basis.

It doesn’t actually lock up the Media100 system. It just prevents you from switching windows within the Media100 environment.

You can still trudge along and complete whatever you’ve been working, save it, etc. if you tap dance between your Media100 windows and the desktop. You can even quit and work on other Media100 projects.

If you want to select a certain Media100 window, click on the desktop first and then the window that you want, timeline for example. Then if you want to go from the timeline window to the bin, first click the desktop and then the bin.

This workaround doesn’t make the bug state go away but permits you to continue working. Some shortcuts don’t work in this state but you can still work. To remove the bug state, you will need a force-quit.

The bug state seems to be tied to the switching of tasks between the Media100 app and the RED app, handing things off from one to the other. By switching the active app from Media100 to Finder & back, you can jump from one Media100 window to the next. If you stay within the Media100 app, you can’t traverse windows.

[Jaeson Koszarsky]

Will Media100 import the AVI if you change the IMPORT TYPE file filter to ALL?

You could try FLV crunch if you want to convert files outside of M100.
https://download.cnet.com/Flv-Crunch/3000-2194_4-10909295.html

We use Sorenson Squeeze but it’s a little more expensive.

Jaeson

[Jaeson Koszarsky]

I’m using 2.1.3 with 10.4.4 and OSX 10.7.5 MacPro 12-core. Seems to be working fine here, at least as fine as the last version was. I still get hang-ups exiting RED back to M100.

I hope I don’t jinx things by mentioning that the annoying random-garbage renders seem to have gone away.

I could use more speed from M100/RED. The activity monitor reports low CPU usage during rendering. Maybe it needs to be 64bit?

Jaeson

[Jaeson Koszarsky]

If you turn on motion-blur, you’ll watch the system come to a crawl if it’s set to a high quality level.

Jaeson

[Jaeson Koszarsky]

Forgot to mention… when you are in the Media100/RED bug state, you can tap-dance between windows but some of the keyboard shortcuts don’t work correctly. If I’m in the program timeline, I use the player controls in that window.

Jaeson

[Jaeson Koszarsky]

I installed the latest Media100 update and this bug persists. It happens to me on a daily basis. In fact, I’m working on a project right now in that Media100/RED bug state.

The work-around that I use is a tap-dance between the desktop and Media100 windows. If your program window is active and you want to select the bin, click on the desktop first and then the bin. To go from the bin to another window, click the desktop first, then the window you want.

I’ll do this dance for a while if I’m close to finishing a project. Eventually, a force-quit is required. Tap-dance through your windows and make sure everything is saved before force-quitting.

Jaeson

[Jaeson Koszarsky]

I don’t know if this is what’s happening in your situation, but I’ve gotten stuck with OpenOffice several times after launching the app and needed to delete the “saved state” information before I could use it again.

In this case, I need to hold OPTION key, go to the GO menu, and select LIBRARY. Then look for the SAVED APPLICATION STATE folder. In there would be a file like org.openoffice.script.savedState that needs deleted.

I’ve not had this ever happen with Media100. But if I did, it would be something I’d try.

Jaeson

[Jaeson Koszarsky]

Thanks again Floh. The 10.4.4 drivers worked.

[Jaeson Koszarsky]

What version of AJA driver is needed for Suite 2.1.3? I didn’t read anything in the release notes that mentions needing to update. So I installed 2.1.3, it went ok. Launched Media100 and was greeted with:

“Could not start the application because an incompatibility with the AJA hardware driver was detected.”

For AJA, I’m currently using 10.3.2 with KONA LHi. I see v10.4.4 on the AJA website. Is that supported by Suite2.1.3?

Jaeson