Reproduction:
Additional comments:
Environment:
Figured it out… just as you said, Speukulos, you need to find the ONE working "flags number" -
Hope that clarifies with more detail for anyone following this thread,
Spekulos, great work! Saved me hours and hours of re-stemming my collection. I had about 5000 missing stems all sorted in less than an hour!!!
Right now I am having this bug coming from nowhere, all my stems are disappearing when i load them ! (Traktor 4.2.0 on Win10)
Yep. This makes sense. I stemmed maybe 1,000 files this spring (yes, 15 at a time, and took months), and maybe 3/4 of them are gone, because subsequently, over the summer I was doing metadata work on my collecton using 3rd party utilities - ie, used SongKong to grab missing year files, using PerfectTunes to grab missing artwork, did some other stuff in iTunes and wherever else - and most of the stems are missing and now I know why. Thx for the post.
What I need to know is if those now-disassociated stem files still remain on the disk, taking up space? And, if I re-stem them, will I then have 2 stem files on the disk for that given entry, or 1 (of course with just 1 being associated with the Traktor entry)?
When stems disapears they are not removed from hdd.
When you regenerate stems it will just erase already exisitng stems files.
If you dont want to regenerate stems you can hack the collection.nml and change for each entries you know there is a existing stem : "FLAGS=XX" to "FLAGS=76". (i get the flags value from entries containing working stems links, check in your collection it is the same value !)
It is what i did to restore all my stems.
But be very careful it can corrupt your collection if not done properly (backup++).
If you dont know how xml works dont do it and regeneate your stems !
Spekulos, can you explain a little better please? I would love to be able to recover all my stems… Yes, I am familiar with using a text editor on the collection.nml file, i do it all the time to switch syntaxes when using same collection from Mac to PC, and PC to Mac.
Hold up… seems in doing the exact methodology above, I have indeed recovered my missing stems, BUT in the process, it seems THE REST of my collection now all has broken stem icons, meaning, the .nml file now thinks that the rest of my collection HAS associated stem files when in reality it doesn't. As such, I see a stem icon (but reddish, and appears to be a "broken" stem icon) for each of the rest of my collection, and when i try to load one of those songs, it tries to load the stemmed version (which doesn't exist). If I hold shift when loading, the regular non-stemmed file loads properly. I'll work on this tonight and report back when i figure it out.
Working this out on the fly here… it seems that, within collection.nml, FLAGS="76" is the designation that an entry has associated stems for it… therefore, if you do a mass replacement of "FLAGS="14" (or whatever number) to FLAGS="76", Traktor will expect all of those changed entries to have associated stems (whetehr they do in reality, or not). Your missing stems (the ones with flags 14) will now be there, but now all manner of other files will have missing stems that never existed, and you'll have to right-click on each and "delete stems" to break the bogus link. Of course, there seems no way to group by broken stems into a smart playlist, moreover, you couldn't right-click on a group of these and delete associated stems. Like the creation of stems, deleting would have to be done one at a time. Therefore, none of my above methodology will work in all practicality since entries with missing stems do not all bear the same flag, and all seem to share flags with non-stemmed entries.
The solution (in the context of a workaround) would be to somehow group or identify the entries with missing stems inside collection.nml, which doesn't seem possible. Sure, we know now that FLAGS="76" is the destination marker for stemmed files, but we're trying to mass-reassociate stems here, not do them one at a time as Spekulos seemed to suggest.
Anyone following this? Any ideas how to identify the entries with missing stems in collection.nml ? If we can identify them in mass within collection.nml, we could be in business and change JUST THOSE entries to FLAGS-"76".
Did you know what you did before getting boken stems link ?
In my case i a m not sure but it is related to :
-Activating "Write all tags to file" in preferences
AND/OR
-Externally editing files id3 tags with another software (like mp3tag)
Guys in this posts are trying to replicate the issue : https://community.native-instruments.com/discussion/46512/why-traktor-reset-track-cue-points-and-color-when-edit-id3-tags?tab=all#latest
Hey! Interesting, I will check it out with the team, and we will see if we come across any other ideas. Thanks for flagging this.
-Activating "Write all tags to file" in preferencesAND/OR-Externally editing files id3 tags with another software (like mp3tag)
Yes, that's exactly my problem too. After I update my tags in One Tagger, Traktor can no longer find the link to the previously generated stems.
Hey Owner, yeah same thing happened with me. I edited my songs' metadata using SongKong, iTunes, and a handful of other utilities, editing the cover art, release year, and perhaps a few other odds and ends, and that did it for me.
I don't think the "write all tags to files" has any bearing here. Why would it? In this case, Traktor is having trouble READING changes made to files, and this issue has nothing to do with it WRITING the changes. If I have working stems in Traktor, i close traktor and make metadata changes outside of Traktor, and re-open up Traktor and it cannot find stemmed files, Traktor has done no writing to files when the error occured.
Moreover, I keep my "write tags to files" checked always, as I do want any changes i make in Traktor to reflect on the files themselves.
I just want to add that I did go thru the effort of confirming 100% that, if you have stems vanish, the stemmed files remain on the HDD, taking up space. Re-creating stems for these files adds no extra space on the disk, it just re-associates itself with the space already taken up.
ie, I create 100 stems, i close traktor, i edit the metadata of these 100 entries in iTunes or wherever, i go back to Traktor and the stems vanish as if they were never created, I go and recreate these 100 stems in Traktor, and at the end of the day, no additional space has been taken on the disk.
Good to know. I suspected this would be the case but never checked myself.
@Martiniix_NI I think you can replicate the bug by enabling "Write all tags to file" with a collection with stems generated. Then close Traktor. Then change the most possibles id3tags with mp3tag (including key tag and bpm). Then start traktor and load stem track, you should see stem link disappear (and other stranges alterations)
