Osstatus Error 208

for theWindows andLinux version Subscribe to RSS feed Rescue of a WAV file « What is Reverse Engineering? Synalyze It! Developer Weblog Doxygen and DocBook » Not long ago a man contacted me

Fix Corrupted Wav File

and asked for help.He had interviewed someone (audio+video), however the audio recording was wav header interrupted at the end. Since the file was not readable by QuickTime and the interview couldn't be repeated you can imagine wav file format the situation in which he was.Now, how to rescue a WAV file that wasn't written until the end?Unfortunately the user didn't know anything about binary files, their formats and what could be wrong with an audio file. His first idea was to copy the end of a valid WAV file to the end of his interview to make it work.So he sent me a short audio recording of 3 seconds to extract header and footer as a first step to repair his main interview file.But… while WAV files indeed have a well-defined file header, there is no such footer - this means, the idea to fix the file end couldn't work! We had to take a different approach…He then downloaded the free version of Synalyze It! and applied the grammar to his file. Because all the structures and their elements was Greek to him he proposed to send me the file.Before doing so I wanted to know if even an unexperienced user could solve such a serious problem on his own by learning the basics of the format underlying his file.A WAV file starts with the RIFF header, followed by so-called chunks, similar to those in PNG files. What could be wrong with his file? First, we tried to fix the size field in the RIFF header structure which was zero. Obviously, since the recording software didn't finish its job and couldn't set the correct size after recording when the size is known.This didn't do the job, QuickTime still complained with an "OSStatus error -208".We had to dig deeper and in the Sample Data chunk we found the solution: There's also a size field that informs the reading software how much data follows. Our unfortunate but courageous user filled there the size of the audio data.He wrote in an email to me:"It worked!!!!!!!!!!!!!!!!!!!!!I opened some other f

Video "unable to parse audio file" and "OSStatus Error -208" ! User Name Remember Me? Password Register FAQ Today's Posts Search Search Forums Show Threads Show Posts Tag Search Advanced Search Go to Page... Thread Tools Search this Thread Display Modes #1 03-05-2009, 07:57 PM reichman Member Join Date: Aug 2000 Location: New York Posts: 1,596 "unable to parse audio file" and "OSStatus Error -208" ! Hello DUC: While opening Pro Tools https://www.synalysis.net/developer-weblog/rescue-of-a-wav-file.html sessions in v8 that were created in v7.4, I ran into a show-stopping error: "Unable to parse audio file xxx". The session wouldn't open. I recovered the offending WAV file from the Retrospect archive, tried again, and then another file had the same error. Suspecting something deeper than a Pro Tools problem (ignore for now the 7.4>8 issue), I found http://duc.avid.com/showthread.php?t=240896 that the Leopard Finder couldn't play these files, but many other files from the same session were fine. Quicktime Player told me that it couldn't open them because of "OSStatus Error -208". Barbabatch iTunes, and Izotope RX refused them too. Now I was really worried, and was unable to dig up any useful information about these errors online (including a search here on the DUC). Only a snapshot Retrospect restore saved me. This is very scary data corruption. Any ideas? Solutions? My sense is that if this happens and you're not backed up, you're hosed. Thanks in advance for thoughts, Nathaniel Reichman www.nathanielreichman.com MacPro 2.8Ghz 8-core, 6GB RAM, 10.5.6, Pro Tools LE 8.0.0cs2 with Complete Production Toolkit, Digi 002R, Blackmagic Intensity Pro, eSATA hotswap tower, Baby HUI, Soundminer 4, Waves Platinum 6, Audio Ease All-In, Melodyne, SoundToys, Izotope RX, GRM Tools, PSP, Retrospect... reichman View Public Profile Send a private message to reichman Visit reichman's homepage! Find all posts by reichman #2 03-06-2009, 11:44 AM DigiTechSupt Avid Join Date: Jan 2000 Location: Worldwide Posts: 33

van GoogleInloggenVerborgen veldenZoeken naar groepen of berichten

NewsletterHelpKnowledge BaseReferencing AudioSharing directly from FCP X to X2ProMedia Locations HelpSupport ForumBuy NowEducational Discount IndexLatestSearch Welcome, Guest Username: Password: Remember me Forgot your password? Forgot your username? Create an account Forum X2Pro Audio Convert X2Pro Failed to open audio extractor OSStatus error -208 TOPIC: Failed to open audio extractor OSStatus error -208 Failed to open audio extractor OSStatus error -208 1 year 3 months ago #2193 Jeremy Norwood Offline Moderator Posts: 450 Thank you received: 16 Hello, Could you provide me with the file "Grito caida.wav"? The Mac Error 208 returns back what is in the [ ] after the code "[was not type AIFF or was of bad format,corrupt]". Please read the forum rules before making a new post. Copy and paste the text from any error message. Please don't post screen grabs of X2Pro error messages. Investigations into issues when converting a project will be faster if you attach your fcpxml file[ If you are having trouble with X2Pro's "Media Locations" or the app sandbox, please read this explanation and guide for help. If you seeing the error message "not a WAV file or too many audio channels", please read this explanation. The administrator has disabled public write access. Failed to open audio extractor OSStatus error -208 1 year 3 months ago #2187 matias.rey.segovia Offline Fresh Boarder Posts: 2 Hello..? is anybody out there..? The administrator has disabled public write access. Failed to open audio extractor OSStatus error -208 1 year 4 months ago #2175 matias.rey.segovia Offline Fresh Boarder Posts: 2 Hi all, i'm working with a FCPX Project, trying to export the aaf file from the xml. I've close all the apps, only let open X2Pro, select the xml file, the destination... etc. - OS X 10.10.3 - FCP X 10.2.1 - All permissions are corrects. - Quick Time opens the file - The media has not been moved or deleted - I