2 Reaper problems (probably operator error)

[K8ch]

Hi all,


There are 2 different problems I'm having, re: Reaper.
They're happening on 2 different computers.


Issue #!:

I believe I may have reduced the buffer size (or something like that) to allow me to hear less latency, as I record.
Well, maybe I didn't "undo" that properly because now, when I hit "play", it will play for a moment, then it sputters and freezes up.

What's going on??
I put the buffer back to 512, but it still crashes the same way.
(There are only 6 MIDI tracks. 2 effect sends and an arpeggiator...so, it's shouldn't b a CPU strain)




Issue #2:

I have Reaper on another machine...and when I hit "play"...it doesn't do anything.
It's a blank MIDI track, and the cursor doesn't even move.



Suggestions are welcome!
Thanks, in advance, for your advice!


Peace,

Keith
https://www.reverbnation.com/keithhaydon

[grinder]

Only thing I can suggest is
Do a reinstall of Reaper (over the top or uninstall the old and reinstall the new)
If that does not change anything uninstall and install an earlier version.
If you are on windows ten has it updated recently?

Grinder

[K8ch]

Hi Grinder....


Well, I re-installed an earlier version and still, the cursor doesn't move, when I hit play.


I haven't used my music computer (having issue #1) in a couple of days.
I will try a r-install on that, too, of course as soon as I can.




Thanks!

Keith

[serr]

Reaper just sitting there unresponsive/frozen after hitting play (with play lit up in the transport but nothing moving) is usually a telltale that it's not talking to the selected audio interface. Investigate there.

[grinder]

you have the right man on the job now Keith!

Grinder

[K8ch]

Thanks for the suggestion however there is no interface attached to this computer.

[serr]

Originally Posted by K8ch

Thanks for the suggestion however there is no interface attached to this computer.

You don't even have a built-in interface to select? Most logic boards have at least some cursory audio interface built-in. I wasn't meaning an externally connected interface necessarily BTW. Whatever interface you connect to to use for sound output. But if you didn't have anything connected... that would be the problem.

The first quick thing I would try (assuming you DO have an interface of some kind) is to go to Reaper Preferences/Audio/Device and select it again from the dropdown (even though it might still look selected). The apply button will un-gray when you select it again. Click it. This forces a request to the interface. Maybe some other app sent a sample rate request at a different rate, for just one possible example. Selecting it again gets you connected again in such scenarios.

[K8ch]

YAY!


Thanks, Serr!!

Okay...that issue is fixed, now!
Thank you!!!

Now, if I can just get Reaper to stop choking/freezing (on my studio computer), I can actually get back to making music!



Peace,

Keith

[serr]

Aha! Cool.

You probably have some other app sending a request to the audio interface. Maybe a different sample rate. Like an internet browser or media player. Any app that sends audio. That's a common scenario.

If you have other performance issues too...
Start by looking at your CPU and ram use when something chokes.