I’m glad you like it! 😊

Sure, you can use the Stream Deck on stage as well if you prefer a more tactile way to control AbleSet 😊

Please excuse my late reply, I didn't get a notification for your comment! AbleSet has an option called "Auto-Loop the Current Section" which you can enable to have the loop region follow the playhead automatically so you can spontaneously loop the current section if needed. I hope this helps!

@@ableset No worries, thanks!

Hey Brandon, unfortunately, the Stream Deck needs to be connected to a computer running BitFocus Companion for this setup to work. This doesn't have to be the same computer that's running AbleSet, though, so you could theoretically install Bitfocus Companion on a Raspberry Pi or another small computer that you put on stage next to the Stream Deck. Here's a short video I found that shows how to set this up: kzfaq.info/get/bejne/m7SeiNuD0ZrdgGg.html I hope this helps! Let me know if you have any further questions :)

Thank you for your interest in AbleSet! Could you elaborate on what you mean by adding markers?

You can still upgrade from AbleSet 1 for a discounted price by logging in to the AbleSet website using the email address you used to buy your license. I hope this helps, let me know if you have any further questions :)

I'm sorry to hear that! If you like, you can send me an email to support@ableset.app with screenshots of your setup and the error message you see so I can take a closer look at what might be causing this issue.

The PA12 only recognizes MIDI devices that are connected via USB, but the Stream Deck is not a MIDI device, unfortunately, so you can't connect it to both computers at the same time. If both computers are connected via AbleNet, you can connect the Stream Deck to one of the two computers and AbleSet will automatically ensure that all commands are also forwarded to your other computer over the network.

That's strange, I just tried to reproduce this issue on my end, but it all seems to work here. Does restarting AbleSet and Companion help? If it doesn't, could you email me a few files so I can take a closer look at the issue? 1. A Companion support bundle. You can create one by opening Bitfocus Companion, then going to the "Log" tab and clicking on the "Export support bundle" button. 2. An AbleSet log package. You can create one by clicking on "Create Log Package" in AbleSet's settings menu. 3. A video of the issue, if you like. This often helps with troubleshooting. You can either send them to support@ableset.app or upload them here: files.ableset.app/i/qwe3cGA/support-inbox

@@ableset I think I resolved the issue. For this specific session, I was given a very messy session with the task of making it compatible with Ablest. I started up the stream deck right when I opened the session which means I had loads of locators (well over 1000) that were all being registered as songs by ablest because they hadn't yet been renamed. So I'm guessing the extreme "song" count just caused Ablest and/or companion to bug out. I've since renamed all of the markers which brings the song count down to ~40 and it's working well now. Thank you for your willingness to help!

@@user-mr3xj5nx2i that's great to hear, I'm glad you found a solution! Please let me know if you have any further questions or feedback in the future :)

The beat presets currently need the AbleSet Max for Live device to be loaded in your project. This is a limitation I’m aiming to remove in the future, but it’s harder to do than I initially thought. I hope this helps!

I'm glad you like it! Regarding the issue, could you check if you have the AbleSet Controller and LTC Display devices loaded in your Ableton project? They provide the information that is displayed on the Stream Deck.

@@ableset how do I do this?

@@SamSoundProductions you can find the controller by going to AbleSet's settings menu and selecting "Get AbleSet Controller". This device requires either Live Suite or Live Standard with the Max for Live extension. To load it into your project, simply drag the file onto a track of your choice. I usually drag the device on my Master/Main track, but that's up to your preference. The LTC Display is a separate purchase. You can learn more about it here: leolabs.gumroad.com/l/ltc-display I hope this helps!

@@ableset ok awesome. so I'm just confirming that I need to do the steps you mention to see LTC timecode info on the streamdeck and abelset performace view as well?

@@SamSoundProductions yes, that's correct!

Unfortunately, it seems like Lemur is no longer available so I'm not sure I can help you with this as I can't test it on my end, but if the app supports OSC, you could consult AbleSet's OSC documentation for more information: ableset.app/docs/osc/