Exporting AVI clips (error: "[\Src\Win\WinFile.cpp-759]" after 4 %)

The following problem:
I have 2 adobe premiere project. both have the same film and film length but different video codecs.
1. project (low quality video codecs (mpeg4)
export works fine
2. project (high quality video codecs (avi)
export stops every time after 4% with the following error notice:
"Premiere Pro has encountered an error.
[..\..\Src\Win\WinFile.cpp-759]"
or if I want export the project with other codecs, eg H.264 then Adobe premiere freezes and I can close Adobe Premiere then.
Premiere memory settings (valid for both premiere projects):
Installed RAM: 3,7 GB
RAM reserved for other applications: 1,5 GB
Ram available for Adobe: 2,2 GB
Optimize rendering for: "Memory"
computer details:
system type: 64 Bit
installed RAM: 3,75 GB
processor: AMD Athlon, 2 x4 635 processor 2.90 GHz
graphics card: ATI Radeon HD4200
windows edition: 7
How can I solve the problem, so that I can export my whole project in AVI codecs without freezing problems or error problems?
Is it a hardware or software problem?
Thanks in advance for your help

Work through all of the steps (ideas) listed at http://ppro.wikia.com/wiki/Troubleshooting
If your problem isn't fixed after you follow all of the steps, report back with ALL OF THE DETAILS asked for in the FINALLY section, the questions at the end of the troubleshooting link
Most especially the SOURCE FILE codec used... see Question 1

Similar Messages

  • AVI clips export (Fehlermeldung: "[..\..\Src\Win\WinFile.cpp-759]") Premiere friert ein beim export

    The following problem:
    I have 2 adobe premiere project. both have the same film and film length but different video codecs.
    1. project (low quality video codecs (mpeg4)
    export works fine
    2. project (high quality video codecs (avi)
    export stops every time after 4% with the following error notice:
    "Premiere Pro has encountered an error.
    [..\..\Src\Win\WinFile.cpp-759]"
    or if I want export the project with other codecs, eg H.264 then Adobe premiere freezes and I can close Adobe Premiere then.
    Premiere memory settings (valid for both premiere projects):
    Installed RAM: 3,7 GB
    RAM reserved for other applications: 1,5 GB
    Ram available for Adobe: 2,2 GB
    Optimize rendering for: "Memory"
    computer details:
    system type: 64 Bit
    installed RAM: 3,75 GB
    processor: AMD Athlon, 2 x4 635 processor 2.90 GHz
    graphics card: ATI Radeon HD4200
    windows edition: 7
    How can I solve the problem, so that I can export my whole project in AVI codecs without freezing problems or error problems?
    Is it a hardware or software problem?
    Thanks in advance for your help
    Ich bin Deutscher. Ich brauche schnelle Hilfe. deshalb habe ich aus dem englischen forum mein eintrag kopiert und hier eingefügt.
    Vielen Dank im Voraus

    Work through all of the steps (ideas) listed at http://ppro.wikia.com/wiki/Troubleshooting
    If your problem isn't fixed after you follow all of the steps, report back with ALL OF THE DETAILS asked for in the FINALLY section, the questions at the end of the troubleshooting link
    Most especially the SOURCE FILE codec used... see Question 1

  • Error message [..\..\Src\Win\WinFile.cpp-758]

    i tried to encode AVI video file with media encoder CS5 to MPEG2
    and after it seemed the encoding was done i got this message?
    [..\..\Src\Win\WinFile.cpp-758]
    can enyone help me with this?

    I had the same problem with recently updated Encore (5.01.) Tried shortening & simplifying file names with no luck either. I tried half a dozen things that sometimes work (e.g., refreshing source material, restarting Prmier Pro project from scratch) because of an error I overlooked. Nothing worked. Then, much by accident, I looked at the Media Cache. I had recently shifted the Media Cache to a new 3 TB hard drive that wasn't being used very heavily, figuring I had a lifetime supply of space. Wrong. It was completely filled up, mostly with the Media Cache. I cleared the Media Cache [Edit > Preferences > Media...] and BINGO! The project rendered cleanly.
    Hope this helps.
    Adobe needs to address this issue. The best solution would be to automatically clear out the cache materials associated with a perticular project whenever the project drops off the radar. A minimal solution that should be quick and easy to implement would be to monitor the empty space on the scratch disk and flash a pop-up warning when it was getting too full.
    Addendum, 10 May 2012:
    This one has left me thoroughly confused. Just ran a similar set of files through Encore, cleared the cache first, then good ole 758 again. It took several attempts, but finally it went through. Then I discovered I had forgotten to set something minor in the navigation and had to re-do it. Three tries later, it worked. Phase of the moon, I suppose.
    This is not the first time this has happened - it happens occasionally with other similar files. I have had my best success running Encore when I let it run alone.  It doesn't seem to time share very well with other programs, which is inconvenient because I like to work with Premiere and Photoshop getting the next project ready to go while Encore is processing the current one. Encore needs a batch queue like the one Premiere uses so I could prep the projects in Premiere/Photoshop during the day and then let the Encore queue run overnight. The queue would have to be configured so that if one project failed it would set it aside and move on to the next one.
    Another problem Encore has is hanging temporarily. It doesn't die but just quits responding for a short time. It took me a while to discover that Encore was running but just not responsive to the operating system. I'm a little surprised because I have a fairly fast AMD 6 core chip and lots of RAM (or so I thought) at 16 GB. The gadgets and Resource Monitor tell me that the six cores are frequently using over 90% of the available combines cpu cycles and occasionally most of the available RAM.
    I put in a 256 GB  solid state drive, divided between the o/s and installed programs, leaveing about 120 GB for the files I was processing. The idea was that everything would be moving strictly in solid state. Maybe that speeded the system up too much. Putting in a 120 GB SSD sure made an 8-year old XP box scream though.
    I am looking forward to getting CS6 in the next few weeks - I hope they have these bugs sorted out by then. From what I have seen in the forums, similar WinFile.cpp problems have been in existence since CS4 at least.
    Message was edited by: Retired Spook

  • Premiere Pro (CS6) - Windows 8 - [..\...Src\Win\Winfile.cpp-814] error

    Hello         
    Im currently having some issues with Premiero Pro (via creative suite 6) on a Windows 8 64 bit machine after reinstalling due to an error resulting in the encoding sequence crashing/hanging and remaining on 0% indefinitly
    Video and audio were both taken via the same machine and are both in .MP4 format. The project will render correctly however will not export
    Upon selection of export with match sequence settings enabled I receive the error box saying:
    Premiere Pro Debug Event
    Premiere Pro has encountered an error.
    [..\...Src\Win\Winfile.cpp-814]
    Upon closing the error the screen returns back to the work space. with an error box saying:Error compiling movie - unknown error. After this it again shows the infinite encoding screen.
    I have tried uninstalling the programme and running any updates etc however I am unable to get it to work.
    Would really appreciate an answer to this.Uninstalling and reinstalling is in itself a pain.
    Many thanks

    I can't give direct help with that error, but some reading that MAY help... These notes are (mostly) for Encore, but some ideas that may help
    As well as the below, right click the program icon and select Run as Administrator, which is NOT the same thing as running the computer with the Administrator account, and which fixes several "odd" problems...
    Run as Administrator http://forums.adobe.com/thread/969395 (Encore AND PPro)
    Odd Errors http://forums.adobe.com/thread/670174
    Long File Names or odd characters cause problems
    Read http://forums.adobe.com/thread/588273
    And #4 http://forums.adobe.com/thread/666558
    And This Message Thread http://forums.adobe.com/thread/665641

  • Premiere Pro (CS6) - Windows 7- [..\...Src\Win\Winfile.cpp-814] error

    Hi,
    I'm currently working on an animated music video to upload on YouTube fairly soon and while trying to export my video I get an error popup saying [..\...Src\Win\Winfile.cpp-814].
    I've had no problem exporting before and now this thing comes out of nowhere to ruin my day and my project haha.
    I've resterted the project and the popup still appears. I even went to the extent of going back to Premiere Pro CS 5.5 but I receive  a popup saying  [..\...Src\Win\Winfile.cpp-785]
    ...with another saying "Thank you for using "Adobe Device Control". The Adobe product that installed "Adobe Device Central" has not been activated. Please launch and activate that Adobe product before continuing to use "Adobe Device Central" after it exports.
    And,  when the project  does export, it exports with just the video with NO audio .
    I have never had this issue before, it just randomly happened. I've use Premiere Pro going on 5 years now and have never had an issue until now. Someone or some hero please help me slay this dragon so I may post my awesome music video on YouTube. Thanks

    I found a bug report on this exact crash. The developer's notes indicate that the crash occurs when Premiere gets an unexpected result when checking to see if a file is open. One thing that might work is to reboot the system, thereby closing any files that were basically in a bad state.
    If that doesn't do the trick, then installing PPro CC as a trial should allow you to get around this.

  • Src/Win/WinFile.cpp-754" error

    I’m using PPRO in Production Premium CS4.
    I’m getting the “Src/Win/WinFile.cpp-754” error” when I AME starts or shortly after it starts. System worked fine since I installed the CS4 upgrade 4 months ago but today a project is due and this happens.
    My system: Dell Precision 690, 3Ghz Xeon processor, 4 GB ram, Internal HDs (1) 300 and (1) 400 GB, External HDs (2) 1 TB.
    I’ve read and searched the forums and now I’m frustrated and in need of some help. Has anyone found definitive solution to this “Src/Win/WinFile.cpp-754” problem?
    Thanks,
    Tony

    Hi,
    I searched the internet with that error mssg and it seems a lot of them have to do with video card drivers. There was some information about matrox drivers and that problem on the internet...
    Also some 'Axio' card driver problems related to that error message...
    Have you recently updated your video card drivers ?
    Rod

  • Adobe Media Encoder error when encoding: winfile.cpp-759

    Mods: Please move this to the appropriate thread wasn't sure to move it to Premiere or Flash
    I receive this error when trying to encode AVI to H.264 using Adobe Media Encoder CS5 (64bit):
    When searching through the forums, several suggestions for CS4 and current releases that I have tried are:
    clearing the media cache through AME, and the folder location in %APPDATA%\Adobe\Common\
    installing K-Lite Codec pack
    changing the media cache files folder to a separate disk entirely
    updating to the latest version (at the time of post ver 5.0.1.0)
    uninstalling and re-installing AME (as an error might have occurred during updates)
    verifying that the CPU has SSE support and is enabled
    I expanded my search to google which gave similar errors (winfile.cpp-754, winfile.cpp-758, etc.) and a few responses were uninstalling any Nero products (don't have any burning programs on this computer - unless you count Windows)
    The system that I have is:
    MS Windows 7 64-bit
    Intel Core 2 Quad Q6600 @ 2.40GHz
    2x 1.0GB Dual-Channel DDR2 @ 800MHz
    512MB GeForce 9600 GHz
    2x 250GB HDD Mirrored
    External USB 500GB HDD
    Any ideas as to what the cause of this is?
    LK.

    The information about installing codecs packs is true. It usually does more damage to your codecs already present with software already installed on your computer, and the registry settings even after removing it. That is why it is in good practice to do full image back ups monthy, saving the latest 3 for when I utilize last resort methods such as codec packs.
    Adobe CS5 software has been working fine on my computer ever since its installation July. I forgot to mention that I have successfully used Premiere Pro CS5 for editing a dozen files ranging from SD small res to HD 1080i. This also includes just using AME CS5 itself for transcoding files for supported playback on different devices. I notice a greater difference in speed when using a more up to date machine that uses a GTX 285 card for GPU playback - a lot faster and smoother.
    I have a 2nd, slightly older computer, that houses an extra drive I put in there to use as a scratch disk. I occasionally add that disk to the computer that has CS5 currently installed as a scratch disk for editing video. The external USB drive is used to store the final product and my backups.
    This error has only come up 1 time out of the 49 files I have encoded that usually run 10 minutes to 1.5 hours. I had 9 AVI files in the encoding queue and it always stopped at this 1 particular file. I skipped the file and encoded the rest successfully, but I want to know why it causes an error in AME because this has never happened before. I have even used it on a more up-to-date machine spec wise, thinking that there is a 1% possibility that it doesn't like my computer. The same error was produced. The 9 files that I did encode are roughly the same video and audio format - just this one is the error.
    I gave the file to my friend who was supposed to analyze before I got home - I usually assist them in PC problems and built his better-than-mine PC.
    Any other suggestions for this error and/or a solution?
    Lk

  • Error on starting [..\..\src\win\winfile.cpp-507]

    I have tried everything that adobe technical have said has anyone else had this error and fixed it

    Welcome to the forum.
    This ARTICLE will give you tips on the types of information that will help others help you most efficiently and effectively.
    Good luck, and we'll be looking for the info to help you solve the issue.
    Hunt

  • Adobe Media Encoder (CS5) has encountered an error (WinFile.cpp-759)

    I have a 714 MB Xvid file that I want to split into smaller pieces. I have gone successfully through a similar process earlier with a larger Xvid file using the same version of Adobe Media Encoder (CS5). It appears that no matter which output video format I choose, the process crashes with the following error message shown in a new pop-up dialog:
    "Adobe Media Encoder has encountered an error. [..\..\Src\Win\WinFile.cpp-759].
    (Even the source program file line number 759 in the above error message is always the same, regardless of my chosen output file format.)
    The only option available from this point onwards is the "Continue" button. When I click Continue the program terminates with the Windows program crash message "Adobe Media Encoder CS5 has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available. <Debug> / <Close program>"
    My search for other similar problem reports revealed that some user(s) has/have experienced a very similar problem in CS4, but the source line number was slightly different in CS4. Both problems are probably caused by the same error in Adobe's software. The small difference in source line numbers is probably due to some (minor) and probably unrelated changes to this C++ source module (WinFile.cpp).
    It might of course be the case that this particular input video file has some rare encoding or other embedded problem. However, the fact that I can view the video without problems using Windows Media Player does not support this theory.
    Apart from this message board I could not find any other avenue to report this bug to Adobe (without paying for support - which I am obviously not going to do as this is clearly a programming bug in the software). Hopefully some Adobe developer responsible for Media Encoder maintenance will read this forum from time to time and would subsequently inspect the source module for any obvious defects. I could supply the source video file with which this problem can be reproduced at will.
    Regards
    Jouni Juntunen

    CS4 Adobe Media Encoder & FMLE are two different softwares - you can post your query here:http://forums.adobe.com/community/ame

  • Bug report: Adobe Media Encoder (CS5) has encountered an error (WinFile.cpp-759)

    I have a 714 MB Xvid file that I want to split into smaller pieces. I have gone successfully through a similar process earlier with a larger Xvid file using the same version of Adobe Media Encoder (CS5). It appears that no matter which output video format I choose, the process crashes with the following error message shown in a new pop-up dialog:
    "Adobe Media Encoder has encountered an error. [..\..\Src\Win\WinFile.cpp-759].
    (Even the source program file line number 759 in the above error message is always the same, regardless of my chosen output file format.)
    The only option available from this point onwards is the "Continue" button. When I click Continue the program terminates with the Windows program crash message "Adobe Media Encoder CS5 has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available. <Debug> / <Close program>"
    My search for other similar problem reports revealed that some user(s) has/have experienced a very similar problem in CS4, but the source line number was slightly different in CS4. Both problems are probably caused by the same error in Adobe's software. The small difference in source line numbers is probably due to some (minor) and probably unrelated changes to this C++ source module (WinFile.cpp).
    It might of course be the case that this particular input video file has some rare encoding or other embedded problem. However, the fact that I can view the video without problems using Windows Media Player does not support this theory.
    Apart from this message board I could not find any other avenue to report this bug to Adobe (without paying for support - which I am obviously not going to do as this is clearly a programming bug in the software). Hopefully some Adobe developer responsible for Media Encoder maintenance will read this forum from time to time and would subsequently inspect the source module for any obvious defects. I could supply the source video file with which this problem can be reproduced at will.
    Regards
    Jouni Juntunen

    OK, I've reported the bug in the linked location. However, I had to use "Creative Suite" as the application, because "Adobe Media Encoder" was not an available option.
    Jouni Juntunen

  • [..\..\Src\Win\WinPathUtils.cpp-427] error?????

    I am running Adobe Production bundle CS3 and in Encore when I try to import an asset this message window appres "Adobe Encore has encountered an error [..\..\Src\Win\WinPathUtils.cpp-427]" and then I click the "continue button" and this pops up "An input contract violation has occured!'
    I am running windos XP Sp2, fast machine with lots of ram and memory! any ideas? Previous Production Bundle ran perfect, but I unistalled it and installed the new CS3 and now I get this problem.
    Any ideas anyone?
    and a HUGE thanks in advance

    While using Adobe Premier Elements 7 to edit AVC HD I encounted the error message  (..\..\Src\Win\WinPathUtils.cpp.533) when trying to reopen an almost completed video project.
    After days of trying to solve why opening the project I encounter error message (..\..\Src\Win\WinPathUtils.cpp.533)  I decided to re-edit the video starting with a different project name. When I came to place AVCHD clip 00055 on the time line I encounter error message (..\..\Src\Win\WinPathUtils.cpp.533) I deleted clip 00055 from the hard drive (these clips were a copy from my camera I still have the originals)
    I was able to reopen the original project as this AVCHD clip 00055 was the cause of error message (..\..\Src\Win\WinPathUtils.cpp.533) I renamed AVCHD clip 00055 to 05555 reinserted it in original project this saved me many hours of re-editing
    Therefore I think in my case error message (..\..\Src\Win\WinPathUtils.cpp.533) was to do with a corupt AVCHD camera file within the project which was removed and the original project was abled to be opened.
    Chris

  • [..\..\Src\Win\WinFile.ccp-754]   Error In Media Encoder CS4!

    ======================================
    Adobe Media Encoder has encountered an error. 
    [..\..\Src\Win\WinFile.ccp-754]
    ======================================
    I have paid a small fortune to get the Masters Collection CS4, and after a few months of using it, I get this error for no reason!
    It happens everytime I try to encode files in Adobe MEdia Encoder CS4 (Fully Updated) like music, home videos ect to different formats so I can share them with family.
    My system: HP Pavilion DV9700 500GB HDD, 512Mb NVideo Geforce, 4Gb DDR2 RAM, Vista Ultimate x64.
    Any help would be greatly appreciated!
    Thanks
    Justin 

    I get this error for no reason!
    You are wrong. There is a reason. What the reason is, is hard to discern due to lack of information. Look at this link closely, read the included link to the WIKI and reply to the 16 questions asked at the end of the article if you have not yet found the solution with all the steps outlined: Some suggestions

  • PRE7 Organiser error [...winfile.cpp-507]

    Here’s an oddity, whenever I started PRE7 it kept throwingup a dialog box that PRE had encountered a problem [..\..\SFX\Win\winfile.cpp-507].
    This seemed to loop indefinitely until I realised that there were some disconnected items showing. So, with some nifty mouse right-clicking and hitting enter I was able to bring up the context sensitive menu on the disconnected items and delete them. Once they had been deleted everything was fine.
    So all is well, but it is disconcerting that something as trivial as a file disconnect could cripple PRE7.
    Has anyone encountered this before and had a better fix? (googling threw up two occurrences but neither with a confirmed fix)
    Cheers,
    Neale
    Insanity is hereditary, you get it from your children

    It is a shame that a missing link will throw up an error like that, Neale.
    Meantime, you go to the Organizer's File menu and select Reconnect/All Missing Files. This feature will search for all missing links in your catalog and offer you the option of removing them from the catalog -- so it won't happen again.

  • Winfile.cpp-759 error when exporting .flv files

    Hi,
    Just got over the P2 file problem (stopped using them in CS5, gone back to CS4) and a new problem has occured.
    I have been exporting .flv files since I first installed CS5, suddenly today Premiere crashes when trying to export individual .flv files and so does the media encoder.
    Any ideas?
    Thanks

    The given problem doesn't have the obvious cause. But it can be avoided.
    The problem emerges after Premiere import video clips with attached audio files, while 'confoming audio'. After the conforming, the 'broken' audio files cannot be heard with playback, or incorporated in export.
    There are two solutions to this problem.
    First: While ripping material, or importnig previously ripped material, import separately audio and video data.
    Second: If you, while working, run into audio stream that doesn't hear ( because of the given 'conforming' ), edit audio of original clip in some sound editing program ( Adobe SoundBooth, for instance ) by cuting it to new file, resampling it, saving to *.wav ( for example ) and importing it to your Premiere project, replacing the broken audio data.
    That should do the trick. At least, it did it for me.
    Cheers!

  • Adobe Media Encoder CS4 Error: WinFile.cpp-754

    When encoding video from one format to another (no matter what is source and what is result file format) I have an error after some time or in the begining of the process. "Adobe Media Encoder has encountered an error ..\..\Src\Win\WinFile.cpp-754"
    Version of Encoder is 4.2.0.006 (updated).
    I can't encode any files. What is the problem?

    Any update on this?
    I get WinFile.cpp-754 on CS4 and WinFile.cpp-785 on CS5 trying to encode the same AVI file.
    I'm trying to load a 59.94 fps AVI file into PremierPro CS4 and need to convert it to something else (correct?)

Maybe you are looking for

  • Control Panel text tool options switched places

    Hello there! Prologue: I've been searching for a solution for this problem and couldn't find any. Perhaps I don't know how to search properly. The problem itself isn't catastrophic yet it is really annoying to me, as I like to work quickly and everyt

  • How to retain File Names in B2B

    Hi, My requirement is to FTP a file from Source system to an Target System through B2B. Eg. Say Customer_PO.xml has to be FTP to DELL using B2B from SONY. Customer_PO.xml (SONY ) ->B2B ->Customer_PO.xml ( DELL ) So here when we transfer the file thro

  • Auto Mount fails on CIFS share

    I have setup auto_master with the following line: /-    auto_direct I also have tested a client smb share connection with the following successfully since this node is a member of the cih-ettm windows domain; I have also setup smbadm add-key with thi

  • Can someone explain to me why Apple says you can only have 4GB max in the Unibody MacBook (white)?

    I'm looking to upgrade the RAM on my Intel 2.4 Core 2 Duo unibody MacBook, which currently has 4GB pre-installed Apple RAM. In searching for an answer to whether this machine is expandable to more than 4gbs of RAM this is one answer I came across tha

  • Photos are corrupted on iphone.

    i recently replaced my iphone.  restore seems to have gone smoothly except that my photo folders are corrupted.  the camera roll and photo stream folders seem ok; all others behave as follows:  i open the folder, select a thumbnail, and the photo tha