Old 06-11-2016, 10:12 AM   #1
vitalker
Human being with feelings
 
vitalker's Avatar
 
Join Date: Dec 2012
Posts: 13,333
Default v5.21rc1 - June 11 2016

v5.21rc1 - June 11 2016
# MIDI editor: fix some visibility/editability issues when switching active take in the arrange view [p=1692096]
# MIDI editor: fixed edit/inserting new event in the range 0xB? [0x78,0x7F] [p=1692017]
vitalker is online now   Reply With Quote
Old 06-11-2016, 02:53 PM   #2
noise_construct
Human being with feelings
 
Join Date: Nov 2015
Posts: 1,566
Default

1. Double-clicking on a MIDI item in arrangement view doesn't open the item fully expanded in the MIDI Editor, double-clicking again does it.

2. Selecting grid or note values from the dropdown menus causes the editor to lose focus.

3. Left and right edge of MIDI notes aren't drawn in the MIDI item peaks when the notes are adjacent to each other.

4. Left and right edge of MIDI notes are drawn in the MIDI Editor at item borders, even if the note extends beyond the border.

5. Note or position preview for multiple notes doesn't work "on the fly", you can't preview any changes without releasing mouse button. Curiously CCs can be previewed like this. There's the note preview option, but it just sends a note-on once for the note under cursor, not for all selected notes and it doesn't "stick" until you release mouse.
noise_construct is offline   Reply With Quote
Old 06-11-2016, 05:15 PM   #3
hamish
Human being with feelings
 
hamish's Avatar
 
Join Date: Sep 2007
Location: The Reflection Free Zone
Posts: 3,026
Default

Quote:
Originally Posted by vitalker View Post
# MIDI editor: fix some visibility/editability issues when switching active take in the arrange view [p=1692096]
Working as expected now, thanks
hamish is offline   Reply With Quote
Old 06-12-2016, 02:19 AM   #4
ELP
Human being with feelings
 
Join Date: Apr 2014
Posts: 943
Default

"fixed edit/inserting new event in the range 0xB? [0x78,0x7F] [p=1692017]"
thank you.

The controller names (120-127) within/from event properties are ok now.

..but the visibility / still disappears after closing the list editor/item and reopen the MIDI item again.

-left side during first inserting/editing etc. pp ok | right side after closing and reopen the same item..


BTW.the same of course if you import MIDI which include controller 120-127 events..
simply not visible/editable from event list view anymore but of course was imported
__________________
I hope you can understand me? Without german beer my written english is always very bad, with beer it becomes unbearable!.
Less is more! To much limited the own creativity.

Last edited by ELP; 06-12-2016 at 02:29 AM.
ELP is offline   Reply With Quote
Old 06-12-2016, 06:29 AM   #5
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 15,749
Default

Quote:
Originally Posted by ELP View Post
..but the visibility / still disappears after closing the list editor/item and reopen the MIDI item again.
I can't reproduce the event disappearing from the list view, even after closing and reopening the MIDI editor. Are there any other steps involved? By any chance is the MIDI filter active?
schwa is offline   Reply With Quote
Old 06-12-2016, 06:30 AM   #6
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 15,749
Default

Quote:
Originally Posted by noise_construct View Post
1. Double-clicking on a MIDI item in arrangement view doesn't open the item fully expanded in the MIDI Editor, double-clicking again does it.

2. Selecting grid or note values from the dropdown menus causes the editor to lose focus.

3. Left and right edge of MIDI notes aren't drawn in the MIDI item peaks when the notes are adjacent to each other.

4. Left and right edge of MIDI notes are drawn in the MIDI Editor at item borders, even if the note extends beyond the border.

5. Note or position preview for multiple notes doesn't work "on the fly", you can't preview any changes without releasing mouse button. Curiously CCs can be previewed like this. There's the note preview option, but it just sends a note-on once for the note under cursor, not for all selected notes and it doesn't "stick" until you release mouse.

There are all valid reports but I don't think any of them is new behavior, so we'd like to wait until after 5.21 is released before addressing these.
schwa is offline   Reply With Quote
Old 06-12-2016, 07:16 AM   #7
noise_construct
Human being with feelings
 
Join Date: Nov 2015
Posts: 1,566
Default

Quote:
Originally Posted by schwa View Post
There are all valid reports but I don't think any of them is new behavior, so we'd like to wait until after 5.21 is released before addressing these.
That's what you said when I reported them for 5.20.
noise_construct is offline   Reply With Quote
Old 06-12-2016, 07:45 AM   #8
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 15,749
Default

:/ Sorry.
schwa is offline   Reply With Quote
Old 06-12-2016, 09:09 AM   #9
noise_construct
Human being with feelings
 
Join Date: Nov 2015
Posts: 1,566
Default

It's alright, just slightly frustrating to report bugs over and over again, and I'm most likely not the only one who's reported them- this forum reporting system is not very efficient from user perspective.

Hope at least some of them get fixed soon. They may sound minor but really cramp fluid workflow.
noise_construct is offline   Reply With Quote
Old 06-12-2016, 11:03 AM   #10
lalo
Human being with feelings
 
Join Date: Jun 2006
Posts: 187
Default

Hi, if set the BPM to 120 everything is fine.
But if i set it to 130, Reapers shows 129.999
if i set 129 it shows 128.998
if 85 it shows 85.01
strange stuff..
lalo is offline   Reply With Quote
Old 06-12-2016, 11:09 AM   #11
ELP
Human being with feelings
 
Join Date: Apr 2014
Posts: 943
Default

"Schwa:I can't reproduce the event disappearing from the list view, even after closing and reopening the MIDI editor. Are there any other steps involved? By any chance is the MIDI filter active?"

hmm
No Schwa, absolute not...

... I just test it once again with an absolute fresh portable 5.21rc1 x64 installed version of REAPER and with one absolute fresh new .x64 *ini to exclude any involved personal setups.....
Controller >119 disappearing after close and reopen(or simply one reopen by click - see licecap') and if you import one MIDI Files which already include such controller they never show within list..


I really do not want to write this
but is there any change that you maybe test one REAPER Version earlier 5.21pre5
or the official release, Schwa?
Within these Versions disappearing is of course not happen.. .. and also the "END" of item is always visible, but not within 5.21 pre5 to rc1...

licecap show you whats happen with an fresh x64 reaper. fresh x86 rc1 version, the same.


Greetings
---

@lalo that´s because you have enable project setting|Force project tempo... occur on whole samples
__________________
I hope you can understand me? Without german beer my written english is always very bad, with beer it becomes unbearable!.
Less is more! To much limited the own creativity.

Last edited by ELP; 06-12-2016 at 12:58 PM.
ELP is offline   Reply With Quote
Old 06-12-2016, 11:27 AM   #12
ELP
Human being with feelings
 
Join Date: Apr 2014
Posts: 943
Default

the difference at the same computer:
5.201
except the wrong names for cc120-127 within/from event properties,
the controller 120-127 events do not disappear-

__________________
I hope you can understand me? Without german beer my written english is always very bad, with beer it becomes unbearable!.
Less is more! To much limited the own creativity.

Last edited by ELP; 06-12-2016 at 11:36 AM.
ELP is offline   Reply With Quote
Old 06-12-2016, 12:00 PM   #13
BogdanS
Human being with feelings
 
Join Date: Aug 2013
Location: Ukraine
Posts: 60
Default

Why does not "lock" (block editable) with the active monitoring of the tracks in TrackList(Midi editor)?
BogdanS is offline   Reply With Quote
Old 06-12-2016, 06:36 PM   #14
hopi
Human being with feelings
 
hopi's Avatar
 
Join Date: Oct 2008
Location: Right Hear
Posts: 15,618
Default

Quote:
Originally Posted by lalo View Post
Hi, if set the BPM to 120 everything is fine.
But if i set it to 130, Reapers shows 129.999
if i set 129 it shows 128.998
if 85 it shows 85.01
strange stuff..
strange... I don't see that happen here... 64 bit version
where do you see that BPM? In the main BPM setting for the TCP or elsewhere?
__________________
...should be fixed for the next build... http://tinyurl.com/cr7o7yl
https://soundcloud.com/hopikiva
hopi is offline   Reply With Quote
Old 06-12-2016, 06:54 PM   #15
Tod
Human being with feelings
 
Tod's Avatar
 
Join Date: Jan 2010
Location: Kalispell
Posts: 14,745
Default

Quote:
Originally Posted by BogdanS View Post
Why does not "lock" (block editable) with the active monitoring of the tracks in TrackList(Midi editor)?
Right click in the track list and check all your settings.

Quote:
Originally Posted by hopi View Post
strange... I don't see that happen here... 64 bit version
where do you see that BPM? In the main BPM setting for the TCP or elsewhere?
I'm not seeing this either, it works fine here.

However, one thing that I do see and it's been this way for a long time, if I have a generator set up for -1.0dB output, Reaper's meters will show -1.1dB. And any metering I put on after reapers initial metering will also show -1.0dB, so Reaper is always showing down .1dB. Not a big deal but thought I'd mention it.
Tod is offline   Reply With Quote
Old 06-12-2016, 06:59 PM   #16
hamish
Human being with feelings
 
hamish's Avatar
 
Join Date: Sep 2007
Location: The Reflection Free Zone
Posts: 3,026
Default

See ELP's comment above. You get that when you set the Project Settings switch 'Force project tempo/time signature changes to occur on whole samples.

Maybe that setting should include a warning?
hamish is offline   Reply With Quote
Old 06-13-2016, 01:41 AM   #17
ELP
Human being with feelings
 
Join Date: Apr 2014
Posts: 943
Default

Independent of the setting and maybe by the fact,
that not really everyone knows or equal aware
would for example 130 BPM never ever result in one exactly 130 BPM.

Simply by the fact, that integer microseconds is the smallest Unit.
Refers to Audio the smallest practical Unit is integer one sample = 1 and not x,yyyyy samples.

and refers to BPM the smallest practical unit at worst consequences/Instance MIDI is microseconds/quarter..

60.000.000 : 130 BPM = 461.538,46153846153846153846153846..... microseconds
Integer= 461.538 microseconds
Possible exactly integer microseconds to BPM steps around 130 BPM
461.537 | 60.000.000 : 461.537 = 130,00041 BPM
461.538 | 60.000.000 : 461.538 = 130,00013 BPM
461.539 | 60.000.000 : 431.539 = 129,99984 BPM
there is simply no exactly 130 BPM

The same of course with all other BPM which 60.000.000 : BPM result
is not exactly integer. (Result without decimals)
125 BPM would be exact 480.000
but 85 BPM would be 705.882,3529411764705........
This would result BPM steps around 85
84,9999208 BPM | 705.883 micros
85,0000425 BPM | 705.882 micros | 85 BPM = true 85,0000425 BPM
85,0001629 BPM | 705.881 micros

As I said the above fact is independent of the setting. "Force project tempo/time signature changes to occur on whole samples"

And now I spammed enough and
yes SRY- of course not the right place.
Greetings
__________________
I hope you can understand me? Without german beer my written english is always very bad, with beer it becomes unbearable!.
Less is more! To much limited the own creativity.

Last edited by ELP; 06-13-2016 at 01:47 AM.
ELP is offline   Reply With Quote
Old 06-13-2016, 03:02 AM   #18
nofish
Human being with feelings
 
nofish's Avatar
 
Join Date: Oct 2007
Location: home is where the heart is
Posts: 12,096
Default

Quote:
Originally Posted by lalo View Post
Hi, if set the BPM to 120 everything is fine.
But if i set it to 130, Reapers shows 129.999
if i set 129 it shows 128.998
if 85 it shows 85.01
strange stuff..
http://forum.cockos.com/showthread.php?t=151501

edit:
I see it's answered already.
nofish is offline   Reply With Quote
Old 06-13-2016, 12:44 PM   #19
aMUSEd
Human being with feelings
 
aMUSEd's Avatar
 
Join Date: Jun 2006
Posts: 1,293
Default

Does this fix the slowness on Mac at the moment?
aMUSEd 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:23 AM.


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