Jens M Andreasen wrote:
If you know that the device is virtual and that it won't pass on any
messages to the next device, you can sometimes get away with sending
usb-midi at a higher rate. This has to be implemented at the driver
level though.
This is handled by the USB protocol: the host
On Thu, 2009-10-08 at 09:26 +0200, Clemens Ladisch wrote:
This is handled by the USB protocol: the host controller retries sending
a data packet until the device acknowledges it. In other words, the
driver can blast away at the device with lots of packets, but the actual
rate is never
Jens M Andreasen wrote:
On Thu, 2009-10-08 at 09:26 +0200, Clemens Ladisch wrote:
This is handled by the USB protocol: the host controller retries sending
a data packet until the device acknowledges it. In other words, the
driver can blast away at the device with lots of packets, but the
On Wed, Oct 07, 2009 at 12:51:20AM +0200, Ralf Mardorf wrote:
I guess I really do understand why you're still searching for another way
and that there are some disadvantages by using SysEx, but it sounds exactly
like what SysEx is designed for, because the user needs a GUI to control
this
On Tue, 2009-10-06 at 17:30 +0200, Nick Copeland wrote:
Out of interest, what was the problem with MIDI sequencing and SYSEX?
The only problem I knew about was that they are atomic and cannot be
interupted hence on 'legacy' 5-pin DIN at a meagre few kilobaud there
were timing issues, largely
On Tue, Oct 6, 2009 at 1:47 AM, Clemens Ladisch clem...@ladisch.de wrote:
David Robillard wrote:
Not enough context quoted to tell; are the stops in Aeolus really too
complicated to be controlled via controllers and programs?
No: For 55 or so organ stops, you'd need 55 boolean controllers;
Nick Copeland wrote:
Completely agree that SYSEX is where this kind of functionality should
reside.
This use of 0x7d is a bit antiquated, no? The reassignment of 0x00 to
indicate 3 byte
SYSEX ID means there is a bit more flexibility in the system.
Currently the following
are assigned:
Paul Davis wrote:
On Tue, Oct 6, 2009 at 1:47 AM, Clemens Ladisch clem...@ladisch.de wrote:
David Robillard wrote:
Not enough context quoted to tell; are the stops in Aeolus really too
complicated to be controlled via controllers and programs?
No: For 55 or so organ stops,
The issue with using the predefined CC such as #7 for other uses is that if any
GM controller sits on your MIDI channel it will use that as a volume control,
and it will be reinterpreted by Aeolus as some organ setting. The result is
highly unpredictable and I don't think there are 55
Paul Davis wrote:
On Tue, Oct 6, 2009 at 9:08 AM, Ralf Mardorf ralf.mard...@alice-dsl.net
wrote:
Keep in mind that you might want to control 2 devices in unison. You will
send control 7 to both devices, one device is using it for volume and the
other device is using it for anything else.
Nick Copeland wrote:
Having everything after 0xf0 as reassignable is a pretty cool idea.
Maybe often used manufacture IDs, eg. Roland, Yamaha, should be excluded ;).
Out of interest, what was the problem with MIDI sequencing and SYSEX?
The only problem I knew about was that they are atomic
On Tue, Oct 6, 2009 at 11:30 AM, Nick Copeland
nickycopel...@hotmail.com wrote:
Out of interest, what was the problem with MIDI sequencing and SYSEX? The
only problem I knew about was that they are atomic and cannot be interupted
hence on 'legacy' 5-pin DIN at a meagre few kilobaud there were
Paul Davis wrote:
how do you edit the messages? it requires librarian style
application handling.
As mentioned before I do agree with you Paul, but anyway there are
sequencers like the Atari Cubase that makes it possible that even
absolutely noobs can edit a GUI to edit SysEx by the
On Tue, Oct 6, 2009 at 1:13 PM, Ralf Mardorf ralf.mard...@alice-dsl.net wrote:
Paul Davis wrote:
how do you edit the messages? it requires librarian style
application handling.
As mentioned before I do agree with you Paul, but anyway there are
sequencers like the Atari Cubase that makes it
Does any know if hidef MIDI will address these issues? The MMA is not very
transparent
regarding what they want to put in there.
Regards, nick.
we have to make sure the old choice [Windows] doesn't disappear”.
Jim Wong, president of IT products, Acer
Date: Tue, 6 Oct 2009 13:15:31 -0400
Paul Davis wrote:
you've missed my point.
if aeolus is currently programmed to switch to stop setting S1, and i
want it to switch setting S2 instead, what do i, as a user do? what do
i have to know?
I don't know Aeolus, but usually a user should be able to change between
setting 1 and
Nick Copeland wrote:
Does any know if hidef MIDI will address these issues? The MMA is not
very transparent
regarding what they want to put in there.
Some days ago I visited the MMA site and didn't found anything about
hidef MIDI, today I found this, but didn't read it:
On Tue, Oct 6, 2009 at 1:26 PM, Ralf Mardorf ralf.mard...@alice-dsl.net wrote:
Paul Davis wrote:
you've missed my point.
if aeolus is currently programmed to switch to stop setting S1, and i
want it to switch setting S2 instead, what do i, as a user do? what do
i have to know?
I don't
so you are saying that in order to edit a sequence that contains
requests for stop changes, the user must understand the *internal*
structure of a sysex message? and this is even more true when they go
to create the first such request (rather than edit an existing one) ?
This depends to the
On Tue, Oct 06, 2009 at 09:34:03PM +0200, Pedro Lopez-Cabanillas wrote:
In addition to the manufacturer ID, there should be enough additional bytes
to
uncertainly identify a particular model among others using the same
manufacturer ID.
Sure, e.g. four unique bytes at the start would solve
Pedro Lopez-Cabanillas wrote:
On Monday, October 5, 2009, Fons Adriaensen wrote:
On Mon, Oct 05, 2009 at 07:00:40PM +0200, Pedro Lopez-Cabanillas wrote:
The MMA requires that you use a registered manufacturer ID, but only for
commercial products. There is a special ID = 0x7D that is
The process for the sysex manufacturer ID registration is not only expensive
($200 per year) but also quite ridiculous. It is almost an invitation to
sysexquatting. Have you seen the Recently Assigned Manufacturer ID Numbers
page? http://www.midi.org/techspecs/manid.php
There are a lot
On Tue, Oct 6, 2009 at 3:25 PM, Fons Adriaensen f...@kokkinizita.net wrote:
On Tue, Oct 06, 2009 at 01:15:31PM -0400, Paul Davis wrote:
if aeolus is currently programmed to switch to stop setting S1, and i
want it to switch setting S2 instead, what do i, as a user do? what do
i have to know?
Fons Adriaensen wrote:
On Tue, Oct 06, 2009 at 07:26:18PM +0200, Ralf Mardorf wrote:
I don't know Aeolus, but usually a user should be able to change between
setting 1 and setting 2 by the GUI of the application, just by using the
mouse and without any knowledge about 0xf0 and 0xf7. The
Paul Davis wrote:
There is no such thing as 'aeolus being programmed to switch to
some stop setting'.
Aeolus has the standard MIDI banks/presets, which you can
load/save from the GUI and recall using the normal MIDI
messages. In most cases that's all that's needed. It also
can use control
On Tue, Oct 06, 2009 at 11:33:13PM +0200, Ralf Mardorf wrote:
For the default it would be very easy, 55 * on + 55 * off = 110 settings.
An universal control change is number 6. This could be used to sent by the
data byte 110 different numbers ;), resp. 128.
0 = S1 off
1 = S1 on
2 = S2
Fons Adriaensen wrote:
On Tue, Oct 06, 2009 at 11:33:13PM +0200, Ralf Mardorf wrote:
For the default it would be very easy, 55 * on + 55 * off = 110 settings.
An universal control change is number 6. This could be used to sent by the
data byte 110 different numbers ;), resp. 128.
0 =
On Tue, 2009-10-06 at 17:30 +0200, Nick Copeland wrote:
The issue with using the predefined CC such as #7 for other uses is
that if any GM controller sits on your MIDI channel it will use that
as a volume control, and it will be reinterpreted by Aeolus as some
organ setting. The result is
On Tue, 2009-10-06 at 23:40 +0200, Ralf Mardorf wrote:
Paul Davis wrote:
There is no such thing as 'aeolus being programmed to switch to
some stop setting'.
Aeolus has the standard MIDI banks/presets, which you can
load/save from the GUI and recall using the normal MIDI
messages. In
On Tue, 2009-10-06 at 22:45 +0200, Fons Adriaensen wrote:
On Tue, Oct 06, 2009 at 07:26:18PM +0200, Ralf Mardorf wrote:
I don't know Aeolus, but usually a user should be able to change between
setting 1 and setting 2 by the GUI of the application, just by using the
mouse and without any
Completely agree that SYSEX is where this kind of functionality should reside.
This use of 0x7d is a bit antiquated, no? The reassignment of 0x00 to indicate
3 byte
SYSEX ID means there is a bit more flexibility in the system. Currently the
following
are assigned:
0x00 0x00 0xXX American
On Mon, 2009-10-05 at 22:47 +0200, Nick Copeland wrote:
Completely agree that SYSEX is where this kind of functionality should
reside.
Using SYSEX more or less completely screws you for sequencing things
easily/nicely, among a zillion other irritating compatibility issues.
Not enough context
David Robillard wrote:
Not enough context quoted to tell; are the stops in Aeolus really too
complicated to be controlled via controllers and programs?
No: For 55 or so organ stops, you'd need 55 boolean controllers; this
can be easily done with NRPNs.
Best regards,
Clemens
33 matches
Mail list logo
