Author |
Topic: Summary of Thread in General (Read 3212 times) |
|
Larry Salomon Jr.
Member
 
 On a quest to play like I had 10 arms
Gender: 
Posts: 24
|
 |
Summary of Thread in General
« on: May 25th, 2005, 2:54pm » |
Quote Modify
|
I posted a long thread in General in hopes that a solution already exists, but just in case one doesn't here are two enhancement requests: Add the ability to send 1) a SysEx file or 2) a MIDI file on receipt of a MIDI event on a specific (or all) channel on a specific (or all) WMD port. For 2), the ability to specify looping options would be helpful: Repeat n times (1 <= n <= 16) Repeat indefinitely Also, a companion "stop playing MIDI" feature should be added, so that the "Repeat indefinitely" option can be stopped. This would be tied to an incoming event on a specific (or all) channel on a specific (or all) WMD port. The "stop playing MIDI" parameters would also specify the channel (or all) and port (or all) where the MIDI that is to be stopped is playing. ------------------------------------- Using this, I could create a .MID file in Cubase (or some other package) containing a 1 measure phrase. Then, I would define a Data Map mapping the E1 Note On event from MIDI IN 3 (my Roland PK5a foot pedal) on any channel to this .MID file, with the repeat set to 1. Similarly, I could create a bunch of other phrasings and tie them to the foot pedal. Then, while I'm playing keys or guitar live, I can trigger the sequences using the foot pedals. The best thing is that, since this is part of the Data Mapping functionality, these phrases could be dynamically loaded per song via the Patch Map functionality (which loads a custom Data Map file on Program Change). This would give another dimension of depth to the 7-member band that I'm in.
|
« Last Edit: May 25th, 2005, 3:19pm by Larry Salomon Jr. » |
IP Logged |
|
|
|
Peter L Jones
Expert
    

Hit it
Gender: 
Posts: 978
|
 |
Re: Summary of Thread in General
« Reply #1 on: May 25th, 2005, 3:19pm » |
Quote Modify
|
These sound more like sequencer features than what MIDI OX is - to me - about. In Muzys, for example, I can have an incoming MIDI note trigger a MIDI sequence containing whatever MIDI events I like getting routed to whatever channels, repeating however I've set that particular trigger to repeat (with some fiddling about). I'm not sure if Muzys supports MIDI transport controls (for "stop playing") but there are other sequencers that do.
|
« Last Edit: May 25th, 2005, 3:22pm by Peter L Jones » |
IP Logged |
"...Playing fast around the drums is one thing. But to play with people for others, to listen to, that's something else. That's a whole other world." -- Tony Williams
|
|
|
Larry Salomon Jr.
Member
 
 On a quest to play like I had 10 arms
Gender: 
Posts: 24
|
 |
Re: Summary of Thread in General
« Reply #2 on: May 25th, 2005, 3:27pm » |
Quote Modify
|
It is more like a sequencer, but a playback-only sequencer. Plus, it is much more general than a sequencer because the playback of the SysEx or MIDI file can be tied to any MIDI event, not just a keypress. MIDI-OX is supposed to be the MIDI equivalent of a Swiss Army Knife. This request fits nicely into that concept.
|
|
IP Logged |
|
|
|
Peter L Jones
Expert
    

Hit it
Gender: 
Posts: 978
|
 |
Re: Summary of Thread in General
« Reply #3 on: May 25th, 2005, 6:03pm » |
Quote Modify
|
But a good sequencer does just that - takes a midi event and responds with a midi sequence. MIDI OX doesn't really do sequencing. That's the next level "up". MIDI OX works on the midi data stream in flight - this event (now) is replaced by these events (now). Stored, time-dependent data is outside its scope (but it does have some timing stuff). Maybe a VB extension to MIDI OX could stream in data from a file... but it's still getting into MIDI sequencer territory and beyond MIDI OX. A free sequencer I have yet to look at: http://www.frieve.com/english/musicstd/features.html May not even have midi triggering but, if it does, it might do exactly what you want. (I can't remember if Muzys can be made to trigger on any MIDI event -- but I'd just use MIDI OX to translate the event to a note and trigger on that note. There's plenty of notes outside the usual range or use a specific channel to give you 128 triggers.)
|
« Last Edit: May 25th, 2005, 6:06pm by Peter L Jones » |
IP Logged |
"...Playing fast around the drums is one thing. But to play with people for others, to listen to, that's something else. That's a whole other world." -- Tony Williams
|
|
|
Larry Salomon Jr.
Member
 
 On a quest to play like I had 10 arms
Gender: 
Posts: 24
|
 |
Re: Summary of Thread in General
« Reply #4 on: May 25th, 2005, 10:56pm » |
Quote Modify
|
I downloaded Alien Disko Systems 3000 019 beta today via the Sonic Spot site. I'm going to look at it over the weekend. Maybe that plus MIDI-Yoke plus MIDI-OX will give me everything I need.
|
|
IP Logged |
|
|
|
Jamie OConnell
Administrator
    


Gender: 
Posts: 2028
|
 |
Re: Summary of Thread in General
« Reply #5 on: May 27th, 2005, 11:58am » |
Quote Modify
|
Right. I'm not sure if you're aware, but the MIDI-OX MIDI Player, MIDIBar, just uses Windows MCI to play MIDI Files. To add true sequencing abilities to MIDI-OX would be a huge effort and beyond the scope of anything anticipated.
|
|
IP Logged |
--Jamie Music is its own reward.
|
|
|
dayton
Member
 
 MIDI-OX Rules!
Posts: 15
|
 |
Re: Summary of Thread in General
« Reply #6 on: May 30th, 2005, 3:09pm » |
Quote Modify
|
I don't know exactly what you need to do, but I needed to have real-time manipulation of a prerecorded MIDI-file. I simply had WSH open up the MIDI-Bar program and start playing the file I wanted (in my case it was when I pressed the lowest key on my keyboard). I do it differently now, using MAX/MSP, but it worked famously in several performances. When I'm home again, I'll post the code.
|
|
IP Logged |
|
|
|
Larry Salomon Jr.
Member
 
 On a quest to play like I had 10 arms
Gender: 
Posts: 24
|
 |
Re: Summary of Thread in General
« Reply #7 on: Jun 1st, 2005, 2:01pm » |
Quote Modify
|
on May 27th, 2005, 11:58am, Jamie OConnell wrote:Right. I'm not sure if you're aware, but the MIDI-OX MIDI Player, MIDIBar, just uses Windows MCI to play MIDI Files. To add true sequencing abilities to MIDI-OX would be a huge effort and beyond the scope of anything anticipated. |
| But I'm not looking to add sequencing capabilities, honestly. I want to be able to trigger the playing of one .MID or .SYX file that I'll create in Cubase (or MIDI-OX, in the case of .SYX files) on receipt of a user-defined MIDI event. It's very similar to the Data Mapping feature you already have. This is easily accomplished using the MCI interface, but it has to be connected with the rest of the Data Mapping functionality.
|
|
IP Logged |
|
|
|
Peter L Jones
Expert
    

Hit it
Gender: 
Posts: 978
|
 |
Re: Summary of Thread in General
« Reply #8 on: Jun 1st, 2005, 2:17pm » |
Quote Modify
|
So you could do it with some VB Script "easily" (I've yet to try VB Script)? Triggering playback of a MIDI sequence is sequencing, anyway! That's pretty much how most sequencers work (at least, those designed for live use).
|
« Last Edit: Jun 1st, 2005, 2:18pm by Peter L Jones » |
IP Logged |
"...Playing fast around the drums is one thing. But to play with people for others, to listen to, that's something else. That's a whole other world." -- Tony Williams
|
|
|
Peter L Jones
Expert
    

Hit it
Gender: 
Posts: 978
|
 |
Re: Summary of Thread in General
« Reply #9 on: Sep 30th, 2005, 3:16am » |
Quote Modify
|
Rather than start my own thread, I thought I'd try to further hijack this one (having killed it ). I'd like the Data Mapping facility to incorporate scripting. That is, I'd like it to wrap the existing WSH interface and make it easy to use. I want to write a script to maintain state information about a MIDI stream -- but I'd like to use the Data Mapping facility to decide which MIDI events get fed to my script. So, on the Data Mapping, Translation Map, Define Mapping form, I'd like an additional "Set Output to" option - a toggle between the existing data mapping and an option to "call script" (with a file chooser UI). The called script would accept the MIDI event and return an event to be used as a replacement. It could also cancel the event. In addition, it would have access to the rest of the MIDI OX object model, so it could create additional events. (And, as a WSH script, do anything else that environment allows, such as triggering MIDI file playback through MIDIBar...) From the scripting side, not a lot of difference. It just makes it easier to plug the script into an existing configuration.
|
« Last Edit: Sep 30th, 2005, 3:19am by Peter L Jones » |
IP Logged |
"...Playing fast around the drums is one thing. But to play with people for others, to listen to, that's something else. That's a whole other world." -- Tony Williams
|
|
|
|