DP-32SD - Writing Failed - issues with importing certain wav files - conformance errors

FrancisT

New Member
Joined
Oct 31, 2024
Messages
1
Karma
0
Gear owned
DP-32SD
Hi users,

I've got a friend's DP-32SD with a frustrating problem. He's brought me in to help troubleshoot - my background is more in film & TV / camera department however I've got a reasonably strong technical / IT proficiency.

We've updated firmware from v1.05 to v1.11
We've ruled out issues with SD cards, USB cables, Chromebook (what the owner is using) vs MacBook Pro (M1)
We've done factory reset / initialisation.
... to no avail. So far I also haven't found any posts that refer to this specific problem.
This I'm told is also a new problem that was never previously an issue.

The owner has a number of tracks previously made on the unit. He's got them saved on his computer and wants to import them in through the usual process of USB connection, copy and paste to the AUDIO DEPOT folder, eject, and then import the audio wave file from AUDIO DEPOT (16bit 44.1KHz) to any particular track within the SONG.

Some tracks import fine and you can then go ahead and hit PLAY/STOP and no problem at all. There are however specific wav files that play back fine on the computer, but when after you successfully import the file from AUDIO DEPOT into any particular empty TRACK and then hit PLAY and then STOP again, you get a Writing Failed message.

The only way to start again is to QUICK format the card (from within the DP-32SD) and start all over again.

I've tried loading the file into Adobe Audition and Audacity and then re exporting the file back out as the same format of wave file in a bid to see whether any corruption may exist in the file, and this is where my technical experience may fall short of what further to do. It seems like we've ruled out all the other variables to be just an issue with the wav file and the DP-32SD not liking it.

IMG_2218.jpgThis happens from after you have hit PLAY, and then hit STOP.


Here is a screenshot of a wave file that works no problem.
Screenshot 2024-11-01 at 2.24.14 PM.pngScreenshot 2024-11-01 at 2.27.15 PM.png

And here is a screenshot of a file that stuffs the whole system up.

Screenshot 2024-11-01 at 2.26.54 PM.pngScreenshot 2024-11-01 at 2.27.29 PM.png

Here we can see the difference and most likely the issue is - Conformance errors: 3 and then the addition of RIFF: Yes.
This is where I'm stuck. What could this mean? The file plays back fine on a computer. I've tried following some of the steps here in the Youtube video with a byte offset of 0 and 10 and same outcome.

Obviously something dodgy has happened to this and many other of his files somewhere along the way, however given the fact that they seem to play back fine on a computer (although not that I have listened to the tracks back to back), I would hope there is someway to fix the issue?

Any help would be much appreciated. Thank you!
 
Welcome to the forum, @FrancisT .

The OM error messages section has the "writing failed" error message in the system fail section, and advises:
"If any of these errors occur, turn the unit's power off and restart it. If the error message continues to appear frequently, please contact the store where you purchased this unit or a TASCAM customer support service."

That said, there may still be a few things to consider.

The owner has a number of tracks previously made on the unit. He's got them saved on his computer and wants to import them in through the usual process of USB connection, copy and paste to the AUDIO DEPOT folder, eject, and then import the audio wave file from AUDIO DEPOT (16bit 44.1KHz) to any particular track within the SONG.
Typically, a direct copying of the entire song folder to a computer and moving the entire song folder back works flawlessly for backup/restore purposes.

When using Audio Depot for restore purposes, the tracks must first have been exported using Audio Depot before they can be restored using Audio Depot. If that sequence isn't followed, then there could be a fatal disconnect with the edit.sys and/or the song.sys files in the individual song folders.

Another possibility might be use of an sd card not TASCAM tested/approved for the DP32SD. File Errors, Write Errors, Freezes, Lockups, etc. have all been traced to use of SD cards not on the TASCAM approved list, counterfeit SD cards, out-of-date firmware, or all three.

The "Equipment Related Tips" sticky thread also has a few posts about common file/sd card related problems that may trigger some thoughts for you.
 
Last edited:

Members online