To scroll around different devices in a track chain, you hold the device button, and then use the navigation arrows, in the bottom left. It would be really interesting to see the specific differences, comparing this to a Push 2. I like the sliders on this, but the Push 2 still has some pluses. Obviously, the Push 3 has some major advantages, as a controller, not even thinking standalone; at a much higher price point.
I got an APC 64 last week and to be honest while it has its limitations it has really exceeded my expectations…it affords a lot more functionality than it seems at first glance. Very nice video
I'd love to be able to do this with a few elektron boxes. But I have never got technical like this. I'm familiar with the mpc an an I get great results from the digitakt an digitone.
Hej Tefty, big fan of your channel, I was thinking: can you use the step sequencer in the APC64 instead of the one of MPC? I was thinking if it is possible to use the sequencer on the APC64 and then send the MIDI sequence to the MPC, to inject the step sequence into the step sequencer of the MPC?
I've just bought an apc64, using it with ableton and it feels like there's a nearly a full second delay between hitting a pad and hearing the sound. Particularly noticeable on drum tracks where my finger has left the pad before i hear the drum hit. I selected reduced latency when monitoring, but it's not helping...do you have any trouble shooting tips?
Try adjusting your buffer settings and sample rate in Ableton settings? Also try to make sure you have the track that you’re currently playing through “selected” and not just record-enabled… you have to have the particular track you’re playing through “highlighted” aka “selected” for the reduced latency while monitoring (if I remember correctly). Make sure you turn off cpu-intensive plugins too, as well as any unnecessary applications you might have running on your computer. Make sure the apc64 has the latest firmware update, as well as Ableton. If none of this works, try starting a fresh project and see if you still have latency from the controller when you try it out with a single track open. If adjusting your buffering and sample rate doesn’t help here either, then try restarting your computer so it can clear all the old cache and try again. Lol I know this is a lot but this has become the story of my life as I’ve added new hardware and plugins to my setup over the past couple years. It’s always a pain in the ass for the most part since I’m using a MacBook with Apple silicon, which makes everything more difficult to just work right out the box. I hope this helps you though! Cheers!
It doesn't seem like a bad controller but the APC40 MK2 just seems way better for using with Ableton. Not just with the tactile controls but everything's directly there. You don't need to tell something to switch between volume and an controlling a device because it just has separate controls for that. And you don't need to page between functions to have a track record/solo/mute, each track just has a button for each of those on the APC40. Plus the crossfader and quick quantize buttons, it's far superior for that purpose. As a general purpose midi controller that can also sequence, this could be better if you don't prefer more tactile faders and knobs. But overall I think this is a huge downgrade. Which is too bad since I'm now looking to get a controller for Ableton and the APC40 is discontinued. I'd rather just get an APC Mini over this one to have the faders but that also lacks a ton of functionality that the 40 had.
For an ableton remote, except if you use it for live in a specific way; my hot take is having volume faders that aren't motorized is completely useless. sure I love completely screwing my mix by just touching something. The only other way to do this is having encoders (and preferably touch encoders or a way to see the value before changing it). The catch function is not a solution since you'll always overshoot, and as soon as you have more than 8 tracks then they'll change values. And for live use you'll want to just map directly your controls because it's a lot better that way. I have the launch control xl and it's a great performance controller but is garbage as an ableton remote; I've simply removed it from my desk when I'm doing composition/mixing. For now I have a ks37 and I use the 4 knobs for plugin control but I'd simply like 8 encoders and a screen; and there's zero option on the market to do this (except a phone and touch osc)
@@valdir7426 That depends a bit on how many faders you have relative to how many you need. And if you’re managing other stuff through busses and mixing/monitoring within those before pushing out to a live channel. I generally don’t see a need for more than 8 concurrent live channels for individual volume control so the faders can be left as actual values and just hard assigned and everything else can be managed on the monitoring side. Depends on what you’re doing with it though. If I’m messing with a bunch of stuff feeding into a bus that later gets mixed in, a midi with endless encoders works totally fine for my purposes and the fader is just used to bring the combined channel in.
many options with a gazillion pads or keyboards; zero actual small factor desktop option; this won't fit on my desk neither will a giant keyboard and I already have an excellent tiny keyboard (ks37); really want that "8 encoders for plug in control and screen to show parameters; 16 pads with launch and simple sequencer capability" thing that doesn't exist (and that novation could do if they release a simple no key version of their keyboards). these manufacturers have still to understand the concept of having a very limited space (and also there are many desk controllers for other daws like from nektar/ssl/icon; none that is really tailored to ableton; it's 64 pads or nothing)
So you are beta testing this device in public, (in two videos now) and finding out that basic, basic functions are missing. I don't know why Akai doing this to themselves, releasing this device with this limited functionality.
right off the bat, how do you turn the tap tempo blinking button off
To scroll around different devices in a track chain, you hold the device button, and then use the navigation arrows, in the bottom left. It would be really interesting to see the specific differences, comparing this to a Push 2. I like the sliders on this, but the Push 2 still has some pluses. Obviously, the Push 3 has some major advantages, as a controller, not even thinking standalone; at a much higher price point.
I got an APC 64 last week and to be honest while it has its limitations it has really exceeded my expectations…it affords a lot more functionality than it seems at first glance. Very nice video
Hello,
Can we use "launch" bottons to launch scenes during we're playing in "note mode" and "chord mode" ??
Thank's
APC64 is lovely for Ableton
I'd love to be able to do this with a few elektron boxes. But I have never got technical like this. I'm familiar with the mpc an an I get great results from the digitakt an digitone.
Another great review! Track also sounds really nice…
Thank you Marc!
I'm sure the first update or two will include settings for quantize that's a big oversight.
Hej Tefty, big fan of your channel, I was thinking: can you use the step sequencer in the APC64 instead of the one of MPC? I was thinking if it is possible to use the sequencer on the APC64 and then send the MIDI sequence to the MPC, to inject the step sequence into the step sequencer of the MPC?
Hold device and use navigation buttons to switch between devices. Or make a rack and do your 8 macros ..
You can adjust the CV settings directly from the device under the Global Settings
Is this only for the session view or arrangement too...im pretty sure both but when seeing these reviews its always discussed in session view
Have you tried Touch OSC on a tablet?
I've just bought an apc64, using it with ableton and it feels like there's a nearly a full second delay between hitting a pad and hearing the sound. Particularly noticeable on drum tracks where my finger has left the pad before i hear the drum hit. I selected reduced latency when monitoring, but it's not helping...do you have any trouble shooting tips?
Try adjusting your buffer settings and sample rate in Ableton settings? Also try to make sure you have the track that you’re currently playing through “selected” and not just record-enabled… you have to have the particular track you’re playing through “highlighted” aka “selected” for the reduced latency while monitoring (if I remember correctly). Make sure you turn off cpu-intensive plugins too, as well as any unnecessary applications you might have running on your computer. Make sure the apc64 has the latest firmware update, as well as Ableton. If none of this works, try starting a fresh project and see if you still have latency from the controller when you try it out with a single track open. If adjusting your buffering and sample rate doesn’t help here either, then try restarting your computer so it can clear all the old cache and try again.
Lol I know this is a lot but this has become the story of my life as I’ve added new hardware and plugins to my setup over the past couple years. It’s always a pain in the ass for the most part since I’m using a MacBook with Apple silicon, which makes everything more difficult to just work right out the box. I hope this helps you though! Cheers!
Can we get some Push 3 content? All this other stuff seem like more of the same.
Nice track 👍. The product seems to have missed opportunities to add great value to its users.
That’s awesome! Feel free to reach out.
Bitwig supports this fully in 5.2
Similar workflow to what’s shown here?
A more advanced Launchpad pro 3?
Boggles my mind how they could discontinue apc40mk2
This was suppose to be Push 2...
It doesn't seem like a bad controller but the APC40 MK2 just seems way better for using with Ableton. Not just with the tactile controls but everything's directly there. You don't need to tell something to switch between volume and an controlling a device because it just has separate controls for that. And you don't need to page between functions to have a track record/solo/mute, each track just has a button for each of those on the APC40. Plus the crossfader and quick quantize buttons, it's far superior for that purpose. As a general purpose midi controller that can also sequence, this could be better if you don't prefer more tactile faders and knobs. But overall I think this is a huge downgrade. Which is too bad since I'm now looking to get a controller for Ableton and the APC40 is discontinued. I'd rather just get an APC Mini over this one to have the faders but that also lacks a ton of functionality that the 40 had.
For an ableton remote, except if you use it for live in a specific way; my hot take is having volume faders that aren't motorized is completely useless. sure I love completely screwing my mix by just touching something. The only other way to do this is having encoders (and preferably touch encoders or a way to see the value before changing it). The catch function is not a solution since you'll always overshoot, and as soon as you have more than 8 tracks then they'll change values. And for live use you'll want to just map directly your controls because it's a lot better that way. I have the launch control xl and it's a great performance controller but is garbage as an ableton remote; I've simply removed it from my desk when I'm doing composition/mixing. For now I have a ks37 and I use the 4 knobs for plugin control but I'd simply like 8 encoders and a screen; and there's zero option on the market to do this (except a phone and touch osc)
@@valdir7426 That depends a bit on how many faders you have relative to how many you need. And if you’re managing other stuff through busses and mixing/monitoring within those before pushing out to a live channel. I generally don’t see a need for more than 8 concurrent live channels for individual volume control so the faders can be left as actual values and just hard assigned and everything else can be managed on the monitoring side. Depends on what you’re doing with it though. If I’m messing with a bunch of stuff feeding into a bus that later gets mixed in, a midi with endless encoders works totally fine for my purposes and the fader is just used to bring the combined channel in.
@@djcrouton2680 in this case I would just hard assign the fader and not use the remote mode
many options with a gazillion pads or keyboards; zero actual small factor desktop option; this won't fit on my desk neither will a giant keyboard and I already have an excellent tiny keyboard (ks37); really want that "8 encoders for plug in control and screen to show parameters; 16 pads with launch and simple sequencer capability" thing that doesn't exist (and that novation could do if they release a simple no key version of their keyboards). these manufacturers have still to understand the concept of having a very limited space (and also there are many desk controllers for other daws like from nektar/ssl/icon; none that is really tailored to ableton; it's 64 pads or nothing)
Only 32 steps is a deal breacker .
Pitty
64
64 ?
Prove me
??? @@effebidi9677
Why you say 32?
@@ElGo-j8k where do you see is 64 steps?
I can't advice it if is a standalone 32 steps sequencer .
So you are beta testing this device in public, (in two videos now) and finding out that basic, basic functions are missing. I don't know why Akai doing this to themselves, releasing this device with this limited functionality.
You are so cool:) Shall we connect?