v5.22 pre 5 June 26th

[nicholas]

v5.22pre5 - June 26 2016
+ Automation: add separate configuration for automation write action transition times
+ Automation: improve behavior when auto-adding envelopes
+ MIDI editor: display note-off velocity properly in MIDI event properties dialog [p=1698784]
+ MIDI editor: preserve vertical zoom level when hiding/unhiding note rows [http://forum.cockos.com/showpost.php...1&postcount=5]
+ Track routing window: improve behavior when modifying track volume and window open [p=1698267]

[EvilDragon]

Originally Posted by nicholas

+ MIDI editor: preserve vertical zoom level when hiding/unhiding note rows [http://forum.cockos.com/showpost.php...1&postcount=5]

FUCK YEAHHHH!!!


Slight tweak perhaps: rows should be starting from the bottom of MIDI editor, not from the top.

Also it's possible to mousewheel vertically up and move out all the rows - this should not happen.

[lachrimae]

Since you're looking at ME zoom, just fyi if the ME piano roll area is taller than ~900 pixels it will only open fully zoomed out. If you increase the size of a cc lane so that the ME area is smaller than 900 pixels it will open with normal zoom.

https://i.imgur.com/4mY79ve.gifv

4k monitors can show up to 2,063 pixels of vertical ME piano roll area but it always opens zoomed out unless a cc lane covers over half the screen.

This isn't a new bug so apologies in advance for posting in a pre :-/

[DeathByGuitar]

Originally Posted by EvilDragon

FUCK YEAHHHH!!!


Slight tweak perhaps: rows should be starting from the bottom of MIDI editor, not from the top.

Also it's possible to mousewheel vertically up and move out all the rows - this should not happen.

FUCK YEAHHHH!!!

ED, you deserve some of the credit for that one. You have more credibility than anyone else on this forum when it comes to MIDI, so thanks for echoing my gripe. :-D I think I actually prefer the notes showing at the top, unless there's a practical reason for why it'd be better at the bottom. Something having to do with docking it, perhaps?

Also, I noticed when I hide unused note rows, if I zoom in then I can't zoom out much, at least not back to the level they were at before.

Lastly, could we possibly get an action for resetting to the default zoom level, whatever that is?

Regardless,this fix is a HUUUUUGE deal,especially for drum programming! Oh dear god this made my month.

[ivansc]

Originally Posted by EvilDragon

FUCK YEAHHHH!!!


Slight tweak perhaps: rows should be starting from the bottom of MIDI editor, not from the top.

Also it's possible to mousewheel vertically up and move out all the rows - this should not happen.

And a big YAY from me too. Getting there, devs....

[EvilDragon]

Originally Posted by DeathByGuitar

I think I actually prefer the notes showing at the top, unless there's a practical reason for why it'd be better at the bottom. Something having to do with docking it, perhaps?

Well, when there are only a few rows shown, there's lots of empty space, and somehow to me it seems to be more logical to stack things from the bottom up, and not vice versa. So the notes would be closer to the CC lanes, it would be easier to visually connect notes and their velocity values...




This one also shows the mousewheel bug (allows vertical scrolling, but the vertical scrollbar doesn't allow scrolling in this case - so mousewheel should behave the same!).

[planetnine]

Originally Posted by nicholas

v5.22pre5 - June 26 2016

+ Automation: add separate configuration for automation write action transition times
...


...

Just had a quick look, but where is this config set, please?


Yay and Whoo for unused note hiding!

Are there plans for enabling a custom ordering of these in the pipeline, please?



>

[EvilDragon]

Editing Behavior->Automation

Originally Posted by planetnine

Are there plans for enabling a custom ordering of these in the pipeline, please?

Also - schwa, when are we getting note map editing back?

[EvilDragon]

Another bug with the new zooming behavior for hide unused notes: it's impossible to get back to the original zoom level (small) after zooming in vertically.


EDIT: ah, that's the same as this:

Originally Posted by DeathByGuitar

Also, I noticed when I hide unused note rows, if I zoom in then I can't zoom out much, at least not back to the level they were at before.

In fact, it's completely impossible to ZOOM OUT in hide unused modes now - only zoom in (this seems to depend on the amount of displayed note rows)! This should definitely be fixed

[EvilDragon]

When action "Notation: Adjust display quantization..." is assigned to a toolbar button, after the dialog is closed, the button doesn't go to "off" state. It should.

[Iu.Gob]

Originally Posted by nicholas

v5.22pre5 - June 26 2016

+ MIDI editor: display note-off velocity properly in MIDI event properties dialog [p=1698784]

Now it works fine. Thanks. Regards.

[Iu.Gob]

Bug Musical Notation. Problem with resolution screen after inserting a "mordent", save the project and reload it. Then decrease the screen resolution can be seen when using Zoom. Please see video. Win7 32.
https://drive.google.com/open?id=0B2...UwzZHpXZ0FOQWM

[Iu.Gob]

I've tried importing XML a project in Musescore. They have appeared time signature and clefs that were not in the original made in Reaper.
Reaper... https://drive.google.com/open?id=0B2...G5ZSWxiVVZ0a2c
Musescore... https://drive.google.com/open?id=0B2...28xXzk1N1A2YWM

Importing XML in Finale 2014. Problems viewing numbers from the tuplets.
Finale 2014... https://drive.google.com/open?id=0B2...21oSzZEaHJlTjQ

[airon]

+ Automation: add separate configuration for automation write action transition times

Tested this.

Write to actively-writing in time selection.

I'm getting the normal automation return time, in this case set to 200 ms, instead of the 30 ms I wanted.

Checked the prefs. It keeps changing back to the time set in Automation recording return speed.

[mccrabney]

when "hide unused note rows" is triggered, subsequent new notes that are recorded via
controller appear in the topmost note's row. super confusing. imo it should be a toggle
action that rechecks for new notes and shows their rows til the action is toggled off.

[Justin]

Originally Posted by airon

+ Automation: add separate configuration for automation write action transition times

Tested this.

Write to actively-writing in time selection.

I'm getting the normal automation return time, in this case set to 200 ms, instead of the 30 ms I wanted.

Checked the prefs. It keeps changing back to the time set in Automation recording return speed.

Oops, bug, fixing.

[EvilDragon]

Originally Posted by mccrabney

when "hide unused note rows" is triggered, subsequent new notes that are recorded via controller appear in the topmost note's row. super confusing. imo it should be a toggle action that rechecks for new notes and shows their rows til the action is toggled off.

Yes, they should be shown where they belong, not always on top.

[mccrabney]

^ licecap of this behavior in action.

also notice that in OVERDUB record mode, the duration lasts til the end of the midi item
until the NOTEOFF is received. as noted elsewhere, ideally it would only last up until
the play cursor rather than the end of the item.

[schwa]

Originally Posted by Iu.Gob

Bug Musical Notation. Problem with resolution screen after inserting a "mordent"

I don't think this has anything to do with mordents, I think the note stems just vanish when zooming out very far. Fixing, thanks for the report.

[schwa]

Originally Posted by Iu.Gob

I've tried importing XML a project in Musescore. They have appeared time signature and clefs that were not in the original made in Reaper.
Reaper... https://drive.google.com/open?id=0B2...G5ZSWxiVVZ0a2c
Musescore... https://drive.google.com/open?id=0B2...28xXzk1N1A2YWM

Importing XML in Finale 2014. Problems viewing numbers from the tuplets.
Finale 2014... https://drive.google.com/open?id=0B2...21oSzZEaHJlTjQ

Could you please attach the .rpp?

[Iu.Gob]

Originally Posted by schwa

Could you please attach the .rpp?

Of course. Regards.

[vanhaze]

Dear Cockos !

I experience instant Reaper crashes with this pre-version (64bit used) , when trying to open any (legally bought) plugin from Goodhertz, on my macbook 2015, OSX 10.10.5


Here's a snippet of crashlog:


Process: REAPER [1169]
Path: /Applications/Reaper 5.22pre5.21/REAPER64.app/Contents/MacOS/REAPER
Identifier: com.cockos.reaper
Version: 5.21.15 (5.21.15)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: REAPER [1169]
User ID: 501

Date/Time: 2016-06-27 23:04:16.497 +0200
OS Version: Mac OS X 10.10.5 (14F1808)
Report Version: 11
Anonymous UUID: 86C2F057-14C8-D0B3-7F9A-7C0F3DDF5234


Time Awake Since Boot: 9000 seconds

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000001ec727234

VM Regions Near 0x1ec727234:
Activity Tracing 000000011831c000-000000011851c000 [ 2048K] rw-/rwx SM=SHM
-->
MALLOC_NANO 0000600000000000-0000600000200000 [ 2048K] rw-/rwx SM=COW

Application Specific Information:
Performing @selector(swellOnControlDoubleClick from sender REAPERSwell_listview 0x100f662d0

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libobjc.A.dylib 0x00007fff8aeeb12a search_method_list(method_list_t const*, objc_selector*) + 140
1 libobjc.A.dylib 0x00007fff8aefab3f protocol_getMethod_nolock(protocol_t*, objc_selector*, bool, bool, bool) + 100
2 libobjc.A.dylib 0x00007fff8aefa9d4 protocol_getMethod + 175
3 libobjc.A.dylib 0x00007fff8aef20ab protocol_getMethodDescription + 31
4 com.audiounit.ghz2-VulfCompressor-VC2X 0x0000000107d460da __ARCLite__load() + 509
5 libobjc.A.dylib 0x00007fff8aeecad1 call_load_methods + 747
6 libobjc.A.dylib 0x00007fff8aeebb04 load_images + 214
7 dyld 0x00007fff68c3ff86 dyld::notifySingle(dyld_image_states, ImageLoader const*) + 249
8 dyld 0x00007fff68c4d8be ImageLoader::recursiveInitialization(ImageLoader:: LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 286
9 dyld 0x00007fff68c4d758 ImageLoader:rocessInitializers(ImageLoader::Link Context const&, unsigned int, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 138
10 dyld 0x00007fff68c4d9c9 ImageLoader::runInitializers(ImageLoader::LinkCont ext const&, ImageLoader::InitializerTimingList&) + 75
11 dyld 0x00007fff68c430ca dyld::runInitializers(ImageLoader*) + 89
12 dyld 0x00007fff68c4a231 dlopen + 578
13 libdyld.dylib 0x00007fff8bc29857 dlopen + 59
14 com.apple.CoreFoundation 0x00007fff9025e9c8 _CFBundleDlfcnLoadBundle + 152
15 com.apple.CoreFoundation 0x00007fff9025e190 _CFBundleLoadExecutableAndReturnError + 528
16 com.apple.audio.toolbox.AudioToolbox 0x00007fff96cfc28a AudioComponentPluginLoader::ResolveFactoryFunction (APComponentFromBundle&) + 82
17 com.apple.audio.toolbox.AudioToolbox 0x00007fff96cfbfeb APComponent::NewInstance(ComponentInstanceRecord*& ) + 143
18 com.apple.audio.toolbox.AudioToolbox 0x00007fff96cfbc97 _AT_AudioComponentInstanceNew + 107
19 com.cockos.reaper 0x00000001004a42fd AU_Plugin::AU_Plugin(void*, char const*, void*, int*) + 7965
20 com.cockos.reaper 0x00000001003489c6 FxDsp::FxDsp(int, char const*, void*) + 1606
21 com.cockos.reaper 0x0000000100360eaf FxChain::addSelection(HWND__*, bool, int) + 1967
22 com.cockos.reaper 0x0000000100388802 addDialogProc(HWND__*, unsigned int, unsigned long, long) + 14450

Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x00007fff92373232 kevent64 + 10
1 libdispatch.dylib 0x00007fff8d92926e _dispatch_mgr_thread + 52

Thread 2:
0 libsystem_kernel.dylib 0x00007fff9237294a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff985303dd start_wqthread + 13

Thread 3:
0 libsystem_kernel.dylib 0x00007fff9237294a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff985303dd start_wqthread + 13

Thread 4:
0 libsystem_kernel.dylib 0x00007fff9237294a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff985303dd start_wqthread + 13

Thread 5:
0 libsystem_kernel.dylib 0x00007fff9237294a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff985303dd start_wqthread + 13

Thread 6:
0 libsystem_kernel.dylib 0x00007fff9237294a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff985303dd start_wqthread + 13

Thread 7:
0 libsystem_kernel.dylib 0x00007fff9237294a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff985303dd start_wqthread + 13

Thread 8:
0 libsystem_kernel.dylib 0x00007fff9237294a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff985303dd start_wqthread + 13

Thread 9:
0 libsystem_kernel.dylib 0x00007fff9237294a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff985303dd start_wqthread + 13

Thread 10:
0 libsystem_kernel.dylib 0x00007fff9236d4de mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff9236c64f mach_msg + 55
2 com.apple.CoreFoundation 0x00007fff90238eb4 __CFRunLoopServiceMachPort + 212
3 com.apple.CoreFoundation 0x00007fff9023837b __CFRunLoopRun + 1371
4 com.apple.CoreFoundation 0x00007fff90237bd8 CFRunLoopRunSpecific + 296
5 com.apple.AppKit 0x00007fff92ae256b _NSEventThread + 137
6 libsystem_pthread.dylib 0x00007fff9853305a _pthread_body + 131
7 libsystem_pthread.dylib 0x00007fff98532fd7 _pthread_start + 176
8 libsystem_pthread.dylib 0x00007fff985303ed thread_start + 13

All Goodhertz plugins open just fine, without a crash, in Logic X 10.2.3.
I contacted Goodhertz about this issue and they stated that their plugins open just fine
in Reaper 5.21 official release, no crahses,

I hope Cockos can have a look at this issue ; I can't miss my beloved Goodhertz plugins in Reaper :0)

Thx 2 Cockos in advance !