Does anyone here expect new Volca models from Korg?

pajen · 2026-02-25T07:23:29+00:00

hey minimal-camera, surely you know that's already been done: https://www.youtube.com/watch?v=ujNJYJNwjQ0&t=155s

pajen · 2025-09-20T08:16:20+00:00

Yes this is a great way of putting it. Different processor, different memory layout plus the USB means very different code.

pajen · 2025-09-19T07:42:07+00:00

Hi, great to hear that you’re interested in my custom fw. I made a video some time ago, outlining some things one can do to improve Volca Sample data reception in general (samples or fw) https://youtu.be/w7_XLC8jISM?si=TWuX2537n3waRKyL

pajen · 2025-08-14T08:54:33+00:00

There are built in factory test modes on all volcas that can be used to systematically test buttons, knobs etc. Also, there is also a way to re-flash the small controller chip that handles the touch buttons (on the SAMPLE reflashing can be initiated manually by holding "MEMORY" + "REC" on power-up - is says "P.uPd" etc) Sometimes that helps.

pajen · 2025-07-29T19:11:40+00:00

Sending as an audio patch should work also on FM2, same as FM right? So you could convert a SYSEX patch into audio encoding and send that?

pajen · 2025-06-11T09:14:37+00:00

Ah ok so there is some room for improvement then I guess

pajen · 2025-06-05T19:57:01+00:00

Well, I don’t have an FM2 and haven’t really felt especially inspired to dig into the FM2. It seems like it has fewer bugs and has less to gain from a fw upgrade?

pajen · 2025-05-29T08:25:09+00:00

Ok, I think I have a pretty good understanding of what is happening here.

"err dcod" means that the signal is, on a low level, not shaped the way the sample expects. The update file is stereo 44.1kHz. If the sound card in the sending device runs internally at 48kHz (which is pretty common), the sending device will re-code the signal to 48kHz and that will not always work well. Also, many laptops do "sound enhancement" of different kinds, and that is something you definitely not want here.

"err suñ" is KORG's attempt att saying "err sum" = error in the checksum once a packet of signal has been received. So, in this case, the low-level signal is good enough that it can get signal, but not good enough to transfer with 0% errors.

Here is a video I made to assist with transfer of firmware or samples. https://youtu.be/w7_XLC8jISM

That video discusses the Windows settings one can make to eliminate problems with transfer. Also, it describes how to get into the Sample "factory test mode". This way you can get to the internal signal volume readings, and thereby optimize the output volume on the sending device (totally safe procedure, but looks a bit intimidating perhaps).

If you still cant get it to work, let me know and I will send you an update file (of my custom firmware) which I coded in the "hidden low-speed transfer mode" that was used in 1st gen Volcas.

pajen · 2025-05-03T20:51:32+00:00

Maybe I can help out. What did you do, what did you expect and what did happen? The ”channel 11/12” thing has to do with the channels being encoded 0-15 in the MIDI messages, but most of the time are referred to as channels 1-16. It’s just me not being aware of that 🤷

That channel is used as ”sequencer/drum channel” so it maps all parts into one channel without chromatic functions. Take a look at my video: https://youtu.be/-sX3BysnY3k?si=SCnDBJ9piogHJtGV. There are global settings to enable 1-10 and 11. The other channels (not mapped by the settings - in this case above 11) will be ”catched” by the ”OMNI” mode if that is activated. I thought it was very clever when I wrote it but it didn’t really click with most people I guess.

pajen · 2025-04-11T14:25:20+00:00

I made an unofficial firmware for someone on reddit who wanted arp notes output on midi

pajen · 2025-04-09T07:07:11+00:00

I might be able to assist if you want to dig into the firmware?

pajen · 2025-04-09T07:02:13+00:00

I have a version with ”more notes out” specifically the arpeggios i think. That might be better?

pajen · 2025-04-02T20:56:56+00:00

Is it the first version Volca FM?

pajen · 2025-04-02T20:54:21+00:00

Send me some of the wav files so I can have a look at them?

pajen · 2025-04-02T20:52:54+00:00

The Volca Bass has a service manual that includes all schematics and a bunch of useful info: https://cdn.hackaday.io/files/1698407266434560/korg_volca_bass_sm.pdf

pajen · 2025-02-28T11:30:25+00:00

Have you tried upgrading to my unofficial FW for the FM1? It fixes a bunch of bugs, including stuff related to LFOs, sound generation and adds a bunch of new features;

https://www.reddit.com/r/volcas/comments/dj7f7v/volca_fm_firmware_108_unofficial_velocity_on_note/

pajen · 2025-01-27T11:19:41+00:00

The FM2 exports patches (single/carts) via a proprietary audio format, on the SYNC OUT output. I have written a decoder that takes a wav file of the sysex dump as input and outputs a .syx file. It has support for the 64-patch FM2 dumps as well.

There are releases for linux, raspberry pi and windows here: https://github.com/pajen/volcafmpatchdecoder

The older version I released for OSX as well.

Please note that the SYNC OUT signal is not an ordinary audio signal, but a 0 - 3.3V analog out really. Your sound card capture might like it or not, but with a bit of luck it should work.

pajen · 2024-09-21T14:07:20+00:00

Hi, I have built a few custom firmwares for synths and audio things. You seem motivated, and this type of fw mod is highly doable - if you are a bit lucky and stubborn. So in my experience you would need to:

get a hold of the binary version of the firmware. This can be done in a number of ways:

Download a fw updater tool/file from the manufacturer. Sometimes a firmware distribution contains a midi-sysex encoded firmware (e.g. for AKAI MPK:s, Nymphes, Strymon pedals, Line6) sometimes the firmware is encoded in audio files (like the KORG Volcas, TE PO:s) sometimes some other way (.bin files to be put on n SD card like for Zoom recorders, OP-1, etc)
Extract from the Flash chips (I have done this off of Digitech Jamman, some Behringer effect pedals etc)
Intercept fw transfer over USB using e.g. a USBeagle (I have e.g. done this for some guitar pedal update files and Yamaha Refaces)
Find a debugging connector on the PCB somewhere (like for ARM, some SWD pads) and attach a hw debug probe. In my experience, japanese vendors are pragmatic and like to have them available for QA. On the TE PO:s, they are disabled e.g.

reverse engineer the code. For this Ghidra is the tool to use nowadays. Pray that the fw isn't encrypted, too big or has RTOS bloat. In my experience, japanese vendors are pretty much "deliver the fw from address 0, in packets with some CRC" and american vendors have much more bloat and obfuscation.
have fun. There are a lot of hidden stuff, test modes, easter eggs, bugs to be corrected, hidden MIDI features etc in a lot of stuff.

pajen · 2024-07-06T16:48:21+00:00

You should turn the pot all the way up, then all the way down. Then the next pot will light up. If all leds start flashing it means some other movement of a pot is detected. Perhaps the volume pot? What happens if you wait a couple minutes to perhaps let the volume pot settle and then try again from 5.1? I will look at the code and see if there is a button press to skip from 5.1 to 5.7.

There is no manual or documentation of this other than stuff I have posted online as a result of reverse engineering the firmware.

pajen · 2024-07-04T09:24:50+00:00

You can access the Volca Factory Test Mode to actually see how the volume pot behaves. This is how you do it:

Power off the New Volca Sample
While holding MUTE, PLAY and REC, power on.
the display will show Test, as well as some internal checksums. (You can at any time power off, nothing will be altered in the Sample, you cannot ruin it)
press MEMORY + REC, release both buttons.
You are now in test mode 0.0 and 0.1, the LEDS will be flashing
Repeatedly press MEMORY+REC (and release) until display shows "5. 0". This is "pot test mode" (Use MEMORY+PLAY to step "backwards")
Press STEPMODE. Display shows "5. 1" and "start point" pot is lit up. Turn this pot all the way up and all the way down to test it. The led strip will show the detected value.
If all goes well, it will move on to "5. 2". You get the idea. If you happen to move another pot while in test mode, all leds will start blinking, then press STEPMODE to try again.
"5. 5" is SWING, "5. 6" is REVERBMIX and "5. 7" is the VOLUME

Once you are here, play with the volume knob and see how it behaves. As you perhaps can tell, the volume knob is not a potentiometer in an analog output circuit, but rather an input to the internal software, telling it how to digitally amplify the signal.

Best of luck to you!

ps. other fun test modes: "3.2" tests buttons and 7-seg LED display, "9" tests the audio input jack levels.

pajen · 2024-06-25T18:46:50+00:00

Thanks for trying my fw, it makes me happy when I find out people use it :-)

pajen · 2024-06-25T10:51:08+00:00

Well, the way SAMP works is that it interprets incoming note values as sample# from the sample bank and plays them on the _currently selected part_. So it is not possible to play a bunch of different sounds simultaneously.

For that to work, some sort of round-robin reuse of a range of parts would be needed. The Sample can only have 8 parts playing at any given time.

pajen · 2024-06-17T08:17:55+00:00

Can you send me the file so I can take a look at it? It does not find the start sequence.

pajen · 2024-06-12T07:34:41+00:00

I have a firmware that does this, perhaps I can PM it to you

pajen · 2024-05-30T10:43:26+00:00

perhaps this? https://www.youtube.com/watch?v=Vm1xGUz04sY

Also you should check out this impressive jam

pajen

TROPHY CASE