So when you say catalina is not supported yet - does this mean the itunes bit? or the whole EP app? just wondering … no problems for me on mojave but now all my other ios devices are on ios13 i cant detect em and EP is the only thing stopping me from upgrading …
update is worse than 1.3.1
everything keeps resetting , ad change cue point colour to blue then would change bk to red , ad move beat grids that would also change bk anyway av sold it , luvly controller tho ,everything jus needs more up dates , great for mobile djs luvly screen ,well responsive , jus dont think its quite there yet , but i perfer pioneer rekordbox , i feel more at home with wat i know , pioneer controller, but its your own preference , rekordbox was poor when it started tho
1 Like
I just noticed they released version 1.3.3. I’ll give it a spin later today.
It hasn’t extended much in many years so
Unfortunately, in what seems to have become the norm, the lack of care for detail crept in again. The release notes for both the Windows and macOS still mentions 1.3.2 in the first line (as shown below), while the executable indeed seem to indicate it’s 1.3.3.
===== excerpt from 1.3.3 Release notes ======
Engine Prime 1.3.2 - Desktop Release Notes
Fixes / Improvements:
Fixed issue with Cue Points sometimes not being saved
Fixed issue with BPM and Beatgrid changes sometimes not being saved
Fixed an issue where track waveform data would not matching the track loaded to deck
Fixed an issue with dragging Engine Prime Playlists to Finder or Explorer can move the files rather than copying
Fixed a crash on older pre-Haswell Intel core-i chipsets
Potential fix for crash on start up
Potential fix for hang on start up
====== end of excerpt =======
I keep wondering when will DenonDJ hire someone to really manage this software development team… the amount of wrong information, leading to confused users, over different releases is incredible for a company that has the stated goal of competing with the likes of PioneerDJ. While the hardware is great, the software and management is going nowhere.
Oh, by the way, it’s been called macOS for years now. OSX was the old way of referring to the Apple Mac operating system…
Pioneer are no angels - the firmware errors they made have been far worse.
Also consider this: pioneer make almost no improvements or give any new features in their firmware. So it’s all pro-rata. If denon release 10 firmwares and pioneer only release 1 - it stands to reason that there’s 9 more chances for a typo in some notes
1 Like
Agreed that other manufacturers do have their share of mistakes. But If DenonDJ really wants to surpass PioneerDJ or any other DJ brand in the wild, it has to be way better, not so-so, definitively not worse, than it has been over the last years in the software department. It’s a steep uphill battle it’s facing now, and with the current lack of attention to detail, it won’t succeed anytime soon.
But again, it’s the pro-rata thing to consider. Denon release far more firmware releases, so there’s more chance of a release having poor documentation
Then again, DenonDJ only has to release far more updates than others, because the main cause is they decided to sell half-baked products. Please note that, by “product”, I’m referring to the whole thing: hardware(excellent as it is)/firmware(half-baked)/software(way below paying customer expectations).
All subjective really. Everyone has different needs.
Also if denon didn’t invite or entertain user requests for brand new features on existing hardware, they’d have far less firmware releases.
But, for either reason, any release is good
I don’t mind the number of releases, nor the amount of, as you say, brand new features. I DO mind, though, the lack of quality (fix one or more things, break others) and the insistence on adding features instead of really fixing basic things that still leave much to be desired, specially in EP. If only they would admit the software is bad, and start over, but no, they insist on trying to mend a broken design. Also, the whole argument about minor mistakes on documentation is just one aspect of the whole software development mismanagement. I could go on and on, but let’s just leave it. And I say it respectfully, I don’t think I will change your opinion, nor you will change mine. PEACE.
Again, objective.
No-one, outside of the software team “know” that. Outside of the team, you and I can only guess. The other thing is, there’s no bad code as such. If a 15 in a line of code, isn’t performing then it can be changed to a 14 or a 16 or whatever. Just tweaks, nothing that means binning every line and starting from a blank page lol
Yes, there is bad code as such. Programming does not work as you describe.
I do agree by looking at how Engine, database navigation behave, as well as regressions in every release that there are proper issues that there.
Nothing to do with “tweaks” - it does not work like that.
I think it is time to consider an engine prime 2 made from scratch and meanwhile try to correct the current bug and leave everything new for the new version that in my opinion should be closer to what rekordbox offers
regards
After programming for over 35 years in several languages, there’s certainly nothing about about Engine Prime, or indeed most modern code, which id ever describe as bad code.
Sure there’s long winded code, where for example 50 lines of code get used to get a result, where maybe 25 lines of code would have achieved the same thing. Or code which doesn’t trap enough of the possible outcomes or situations/events that might occur like code which know la how to cope with any value bewteen 0 and 50, but someone didn’t tell the subroutine how to deal with minus values or 51 for example. If you’re saying that long-winded code or incomplete code is what you mean by “bad code” then we can agree there for sure.
Neither example is bad code just incomplete event trapping or rushed coding.
Engine Prime has only been around now about a quarter of the time that recordbox has, and about an eighth of the time of the DJ software titles. Nor is it supposed to be used as a performer tool during a gig - It’s for library management - understandable that it’s not going to be the same as traktor or the same as serato
I beg to disagree again… There is bad code. It’s code that is not suitable to addressing the problem it was suposed to address, or code that provide bad data and people makes wrong decisions based on that. By the way, I’m also on IT, having started in 1981,first as a programmer, then climbed the management ladder and ended up starting my own company from scratch.
Now, back at the issue at hand, if you ask a programmer to write a program that plots the route from people’s work to house and when someone uses that program ends up lost, because the program did not work as expected, then I suppose most people would classify it as bad, non working, wrong, whatever their frustration would warrant. But maybe you would like being astray. who knows…
Ploting wrong waveforms, beat grids and calculating wrong BPMs is the equivalent to being lost when using EP to analyse one’s music library, and have that same bad information transferred to your GPS (Prime 4 / other prime series units).
This reminds me of pilots in Asia too dependent on automation and autopilot with their manual flying skills degraded while they get “soft”, and some glitch crops up and people get killed. While no one’s going to die from DJing, I believe staying away from automation is the general solution to the general problem of the lack of perfection in automation.
Yes, having started with vinyl, I can understand your point. I also prefer to beat match by ear, but in my humble opinion, wrong information can sometimes be worse than no information at all. When we did not have GPS units, we would stop someone and ask for directions, or maybe even use a paper map. Now, with all the reliance in technology, I doubt anyone would prefer such methods.
Which is one of the reasons I’d like the option to make the BPM and moving waveforms black and disappear.
I would not go this far. I just want them to be right. As in “If you propose yourself to do it something, don’t just do it, do it right”.