Something bad happened to the loop tweaker with this update. If I use the automatic search function, I can see the new loop selected and all seems fine until I watch the loop markers in the actual file and see that they stop moving at some point and I can see the actual loop that the loop tweaker has defined wandering around completely outside the loop markers in the file. To make matters worse, if I use a crossfade and then undo it, the loop that was defined by the loop tweaker is abandoned and the original loop that was defined by the loop markers is back, as if nothing I did in the loop tweaker even happened. I thought that maybe the loop markers just failed to update, because after leaving the loop tweaker the new loop was still working, but the situation is actually the worst that you can have. You save the file thinking that the loop is good and when you reopen it, you find that the original loop is the one that got saved and all your work went away. I rolled back to 10.0 and these problems don’t occur.
While I’m on the subject of the loop tweaker - is it really possible that in 2019 I have to render a crossfade (hit Apply) and then undo it in order to eventually find the best crossfade position and curve? Isn’t this something that even a cpu in 1990 could accomplish in real time? It appears that Halion 6 somehow borrowed all the best things from the loop tweaker and then made it work exactly the way I wish the loop tweaker worked. But, it’s much more awkward to use Halion as a general wave editor, so I’d prefer the same functionality in WL.