|
|
|
02-03-2012, 08:43 PM
|
#1
|
Human being with feelings
Join Date: Jan 2012
Location: Sydney
Posts: 59
|
BUG? Reset CC on stop/play or Loop
There is an option in Preferences | Audio | Midi Devices
whereby "On stop/play" you can tick a box to "reset CC" (Continuous Controller).
I unticked this box but still have a reset MIDI controller message generated at the start of every loop. Considering SPP sends a stop & start each loop iteration, this may be the above option not working. I have created a video illustrating the bug and reported it.
http://forum.cockos.com/project.php?issueid=3924
Can someone please reproduce this and tick the box in that thread?
__________________
http://DJsquiggle.com
Traktor controlled by VirtualMidiController (translating QWERTY into MIDI)
and three Korg NanoKontrols. Automated by a synchronised, looping Reaper.
Last edited by sqgl; 03-15-2012 at 07:09 PM.
|
|
|
02-11-2012, 09:32 AM
|
#2
|
Human being with feelings
Join Date: Jan 2012
Location: Sydney
Posts: 59
|
I've just had the same thing happen with non reset values. See the thread I mentioned.
EDIT - "tracker issue" actually, not "thread". Please limit any discussion there.
__________________
http://DJsquiggle.com
Traktor controlled by VirtualMidiController (translating QWERTY into MIDI)
and three Korg NanoKontrols. Automated by a synchronised, looping Reaper.
Last edited by sqgl; 03-02-2012 at 07:12 AM.
|
|
|
02-13-2012, 01:28 PM
|
#3
|
Human being with feelings
Join Date: May 2011
Posts: 14
|
I am seeing the same or similar behavior (in 4.151). When playing a looped midi track, if I use a controller to send CC's, the CC I sent on the current loop will sometimes be reset to 0 on the start of the next loop. It does not occur every time though.
Dan
|
|
|
02-14-2012, 07:08 AM
|
#4
|
Human being with feelings
Join Date: May 2011
Posts: 14
|
It looks like this was supposed to be fixed in 4.11 but I'm still seeing it in 4.151:
v4.11 - November 12 2011
+ [4.111 - November 13 2011] OSX64/Win64: stability fix
+ MIDI: fixed sending of excess pitch/note/cc resets on loop
Dan
|
|
|
03-02-2012, 07:39 AM
|
#5
|
Human being with feelings
Join Date: Jan 2012
Location: Sydney
Posts: 59
|
This came up in another thread called Does reaper send all notes off when relocating the play cursor in a loop? where I posted the following animated GIF.
A developer, responded, the gist of which is reproduced below. This is the place for discussion rather than me further hijacking that other thread (or adding confusion to the bug tracker post).
Quote:
Originally Posted by gofer
Confirming that Reaper resets CC when a timeline loop repeats, even if "Reset CC on stop/play" is disabled in the prefs.
To be fair it should be mentioned that a loop repeat is not stop/play. Actually I have a hunch this is planned behavior and not a bug although it's outcome is understandably not good in some situations (similar to the reset messages at stop/play themselves which would need a rethink as well and also the item based search-back for the last sent CC which totally needs to work track-wide across items).
I suppose it would be wise to open this again as a feature request (for an option to disable the loop CC reset altogether and maybe for a way to define our own reset values).
|
In addition to my bug tracker post? Won't others consider that to be a double posting?
Quote:
Originally Posted by gofer
I am trying to think of situations where this behavior is annoying to back up the urgency of such a request. It doesn't seem to bother many people (myself I didn't even notice it up to now).
One situation is when you intend to play an instrument live (or record) over a loop of pre-recorded CC values if the pre-recorded item starts later than the left loop edge or has no CC event to fall back to at it's start.
Are there more situations?
|
"Fall back to"? Sometimes it actually uses the last known value in the loop and inserts it at the start of the loop (ie not an actual reset). This new "initial" value sometimes gets "sticky" ie you cannot delete it and is described in the bug tracker report mentioned earlier.
Quote:
Originally Posted by gofer
Are there more situations?
|
Playing an instrument through delay and you change the feedback via a continuous controller. Every loop restart would set feedback to zero.
Last edited by sqgl; 03-02-2012 at 07:56 AM.
|
|
|
03-02-2012, 08:18 AM
|
#6
|
-blänk-
Join Date: Jun 2008
Posts: 11,359
|
The only thing I can develop is bad habits . I'm totally no dev, sqgl, just a mere user blessed with some moderation keys here in the forum.
With "fall back to" I meant that if you have a CC event at a point before or at the loop start time Reaper will reset to that value.
Like this situation in the upper pic:
The lower pic shows a situation I personally hate about Reaper's MIDI. It doesn't trace back across items. I reckon it's sort of a shameless plug here, but I just can't resist to mention it wherever it somehow fits
Trying to recreate the sticky reset values, but don't yet succeed.
|
|
|
03-02-2012, 11:47 AM
|
#7
|
Human being with feelings
Join Date: Sep 2011
Location: The Netherlands
Posts: 6
|
Also have this problem, using latest version of Reaper.
|
|
|
03-02-2012, 07:35 PM
|
#8
|
Human being with feelings
Join Date: Apr 2011
Location: Canada
Posts: 454
|
Quote:
Originally Posted by gofer
The only thing I can develop is bad habits . I'm totally no dev, sqgl, just a mere user blessed with some moderation keys here in the forum.
With "fall back to" I meant that if you have a CC event at a point before or at the loop start time Reaper will reset to that value.
Like this situation in the upper pic:
The lower pic shows a situation I personally hate about Reaper's MIDI. It doesn't trace back across items. I reckon it's sort of a shameless plug here, but I just can't resist to mention it wherever it somehow fits
Trying to recreate the sticky reset values, but don't yet succeed.
|
Agree fully with you that Reaper's MIDI should trace back across items. That's something any sequencer/DAW should do in 2012. On my (very) old ATARI sequencer, they called the option "Chase Controllers" and you could choose which controller to chase. It worked perfectly from anywhere in the sequence... in 1990
|
|
|
03-06-2012, 11:30 AM
|
#9
|
Human being with feelings
Join Date: May 2011
Posts: 14
|
I'm glad this is getting noticed by others. I'll give an example where this behavior is annoying and causing headaches for me. Using a VSTi, I've midi-learned many of the synths parameters to the knobs and faders on my midi controller (ADSR, filter cutoff, resonance, envelope amount, etc.). Sometimes it's just easier to dial in a patch using knobs and faders than it is to do it with a mouse. Anyway, I'll set up a midi riff and set loop points to let it repeat indefinitely when playing. Then I'll go to work adjusting the synth parameters with the controller to get things sounding just right. However, sometimes (not every loop) the last adjusted parameter will jump to 0. If filter cutoff jumps to 0, usually the sound goes away. I haven't noticed the jumping to a random value behavior, but if it is jumping back to the last set value I probably am not noticing. A work around is to create a midi clip with looping checked and drag it out for many measures so that play never needs to repeat. Still, when I tried this I think one or some of the CC's still reset even though I have the option to reset CC's on start/stop disabled. I'll have to check that.
Dan
|
|
|
03-14-2012, 04:11 AM
|
#10
|
Human being with feelings
Join Date: Sep 2011
Posts: 14
|
Me Too
When I have midi items with vol and exp cc in them
The Vol and exp CC's change to zero or maximum unpredictably when the item ends or loops or I back up to the beginning. I turned off the "reset cc on stop/play" to no effect
Both my OSX and WinXP installs have always done this to me - I keep telling myself NOT to enter ANY VOL or EXP cc data EVER - pretty inconvenient!
It's messing up my mix!
^^ after reading the above ^^
My expectation is that when the play head is moved to a point in time, Reaper should set the cc's to the value they would be if it had arrived there during normal play. Or leave them the hell alone! And it should do this in every and all situations unless I tell it different!
It's messing up my mix!
|
|
|
03-14-2012, 04:57 PM
|
#11
|
Human being with feelings
Join Date: Sep 2011
Posts: 14
|
Shh!
( Psst! gluing all midi items together is a workaround! But don't tell Cockos, I still want them to fix it! )
|
|
|
03-14-2012, 05:03 PM
|
#12
|
Human being with feelings
Join Date: Jun 2009
Location: Croatia
Posts: 24,790
|
Quote:
Originally Posted by chucky5p
It worked perfectly from anywhere in the sequence... in 1990
|
In 1990! WAKE UP CALL to Reaper devs!!!
|
|
|
03-15-2012, 12:00 AM
|
#13
|
Human being with feelings
Join Date: Jan 2012
Location: Sydney
Posts: 59
|
Quote:
Originally Posted by ball2000
( Psst! gluing all midi items together is a workaround! But don't tell Cockos, I still want them to fix it! )
|
That does not help the situation shown in my earlier post's animated GIF.
|
|
|
03-15-2012, 04:03 AM
|
#14
|
Human being with feelings
Join Date: Apr 2011
Location: Canada
Posts: 454
|
Quote:
Originally Posted by EvilDragon
In 1990! WAKE UP CALL to Reaper devs!!!
|
Yep, that was in 1990. FWIW, the sequencer's name was Master Track Pro. Beside having a very good "chase controller" option, it had many other features that are still not available in Reaper, such as "quantize while recording", a sysEx librarian, etc. It's been so long that I don't recall exactly why I chose this sequencer over its competitors back then (Cubase and Notator were also available for the Atari ST). For those who are curious about this program, check out this link: (you can also download the program, it's now freeware and works fine on a PC with an Atari emulator)
http://tamw.atari-users.net/mtpro.htm
Note: the screen cap I posted in my previous post is from the Windows version that came out in 2003 (it was easier to capture) but the 1990 Atari ST version had the exact same "Chase Controller" option.
|
|
|
03-15-2012, 10:07 AM
|
#15
|
Human being with feelings
Join Date: Apr 2009
Posts: 16,031
|
I thought it was me
|
|
|
03-16-2012, 06:24 AM
|
#16
|
Human being with feelings
Join Date: Sep 2011
Posts: 14
|
Quote:
Originally Posted by sqgl
|
oh right, that's annoying!
What you could try is creating empty items before and after the loop and gluing them so your loop never crosses item bounds, wouldn't that fix it?
|
|
|
04-05-2012, 09:14 AM
|
#17
|
Human being with feelings
Join Date: Aug 2011
Posts: 123
|
This is really making me crazy. I decided to try Studio One because of this and it works perfect for midi and automation. Unfortunately it is missing stuff like track templates and editing modifiers for midi editing.
So I'm stuck with re-entering all of my tracks by hand every time in studio one and being able to record, or having my Synth reset constantly in reaper.
|
|
|
04-05-2012, 11:51 AM
|
#18
|
Human being with feelings
Join Date: Nov 2006
Posts: 2,533
|
Quote:
Originally Posted by chucky5p
Agree fully with you that
Reaper's MIDI should trace back across items.
That's something any sequencer/DAW should do
in 2012. On my (very) old ATARI sequencer,
they called the option "Chase Controllers"
and you could choose which controller to chase.
It worked perfectly from anywhere in the sequence...
in 1990 ///
|
+1 to this. Track Media Item count should not
affect this. It should always chase the last
value on the Track, regardless of what Media
Item that value is in.
|
|
|
04-05-2012, 10:49 PM
|
#19
|
Human being with feelings
Join Date: Apr 2009
Posts: 16,031
|
Ok, this has got me all confused now.
My controller is dropping messages in (117, 118, some others) when I'm recording. Is this what we are talking about? It's not the same as "midi learning/actions" where you set up stop, loop, record, etc. But those cc's are coming through.
So before I bother with anything further, this is what we are talking about? I thought I knew what this thread was about but now I just feel lost.
|
|
|
04-05-2012, 11:53 PM
|
#20
|
Human being with feelings
Join Date: May 2010
Location: Norway
Posts: 7,318
|
Quote:
Originally Posted by gofer
With "fall back to" I meant that if you have a CC event at a point before or at the loop start time Reaper will reset to that value.
|
+1 for fall back to across items
__________________
Reaper x64, win 11
Composer, text-writer, producer
Bandcamp
|
|
|
04-06-2012, 07:46 AM
|
#21
|
Human being with feelings
Join Date: Jan 2012
Location: Sydney
Posts: 59
|
Quote:
Originally Posted by chrisharbin
My controller is dropping messages in (117, 118, some others) when I'm recording. Is this what we are talking about?
|
This thread is about Reaper adding (not dropping) messages. You may need to start a new thread to sort it out.
|
|
|
04-17-2012, 05:04 AM
|
#22
|
Human being with feelings
Join Date: Sep 2010
Posts: 120
|
Voted able to reproduce.
I've been getting the same behaviour here too. =(
It happens for me even though I've not recorded any CC changes, only tweaked knobs on a controller.
Developers - This is RUINING REAPER ENTIRELY for a small number of people.
Surely that is as important as a small issue that is causing minor grievance to a great number of people.
|
|
|
04-17-2012, 07:46 AM
|
#23
|
Human being with feelings
Join Date: Sep 2010
Posts: 120
|
Okay. Some, I think, new information.
I don't reckon it is tied in with just recorded CC data. I don't use any recorded CC data and I can reproduce what looks like the same bug.
Using a MIDI controller to control a VST parameters via CC (not via Reaper MIDI learn) I can recreate this bug thusly...
-Create a track and add a VST that has parameters that respond to CC
-Create an item with one midi note
-Set up a loop and press play
-Send CC data from MIDI controller to move parameter on VST making sure to move the controller when the playhead passes the note-on and the note-off!
-Jumping value occurs now on every end/beginning of loop
-Restart program to fix
Can anybody else confirm this?
Last edited by chopstickkk; 04-17-2012 at 10:30 AM.
|
|
|
04-22-2012, 10:49 PM
|
#25
|
Human being with feelings
Join Date: Apr 2012
Posts: 1
|
I can confirm this is still present in reaper 4.21. It basically makes CC jamming with my controller useless. Please please please fix this one!!
Thanks Cockos
|
|
|
04-23-2012, 03:29 AM
|
#26
|
Human being with feelings
Join Date: Aug 2007
Location: Near Cambridge UK and Near Questembert, France
Posts: 22,754
|
skimmed the thread havent come across this so far but I take it there IS a bug report in already?
|
|
|
04-23-2012, 05:09 AM
|
#27
|
Human being with feelings
Join Date: Sep 2010
Posts: 120
|
Quote:
Originally Posted by ivansc
skimmed the thread havent come across this so far but I take it there IS a bug report in already?
|
http://forum.cockos.com/project.php?issueid=3924
Vote reproducible if you can.
|
|
|
04-23-2012, 08:51 AM
|
#28
|
Human being with feelings
Join Date: Jul 2010
Location: Online
Posts: 4,896
|
I'm getting a hopping fader with my x session pro too.
Rather annoying
__________________
it aint worth a bop,if it dont got that pop
|
|
|
04-23-2012, 08:56 AM
|
#29
|
Human being with feelings
Join Date: Sep 2010
Location: Hertfordshire, England
Posts: 1,965
|
Hey Gazza,
What are you doing out of your coffin in daylight?
|
|
|
04-30-2012, 01:43 PM
|
#30
|
Human being with feelings
Join Date: Sep 2010
Posts: 120
|
Bumpgif
|
|
|
07-12-2012, 01:08 PM
|
#31
|
Human being with feelings
Join Date: Sep 2011
Location: The Netherlands
Posts: 6
|
Bump..
Is this actually going to get fixed?
Why is there no reply from a dev confirming this, or telling us when they are able to take a look and fix it.
Am starting to think I bought the wrong host to replace Cubase for MIDI, cheap DAW apparently means: poor support.
I have a EMU Xboard49 controlling hardware- and softwaresynthesizers, i have deselected reset CC at the MIDI preference screen but am getting so fed up with CC reset after using a knob on the keyboard. Why.. why...why are we experiencing this??? ..Come on..
Cheers.
Last edited by xgmode; 07-12-2012 at 02:56 PM.
|
|
|
07-13-2012, 02:20 PM
|
#32
|
Human being with feelings
Join Date: Sep 2010
Posts: 120
|
Quote:
Originally Posted by xgmode
...for MIDI, cheap DAW apparently means: poor support.
|
+1. Unfortunately =(
|
|
|
07-13-2012, 07:19 PM
|
#33
|
Human being with feelings
Join Date: Sep 2011
Location: The Netherlands
Posts: 6
|
Sorry for the harsh tone earlier, it would mean a lot to us if this can be fixed.
|
|
|
07-13-2012, 07:34 PM
|
#34
|
Human being with feelings
Join Date: Feb 2012
Posts: 1,972
|
Quote:
Originally Posted by xgmode
cheap DAW apparently means: poor support.
|
Cmoon, i guess you didn't face Ableton or Logic support... Where else on earth the devs are talking to users on forums?
|
|
|
07-14-2012, 03:09 AM
|
#35
|
Human being with feelings
Join Date: Aug 2007
Location: Near Cambridge UK and Near Questembert, France
Posts: 22,754
|
Yeah but fixing always beats talking to us about.
Not that the devs are generally lax in that area, but there are a lot of long term irritants like this still hanging around since who knows when.
Maybe it is another one of those that would take a disproportionately large amount of coding and dev time to fix.... like many of the other MIDI requests, apparently.
|
|
|
07-14-2012, 04:42 AM
|
#36
|
Human being with feelings
Join Date: Jun 2009
Location: Croatia
Posts: 24,790
|
Quote:
Originally Posted by ivansc
Maybe it is another one of those that would take a disproportionately large amount of coding and dev time to fix.... like many of the other MIDI requests, apparently.
|
I'm pretty sure it isn't.
if loopEnd_reached then dontSendCCresetForCryingOutLoud
|
|
|
07-26-2012, 03:35 AM
|
#37
|
Human being with feelings
Join Date: Sep 2010
Posts: 120
|
Animabump...
Just to re-interate this happens only for MIDI CC not for Reaper MIDI learned parameters.
i.e. the volume on the V-Station responds to MIDI CC #7 directly but the threshold on the compressor was MIDI Learned.
|
|
|
05-26-2013, 05:54 AM
|
#38
|
Human being with feelings
Join Date: May 2010
Posts: 90
|
I can replicate this very easily .
Using Maschine controller and a midi keyboard controller.
After moving a vst parameter either using the midi contoller the midi cc is resetting.I do not understand why it does it sometimes but not all the time.
THanks chopstikkk though. I had not realised that you could work round it by using reaper midi learn... Its a pain in the ass though as i have several templates set up that i use on maschine to saved me having to go in and learn everything.
|
|
|
05-26-2013, 12:31 PM
|
#39
|
Human being with feelings
Join Date: Sep 2010
Posts: 120
|
Quote:
Originally Posted by deailes
...Its a pain in the ass...
|
Suuuuure is.
deailes don't forget to vote on this page if you haven't already...
http://forum.cockos.com/project.php?issueid=3924
I don't think it'll make much difference.
Like most MIDI users I've moved to a different software. REAPER is a glorified VST rack for me now.
Sigh...
|
|
|
02-16-2015, 03:49 PM
|
#40
|
Human being with feelings
Join Date: Mar 2012
Location: Occitanie
Posts: 4
|
How can this NOT be fixed
I am reading all this in disbelief. I fetched up here looking for a solution to a silly bit of software beaviour: CC values being set to unrequired values in various Stop, Loop and Pause scenarios.
That this is still an issue after >2 years and so many versions is amazing. Don't devs read any of this?
This is a game changer. After a couple of years getting into Reaper after >20 years of Cubase, I have lost 90% of my belief in the product.
If I had this problem in a mixing desk, I would bin it.
Anyone know of a DAW that can manage MIDI properly? Please don't tell me Cubase!
|
|
|
Thread Tools |
|
Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -7. The time now is 04:24 AM.
|