Messages in this topic - RSS

Home ? Tech Help ? *Solved* Out off memory on start up *Solved*

the topic is closed
14/02/2011 03:49:22

primaryartemis
primaryartemis
Posts: 3
*What the Problem was*
Hello I used muvizu for awhile several months back and with some new free time I have been wanting to get back into it. I downloaded the newest version of Muvizu and opened it hoping to re familiarize myself. When I opened it was was greeted with

"It is with some regret I must inform you of the following error:
Out of Memory."

"Muvizu is running low on memory and will run in restricted mode until memory is freed up" ect. ect.

This happened when I first open it when I have nothing created yet.

Windows XP 32-bit
Geforce 8400 GS
DirectX 9.0c
4 GB of RAM
Ran it without other programs running.

I am hoping there is some way to fix this I enjoyed using Muvizu some time back.

-Artemis.


*Solution*
When running a 32 Bit version of Windows you can go into the boot file and add /3GB to increase the amount of ram programs can use from 2GB of ram to 3GB of ram. I found out that this was the error and by removing it I can now use Muvizu like I had before. Hope this helps some one else as well.

If you have ever added something to your boot file to modify the page file or RAM (which is what caused this error) Here are the steps to revert it and thus make Muvizu work again for each Windows OS.

  • Windows XP
  • Click "Start"
  • Select "Run"
  • Type notepad c:\boot.ini and click OK
  • Look for /3GB and /Userva=####, where #### is a number. Make note of the value for #### in case you wish to restore these entries later.
  • If either exists, delete ONLY the /3GB and /Userva=#### text - do not modify any other part of the file.
  • Save the changes and reboot your system to apply the change.

  • Note: To revert this change, simply restore the /3GB and /Userva=#### entries in the exact location you removed them from.


Windows Vista or Windows 7
  • Click "Start"
  • Type cmd and press Enter
  • Type bcdedit and press Enter
  • Look under the "Windows Boot Loader" section for an entry titled "increaseuserva". Make note of the value in the right column next to increaseuserva in case you wish to restore this entry later.
  • If it exists, type bcdedit /deletevalue increaseuserva and press Enter. The message "The operation completed successfully" should appear.
  • Reboot your system to apply the change.

  • Note: To revert this change, follow these instructions but enter bcdedit /set increaseuserva ####, where #### is the value you made note of earlier.
    edited by primaryartemis on 21/02/2011
    edited by primaryartemis on 21/02/2011
    edited by primaryartemis on 21/02/2011
    permalink
    14/02/2011 10:14:51

    Marco_D
    Marco_D
    Posts: 582
    Hello primaryartemis,

    Sorry to hear that you are having problems with Muvizu.
    I once had the same problem and tweaking the virtual memory settings solved the problem. So hopefully it will work for you too.

    Here are the steps you need to take to tweak your virtual memory.

    How to manually change the size of the virtual memory paging file.

    You must be logged on as an administrator or as a member of the administrator’s group to complete this procedure. If your computer is connected to a network, network policy settings may prevent you from completing this procedure.

    To manually change the size of virtual memory, follow these steps:

    • Click Start, click Run, type sysdm.cpl in the Open box, and then press ENTER.
    • Click the Advanced tab, and then under Performance click Settings.
    • Click the Advanced tab, and then under Virtual memory click Change.
    • Under Drive , click the drive that contains the paging file that you want to change.
    • Under Paging file size for selected drive, click Custom size, type a new paging file size in megabytes (MB) in the Initial size (MB) or Maximum size (MB) box, and then click Set.
    • Click OK to close the dialogue box and apply changes.

    Note: After you change the size of the paging file, you may be prompted to restart Windows. If you are prompted to restart, the changes will not take effect until Windows is restarted.

    Note 2: To have Windows select the best paging file size, click System managed size. The recommended minimum size is the same as 1.5 times the RAM on your computer, and 3 times that figure for the maximum size. For example, if you have 256 MB of RAM, the minimum size is 384 MB, and the maximum size is 1152 MB.

    Please let us know if you were able to solve this issue.

    Kind regards,
    Marco
    edited by Marco_D on 14/02/2011
    permalink
    21/02/2011 13:23:05

    Quoling
    Quoling
    Posts: 112
    I have the same issue with 8GB on Win7 64 - it seems the bigger the set gets the more memory is needed and this causes the error. I have tried the suggestion without success...really looking forward to the next version of Muvizu as these types of errors are stopping me from using the app.
    permalink
    21/02/2011 13:30:58

    mystoMuvizu mogulExperimental user
    mysto
    Posts: 471
    I have 12 GB on Win 7 64 and have the same issue with the "out of memory" message. It doesn't stop me from animating, I just try to work within the memory limits of the current release of the program. The 64 bit version due out soon will probably fix this issue.
    permalink
    21/02/2011 13:33:37

    Quoling
    Quoling
    Posts: 112
    mysto wrote:
    I have 12 GB on Win 7 64 and have the same issue with the "out of memory" message. It doesn't stop me from animating, I just try to work within the memory limits of the current release of the program. The 64 bit version due out soon will probably fix this issue.


    How do you "work within the memory limits" ? - how do you know what these are?
    permalink
    21/02/2011 15:03:57

    mystoMuvizu mogulExperimental user
    mysto
    Posts: 471
    Well, in my case the memory issues seem to "pop up" whenever I try to use a lot of special effects and lighting effects. From what I understand those things are very memory intensive. I'll use the Status Quo animation I did as an example.

    I started by building the set, which was fairly elaborate at first with no problems. I then added the characters and props to the set with no problems. Then I animated each character from start to finish with no problems. So far so good.

    My memory issues came when I was adding all of the special effects to the animation. Lights flashing in sequence, Images projected on the background, smoke, fire, etc. At first everything was going pretty well and was looking really good. Then things started to "bog down". I started getting "low on memory" messages. Quite a lot of them as a matter of fact. My solution was to eliminate effects one by one until I didn't get the "out of memory messages" anymore. A fairly simple solution but it worked in my particular case.

    I could have probably broken down the animation into several different scenes, saved each scene as a set file, worked on each scene separately and then used a post processing program to edit the scenes together into one animation. That would have probably taken care of the memory issues because instead of one huge "memory hog" set file, the animation would have been broken down into several smaller less memory intensive files.

    I chose to work on the project as one big set file though and therefore had to limit the amount of special effects that was in the animation. It was kind of frustrating not being able to add "all the goodies" into one set file that I wanted but I still think that given the circumstances the final animation turned out pretty well.

    My solution was to for lack of better words "tone down" my animation a bit until I got rid of the out of memory issues. It worked for me. Please keep in mind that I am not a very technical minded fellow and the Devs here at Muvizu can probably answer any questions you have way better then I can. They are a great group of people.

    I hope my explanation helps you out a little.
    permalink
    21/02/2011 16:21:09

    Quoling
    Quoling
    Posts: 112
    Thanks for the detailed reply - that's what I was thinking the solution would be - I have a very large set (inspired by your Quo film) of a Queen stage and am going to have to cut it down into sections and different videos and then join them together for the full thing (doing Bohemian Rhapsody live) - this partly due to the memory issues but also because "artistic" issues... Rock Band
    permalink
    21/02/2011 16:37:40

    mystoMuvizu mogulExperimental user
    mysto
    Posts: 471
    Glad I could be of some help. I look forward to seeing your Queen video.
    permalink
    21/02/2011 16:39:35

    Quoling
    Quoling
    Posts: 112
    mysto wrote:
    Glad I could be of some help. I look forward to seeing your Queen video.


    Sadly it's still a long long way off - proving to be a tad more difficult than I was hoping....
    permalink
    21/02/2011 17:08:50

    mystoMuvizu mogulExperimental user
    mysto
    Posts: 471
    Hang in there, I know how you feel but it'll be worth all of the hard effort in the end. If I can be of any help just ask! Good Luck!
    edited by mysto on 21/02/2011
    permalink
    21/02/2011 17:40:45

    primaryartemis
    primaryartemis
    Posts: 3
    Problem solved!

    Since I run a 32bit version of windows XP I had modified the boot file with the /3GB function that allows programs to access 3GB of memory oppose to 2GB. Oddly enough this is what was causing the crash for me. Hope this helps some one else. Just remove the /3GB from you boot file people.
    permalink
    21/02/2011 17:50:52

    primaryartemis
    primaryartemis
    Posts: 3
    Sorry for the double post but look in OP for detailed description on how to fix this specific error for XP and Vista/7
    permalink
    22/02/2011 10:06:23

    Marco_D
    Marco_D
    Posts: 582
    Hi primaryartemis,

    Glad you managed to identify the problem.
    Have fun with Muvizu.

    Cheers,
    Marco
    permalink
    the topic is closed

    Home ? Tech Help ? *Solved* Out off memory on start up *Solved*