v5.81pre7 - May 4 2018

[zappadave]

v5.81pre7 - May 4 2018
+ MIDI editor: 14-bit CC editing fixes [t=201025]
+ MIDI editor: do not include end-of-item ANO in channel list [t=185555]
+ MIDI editor: improve undo messages on various lane edits
+ MIDI editor: merge note names w/ shift pressed when loading from recent list (feature lost in v5.0) [t=178560]
# API: SetTrackSelected() notifies various windows of state change
# macOS: sign icc18 build disk images

[Justin]

ahh that macOS .dmg signing thing failed miserably, boo.

[ivansc]

Shit happens, Justin.

[Geoff Waddington]

Originally Posted by Justin

ahh that macOS .dmg signing thing failed miserably, boo.

Don't know if you already know this, saw this thread posting:

>>>>>>>
There's 3 ways to do this. In the terminal on OS X 10.11.5 or newer. Note: you can code sign DMGs on earlier OS versions, however Sierra only likes them from 10.11.5 or newer.

codesign --force --sign "Developer ID Application: <identityIdentifier>" <pathToDMG>

Verification is done via (requires macOS Sierra).

spctl -a -t open --context context:primary-signature -v <pathToDMG>

Araelium have updated DMG Canvas (v2.3), so it will code sign DMGs when it builds.

DropDMG has been updated to code sign DMG image files too (v3.4).

There's also (a tool I developed) called App Wrapper (3.6), which can code sign DMG files.
>>>>>>>

[tusitala]

Hi Justin,

Tested this latest Pre and encountered the same behaviour I reported here:

https://forum.cockos.com/showpost.ph...6&postcount=31


Thanks for your work!

All the best
-t

[Justin]

Originally Posted by Geoff Waddington

Don't know if you already know this, saw this thread posting:

>>>>>>>
There's 3 ways to do this. In the terminal on OS X 10.11.5 or newer. Note: you can code sign DMGs on earlier OS versions, however Sierra only likes them from 10.11.5 or newer.

codesign --force --sign "Developer ID Application: <identityIdentifier>" <pathToDMG>

Verification is done via (requires macOS Sierra).

spctl -a -t open --context context:primary-signature -v <pathToDMG>

Araelium have updated DMG Canvas (v2.3), so it will code sign DMGs when it builds.

DropDMG has been updated to code sign DMG image files too (v3.4).

There's also (a tool I developed) called App Wrapper (3.6), which can code sign DMG files.
>>>>>>>

This is exactly what we did, and I double-checked that. This is on High Sierra rather than Sierra. Here's the output of spctl

$ spctl -a -t open --context context:primary-signature -v reaper581pre7-icc18_x86_64.dmg 
reaper581pre7-icc18_x86_64.dmg: rejected
source=Developer ID

Let me try verification on another system too... Edit: ah, seems GateKeeper on my High Sierra install is still odd, maybe related to this earlier issue I had with this system: https://www.1014.org/index.php?article=718. On a Sierra install it worked.

Anybody else test the icc18 images?

[Futur8me]

I have installed the icc18 and no issues here so far on 10.13.4.

I have never had any warnings at all with any of the non signed reaper installs?.

.

.

.

[EvilDragon]

Hey Justin/schwa... this one might be quite old, but it's really weird, but since you guys are in MIDI editor mode, let's see if something can be done about it:

1. Create an empty MIDI item
2. Input some MIDI CCs ONLY (no notes)
3. See Edit menu, copy/paste actions (default Ctrl+C/V) are grayed out
4. Actually try to do Ctrl+C/V and IT WORKS.
5. As soon as a single note is entered in MIDI editor, copy/paste actions in Edit menu are not grayed out any longer.


Interestingly, if I assign these same cut/copy/paste actions to MIDI CC context menu, they never get grayed out! They do get grayed out in MIDI piano roll context, MIDI main menu context, and of course the MIDI main edit.

This is cosmetic, but it's also confusing. By all means, Copy should not be grayed out if there's ANY MIDI data entered in the item, not just notes. Right?


Just had a newbie Reaper user trip up on this one, so... might be nice to have this one fixed?

[EvilDragon]

And another one:

1. Have some MIDI data in the clipboard
2. Make sure MIDI editor is still open (relevant option not to close MIDI editor after deleting the selected item enabled)
3. Create new empty project, add a track
4. Paste from MIDI editor (NOT the arrange!)

Result: MIDI data gets pasted, but no MIDI item gets created. If pasted from arrange, MIDI item will be created.


Also, where is this clipboard even stored? It seems to be retained even after Reaper is closed...

[swiiscompos]

I am testing for the first time the changes in the MIDI editor but so far it's quite confusing. I think it is because some options cancel each others and some others don't seem to work correctly (for one MIDI Editor per project)

1. For example (and it took me a while to understand what the problem was): I had "Selection is linked to editability" checked so I expected all selected item to be editable... except that it wasn't the case because "Avoid automatically setting MIDI items from other tracks editable" was also checked.

2. Is there any difference between "Active MIDI item follows selection change in arrange view" and "Selection is linked to editability"?

3. If "Selection is linked to visibility" is checked, double clicking on another MIDI item in the arrange view will make it editable but the previously double clicked MIDI item will still be visible and selected but not editable, even if "Selection follows editability" is also checked.

4. With "Selection follows editability" checked I have a weird behavior. With the MIDI editor closed double click on a MIDI item in the arrange. Then single click another MIDI item in the arrange view: Nothing happens (expected: newly selected MIDI item is editable). However double click on another MIDI item: it opens but all the previously opened MIDI items are still visible and now single clicking them will switch the editability as expected, but only among those items who have been double clicked before (and are visible).

5. "Active MIDI item follows selection change in arrange view" seems buggy. When only this one checked selecting another item in the arrange view will add it (previous item still editable) as opposed to closing the previous item and opening the newly selected one as expected.

[tack]

Originally Posted by EvilDragon

5. As soon as a single note is entered in MIDI editor, copy/paste actions in Edit menu are not grayed out any longer.

For me, Copy is always greyed out unless a note is selected. That is, I can add notes, but if I just select CCs and not notes, Copy is still disabled.

Indeed, ctrl-c/ctrl-v always works, which is almost certainly why I've never noticed this.

[EvilDragon]

Yeah it makes no sense that it would be grayed out if there are no notes in the MIDI item, but there IS other MIDI data in it...

[EvilDragon]

Originally Posted by swiiscompos

1. For example (and it took me a while to understand what the problem was): I had "Selection is linked to editability" checked so I expected all selected item to be editable... except that it wasn't the case because "Avoid automatically setting MIDI items from other tracks editable" was also checked.

I guess that's an additional precaution measure, I assume. We had this option before as well, it was called differently IIRC.

Originally Posted by swiiscompos

2. Is there any difference between "Active MIDI item follows selection change in arrange view" and "Selection is linked to editability"?

Yes. Former sets the active item to the one you clicked on, the latter changes editability of all selected items (via marquee). There is a difference.

Originally Posted by swiiscompos

3. If "Selection is linked to visibility" is checked, double clicking on another MIDI item in the arrange view will make it editable but the previously double clicked MIDI item will still be visible and selected but not editable, even if "Selection follows editability" is also checked.

Cannot confirm this one. I double-click one item, only this one is shown in MIDI editor. Then I double-click another one, only that one is shown, the old one is not visible nor editable anymore.

Originally Posted by swiiscompos

5. "Active MIDI item follows selection change in arrange view" seems buggy. When only this one checked selecting another item in the arrange view will add it (previous item still editable) as opposed to closing the previous item and opening the newly selected one as expected.

Hm, I cannot confirm this one somehow.

[swiiscompos]

Originally Posted by EvilDragon

Hm, I cannot confirm this one somehow.

Do you mind trying with my project? If you can't reproduce then it's either something on the MacOS build or one of my settings. But something is definitely broke, either in the build or on my side.

[Justin]

Originally Posted by swiiscompos

5. "Active MIDI item follows selection change in arrange view" seems buggy. When only this one checked selecting another item in the arrange view will add it (previous item still editable) as opposed to closing the previous item and opening the newly selected one as expected.

Ah yeah, confirmed this.

[FnA]

"Link to visibility" has something like that, and the item re-select bug of previous prereleases, going on too. (with or without "link to editability" turned on as well). Other check boxes off. one per project. open selected items.

For example,
you have only one visible, the active item
you single click another it becomes visible. expected.
you double click it (the only selected item)
formerly active item is left visible, and is re-selected.

Similar with more selected items. I guess the point is the formerly active item gets left visible/re-selected.

Not sure if link to visibility will become important to me, but this seems wrong.


edit. I see #3 in swiiscompos post is this issue.

[Justin]

Originally Posted by EvilDragon

And another one:

1. Have some MIDI data in the clipboard
2. Make sure MIDI editor is still open (relevant option not to close MIDI editor after deleting the selected item enabled)
3. Create new empty project, add a track
4. Paste from MIDI editor (NOT the arrange!)

Result: MIDI data gets pasted, but no MIDI item gets created. If pasted from arrange, MIDI item will be created.


Also, where is this clipboard even stored? It seems to be retained even after Reaper is closed...

Clipboard is a system thing. Pasting here into an empty MIDI editor does nothing, hmmmm.... edit: ah there it goes, ok.

[EvilDragon]

What about the cut/copy being grayed out and this depending only on existence of notes in MIDI items?

[MaestroS]

Justin. could you do makeup. Create mode Hide and open icons in TCP
Toggle Show Track icon in TCP

[EvilDragon]

^^^ Post in feature requests subforum, what you ask for is unrelated to this prerelease cycle.

Also not sure why you just don't use Track Manager for what you're saying there.

[MaestroS]

In the Track Manager there is no way to turn off or turn on the icons

[snooks]

Originally Posted by zappadave

# API: SetTrackSelected() notifies various windows of state change

Thanks for this!