Floh Peters
Forum Replies Created
-
[Danielle DeLucia] “I’m also trying to use this fix to correct a bin visibility issue in Suite. I originally started a thread on Producer crashing on HD import and have now moved to the Suite trial to get some resolution on the issue. I’ve been watching this thread for some time, as it reminds me of my unsolvable HD import crash problem in Producer. Being unfamiliar with the technique for applying the above script for Suite; does anyone know if the entire line starting with “defaults..” goes in the Terminal window. I was told I had to quit out of Suite altogether before tying it in. Thanks.
“If you have the latest version (Suite 1.6.2) you don´t need to apply the fix anymore. It has been fixed in 1.6.1, so you should be okay.
-
Drives too slow or too full? Or maybe you have rendered parts into Uncompressed instead of e.g. ProRes, so your drives reach their performance limit? Easy way to see this is to select all in your timeline, do a right click and then choose “Get Clip info”. Look at the “Codec” area of the resulting Bin.
-
Can you post an example still here?
-
Hmmm, sounds like something still is not right. Here´s what you should try:
find one of the original media files that you have imported on your HD (e.g. Right-click on a clip in a Bin and use “show in Finder”).
Import that file into AE
In the AE project window, when you have the file selected you should see its native dimensions and pixel aspect ratio. These are the values you should use in AE; probably they should be 1280*720, with square pixels, which should match the 720p presets in AE.
Now render that out to a Media 100 supported codec, like ProRes or DVCProHD. If you import the rendered clip into Media 100, the file should “fast import”, meaning that only a short “update media” dialog should appear and not a “rendering video” during import of the clip.
After the import, your clip colors should be identical to your original clip; the resolution and sharpness also should be the same. -
[Sue Daly] “The only thing I’ve missed is where do I go to downland the upgrade? I’ve also had an email from M100 giving me the install code for the free 14 day trail but I’ve paid for the full upgrade.”
After you have installed the trial version as described in the last post, you need to send the authorization request code from the Media 100 startup message to Media 100. They will create a permanent unlock code based on your individual request code.
-
[Andy Taplin] “It’s a weird problem, is the XDCAM transfer software to blame most likely? I’m using version 2.11.0”
Absolutely not sure. You could try version 2.12 of the XDCam Transfer, and of course you could try the latest Media 100 trial version to see if one of these components fixes your issues. What is the exact error message of your crashes?? -
[Andy Taplin] “The clip icon is also different. So is this because the file is corrupted during the failed import or does M100 suddenly ‘see’ an NTSC clip and then crash?”
This usually is due to a corruption during import, and usually not the reason for the crash.
-
[Danielle DeLucia] “We tried creating a new bin and acquiring again, only with the same results. We end up with two bins in the project window, both spotted-looking (not like your active-type bin).”
Does that mean your newly created bin did not show up also? Then you most likely have a preference problem. Try to go to YourHomeFolder->Library->Preferences->Media 100 Suite folder and remove the “Current configuration”file while Media 100 is not running. This should reset your prefs. Then launch the app again and look if your new Bins show up. In case you need additional help with that there would be the option of a remote session if your system is connected to the web…
-
Not in the Sony world. They went to 2.9, then to 2.10 and so on. So 2.12 is 5 higher than 2.7 😉
-
Have you tried the latest XDCam transfer software? They are up to 2.12 now, I think.