|
|
|
10-25-2014, 04:06 PM
|
#1
|
Human being with feelings
Join Date: Sep 2008
Location: Sweden
Posts: 7,432
|
All kinds of strange behavior...
I'm suddenly getting all kinds of strange behavior from just playing a rather basic Reaper project. First it was a crash when staring up v 4.731 (see http://forum.cockos.com/showthread.php?t=148007), now several times during playing of the project I get this:
I'm not sure what is going on, but the main thing that has changed is Reaper updating to v 4.731. And of course general W7x64 updates.
I have 8GB RAM and performance meter says RAM use is 3646MB. Hm... that is 3GB! Does Reaper really use that much? This is not at all a very heavy project, only 43 tracks.
__________________
// MVHMF
I never always did the right thing, but all I did wasn't wrong...
|
|
|
10-25-2014, 04:11 PM
|
#2
|
Human being with feelings
Join Date: Sep 2008
Location: Sweden
Posts: 7,432
|
And now I'm getting this:
This one I have definitely NEVER seen before. Not on thsi project nor on any other.
Is the v 4.731 of Reaper more RAM-intensive than previous versions?
__________________
// MVHMF
I never always did the right thing, but all I did wasn't wrong...
|
|
|
10-25-2014, 04:12 PM
|
#3
|
Human being with feelings
Join Date: Dec 2011
Location: Portsmouth, UK
Posts: 4,376
|
Quote:
Originally Posted by Fabian
This is not at all a very heavy project, only 43 tracks.
|
43? There was a time when I dreamed of one day owing an eight track....
The heaviest project I ever worked on in my life uses about 50 tracks. I don't know how this computer would handle it, but it slowed my old PC to a crawl.
I ended up starting a bunch of sub-projects to deal with individual tracks against a rough mix of everything else.
It all depends on what those tracks are actually doing, of course....
View > Performance Meter (Ctrl + Alt + P) will show you which tracks are hogging your resources.
Last edited by Fex; 10-26-2014 at 05:31 PM.
Reason: typo
|
|
|
10-25-2014, 04:27 PM
|
#4
|
Human being with feelings
Join Date: Sep 2008
Location: Sweden
Posts: 7,432
|
There is no hogging the resources, that is what confuses me... This is an AMD Phenom II x6 1055 machine with 8 GB RAM, and it has never so much as hiccuped on this project before.
Now I'm getting tracks that suddenly do not output any sound, I get these warnings, and stutter and what-nots. And CPU is at ~12% total, ~2% RT. Disk read is at ~1.5 MB/s.
It seems that RAM use is the problem, and the performance meter does not say much more about that than 3567 MB.
8-track...? Yeah, I started with a Fostex 4-track 40 years ago
__________________
// MVHMF
I never always did the right thing, but all I did wasn't wrong...
|
|
|
10-25-2014, 04:31 PM
|
#5
|
Human being with feelings
Join Date: Dec 2011
Location: Portsmouth, UK
Posts: 4,376
|
Have you tried opening the project with FX offline, and bringing them back in one by one? It might be that one plug-in is causing the problem.
|
|
|
10-26-2014, 02:01 AM
|
#6
|
Banned
Join Date: Jul 2014
Location: United States of Europe, Germany, Mönchengladbach
Posts: 2,047
|
Quote:
Originally Posted by Fabian
And now I'm getting this:
This one I have definitely NEVER seen before. Not on thsi project nor on any other.
Is the v 4.731 of Reaper more RAM-intensive than previous versions?
|
I would have a close look at what you have set for a size for virtual memory (pagefile.sys). if this is too small or set to a fixed value that error message can come up.
let Win decide what size this should be. if everything is fine with pagefile.sys go to Reaper preferneces and tell Reaper to shut up. if then the project is stuttering ... well, then you are out of memory and the virtual memory cant save you there. in that case you should set your latency to higher values, helps a lot.
|
|
|
10-26-2014, 04:06 AM
|
#7
|
Human being with feelings
Join Date: Nov 2012
Location: 'straya
Posts: 9,409
|
Back then 4 tracks was plenty enough for my one-track mind.
Is it possible theres some kind of feedback loop thats processed over and over via fx and routing? I'll get me coat.
|
|
|
10-26-2014, 10:40 AM
|
#8
|
Human being with feelings
Join Date: Jan 2010
Location: Kalispell
Posts: 14,759
|
Or you could possibly have some RAM that's going bad.
When you right click on "My Computer" and select properties, what does the RAM say there?
|
|
|
10-26-2014, 01:10 PM
|
#9
|
Human being with feelings
Join Date: Sep 2008
Location: Sweden
Posts: 7,432
|
Looking around W7 I see nothing strange. RAM is 8GB, page file 7934 MB.
Again... this (and all other) project(s) previously ran like water on this system. This is the first time that I've noticed hiccups and stuff. And the only thing that changed is Reaper version and W7x64 updates.
I'll do some RAM testing see if it reveals something...
__________________
// MVHMF
I never always did the right thing, but all I did wasn't wrong...
|
|
|
10-27-2014, 09:02 AM
|
#10
|
Human being with feelings
Join Date: Jan 2010
Location: Kalispell
Posts: 14,759
|
Quote:
Originally Posted by Fabian
I'll do some RAM testing see if it reveals something...
|
Also if you can, you might try going back to an earlier version that you know worked to see if the problems go away.
I'll be anxious to see what you come up with.
|
|
|
11-03-2014, 04:54 PM
|
#11
|
Human being with feelings
Join Date: Nov 2013
Location: Jerusalem, Israel
Posts: 659
|
Take a look at this thread:
http://forum.cockos.com/showthread.php?t=145430
If you are using loops as I do, you might well have bumped into the same bug.
I have reported it on the tracker:
http://forum.cockos.com/project.php?issueid=5355
In case you are indeed affected, please vote on the tracker. I bet this affects many people using loops in a moderately complex project, and it could help if more people voted, so this issue gets some attention from devs.
Edit: By the way, I'm using v4.73, but I've been seing this problem for as long as I'm into Reaper (about a year).
|
|
|
11-03-2014, 05:11 PM
|
#12
|
Human being with feelings
Join Date: Nov 2013
Location: Jerusalem, Israel
Posts: 659
|
Anyway I don't think RAM going bad can have anything to do with Reaper utilizing huge amounts of memory. What you describe is a typical manifestation of memory leak in software, whether it is caused by the "loop bug" or something else. If you have time and will (and if it turns out to be a separate bug from the one I reported), you can try to analyze under what conditions this bug is triggered. You will need to monitor RAM use closely while working on your project.
|
|
|
11-06-2014, 09:13 PM
|
#13
|
Human being with feelings
Join Date: Aug 2013
Location: Bowral, Australia
Posts: 1,643
|
Are you using the 32 bit or 64 bit version of Reaper? If 32, then you may have have reached your limit (assuming you are actually using that much ram for your project).
|
|
|
Thread Tools |
|
Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -7. The time now is 01:41 AM.
|