Moderators: MattKingUSA, khz, spamatica
Tim E. Real wrote: ↑Sun Jun 18, 2023 3:43 pmHowever, some relief can be found in our midi track controller graphs.
Look closely and it can be seen that when the midi track is driving a synthesizer, midi controller graphs are available
that are mapped to each of a synth's audio controllers.
Cool! Is this new? I never saw this before! This way you can create dedicated tracks for automation parameters, with automation in movable parts. Very nice.
It's not perfect though.
It only maps to actual synth controllers.
It does not map to our built-in volume and pan audio controllers that are found on every audio track.
I'd like to add both of them someday.
Also, the actual midi controller numbers that are assigned to these controllers are arbitrarily chosen.
They start at NRPN 0x6000 (I think).
These numbers cannot be changed or chosen by the user.
Great for drawing but not so good for recording from an external controller, since (N)RPN input support is not very good ATM.
Someday I'm going to allow mapping to any chosen numbers.
When I get around to replacing these popup menus with a 'grand table' itemized listing.
Same for the audio controller popups. Some plugins have thousands of controllers. A popup kinda fails in that scenario, too many entries.
A scrollable 'grand table' will be much better.
And finally on the wish list:
I really would like to add individual read, off, touch, write settings for each audio controller
instead of one setting for all of them at the bottom of each mixer strip.
Because it would be nice to be able to say, turn off individual controllers, or record to only one while preserving the others.
Same with midi controllers.
It comes with the risk of more micro-management, but hopefully we'll find a way to make it work.
Tim E. Real wrote: ↑Sun Jun 18, 2023 4:46 pmSomeday I'm going to allow mapping to any chosen numbers.
Should be nrpn for continuous controllers though, for the better resolution?
The midi-controller-graphs are not so easy to handle as the automation graphs. They use the "resolution" you choose, so the graph will be taken in 16s when you have added some notes before in 16s. Yo nee to change the resolution finer, and change itback when returning to notes.
So the automation is easier to handle, have never changed speed in the past, so i can live with this 
Many thanks for the lighing speed fast changes... Have compiled well,and both systems now work with it...
While on this subject, for the mixer automation type thing, I noticed when I switched to version 4 that some more had been added, but the documentation is out of date. Unless the docs have been updated since then. So what are "Auto off", "Read", "Touch", "Latch", and "Write"?
I prefer to be known as a figment of the 'nets imagination, living in the future, waiting for the rest of you to catch up.
Notes from Untalenz, an untalented old muso https://Untalenz.rocks/
onefang wrote: ↑Mon Jun 19, 2023 6:32 amWhile on this subject, for the mixer automation type thing, I noticed when I switched to version 4 that some more had been added, but the documentation is out of date. Unless the docs have been updated since then. So what are "Auto off", "Read", "Touch", "Latch", and "Write"?
Playback modes
Auto Off: ignore all existing automation
Read: use automation
Record modes
Touch: set automation value with a controller at playhead location while not playing
Write: record automation with a controller while playing
Latch: no clue
I rewrote the book on automation!
Well, actually just our wiki page.
Hm, we seem to now have two wikis.
The one I fixed was the recent wiki, added to our web page - not the github wiki.
Please take a look for info and questions. Note that this stuff actually has not made it into an official release yet, but will on next release.
https://muse-sequencer.github.io/docs/automation.html
There seems to be the same "freewheel" issue with Yoshimi.