I'm afraid that controls to store a performance to memory, and any sort of polyphony monitor are not exposed by the MONTAGE MIDI implementation, so I won't be able to implement either of those features.
That was a bit cryptic wasn't it..?
I'm working on a new 'mixing' editor, separate from the main sound design interface. I'll be built around the concept of channel strips.
At present, I'm planning to expose the following controls for each part:
Part switch
Part arp switch
MIDI channel...
Aah okay I understand. No, KDx is a sound and live set editor rather than a performance manager so it doesn't currently expose those sort of controls in a standard interface.
That said, some sort of mixing mode interface might be a nice addition to KDx.
@Mallory50 I've just taken a look at this on my M8x with KDx, and I see the following waveform numbers:
52: CF3 Flat Soft St
52: CF3 Flat Soft St
58: CF3 Flat Med St
64: CF3 Flat Hard St
50: CF3 Flat Sw St
2156: VP Strings St
2162: Dark Light
2160: Syzzle Strings
... which all appears to be...
No, you'll find copy/paste buttons on individual elements/operators/oscillators while working within KDx, which allows you to copy and paste the settings from one to another.
KDx Live Sets can access library performances - they just need to be synced in the same way as your user performances were. Add a library performance to a user live set, load that live set into KDx and it will prompt you to sync again, then just go through the sync process, including your...
It sounds to me like the system might be trying to set the slider/knob values before it has set the mode value, which would prevent the controls from accepting the correct values. I'll dig into it and see what I can find.
I have a couple of new features to announce today.
MIDI Router
The first is the direct result of a suggestion from @chrishonmusic, and I have called it 'the Router'.
By enabling the 'ROUTER' control in the header, KDx will intercept any standard incoming MIDI messages from any connected...
I'm working on a test script to try to diagnose the problem with the Android devices. I am a little foxed at the moment, because Chrome on Android should support the WebSocket connection in the same way as iOS, but the test script should give us more info. Watch this space.
It's unlikely to be wifi security settings, but it could be the Samsung devices failing to connect to the WebSocket that is the foundation of the relay system. I'll look into adding some sort of more meaningful error message so we can work through this problem and find the cause.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.