Thanks for responding.
Unfortunately, this is not the case. Media 100 app runs off the internal startup disk where I have M100 progs and bins located in the Document Folder. Media files are acquired and transitions rendered on 2 internals Western Digital striped as an array volume.
The real big deals for me, as stated before, are, when both Render All or manually rendered clips, result in playing the first frame of Clip as “still/freeze” (CTI moving) for half a second, let’s say, and then showing the actual fast/slow motion. The Still frames are actually part of the Purple Clip which is a non sense. The other problem I have is when doing the same task, creating a fsst/slow FX on a clip, the rendered Clip shows a totally different TC (different content) of the same Source clip. There is no workarounds for the later, except going back to the source clip in the bin (sometimes re-import from the drives even) redo the FX then from the bin 4,5 even6 times before it works to finally replace the Purple Clip in the Program.
I thought at first I was affected by corruption of some kind, but after a clean reinstall of system and Apps I can’t figure out. Are all users experiencing these problems? Have you been able to replicate these issues at Media 100?
Curiously, exporting a program SELF CONTAINED with FX Preview Online gives same problems in the resulting quickTime file. BUT, as mentionned before, exporting a program from Export-Other-QuickTime Command in a M100 Codec, Animation or H.264 works fine for me.
2×2.8 GHz Quad Core Intel Xeon
6 Gb RAM
OSX 10.5.8
Medai100 Suite 1.0.1
QuickTime 7.6.2