Hot loops in Algoriddm are a big pain point the way is is implemented currently.
In other platforms, including standalone CDJs and Rekordbox, when selecting a loop, pressing a blank hotcue saves that loop as a hot loop. At any point int he track, selecting that hot loop brings that loop up and activates the loop.
Currently, loops are stored as a separate entity with little or no support from hardware manufactures to create a loop bank.
SUGGESTION- Please allow savings hot loops in place of a hot cue. Can even have it as an option, but I don’t see why anyone would want loops saved separately.
