Author |
Topic: Current Wish List (Read 1360 times) |
|
Jamie OConnell
Administrator
    


Gender: 
Posts: 2027
|
 |
Current Wish List
« on: Aug 15th, 2001, 1:14am » |
Quote Modify
|
There's still a few items left over from last cycle, that I'll have to dig up and post here. Feel free to add any that you come up with. I can't promise that we'll get to everything or promise a timeframe, but I will promise that everything will be considered. We also consider feature popularity, so often requested features usually get implemented before ones that only help a few.
|
« Last Edit: Sep 10th, 2001, 9:23am by admin » |
IP Logged |
--Jamie Music is its own reward.
|
|
|
TabSel
Member
 


Posts: 13
|
 |
Re: Current Wish List
« Reply #1 on: Aug 15th, 2001, 12:52pm » |
Quote Modify
|
Hi Jamie, congratulation for the move to the new forum, great! I wonder how you manage all this... I thought about some things I would like to see in MidiOX: After making the Keyboard to MIDI part configurable (thanks for this again, I have a german keyboard layout I come about the idea to use "other peripherals" as "MIDI control devices" as well. What about a configurable Mouse x/y Panel. Or a TouchPad x/y/z controller? I own several Laptops whith builtin Synaptics pressure sensitive Touchpads. Would be great to use the TPs as 3 dimensional MIDI Controllers... I thought about implementing it myself in a standalone application/applet but this Windows/C++ stuff is hard to learn for me as newbie...I understand all quite well though and made the beginning...But integration into MidiOX would be better as it will not cut down the number of applications for Yoke Ports as MidiOX itself captured them already for monitoring... Synaptics provides a TouchPad API which even I understand!!! Just an idea...
|
|
IP Logged |
|
|
|
Jamie OConnell
Administrator
    


Gender: 
Posts: 2027
|
 |
Re: Current Wish List
« Reply #2 on: Aug 15th, 2001, 3:09pm » |
Quote Modify
|
Thanks for the suggestion about adding support for control surfaces. Some time ago we did do some experimenting for possible inclusion of joystick support, and Jerry actually wrote an applet which would do Mouse x/y mapping of controllers. You could assign a controller to each of 4 quadrants (top, bottom, left, right). Perhaps Jerry could be coaxed into releasing it as a sample . There's also the MIDI Joy program, that allows you to assign controllers to a Joystick: http://vellocet.com/ We will consider adding more surface control capabilities to MIDI-OX itself.
|
|
IP Logged |
--Jamie Music is its own reward.
|
|
|
TabSel
Member
 


Posts: 13
|
 |
Re: Current Wish List
« Reply #3 on: Aug 15th, 2001, 3:34pm » |
Quote Modify
|
Great to hear! Maybe you uncover your coding secrets a little and tell me how you do this, basically, so I might add a TouchPad control device... TabSel
|
|
IP Logged |
|
|
|
Lynn
Member
 


Gender: 
Posts: 16
|
 |
Re: Current Wish List
« Reply #4 on: Aug 16th, 2001, 5:48pm » |
Quote Modify
|
Jamie, I am thinking of a network of computers each running a copy of MIDI-OX that can be linked together using TCP/IP. My vision would be that a remote MIDI-OX would appear to a local MIDI-OX like standard MIDI-In and/or MIDI-Out ports. Each copy of MIDI-OX on the various computers would have configuration settings (IP address, port number) for each remote MIDI-OX copy with which it would communicate. There is a "shareware" package available (MidiViaNet) that somewhat attempts to do this, but it only transmits the standard midi "commands" (note on/off, program change, controller change, etc.) -- but not SysEx data. It does a fairly good job of sending MIDI data in realtime between two computers on a 100mb/s ethernet TCP/IP link. But I can't make contact with the developer and the package has been dormant for a long time. I'm afraid that it's ability to transmit all valid MIDI data, including SysEx, will never materialize. I realize that it will be difficult to get perfect timing over a TCP/IP link, but my experiments with MidiViaNet have convinced me that this capability is usable. And anyway, I think MIDI-OX could do it better and faster.
|
|
IP Logged |
|
|
|
Jamie OConnell
Administrator
    


Gender: 
Posts: 2027
|
 |
Re: Current Wish List
« Reply #5 on: Aug 16th, 2001, 8:36pm » |
Quote Modify
|
Thanks for the confidence . We will consider it, but this is a pretty big ticket item in terms of time and resources. For something to appear as if it was a driver, it would probably be best if it were a driver. Of course, once you do that, there are completely different issues between Windows 9x (obsolete within a year or two), and Windows NT (2000, XP).
|
|
IP Logged |
--Jamie Music is its own reward.
|
|
|
TabSel
Member
 


Posts: 13
|
 |
Re: Current Wish List
« Reply #6 on: Aug 16th, 2001, 11:18pm » |
Quote Modify
|
Yes, notwork linkage would be great. I think it would be considerable easier to implement the OSC-API as Reaktor does than inventing the whell again... And what I also want to see somewhere in the future is the extension of MIDIOX to monitor not only midi but audio (ASIO !) as well plus an addition to MidiYoke like ASIOYoke - an ASIO loopback driver. Of course networked!!! TabSel
|
|
IP Logged |
|
|
|
norman
New Member

 MIDI-OX Rules!
Posts: 1
|
 |
Re: Current Wish List
« Reply #7 on: Feb 15th, 2008, 4:18pm » |
Quote Modify
|
I've often fancied being able to intercept the IN data and put it through a kind of arppegiator module before sending it on it's way. The module I imagine is a simple but OPEN sort of thing that would allow me to experiment with lots of different mathematical ideas. Does this sound crazy or not? Best wishes from norman.
|
|
IP Logged |
|
|
|
Jamie OConnell
Administrator
    


Gender: 
Posts: 2027
|
 |
Re: Current Wish List
« Reply #8 on: Feb 15th, 2008, 5:39pm » |
Quote Modify
|
Have you checked out the MOXArp sample from the MIDI-OX main page? The source code is there, so it definitely is open in that regard.
|
« Last Edit: Feb 16th, 2008, 3:32pm by Jamie OConnell » |
IP Logged |
--Jamie Music is its own reward.
|
|
|
|