My bug:
- Chorus delay surface panel not selectable due to big graphic groups not leaving any space on the panel expect may be 2 milimeters which is not enough. Ungroup the parameters to solve bug
@ Janni:
>>>>Other strange thing is, the MOut on Midi Remote & -Fader aren't red triangles but white squares
not normal, it should be a regular midi out "red" pad ("Midi Remote Fader" it is not one of my device - or i really don't remember it
)
This wrong pad type "can" be a bug cause (but it is not always the case because the pad type is set by the user. The white losange generally shows an async "non-audio" signal which is very bad to have at project window level. In the same time, it could be a midi connection and the maker just forgot to assign the right Pad Type (in which case it is only visually wrong, and may not be a cause of bugs).
>>> Cables disapearing / no possibility to connect (and all seems frozen when talking about connections).
According to my experience, it is caused by
- something "not audio" has been connected to an audio input (mixer or else) and can cause this bug (async modulation to sync audio input=can cause this bug in Scope 4.x).
- Device where the module name can be changed by the user. Has been reported by others as one other cause of the connectivity bug.
Device IO Setup: i looked for that one recently... i should add preset lists no (unless it is that yellow led at the top right ? )...
