I am thinking about upgrading to MediaStudio Pro 8 from VideoStudio 9. Can anyone tell me is this is a wise move and how much different the two programs are?
Also, if I decide to upgrade, I will order the boxed version. How can I find the entire list of fixes, plugins, etc. that I need to download for MediaStudio Pro 8 to be fully updated?
Also, I noticed alot of people having trouble with the Smart Compositor. Have the problems been fixed with this software or should I wait to load later? I really don't want to have to wipe out my system if the Smart Compositor messes up my system.
Any advice or suggestions would be appreciated.
Susan
Upgrade from VideoStudio 9 to MediaStudio Pro 8
Hi, Susan...
I had this debate with myself a couple of years ago - but from VS7 to MSP7. I've never regretted spending the money (about $500 of my Canadian dollars at the time) and moving up to the "pro" version as I was just running into too many limitations with VideoStudio.
I also found that all of my VS7 project files were able to be imported into MSP7. Since then, I've upgraded to MSP8, and was able to import/update my MSP files to the newest version with very few problems. There have been a few minor glitches with MSP8, but I've found it quite stable on my editing system (Athlon 2400+, 768 megs RAM, ATI All-In-Wonder, Win XP Pro, and lots of (but never enough) disk space). There's also a solution for the Smart Compositor issue so that shouldn't be a concern for you.
Of course your mileage may vary, but I'd start by looking at the feature list, or possibly downloading the trial of MSP to have a look at it. Once you're comfortable with the new interface, you'll likely never look back...
Regards, Al
I had this debate with myself a couple of years ago - but from VS7 to MSP7. I've never regretted spending the money (about $500 of my Canadian dollars at the time) and moving up to the "pro" version as I was just running into too many limitations with VideoStudio.
I also found that all of my VS7 project files were able to be imported into MSP7. Since then, I've upgraded to MSP8, and was able to import/update my MSP files to the newest version with very few problems. There have been a few minor glitches with MSP8, but I've found it quite stable on my editing system (Athlon 2400+, 768 megs RAM, ATI All-In-Wonder, Win XP Pro, and lots of (but never enough) disk space). There's also a solution for the Smart Compositor issue so that shouldn't be a concern for you.
Of course your mileage may vary, but I'd start by looking at the feature list, or possibly downloading the trial of MSP to have a look at it. Once you're comfortable with the new interface, you'll likely never look back...
Regards, Al
Thanks Al for your comments. I believe I will go for it. I would like my video editing to look more professional and I do hope MSP8 will do that for me.
I noticed there were some fixes for MSP8 on the Ulead website. If I buy the boxed version, do you think those upgrades and fixes are already included on the disk?
I noticed there were some fixes for MSP8 on the Ulead website. If I buy the boxed version, do you think those upgrades and fixes are already included on the disk?
-
jday
I doubt (but could be wrong) that the new fixes listed on the web site would be included in the box version you purchase. Actually, only one of the update files is a "fix"--the labeled "Hot Fix". The other files actually add new features. For example, if you have the MPEG4 plug-in for MSP8 there is a new update that will work allow your MPEG4 files to be used on an iPOD.
Another new update is the Smart Compositor Designer. Again, not a fix, but a new feature. There is a problem with these update files (and the Smart Compositor Designer) on TBYB download versions of MSP8, but not with the box version of the download version that requires a serial number. Ulead is aware of this issue and I read on another forum that they will be releasing a new TBYB version that will work with the fixes. So, (especially since you are buying the box version) I'd definitely recommend the upgrade to MSP8. I did it about a year ago and haven't regretted it a bit.
Another new update is the Smart Compositor Designer. Again, not a fix, but a new feature. There is a problem with these update files (and the Smart Compositor Designer) on TBYB download versions of MSP8, but not with the box version of the download version that requires a serial number. Ulead is aware of this issue and I read on another forum that they will be releasing a new TBYB version that will work with the fixes. So, (especially since you are buying the box version) I'd definitely recommend the upgrade to MSP8. I did it about a year ago and haven't regretted it a bit.
I tried upgrading and MSPro 8 looks great, I want to use it. But there is one flaw that ruins this program for me.
Once you fill up the production library with too much stuff if the program has to restart it could take anywhere from 5minutes - 3 hours to load. So if you plan on putting movies or tv episodes in it and use the split by scene function (which would give about 700 separate scenes...you can do it once or twice and wait 5 minutes for the program to load, whenever you restart) but any more than that and you're looking at a 2 hour wait.
VS9 does not load your libraries at startup which is a really nice feature I wish MSPRO 8 would implement. especially since it takes about 30 minutes to scan and split your videos.
If you don't plan to put a lot of videos in your libraries (or use the split by scene function) then you're probably good to go with upgrading. It's a nice program.
I've even tried different video formats. AVI, MPEG it didn't make a difference both slowed down the program startup.
My computer specs are 2800 AMD Althlon processor, 1 gig of memory, and XP operating system.
Once you fill up the production library with too much stuff if the program has to restart it could take anywhere from 5minutes - 3 hours to load. So if you plan on putting movies or tv episodes in it and use the split by scene function (which would give about 700 separate scenes...you can do it once or twice and wait 5 minutes for the program to load, whenever you restart) but any more than that and you're looking at a 2 hour wait.
VS9 does not load your libraries at startup which is a really nice feature I wish MSPRO 8 would implement. especially since it takes about 30 minutes to scan and split your videos.
If you don't plan to put a lot of videos in your libraries (or use the split by scene function) then you're probably good to go with upgrading. It's a nice program.
I've even tried different video formats. AVI, MPEG it didn't make a difference both slowed down the program startup.
My computer specs are 2800 AMD Althlon processor, 1 gig of memory, and XP operating system.
AMD Athlon 8600+ 64 Processor
Memory: 1.81 GHz, 1GB of RAM
Operating system: XP Professional Service pack 2
Virtual Memory: Total paging file size for all drives 1535MB
Memory: 1.81 GHz, 1GB of RAM
Operating system: XP Professional Service pack 2
Virtual Memory: Total paging file size for all drives 1535MB
I'm sorry, but the Production Library is meant just for that, i.e., for storing things that you use regularly in all your projects or, at least, repeatedly. Things you wish to use in an individual project should go into the Project Tray, which is coupled to an individual dvp file and thus they do not affect start-up time for MSP, only the project, which has no data from other projects.
Of course, each of us has our own working method and I rarely use the PT, preferring to import directly from the working directory into the timelines. I find this more satisfactory as it eliminates the need for relinking, but this is very personal.
Of course, each of us has our own working method and I rarely use the PT, preferring to import directly from the working directory into the timelines. I find this more satisfactory as it eliminates the need for relinking, but this is very personal.
[b][i][color=red]Devil[/color][/i][/b]
[size=84]P4 Core 2 Duo 2.6 GHz/Elite NVidia NF650iSLIT-A/2 Gb dual channel FSB 1333 MHz/Gainward NVidia 7300/2 x 80 Gb, 1 x 300 Gb, 1 x 200 Gb/DVCAM DRV-1000P drive/ Pan NV-DX1&-DX100/MSP8/WS2/PI11/C3D etc.[/size]
[size=84]P4 Core 2 Duo 2.6 GHz/Elite NVidia NF650iSLIT-A/2 Gb dual channel FSB 1333 MHz/Gainward NVidia 7300/2 x 80 Gb, 1 x 300 Gb, 1 x 200 Gb/DVCAM DRV-1000P drive/ Pan NV-DX1&-DX100/MSP8/WS2/PI11/C3D etc.[/size]
I don't like redoing the same thing twice and if you plan to make more than one video with the same series it helps save time if you don't have to scan and split by scene your episodes every time you want to vid and most tv shows have 22 episodes a season. With UVS9 you can have up to 35-40 libraries to store your information and those libraries can hold a lot of information. you'd think the more advanced program could handle the same work load. That's my main complaint. They need a long term library for stuff people want to use for every project because not everyone is going to use their library the way you're using it, or the way I'm using it. They should have been prepared for all possible uses.
I still think loading the Production library on start up isn't a good idea. I mean sure people start off with a few files here, a few there, but two or three years later these things will add up and not everyone deletes or will use the Project Tray to store their information. And I'm sure I'm not the only one making videos using the multilpe sources files and the split by scene function.
It makes MSPRO8 look kind of bad if it can't handle loading library files without crashing the program. (which is basically what happens and what most people will assume when the screen goes white for more than 10 minutes)
I still think loading the Production library on start up isn't a good idea. I mean sure people start off with a few files here, a few there, but two or three years later these things will add up and not everyone deletes or will use the Project Tray to store their information. And I'm sure I'm not the only one making videos using the multilpe sources files and the split by scene function.
It makes MSPRO8 look kind of bad if it can't handle loading library files without crashing the program. (which is basically what happens and what most people will assume when the screen goes white for more than 10 minutes)
AMD Athlon 8600+ 64 Processor
Memory: 1.81 GHz, 1GB of RAM
Operating system: XP Professional Service pack 2
Virtual Memory: Total paging file size for all drives 1535MB
Memory: 1.81 GHz, 1GB of RAM
Operating system: XP Professional Service pack 2
Virtual Memory: Total paging file size for all drives 1535MB
I'm sorry, but you haven't appeared to catch on to what I'm trying to say. You are using MSP in a way that was never intended. Here is what I suggest you try:
After splitting by scene one long clip, use Smart-trimmed Package to place the many resultant scene clips into a specific directory (one per project).
When starting a new project, if you wish to use the library method, all you then have to do is import the partial or full directory contents of the clips you may wish to use into your Project Tray (under different tray names, if you prefer).
That way, you don't overload your Production Library with hundreds of clips, your MSP loads rapidly, you have ONLY what you need specific to each project and you will find your work will proceed much faster.
FYI, I've added only two short clips to my Production Library over the years, a PAL and a NTSC intro/logo/copyright notice. I don't need any more. And yes, I do use split by scene.
After splitting by scene one long clip, use Smart-trimmed Package to place the many resultant scene clips into a specific directory (one per project).
When starting a new project, if you wish to use the library method, all you then have to do is import the partial or full directory contents of the clips you may wish to use into your Project Tray (under different tray names, if you prefer).
That way, you don't overload your Production Library with hundreds of clips, your MSP loads rapidly, you have ONLY what you need specific to each project and you will find your work will proceed much faster.
FYI, I've added only two short clips to my Production Library over the years, a PAL and a NTSC intro/logo/copyright notice. I don't need any more. And yes, I do use split by scene.
[b][i][color=red]Devil[/color][/i][/b]
[size=84]P4 Core 2 Duo 2.6 GHz/Elite NVidia NF650iSLIT-A/2 Gb dual channel FSB 1333 MHz/Gainward NVidia 7300/2 x 80 Gb, 1 x 300 Gb, 1 x 200 Gb/DVCAM DRV-1000P drive/ Pan NV-DX1&-DX100/MSP8/WS2/PI11/C3D etc.[/size]
[size=84]P4 Core 2 Duo 2.6 GHz/Elite NVidia NF650iSLIT-A/2 Gb dual channel FSB 1333 MHz/Gainward NVidia 7300/2 x 80 Gb, 1 x 300 Gb, 1 x 200 Gb/DVCAM DRV-1000P drive/ Pan NV-DX1&-DX100/MSP8/WS2/PI11/C3D etc.[/size]
I haven't done much with the smart trim package...I'll give what you suggest a try see how it works. I just like being able to browse through scenes to pick what I want, but I did come up with another solution to this problem.
use the mult-trim function and select the scenes I want manually from the episode. It's more time consuming but once you have your clips...you can save them to a library or a project. And if you need more clips it's not hard to go back to the original file and grab more. I figured as long as I don't get more than 6000 scenes I'm good to go because I don't mind waiting 5-10 minutes if necessary.
use the mult-trim function and select the scenes I want manually from the episode. It's more time consuming but once you have your clips...you can save them to a library or a project. And if you need more clips it's not hard to go back to the original file and grab more. I figured as long as I don't get more than 6000 scenes I'm good to go because I don't mind waiting 5-10 minutes if necessary.
AMD Athlon 8600+ 64 Processor
Memory: 1.81 GHz, 1GB of RAM
Operating system: XP Professional Service pack 2
Virtual Memory: Total paging file size for all drives 1535MB
Memory: 1.81 GHz, 1GB of RAM
Operating system: XP Professional Service pack 2
Virtual Memory: Total paging file size for all drives 1535MB
