since the implementation of rude solo it seems we don't need the solos arraylist any longer. Remove it after a stabilisation period (not customer complaint).

fader movement is jittery when moving more than 6 faders at the same time

when the faders are not installed consecutively (that is, there is another (without fadercomms) or no module in between), addressing is off.
Also the first motorized fader module address found should become fader 1 no matter where it is positioned in the frame

refactor the connection state machine for both local and remote side. Transparent for the user

make it reliable

Only on some systems:
Although IAC Midi setup is correctly done and the tinyCCM app enumerate all midi devices correctly there will be no midi traffic showing up on port 2 and higher. It could be that the underlying midi driver flips out when enumerating over external USB MIDI devices. A newer midi driver should fix that - let's hope and see....

There is an Exception not shown on the UI when fader movements or MUTE/SOLO from HUI on instance 3+ (or latest instance) - nothing happens (even no log).
However, in Stand-alone mode, all faders and commands work from DAW to APP.
The reverse direction CADAC -> HUI always worked correctly.

If solo's are not rejected, the "rude solo" indicator shall be respected as depending on the workflow the user might have a track in solo that is not visible for the tiny

Three new menu options under "commands" shall be implemented to set all (motorized) faders into Write, Ready or Safe Mode. This is handy for faders having an old firmware and for troubleshooting.

find a way to have a log scale for the GUI faders. not easy thou....

fader curves have to be reviewed for each DAW type.

When the osx tray bar is not in black mode, the ccm try icon shows black as a background. Improve the icons!

When opening a cue file or saving a cue as a file - file path navigation is very cumbersome.
Also specificing a filename without extension should create the extension automatically

Since Pro Tools has blinking Solos all Mute changes during Solo mode will be lost. This option tries(!) to fix it by re-sending Mutes (after leaving Solo) to channels which were detected as non blinking.

Check feasibility to support more than one cadac frame by daisy-chaining them.

this is transparent for you but in the past the licensing validation is done in a double fashion which really is not needed. Make it simpler.
Note: any change on the tupel (tiny hardware, tiny FW version, app version) results in a new license file that will be provided to you. Changing the computer is allowed of course.

firmware: if ethernet link is down after it has been established, mDNS service advertisement is not happening.

after a while the tinyCCM gateway seems to not reply to a ping (no pingback). It's unclear if that's a networking issue or code issue. Also there seems no pattern to reproduce this. The ping mechanism shall be improved or dropped entirely to make the connection up and running even if the network might drop data packets.

find a better way how to handle debug and info level chattiness

a menu option "reject solo" should be created so that solo commands will never be sent to the cadac desk.