hello,
i’ve noticed a change when editing a chord-seq. previously i selected notes then changed to set, let’s say, midichannel and set them. this was done instantly. now it seems i have to set and the click in the chord-seq editor window to set the new channel. is this a new intended behaviour? also it seems command-a is not working. selecting by click&drag works ok, though.
i’m on a macbook pro m1 with Sonoma 14.7
thanks in advance,
perti
Dear perti,
I don’t think i got your problem here, What do you mean by “i selected notes then changed to set,” ?
There has been some changes for VOICE and Chord-seq indeed, Before you you could drag the note up and down. We removed this feature to prevent accidentally changing pitches which is very annoying. Are you talking about this?
If you need to do so, will make an option or shortcut to do so,
BEst
K
dear Karim,
i apologise for the poor phrasing. what i meant was that when selecting notes in a chord-seq editor and then changing an attribute, the changes are not reflected if i don’t click in the window. till 7.4 i was able to select any items and then change any attribute as channel, or duration, or whatever, all at once and instantly as soon as i changed its value. now it does not happen till i click anywhere in the editor window. also it seems that the shortcut command-a is not working, so i need to click-drag to select.
i hope it’s a bit clearer now.
and yes please, bring the old drag behaviour feature back as an option.
thanks a lot again,
p.
Dear Perti,
No worries, Yes indeed there are some “glitches” side effects. But I am almost there.
It will be dealt with, and pretty soon will deliver a corrective patch.
I am really sorry about this. I have to deal with multi platform issues (mac, win and linux), and didn’t have a lot of feedback, Next delivery, i will try to send to the community Beta versions for testing.
Will soon send a patch ASAP.
Best
K
thanks again Karim!
Dear Perti,
You will find all fixes here:
https://github.com/openmusic-project/openmusic/releases/download/v7.5/patch_251124.lisp
(put the patch lisp file in the init folder of your OM installed application)
Sorry for that.
Best
K
dear Karim,
thanks for the patch. there’s something that it still not working as before. please let me know if i’m missing some new behaviour. the point is that when i select a group of notes in a chord-seq, and change its midi channel, they are not automatically updated unless i click anywhere in the editor window. clicking on any blank space will update the midi channel. in versions 7.2 and 7.4 this was done automatically, no need of clicking for updating the new values. i’ve just double-checked it. is this a new intended behaviour?
thanks again for taking care of this,
perti
(Sonoma mbp m1)
Dear perti,
Are you sure you have put the patch above:
https://github.com/openmusic-project/openmusic/releases/download/v7.5/patch_251124.lisp
in your init file, and restarted OM?
Because the fix is in this patch, just tested it on M1 sonoma.
Best
K
dear Karim,
i did that, and just in case, did it again. results are the same. i also moved out other init files, just in case they where redefining something, but no, i’ve got the same behaviour.
is there something you may suggest to try? some checklist i can follow to test this?
perti
UPD: it must be something in my workspace, which was set with an older om version. i tried with a new workspace and it seems that everything is fine. i need to continue to work in that workspace, though.
Can you send me the workspace (zipped) to look into that?
Very strange. Maybe some code inside it, or preferences?
I tried with old workspaces and they work good.
found it! it is a file that I’ve got from anders and was located in the user folder. it was a patch for a request of mine which had to do with making onset a user-editable parameter for individual chords in a chord-seq. and as this is incorporated as a normal feature of om, i deleted it with no visible consequences. the strange thing for me was that it worked flawlessly until 7.4.
thanks a lot Karim! and anders too!
best,
perti
Do you mean this:
Best
K
onset-slot-edit-2.lisp.zip (1.5 KB)
i had this file into the user folder of my workspace. as soon as i deleted it all went back to normal. it seems it was interfering with om7.5, as this request was always there in the workspace.
Yes, you don’t need it anymore since you have it in version 7.5 (see above)
Best
K