Re: [LAD] MIDI program change

I take your point about MIDI 2 being able to request info, but for the rest it's ignoring the musician's preferred workflow - and not even allowing them to change the behaviour. For me, the earliest sequencer I used (on the Acorn Archimedes no less) got this right - did exactly what you told it and nothing else. I'll not name names, but the worst I've come across in recent times would reset just about everything each time you stop and restart the transport! I still use a Yamaha for some stuff, and I've always kept it in multi mode. It remembers the full setup over power cycles, so it's switch on and go. If I change project it's a one button change of selected multi, so all bank and program information is set correctly at the start. On the software side it's a state file, and in a long project I might make program and bank changes while running, so I don't need a DAW then resetting all of these to what it considers are the 'right' ones. The argument about looping is a non-starter. Firstly it's extremely rare for me to even think about this, so why am I constrained by what some others do? If I did want it, then I've got enough going on upstairs to plonk the necessary bits in where needed. I'm sorry if this is coming over as a rant, but it seems to me that even in music, free expression is becoming less and less free, and the only people who can do anything about it are those of us producing the code! -- Will J Godfrey https://willgodfrey.bandcamp.com/ http://yoshimi.github.io Say you have a poem and I have a tune. Exchange them and we can both have a poem, a tune, and a song.