Floh Peters
Forum Replies Created
-
At least I haven´t heard about this problem before. Did you want to export the XML for AfterEffects or for FinalCutPro? Did you try it again? Same result? And is there an error message like “The application has unexpectedly quit”? If yes, you should copy the info provided in this dialog and send it to Media 100 Support with the steps you did to get to this problem. If they know about a problem chances are good that it is going to be fixed.
-
Can you post a timeline file zipped somewhere, so that I can have a look at what is happening there?
As a workaround, you could export your whole timeline self-contained, reimport and conform then to SD… or maybe the new conform in Suite 2 will work better. Maybe you should give the trial version a chance.
-
I doubt that re-acquiring with center setting will change anything.
Basically you want to hear the 1st channel of Cam1? And you see levels on A1A2 in the audio mixer? What about B1 and B2? Do you see levels on any of the Busses? And what on C1/2? Is there a level display? I guess your routing is wrong somewhere. If you want to route your A1A2 signal to B2, you need to make sure that 1.) B2 is active (for example in the Track Setup window that you have 2 buses), and that the green dots in the audio mixer or the blue dots in the Track Setup window for A1 and A2 are set to B2. Then you have to make sure that B2 is routed to whatever out channel you are monitoring.
If you still have problems, or if you think that your setup is correct we could try a remote session with e.g. Teamviewer.com so that I can have a look at the problem.
-
I am not sure if there is a current documentation for the Multiclip editing workflow. But of course you can ask questions here.
-
You should delete your “Current Configuration” file in YourHomeFolder->Library->Preferences->Media 100 Suite Preferences. Most likely there is a setting that went wrong within this file. If you remember which configuration you used, you could try to delete the configuration file (located in the same folder) as well.
-
Another idea: you are not trying to export to an USB-Stick or a windows formatted drive? They still have a 2GB (or maybe 4GB) filesize limit on MacOS, as far as I know.
-
Maybe 720p60 was not supported in Suite 1.1.3; I am not sure about that. The current version does support this framerate. Maybe you can download the Suite 2 trial to see if your files do work with it. Or send me a small file (floh@mac.com), and I will have a look if it imports into Suite 2.
-
Are you really running Media 100 V7.1? Interesting. If this is the case, you could hit a 2GB filesize limit which was around in earlier OS versions. Or maybe your drive is formatted HFS and not HFS+, which also allows only 2GB. Try exporting short ranges, increase the length and look where it fails.
-
Media 100 documents (like many MacOS files) contains of 2 parts, a resource fork and a data fork. Windows and Linux systems usually store the data fork, so it could be quite likely that your cloud storage solution did not store the resource fork. Usually it is a good idea to zip files before sending them to the cloud. If the resource fork is gone there is not much you can do, as far as I know.
-
[Lukkee Chong] “Also it seems the “different standards” report is being caused by missing footage in the time line. Now this is another problem to solve!”
You won´t see the “different standards” message for video clips in Suite 2 anymore.