Bug affects songs that have never been edited in djay Pro.
Bug affects songs that have been analyzed or are un-analyzed.
Bug does not repeat after track has been edited and re-loaded onto deck. At that point, you can load a song on to a deck and edit the metadata, without the waveform disappearing → this remains true even if djay Pro is re-started.
I am particularly tracking many bugs because I think the underpinning factor is that
EITHER:
the app has grown alot heavy on even the most powerful of machines. I am an intel mac user (2019, i7 MBP), and I don’t believe our macs are incapable as some users might suggest.
OR:
something in the new updates is taking up too much priviledges (over basic playback) and overwhelming system resources to the point that sound output and visuals are affected
Hi @Michael_Wisniewski, thanks for the details about your setup and the issue - this is very helpful! Unfortunately, I was not able to reproduce this on my M4 MBAir, macOS 26.1 and djay 5.5.1. I have forwarded this to the engineering team to see if they can reproduce the issue on similar hardware to yours and offer any suggestions. I’ll report back here when I have news. Thanks!
try this step to reproduce bug:
1- play a track in any deck
2- open same track in mp3tag or similar editing program
3- edit metadata
Result:
track playing in djay goes blank as describe above.
Okay..
Well the truth is, that a file can’t be open to read and write at the same time.
That’s just the way operating system works.
You could check this like in python programming
I know, you would say that it’s possible to do it like notepad or another editing tool to edit .txt files.
Those tools works differently : they are reading the whole file into memory to avoid locking the actual file. So that for users it seems that files can be edited simultaneosuly.
When it comes to files like mp3’s.
The id tags are stored and written first into the file and the actual “music data” after metadata data.
What it means that if you edit the metadata files, those bits needs to be stored to the files.
Eventually that will affect to the fact, how the waveform is read out of the “music data” bytes as the file has been changed. That means that there will be small delay to refresh the “waveform” even though it might have not been changed.
But djpro can’t know what have happened to file, who changed it.
Was it some other tool who edited it?
It just knows that the something changed => and whole data structure needs to be read again.
You just can’t read only the changed bits.
Letsay that the file doesn’t contain any metadata.
It’s like, a= representing audio.
aaaaaaaaaa
Now you are writing metadata to the file “m” with mp3tag or anything else.
maaaaaaaaaa
Now the size of the file has been changed, so djpro needs to re-read the info, ie. read tags to collection and reread audiobits and recreate the waveform. There is no way to know what bits has been changed only the size of the file.
Now it’s okay as the metadata (I suppose with the waveform) has been read into collecion.
Now djpro can allow you to edit the metadata in collection, while you are playing the song.
When you have unload the track, the djpro can write the changed metadata into the file.
mmaaaaaaaaaa.
And you can reread/refresh the info with mp3tag.
They suspect this only affects certain file types (e.g. only MP3 or only M4A), as some types may store the metadata at the beginning and others at the end of the file. The issue makes sense for formats that store metadata at the beginning of the file, as editing the metadata would essentially shift the audio data in the file. Can you please confirm which file formats you are experiencing this issue with? Thanks!
