12 was build 334, I found the newest version 64bit suite build. At the end it seemed to complete fully but got an error message Movie Studio stopped responding. I defined the loop section in both versions. The clip was a standard definition dv-avi clip. I places the same 2 minute video clip on the timeline of each program version. I also set video card acceleration in both programs for my video card. It's so much different to me from Adobe.Īnyway, I set both programs, 12 and 13 to use the same amount of memory, 5 gigs, since I have 16. Admittedly I'm still playing with everything. And you could render the project with 13-less plugins in 12 and continue then in 13. Of course you could try the update option inside the plugin to see if you'd get updated.īut you might be able to do most of what you want in MSP 12 instead of 13. So you probably aren't able to get rid of that if it happens. Versions prior to Movie Studio 13 being released would not recognize Movie Studio 13 and would give a watermark."
Regarding this, an NB rep wrote on the SCS forum at the time: " There was an updated build after Movie Studio 13 was released. You should read Dr Zen's tutorial on MB QL before you install and boot up MSP 12.Īnd there was also NewBlueFX 3D Titling and Video Effects. No serial number was needed for that if I recall correctly. In addition, there was Magic Bullet QuickLooks (32-bit and 64-bit versions) with the Suite.
MS Platinum 12 Suite had extras like Sound Forge Audio Studio 10, which is its own program and can be used of course with MSP 13. You may want to check with MAGIX Customer Support what you need to do. You know the procedure to see what's on MAGIX.
I don't know if a deactivation is enough with MAGIX if he registered it. Did your friend install and register it? Sony/SCS needed to be informed of the transfer of the license and they then gave the new user a new license.
0 kommentar(er)
