CS3 to H.264

I have an HDV project and I'm looking to have my final product in H.264.
How would you get from CS3 to H.264?
My current method:
CS3 exports an AVI --> Import AVI into Quicktime Pro --> Export H.264 from Quicktime.
I'd like to hear your suggestions.
Also, what compressor would you use if you choose AVI?
(Please, no Cineform suggestions)
Thanks,
Scott

I had this problem and could find no way from Adobe media encoder to get a qt movie that would fast start - when on the webserver they always needed to have the whole thing downloaded before starting to play. I used squeeze eventually. Is there a way to convert a AME produced qt movie to fast start? I think i tried to re-export the mov from QTPro with fast start settings and it would still not fast start.
Scott - do you use AME then QTPro and it works?

Similar Messages

  • Rendering H.264 Quicktime from Premiere CS3

    For  a cliënt I have to make a H.264 file in Quicktime that is meant for a website www.leraar24.nl
    Since people before me used to deliver using FinalCutPro they made a short tutorial of the exact settings used in FCPro. Now I have to translate those settings to my setup: Premiere CS3 on Windows. I'd like to have your opinion on what settings I should use. Here's what they give up for FCPro:
    Video settings:
    Compression type: H.264
    Frame rate: current
    Key frames: automatic, vink frame recording (I think someone misread this  'cause the only the choice in FCP is  frame reordering)
    Data rate: automatic
    Quality: high
    Compressor: best quality
    Video size: 512x288. vink deinterlace source video
    Sound settings:
    AAC
    Stereo (L R)
    48.000 Hz
    best quality
    256kbps
    Streaming moede: Hinted streaming (prepare for internet streaming)
    I thought this should match the following in Premiere CS3:
    Format: H.264
    Range: Work Area
    Preset: Custom
    Basic Video Settings:
    TV Standard: PAL (it's the Netherlands)
    Frame Width: 512
    Frame Height: 288
    Frame rate: 25
    Field Order: None (Progressive)
    Pixel aspect ratio: Widescreen 16:9
    Profile: High\
    Level: 5.1
    (I have a jpg attached with the settings I used execpt I chose 25 frames instead of 50 frames)
    But  apparantly I was wrong 'cause the reported me that they don't want .mp4 but they want .mov instead. They only othter option for me is to export it to DV 25 .mov and then export it from Quikctime Pro which gives me the exact parameters as they gave for FinalCutPro. But then it doesn't look as good as when I export direct from Premiere.
    Does anyone have a better idea?

    Thanks a lot Rod,
    Here's what I used this weekend:
    The only problem is that for audio it won't let me choose AAC like it was 'told' to do in the FCPro settings guide. do you know why the option AAC isn't available? Because when I would choose H.264 as a format then there `is the option AAC so apparantly the audio codec AAC is on my machine. Or isn't it? And should I install it separately? What I did now was chosing the Apple Losless instead:
    Tomorrow I'll be hearing if they can get along with these settings.
    Thanks for your feedback.
    Gr. Karel

  • H.264 inconsistent quality- Fine within Premiere but bad outside of it.

    On my windows XP system I can import into Premiere CS3 original H.264 clips taken with a Canon digicam and they look great in the timeline. They also export without error as a H.264 movie. I can also import these H.264 movies that Premiere created back into another sequence and they too look fine.
    Where I'm having problems is when those same H.264 movies are played back in common players like Quicktime, WMP, VLC, or Power DVD, they don't look at all pretty. It doesn't matter whether they are the original out of camera clips transferred to the computer or the movies created in Premiere using the H264 preset. Quicktime always displays the originals as faded. It plays the output files from Premiere fine at first but as soon as I resize, they too get faded. The other players show them as very dark and dingy. I've done some forum reading about this and have tried the gamma stripper utility on both the original clips and the output movies with no change in the results. Any other ideas? Remember these look fine WITHIN Premiere. I just can't find a commonly used player that will do them justice outside of Premiere.
    Thanks.

    I solved the problem by downloading and installing the Premiere Pro and After Effects patches from the same place as the Media Encoder update.
    http://www.adobe.com/support/downloads/new.jsp
    It seem to be working okay now.

  • Exporting h.264 with CS4 vs CS3

    Maybe I'm just dumb and this is an easy question....I'm not sure, but here goes:
    I had a project in Premiere Pro CS3, a music video. I'm used to exporting videos as quicktime with an h.264 codec for online streaming from CS3, and they always looked great. A lot of websites cap video uploads to 500MB or a gig, so it was a perfect way to get a high quality video on the net. The 3 minute music video I was working on became a great looking 450MB h.264 movie.
    With CS4 and the adobe media encoder, things are a bit different. I export as a quicktime movie with the h.264 codec, at the same settings (100% quality) but it looks awful. The same music video was around 80MB and didn't look anywhere near the quality of same video exported from CS3. I've tried a number of options and presets, and havn't been able to get the same quality or size file.
    I even checked both files in G-Spot codec reader (great tool) and they were the exact same AVC1-h.264 codec.
    What is happening here? Is the codec somehow used differently in CS4 than in CS3? Is there something I'm not doing to get a high quality h.264 movie out of CS4?
    Thanks,
    Peter

    The bitrate of your output movie depends on your Export Settings. At the bottom of the Preset list is "Edit Export Settings". There you can adjust all the settings just like CS3.

  • Exporting H.264 Blu-ray material in CS3

    System:
    2009 Mac Pro 3.33GHz Quad core
    Snow Leopard 10.6.5
    16GB RAM
    Radeon HD 5870
    Adobe Premiere Pro CS3, 3.2.0
    Video material:
    DVCProHD, 1080p60i/24p, 23.976fps shot on P2, MXF file format.
    Exporting to:
    H.264 Blu-ray via Adobe Media Encoder
    I can render Blu-ray material, and even burn it in an internal LG 10x Blu-ray burner that I installed.  The result was wonderful when played back on a Blu-ray player and HDTV.
    What I cannot figure out is why I have to render projects in small little segments, rather than one large one, and then line them all up on a timeline in Encore.  I then have to rearrange my chapter points, since Encore places a chapter marker at each clip.  It's not the biggest deal in the world, but it's just annoying.
    I've tried different settings, and the one that gives me the most success is starting with the preset for H.264 (Blu-ray), HDTV 1080p 23.976 High Quality, and switching the Profile from High to Main, and leaving the rest alone.  I'm not sure if I tried HDTV 1080i 29.97... maybe I should.  Whether it crashes or not seems to depend on how many effects are in the clip, or how long the segment is, but I can usually get away with up to about 10000 frames of video without a crash.  The crash almost always occurs during the second pass of VBR encoding.  It closes Premiere and offers the crash report window, which I am not good at decyphering.  Anyway, I always submit the crash report with what I was trying to do.  Adobe has many of them from me now.
    Can anyone shed some light as to why it only allows 6000-10000 frames go through this encoding process?  My system will show that it only used about 6 out of 16 GB of RAM after a fresh reboot.  It helps if I reboot between each encode session, as well.  If I try to encode two short segments without rebooting between, I usually get a crash.  Also, I can encode DVDs just fine with the same project.  I encoded the 105 minute movie with all the same effects, clips, etc. and the DVD was flawless on the first try.  It's just the H.264 Blu-ray setting that jacks it up.
    I'm glad I can get the thing done piecemeal, but I was hoping someone could at least explain why it's so difficult. (:

    I would agree, and I think it must have to do with RAM.  When I get a segment exported successfully, the Activity Monitor shows very close to all 16 GB used in many cases.  I surmise that when the program sucks too close to all 16GB up, it crashes.

  • H.264 for iPad, problems in CS5 - OK in CS3 (Mac)

    Hi all,
    I have a CS3 project built on a PC, I've just brought into CS5 on a Mac. The encoding setup is for iPad, running full screen: H.264, 25fps, 1024x768, with a keyframe every 5 frames. I'm using the same setting as the CS3 project.
    All movies out of CS3 are reported by Quicktime to be 25fps. However movies out of CS5 are reported to be 25.33fps. In addition the results look blurry and generally poor compared to CS3 for the same file size. Anyone have any advice or experiencing similar issues?
    Mostly I need to ensure it comes out at 25fps as the engine/code base require 25fps with a key frame every 5 frames for movies to work correctly in App (as it has been doing with CS3 exports).

    Whoops--yes, QT 7 is what I meant but not what I said!
    (all the listings here are for the same movie)
    QT X reports - 25.35 FPS (playing FPS not listed)
    QT 7 reports - 25.07 FPS (playing FPS: 25)
    Premiere reports - 25 FPS
    Would you say this means I am actually getting 25fps?
    Without having much scientific evidence to go on, I would have to say "yes." Since software playback is not strictly timed the way, say, a professional video tape playback would be, there is bound to be some variability in how that file actually gets played back. It will vary based on the host computer, the file, and the player used. Ultimately, though, it's the way the file is encoded that matters, and I believe that the file actually is 25fps as you've specified.
    The most important question is: have you tried one of these CS5 exports in your destination application to see if everything works correctly? If they do, I don't think you have to worry about too much more; after all, based on your description, the most important factor is that you have keyframes encoded into the video stream for navigation/cueing. If this works, the playback framerate should be largely irrelevant, at least in how it is reported in a host of different playback applications.
    I am still wondering about the Data Rate, appearing (in QT) to be below the range listed in the Encoder settings.Using variable between 4 - 8Mbps yet the output is reported as:
    QT 7 - 3837.74 kbits/s
    Premiere is says Average Data Rate: 463 KB / second
    Changing to CBR with 5 Mb/s
    QT 7 reports - 25.07 FPS (playing FPS: 25) - 4128.64 kbits/s
    Premiere reports - 25 FPD - Average Data Rate: 498 KB / second
    There is bound to be some variation between the data rates of two files encoded even with the same encoding parameters, particularly when you're using VBR (variable bit rate) encoding. The amount of used bits will vary throughout the course of an encoded video stream, as some portions will require more bits to encode cleanly, while others can be compressed much more efficiently and therefore use fewer available bits. A busier video will require more of the available bits than one with less action. This would account for variations in data rate between two files using the same encoding settings.
    Now, if you are talking about the difference between what QT7 and Premiere report as far as data rate is concerned--that's simply a reporting issue. QT7 is using kbits/s, or "kilobits per second," whereas Premiere is being far less precise with kBps, or "kilobytes per second." One kilobyte per second (1 kBps) is roughly equal to eight kilobits per second (8 kbps), so if you multiply one the Premiere-reported data rates by 8, you get the QT7 rate.
    For example: 8 kilobits x 463 kBps = 3704 kbps; fairly similar to what QT7 reported.
    Why the difference? Well, one may be factoring in audio bitrate as well as video bitrate, or the Premiere reported data rate is less precise, or maybe just the fact that binary math is a little more involved than simple straightforward calculations In any event, they're both "right;" it just depends how accurate you need to be.
    Is Premiere the best place to check for data rates and FPS? Could do with one reliable source
    My recommendation would be MediaInfo; it's available for many platforms, including Mac, and gives a great deal of information about any particular file.

  • Crash AE CS3 when setting MPEG2/H.264

    AE crashes with "AE crashed 00::42" box, when trying access MPEG2/H.264 in RenderQueues OutputModule.
    We've uninstalled/cleanuped everything Adobe related and done fresh install of AE CS3 on following workstation:
    Intel Core i7 920, 6Gb RAM,
    WinXPPro x64, SP2, DX9,
    nVidia Quadro FX1800, 768Mb RAM, dr.v. 6.14.11.8267,
    Latest K-Lite and QT drivers.
    sherlock.exe shows "known false positives" - H.264/AVC, MPEG. (are they really so false?)
    dxDiag.exe passed perfectly, however Windows Error Reporting displays a number of identical entries:
    "AppErr afterfx.exe <ver>, faulting module winmediawriter.vwr <ver>, fault address 0x0002492d;&#x000d;&#x000a;"
    (as I remember this module also caused AE CS4 crash on startup before, so we removed CS4 completely)
    Reinstalled suite and QT already several times in different combos - no progress.
    Entering win diagnostic mode won't allow installing CS at all. Disabling AVG/Spybot during install made no change.
    tired and no idea what to do next.
    please, can anyone suggest any solution?
    thankyou in advance
    P.S. Crash also happens, when in PPro trying to access Adobe Media Encoder.

    Thanks, Mylenium. I am surprized about K-Lite, because it worked for me for years untill this workstation. Uninstalling this codec-pack was also what Harm Millaard and Jim Simon suggested in Premiere forum. I followed their advice, but unfortunately it did not change things - AE and PP were still crashing like before.
    Things seemed totally grim..
    ..and then I disabled faulty module mentioned before.. and, man, now IT WORKS!!!!!!! (not fully tested yet, but probably works also because of K-Lite gone). Thanks God my efforts and your advices were not in vain.
    Still, I don't know what that winmediawriter.vwr is intended for, but as far as I tried, uncompressed AVIs and MPEG2s (those I specially cared about) are encoding like a charm. Does anyone knows what consequences can I expect?
    I left my coleague installing back rest of CS3 to see tomorrow if it still works with such modules as Encore. And probably we will test KLite pack again.

  • Importing H.264 into Flash CS3

    I have an H.264 video that I saved out from FCP via Compressor using the H.264 Format for QT 7.0. The Video looks great when viewed in Quicktime. It was my understanding the H.264 is now supported by the Flash Player natively; however, when I try to IMPORT my H-264.mov into Flash CS3 it looks like it only offers me two choices of RE-Encoding to wither VP6 or Spark - this results in an inferior result after it re-compresses the video.
    Why can I not just reference the H.264 movie to play without re-encoding?

    This is what I did.  I saved my movie to the MP4 format in my video editing program and then I used this program to encode it with the H.264 codec.  http://www.h264encoder.com Then I used this program to move the metadata from the back of the file to the front so that it would start to play before it completely downloaded.  http://howbits.com/stream-mp4-website-h264-high which leads to this link http://rndware.info/download/metadatamover09
    I hope this helps you.

  • H.264 encoder (in cs3) produces really bad aliasing from AVI MJpeg source

    I have many 640x480 mjpg avi files from a Canon Powershot camera that I put in a 640x360 project.  I keep the vids at 100% scale and just leave them cropped top and bottom.
    What I find interesting is that when I encode my project out using h.264 (keeping the same 640x360, square pixels, ridiculously high bitrates, etc etc) I great really terrible aliasing.  If I use MPEG2 (with basically the same settings, though obviously much lower bitrate), it looks fantastic and quite similar to my original videos.
    Can anyone enlighten me as to why this is?  Is there some secret setting in h.264 that I'm missing?
    My project settings are:
    Timebase: 30.00 frames/second
    Frame size: 640x360
    Pixel Aspect Ratio: Square Pixels (1.0
    Fields: No Fields (Progressive Scan)
    The AVI files show these properties in Premiere:
    Type: AVI Movie
    File Size: 50.4 MB
    Image Size: 640 x 480
    Pixel Depth: 640
    Frame Rate: 30.00
    Source Audio Format: 11024 Hz - 8 bit - Mono
    Project Audio Format: 48000 Hz - 32 bit floating point - Mono
    Total Duration: 00:00:28:05
    Average Data Rate: 1.8 MB / second
    Pixel Aspect Ratio: 1.0

    John T Smith wrote:
    >Tell me something that helps me for free
    I like free as much as the next guy... but it seems, from some of the attitudes I've read in various forums, that some people feel "entitled" to free software
    A few Billion ticks of the computer clock ago, I wrote a specialty database application (dBase III compiled by Clipper... way back pre-history in Dos days) and cast it out upon the Shareware waters
    As a bonus for registering, I had a version with additional reports... and was amazed at the GALL of people who would write in wanting more reports... and who had never sent in a registration fee
    I finally gave up on Shareware... but I'm still amazed at people who want something for nothing
    I had to chuckle at the email I received this morning... see below
    Hunt has been around a long time, and we've given advice in the same message many times, so I'm sure he knew that I was simply adding a comment to what he said about being wary about giving software advice
    But... someone seems to be upset by me saying some people have an "attitude" about wanting free software
    "Hello,
    Though the content you posted was reported for abuse, it has been approved by our moderators:"

  • Adobe After Effects CS3 horrible export quality

    I made an intro for my Youtube channel using Adobe After Effects CS3, in the preview and whilst I was rendering the video quality was remarkable, no flaw in it. But after it rendered and I exported it as a .flv file the quality was horrible and grainy. Since I'm starting a serious channel my videos have to be high quality, including the intro. Is there any way to make it better quality, perhaps a free program that converts it into a better quality extension, or anything. I appreciate any feedback since I really need this intro in high quality.
    Here's the video link as you can see it's grainy as hell, even when put at 720p(HD):
    As I mentioned before in the preview and whilst rendering the quality was one of the best I've ever seen, no grain or anything, it was flawless, but when I exported, the quality turned to s***. Please help.

    Well, straight to the point: Read YouTube's requirements! FLV? They don't even recomemnd it themselves and in the last 3 years nobody serious has used it. There are enough free H.264 encoders based on ffmpeg. Download one and render an uncompressed movie from AE to be used for final output.
    Mylenium

  • Premiere Pro CS3: Many Problems Fixed By Upgrading to Windows 7 Pro 64-bit

    I recently installed an SSD drive and Windows 7 Pro 64-bit.
    Installing the Adobe Master Collection CS3 went smoothly and only took a few minutes instead of an hour, as in the past.
    Premiere, for the first time in the years I've used it, runs STABLE. Not only that, but I can have AfterEffects open at the same time. And Maya 2008. And everything chugs along smoothly.
    Case in point tonight: Multicam Editor: Under XP, it worked, but the quality of the video displays would be badly pixellated when video was playing. Under Windows 7, all the four viewports plus the 'online' viewport are sharp and clear and I can see if a camera is slightly out of focus, which was impossible to detect in the past until I watched the finished result.
    The audio dropouts everyone complained about for years are a thing of the past.
    And here's the biggie: I can render, render, render and keep rendering h.264 files and Premiere keeps ticking. Under XP, 2 to 3 files and that's it. Unknown Error would be the next render result. Under W7-64, I rendered all night and day without shutting or restarting Premiere, and I even had Maya and AE going and was working in them at the same time, something I could never do in XP because it would run out of RAM. And I can do this in 4GB ram! With 8GB, AE renders 3.5X faster, but most other programs remain about the same. I figure in the case of AE, it has EXCLUSIVE use of 4GB ram all to itself on an 8GB system. At any rate, die-hard CS3 users, don't be afraid to upgrade to Windows 7 64-bit.
    The only thing you need to do differently is put the Postscript fonts in Adobe's fonts folder, as it won't see the Windows\Fonts-located PS fonts.
    My 2008-vintage editing workstation breaths new life, like a major hardware upgrade was done. The "$139 system performance upgrade" I call it. (Sure, adding the Intel 320 SSD helps, but mainly with launching programs--once they're running, the main improvement comes from Windows 7 64-bit.)

    Actually, Win8 is really not a tablet OS... it is "essentially" Win7 with a different front end http://forums.adobe.com/thread/1101032
    Anything other than a new Win8 "app" runs on the same kind of desktop you see with Win7

  • Exporting h.264 and color managment

    I'm wondering what everyone that owns the production suite does with color management.
    If you open Adobe Bridge....what are you color management settings?    The reason I'm asking is that I've got two 2408WFP monitors and I'm using CS3.  Everything looks great in Premiere CS3, but when export to h.264 I get horrible contrast results.  It really looks over exposed.  I've checked my Adobe Media Encoder settings and I'm exporting at 100% with 20,000kbps and it still looks like garbage.
    When I play the same footage on a iMac....it looks under exposed to the point I can barely see it.
    If this is a monitor calibration issue, how do you recommend I calibrate?  What do you use and what are your settings?  Also, does anyone else here use a 2408WFP monitor?
    Much thanks!

    It has to do with default Gamma settings.  Mac are 1.8,(until Snow Leopard, which is now 2.2) PC is 2.2
    PC's look a little brighter, more washed out compared to MAC.  You should get a monitor calibration image from the net, and adjust your monitor.
    Here is a link that might help...
    http://www.gballard.net/photoshop/osx_22_gamma.html

  • H.264 Audio Out Of Sync in Media Encoder. Help Needed.

    I use Adobe Premiere Pro CS3 and I find that the best way to get a good video with low file size is by Exporting to Media Encoder and using
    the H.264 codec. Note, this is the codec by itself NOT the one used with the Quicktime preset.
    Here's the problem : When I export these files, they always end up a few frames slower than what I have on the timeline and the audio is always
    out of sync by just less than a second. Although it's a very small difference, timing is crucial in editing when it comes to dialogue as I'm sure anyone who uses Premiere understands.
    I have tried tweaking with the settings. I've used VBR 1 Pass, 2 Pass, CBR, Progressive Scan, Upper and Lower fields first, all of that.
    Has anyone else had this problem, and if so how was it solved?
    IF not, can anyone give me a good solution as to how I can get good video quality + low file size. The benchmark is a 45second video takes a maximum of 5MB, Quicktime video. Any suggestions or any methods you find better? Any ideas on how the guys at Apple Trailers manage to do the job so well?
    All the help is appreciated. Thanks, guys!

    Hi Jeff, I've experimented with a bunch of formats to find the root of the problem, but for this conversation I'll use a Quicktime (.mov) example.
    Source Footage Settings :
    Video : 640x268, Millions of colors. FPS : 23.98 Data Rate : 1.15mbits/sec
    Audio : AAC, Stereo (L R), 44.100 kHz
    Sequence Settings :
    Video : Quicktime Movie, Pixel Depth : 640, Frame Rate : 23.976
    Audio : Source Audio Format : 44100 Hz - 16bit Stereo. Project Audio Format : 44100 Hz - 32bit floating point - Stereo
    Average Data Rate : 141KB / second
    Pixel Aspect Ratio : 1.0 (Square Pixels)
    Export Settings :
    Main Concept H.264 Video, Custom Preset.
    Video : Frame width & height is same as source. Frame Rate : 23.976. Field Order : None (Progressive) Pixel Aspect Ratio : Square Pixels
               Profile : High. Level : 3.0. Encoding : VBR, 1 Pass. Target Bitrate [Mbps] : 1.3. Maximum Bitrate [Mbps] : 1.5
    Audio : AAC, Stereo, 44.1 kHz. Audio Quality : High. Bitrate [kbps] : 192. Precedence : Bitrate
    Multiplexer : MP4. Stream Compatibility : Standard
    NOTE : I have done the same with .avi files as well with the same audio lag issues. As for the file above, it's a trailer off Apple Trailers which also uses the H.264 encoding. To prove that there is a lag, I imported the 'rendered' file back into Premiere, placed it on a seperate layer on top of the original footage in the timeline and pressed play. As expected, there was a difference in audio playback and video was about a frame late.
    Any ideas? Thanks!

  • Media encoder crashing when exporting h.264

    I have a short 1:30 project I'd like to export using the h.264 codec.  The project is made up of [email protected] h.264 quicktimes shot on a Canon 1DmkIV.  If I export to h.264 using either the 720p or 1080p presets the Media Encoder will do two render passes then crash with an "Unknown Error".  This will happen if I export h.264 or as a quicktime using the h.264.  Strangely if I export as h.264 bluray it works fine but then the audio and video are seperate and not what I need if I intend to upload to Vimeo.  I can successfuly export to other codecs.
    I've clicked through premierepro.wikia.com but couldn't seem to find any answers.  Anyone have a suggestion?
    Thanks in advance,
    FYI
    Adobe Premiere Pro CS3 v.3.2.0 (374)
    Windows XP SP3
    Intel E6850 Duo Core @3Ghz
    4Gb RAM
    nVidia 8800GTX
    Soundblaster X-Fi

    Ok, that worked but Media Encoder wouldn't render out with TS checked using PCM audio, I had to change to Dolby Digital.  Once rendered and uploaded to Vimeo the image was displayed as 4:3 but with the anamorphic vertical squeeze even though I was using the 1080p24 preset.  <shrug>
    I'm wondering if it is the Mainconcept codec that's buggy.  Is there an alternative h.264 codec to use with Premiere CS3?

  • Crash PPro CS3 when launching AME

    PProCS3 crashes with "Sorry, serious problem" box, when trying to export sequence through Adobe Media Encoder. Same happended with CS4, so we decided to downgrade back to CS3.
    We've uninstalled/cleanuped everything Adobe related and done fresh install of PPro CS3 on following workstation:
    Intel Core i7 920, 6Gb RAM,
    WinXPPro x64, SP2, DX9,
    nVidia Quadro FX1800, 768Mb RAM, dr.v. 6.14.11.8267,
    Latest K-Lite and QT drivers.
    sherlock.exe shows "known false positives" - H.264/AVC, MPEG. (are they really so false?)
    dxDiag.exe passed perfectly, however Windows Error Reporting displays a number of identical entries:
    "AppErr adobe_media_encoder.exe <ver>, faulting module winmediaopwriter.vwr <ver>, fault address 0x0002934d;&#x000d;&#x000a;"
    another computer (Intel P4, 512Mb RAM), runs PProCS3 and exports all and everything (except Encore). I even  copied all those .ax and .dll files to i7's PPro with no change in its crashing.
    reinstalled suite and QT already several times in different combos - no progress.
    tired and no idea what to do next.
    please, can anyone suggest any solution?.
    P.S. Crash also happens, when in AfterEffects trying to set output format to MPEG/H.264

    Cannot describe my feelings, but yes I did uninstall KLite with no change - crashed like before.
    And then I recalled someone in forums sugesting to disable modules on crashy startup sequence (we have experienced this with CS4)..
    on last resort I decided to disable that winMediOPWriter.vwr and couldnt believe myself when AME window dialog appeared.. I expected to PPro crash on encoding, but NO - IT WORKS WORKS WORKS!! (at least DV-AVI, MPEG1 and MPEG2).
    Similar solution ALSO worked for After Effects, still I don't know what those modules are intended to do. Could anyone tell?
    Tomorrow I'll check other formats and compatibility with other CS3 modules, like Encore.. or even K-Lite pack.
    Thank you all for your will to help and I hope my experience will save someones hours, days, weeks and nerves..

Maybe you are looking for

  • Pick Full Storage Units

    Hi Guys I have two St types 003 and 005 003 is where we have the picking and 005 is the reserve st type I have stock in both and in 005 they are in boxes of 20 I am using two step picking in AFS I require 150 units for one material and 200 for anothe

  • Forwarding one iCloud email to another & replying from the correct address

    I have 2 iCloud accounts and to make things easier for me, I want to forward one to the other, which I am aware how to do. However, when I hit "reply" to an email, the address showing is the address I am "forwarding to", NOT the address the email was

  • Problem in installing patch set 8.1.7.4

    Hi All, when i am installing patch set 8.1.7.4 i am getting stuck here like it is not able to file link the binaries can i know what is the reason when i tailed install log i am getting below error. /usr/ccs/bin/make -f ins_net_client.mk client_share

  • CAFLockException

    Gurus salutem, In my BPM flow I use a CAF service, and use the operation to update a record. Prior to the update I read the record, and use the results to be passed on to the update service, except for the attribute status. Attribute status is change

  • DSL contract changes not possible since FIOS is available?

    I've been a Verizon DSL customer for 4-5 years. Only the 1.5Mbps is available to us. FIOS became available shortly after I signed for DSL. For the past year (or 2?), I've been considering moving out of state, as a result, I've been on the monthly pla