You are here

Wav file corruption using We Transfer?

Page 1 of 1

Wav file corruption using We Transfer?

PostPosted: Wed Jun 19, 2019 2:24 pm
by Dr Huge Longjohns
I've been sending some 24bit stereo wav files to a colloborator via We Transfer and a couple of them seem to have got corrupted. Just clicks appearing randomly on the tracks that weren't there on the Logic project or on the bounced stereo files when they left here. The files are around 70MB each and were sent separately.

Anyone else experienced this?

Re: Wav file corruption using We Transfer?

PostPosted: Wed Jun 19, 2019 2:48 pm
by blinddrew
Not experienced this but if you zip them it should perform a checksum at the unzip stage and then you'll know you've got the exact file.
I'd also wonder about buffer settings at the receiver's end...

Re: Wav file corruption using We Transfer?

PostPosted: Wed Jun 19, 2019 2:50 pm
by Dr Huge Longjohns
Good point, I sent them as raw wavs

Re: Wav file corruption using We Transfer?

PostPosted: Wed Jun 19, 2019 4:05 pm
by Bob Bickerton
I use We Transfer all the time and have never had a problem - it’s an excellent service.

It’ll be a problem with the export or packaging. You can’t send folders via We Transfer, so best to Zip before send.

Bob

Re: Wav file corruption using We Transfer?

PostPosted: Wed Jun 19, 2019 6:21 pm
by wireman
You can also checksum files after transfer, or send the checksums with the files so a check can be done at the remote end. How easy this is to do depends on the platforms and users so using zip in the first place is a good idea.

Re: Wav file corruption using We Transfer?

PostPosted: Wed Jun 19, 2019 6:47 pm
by Forum Admin
SOS uses WeTransfer to move audio WAVs around from person to person but they are generally always in subfolders and we ZIP the whole shebang.

Never experienced any problems thus far. WeTransfer is a great service IMHO.

Re: Wav file corruption using We Transfer?

PostPosted: Thu Jun 20, 2019 9:18 am
by CS70
Dr Huge Longjohns wrote:I've been sending some 24bit stereo wav files to a colloborator via We Transfer and a couple of them seem to have got corrupted. Just clicks appearing randomly on the tracks that weren't there on the Logic project or on the bounced stereo files when they left here. The files are around 70MB each and were sent separately.

Anyone else experienced this?

It's very unlikely WeTransfer is the source of the clicks, there's multiple checkpoints of the integrity of data at the various protocol levels involved, and the likelihood that a data corruption survives all of them is extremely little.

Much more likely that something's off in the media where the files are stored, or in the source/destination machines.