pwalpwal
so sysex can appear in either event list or sysex view, but not consistently in both? pffft
Be aware that these views have different purposes and operate differently.
An event list belongs to a track, whose events are directed to a particular synth or external port in the order and at the time they appear as part of playing a project. So sysex events on tracks are played on each playback in real time in the order they appear in the project. These are usually small messages that switch modes or load programs in a way that other MIDI events cannot. Longer messages will suspend playback, so we don't like putting them on tracks.
The sysex view is a database of sysex banks or messages we collect for various purposes: to be loaded or saved in (.syx) files, added to one or more tracks, sent automatically on project startup, loaded directly from synths, dumped directly to synths on demand, etc, and are not associated with any particular track or playback time. This view is useful as a library of small canned messages for mode switching or large bulk dumps of synth memory, such as patch data, patch banks, microtuned scales, etc., in a way that works pretty well across many different makers and models of h/w synths. Along with the sysex view is a built-in library of custom parameterized bulk dump requests for many different synths, and we can modify or create our own. These help us to collect bulk dumps from our external synths. The sysex view is per-project, so is very useful for setting up a world of synths when a project is loaded, with no repeat overhead on playback. But I also keep one project that has a collection of all my synth banks for backups.
The two views ought not be tied together, and owners of multiple hardware synths are very happy to employ those two views accordingly. So pffft right back (whatever that means?).
