Stop traktor from editing my ID3 tags..please (also a bug)

I 've send them samples myself....

 

Hi Guys,
I agree that traktor should not change id3 tags.
I am a dance instructor and I changed all BPM fields of my songs to be able to selet one with the correct speed. In our world a song is rated for his speed by dividing the BPM by the bars.

Example:
JIVE: BPM for a song is 160 and divide by the Bars (4) gives you a speed of 40
SLOW WALZ: BPM for a song is 87 and divided by the Bars (3) gives you a speed of 29

As there is no field to enter this speed, I changed all the BPM fields to match the speed figure. This alows me to immediately see if the song I select is a fast or slow one for that kind of dance. Beginners must dance at lower speeds (songs) than experienced once.

I have no problem that Traktor analyses the track and find the correct BPM but Traktor cannot change the tag of the BPM. After a set I have to manually change all BPM's again of all the tracks I played.

For me it's the BPM tag that is important but for other users it will be other tags. The request for not changing tags is founded and not a minor issue.

NI please correct this!

Regards,
Geof.

 

As a work around you could use the comment field for the devided bpm.

 

Nice suggestion but the comment field is alreadu used for other content

 

I guessed that you already have considered this, but I thought I'd mention it anyways Maybe you could add the BPM to the note field like this: [40bpm | Some other content...] - of course we are still talking about a work around, not a solution.

 

+1

For an option to not write tags. I've seen Traktor mess up release dates (ie; setting 01-01-year) and timestamps. I dont want to have to mess with permissions (on numerous folders) or workarounds, when there could be a simple on/off option for it included in prefs.

It would also be nice if there was an option to restore the original timestamp (to keep the creation date) also.

 

I don't think it's so simple... I wrote it before that in order for Traktor to function properly it needs to write some info in the tag of each file. The problem is not in writing that extra info, but messing up the existing info.

If there was an on/off option Traktor would not function properly, since it needs that extra info, or it would have to do the same job for each track every time it was loaded, which would also be very frustrating.

I thing it's just a bug that hasn't been taken care of yet...:angry:

 

Ok, so I went through the trouble of attempting the "workaround" (of making the music folders read-only);

I changed the perms of all music/mp3 folders, Created an additional profile for Traktor S4 PRO, and ran the Traktor PRO S4 application using "Run As other User" (under Windows 7) so that Traktor has only read access to the music/mp3 folders, but found that this endeavour is a complete waste of time because doing so seems to disable the ability for Traktor to analyze the files entirely. It also showed a huge majority of my music as missing (AFTER running a consistancy check), and upon manual confirmation the files were not missing, nor were the tags modified.

As an added note, if you are dealing with mapped network shares, and using the RUN AS option, Traktor seems to think that the folders are missing (and prompts you to relocate or provide the path) on every load, even when...after loaded, the mapped share is there and fully accessible by Traktor (another bug?). I am sure I will waste even more time troubleshooting, attempting the "consistancy check" + "analyze missing" process again under the Traktor profile itself, but I'm sure it will not make any difference in respect to not being able to analyze the files, which seems to me that it makes the entire workaround attempt to be a pointless endeavour.

I read somewhere in the forum that at least one of the reasons Traktor PRO / Traktor PRO S4 wants to rewrite our tags is to convert/upgrade them to v2.4(?) tags, and if that is the case does this really have to be mandatory? And if it has to be mandatory, Traktor should NOT reset the timestamps, (or overrwrite any existing tag info) or at the very least it should give us the option to keep the original timestamp of each file, (or any orginal tag info), (equals options to "NOT overrwrite tag info" and option for "KEEP original timestamp") and if Traktor can keep stripes and transient info in it's own folder, it would be nice if it could do the same with any other additional info that Traktor feels it must have, and give us the choice/option to write that info to tags OR to the collection (or both).

Also Traktor still after almost 2 years of using this software, stops the entire analyze process when it encounters a bad wma (or a file tag it cannot read) that is otherwise playable in other players. As a result of this bug the collection will not save properly afterwards either, rendering the entire time consuming process of running a "consistancy check" + "analayze missing" (on a large collection)... a complete waste of time, cpu/mem resources and disk accesses, unless i remember to exclude those files from the process by manually selecting which files to analyze or delete those files entirely, but again these files that Traktor thinks are bad, are completely fine and playable in other players so deleting them is not an acceptable workaround either.

Now i love using Traktor, or i wouldnt have purchased an S4, but how long does it take to fix these bugs that have existed for more than 2 years or longer? If it can't read a tag...it should just move onto the next one. And stop messing with our tags and timestamps already.

Please fix this behaviour already. Workarounds just don't cut it.

 

That last comment was the equivalent of if you don't like it, you should go elsewhere. A program is supposed to do what the user needs or wants it to. The user is the most important part of the software. The code needs updating to remedy this important issue.

 

Sorry, but I really fail to see what you mean as you are agreeing with what the post above you says, no ?
The post before you by commentor is merely trying to look for alternatives as well and is as productive as it can be on a forum - going by suggestions of others, trying them for one self and commenting on why they do or in this case don;t work, which most of us agree on (apart from you maybe as I am not sure what you want to sayr...). Commentor's move I woudl interprete as a frustrated one though as NI doesn't seem to react / acknowlegde these forum feature requests publicly apparently.
So it seems the only way for us to go about this, is to each log their own bug with NI support that the state this is in, is unbearable - especially should it be found in Traktor 2 as well, or at least that's what I will hold out for and see if it has been resolved in 2...
Good luck for everyone that this is better thought out & realized in T2...
c.

 

Or vice versa

 

The other guy was basically saying just deal with the issue or go elsewhere. I felt that was an incorrect statement. I said what I said to address that. I do appreciate the idea of a work around, but it should be fixed or addressed if it is an issue.

 

Anyone know whether the date issue is resolved in TSP2?

 

I just downloaded the demo yesterday and tried a few tracks. Unfortunately it's still modifying the tag just like TSP

Somehow I find it funny that this is even an issue. The thing is that that all they would have to change in the file writing process is to write to a "ReleaseDate" tag, which is the actual name of the column, instead of overwriting the "Year" tag. Reading the file would be just as easy as they would only have to change the tag to read the date from & keep everything else pretty much exactly the same (unless their code is really that convoluted!).

Even just adding an option to "only write to Traktor database" (which Traktor already does for some info & like how Traktor 3 used to work I believe) would work just as well.

As minor as this issue may seem I would likely never use Itch (or any other software) again if this was fixed

 

Very disappointed about this. TP2 is still doing the destructive, non-standard compliant way. I won't buy the new version.

 

I use the following programs.

PC - Change Properties Now (not specifically for W7, but it works) - wicked fast attribute changing on Windows. Be certain to select the correct drive, filter by MP3 (or similar), and click Read Only. If you select "C" with no filter, you just messed up big time.

Mac - BatChmod (you can actually do this through command line, but this little app rocks) - almost too easy, especially if you're not familiar with CHMOD. Just pick your music folder(s), click the "Apply to enclosed folders and files" option, and unclick "W".

[EDIT added other software suggestion]
...also, backup your music database (I have five copies of my 500GB library), and use a Sync program. The latter will easily let you know when something got changed. I suggest GoodSync. It runs on PC/Mac, and has a lovely interface that quickly identifies changes, as well as allowing you to easily change direction of sync in case something gets changed. AllWay Sync is also good, but the interface is primitive in comparison (additionally, PC only).

 

Hello NI. This is a BUG, not a FEATURE.
Perfect program expect this one ****ing issue.
It messes up stuff we pay for (music files), can't be.

Give us a chance to disable this please
As a user I should be able to select if it writes stuff in my files except analayizing data.
I'm not going to buy Pro (rather go for Itch 2.0 or anything) until that is fixed.

 

i see no problem with trakor adding 2011-1-1 to the tag.

 

Very funny... Just to clarify for people who aren't trolls: This is obviously a problem, since the track is not very likely to have been released on January 1st...

Would anyone like to state that they don't see the problem with files having multiple genres such like "Tech House", "Techno", and "Downtempo" irreversibly concatenated as "Tech House Techno Downtempo"? Just imagine having a huge music library organized with many multiple fields tags and then having everything concatenated -- it destroys it...

 

2011-01-01 is not nice but accaple, easily to change back.
It's just that 20% of my tags are missing after traktor analyzing.
That's why I want that stupiud autotagging to be disabled