| Author | Message | ||
     Mark Walsen (markwa) MidiNotate Developer Username: markwa Post Number: 1431 Registered: 7-2003 |
Please let me know whether MIDI SysEx support is important to you. Thanks! -- Mark | ||
| Sherry Crann (sherry) Senior Forum User Username: sherry Post Number: 636 Registered: 1-2004 |
Howdy Mark, Things are looking really good in the new section  For me personally this isn't something that I would use. All my sound sources are on my computer. But I also know that a lot of folks use external sound sources for their music, so I'm sure there's a group of folks out there who would love to have this feature. ttfn, Sherry | ||
| Jaap Veneman (jaapv) Senior Forum User Username: jaapv Post Number: 200 Registered: 6-2003 |
Mark, This support of MIDI SysEx is a quite common requirement for those who use synthesizers and/or keyboards. I think its an important function to add. Cheers Jaap | ||
| Mark Walsen (markwa) MidiNotate Developer Username: markwa Post Number: 1438 Registered: 7-2003 |
Jaap, I'm working on it now. The SysEx support will be included in a Composer Pro 1.0.9.2 beta release in a few days. Since you seem to be asking for this, you are obligated to test the SysEx support in the next Composer Pro beta :-) Cheers -- Mark | ||
| Jaap Veneman (jaapv) Senior Forum User Username: jaapv Post Number: 202 Registered: 6-2003 |
Mark, Personally I did not use SysEx commands and don't have experience with it. It would be a challenge for me. I know however from FORUMS that there are quite some users of keyboard and synth's that use SysEx commands to do specific musical or technical settings of their instruments. If you like I can ask one or two of these guys if the are willing to execute some tests. Problem however the guys I know are German's so language can be a problem. Jaap | ||
| Jaap Veneman (jaapv) Senior Forum User Username: jaapv Post Number: 203 Registered: 6-2003 |
Mark, I have not seen your general spec's for supporting SysEx functions I's sure yuu know these, but searching around I found a comprehensive list of requirements. I cannot fully judge these, but just for your information. -Open, edit, save .syx files -View bytes in Decimal, Hexadecimal or ASCII Character -Send .syx files to MIDI devices -Record all Sysex messages coming from a MIDI port -Store .syx files or Sysex messages in a local database -Browse the database to find out your device's massage -By device name -By head of sysex message -By message type -By date of insertion -By device's manufacturer -Comes with a database of more than 300 messages for about 70 MIDI devices Cheers Jaap | ||
| Jaap Veneman (jaapv) Senior Forum User Username: jaapv Post Number: 204 Registered: 6-2003 |
Mark, I have found a tool specific to create SysEx commands for the Yamaha keyboards. The tool is written in MS-Excel. It features to choose from several listings specific SysEx commands and does not require specific knowledge. The constructed SysEx is exported to either Cakewalk, XGWorks, Windows Clipboard. Did you foresee an import from Clipboard?? Its in German Language. Are you interested to see this tool? (English manual is included) Cheers Jaap | ||
| Mark Walsen (markwa) MidiNotate Developer Username: markwa Post Number: 1440 Registered: 7-2003 |
Jaap, My goal for SysEx support in Composer Pro are fairly limited, at least for the first version of Composer Pro. The goal is simply this: to enable the user to save and restore from the .not file the patch settings on his MIDI keyboard (or MIDI sound module) that were used for that specific song. The kind of support you are describing is what a "patch librarian" tool provides. Some patch librarians have specific knowledge about specific types of MIDI keyboards and sound modules. Such patch librarians offer a user interface for editing the patches, as an alternative to the user interface provided on the control panel of the physical device (MIDI keyboard or sound module). I have no ambitions to provide that kind of patch librarian support, that has specific knowledge about specific manufacturer/model devices. Some patch libraries provide general save/restore patch support, that doesn't have specific knowledge abou the specific manufacturer/models of MIDI devices. Composer Pro's support will be a little bit like such a limited patch librarian, except that Composer Pro will save the patch information to a specific .not file. Composer Pro will record a SysEx dump of patch information from the MIDI device, and will play (restore) the same SysEx dump back to the device. This SysEx information will be stored in the .not file. That is the basic functionality in Composer Pro. In addition, perhaps the first version of Composer Pro will support importing and exporting .syx files to/from a .not file. I'll take a look at some of the high-end MIDI sequencers out there and see if they do any more than what I've planned. I think that trying to combine the functionality of a full-featured patch librarian with MIDI sequencing, in a single application, would be a thankless job. I suspect customers would rather independently choose the patch librarian, separate from the choice of the MIDI sequencer. Cheers -- Mark | ||
| Jaap Veneman (jaapv) Senior Forum User Username: jaapv Post Number: 205 Registered: 6-2003 |
Mark, I think you are right here. See also my later email, import from windows clipboard might be usefull. At least the librarian I found supports export to clipboard. Cheers Jaap | ||
| Mark Walsen (markwa) MidiNotate Developer Username: markwa Post Number: 1441 Registered: 7-2003 |
Jaap, I took a look at Cakewalk Sonar's SysEx support. It provides the funcitonality I was thinking of providing, and a little more. Sonar does let the user edit SysEx messages that are small (less than 256 bytes I believe). Sonar also lets the user insert SysEx events for playback in the middle of a track. I had not anticipated that need. I'm not familiar with the scenarios where a mid-track SysEx command would be needed. I anticipated only needed to play the SysEx commands when the user first loads the song, and when the user explicitly requests the SysEx commands to be played. Thus, following Sonar's typically good model for functionality, I'll probably add these two other options: (1) editing of small SysEx messages, and (2) mid-track SysEx events. Easy to do. -- Cheers Mark |
