Bug- Tags not updating in collection

Hey Daniel,

The fact the track is loaded to the collection when previewed or edited is normal, rekordbox presumes you want to eventually add songs when performing these functions, so it does that for you. And given that a MyTag can only be added to a song in the collection, it would naturally require it to be within the database (in the collection) for the tags to be added or edited. But you're right, editing the MyTag in the Explorer view did not update the comment field -- I'll pass that along.

I have thousands of songs I don't want to add to my collections.  How would you suggest someone go through a folder and decide which songs to add to a collection? You need to preview it in order to decide if you want to add it.  Right now, there is no option. I think the presumption that the user wants to add it is a problem.  There should at least be an option "automatically add songs to collection", that, when disabled, requires the user to use the "add to collection" button. At the moment, my collection keeps getting filled with stuff I don't want.

Still, if you're going to add things to my collection automatically, it would be great if I didn't have to re-tag everything in collection view.  The way things are now, it seems you would expect me to add everything into my collection first, tag it there, and then remove from collection things I don't want.  Everything would work fine that way if I didn't have a massive library of tracks I don't want in cluttering up rekordbox.

Can I ask why you wouldn't want to add them to the collection? If not, why are you using rekordbox to preview them at all? Why are you keeping the files if you don't want them in the collection?

Personally, I don't exclude songs from rekordbox - I import everything, then if I don't want it, I'll remove it from the collection and/or delete it from the hard drive.

I agree that it shouldn't require the re-tagging, that's a bug we'll investigate.

I currently use MediaMonkey to organize ALL my music.  According to that app, I have over 540,000 tracks in my music folders.  This includes albums, mixes, downloads, and things people have shared. Media Monkey is far superior for managing ID3 tags and previewing audio. However, there are other things that can only be done in RB.

Rekordbox on the other hand is only for things I would DJ with.  That means anything in Rekordbox needs to be previewed, metadata clean and correct but also beatgrid checked, and properly tagged.  Obviously, this is not possible for ALL my music. If I added everything, I would not know what is clean and what is not.  It would make it much for difficult to find things.  That's why I don't want things added to my collection unless I've completed my screening and preparation of a track.  Is that not a normal workflow?  Why can't I listen to a track before deciding if it shoul be in my collection?

If it helps, with regards to the bug, if I have multiple tags set on a track, when I go to the collection to "re-tag" so it writes to the comments, I don't have to re-tag EVERY tag.  Just unchecking and checking a single tag will write all the selected tags to the comments. 

This was fixed in the 6.0.1 release; please update to see if it's working for you.

I can't.  I'm stuck on V5 now.  If I uprade to 6 then my license that allows me to use performance mode with my CDJ will be useless and I'll have to pay a monthly subscription to use it.  Switching back to Traktor.  Amazing that you guys would force a monthly subscription on someone who already spent a ton on hardware.  Thanks.

We're not forcing anything on our customers. If you've got a license for version 5, you can continue to use version 5.

That's what I said.  I'm stuck with version 5.  Unfortunately that means I won't get the bug fix either.  

No you're not forcing me to use your product. I'm free to stay on 5.  I'm also free to switch to Traktor and use my CDJs as controllers..   You're just taking away a capability that I already had  unless I pay you a monthly fee.  What's worse, there's no reason for it.  You already enable hardware unlock for people with cheaper devices.  

"We're not forcing anything" is meaningless.  You know very well what the implications are for not being able to upgrade.  I'm not here to convince you.  The results of your product decisions will be speak for themselves.  Feel free to disregard my feedback.  I'm only a customer.

Daniel, I don't understand why you keep insisting we're preventing you from doing things you did before, or taking things away:

"You're just taking away a capability that I already had unless I pay you a monthly fee."

That is entirely not true. You still have the capability to do everything you already paid for on rekordbox 5, and you even acknowledged it. You never had the capability of using rekordbox 6.

It's only if you want to upgrade to rekordbox 6 with the new features it provides, then yes, you would then have to purchase a subscription. You purchased access to rekordbox 5, and you still have that. This is no different than buying Ableton Live 9 and then when Ableton Live 10 comes out, you're upset that you have to pay for it to be an upgrade.

Are you upset only about the fact it's a subscription model now and not a one-time purchase? Because you could certainly achieve that by buying a DDJ-SP1, SP2, or Interface2. All of those devices unlock not only performance mode but DVS as well as the SP units providing additional hardware control -- and as they can be found for sale online used for less than $200, that's roughly the same as 2 years of the core subscription.

You also said:

"What's worse, there's no reason for it."

Your hardware never came with a rekordbox key, so no, it doesn't get a hardware unlock for free, regardless of less expensive players shipping with that ability ... which rely on rekordbox to function whereas your CDJs are stand-alone players. If you are using them as controllers, that's a hefty investment for hardware that could do the same thing costing 1/3rd the price or less.

The reason for it is most DJs who are using the equipment you have are not using it as controllers. They're using export mode and playing in stand-alone mode. And for those who are looking for the advanced features, they're going to reach for the Creative plan for services like Cloud Sync.

Again, I'm not complaining about 5.  I was fine with 5 except for this bug.  No, I don't have to upgrade to 6, but that means I don't get the bug fix.  (My original point).

And yes, with Rekordbox 5, you didn't get the feature with you needed to pay for a license in order to get the performance features.  This allowed you to use CDJ's as a controller.  Done deal.  No monthly fee.  But if I want to upgrade I have to pay every year as much as it costs for the 5 license; just to keep the same feature I had already already had.   So yes, I am annoyed that if I want to upgrade and fix my the bug, I not only have to pay for something I had already licensed, I have to pay for it on an ongoing basis.

I do find it fascinating that you are suggesting I buy additional equipment, with less capabilities in order to avoid the subscription.  I guess spending $4k+ on equipment on top of an existing license.

I'm sure some users will make use of your cloud sync.  Those types of services have ongoing costs and require an ongoing subscription fees to support them.  This is just a feature you chose to disable.  You could easily have included it for higher end devices; or at the very least for people who had already licensed performance mode.  

Sorry, I'm a product manager for subscriptions services.  I know how these things are marketed.  I am irked enough when people grab for recurring subscriptions for features that don't require ongoing services.  Even more so when that feature previously had a flat fee license.  Even more so when it's given away to people who bought much cheaper equipment.  Really makes me happy I made the investment in your best equipment.  Spend more, get less.   I'll be sure to recommend it to others....

Following up with additional information on the "bug" complaint; if a song is actively loaded to a deck, the file itself cannot have the tags written because the file is in use. This is a limitation that we are unable to work-around.