Comments by MaxDetal
Maybe 20 channels is a bit overkill—4 to 8 would do just fine. I just wanted to fully share the idea with you. Your devices are awesome, but what I really miss is the chance to toss them into my custom instrument racks so that whenever I open my pre-made drum or instrument racks in a new project, the sounds always head to the right sends.
Posted on March 02 2025 by MaxDetal |
Report Issue |
See Comment
Yeah, the idea is to be able to save routing. That is, for example, so I can load several senders in Drum Rack and direct them—say, to the first send channel. And then, every time I open that Drum Rack in a new project, all the senders automatically send their signal there and don’t get lost.
But if I knew how to make M4L plugins, I’d do it like this: we’d create two devices—a sender and a receiver. Each of them would have a certain number of channels, say 20: A, B, C, D, and so on. So, when I select, say, “B” on the sender and the same “B” on the receiver, the devices automatically link up and the sound comes out of the receiver. In other words, the user would choose not a channel, but simply the name or number of the “virtual” audio channel. The sender would have a passthru button for the audio.
Also, I’d try to do it without using the Ableton API, if that’s even possible. That way, the system won’t be overloaded when using a very large number of senders.
sooo =)
I thought you might be interested in adding such a device to your collection.
But if I knew how to make M4L plugins, I’d do it like this: we’d create two devices—a sender and a receiver. Each of them would have a certain number of channels, say 20: A, B, C, D, and so on. So, when I select, say, “B” on the sender and the same “B” on the receiver, the devices automatically link up and the sound comes out of the receiver. In other words, the user would choose not a channel, but simply the name or number of the “virtual” audio channel. The sender would have a passthru button for the audio.
Also, I’d try to do it without using the Ableton API, if that’s even possible. That way, the system won’t be overloaded when using a very large number of senders.
sooo =)
I thought you might be interested in adding such a device to your collection.
Hey dear,
My name is Max DetaL’ and I’m absolutely stoked about your sender! But I’ve run into a little snag and have a couple of questions for you. Really hoping you can help me out.
1 – Is there any way to set it up so I can tell the sender to route its signal, say, to the first send channel named “A Drum Looper,” and then save that configuration so that every time I open a new sender, it automatically sends the signal to the channel I set before saving? In other words, can I lock it permanently to that send/return channel “A Drum Looper” (which I have in literally every project and always as the first one)? Right now, the device doesn’t save the routing on a new launch, which is super disappointing since it means I can’t use it.
2 – Maybe it’s possible to create a sender that specifies a virtual bus. For example, in the sender we could assign something like A1, and if the receiver is also set to A1, then they’d always be locked to work together. All A1 senders in the project would automatically send everything to the receiver where A1 is selected. Is this even possible? It’s important that I can save a preset and have it load immediately with the bus I configured in advance.
Really hoping something can be done. Your device is super cool. Thanks!
My name is Max DetaL’ and I’m absolutely stoked about your sender! But I’ve run into a little snag and have a couple of questions for you. Really hoping you can help me out.
1 – Is there any way to set it up so I can tell the sender to route its signal, say, to the first send channel named “A Drum Looper,” and then save that configuration so that every time I open a new sender, it automatically sends the signal to the channel I set before saving? In other words, can I lock it permanently to that send/return channel “A Drum Looper” (which I have in literally every project and always as the first one)? Right now, the device doesn’t save the routing on a new launch, which is super disappointing since it means I can’t use it.
2 – Maybe it’s possible to create a sender that specifies a virtual bus. For example, in the sender we could assign something like A1, and if the receiver is also set to A1, then they’d always be locked to work together. All A1 senders in the project would automatically send everything to the receiver where A1 is selected. Is this even possible? It’s important that I can save a preset and have it load immediately with the bus I configured in advance.
Really hoping something can be done. Your device is super cool. Thanks!
Hey dear,
My name is Max DetaL’ and I’m absolutely stoked about your sender! But I’ve run into a little snag and have a couple of questions for you. Really hoping you can help me out.
1 – Is there any way to set it up so I can tell the sender to route its signal, say, to the first send channel named “A Drum Looper,” and then save that configuration so that every time I open a new sender, it automatically sends the signal to the channel I set before saving? In other words, can I lock it permanently to that send/return channel “A Drum Looper” (which I have in literally every project and always as the first one)? Right now, the device doesn’t save the routing on a new launch, which is super disappointing since it means I can’t use it.
2 – Maybe it’s possible to create a sender that specifies a virtual bus. For example, in the sender we could assign something like A1, and if the receiver is also set to A1, then they’d always be locked to work together. All A1 senders in the project would automatically send everything to the receiver where A1 is selected. Is this even possible? It’s important that I can save a preset and have it load immediately with the bus I configured in advance.
Really hoping something can be done. Your device is super cool. Thanks!
My name is Max DetaL’ and I’m absolutely stoked about your sender! But I’ve run into a little snag and have a couple of questions for you. Really hoping you can help me out.
1 – Is there any way to set it up so I can tell the sender to route its signal, say, to the first send channel named “A Drum Looper,” and then save that configuration so that every time I open a new sender, it automatically sends the signal to the channel I set before saving? In other words, can I lock it permanently to that send/return channel “A Drum Looper” (which I have in literally every project and always as the first one)? Right now, the device doesn’t save the routing on a new launch, which is super disappointing since it means I can’t use it.
2 – Maybe it’s possible to create a sender that specifies a virtual bus. For example, in the sender we could assign something like A1, and if the receiver is also set to A1, then they’d always be locked to work together. All A1 senders in the project would automatically send everything to the receiver where A1 is selected. Is this even possible? It’s important that I can save a preset and have it load immediately with the bus I configured in advance.
Really hoping something can be done. Your device is super cool. Thanks!
Hey dear,
My name is Max DetaL’ and I’m absolutely stoked about your sender! But I’ve run into a little snag and have a couple of questions for you. Really hoping you can help me out.
1 – Is there any way to set it up so I can tell the sender to route its signal, say, to the first send channel named “A Drum Looper,” and then save that configuration so that every time I open a new sender, it automatically sends the signal to the channel I set before saving? In other words, can I lock it permanently to that send/return channel “A Drum Looper” (which I have in literally every project and always as the first one)? Right now, the device doesn’t save the routing on a new launch, which is super disappointing since it means I can’t use it.
2 – Maybe it’s possible to create a sender that specifies a virtual bus. For example, in the sender we could assign something like A1, and if the receiver is also set to A1, then they’d always be locked to work together. All A1 senders in the project would automatically send everything to the receiver where A1 is selected. Is this even possible? It’s important that I can save a preset and have it load immediately with the bus I configured in advance.
Really hoping something can be done. Your device is super cool. Thanks!
My name is Max DetaL’ and I’m absolutely stoked about your sender! But I’ve run into a little snag and have a couple of questions for you. Really hoping you can help me out.
1 – Is there any way to set it up so I can tell the sender to route its signal, say, to the first send channel named “A Drum Looper,” and then save that configuration so that every time I open a new sender, it automatically sends the signal to the channel I set before saving? In other words, can I lock it permanently to that send/return channel “A Drum Looper” (which I have in literally every project and always as the first one)? Right now, the device doesn’t save the routing on a new launch, which is super disappointing since it means I can’t use it.
2 – Maybe it’s possible to create a sender that specifies a virtual bus. For example, in the sender we could assign something like A1, and if the receiver is also set to A1, then they’d always be locked to work together. All A1 senders in the project would automatically send everything to the receiver where A1 is selected. Is this even possible? It’s important that I can save a preset and have it load immediately with the bus I configured in advance.
Really hoping something can be done. Your device is super cool. Thanks!
Man, that's a very cool device, kudos. But why when I reload the project I get everything in LOCK? Will it still not work when loading the live set? and even if I map it to a third-party LFO, it still stops working over time. Macbook Pro M1pro
Dear SimonR, your device is unbelievably gorgeous. Thank you very much for it.
But unfortunately it is impossible to use it in my live, because each device takes 300-350 mb RAM. This is very frustrating, does not allow you to use it. I really hope and expect that you will optimise it for CPU and RAM one day.
Thanks and respect!
But unfortunately it is impossible to use it in my live, because each device takes 300-350 mb RAM. This is very frustrating, does not allow you to use it. I really hope and expect that you will optimise it for CPU and RAM one day.
Thanks and respect!
Dear SimonR, your device is unbelievably gorgeous. Thank you very much for it.
But unfortunately it is impossible to use it in my live, because each device takes 300-350 mb RAM. This is very frustrating, does not allow you to use it. I really hope and expect that you will optimise it for CPU and RAM one day.
Thanks and respect!
But unfortunately it is impossible to use it in my live, because each device takes 300-350 mb RAM. This is very frustrating, does not allow you to use it. I really hope and expect that you will optimise it for CPU and RAM one day.
Thanks and respect!
So cool device man! But unfortunately it reset after reloading ableton. Do you fix it in next version? if yes, how i can get it?
Guys, is there really no existing option to record master in Ableton?
I need a device that will hold the ARM forever during a live session, so that everything that happens in the DAW was recorded. Because if you use a looper, the Ableton won't record it. Using comand+click will not help, because I use a lot of tracks and do everything through controllers on the fly.
So far I know only one device, it's _P4R - Arm-Me audio v1.5 But it stops recording as soon as you turn on ARM on another track. PLEASE HELP!!!
Translated with www.DeepL.com/Translator (free version)
I need a device that will hold the ARM forever during a live session, so that everything that happens in the DAW was recorded. Because if you use a looper, the Ableton won't record it. Using comand+click will not help, because I use a lot of tracks and do everything through controllers on the fly.
So far I know only one device, it's _P4R - Arm-Me audio v1.5 But it stops recording as soon as you turn on ARM on another track. PLEASE HELP!!!
Translated with www.DeepL.com/Translator (free version)
Guys, is there really no existing option to record master in Ableton?
I need a device that will hold the ARM forever during a live session, so that everything that happens in the DAW was recorded. Because if you use a looper, the Ableton won't record it. Using comand+click will not help, because I use a lot of tracks and do everything through controllers on the fly.
So far I know only one device, it's _P4R - Arm-Me audio v1.5 But it stops recording as soon as you turn on ARM on another track. PLEASE HELP!!!
I need a device that will hold the ARM forever during a live session, so that everything that happens in the DAW was recorded. Because if you use a looper, the Ableton won't record it. Using comand+click will not help, because I use a lot of tracks and do everything through controllers on the fly.
So far I know only one device, it's _P4R - Arm-Me audio v1.5 But it stops recording as soon as you turn on ARM on another track. PLEASE HELP!!!
Hi! Great device, but why doesn't the HOLD function work? I really really badly need the ARM lock function on the channel. How to do it?
Need a device that will hold the ARM forever during a live session, so that everything that happens in the DAW was recorded. So far I know only one device, it is _P4R - Arm-Me audio v1.5 But it stops recording as soon as you turn on ARM on another track. PLEASE HELP!!!
Need a device that will hold the ARM forever during a live session, so that everything that happens in the DAW was recorded. So far I know only one device, it is _P4R - Arm-Me audio v1.5 But it stops recording as soon as you turn on ARM on another track. PLEASE HELP!!!