Zoom MS-70CDR

Started by Elantric, August 09, 2013, 09:54:43 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

sixeight

Quote from: Elantric on July 07, 2016, 12:53:29 PMhttp://arduinozoomms50g.blogspot.hu/

Thanks,  but I already know that the ZOOM pedals support midi program change messages.  I want to know if these pedals support sysex messages.

Elantric


A quick overview. Touchscreen, footswitch, expression pedal control via USB. No G5 mods needed.

The controller also works with other Zoom multi-effects and multi-stomp pedals. More info to come - stay tuned...




Zoom MS-70CDR G1on USB control - touchscreen, assignable knob and footswitches, expression pedals. Works with all G series (G5, G3, B3) 1 series (G1on, B1on) and MS series (MS-70-CDR, MS-60B, MS-50G) without mods to Zoom pedal.


Zoom MS-70CDR G1on USB control - touchscreen, assignable knob and footswitches, expression pedals. Works with all G series (G5, G3, B3) 1 series (G1on, B1on) and MS series (MS-70-CDR, MS-60B, MS-50G) without mods to Zoom pedal.

sixeight

#27
Great find,  Elantric.  It confirms that sysex control of the ms70cdr is possible.  Now I will have to find a good deal on the ms70cdr...

It also is very sophisticated project, with both a foot controller and a touch screen on a stand. I haven't been able to work out the technology Dave used for this project (arduino, raspberry pi, other processor)

More info can be found here:
http://www.thegearpage.net/board/index.php?threads/zoom-multi-stomp-multi-effects-usb-control-ms-70cdr-g1on-etc.1652836/

Elantric


sixeight

#29
Quote from: Elantric on August 21, 2016, 08:23:48 AM
You can check it out at: https://github.com/Craven112/ZoomControl
And check the wiki for more information: https://github.com/Craven112/ZoomControl/wiki

https://github.com/Craven112/ZoomControl/wiki/Android-app
https://github.com/Craven112/ZoomControl/wiki/Full-Version

This is unfortunately not the firmware of the controller with the touchscreen. This firmware of Craven112 only does patch change and includes no sysex. Here is a link to the video of his project:


I expect the firmware of the controller with the touchscreen to be rather large. I posted a message on thegearpage.net. Hopefully I will get a response from Dave (drdashdot), the author of the project.

As far as I can tell from the videos (see three posts back) this firmware has full control of all parameters with a graphic interface. Also there is a very nice way to make assigns from pedals, switches and an LFO (like Roland's wave pedal). It really is outstanding work. I would love to browse his code...

Elantric

#30
He developed this for Zoom G3/ G5 - but discovered it works with MS70CDR and G1x

Android tablet touchscreen app (*.apk) is here
https://github.com/Craven112/ZoomControl/tree/master/Android%20app

https://github.com/Craven112/ZoomControl

Contact me: cdeenen@outlook.com
https://github.com/Craven112/ZoomControl/wiki/Full-Version
Standalone Version
Craven112 edited this page on Jun 29, 2015 · 10 revisions

This is for the standalone version. For the full version go here.

Overview

The standalone version of the controller can be used to navigate through the patches of your Zoom. It has footswitches for the next and previous patch, the next and previous bank, and for the tuner. This video demonstrates the standalone mode of the full version of the controller. The standalone controller behaves exactly like that.



Disclaimer

I cannot be held responsible for any damages. This includes electrocution, lost fingers, lost gigs due to malfunction, etc. Everything is still in beta, so expect bugs and other problems. Use at your own risk!

Requirements

If you don't need the tuner, you can leave out the tuner switch and the mono jack.

Minimum requirements

Zoom B3/G3
Arduino Uno
Arduino USB Host Shield
Momentary footswitches (4x)
Resistors: 1x 10k for every switch
Optional

Momentary footswitches (1x)
LEDs (2x)
6.3mm Mono Jack
Enclosure
Resistors: 2x220 ohm for every LED
Arduino libraries

USBH_MIDI
https://github.com/YuuichiAkagawa/USBH_MIDI

USB-Host_Shield_2.0
https://github.com/felis/USB_Host_Shield_2.0


Setting it all up

Download and install the Arduino software
https://www.arduino.cc/en/Main/Software
and the required libraries
(here
https://github.com/YuuichiAkagawa/USBH_MIDI

and here)
https://github.com/felis/USB_Host_Shield_2.0

(guide to installing libraries)
https://www.arduino.cc/en/guide/libraries

Download the Arduino code here.
https://github.com/Craven112/ZoomControl

Upload the Arduino code to the Arduino (guide)
https://www.arduino.cc/en/Main/Howto

Connect everything to the Arduino
Connect the Zoom to the USB host shield
Done!

Arduino connections

Here's a schematic of the footcontroller:

Footswitches

Each footswitch is connected to vcc at one leg, and to ground through a 10k resistor and to the arduino at the other leg, just like at the blink tutorial. They are connected to the following Arduino (analog) pins:

PrevPatch = A0
NextPatch = A1
PrevBank = A2
NextBank = A3
Tuner/Mute = A5
LEDs

The leds are connected to an Arduino pin and ground, with a 220 ohm resistor in series. They are connected to the following Arduino pins:

LED Power = 5
LED Tuner = 7
Control

The footcontroller can simulate a footswitch push through a mono 6.3mm cable.

Sleeve = Not connected (ground is already supplied through the USB cable)
Ring = Pin 9
Tip = Pin 8
To go into the tuner:

Tip = Low
Ring = Low


The touchscreen is an Android app here
https://github.com/Craven112/ZoomControl/wiki/Android-app


--
must read all the URL links and pages

--
Standalone vs Full
Craven112 edited this page on Jun 29, 2015 · 3 revisions
Pages 7
Home
Android app
Compatibility
Full Version
Standalone Version
Standalone vs Full
Videos
Clone this wiki locally

    Clone in Desktop
The difference between the standalone and full version is that the standalone version does not need an Android device and a bluetooth module.

The standalone version can do the following:

Move up and down patches
Move up and down banks
Turn tuner/mute on or off
If you want simplicity and never want to upgrade to the full version, use the standalone version. More info on the standalone version

The full version can do much more, by using an Android device to control the Zoom. It has standalone functionality build-in by holding the tuner pedal down while the board is being powered up (keep holding the tuner until the power led turns orange).

If you want more control, go for the full version (it can behave like the standalone version if you like). More info on the full version
Contact GitHub API Training Shop Blog About

Smash

I'm moving on from my CDR pedal but am very fond for the Particle reverb (stable) mode effect. Sounds like it's a combination of reverb and delays - like a swelling delay on very short repeat into verb.

Does anyone know specifically what it does so i can try adn replicate from separate effects blocks?

sixeight

I managed to find a lightly used zoom ms70cdr. I want to use it after my Boss GP10 and see if I can control it from the VController... It should arrive sometime this week...

( . )( . )

#33
^ I'd also like to run this after my GP-10...

Could I use my MIDX 20 and MIDI Mate for independent patch changes of the GP-10 and MS70?

sixeight

Quote from: Chameleon on October 09, 2016, 01:57:45 PM
^ I'd also like to run this after my GP-10...

Could I use my MIDX 20 and MIDI Mate for independent patch changes of the GP-10 and MS70?

AFAIK the midx10 is not compatible yet...  But there have been some changes to the midx10 lately so I could be wrong. Maybe someone can test this...

( . )( . )

Update - I picked up a used MS-70CDR, hooked it up to the MIDX-20, and MIDI Mate, and it's responding to patch changes...I just hooked it up, and have no time to further explore tonight, but I was pleasantly surprised. BTW - I have not updated the MIDX-20 yet.

sixeight

Quote from: Chameleon on November 10, 2016, 07:20:54 PM
Update - I picked up a used MS-70CDR, hooked it up to the MIDX-20, and MIDI Mate, and it's responding to patch changes...I just hooked it up, and have no time to further explore tonight, but I was pleasantly surprised. BTW - I have not updated the MIDX-20 yet.

Excellent.  I have tried the same with my MIDX10, but that does not work yet.

I  am working on getting the VController compatible with the ms70cdr.  So far patch changes and patch names are working.  But I haven't figured out how to read effect types yet.  The sysex is a bit different from the Zoom G3... And there are holes in the implementation,  as there is no editor...

shawnb

This is tempting - I've been looking for something compact to use after the 6Appeal, specifically for reverb & chorus & delay...

Time to look at the manual.
Address the process rather than the outcome.  Then, the outcome becomes more likely.   - Fripp

( . )( . )

#38
...another update...

If you want to see the preset names appear as they do in memory mode on the MS70-CDR using MIDI, you have to manually put the unit in memory mode and click the main footswitch once each time the unit is powered on. If you don't do this (and it's really no big deal), the presets will scroll according to patch change numbers, but the display will read as if it's in effect mode. This doesn't matter if you've set your patches on all your devices as you want them.

The main limiting factor for me is that both the GP-10 and MS70-CDR only respond to MIDI channel 1, so each patch must be set up accordingly...still a learning process. Ideally, I'd like to be able to access the GP-10 from the bottom row of buttons of the MIDI MATE and the MS-70 from the top row on a per bank basis, or even better, have the effects in the MS70 respond on and off as control change messages, but this isn't possible. I must say though...the unit really sounds good for for ambient tones and fullness, especially for its price.

vtgearhead

I wonder what goes through the head of the software designer when they decide that a single, fixed MIDI channel is somehow the correct choice?

CodeSmart

Quote from: snhirsch on November 20, 2016, 06:41:19 AM
I wonder what goes through the head of the software designer when they decide that a single, fixed MIDI channel is somehow the correct choice?

Considering adding a virtual MIDI channel option to the MIDX firmware.
Example: If set to 3:1
All outgoing USB packages at channel 3 will be modified to channel 1 just before transmission.
All incoming USB packages at channel 1 will be modified to channel 3 just after reception.

This setting would be individual to each USB port on the MIDX-20 allowing separate control at separate channels even though they both operate at channel 1.
Good?
But I got more gear than I need...and I like it!

( . )( . )

#41
That would be really cool Robert. I think a lot of  MIDX users could greatly benefit from it. The GP-10 and ME-80 only respond to channel 1, and I'm assuming the GT-1 and GT-001 do as well. I'm sure there are a lot of other USB devices that only use channel 1 also.

I'm assuming you could make the 3:1 example work from/to the MIDI DIN's to/from each of the USB's... 

vtgearhead

If you still have room left in the EEPROM, then by all means!  If you get a chance, take a look at the iConnectivity mio2 documentation.  For a unit that's nominally a pair of USB<-->5-pin bridges it has a wide variety of filtering and remapping features.  I was quite surprised to find all that flexibility after buying it to do simple bridging.

sixeight

I have attached my MIDI sysex implementation guide for the MS70-CDR. I hope it may be useful to somebody.

Elantric

Excellent resource!!

thank you for sharing!

sixeight

Here is a wonderful midi controller for the MS70-CDR that should be available soon.





http://www.thegearpage.net/board/index.php?threads/zoom-multi-fx-usb-midi-controller-update.1776550/

I know from first hand e experience how hard it is to develop this kind of hardware and software. There are some great ideas implemented here and the user interface looks great too.

Elantric


Redvers

I did the update, it was fine, kept my patches and everything. Can't remember if I put it into update mode first in the settings. Worth doing either way. The most promising effects (pitch and synth based) aren't all that great in my opinion but the comps, phases flangers and filters are really good.

I've been thinking about this sysex implementation, If you could intercept the data between the zoom and a PC, could you swap the device id, so the PC thought you had a different version, and then run an update for another pedal?

Elantric






Zoom Pedal Interface now controls all three recently updated MS pedals.
Lots of testing over the coming week (and then look out for additional capability to be announced...)

https://www.facebook.com/zoom.control/

Elantric

#49


http://www.g200kg.com/

The patch editor for ZOOM MS is also compatible with MS-60B, which makes it compatible with 3 types of MS-50G / MS-60B / MS-70CDR.

In fact MS-50G and MS-70CDR thought that the format of the data was almost the same, probably 60B would probably be something similar, but 50G and 70CDR had 6 simultaneous use effects, while 60B was 4 , The data format is slightly different due to this.

The details are written here: https://github.com/g200kg/zoom-ms-utility/blob/master/midimessage.md

I do not understand why I bothered. I thought that there are differences in DSP capabilities, etc., that the number of effects is 4, but it is not the same, even if you compare by the number that can handle the same effect that is also included in other models. Because it is for the base, it is good if there are only four, is it normal?

After a while you are worried about
* It is not verified whether it works properly even with the old version of the farm, and it can not be reverted if the main body is updated
* Behavior around auto save does not link with the main body. It is still unknown whether we can get around this condition
* New effects are likely to be "DSP full" because there are many heavy guys so I can not quantitatively display this neighborhood


----
Usage

Launch
Connect PC / Mac to MS-50G / 60B / 70CDR via USB
You should use Latest Chrome. On Windows, unplugging the USB while running may cause freeze (this will be fixed on Chrome 60). Once close all Chrome window if you have MidiPort detection problem.
Press accept if 'MIDI device' permission dialog is displayed (press keyboard icon on right edge of address bar and retry if you make a mistake)
After splash screen, all patches and effects with parameters are displayed
AutoSave
Autosave mode is defaultly ON. This is not automatically linked to device's "AUTOSAVE" mode. It is recommended to set according to device's "AUTOSAVE" mode.
In "AutoSave On" mode, patch replacement etc on the browser will be automatically stored to the device's memory
If AutoSave is Off, patch replacement etc in the browser is not stored to device's memory until pressing the Save all patches button or Context-menu - SavePatchToDevice for each patch.
Note that device's "AUTOSAVE" mode is independent to this behavior. A patch may be stored to memory by operation of device itself.
"Save all patches" button will force all 50 patches to be stored to device's memory
Patches
Click patch name to select
Right-click (ctrl + click for Mac) or patch number button will show Context-menu.
From context-menu, Copy / Paste / Rename / etc patches
Patches are draggable to another position for overwrite / exchange
By context menu - ExportToFile / ImportFromFile, each patch can be backup / restore to local file
By context menu - SavePatchToDevice, force each patch to be stored to device's memory
If you want to choose export directory when 'ExportToFile', I recommend change Chrome setting of setting-detail-download confirm folder
Effects
Click effect name to switch effect / bypass
From right-click or number-button context menu, each effect can be add / move / del
Each parameter can be edit by drag (coarse) / shift-drag (fine)
Mouse wheel and Shift + wheel are also available to value edit
Effects are draggable to another position to change order
Bank
By Export Bank / Import Bank buttons, all 50 patches can be save / load as zipped one file.
It can be edit as normal. Zip file if you need.
When a bank file is selected from patch file loading, a list in the bank file is displayed, and one patch can be selected from among them.
Keyboard
'A' - 't': patch 1 - patch 20, 'A' - 'T': patch 21 - patch 40 '1' - '9', '0': patch 41 - patch 50
Keyboard 'F1' - 'F6' is assigned to On / Off each effect.
Keybeard 'F9' is assigned to Tuner mode On / Off.



https://g200kg.github.io/zoom-ms-utility/


https://github.com/g200kg/zoom-ms-utility