MIXVIBES Dj Community old forum

Hallihallo, ich nutze Cross sowie Cross DJ auf Windows 7 64Bit und seit dem Cross3.2.0 Release werden diverse Tracks in der Collection mit Releasedate (Veröffentlichungsdatum) des Jahres 2020 angezeigt... Ich bin ja gerne up-to date aber das ist definitiv ein Fehler. Vielleicht kann mir ja jemand helfen oder hat das Selbe Problem oder am Besten eine Lösung parat...?
Vielen Dank schonmal im Voraus.

Bin ich etwa tatsächlich der Einzige, bei dem dieses Problem auftritt???

Sorry for my German,
You're at least the only one reporting it...
I checked my column 'released' and could only find like 20 tracks (of 80k) with a date in this field.
Most likely this comes from the tags of the imported file tags.
You may want to check in e.g. explorer to see if a release date is present in the tags.
If Cross added a date to the field in the collection (as a bug) it is very unlikely the tags of the file were updated as well.

The most Tracks are bought at beatport, others are recorded from vinyl-records. At the Beatport Tracks the releasedate is added to the tags and at the recorded Tracks i add it manually into the tags. It worked perfectly up to Cross version 3.0.0.

This info triggers some more questions.
- Did the 2020's have a different date before (might you have a backup collection).
- Are only newly added tracks wrong.

Not having this issue makes it a little hard to narrow down what could've gone wrong when, but maybe going back and forth might help to pinpoint it. Dates aren't the easiest to figure out as many OS and application settings are in between the stored info and the actual visualisation of the date.

Yes, the 2020´s do have other (different) releasedates. In Cross 3.0.0 it´s working and it show´s me the original releasedates. Since the updates 3.1.0 and 3.2.0 there´s the mistake with 2020.
A mistake into the Track-Tags can be closed out. At many Track´s there´s not shown the Release date anymore, some are right and many are 2020. It doesn´t matter if they´re recorded or bought.
some are working, a lot of aren´t.
How I wrote, in the version 3.0.0 it´s working perfectly...
It´s not possible to minimize the problem to Track-Specifics...

ok...seems like nobody is able to help me with this problem...