|
|
|
02-04-2012 05:14 AM | |||
|
|||
Have found a workaround.
You can simply filter out the zero and 127 values! To do so I use a free Midi mapping utility called MidiOx. Yes, the collateral damage is that you can never deliberately turn your controller completely down (zero) or completely up (127) but 1 and 126 will be good enough (barely audiblly different from 0 and 127). So Reaper output goes via this instead of directly into my instrument. See attached .txm settings file that you load via Options | Data Mapping |
02-11-2012 09:36 AM | |||
|
|||
The workaround is only good if the values are zero or 127 but I have just found it can be *any* value.
If you loop (four bars say) and record a MIDI CC sweep in bar two, Reaper inserts a value at the very start of the loop (bar zero, say). That value will be identical to either the first one (plus or minus one) in that sweep from bar two or the last one (plus or minus one). That's fine.. If you are in "RECORD: MIDI replace"-mode and let it keep looping, all the CC contents of the loop (bar two in our example) are deleted (as expected) except for that one value at the loop-start which lingers. Although this can be annoying from my perspective it is understandable but the rationale of the following behaviour is hard to understand... Even if you go into the editor, select-all then delete all the items on that track and hit record (this time without touching any CC) that phantom value reappears. Surely this is not meant to happen? |
02-11-2012 09:38 AM | |||
|
|||
Quote:
|
02-11-2012 10:49 PM | |||
|
|||
Quote:
Seems like I am just having a conversation with myself in this thread. Well at least it serves as notes to myself and for future others that may encounter this phenomenom. |
02-11-2012 11:32 PM | |||
|
|||
Quote:
|
02-13-2012 01:24 PM | ||
|
||
I have experienced the same behavior, at least the unpredictable resets when looping. I haven't noticed CC's getting reset to values other than 0though.
|
02-14-2012 08:06 AM | |||
|
|||
This bug keeps looking worse and worse.
Quote:
Quote:
This is because MIDI is so slow that, for instance, a fader sweep down will not generate all values, eg instead of 12,11,10,9,8,7,6,5,4,3,2,1,0 you may get 12,6,0 or even (in my experience) 12,0. You need to turn that zero into a one before it gets into Reaper. Any zero (or 127) coming out of Reaper will definitely be the phantom value this bug report talks about and you can safely discard it, knowing that a near-enough value (one or 126) is "hot on its heels". |
02-18-2012 06:58 AM | |||
|
|||
The first time I've recognized this behavious was when I've used CC7 to control the volume of my Kontakt-instruments. It was kinda strange when the Volume Knob of the Instruments sometimes jumped to 12db without a given reason.
I'm looking for a solution for the problem right know. Resetting CC7 and CC10 can be avoided by using the Volume-Faders in the MCP for MIDI-Control, but things are getting pretty annoying when other CCs keep resetting themself whenever the loop starts the next round. So, whenever I'm playing around with a knob it's going the be only the last changed CC that'll be reseted to 0 (or 127 and 64 when using CC7 or CC10). There's a small chance that there won't be any reset, I guess it's random. There's no CC-resetting when there's no Midi-Item in the Track. Once there is recorded Midi inside the Loop, the CC-Reset might happen. The position of the loop doesn't matter. Also, I'm already routing the Midi-Data trough Midi-OX to Reaper. Can't be the controller itself that causes the problem. Did ya found anything yet? Drives me crazy to deal with bugs like that when you need something like a bullet-proof setup for loop-recording. |
02-18-2012 02:17 PM | |||
|
|||
Fleeshch have you tried my MidiOx workaround that I mentioned in the post just before yours?
|
02-18-2012 02:46 PM | |||
|
|||
Already tried that. The range of the CC doesn't matter at all, the reset pehnomena also happens when I'm changing CC values between 1 and 126.
It looks like that a reset only happens whenever I'm changing a CC value while Reaper is playing some MIDI-notes of a MIDI-item in the track. Twisting my nobs without something playing in the background won't cause a reset. Did the MidiOX workaround actually solve your problem? EDIT: Found out that there wasn't such a problem in Reaper 4.00 . I'm going to use this version until the resetting bug is solved. |
02-19-2012 04:12 AM | |||||
|
|||||
Quote:
Quote:
Quote:
Quote:
Quote:
EDIT: Be reverting to 4.0 you may have another problem because the changlog for v4.02 says "MIDI: fixed stuck notes when looping". So I wonder if the reset problem happens in 4.02. I wish the change log also listed bugs that are *introduced* (not just the ones fixed) |
02-19-2012 04:51 AM | |||
|
|||
Quote:
I didn't encounter any problems with stuck notes, whether I'm just playing live with my keyboard or recording notes while looping. Maybe it is because of the fact that I've switched to the simple "Record: Input" option instead of using Reapers special MIDI recording abilities (MIDI replace, ovderdub, etc.). Every take generates a new MIDI item rather than a new take, when I'm done recording my stuff I usually just glue everything together. There was a member in this board that mentioned a fix in v4.111 regarding our little problem: Quote:
|
03-02-2012 07:47 AM | |||
|
|||
I've just been advised to encourage any further discussion to be done at the original thread rather than here. I've muddied this ticket enough as it is.
|
05-23-2012 06:00 PM | ||
|
||
I'm new to computer music, and I got my first midi controller a few days ago. My use of Reaper has been fairly limited, but the first thing I wanted to do was play a loop and edit the controls of some vsti's to test it out, and I encountered this problem within 5 minutes of setting those capabilities up. I think this issue is pretty high priority- I hardly had to dig deep in any way. Please fix this!
|
This petition for a change to Fixed was rejected
04-17-2016 11:04 AM
|
||
|
||
FIXED (5.18)
|
Issue Tools |
---|
Subscribe to this issue |