28 replies to this topic

[outerbank]

Got my computer back today.  VideoWave is fixed.  Opened a previously created project.  The project opened after only 3 minutes.  Whereas previously, it took about 1 hour to open.  According to the tech there was a bug within the VideoWave program.  He explained what was wrong, but quite honestly what he described was beyond my comprehension.  I'll try to question him again about the problem.  He was quite busy today.  

There was absolutely nothing wrong with the computer, its hardware, settings nor anything else.  Nor was it related to not upgrading to Microsoft SP3, which my computer still does not have.  He's unwilling to perform the upgrade.  Norton Internet Security was also not the culprit.  There was no malware found.

Thanks to all that tried to help.  It was appreciated very much.

[myguggi]

outerbank, on 03 February 2011 - 01:30 PM, said:

Got my computer back today.  VideoWave is fixed.  Opened a previously created project.  The project opened after only 3 minutes.  Whereas previously, it took about 1 hour to open.  According to the tech there was a bug within the VideoWave program.  He explained what was wrong, but quite honestly what he described was beyond my comprehension.  I'll try to question him again about the problem.  He was quite busy today.  

There was absolutely nothing wrong with the computer, its hardware, settings nor anything else.  Nor was it related to not upgrading to Microsoft SP3, which my computer still does not have.  He's unwilling to perform the upgrade.  Norton Internet Security was also not the culprit.  There was no malware found.

Thanks to all that tried to help.  It was appreciated very much.

THree minutes is still along time for a project to open.
I doubt very much that a bug in Videowave was the cause of the problem. If there was one, everybody else would have had that problem. Try to find out what he thinks the "bug" was and what he did to solve the problem.

Edited by myguggi, 03 February 2011 - 02:09 PM.

[outerbank]

I still am not sure what the tech guy did to VideoWave to shorten the times it takes to open and/or save as a .dmsm file in VideoWave. My guggi, you wrote that the time I described was still too long.  Here's an update on the times. I've performed 6 time tests.  The average time to open a project that is 2.22mb is 9 minutes.  The time required to "save as" is 14 minutes.  Still too long according to you, but much shorter than before the tech guy worked on the computer.  One thing that he wasn't quite sure about was how the project file is saved.  That is, does it create another file as it saves?  He compares it to how Adobe saves files.  He asked because he wondered if my hard drive should have more free space to do this.  My hard drive currently has 7.3GB of free space.  Right now VideoWave uses anywhere from 80+ percent to 100% of the CPU when opening the .dmsm file.  The only other activity running concurrently was Media MgrDB11.  He believes this usage is too high.  Or, is it just related to the 1.8GHz Pentium 4 CPU?  

While browsing the Roxio support forum there was a post regarding going into Media Mgr to turn off catalog all images, video and music files.  This was the recommendation to someone experiencing a similar "slow VideoWave".  First, will this make a difference?  Second, if so, how does one do this?

[outerbank]

If you can tolerate my questions for a little while longer, here's what I've noted.  I've been using taskmgr to monitor CPU usage while opening and using save as in VideoWave.  On average VideoWave takes about 8 minutes to open a project file, and requires about 13 minutes to save as.  During this period the following programs are active in taskmgr:

VideoWave, RoxMediaDB and VCGProxy File Manager.  The CPU usage varies from about 20 to 97% in combination with RoxMedia and VCGproxy.  The last two items vary from 14 to 50% or thereabouts, while the usage for VideoWave varies commensurately with these two.  Periodically, explorer.exe is active by a small %.  Don't know why.  ssvcHost is also active periodically.  I have no idea if this is normal.  Deleting the proxy files before opening the project file .dmsm does not appear to have a material effect on how long it takes to open the project file.  Although, VCGproxy is more active when the proxy file is deleted before opening the project. Most likely recreating the proxy files.

After the project is open and nothing is being done within the project file, VCGproxy CPU usage continues.  Varying from 00 to 97%.  Is this normal and expected?

Opened Media Mgr.  Then opened Tools.  Clicked on "Select Monitored Folder Settings".  The folders Music, Pictures and Video are shown.  Does monitoring these folders have any impact on how long it takes to either open or save a .dmsm file?  I came upon a forum post that refers to "slow VideoWave".  Within this posting is a reference to turning off media mgr monitoring.  

Thanks for your patience and input.

[grandpabruce]

outerbank, on 05 February 2011 - 01:34 PM, said:

If you can tolerate my questions for a little while longer, here's what I've noted.  I've been using taskmgr to monitor CPU usage while opening and using save as in VideoWave.  On average VideoWave takes about 8 minutes to open a project file, and requires about 13 minutes to save as.  During this period the following programs are active in taskmgr:

VideoWave, RoxMediaDB and VCGProxy File Manager.  The CPU usage varies from about 20 to 97% in combination with RoxMedia and VCGproxy.  The last two items vary from 14 to 50% or thereabouts, while the usage for VideoWave varies commensurately with these two.  Periodically, explorer.exe is active by a small %.  Don't know why.  ssvcHost is also active periodically.  I have no idea if this is normal.  Deleting the proxy files before opening the project file .dmsm does not appear to have a material effect on how long it takes to open the project file.  Although, VCGproxy is more active when the proxy file is deleted before opening the project. Most likely recreating the proxy files.

After the project is open and nothing is being done within the project file, VCGproxy CPU usage continues.  Varying from 00 to 97%.  Is this normal and expected?

Opened Media Mgr.  Then opened Tools.  Clicked on "Select Monitored Folder Settings".  The folders Music, Pictures and Video are shown.  Does monitoring these folders have any impact on how long it takes to either open or save a .dmsm file?  I came upon a forum post that refers to "slow VideoWave".  Within this posting is a reference to turning off media mgr monitoring.  

Thanks for your patience and input.

Which computer are you using when this is happening?  I don't want to go back through your countless posts to look.  If it is the boat anchor, in your signature, then I can see why there is a problem.

Edited by grandpabruce, 05 February 2011 - 03:13 PM.

[outerbank]

It is the boat anchor (Dell) using your adjective. Even though it isn't as fast as what many indicate it ought to be, its much better than it was (9 to 14 minutes versus 1 plus hours) after the tech guy sorted out the problem.  I did reach the conclusion that the limitations of the computer is at fault, not some other factor.

Now to install C2011 on the new computer.  Sort of scary as I read through all the problems people have encountered after installing C2011.  I do have a complaint with Roxio's 000080GN "Preparing your computer for installing Roxio products".  Item 1 indicates that one should perform a Windows Update.  It even provides a link.  In my case, there are a few optional .NET Framework updates that have not been installed, one of which is .Net Framework 2.0.  If I had not contacted Roxio Support by e-mail to ask about installing C2011, I would not have learned that .NET Framework 2.0 must be removed prior to installing C2011.  It seems to me that these perparation instructions are flawed in that they should include information about removing .Net Framework 2.0 prior to installing C2011, or not to install .Net Framework 2.0 after proceeding to update.  The same short-coming with their instructions occurred with reinstalling C2009.  They left out the part about removing .Net Framework 3.5, which apparently caused a host of problems for a number of users trying to reinstall C2009.  I was one of them.  That's my two cents for what it is worth.

Thanks you granpabruce for your response.

[grandpabruce]

outerbank, on 05 February 2011 - 03:51 PM, said:

It is the boat anchor (Dell) using your adjective. Even though it isn't as fast as what many indicate it ought to be, its much better than it was (9 to 14 minutes versus 1 plus hours) after the tech guy sorted out the problem.  I did reach the conclusion that the limitations of the computer is at fault, not some other factor.

Now to install C2011 on the new computer.  Sort of scary as I read through all the problems people have encountered after installing C2011.  I do have a complaint with Roxio's 000080GN "Preparing your computer for installing Roxio products".  Item 1 indicates that one should perform a Windows Update.  It even provides a link.  In my case, there are a few optional .NET Framework updates that have not been installed, one of which is .Net Framework 2.0.  If I had not contacted Roxio Support by e-mail to ask about installing C2011, I would not have learned that .NET Framework 2.0 must be removed prior to installing C2011.  It seems to me that these perparation instructions are flawed in that they should include information about removing .Net Framework 2.0 prior to installing C2011, or not to install .Net Framework 2.0 after proceeding to update.  The same short-coming with their instructions occurred with reinstalling C2009.  They left out the part about removing .Net Framework 3.5, which apparently caused a host of problems for a number of users trying to reinstall C2009.  I was one of them.  That's my two cents for what it is worth.

Thanks you granpabruce for your response.

You have wasted one helluva a lot of time of folks trying to help you, then.  That computer would have been slow running EMC 7, which came out this time just about 7 years ago!  It didn't even meet the minimum requirements of EMC7, for any video work.  Your computer was then, and is now, good for burning data.

Creator 2011 should run very nicely on your new computer.

Edited by grandpabruce, 05 February 2011 - 07:49 PM.

[outerbank]

I beg to differ with you with some of your comments.  If one looks at Roxio minimum specs for C2009, this computer was at least equal to some of the minimum requirements and exceeded it in others.  Moreover, I recall one of the gurus indicating that this computer should do fine.  That was made just after installing C2009 at the beginning of 2009.  There was at least one individual who just recently remarked that my computer was the problem, although that remark was made prior to having it repaired and when it was taking so long to open and/or save VideoWave files. Additionally, my profile has been there for everyone to see.  Lastly, it shouldn't be overlooked that the discussion initially centered on my asking if C2011 would function similarly on the new computer, and after describing how my old computer took one hour to open and/or save VideoWave files. This opened the dialog that opening and/or saving a VideoWave file should be in minutes.  

Lastly, for those who feel they've wasted their time with my issue, I apologize.  However, I did learn an awful lot about how the software should function, and that I should stick with Roxio.  Finally, there is the outcome of at least my old computer is functioning much better than before.  So again, I need to thank everyone for their help.

[gi7omy]

I did point out in post number 2 that you were at the very bare minimum for the suite to run - and that you were BELOW the recommended specifications for any video work

'minimum requirements' are a joke really - all they say is "well it will run - but it WILL be slow"

Roxio isn't alone in this - check a laptop running Vista or W7 that is at 'minimum spec' for MS and see how long that takes to even load up