No, I don't think this is a problem here since I the samples are most probably buffered in or played completely from RAM. The easiest way to grab screenshots and uploading them is using Shup: īut I won't promise an easy solution - problems of this kind can be really hard to figure out and posts often remain unanswered. Since some prefs settings have to be checked, it would be cool if you could post screenshots (here or in your new thread) of the following prefs pages: You might also consider to ask that question in the general forums again. Is the automatic output routing working now? Maybe it's a problem with my template only? If not: That's a tough one, but since you checked already some stuff and provided vital information, I'd say this is a Reaper configuration problem. Reaper seems to be so conceptually different from other sequencers.
#Emu proteus x2 instrument definitions manual#
Other than the openlabs site, are there any more tutorial videos or other resources that could be helpful?Īlso, what benefits does Reaper's manual routing functionality give that other, conventional track/channel sequencing systems doesn't? Is there a way to simplify things because at the moment we have a bazillion faders at the bottom of our screen? My machine has a 3.2 GHz chip and 1Gb of RAM. We ran the DPC latency checker ( ) and there were no problems at all.
#Emu proteus x2 instrument definitions how to#
Have you (or anyone) got any thoughts on what's causing it and how to make it stop? Our card is an EMU 0404. This is just real-time playing, not recording or sequencing in any way. The crackling sounds even when CPU is at only 10% use. The crackling happens whatever instrument we use. Its only when we use VST instruments in Reaper that the crackling begins to sound. And if we use Proteus X on a stand alone basis, the sound is fine. With just one track open, there is no problem. After a few teething problems we seem to be making music.įirst, when we use reaper, we get a horrible digital crackling sound when we use the template with all the tracks and channels and routing. The template is already labeled and colored and so I thought I don't just delete that part of this post. But I hope also that it's superfluous because with some outputs set in Proteus, the automatic multichannel routing may work. I hope I didn't make some dumb mistake while creating the template. If you're ready setting it up, save it again as template so you don't have to go through this twice. Now you can open an empty (new) project and r-click on the empty space in the TCP and select the template from the "insert track from template" flyout menu. Delete audio and MIDI channels you don't need later to keep the track count low.Ĭ:\Documents and Settings\Your_Account_Name\Application Data\REAPER\Track Templates\ It routes from there to 19 output channels and has the 16 MIDI channels routing to it. It's empty (since I don't have Proteus) and you have to load Proteus on track 1 (labeled "ProteusVSTi") yourself. Maybe that solves or improves something or even works. However, I quickly made a track template for you before I had the idea to look into the Proteus X manual. If I understood you correct, you can't select any other bus within Proteus X than bus 1? I have to verify here, do you use Proteus X or X2? If it's Proteus X, you maybe just forgot to set a number of outputs in the Proteus preferences: Doing this in that order may be essential, this is probably the reason why the automatic routing didn't work.
In this video, the MIDI channels/instruments and the output busses are being set up in Proteus before the "build multichannel routing for output." function in the Reaper FX chain window is being employed. I assume you watched the "Proteus Setup" video. Do you (or anyone) know what's happening here, and is it related to the above error msg?
I found an openlabs video addressing the multitimbral routing issue, but on attempting to follow it, I got stuck when attempting to route different Proteus MIDI channels to different buses - on the video there were 19 buses available - but I only seem to have Bus 1 for each channel.