Hey, I'm glad you like it! : ) I think adding a button like that would cause more harm than good. (People would accidentally press it, and I would get a lot of emails :D.) So I think the deleting/inserting a new instance method is more ideal. (It doesn't take that much longer than a single button press, and it's not something you would do countless times with a Live set. Maybe once or twice I guess.) But I will think about it!

@@homelandelisabeth7090 That's totally fair!

Néha : )

Thank you! : )

Have fun with it! : )

It should still work just fine! : ) The device doesn't communicate with the audio driver. It gatheres all information from the Console app directly. One thing you have to keep in mind, is if you want to be able to use the "auto input assignment" feature. You need to have the Apollo interface input channels at the top of your aggregated devices. (So it can find the corresponding inputs) And all your other devices inputs should come second. Other than that, everything will work. : )

@@leonnaffin GroundControl won't be discounted on BF this year! : (

❤️

Thank you! : ) I'm glad you like it!

I'm not familiar with it so I'm not sure. I'm guessing that it'll work like every other built in Live device and M4L device with it. So if you can access the parameters for those you can access the Parameters of GroundControl too. : ) In the worst case you can just simply MIDI map the controls of the device.

It was intentional! :D :D

It's also a built in feature in lot of other DAW-s Have fun with it! : )

Have fun with it! : )

I didn't tried, but it should... I never thought that someone would want to cascade assign MIDI inputs/outputs. Give it a try, it's free. : )

Thank you! : )

Everything works just as before. : )

Thank you! : )

Hey, Sorry about the difficulties! Of course just write me an email: [email protected] (Don't forget to tell me what operating system you're using, Which Ableton Live version, and what Apollo devices you have) We're gonna make it work! : )

Yes, absolutely! : ) You just map the reverb/delay parameters to one of the 8 quick control parameters, then you can automate/modulate it, or control it with MIDI There's two things to keep in mind though: 1: The track needs to be selected when the automation happens. Or you can enable the "Enable Output if not selected" option in the device, but I would be careful with that option if you plan to use it for automation. ( It meant for MIDI remote control) But I can also send you a device that you can also automate to select different tracks during the song. 2: As I said you can have different plugins on the channel on different tracks, and the device will recall them automatically. So you can not only automate certain parameters, but you can even recall complete "states". But If you plan to use it in Live situations I recommend to only switch between tracks (where you have the device) where you use the same plugins on the channel during the song. Otherwise the console will mute the output for a second while it loads/removes the plugins. You can of course switch to another track with different plugins between songs to achieve a completely different sound. : ) I plan to add more Live performance tools to this pack in the future. (for example a device that works like the quick parameters page, but it lets you automate any plugin parameter on any channel)

Thank you! : )

Then what would I do? :D :D

Yes It's both in the description, and on the product page. I released this two devices before Live 12 came out. And I left it out there because 1: There are people who didn't upgraded yet to Live 12. 2: Some use it to compensate for external hardware latency.

@@homelandelisabeth7090 no live has this feature since version 7

No it's been a feature since Ableton 7.

@@Bthelick Ohhh sorry... looks like I didn't actually read what you wrote.. I thought you're talking about the new "Keep Latency" track option they introduced in Live 12. (That fixes the issue) The "Reduce Latency when monitoring" option doesn't fix the problem these devices were meant to fix. When you record something in Live with enabled monitoring, and you have any plugins in your project that introduces latency this latency amount will bake into the recorded take. (So for example if you have a plugin that creates 100ms latency, the clip will be 100ms later than you played it. + the latency from the IO settings) When you enable "Reduce Latency when monitoring" Live will take every track (and their path) to a separate delay compensation paths. So if you have plugins on other tracks it won't affect the "latency bake in" but if you have something that creates latency on the actual track you record, or it's group track, any send you send it into, or on the master. it'll still get baked into the take. So this option doesn't fix the problem. In Live 12 you have a new option to turn off "keep latency" for each track. and in that case the clip you recorded will get into the timeline right when you played it.

@@homelandelisabeth7090 really? I'm gonna have to do some tests I've never had this problem. Why would Ableton pass plugin latency into the recording path and not record directly from the interface? Weird. Maybe my rme behaves differently let me check.

Haha Thank you! : ) I hope you're gonna use it a lot! And the best part: it's only the first release! Tomorrow I'll drop 1.1 with a lot of user request features ( option to: don't copy plugins when you select another channel, link the record arm button to the channel's mute button.. things like that. Plus I added meter sections both for the channel and for the sends. so you can actually see the volume like in the console : ) ) I have plans to implement a lot of cool stuff in the future! : )

@@homelandelisabeth7090 it gets better! I'm all in.

​@@homelandelisabeth7090 hey again - have downloaded and doing some initial tests - just wanted to let you know it's working well with my Softube Console 1 fader unit in Apollo Mode. what's the best way to contact you with feature suggestions / test findings etc (if useful!)?

@@synthshed Hell yeah! That sounds amazing! : ) I don't have a console one so I didn't had the chance to test it. (but since everything communicates with everything it's not surprising that it works) You can write me to [email protected] And of course it's useful, I'm eager for suggestions! : )

@@homelandelisabeth7090 cool I'll be in touch, thanks!

When I created this device I also tried to do something like that, but I wasn't able to pull it off... Sadly it only possible with keyboard shortcuts. (Select the first clip then Shift+Down)

​ @homelandelisabeth7090 I'm going to buy this for the "Keep Collapsed". I'm currently selecting the region then Ctrl + L to loop the region. Then I click The loop and it automatically selects everything below the region. I'm going to try something with the AutoHotKey from windows to see if I can create a better way to do that, thanks!

Yes it does! : )

: )

I don't have any RME interface : /

Thank you! : )

Have a lot of fun with it! And thank you! : )

@@homelandelisabeth7090 I feel like I just bought NOT WORRYING about what key I start a song in 😃 I've spent so much time manually transposing a whole song a (semi)tone up or down clip by clip just to see if that fits the song better, often only to find out it didn't work after all, so all that time was wasted. This device makes me feel completely free to try a different key on a whim 👍👍👍 Also the exclude-words and the fact that it actually works with Auto-tune, Melodyne etc are all so thoughtful, I love it!

@@nouzeg123 Thank you, it means a lot to hear that! : ) let me know if you created a song using it, I would love to hear it.

@@homelandelisabeth7090 Will do 👍

Haha :D It's just because I'm nervous in front of the camera and I pressed it like an idiot. :D

Have fun with it! : )

Thanks! : ) Sure thing, why not. : )

@@homelandelisabeth7090 you're my hero

@@raggedrec write me an email to [email protected]