Hi,
I'm running a project right now with 12 tracks only, most of them drum samples and only 1 Massive instance.
I added my BCF2000 Controler to propperly record Massive CUTOFF etc. along the track but I can't work with the song anymore as my CPU goes up to 160%. Anyone an idea? I MERGED many instruments and kicked them out again during production process. Might this be an ORION specific problem? I had project with many more tracks and hard core generators running without any problems.
It the BCF2000 controler to time consuming?
Need help!
Very Low Orion PerformanceModerators: Christophe, Mark
10 posts
• Page 1 of 1
Re: Very Low Orion PerformanceComputer specs? Audio settings? Timebase?
Re: Very Low Orion PerformanceI have read Massive sometimes requires high CPU resources. Read this:
http://www.native-instruments.com/forum/threads/cpu-load-in-massive.42923/ and this http://www.massivesynth.com/tutorials/ni-massive-cpu-overload/ "Pleeease, bring back ORION!"
Re: Very Low Orion Performance
Disconnect it and there is a chance you'll see if this is the case. Bear in mind that the link dmassive gave are from 2006, when Massive was known to be a CPU hog but not on a modern computer. So unless you are using a 10+ years old rig it is unlikely to be that bad. We need more info on your specs. Project a bit more detailed and what version of Orion?
Re: Very Low Orion PerformanceIntel i7-2600 CPU 3,4 GHz
8 GB Ram Soundcard: RME: Hammerfall DSP 9632 My system is pretty phat for production and I hardly realize any hard CPU drops even with 12, 14, 16 or whatever tracks and instances of GeForce's Minimonsta which is very CPU hungry. Somehow this set is strange. Richard tested it already but without all the plugins and samples. His CPU is @ 9% but that is not really recreating the case without the entire setup. The song is not really challenging from a generator perspective. Most tracks are Drum samples. Only Massive is a CPU crackhead but this should not be the case. I still think that the MERGE function caused the problem. I MERGED a lot of instruments from other projects and deleted them. There might be some artifacts.
Re: Very Low Orion PerformanceI'll test merge and see if I get any issues here.
Re: Very Low Orion Performance
Cool. Thx! That's great. It's strange as the project is really not "heavy". It must be something with the project.
Re: Very Low Orion PerformanceMaybe more got merged than expected and therefore got duplicated causing more CPU demand ? I've never used Merge in practice only during testing so I don't think I'll be much help..............
If you delete each track at a time is it possible to narrow down which on is causing the demand ? Sorry. I just had three teeth pulled and the Meds are starting to kick in so the brain isn't working too well.............
Re: Very Low Orion PerformanceI tried to transfer each instrument/track to an empty project with MERGE. The recording of some instruments e.g. CUTOFF etc. is missing in the new project. All parameters of instruments are empty. No CUTOFF, Filter or any other value that I recorded by hand in the old project got transfered.
I also tried that. I deleted each instrument down to only 2 left in the project. The performance still dropped at the same positions in the track. And MASSIVE was not part of the project anymore. Only 2 frum sets I think.
Re: Very Low Orion PerformanceWhen you say the performance dropped at that point you mean the CPU demand went up ? There must be something at that point in the song causing the demand (thanks Captain Obvious )
Just two Drum Racks ? No effects no automation.......wierd.
10 posts
• Page 1 of 1
Who is onlineUsers browsing this forum: No registered users and 214 guests |
© 2017 Synapse Audio Software. All Rights Reserved. |