Video/ Routing/ Performance-issue FR/BR?

Thanks Diogenes for your quick reply! Any shortcut for this action would be great...! I need this kind of track-copying quite often.

Yes Sir! That's exactly what I was looking for! Your quite a genius EvilDragon, thanks for showing up! Do you have any idea about what 'could possibly cause this strange video-behaviour? Or did you have similar results in any of your projects, when you're working with VSTi's and their routings? I mean my "test-project" actually only had 4 audio-tracks and 4 midi-tracks running and really doing something. There were a some more VSTi's open, but didn't have anything to do.... just sitting there and wait. In other words: maybe what I tried to do wasn't quite the "Reaper-way". Do you know about any other workaround to setup a default template, which consists of my favourite VSTi's, FX, routings and video-track (see above as example), not eating so much CPU? Maybe I can tweak Reaper's audio-processing (Preferences settings), but I have no clue where to find some more information about it? Thanks so much for your help!

A little update: this afternoon I spend some time to rebuild this project in a different way. First I began to create all those VSTi-tracks I would need, took care of proper routing, and adding FX. Afterwards I imported the midi-arrangement and created the sends to the VSTi's. At last I added the audio-tracks and imported the audio-files. Funny thing is, the system now ran on about 15-39% CPU, according to Reapers Performance-meter, all the FX used not more than 10% CPU. On idle, Reaper ran on 10-30%...doing nothing... but this now was even less than with my first project. Then I opened a new Project's Tab, worked on some audio-files for quite a while, just 7 tracks, closed it again and switched back to the "big" arrangement. And guess what..? Reaper now ran on 7-18% CPU!!! On idle a bit less. Is there anybody out there, who knows what's going on there...? This seemed like Reaper saying "ok, give me just a few minutes, I'll be right there for you!" Strange, isn't it?

Really noone...? Hmmmmm...

No idea mate. You could post the project here(sans media). I haven't gone that deep researching Reaper before, but if you like, why not do a standard situation test session, then repeat what you did, and post that session with a detailed description. If the CPU consumption does change, there are many ways this could happen. For this to be of any use it needs to be reproducible.

Hey airon! That's what I'm tryin' to do now. It might have something to do with Reaper's handling of VSTi outputs... not quit sure yet... As soon as I know a bit more, I'll get back on this. Thanks for any help!

After doing a little more research, I found this thread: And NOW I wonder if this has something to do with the Asus P5B-mainboard...? evanrabby had similar problems and obviously he ran some serious tests... Again: hmmmmmmm! Any fellows out there, with an Intel Setup based on The P5B (E/ E-Plus)? Also any problems/ strange behaviours...?

Solved! 

I hope this is some useful info for someone out there.. DISABLING "Anticipate FX procesing..." and DISABLING "Allow live FX multiprocessing.." in "Preferences" > "Audio" > "Buffering" settings worked it all out! Now I run this project with the same CPU-consumption like I did in Cubase. Maybe even a little less... I couldn't notice any difference while playing back, or listening to live input, I could hear every FX loud and clear, so... for me this is solved! That would be a real Feature Request for me, by the way: Way more real deep information about the Audio System Settings! I like to know what I'm doing... ;o)