Foolproofing of buffer settings

[Buy One]

For the following reason

Recently, I adjusted the buffer size to a very high value in the millions. As a result, Reaper is now unable to open and crashes immediately, regardless of what I try.

[bobobo]

a very high buffer needs a place to reside.

more ram, i your case a million times more, could help here.

[Coachz]

[EpicSounds]

I agree, there should be some error checking with this like there is with plugin crashing in the monitor chain and other situations.

If anyone is looking for a solution in the meantime

open reaper.ini

for mac
coreaudiobs=

for windows

asio_bsize=
waveout_bs=
dsound_bs=
wasapi_bs=

On Windows you can go to the start menu and find the option to open reaper with audio configuration on startup, which should start with audio offline

[bobobo]

interesting thing.
set the buffer to a high value 50000 f.i., make a track weitch the beloved reasynth and parameter-modulate one value and examine it.

[Phazma]

Regarding this, I was always curious if there is a downside to setting a buffer size that's not 2^x. Most software limits the user to such values, while Reaper allows to freely type any number. Is there a decrease in performance or other problems to be expected when setting non standard values like for example 250 instead of 256 or 500 instead of 512.. except obviously that lower buffer sizes require faster CPU speeds.

[Buy One]

Originally Posted by Phazma

Regarding this, I was always curious if there is a downside to setting a buffer size that's not 2^x. Most software limits the user to such values, while Reaper allows to freely type any number. Is there a decrease in performance or other problems to be expected when setting non standard values like for example 250 instead of 256 or 500 instead of 512.. except obviously that lower buffer sizes require faster CPU speeds.

Not long ago in the comment section under one of Kenny's videos a user asked about that (i doubt i'll be able to find it). Kenny consulted the devs and responded that it doesn't matter.

[Phazma]

Thanks for the answer. This might give Reaper an advantage, if for example a system can handle around 300ms the user could set it to something like 350ms and have lower latency than at 512ms while still not overloading the system as with 256ms. In that case I find it bizarre that other DAWs force 2^x values onto the user istead of simply giving a continuous slider or similar.

[Buy One]

Found that exchange

Originally Posted by adrienteixeira5590

I always wondered why reaper doesn't have set block sizes. Like a drop down with 32, 64, 128, 256, 512, and 1024 etc. is there a benefit to having different block sizes? Like I don't, 55? Also, is there an easier way to change block size than having to go to the preferences?

Originally Posted by Kenny

That's a good question. I'll ask and get back to you. Thanks.

....

From the man - Some devices have odd block size preferences - there’s no real benefit to powers of two anyway