Re: [EXS] program changes and so...
2004-05-10 by Sascha Franck
Per wrote: > Then click learn midi, and use your midi-program-change-button on your > controller. I allready do so. But as Hendrik Jan allready wrote, this only allows for +/-1 patch changes. Hendrik Jan Veenstra wrote: > Hmm... I feel tempted to say something about armchair programmers > here :-) The fact that the EXSP implements something doesn't > necessarily say it's easy to implement the same feature in the EXS. No, this is no "armchair programmers" opinion. I can't say anything more as I signed an NDA once upon a time. Apart from that, do you really think that Emagics superb programmers (which they certainly are) won't be able to implement MIDI program changes into their synths while almost every freebie developer is able to? > Still: the > fact that you can have 20000 instruments _might_ have been the reason > prog-changes were never implemented. And while it *might* have been the reason, it's no excuse. Just look at the way other virtual instruments do it. You can save as much patches as you like as Logic (or other host) presets (or through some internal preset menu) while still being able to compile them into banks of 128 patches. It would just have to be an addition (not a change) to what we allready have. > Rather > straightforward, but the disadvantage is that the Cable Switcher > track then can't contain automation data for the EXS's, for which you > thus need 2 additional tracks. Exactly. And of course it's a waste of further inserted plugins - unless you do some rerouting through busses and aux objects (better don't get me started on that one...). > I don't use midi files :-). And if I ever have to, I use a simple > midifile player that utilises the GM-bank from the quicktime synth. I have to use MIDI files in some situations and even if I could use the Windows equivalent or my QY70, it's just not the same as if they were playing through proper patches (let alone the fact that MIDI file import is one of the most screwed up things ever... since ages that is). > Why not give us the _best_ solution from the onset? [snippedisnip] Well, I don't know what the "best" solution would be, but supporting standard PrgChanges would at least follow some standard - and not necessarily a bad one. At least IMO it's some sort of necessary addition. Regards, Sascha