I did, of course, but although I did manage to glean some information, it must be said that these guides are not exactly comprehensive, nor do the linked topics really cover what I need to know in sufficient depth.
In fact, I spent the time waiting for my Mod device to arrive reading through all the guides in preparation - knowing that there was likely to be a steep learning curve ahead.
But for example, the menus accessible on the Mod device itself are more often than not skimmed over, without at any point showing the content of the sub-menus or making any attempt to explain their content.
The subject of MIDI control assignments is a case in point, making finding reference material specific to these topics difficult to access, and making it necessary for me to contact more knowledgeable members like yourself for help.
But in my opinion any guides should be well written with all spelling and grammatical errors corrected before posting in order to make the information presented easier to understand and assimilate, and should certainly not be allowed to turn into an ongoing conversation.
In the case of this specific thread, it has become far too long and convoluted, since several of the suggestions from other contributors have been taken up by the OP but not actually integrated into the guide itself - meaning that the guide should have been kept separate from all these comments, then updated in order to integrate any new ideas.
Since the guide was not formulated in that way it is certainly not as useful as it could be for anyone new to working with these devices, and one should also take into account the differences between different sorts of user - for example guitarists like myself may have a very basic grasp of MIDI, but no understanding relating to programming actual MIDI commands - as opposed to the typical keyboard player who will undoubtedly have considerably more experience with this type of thing.
In my opinion this guide should take these different levels of experience into account, and not assume that everyone participating in the conversation has an equal level of understanding of these concepts or experience working within the MIDI framework.
It may be clear, but as I said - far from comprehensive. For example please explain where there is any mention of Program Change messages found in the Cube Suite app which corresponds to this section of the wiki:
This means that if PC 1 is issued, the first pedalboard will be loaded, if PC 2 is received the second pedalboard will be loaded, and so on.
I believe that a PC command is just a different type of CC command, but have no idea which CC command I need to select from the menus on the Cube Suite app?
I think I understand how to assign CC commands within the individual plugins within the web interface, but not how to define them on the Chocolate foot controller via the Cube Suite app. That is what I am unable to get my head around. How can I access the corresponding PC commands within the menus of the app?
I just need help setting up the Chocolate so that it actually connects to my Mod Duo X and I can use the MIDI display plugin in the web interface to check which MIDI commands are being received by the Mod device. That would be a start. Once I have managed to establish the connection between the two devices I can then start to experiment with mapping different parameter assignments to the Chocolateās foot switches. But I have been unable to get that farā¦
I am able to open the MIDI tab on the web interface, and I can see a MIDI device listed, which I am guessing is the USB dongle I have connected to the Mod Duo X USB port. I can also access both the dongle and the Chocolate foot controller on the Cube Suite app, and both of these are successfully paired. But aside from the dongle appearing in the MIDI tab of the web interface there appears to be no actual communication between the USB dongle and my Mod device. Iām obviously out of my depth here, which is why I am reaching out now. So can you help?
I particularly wanted to use that mode, because it would allow me to send PC messages on one channel with the first press, then a second channel on the second press - the idea being to be able to assign PC commands to either change banks, or individual patches on the Mod Duo X, or select specific snapshots.
I checked the midi output from the MVave Chocolate using a midi app on my iPad, so I can see that it is sending the PC messages correctly - the problem is that when connected via the MS-1 midi USB dongle there seems to be no communication with my Mod Duo X.
The problem is that as soon as I have the dongle plugged into any USB port it immediately pairs with the MVave Chocolate, and wonāt pair with anything else, and the only way it it will connect to any of my devices is by using the Cube Suite app, but I really donāt know whatās going on, because the USB A or B midi adapters wonāt connect unless I use the Cube Suite app, and in the case of my PC not even with the app - this is driving me nuts!!!
Iāve been in touch with the Amazon vendor, and I also wrote to MVave via their webpage, but Iām not very hopeful that they will be able to help me sort this out.
Even if I connect the MVave Chocolate directly to the USB port of the Mod Duo X it seems to do nothing, and there is no indication on the Mod device when a BT or USB device connects to it. Using the web interface with a midi monitor plugin I see nothing happening either.
I also update the firmware on each of the devices, but still no joy.
you are able to connect via bluetooth to your ipad
when the USB dongle is connected to the MOD, the chocolate pairs with the dongle but no midi is detected on the MOD
seems like a broken dongleā¦ Have you tried to plug it on your PC to check it?
Also, since there are many people here for whom English is not the first language (myself included), I recommend using short sentences, summarizing the information in a less verbose and more schematic way. It will help you get assistance
Hi. The MS-1 midi USB dongle doesnāt work that way - from my understanding it is simply a BT dongle. If you try plugging it into the PC it is recognized, but not as a BT device.
Regarding the verbose nature of my contributions - I suffer from aphantasia, so since I am unable visually conceptualize anything (no mindās eye), I actually need to think in this way in order to actually remember anything. Thatās because I use an internal dialogue which contains as much detail as possible, since without that I am unable to conceptualize ideas or remember anything.
[This is also probably why it is so difficult for me to follow instructional threads which a poorly constructed such as this one, and also why I requested a concise and simplified version, focusing on one setup specifically, and without the ever-growing list of commentaries ]
Unfortunately this translates into me expressing myself in a similar way, so when I write it also automatically influences that. I do apologise, and Iāll do my best to simplify my posts in future. But please understand that since I actually think this way it will not be easy for me But point taken anyway.
These are absolutely separate types of MIDI messages.
PC is not a type of CC.
CC is usually used to tweak parameters and turn virtual knobs.
PC usually means choosing some sound banks or presets.
P.S.
It is 3am here, my eye had catched this sentence and I am answering to this particular sentence without paying attention to any context around it, hoping that it would make sense anyway.
I had no clue at all when looking for an affordable footswitch solution for supporting my looping guitar exercises. The chocolate controller seemed to meet my expectations. It was quite interesting to set this up as the documentation coming with it is pretty limited. So as a non expert, Iāve had a hard time. However, now the gear is working and i am perfectly fine with what it does; a very good value for the price. Thatās why I want to share some of my experiences that may help others.
First thing I had to build an understanding:
This MIDI controller sends out MIDI commands via three ways at your choice:
Bluetooth: I did not manage yet to connect it to a windows pc; that is still be be found out. However, on a linux machine, connection went fine, and the device is shown as āFootCtrlā capture (out) and playback (in), respectively. This seems to be a standard as I did not need to intervene manually.
USB: This worked under WIN 11 as well as under Linux. In both cases, the device identifies itself as āSINCOā, again capture and playback.
TRS cable: It is documented, but I did not try this. So I canāt comment.
The MIDI controller itself is configured via
USB: This is achieved via the software āCubeSuiteā. This process is documented quite well, so I will not repeat this here. I downloaded the app, I got it to work on WIN11 and even on linux (via WIN wrapper āwineā). In both cases, it detected the USB connected device and I had the well described interface to configure the four knobs to send my desired MIDI signals.
I am using this setup for steering my software looper, e.g. with foot driven commands ārecordā, āoverdubā and āundo/ redoā. I could get around having to dig too much into MIDI as my software looper has a learning function; I guess most loopers out there have that. So the only thing I had to do was to configure four different MIDI commands for each knob, start the looper app and the learning function for each function (ārecordā etc.) and push the respective knob.
I have the cuvave cube baby and the mvave chocolate plus on the pedal as you know are 3 presets they can be live or preset mode then how do you save more different patches with the chocolate controller I have the cubesuite app on my laptop and the controller showing the option s available with the commands like cc and things but i havenāt got a clue how to assign presets can anyone help mene er used midi commands before help would be greatly appreciated.
But point taken anyway.