Just wanted to show what im dealing with.
I believe that is some terrible responsive pads or is it just my fingers ?
I have Mikro MK3 incoming via mail in case that its the pads. If its my fingers I can give up ?
Just wanted to show what im dealing with.
I believe that is some terrible responsive pads or is it just my fingers ?
I have Mikro MK3 incoming via mail in case that its the pads. If its my fingers I can give up ?
Don’t give up. I think it’s your computer. It takes some time to figure out what causes latency in each set up. It could be your audio interface, your drum software, or some other mystery. I struggled with the same thing and finally got it sorted. But there is probably nothing wrong with your hardware or with you.
Latency is not the problem. That’s from my terrible camera.
I’m more worried about 50% times that didn’t trigger even when I got both pads with same strength all the time.
Any answer for that and dry about bad start for the discussion
It’s not your fingers it’s the pads. This is the problem with pad controlelrs that unreliably trigger softer hits. It messes you up because you’re trying to learn how much force is needed for what type of sound response and all of a sudden the outcome is completely unreliable. That will lead to you banging on the pads, playing less dynamically etc.
As for latency, I did hear your hands hitting the pads (a soft thud) and then I heard the sound your computer produced a little later. That is probably latency since those should sound at exactly the same time. If you’re sure it’s not that and it was just a thing in the example you recorded don’t worry about it, but keep this in mind!
I will take a look for posaible latency. But for now the pads is the main issue.
I’m assuming that you are operating through your DAW. You might want to check the latency settings, in Ableton under Options / Preferences, to make sure that the overall latency is as close to 0.00 that you can get it. That may changes if your Audio interface changes or your PC is for what ever reason struggling a bit more on any particular day. Just need to keep an eye on it really. Ableton allows you to enter a compensation figure which on mine is normally a minus number. Hope it helps.
I dont feel latency while I play… I notice it more on video so I just blame that and my mick was next to speaker so that explanes that
Anyway I did check Overal Latency and fixed it too. Does it look too bad now
Ah I don’t really know what driver error compensation does, since I’m not an Ableton user but a latency that is negative (-0.36) seems weird to me.
That would mean the computer can see 0.36 ms into the future and predict what you are going to do
If you’re not experiencing issues right now, maybe just forget about it for now. Just keep all of this in mind because maybe a couple of months into the future, once you’ve played some more and you’re focusing on small timing differences you might all of a sudden feel like there might be something there to improve.
For now I’d say have fun first and make some music!
As I guess from the video you are dealing with 2 issues, low sensitivity of the pads and high latency. The first means that the pads are not triggering with soft hits. I am saying that because when I looked at the video carefully I realized that your pads don’t light up with softer hits so that’s why no sound is coming out then. When you hit them harder they light up and produce sound, but it comes out with latency, and that’s exactly your second issue.
The first issue depends on the sensitivity of the pad controller, which could be not sensitive enough. Which is your controller on this video? The second one depends on the latency settings of your audio interface and DAW, which optimally should be a positive number below 6ms. For better results you should select ASIO.
@mps15 - Both Rob and Vince are correct in what they say. If you are having to compensate the latency by -279.0 then you must have a buffer in your audio set far too high. Look at the Audio interfaces buffer size first as Ableton will take what is set their and apply to the Ableton buffer settings. For standard recording your buffer should be around 512mb, if you have a lot of tracks or you are mixing a lot of tracks then you could put it up to 1024mb. At 512mb buffer and 0.00 in the compensation your overall latency will probably be around 22ms. At 1024mb buffer your overall latency would be around 54ms. It doesn’t always follow to then put the minus symbol in from of that number though, so it could be a little trial and error.
At the end of the day, you need to have the overall latency betwen 0.00 and +6ms. The overall latency shouldn’t be negative. However, becuase the overall latency (with 0.00 in tghe compensation box) is already more than +6ms, you have to use a negative in the compensation box to bring the overall letency down to the right amount.
You do have to keep an eye on the buffer in the audio interface though, mine does change quite ramdonly sometimes. The last time I recorded I was on 512mb, turned on the PC at the weekend and it had auto changed to 1024mb so I had to change the latency to compensate.
I hope this explains it well enough. Ping me another if you are still stuck.
What pad device is it?
That is mpd218.
Can’t wait to try out mk3 mikro
I was originally looking at the MPD218 but ended up buying the Mikro Mk3. I think you will like the pads on the Mikro. In terms of finger drumming the Mikro does an excellent job really. My main dissapointment is the lack of functionality in Ableton compared to what you can do if you use Machine software as your DAW. Finger drumming, I can’t really fault it.
Fills sounds so much better & feels easyer to complete with mikro mk3 :))) Still doesnt sound like Robs, but some day