5 Nov
2004
5 Nov
'04
8:23 p.m.
On fre, 2004-11-05 at 22:48, Paul Davis wrote:
Wait a second while I google for sooperlooper ...
...
...
Mmmm ... It looks to me like you haven't got a massive amount of
parameters (like ie the DX7?)
I never had a problem with parameter changes coming in at the midi port.
Problem is that I have no sysex ID [1]
(And yes, I did notice that there is an implementation of DX7 for dssi.
It relies on sysex for individual parameters.)
32 something programmable knobs (with multiple destinations) on a
usb/midi surface is probably more than you'll ever have time to
understand (nor me), but when it comes to setting up the whole sheebang,
we'll both want to have access to *all* parameters. This is where the
native UI has its place. You'll do the setup off-line, therefore races
are a minor concern.
*1) Yamaha is a registered midi vendor, and have their own sysex
preample. We have not!
mvh // Jens M Andreasen
I like the idea
of UI being a seperate app, but ...
I am into a similar idea, although by using memmap, but, as I understand
it, that won't work with your scheme?
Hmmm ... I have almost nothing going on between engine and UI except for
that UI might have decided to update the patch (and engine might via
midi have decided to change to another patch) ...
follow sooperlooper - the UI is the MIDI connection, and tunnels it as
OSC to the engine. no races.
--p