Відео

no. it'll map it chromatically to the keyboard automatically. in order for the notes to match up (when you hit the C key the C note will play) you will have to transpose it to C

Thank you. I've been playing bass in some bands and going to school. My volca hasn't gotten much love recently but I still have ideas planned for the future

The vsample does have pitch control through the speed knob. By holding func and turning the speed knob you can edit the notes chromatically. You can also motion sequence these changes to create melodies. You can also emulate velocity by using motion sequence on the volume knob. The midi has two major functions as far as I can tell. The first allows you to play samples chromatically by using a keyboard. The rk002 midi cable will be necessary for this. If you have the pajen update, then a normal 5 pin midi cable will do. You can also play the drum samples by using midi pads using this method. The second purpose applies only to the pajen update because it has a setting on there where you can launch any of the stored 10 patterns using midi. Even though the vsample is built like a drum machine, there are many work arounds that allow you to create full tracks using it alone. Hope this helps

This video in particular was made without the pajen update and I used midi to play the samples chromatically

No prob. That is an 1/8 inch to 1/4 inch adapter. The normal headphone output on the volcas are all 1/8 inch while mixer inputs are 1/4 inch. With the adapter, I can use a normal instrument cable to plug the vsample into my mixer/audio interface. So pretty much it's used for capturing the audio coming from the vsample.

What is your setup? Is it the keystep pro plugged into the vsample using the rk002? Does your vsample have the pajen firmware update?

@@nightcrook9337 1. yes. 2. no you think my problems will disappear after the update ?

I was asking about the pajen update because after you get the update, the rk002 won't work anymore. Only a normal 5 pin midi cable will. I do not own a keystep pro but I do own the beatstep pro. For the og keystep, I only had to plug it in and play. For the bsp, I had to plug it in to my computer and set it up using the midi control center program. It required me to change the type of signal being sent out to be compatible with the volcas and then I had to manually set the pads to different midi tracks because the vsample has each sample on a different midi track. Sample 1 on midi track 1, sample 2 on midi track 2 etc. If you haven't done that with your ksp then I would recommend that.

It's It's job to keep you wanting more

With a normal midi cable, you wouldn't be able to play the samples on the vsample chromatically. For example, if you have a piano sample selected, it will play the same note no matter what key you hit. The RK-002 worked around this. It made it so that a midi keyboard can play notes on the vsample chromatically. As far as I know, this used to be the only way to achieve this. The pajen firmware update currently allows a normal midi cable to do this so there really isn't any need for the RK-002 on the vsample. I believe the only other thing it does with volcas is allow velocity to be played on the keyboard when plugged into the volca fm.

@@nightcrook9337 Thank you so much for your time and explanation!

Navi commands you

Id love to listen! All my tracks are available for free download so you can make something new and spread the music

Thank you! In this video, I did not have the pajen update. I use it on later videos. When I got first got the volca, I looked up a hunch of different tutorials to get started. After that, everything else was just done through experimentation and seeing how far I could push the machine. I started to feel as though the things i was making on the vsample started to feel like songs instead of just cool ideas after about a year.. My first video with the vsample was made after owning the machine for about a year and a half.

@@nightcrook9337 i have a little question: when you press the Memory button, for example at 1:59, i see that all the 16 "pads" are lighten up instead of just 10 memory slots. Why?

I'm glad to hear you're a fellow volca player. The problem you're having seems to be with the clock setting on the volca. It comes with the factory global setting to not use the internal clock when plugged in. Try turning on your vsample while holding the FUNC button. This should bring you to the global setting menu. Check to see if step 6 is lit up. If it is, then press it to make it unlit. You should see "CL. In" pop up. Once done, press REC to save the settings. This should make it so the vsample will use its own clock when plugged in through midi. If this doesn't work, then there must be a clock setting on your launchkey mini to stop it from sending a clock signal. Unfortunately, I do not own or have used the launchkey mini so I cannot tell you how to do this. Regardless, I hope this helps and you can continue jamming on.

@@nightcrook9337 thanks! I found the int. clock setting on the volca.. now I just need to find out why the launchkey still won't change its own clock speed when I turn the tempo knob. According to the manual, it should when it's being used as a standalone midi controller..

Wait a minute, you're starting to confuse me. Which machine do you want to be the master, the vsample or the launchkey? When you have two clocks connected by midi, one will be unusable because it'll be slaved to the master. I thought you wanted your vsample to be able to adjust its tempo which is why I had you set it to internal clock. This means that it is ignoring the clock signal from the launchkey. If you want the launchkey to be the master, then change it back to auto. But if you control the tempo on the launchkey mini you won't be able to adjust the tempo from the vsample.

Are you using the launchkey mini as a sequencer or just as a controller?

@@nightcrook9337 i wanted the launchkey to control the tempo because I want to make use of its arpeggiator. But when I hooked it up, both were stuck at 120bpm. So I thought maybe there is an issue that affects both devices, and if I set the volca's clock back to int, i could control both tempos manually and match them. But by now I understand that the launchkey wouldn't be affected by the volca because it only sends and doesn't receive anything. So yeah, the actual issue seems to be that the launchkey is stuck at 120bpm and I have no idea why that is. I'm sure I've missed something somewhere, but the manual hasn't been helpful at all.

Lol. Ill be keeping a look out for that name

The launchpad is connected to the pc via USB while the volca is hooked up to an audioninterface with a midi out plug. The launchpad sends midi patterns to the volca for it to play. This means that a sequence can be a long as your computer can handle rather than the 1 bar on the volca. The launchpad is also sending audio effect automation to ableton.