So I'm creating this while I test with the s4 this new promising update.
I'm also creating it here within the s4's section as I can't tell if that could be applied to other controllers.
Feel free to add to the subject and/or add it on another thread.
First bug I felt into:
* (new and F%µ£¨¨¨major one): I use macros to change effects in group mode, the title of the effect changes..not the effect itself (ie the audio is applied with a previous effect sound, not the chosen current one!! I'm still trying to figure why as it's not even taking into account the previous one but another one. For example I use a macro to choose a reverb, title changes to reverb but that's a gater effect applied). The most logical way I can think of to explain that would be a relationship with the coding that relates to the situation of a given effect within your list of effects (something here that is totally different about mappings where an effect is changed within the list and its mapping command, as I said here, the title changes in the effect slot where it is another one). This bug is only affecting some effects it seems and not in all circumstances, there's no pattern I could recognise for this. Weird. It affects for me the reverb, TTFX, digital lofi and some others.
* something that didn't change and that sucks: the choice of an advanced effect will also change the 1st slot in group mode. Boring before, still boring.
The flux mode is quite cool for loops.
If you set a deck to flux mode, note that the loop size encoder's push button will now act as an 'hold' type and won't be toggling anymore the loop active on and off. In place you select the size, engage the loop by pushing and holding the encoder, play with its size, release the loop by releasing the encoder. Quite cool.
My buttons are set to auto loop so to now engage a 'real' loop i use either the 'in' or 'ou' buttons to set either a 4 or 8 beats loop and divide or multiply its size with the same buttons. In flux mode, the active button does as it did before (mainly here now activates on/off a loop for a stored 'hotloop').
I'm not a great fan of the flux mode for hotcues (I use them mainly to cut tracks or move from a section to another one, so the flux mode here is quite pointless, probably better for cue point juggling). I also find the flux mode when scratching not that efficient (there's a tiny bit of lag when the audio 'rejumps' to where it's supposed to be - but I'm not scratch efficient anyway so my view doesn't really count. Can it be related to temp or beat sync options? If someone could give his opinion here that would be great.
I may have missed it but there's no visual feedback indication that the flux mode is on or off apart inside the deck header's drop down menu, that sucks.
I'm not a great fan of the new effects apart from one or two, the rest are "meh" (that's very subjective and I need more experience, but those are things that could have been created before (for example a slicer+flanger, etc...).
I'll work on what can be done with the override option in the mapping. But especially curious of the browse/copy mode and the links with all related buttons to those modes. Globally speaking I'm still wondering about how the override option would affect decks layers and things that do use a build-in invisible modifier.
I don't like the fact it's still not possible to map the loop length encoder...
That's it for now. More to come.