Hi Daniel That’s a great way to save headroom! You can also use the BlueRipple Panner 32 as well for this..
This isn’t his bottleneck though, as I am running over 100 separate tracks (100x16= 1600 channels), as each is processed differently. This is also using an aggregate of non LAN audio interfaces spread across a 48khz AES67 network. On two separate machines…. With all sessions running at 96khz, downsampled on the fly.. My machine is an old 2009 cheese grater upgraded with two 6 core 3.46ghz cpu…. So his should be eating what I do as a snack… Tom, have you turned plugin delay compensation off for the block decoders? I found this problematic, and if they are all the same order it's not needed. I manually enter the values if needed, as I decode my subs at first order, which saves headroom but also sounds better to me… It’s a 36 channel array inc the 4 subs Are you using any other plugs? bypass one by one to see if there’s a spike. I have compatibility problems with Izotope plugs sometimes. Sparta and the IEM suite of plugs are fabulous, but they can also create random problems with the other plugs I use. They aren’t always the most efficient either Are you using any IRs? bad ones can sometimes be a problem, and if you are using many large ones the spikes will add up… Are u using live input FX? I do but each FX pretty much needs it’s own core, which means with the block decoders, there isn’t much left. So it will still state not much of the headroom has been used, and still crackle and pop... Can you tell me your buffering settings.. Mine as follows: Unchecked ‘auto-detect the number of processing threads’ Manually typed in the amount of cores. 12 for me. Thread priority set to ‘highest', behaviour ‘automatic’ media buffer 1200 ore buffer 100% checked ‘Disable media buffing for tracks with open midi editors' unchecked ‘disable media buffering for tracks that are selected’ Checked ‘Anticipative FX processing’ unchecked ‘allow on tracks with out….’ unchecked’ Allow on tracks with open…' checked Allow live FX multiprocessing on 12 CPUs Best Steve > On 19 Oct 2021, at 17:25, Courville, Daniel <courville.dan...@uqam.ca> wrote: > > Hi, > > The problem is that you have, say, 30 mono audio files * 16 channels = 480 > channels. > > You could use IEM MultiEncoder and have the 30 mono audio files sent to a > 30-channels aux bus (with the MultiEncoder on that bus) = 60 channels > > That's the way I would do it. > > Le 2021-10-19 12:00, Sursound au nom de sursound-requ...@music.vt.edu a > écrit: > > Today's Topics: > > 1. Reaper performance issues. (Tom Slater) > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 18 Oct 2021 20:10:22 +0100 > From: Tom Slater <slater...@gmail.com> > To: "sursound@music.vt.edu" <sursound@music.vt.edu> > Subject: [Sursound] Reaper performance issues. > Message-ID: > <CAOg=fv65x09w8xvn+wp87umlqwawpdd_zs9jazeqk11+ne8...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi everyone, > > I wanted to get an idea of your experiences with Reaper running large (ish) > ambisonic sessions. > > I mostly work in 3rd order ambisonic and use the Blue Ripple plug-in suite > and Rapture 3D Advanced for decoding. > > I?m decoding to a 25.2 channel speaker array and could have up to 40 odd > tracks, each with a 3rd order encoder/panner on. > > When I reach about 30 tracks Reaper performs very badly - laggy response > when moving play head around, lots of clicks and pops when muting/soloing, > random clicks and pops when just playing the session. Sometimes if I need > to record arm a track playback is completely glitchy. > > I understand that 30 odd tracks each with a 3rd order encoder, and decoding > to 27 channels is a lot to ask of the computer. BUT I?m using a 14 core > iMac Pro with 64gbs ram. The sessions are running off an external TB2 drive > (not SSD). > > I?ve played around with buffer settings which don?t seem to make much > difference. Also the perf monitor in Reaper and the activity monitor in OSX > don?t show that much strain. > > Any optimisation tips greatly appreciated. Or any other similar issues with > Reaper? > > Cheers > -------------- next part -------------- > **************************************** > > _______________________________________________ > Sursound mailing list > Sursound@music.vt.edu > https://mail.music.vt.edu/mailman/listinfo/sursound - unsubscribe here, edit > account or options, view archives and so on. _______________________________________________ Sursound mailing list Sursound@music.vt.edu https://mail.music.vt.edu/mailman/listinfo/sursound - unsubscribe here, edit account or options, view archives and so on.
