WavFix is a lightweight application designed to address the Pioneer DJ Error E-8305. The open-source repository is here: github.com/Dre... You can support to the project and download WavFix for free on Ko-Fi: tinyurl.com/Wa...
Just trying to understand the order of operation when using wavfix.. My whole rekordbox library and collection are on an external SSD, and i've separated some tracks into designated folders. Most of my main library is just in a main library folder. But some albums, and compilations as well as where I have purchased and download from different pools are in their own folders. If I load in my entire folder where everything is store, and after it runs through wavfix, Do I take the new export folder and replace the existing collections of folders on my SSD? Apologies for my confusion. Just dont want to screw it up.
hey man, does not work for me aswel. Tracks have been cleaned, the application found the right one who were not working but even if they become green they still don't work
the problem is the bit depth and sampling frequenze that arent working in pioneer, you need 16 or 24 NOT 32 bit depth, also 44 or 48 kiloherts,,, other vise you need to re sample the tune with like free nhs software to get proper figures, to work in pioneers cdjs , just learned this , after looking throught several forums that people talk about this problem , so i would proabably use first way is to make all strange wavs to mp3 320 kpbs or seconde resample all the tracks that have 32 bits bit depth ,, over and out !
I would put them in the app first because it will check them all for pcm encoding and clean only the ones which have it. Whereas you will have to take them from rekordbox to a physical player to see which ones return the error. However one advantage of WavFix versus re-encoding the audio, is that because we directly modify the file, you won’t lose your hotqueues or any other data associated to rekordbox since the audio file remains the same. So that if you did go through applying hotqueus and then found the file returns an error; you can clean it without losing those.
does not work here I made exactely the process you teach. Put all playlists (over 1000 songs) - does not work put just 1 playlist (70 musics) doesnot work My pen drive has 256gb (i already convert for fat32 by a external software, this one dont allow format by the computer in fat32) but the same songs, with a 16gb pen drive work normally. (this pen drive allows format in fat32 normally) is there a possible of this issue is because 256gb is too much capacity ?
Could you describe what the problem is in more detail? What doesn’t work? What part of the process fails? When you say you are getting the 16gb drive to work do you mean that the files are not returning an error in the player?
@@dreamwalkertunes after a bought a 256gb pen drive, when I send my playlists, this Error E 3805 came thru. I found your video. Made all process with your program, the tracks in your program was All Green color ( I supposed the it worked after that) But when I move this clean tracks by your system to my pen drive, again this error shows up... I don't know what may I made wrong. This same tracks, in my 16gb pen drive, works normally. With or without the tracks ,"cleanned" by your program... I think maybe the problem is in this mew 256gb pen drive ?
Ive heard that it depends on bitrate because cdjs can play max 16 bits. Ive used the program and it works now but in the properties of the file it still shows more than 16 bit. Is there any reasoning behind this? and does it affect quality?
It’s because they are .flac files so WavFix will mot modify them. WavFix removes the PCM encoding from the header of a .wav file. It is likely that your player is not compatible with .flac files.
WavFix isn’t capable of corrupting the actual audio. The only case where WavFix can corrupt a file is if the file is already corrupted; ie the structure is not that of a wav file but the file has the .wav extension. This is because for efficiency WavFix doesn’t read the whole file; it only reads the first 22 bytes of exclusively files that have the .wav extension. Which if uncorrupted have a consistently structured header. So it doesn’t check for the integrity of the file which means if the data in the header is missing or modified; corrupted, then WavFix swill modify bytes which are not the PCM encoding. TLDR; the only way for WavFix to change any data that isn’t the PCM encoding is if the file is already corrupted.
No it won’t, it simply removes the pcm encoding from the header of a wav file. But that’s curious that you get the error with some mp3’s... How did you convert them?
I found a batch converter after searching through Reddit, I can't remember but I think it was dBpoweramp Music Converter@@dreamwalkertunes so annoying and I feel like I'm the only person in the world with this problem
i have the same problem with MP3 files. The annoying thing is you can never tell in advance which files are 'bad' because Recordbox export them without problems... if anyone knows a fix for MP3 files I REALLY would like to know!
There’s no way to ruin the audio with this tool. What is possible is you are playing the files on a piece of software that requires the PCM encoding contained in that bit. I have never heard of such a thing. The absence of that data is generally irrelevant to most players. Except in the case of the Pioneer players where it causes the error. But the PCM encoding’s purpose is to tell the player what type of data to expect; multichannel audio. In theory it’s possible some player needs that data. Outside of that very unlikely possibility, there is a different unrelated problem with your .wav files. WavFix will only modify .wav files. Wav files (unless corrupted) always have the same structure. Which uses a header with things like the artist info or the pcm encoding. Which means in a wav file bits 20-21 are always the pcm encoding (unless it’s corrupted). And for efficiency purposes WavFix only has access to bits 20-21 of wav files. So the only condition under which WavFix can change something that isn’t the pcm encoding is if the file is already corrupted. I could add into a future version; the ability to check wav files to ensure they are not corrupted already. But that would mean reading a LOT more than the two bytes of data and so would slow things down quite a bit. However, I’m considering WavFix Pro with a lot more features for repairing wav files including using machine learning to attempt to fix corrupted files. That’s a lot to pull off as one dude and someone probably already has a good lead on that. It’s basically Topaz ai but for wav files. Creating the training data would be very very time consuming.
