What about Zoom G2-Four pedals and their effects? #64
Comments
|
You mean the G2 FOUR, not the older G2. Do you have one and willing to explore? |
mungewell
changed the title
|
Assume that OP means the G2-Four, so updated the title. As I understand Zoom has only released app for iPhone/Android, and does not support these pedals via PC. I saw note that iPhone needs a special cable. I can't image that that Zoom would use older format with the fact that these pedals implement IR modeling. Personally I considered getting one (B2-Four though), but haven't found the right excuse to spend the $250... anyone want to sponsor? LOL |
|
I have B1 Four only. My understanding is that G1 Four acoustic modelling is using some short IRs already. At least this is that Zooms tells. Can be cool to find arrays containing IR data and write simple utility to replace them with user IRs, it don't require any code changes. |
|
@maximka1812 The At present it is set up to decode/encode TBLs as float32, but trivial to change to some other format. The '--list' option will dump a list of all the symbols that exist, if one is called 'COOL_IR_TBL' that would be a suspicious target :-) |
|
I have B2 four. I'm interested in this project because I only have Android smartphones that doesn't support zoom pedals except G1/G1X. |
|
@Licarde: Do you have a PC (preferably with Linux on it) or such to try out MIDI connectivity? At least to see if the pedal presents itself as a MIDI port. |
|
@Licarde Hi, I don't know how familiar you are with Midi so please excuse if I'm too simple... Basically the Pedals are controlled via midi packets, normally a PC would send a series of SysEx packets to query/control the device settings. Midi is normally 7-bit data, SysEx is one of the exceptions where the packets starts with 0xF0 and ends 0xF7. The first 3 bytes of the packet are an 'address', the reset are vendor specific. We see that the 4th byte seems to be a 'command' with following bytes being data We have figured out that all the pedals (we've tested so far) respond on the same 'address' and thus can be queried/controlled. For example @nomadbyte had me run the following commands on my GCE-3, whilst it was pretended to be a number of pedals.... ie. 'cmd_44' I don't know off the top of my head how to send SysEx midi from an Android phone, but it must be possible.... I guess the first thing is to work that out, and then have you try the same on your B2-Four pedal to see if it responds the same. |
|
I'm a very beginner at both MIDI and Python. Please excuse. I have Windows only. But if I'm in college, I can use Ubuntu in my lab. |
|
|
Cool! Can you dump these too? All these are info commands, no changes. |
|
Here you are. |
|
Thanks, lots of new details. Here's a bash script to list the files on the pedal's internal flash: Copy the script's text into a file, then make it executable It lists the file names, one per line. |
|
|
Wow! Thanks for the list, at least we now know what's in the box, so to speak.
Some notes:
|
|
B2 FOUR has 300 user patches, 10 patches per bank (30 banks). Here's how to dump a selected patch and the current edit buffer. For the test, you need to select some of preset patch, say, "001: DamnTime2022" and then dump the data, so we could compare the patch/buffer size. If you want to select a patch directly, just pass it's Bank (MSB, LSB) and Prog MIDI codes. It's just common MIDI (not SysEx), so should work even without Editor Mode, well, it used to. |
|
WOW! Here I am on MST, and when I wake up it's like Santa's Elves have been super busy :-) @Licarde Thank you so much for this testing and the information you have provided is super helpful. It would seem that the B2-Four pedal is a very close relative of the B1-Four, and the fact that it is responding to these commands suggests that it would work OK with the Python scripts as they are. The scripts also run with Python on Windows, I used the https://github.com/mungewell/zoom-zt2/releases The scripts need the Construct module, and use WX-Windows for their GUI display. You mention that your college's lab run Ubuntu, do you have scope for installing additional Python modules? BTW what are your interests/hopes with/for this project? Are you studying programming?? |
Although we can't (for copyright reasons) share these files, I did upload a 'master list' of all the effects that are referenced in Guitar-Lab and this includes the MD5 sums of the ZD2 file. https://github.com/mungewell/zoom-zt2/blob/master/zoom_fx_AllZDL7/master.txt The GUI script contains has a 'download' button on the 'files' tab, if one or two ZD2 could be manually downloaded and checksum'ed that would answer that question. |
Well, it's still a new device. So, it'd be more prudent to keep the initial analysis in read-only mode until we figure out what's the same, what's different. It's tempting to use the zoom-zt2 tool, yet maybe it would be better to use the |
|
@mungewell @nomadbyte |
|
@Licarde: So far B2 FOUR protocol appears very much similar to that of G1/B1 FOUR model family, but we still need to figure out some details, such as:
Eventually, we may gather enough details to come up with some alternative editor for this model. |
|
"DamnTime2022" |
|
Here it is, more differences:
Again, looks like similar PTCF format to one used with G1/B1 FOUR (G5n platform), yet different. Ok, done with the patch info for now. Thanks to @Licarde we're learning bit-by-bit about the multi-effect platform evolution! Once you've the access to |
|
@nomadbyte I started adding ability to automatically de-pack from SysEx dumps, and noticed that my code uses different 'cmds' to read patch data. Should these be updated?? [edit] Yes... see #68 |
|
Happy New Year! Hope it started well for all of you here. @Licarde: Any progress with continuing the B2 FOUR exploration dumps? |
|
@nomadbyte I am very busy this month. |
|
@Licarde : Understood, no problem. Life priorities require attention. Join back in, when you'll have a chance! |
|
I'm currently trying to get B2 FOUR output from the following SysEx commands. All deal with patch details. Say, select the first preset '001 - DamnTime2022' and then do: @Licarde Any chance you could try this out? |
|
Recently, I am able to help with this project again. Other, I tried thammer's 'sym.bios.is' and was able to save and load the patch! |
|
@Licarde If you are on windows you can run the scripts there too.... need to install a few modules (construct, python-midi, etc). GUI also runs with WxPython. Should also work on Mac, but don't have confirmation on that... If you want to try sending SysEx data you can use MidiOx on Windows. I think that we are getting close to pushing a new release, as we've got confirmation that we can work with the MS+ pedals. |
|
OK. I tried to sent the data via MidiOx. |
|
@Licarde thanks for getting back and joining another piece in this puzzle. For the most part it's clear that B2 FOUR is also using the ZD2 format and somewhat modified yet similar PTCF format for the patches. Same likely goes for the SysEx File IO, so it should be possible to adapt @mungewell tool to download files off the pedal. However I would not rush with installing/removing effect files yet, until we can figure out the contents of the Here's another SysEx to dump to figure out the internal flash size: |
|
|
SysEx:<60 29> ==> B2 FOUR internal flash capacity: 5.7MB |
Are they also ZD2?
They have some new multi layered IR cabinets and stuff.
The text was updated successfully, but these errors were encountered: