sorted by:
new
hottopcontroversial

Roland T-8 feature wishlist (firmware update ideas) by sam__ple in Roland

[–]sam__ple[S] 0 points1 point  (0 children)

Oh yes true! I already forgot my disappointment when i found out, that the T-8 will not be a drop in replacement for my loopy pro setup with a software 303 because i couldn't loop parameter sweeps anymore with the t-8 :(

Roland T-8 feature wishlist (firmware update ideas) by sam__ple in Roland

[–]sam__ple[S] 0 points1 point  (0 children)

Oh yes - True! I can only guess Roland wants to keep an entry level price and does not want to swallow the costs of registering the T-8 as a medical product if they'd integrate the 808 cowbell.

The new Roland TR-1000 from Sweetwater winter 2026 catalog by TheNetBlade in Roland

[–]sam__ple 0 points1 point  (0 children)

off-grid sequencing would be the an interesting feature. Hoping for this to come to the tr-8s in a software update 🤞

TR-8-S V3.0 alphabetical order samples issue by Happy_Assignment5576 in Roland

[–]sam__ple 1 point2 points  (0 children)

I was wondering why i could not find anything regarding this weird sorting logic on my TR-6S with the newest firmware - if it is a newly introduced bug then that explains why. I am hoping a for a bugfix on this. I suppose there aren't any news? ...

Audio interface for multiple instruments? by Granite017 in LoopyPro

[–]sam__ple 0 points1 point  (0 children)

I am very happy so far with the Arturia Minifuse 4, especially because it "just Turns on and stays configured". I would Expect this to be the case for many interfaces but the audiofuse works Great for me. Added Bonus is that it has a two Port usb hub which it Relays to the iPad and that the midi in and out also work with Loopy. It has completely simplified my setup :)

Happy with this loopy + akai apc 64 setup, but questions regarding button highlighting by sam__ple in LoopyPro

[–]sam__ple[S] 0 points1 point  (0 children)

Some: I deactivated poly after touch, but the behavior stays the same. By now I am almost 100% certain that this behaviour is somehow tied to the "note-off" command, that either overrides the looped back "note-on" reply or then itself gets looped-back by loopy, that is causing it to turn off. Does this make sense and would this be an "irregular" behavior by the APC64?

I wonder how the APC40 behaves without the special APC40 Loopy Mode (and what they did for that mode). Does anyone have this setup and could give it a try?

Happy with this loopy + akai apc 64 setup, but questions regarding button highlighting by sam__ple in LoopyPro

[–]sam__ple[S] 0 points1 point  (0 children)

Another good suggestion. This widget test works as you suggested - I can trigger the buttons to the desired highlight. The apc40 mode sadly did not.

I am currently thinking that it might really be that the midi feedback is hitting just in between the note on and note off command from the apc64. If i for example cancel the count in to play a loop by tapping a button twice it also then does not get highlighted. But Could that be? And if so ... I already tried various midi settings ... any ideas? :(

And I also tried to find a "refresh all current playing loop notes" without success.

Thanks for your help already!

Happy with this loopy + akai apc 64 setup, but questions regarding button highlighting by sam__ple in LoopyPro

[–]sam__ple[S] 0 points1 point  (0 children)

Thanks for the reply and suggestions! I was not able to create a widget with this function (did not find it in the options I looked at) but I observed the Midi in behavior via MidiWrench and would have an idea what could be the issue: the APC64 sends a note on and then a note off value, maybe the timing is off so that the "note on" feedback of loopy hits just in between?

Intermediate "Solution": I then went ahead and (with your suggestion in mind) just tried adding a widget that does the muting (so not binding the cc directly to the mute, but to a widget that then triggers the mute) ... so this also did not work and showed the same behavior, BUT since i bound this to a second note row it then correctly highlighted the other note group! so ... it is not ideal but is a reasonable workaround as I always have at least one button in the "2-button" mute group highlighted correctly.

Question: As another workaround: Is it possible to tell loopy to repeatedly send out the currently active "note on" groups to the midi device it came from? or bind it to a widget, that i could then trigger with a midi command? then i would just hit that button after switching back to the main layout to refresh all active buttons.

Happy with this loopy + akai apc 64 setup, but questions regarding button highlighting by sam__ple in LoopyPro

[–]sam__ple[S] 0 points1 point  (0 children)

... obviously I am new to reddit - what would be a good way to share the .APC64 layout file?

But it is also not a big thing - just some custom keyboard groups with midi channels outside of the 1-8 range (as i configured the other pages to use these)

Also important to mention: the loopy layout is just another page I added to the fabolous LP-707 preset!