开云体育

Hi Karl ! A bit O.T. but ... Assigning MIDI CCs to Xpander-parameters like VCF cutoff and MIDI volume works on my Xpander uising the MIDI Controls page. The limitation are the modulation busses,-

I agree, changing Xplorer to do that should be trivial. However, anyhting you can do from Xplorer you can do from the Xpander, except for random patch generation. We dont have the Xplorer source

Hi Tony,I have written tons of assembly code for a Motorolla 68HC11 which has a similar instruction set. I would be willing to help with this project any way I can.I would love to "enhance" the

Tony Cappellini cappy2112@... [xpantastic] wrote: I don't know how to. It shouldn't be hard to program Xplorer to edit the program automatically. Cheers, Jeremy.

Hi Jeremy Can't you generate a random patch with Xplorer, then just edit it mnaully with the program to do that? <xpantastic@...> wrote:

Hi folks, I'm willing to pay $100 to the person who can generate a random patch, and make the patch play from the keyboard instead of just a one-shot with no scale. This would be a modification to the

If I can get it disassembled- correctly I will. I don't have any serious plans other than looking through it to see what might jump out. I don't know if I'll get around to adding any comments, since

Hi Tony, if you're willing to share, I'm curious to know what your plans are for the code?

I had tried to do this to the VS but came up short... I've interleaved the ROMs and the single file works in a VS emulator, but I cant seem to figure out getting it into assembly in IDA. Any tips? You

I've not done this for the Xpander, but I have for the Prophet VS. I combined the roms into one file using Python - relatively simple script to load a byte from each file and interleave them. I then

Has anyone here attempted to disassemble the XPander or Matrix 12 ROMS? If so, where is the dissembled source code at? If not, what would you recommend using getting the ROM bin files that are

Hi, you should look at the XpanderSinglePatchViewer.cpp, it is self explanatory there. you have OBWORDS_DATA_LENGTH of data to be "repacked" as double byte values, which is not required of course for

I have to correct my own calculation, however it still doesn't add up from what i can see. 196 *2 = 392 bytes, including the patch name. Add the first 6 bytes for the sysex command, + 1 EOX, 399

I think the comments explain it: "188 double bytes data for the values and 8 double bytes for the patch name" What is meant by "double bytes" is some form of encoding bytes (8-bit values) into sysex

I'm trying to understand the calculations that the single patch browser (included with Xplorer) ueses. Looking at XpanderSysEx.h // Single patch data sysex length is 399 bytes // 6 bytes for sysex

You can use a razor blade to carefully work under the cap and pry it up. That is what I do on old OB's. Don't slip though. <xpantastic@...> wrote: -- Patrick

Hi. Is there anyone who knows how to safely open up an Xpander panel switch, i.e. remove the switch cap? /M

Anybody?

Hi, The project will be released as open source one day. For now I don't have time to cleanup things and migrate the history to Github or similar repository, maybe I will be able to work on it in the

Thomas Dial dialtr@... [xpantastic] wrote: One feature I would like - and would pay for - is for random patches to have an option to keyboard track so it's playable and not a one-shot sound. Can