@anak.utara Agreed. He really squeezes out a lot from relatively cheap gear, and his outdoor performances (with included sound from the environment) are consistently excellent.
@leonsarmiento you’re definitely adding to the gas… although I was hoping to use it more as a sound module and sequence it with my M8. Do you think its performative abilities could still be incorporated into this kind of workflow?
If your sequencer device is flexible and powerful enough it can be even more powerful. The utter example of this are the PD controllers for the VD, such as the one in the video at the end.
However, for me that’s more on the programming side of things (ultra powerful programming). RandoLocking steps of the key 6~8 parameters of each track of the VD in a brutal way can be pulled out with something like the Digitakt and above, for example
On the performance side, some of the key functions Takeo uses are sequencer based (#steps, start/end step, retriggs on the fly) so your sequencer device flexibility is a factor. I cannot pull those from the sequencers in my Samples/Cycles, for example.
If you send only clock, then you can have the performance side of the VD because it becomes an instrument for you to play along the rest. If you control it as module via midi how much can you squeeze of the VD depends on how flexible/programmable your sequencer is.
I’m still not loving VD as an acronym, but it is what it is. 
I ended up buying a used one for $80. At this price it’s the best value per dollar synth I’ve ever acquired. While the interface is a little clunky and unintuitive, I can look passed it cuz it sounds so good. I’m particularly loving all the pops and sizzles I’m culling from it, and just how nuanced it can get when parameters are sequenced. It’s like having a little box filled with 00s-era Raster-noton percussive sounds. Once I fully grasp all of the controls and features I want to start sequencing it with my M8 and really dive into the asynchronous glitchy side of it. I’ll share whatever I come up with.
Made on a Volca Drum:
Listen to 165GlitchPerMinute by MC #bc8e47 on #SoundCloud
https://www.instagram.com/p/CvlZHgMJfDK/?igshid=MzRlODBiNWFlZA==
I’m really loving this combo. It’s so easy to have the M8 sequence the VC, sample the results, and then chop and tweak it further.
I just had an idea… I’ve not tried it yet. Maybe it’s possible to sequence deep & complex parameter changes from an external sequencer but still use the built-in sequencer for trigs/step control etc at the same time. Might open up a bit more expressivity!
I’ll try this later from my Akai Force… Maybe with the envelope follower and some extreme random cc data…
Also I bought a EHX Platform the other day from another Elektronaut and I’ve been enjoying running the Drum through that for squish and grit!
Hi everyone. Just wondering if someone here has tried to use synthmata volca drum with model cycles as midi interface?
I’ve connected my volca drum to my model cycles’ midi out, and when I edit the parameters with synthmata nothing really changes as what the demo have shown. I’ve also tried to save my patch to test, and my chrome downloaded a midi data instead. This is my first time using synthmata, and I want to use it to edit and save my kits for backups.
Hope I can get some enlightenment from many volca drums experienced users here. Thank you in advance!
Hi there! Not used synthmata’s editor but I’m guessing the it saves the patch data as a .midi file and that’s just fine and dandy. You just keep those midi files in a folder and they are the patches. Load them back up to synthmata then send the patch to the volca drum to load it on there.
Re getting the volca drum to respond to the changes in real time, I’m gonna say the obvious + ask if you’ve checked the model:cycles midi thru settings are set correctly? If it has them! I don’t have one myself so not sure. And check any channel settings on the model: samples in case it’s got filtering etc for the midi thru.
Also did you check your volca drum is set to split channel mode? (synthmata controller’s instructions says this is required) Hold down record while turning on and check that steps 1-6 are lit. If only one step is lit, press that step and it’ll change to steps 1-6 for split channel mode. Press rec again to save and reboot.
Also you might need to check the other settings menu in the volca drum - press and hold func while turning it on, and check that step 7 is lit (allow receiving (rx) short midi messages for triggering notes and receiving CCs). Whilst you’re there if you want the volca drum to sync to external clock / start / stop, make sure step 6 is lit (to enable auto receive external clock).
Then press rec again to save and reboot.
Thanks for the feedback! I’ve read and test everything with the same precautions that you gave. But still to no avail. Maybe it’s just not suited yet for complex devices such as model cycles where it can be a controller and also a standalone synth at the same time.
I might test it later with simpler setup, probably with just a midi controller such as a launchkey mini and see whether it’ll work or not. Though if anybody else used the same setup as me, using model cycles to control korg volca drum via midi out and able to use synthmata to change volca drum’s parameters with real time sound feedback. I would be real happy to understand how it works and use my volca drum to the fullest.
Agree with the previous poster, this sounds like you need to set the MIDI on Cycles to MIDI Thru when you want to do patching from synthmata and then if you actually want to control the Drum with the Cycles itself you’ll need to set it back to MIDI Out after. Also make sure you are receiving MIDI In from USB, as that can be disabled.
I currently have a Volca Drum and have had a model cycles. Currently have a digitakt I can test this later with if need be.
I think the volca drum is the first real successor of the korg er-1, looking at the sound engine.
The volca-format with micro-knobless pots puts me off though. If it had the same form factor of the 1st gen electribes, or even a bit beefier than that, one would be standing here right now.
Thank you very much for this! I think I have tried midi thru but still nothing happened. But, I’ll try the midi in from usb tip as it’s the only thing that I think I haven’t tried yet.
It’s a great sound engine! I use my Akai Force with its knobs and pad macros to really open it up for quicker sound design and performance fx. I keep threatening to post a video of that here so maybe I’ll do that.
gosh… I have been modifying his v1 of the sequencer, adapting it to the M:S and the M:C, and also for the Korg Monologue.
This v2 seems like a nice weekend project for porting it to the Models too.
I wish when Korg came out with the drumlogue, it was going to be basically a Super Volca drum.
Same, and I was convinced it would be, but… 
It feels like the Volca Drum was some kind of playground experimentation for Korg - it’s so adventurous - but they didn’t take it seriously enough to make it a higher range product. That’s really a missed opportunity.
The good thing is: the VD is pretty cheap! And once paired with a decent controller/sequencer, it unleashes awesome beats to the world.
the sound engine is inspiring.
