TranceAddict Forums (www.tranceaddict.com/forums)
- Production Studio
-- reason DPU problem
Pages (3): « 1 [2] 3 »

not sure if i got u on my msn but u could send me the track to doublecheck here unless ur realy secret about how you work tho.

Reason WILL max out at 50% cpu load, since it only uses one core..

how can i get it to use two cores, or can i?.

yeah palm i will send you the track to have a look at, send me a pm or msn message

whats your cpu usage limit at?

edit> preferences> cpu usage limit

i think reason defaults at something like 75%

dont have it at 100% tho or your pc will max out and take AGES to respond.

AMD cpus aint too good these days, intel core2 duo are much more powerful. maybe best to upgrade your cpu.

saying that my tracks max out my core 2 duo aswell, and its quite annoying, reason defo aint a dual core friendly program.

i have my reason cpu limit set too 100%. if i set it lower reason maxes out quicker.

i have a HP Pavilion a6030n

AMD 64x2 dual core processor

2048 MB system memory

the thing is the cpu says 50% and reason says 100%. so even if i buy a better computer i will always have this problem.

Hey there, I was in the same trouble when I just updated my CPU to a dual core processor. I noticed that when I was working in a simple project just loading a few instruments (just some subtractor routed to a main mixer with send fx such Advanced Reverb and delay line 1) the led indicator turned up to red.

So, I did a lot more of tests. I was in a Pentium 4, 2.2 Ghz, 512kb L2 cache, using just 512 MB RAM, and the projects I was working in, got a slightly increment around 90% when it was played in real time, but still playing correctly.

How you can explain that a more sophisticated processor would to turn up a lot with the same project?.

The answer: > RAM <

For some reason, there was an incompatibly managing system resources in conjunction with the processor. I used an 1GB generic RAM, so I replaced it with a Kingston one, same capacity... 1 GB.

And then everything went back to normal when I formatted my PC, installed Reason right away, and did the tests.

Don't know exactly what happened, because some other software as games, and 3D modeling software, worked very well & fast still using the previous RAM module.

About of how many cores Reason uses, I think it use just one, that's because I believe that Reason lacks of a multicore support atm.

quote:

Originally posted by lowski the thing is the cpu says 50% and reason says 100%. so even if i buy a better computer i will always have this problem.

Completely true, the PC market can only churn out more powerful CPUs so fast.

What it comes down to is knowing what instruments are necessary and which can be taken out or rendered into an audio clip. Personally i also use reason, and am not a fan of using audio clip substitutions, so i tend to just put a little more thought into my synthesis process. Its sometimes a choice you have to make, whether to have a thor or replace it with a few layered subtractors.

PM me and i can help you out with reason related stuff if you want.

So if you were to use a quad core 2.4ghz cpu pc, reason would only use one of the processors out of the 4?

Would it make more sense to use say a P4 3.4ghz as reason only uses the on processor?

Lowski - If you have many thor's maybe bounce them. I made a combi with 3 thor's the meter went to red when playing. Thor is a hungry beast

quote:

Originally posted by music2dance2 So if you were to use a quad core 2.4ghz cpu pc, reason would only use one of the processors out of the 4? Would it make more sense to use say a P4 3.4ghz as reason only uses the on processor?

Yes, and yes.

quote:

Originally posted by music2dance2 2.4ghz quad core

i have exactly that and im having no problems what so ever, so i keep wondering how big ass projects you guys make??? Either this or it has to do with something else too, like someone suggested RAM type etc. How well the components of the computer playes together.

I was really surpiced when i tested Reason and some of my heavier projects on Mac Mini, 1,87Ghz 1GB Ram - no big problems at all, i thought i wouldnt be able to play the first 10secs. So it seems the mac is well build.

Tho i couldnt do much else, iTunes and mozilla had to be closed to gain performance.

Ive experienced some of the same thing one time before on my GFs PC, which i thought was crap, some old HP shit with no CPU or RAM to talk about at all, but stuff worked anyway. i just dont understand stuff like that.

also a tip, the combinator EATS CPU as hell.

quote:

Originally posted by palm also a tip, the combinator EATS CPU as hell.

I recently found this out, I made a mistake and used too many. I'm going to do a test tomorrow on my thor patch and double check a few things. I'll post up my findings as I'm a little shocked on how much cpu is used with it.

I have to admit not one of my older projects had any problems i have a 3.2ghz HT P4 with 1gb ram and have no problems, my last project does however some how eat up my cpu. That said its obviously down to that particular project, which i have streamlined it down and its better except the thor patch i mentioned earlier.

Beyer - So I would benefit in having more ram rather than maybe a a quad core PC?

There is a PC at my work which is a 3gb ram, 3.6 Xeon dual core with HT so it runs as a quad core I may try and run my project on there and see how things look with my latest project.

quote:

Originally posted by palm i have exactly that and im having no problems what so ever, so i keep wondering how big ass projects you guys make??? Either this or it has to do with something else too, like someone suggested RAM type etc. How well the components of the computer playes together. I was really surpiced when i tested Reason and some of my heavier projects on Mac Mini, 1,87Ghz 1GB Ram - no big problems at all, i thought i wouldnt be able to play the first 10secs. So it seems the mac is well build. Tho i couldnt do much else, iTunes and mozilla had to be closed to gain performance. Ive experienced some of the same thing one time before on my GFs PC, which i thought was crap, some old HP shit with no CPU or RAM to talk about at all, but stuff worked anyway. i just dont understand stuff like that. also a tip, the combinator EATS CPU as hell.

I think the acid test is to test the file on other pc's at least it could narrow down if this was the project or not?

quote:

Originally posted by palm also a tip, the combinator EATS CPU as hell.

Are you sure about that?. i remember reading on the propellerhead site (or somewhere) that the combinator was actually pretty good on using cpu. i usualy have all of my synth patches in a combinator, however i almost never use the thor.

one thing i'm not interested in i bouncing down to audio. it makes reason seem like a toy if you have to start doing all these things just becuase it can't handle enough functions.

i started off producing on a technics kn7000 with 16 tracks. i maxed that thing out pretty fast aswell, and found it pointless to even play on it when i knew that i could never get a good song out of it. maybe it's time for a change. i love reason but i want something that i can really go off on. plus; without being skilled at programming patches it's almost impossible to find good refills geared toward modern trance

i havent red anywhere that combinator uses alot of CPU ive experienced it on my old computer and learned how to make effecient tracks then.

I would stick it out and try harder, you will look back and be glad you did. But not saying to not to move on at all that is. WIth regards to sounds, try a refill that sounds similar and tweak away, it will teach you how to program sounds or just get the sound you want from another preset/refill. Oh also get a book or two on this, honestly a week reading up on it and you'll propell yourself forward in making sounds you want and tweaking sounds for the better.

Bouncing isnt something i do Ive done it once but I reckon once I figure out whats up with my project I wont have to. That said though its your choice dude

quote:

Originally posted by music2dance2 WIth regards to sounds, try a refill that sounds similar and tweak away, it will teach you how to program sounds or just get the sound you want from another preset/refill. Oh also get a book or two on this, honestly a week reading up on it and you'll propell yourself forward in making sounds you want and tweaking sounds for the better.

What's a good book to get?. Is there any books geared towards making patches in reason?

There are probably some with info on specific patch types but you will have to research that. I would say get the dance music manual, that will tech you how to make patchs in reason or any DAW/hardware synth- well it will give you the understanding on how to go about it. Plus lots more info on everything else.

check it out here (this isnt the whole book)

http://books.google.co.uk/books?id=...ce+music+manual

there are good thor tutorials already on propheads, fm -synthesis etc really cool. fm is so phatt

Thats very true the site is a great resource.

thanks guys!! that book looks really good, i will pick up that right away. and i will check out propellerheads to.

Did you ever get to the bottom of this mate? My latest track that screwed my PC was probably the over use of devices - I remember seeing one of your tracks before. How many are you using in the project concerned?

I don't get how people max out reason, that thing is really cpu efficient, and that is exactly why the propellerhead peepz don't want to add audio tracks in there, they just want to keep it simple and stable.

Actually what did people before when they had no audio recorder?? They were using their sampler as a recorder.

Can you try this out:

Make a specific NNXT or 2 featuring several outputs linked to a mixe, check every single channel that eats your cpu, and render it to a wav, import it into the nnxt and set it to a specific keyboard note and audio output. Do it again and again on that nnxt with all tracks, of course on different keyb notes and channels, you should see a huge difference.

quote:

Originally posted by Lolo Make a specific NNXT or 2 featuring several outputs linked to a mixer, check every single channel that eats your cpu, and render it to a wav.

You're right on this, Lolo. In my experience Reason hits CPU limits faster than RAM limits. This workaround will free up CPU, but it's such a hassle that Reason doesn't start playing a long WAV sound at the point you jump to - you have to play the sample from the very start every time. Sure, if you're working on a small loop in the middle of a song, you can render just that loop to WAV. But overall, it's not ideal. If they somehow managed to get the software to play sounds partway through MIDI events, that would be fantastic. But that seems like it'd be tricky to implement, and make the audio stop for a bit while you jump around the song.

Reason is good for learning how to use tools economically - choosing the right sounds to avoid heavy EQ use, treating groups of instruments rather than individual instruments, and so on. It's not good just for CPU issues, it improves workflow as well.

Powered by: vBulletin
Copyright © 2000-2021, Jelsoft Enterprises Ltd.