Go Back   Cockos Incorporated Forums > REAPER Forums > REAPER Bug Reports

Reply
 
Thread Tools Display Modes
Old 03-30-2021, 09:09 AM   #1
doc_jochim
Human being with feelings
 
Join Date: Mar 2021
Posts: 15
Default ReaTune crashes Reaper while setting certain parameters (FIXED)

My System:
New Win10pro64 desktop-PC
Intel i5-10500
Samsung m.2-SSD
16GB DDR4 RAM
Behringer UMC1820 audio-interface using 128Bit sample rate and the latest 5.0 driver from Behringer website
reaper 6.25 / 6.26 64bit

The first time I tested ReaTune as an effect I immediately got Reaper crashing completely doing just a few clicks. Reproducible:

What I did:

open Reaper
create an empty track for Input 1
add ReaTune as FX to the track
arm the track
monitoring ON
open ReaTune
check 'automatic pitch correction' and set a key (e.g. C major)

Up to this point, everything still works and you can see and hear how ReaTune works and pitches the input signal matching the chosen key.

But if I now select any value for 'maximum pitch', I only get some short scratchy sounds like digital noise and Reaper immediately crashes. Program is closed and settings gone....

This also happens when I simply playback a recorded test sweep instead of giving a live signal of the armed channel via the mic.


To check if the system or any driver can be blamed for the behaviour, I installed Reaper on another computer. Using just the internal soundcard and a headset.
But also here there is the same crash problem doing the same procedure.

Windows' event log is showing similar Application-errors on both systems (see attachment).

Can anyone of the reaper-team reproduce this? Is this an error of Reaper? Or am I doing anything wrong?

Yesterday I additionally tried to install reaper 6.26 - but it is showing the same behaviour :-(

What do the settings max.pitch and min.pitch do? Neither in the current reaper manual nor in any tutorial I could find information about these settings.


Thanks for your help


André
Attached Files
File Type: zip eventlog application error.zip (12.0 KB, 8 views)

Last edited by doc_jochim; 03-30-2021 at 01:38 PM.
doc_jochim is offline   Reply With Quote
Old 03-30-2021, 09:15 AM   #2
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 11,620
Default

Fixing, thanks for the report!
schwa is offline   Reply With Quote
Old 03-30-2021, 09:43 AM   #3
doc_jochim
Human being with feelings
 
Join Date: Mar 2021
Posts: 15
Default

Quote:
Originally Posted by schwa View Post
Fixing, thanks for the report!
Does that mean that you were able to reproduce the described behaviour and the error wasn't located in front of the monitor?

Where do I find a description of what max.pitch and min.pitch are supposed to do?

André

PS: sorry for my bad english, but school is already a long time ago...
doc_jochim is offline   Reply With Quote
Old 03-30-2021, 09:49 AM   #4
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 11,620
Default

Yes, this is a REAPER bug that occurs if the UI is open and the input pitch is out of range of the user maximum setting. Those settings are meant to clamp the corrected pitch to a minimum and/or maximum value.
schwa is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 09:59 AM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, vBulletin Solutions Inc.