mungewell
mungewell
Noted the Drum replies (0x32) in double bytes, so maybe the Pro just uses 2 bytes for selecting preset `$ amidi -p hw:1,0,0 -S 'f0 00 21 1a 02 03...
Hi @SeanLuke personally I never got my hands on a Pro, so haven't done any real investigates. Above was from discussion with another user... Willing to offer any help/encouragement I...
> Okay, here's what I have ascertained at first glance. That's some pretty awesome info! It might be helpful to identify/hilight the 'CMD' byte(s), and if you haven't noticed the...
> Thing is, the unit emits CC, and the editor also emits CC. And you're right, they're not fine enough! But I don't know what the sysex equivalents should be....
> > > Can you provide a hexdump/example? > > Sure. After loading patch 0 bank 0 into memory, here's the current memory dump: > > ``` > 0000 F0...
@Colatino Nice work on the video and your project!
I have a GCE-3 and in theory could emulate the A1Four to save them off... however I am travelling for the next week. A simple script could grab the patches....
Sure do... is this what you wanted? GCE3-as-G5n ``` $ amidi -l Dir Device Name IO hw:1,0,0 ZOOM GCE-3 $ amidi -p hw:1,0,0 -S 'F0 52 00 6e 55 00...
Sure do... is this what you wanted? GCE3-as-G3n ``` $ amidi -l Dir Device Name IO hw:1,0,0 ZOOM GCE-3 $ amidi -p hw:1,0,0 -S 'F0 52 00 6e 55 00...
BTW, do you know about the 'decode_screens.py' script. This gives a representation of what's on the device's screen.