I authored a mogrt in Premiere Pro v13.0.3 (build 9) on Windows 10 and published it to a shared CC Library. I opened up Rush on Win10 (1.0.3 build 19), dropped the mogrt onto a timeline and BOOM, it worked as expected. So far so good.
BUT... when I move over to an OSX machine (10.14) with Rush 1.0.4 (build 2) installed, that same mogrt template breaks. When I import the mogrt from the CC Library, the animation is there but does not respect the masks that were there when designed. Also, when I try to install the mogrt locally via disk, Rush throws an error saying the mogrt cannot be installed; the error message does not provide any other details.
Now get this, the same mogrt works in Premiere Pro on the same OSX machine.
Any ideas on how to get mogrt's to work in Rush across operating systems?
could you please tell me which MOGRT it was or share with me? Then I'll be happy to take a look if I can repro this issue
Just checking to see if you've had a chance to check out my problem with importing mogrt's into Rush on OSX. Since my initial post I've updated to the newest version of Pr on Windows 10 and OSX and am still having the same problem. One difference now is that when I try to import a mogrt into Rush on OSX, Rush simply crashes. I've tried this on multiple OSX boxes with a clean install of Rush.
Feel free to give me a shout if you need any more information.
Current Mac OS is 10.14.3 - not sure that makes a difference but to eliminate it can you update?
richs29581498, the mogrt was created with masks in the Effect Controls inside of Premiere Pro. This is currently not supported by Rush. The problem is that you can apply it in Rush at all. If you want to play with the mogrt in Premiere, you can delete the masks from the text layers in the Effect Controls and instead use Opacity and Position keyframes to animate in the text and export the mogrt again from within Premiere, but of course it is not quite as elegant as the mask solution. Sorry, you are going through that trouble. You should expect to see this supported in Rush in the near future.
It looks like the latest update to Rush (1.1) has resolved this problem. Woo hoo!
There you go! Thanks for adding this to the thread. Keep up the reporting of any difficulties!