|
|
|
09-12-2014, 07:42 PM
|
#1
|
Human being with feelings
Join Date: Oct 2013
Posts: 93
|
v4.73rc1 - September 12 2014
v4.73rc1 - September 12 2014
+ ReaVerb: improved handling of certain low-level mono signals [t=146070]
|
|
|
09-13-2014, 07:06 AM
|
#2
|
Human being with feelings
Join Date: Oct 2013
Location: Argentina
Posts: 1,303
|
Hi Justin!
I´ve been noticing some odd behaviour with ReaControlMIDI´s extended 14-bit support. I copied various instances across a project with RC´s new 14-bit pairs, but after working in the project for some time - maybe even after one or two days in some cases -, there seems to be a regression and ReaControl shows the CCs in the old way. This is the case with a simple project I attach : originally it showed CCs 20 & 21 as 14-bit pairs in non-raw mode, but now it can be seen that they are shown in the old MSB fashion. The problem is that I still cannot give a recipe to reproduce this; I haven´t been able yet to see a pattern for this behaviour. Anyway, I think you must be informed about it...
|
|
|
09-13-2014, 07:30 AM
|
#3
|
Human being with feelings
Join Date: Jun 2009
Location: Croatia
Posts: 24,790
|
Yeah, after all that discussion about 14-bit list of CCs in RCM, no changes in naming of them yet? Guys, please do that. I want a clearly named CC list with numbers only (no GM-specified names at all) in RCM in non-raw mode.
|
|
|
09-13-2014, 08:38 AM
|
#4
|
Mortal
Join Date: Dec 2008
Location: France
Posts: 1,969
|
Quote:
Originally Posted by Soli Deo Gloria
Hi Justin!
I´ve been noticing some odd behaviour with ReaControlMIDI´s extended 14-bit support. I copied various instances across a project with RC´s new 14-bit pairs, but after working in the project for some time - maybe even after one or two days in some cases -, there seems to be a regression and ReaControl shows the CCs in the old way. This is the case with a simple project I attach : originally it showed CCs 20 & 21 as 14-bit pairs in non-raw mode, but now it can be seen that they are shown in the old MSB fashion. The problem is that I still cannot give a recipe to reproduce this; I haven´t been able yet to see a pattern for this behaviour. Anyway, I think you must be informed about it...
|
hum.. can't duplicate. do you have more accurate reproduction steps?
also are your sure you did not do one of the following things?
- if you save this project in 4.72 or any version < v4.73pre5, CCs 16 to 31 will switch back to 7-bit
- if you load an "old" project (i.e. saved before v4.73pre5) that include those CCs, they will remain 7-bit (no to break users' projects when upgrading)
- if you load "old" presets which use the said CCs, they will remain 7-bit too
|
|
|
09-13-2014, 08:59 AM
|
#5
|
Human being with feelings
Join Date: Jan 2010
Posts: 2,686
|
Quote:
Originally Posted by EvilDragon
Yeah, after all that discussion about 14-bit list of CCs in RCM, no changes in naming of them yet? Guys, please do that. I want a clearly named CC list with numbers only (no GM-specified names at all) in RCM in non-raw mode.
|
it would be cool
|
|
|
09-13-2014, 09:17 AM
|
#6
|
Human being with feelings
Join Date: Oct 2013
Location: Argentina
Posts: 1,303
|
Quote:
Originally Posted by Jeffos
also are your sure you did not do one of the following things?
- if you save this project in 4.72 or any version < v4.73pre5, CCs 16 to 31 will switch back to 7-bit
- if you load an "old" project (i.e. saved before v4.73pre5) that include those CCs, they will remain 7-bit (no to break users' projects when upgrading)
- if you load "old" presets which use the said CCs, they will remain 7-bit too
|
Hi Jeffos, thanks for the reply!
I won´t be able to check again all of this until Monday, but I´ll do so that day. What seemed strange every time it happened, though, is that the instances of ReaControl were showing the new 14-bit pairs and then they seemed to change spontaneously at one point. I´ll have an eye on this to see if I can confirm wheter is it my mistake or a potential bug.
|
|
|
09-14-2014, 05:41 AM
|
#7
|
Mortal
Join Date: Dec 2008
Location: France
Posts: 1,969
|
ok, got it, thanks for the report Soli Deo Gloria!
|
|
|
09-14-2014, 12:46 PM
|
#8
|
Human being with feelings
Join Date: Nov 2011
Posts: 3,409
|
Hand-scroll is still wonky when the window is stretched over two monitors... (since ~4.62) (Win 8)
If you maxmize the reaper window on one screen, and the Arrange View mouse modifier for middle drag is set to "Hand Scroll", it works great, and I realized that there is a feature where if the hand is dragged all the way to one side or the other, it keeps scrolling, which is handy.
Unfortunately, that algorithm is apparently broken when the window is larger than one monitor. In my case, I have two 1280x1024 monitors side-by-side with the Reaper window across both. If I hand drag on the left monitor, the scroll never stops, and keeps going on its own until the button is released. But if, while doing that, I drag over to the monitor on the right side, the scrolling stops and just stays with the hand, as expected.
I figured this was an easy thing so i didn't bother with a bug report, but I suppose I should. Here it is: http://forums.cockos.com/project.php?issueid=5342
Mare at these links:
http://forums.cockos.com/showpost.ph...17&postcount=4
http://forums.cockos.com/showpost.ph...5&postcount=79
http://forums.cockos.com/showpost.ph...4&postcount=47
|
|
|
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 05:35 AM.
|