Currently Being ModeratedJan 12, 2013 12:03 PM (in response to dinky2)
In addition: I am not able to open ANY project I created. Since this is the most basic of all functionalities I can not imagine the product would be shipped with such a bug. It must be something stupid, but WHAT?????
Because I installed a Motion update today as well via Software Update I decided to reinstall, but that didn't help
As it is I cannot use it and it is €45,- thrown overboard.
Currently Being ModeratedJan 12, 2013 3:51 PM (in response to dinky2)
What MAC OSX are you running?
I would try uninstalling Motion and try downloading it again from the Apple Store. When you uninstall make sure all the components have been removed from your computer. Try doing a basic search through Spotlight and make sure all elements have been thrown in the trash. In the finder opt-click the go menu to reveal your library to also trash all the preferences related to Motion.
Currently Being ModeratedJan 13, 2013 1:24 AM (in response to nickwitz)
Thanks for your response. That is exactly what I did. I used an app (AppCleaner) which identifies all copmponents of an app, including all plists. So I removed Motion completely, downloaded it again from the Appstore and reinstalled. No luck.
Yesterday I created a tiny Motion project with only a single clip and a light and was able to open that again. Projects created earlier will not open, though, and cause the complete system to stall to the extent that even force quit is not possible anymore.
The console log shows a couple of messages that might give a clue:
Pretty strange, btw, that a single app is capable of neutralizing an operating system. I have always thought this was a Windows thingy, but not Apple.....
Currently Being ModeratedJan 13, 2013 4:15 AM (in response to dinky2)
Try not to do it from the menu. With a new projected created, press Cmd+1 to go to the File Browser. Navigate to where your file is on your drive or external drive. Select the file and click the import button in the File Browser or drag the Motion File directly to the layers tab.
Currently Being ModeratedJan 13, 2013 4:42 AM (in response to nickwitz)
OK, will try that.
In the meantime I have been testing a bit more and it looks like it is related to a moving light, I have added to the project. As soon as that is part of a project it most of the time (not always.....) causes Motion to use a huge amount of CPU during/after opening the project and the viewer only shows the 3D rings associated with the light. I can still do some things in Motion, though, like deleting the light. When I do that, the rest of the project now shows in the viewer and CPU returns to normal.
Currently Being ModeratedJan 13, 2013 4:48 AM (in response to dinky2)
I have tried your suggestion and that works. Hurrah !!
So at least I can use this as a work around, but there is something rotten, of course. I don't think this is the way it is supposed to work. If you come across a way to really solve this, it would be much appreciated. In the meantime thanks a lot for your help