I am still to get busy with my hot cues as I have only done two mixes sussing out my new set up , but now after solving my mixer issues from another vender at last I will be able to get busy later this week and then I will know exactly if I can agree with or disagree,. but from the offset I agree that things should behave in a logical way and reliable way.
Open source is love for home project but a shared decks like in a dj booth with open source firmwares would mean a visit DJ would be walking into possible badly mutated decks ever time. Worse than midi map modifier over users
But being fair, the competition are not of additioning many user requests to firmware at all stages. Pioneer example is that they just offering bug fixes for what they model did one day #1 but no new function.
Instead pioneer bring out a different new model with new features on only - then you choose to buy they new model or just keep using the old features on of the old model.
It’s easy to beta test a pencil - does it write ? Yes? No? With mcx and Prime being multiples modes of standalone and different hot cue modes and different menu preferred options it much of more difficulty to beta test - even more difficulty added to beta test when new features add.
Exactly that’s the point. These systems are very complex, testing is expensive and bugs will occur. That’s why there should be a solid pipeline for reporting and fixing problems. An active user group finds bugs quickly. We’ve talked a lot about existing problems, but for us users there is no list of what has been detected and what will be fixed. Actually I’m quite anxious that problems from the original release might not get fixed with the next update (quantized hot cues from inside loops).
This is a good point and an area where something like Mixxx and other open sourcey stuff tends to work well with crowd sourced effort and transparency. I also think completely opening up Engine Prime’s analysis and meta info formats would help push for wider adoption across the brandings.
The original problem was that the hot loops were not quantized. That has been fixed. However another issue is that the hot cues - usually quantized - are not quantized when triggered from within an active loop. That problem has been overlooked, although it was reported.
To try it yourself just get a loop running and then jump to a hot cue (quantize active).