I agree it must be rock solid and they tried to do too much. They're starting to allow some features (analysis) to be disabled, both because I find that "amateur DJ" cheat shit annoying & distracting, it's completely inappropriate for open deck nights and tutoring new DJs, and because I figured it would speed things up and reduce the variables that could be contributing to issues. With browser split screen also gone, delayed, or optional, I think browsing would likely be improved in both function and speed. The option to make it on, off, delayed, or with push (4 settings values possible) would be optimal, I think. Then there are all the glitches and oversights here and there I've mentioned that, when resolved, the performance and stability could start being focused on. I think it's strange v6.5 has analysis, BPM detection, and sync performance all improved, but that may have been something that was already close to seeing results on. I will say that they do spend too much time on that extra junk when there are core capabilities that need the attention still. I am crossing my fingers this progress can be kept up and continued, though, regardless of how they are unfortunately prioritizing. Oh, and the real difficulty is landing, not take-off :-)
P.S. The problem with big loops seems to be resolved or at least mitigated. If they're really long, sometimes it seems to just delete the In point. You can do a loop of a couple minutes now, though, instead of weirder behavior. Also, the setting of BPM to manual and BPM lock to 100 is not effective as a means of changing the 130 default value to confuse people less. Upon reboot later, it keeps the 130 as some kind of background sync value and then pitches the track down until it would be 100 BPM. This is with analysis off.
Bookmarks