Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro AVI File Corruption on Massive Scale

  • AVI File Corruption on Massive Scale

    Posted by Keeley Charlton on March 8, 2013 at 6:42 pm

    I didn’t want to post in both this forum and Vegas since I couldn’t find a forum for discussing editing in general so I posted here as I use Premiere as my primary editor.

    This may be long winded so here goes.

    I record many videos from online gameplay using multiple software and hardware tools (PlayClaw, DxTory, Fraps, Hauppauge Collosus). Up until 2 days ago all of these various file formats and recording were all viewable and importable into Adobe Premiere 5.5 or Sony Vegas Pro 12.

    – Files WILL still play either using VLC media player or Windows Media Player but can’t be imported into either of the editors.

    – New files or even old files that I could once import before can’t be imported anymore. In Premiere the import process causes a BSOD after a minute part way through the file import and waveform audit. In Vegas I get an error stating that “None of the files dropped into Vegas Pro could be opened”.

    – The BSOD resulted in and error code related to a very ambiguous field of error possibilities but it did show that my mv9xx.dll driver seemed to be the final fault error after all BSOD’s.

    – Further inspection and attempted resolution to solve the BSOD I reinstalled the newest drivers and bios for my MB including the Marvell SATA drivers. For the record I tried just using the Intel SATA drivers and the Marvell drivers only and a combination to no avail. I have also tried the drive in different SATA ports.

    – The drive in question is only 2 weeks old and is a WD 2TB 7200rpm Caviar Black slush drive which has worked perfectly until now. To eliminate the drive as the cause of the problem I tried it on different SATA ports (no luck) and moved the files to another working drive and tested them from the secondary drive on different SATA ports (no luck). The avi files will not import to either editor.

    – Previously edited and finally copy files like MKV’s and MP4’s, unedited recorded MP4’s work just fine they play and import properly.

    – The only hardware change made recently is that I actually removed my Hauppauge Collusus as I haven’t been using it for some time now. I fail to see how removing this could cause the avi files themselves to become so unusable, especially since 99% of the recordings were not even made with it.

    – No viruses have been found by 3 different scanners over the past 3 weeks. No malware/spyware or junkmail has been involved.

    My system specs are listed via the link in my profile/signature or below for good measure.
    https://www.xecutionrs.com/press/visi…-gaming-setup/

    GSpot has revealed no relevant errors in some of the avi’s that I can see so this is bothering me. VirtualDubMod as suggested by another forum thread won’t work for me as it can’t read the file saying it is corrupt.

    GSpot info
    Some files show this:

    File Length Correct
    Multipart OpenDML AVI (2 parts)
    (13039 frames in first part, 3567 frames follow)

    Other files show this

    Note: 8.30 GB unneeded bytes at end of file
    Multipart OpenDML AVI (3 parts)
    (13442 frames in first part, 84888 frames follow)

    Why all of a sudden can I not import my files to edit anymore? If you need more info please ask.

    Ryan Holmes replied 13 years, 5 months ago 4 Members · 8 Replies
  • 8 Replies
  • Ryan Holmes

    March 8, 2013 at 8:08 pm

    What’s the codec of the avi’s in question? avi is just a wrapper (like like mov) but the codec inside is what you need to unpack.

    Do you have the correct codecs installed on your machine? Did they get deleted? Become corrupt?

    Do the files work on a different computer with PPro (ask a buddy if you can try importing your files on their setup)?

    Ryan Holmes
    http://www.ryanholmes.me
    vimeo.com/ryanholmes

  • Tero Ahlfors

    March 8, 2013 at 8:11 pm

    Have you tried cleaning up your preferences and media cache?

  • Angelo Lorenzo

    March 8, 2013 at 8:16 pm

    Sounds like a corrupted drive. You may be better off in a Window’s tech forum somewhere posting the dump file or the full text of the BSOD error (which now has a smiley face mocking you in Windows 8… thanks Avast AV for crashing my computer randomly) for confirmation.

    If the files are still borderline playable then I would try rewrapping them with FFMPEG. You may be fighting wrapper corruption. Something like:

    ffmpeg.exe -i input.avi -vcodec copy -acodec copy output.avi

    I don’t know if FFMPEG even deals with OpenDML AVI files as these aren’t part of AVI’s official spec. I would use this to output the file to a different drive.

    [Keeley Charlton] “Note: 8.30 GB unneeded bytes at end of file
    Multipart OpenDML AVI (3 parts)
    (13442 frames in first part, 84888 frames follow)”

    Sounds like wrapper corruption. Your drive probably wrote an erroneous bit somewhere or isn’t reading back what is on the disk properly.

    ——————–
    Angelo Lorenzo

    Need to encode ProRes on your Windows PC?
    Introducing ProRes Helper, an awesome little app that makes it possible
    Fallen Empire Digital Production Services – Los Angeles
    RED transcoding, on-set DIT, and RED Epic rental services
    Fallen Empire – The Blog
    A blog dedicated to filmmaking, the RED workflow, and DIT tips and tricks
    Can your post production question fit in a tweet? Follow me on Twitter

  • Angelo Lorenzo

    March 8, 2013 at 8:24 pm

    The files may be corrupted permanently, but have you tried switching SATA cables to relieve the BSOD errors?

    ——————–
    Angelo Lorenzo

    Need to encode ProRes on your Windows PC?
    Introducing ProRes Helper, an awesome little app that makes it possible
    Fallen Empire Digital Production Services – Los Angeles
    RED transcoding, on-set DIT, and RED Epic rental services
    Fallen Empire – The Blog
    A blog dedicated to filmmaking, the RED workflow, and DIT tips and tricks
    Can your post production question fit in a tweet? Follow me on Twitter

  • Keeley Charlton

    March 8, 2013 at 9:05 pm

    Thank you for the quick replies. Your questions are in Bold my response follow each one.

    What’s the codec of the avi’s in question? avi is just a wrapper (like like mov) but the codec inside is what you need to unpack.

    GSpot indicates that all the files in question including the ones with or without erroneous data are using MJPG for video and PCM Audio.

    Do you have the correct codecs installed on your machine? Did they get deleted? Become corrupt?

    I do have the correct codecs installed, none have been removed or updated outside of Adobe or Vegas (I don’t believe they updated either). Corrupt is a possibility but not sure how to test this short of installing the codecs again. I would like to keep using the ones that came with each of the editors but how do I re-install said codecs without re-installing the whole program again?

    Do the files work on a different computer with PPro (ask a buddy if you can try importing your files on their setup)?

    They play on a different computer yes but do not import into PPro or Vegas

    Have you tried cleaning up your preferences and media cache?

    Yes. Doesn’t fix issue.

    Sounds like a corrupted drive. You may be better off in a Window’s tech forum somewhere posting the dump file or the full text of the BSOD error (which now has a smiley face mocking you in Windows 8… thanks Avast AV for crashing my computer randomly) for confirmation.

    If the files are still borderline playable then I would try rewrapping them with FFMPEG. You may be fighting wrapper corruption. Something like:

    ffmpeg.exe -i input.avi -vcodec copy -acodec copy output.avi

    I don’t know if FFMPEG even deals with OpenDML AVI files as these aren’t part of AVI’s official spec. I would use this to output the file to a different drive.

    [Keeley Charlton] “Note: 8.30 GB unneeded bytes at end of file
    Multipart OpenDML AVI (3 parts)
    (13442 frames in first part, 84888 frames follow)”

    Sounds like wrapper corruption. Your drive probably wrote an erroneous bit somewhere or isn’t reading back what is on the disk properly.

    I have posted in a windows forum as well as the my MB manufacturer forum. Upon researching my BSOD error code I came across a defect resulting in recalls for MB’s with a particular Intel Southbridge Chip version which I fall under. The issue regarding this particular SB chip from what I’ve seen is only resulting in slower data transfer rates. SATA ports rated at 6Gb/s were only producing 3Gb/s. Nothing was seen related to the ports not working just improper speed allocations. Either way I tried all SATA ports on my board including all 4 Intel SATA II, 2 Intel SATA III and 2 Marvell SATA III ports.

    The drive corruption dawned on me as well but hard to imagine it’s literally brand new and everything else seems to work. I haven’t tried to record anything new since this happened and import it to see if it’s only affecting currently existing files or newly generated ones as well. I will try this with new recordings and test them being recorded on separate drives for good measure.

    I have not tried FFMPEG yet but will try what you suggested and report back. FYI the files were recorded on the drive in question and were able to import before this happened. Files were not moved or changed.

    The files may be corrupted permanently, but have you tried switching SATA cables to relieve the BSOD errors?

    I guess I did not specify this in my first post but yes I did try different SATA cables.

  • Keeley Charlton

    March 8, 2013 at 10:52 pm

    Sorry I couldn’t figure out how to edit my post.

    I have tried recording using 3 different software programs onto 2 different HDDs and they all play fine but none of them will import into PPro or Vegas.

    For clarification:

    Files recorded prior to this issue were once able to be imported but not can only be played via media players not imported.

    Files recorded after errors occurred are playable in media players but cannot be imported into PPro or Vegas.

    I have come to the belief that it is related to the editors libraries some how and how they import files, or a codec related to the files themselves.

    If someone is able to show me how to re-install codecs for PPro or Vegas without re-installing the whole program again that would be great way to test my theory.

    Thank you.

  • Keeley Charlton

    March 9, 2013 at 10:49 pm

    Update!

    Upon finding another user with frustrations regarding Adobe Premiere crashing in all version he had ever own, I found some solid theories in his solutions.

    In almost all of his cases for Adobe Premiere to crash his problems were the result of the codec library. I am not saying this covers all crashes 100% but it at least covered mine as I came to this conclusion after multiple troubleshooting sessions.

    I followed his instructions which included going through your installed programs and uninstalling all other programs that use/install their own codecs or may have overwritten the ones used by Adobe.

    In my case I believe the culprit to DxTory. I am not sure what exactly is the cause because I know many people and friends who use DxTory in combination with Adobe Premiere and/or Sony Vegas without any of the issues I had.

    I removed DxTory as it was the only codec or program related to the issue that I had installed in the last month. Before moving on to removing Adobe Premiere so that I could re-install the codecs again I decided to test my set up before doing that.

    Conclusion:

    DxTory caused an error in dynamics linking or codecs/libraries for Adobe Premiere and Sony Vegas Pro. All avi files created before or after or on separate HDD’s were not able to be imported into either editor. Vegas produced an error say file is not able to be opened while PPro generated a BSOD due to a crash in SATA drivers for my MB. Removal of DxTory fixed whatever the cause was and I can now import previously problematic files without issues.

    Thank you to all who suggested ideas for me to try and I hope my responses back will help some else in the future who may have the unfortunate luck of running into the same issues.

  • Ryan Holmes

    March 9, 2013 at 11:52 pm

    Glad to hear you found the culprit and got it ironed out. Thanks for posting a follow-up…I’ll keep that in mind for the next Cow user who posts something similar.

    Ryan Holmes
    http://www.ryanholmes.me
    vimeo.com/ryanholmes

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy