I’m assuming you could use the Fire as a generic MIDI device, running through MTP (or a python script in FLS). They’ve been aware of these things for over two years they just don’t care. I’ve listed the issues with the Fire to IL, including some other things like the Slicex mode and the browser mode. Since it can never be fixed, I don’t have a reason to continue bothering you about it. I just decided to note this problem to you. The mixer mode is fine because the mixer track parameters are vertically opposed, not horizontally. So in the daw you habitually use pan on the left, and when you use the Fire it’s always going to be backwards.

It’s not even a matter of retraining muscle memory because it is still backwards, and will remain that way. The hardware is the issue because FL Studio and its setup existed first. I thought you could easily use as a controller for any midi? Very much like the korg sq10 when it came oit Having encoders without push function…THAT is a big deal (ie then you could just push down for the pan function) I dont even look at the visual when Im doing that…only for a rough guide and then its over to earsĪs a workflow that I do anyway ie 60/30/10 Ie use panning for spatial keying/positioning always check back to mono for phase. The tweaks begin on high res after the midrange painting I understand your expectations (and I commiserate with long held muscle memory) but once you are in the hardware world, I dont find that a real issue as the amount I would change the pan is…well…almost 0.1% of the time. The ui is the issue, not the hardware and unfortunately just baked into the siltation.

Yeah I used FL from about 2005 - 2012…but slowly migrated to mostly real acoustic stuff actually playing with people…which changes the tools a lot

Akai fire