Crashing on import XDCAM (transfer)

[Andy Taplin]

I can’t remember the error message, next time it happens I’ll write down the info. In the meantime I’ll update XDCAM transfer.

Thanks, Andy

[Jay Ryscki]

THis was a known issue in suite 1.6 and there was a workaround that could be done to settings in the application parameters to avoid the error. You had to log in using Terminal to make the change. THe new version 1.6.1 had the fix installed.

From Media 100-

Engineering says: If he is running Suite 1.6, have him open a Terminal
window and enter this command:

defaults write “com.Media100.Media100 Suite.override”
UseImportMovieCache -integer 0

That should solve your issue.
Also, V 1.6.1 is being posted within the next 2 days and contains a fix for
this issue.

[Kris Mcmullin]

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.

[Floh Peters]

[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.