Bug list and wish list premiere pro cs4

Iam realy interesting someone, sometime work with Premiere pro cs4 from Adobe team ? I gues not!! Some bug might not seen only people who not work on premiere !!! 2 russian video editing forum named premiere cs4 most worst of version premiere. Old bugs not fixed on premiere cs3 adobe make premiere cs4 with new most worst bugs and some options was remove(Fast export to frame\movie) What for ????!!!!! Cuting the clip i must press 2 button - what for ? Cut it most usful operation and adobe make 2 button press to cut. And domenation effects then adding to clip, please try add some effect to clip then add someone again. Why new effects adds not to last posotion ?
And time warp, posterize time work only with neast sequence!!! What for !!!Its make work with premiere faster ????
ADOBE PLEASE WORK YOUR SELF ON PREMIERE PRO CS4 SOMETIME !!!

FAQ:How/Where do I report a bug?
Cheers
Eddie
PremiereProPedia   (
RSS feed)
- Over 300 frequently answered questions
- Over 250 free tutorials
- Maintained by editors like
you
Forum FAQ

Similar Messages

  • Where can I download and install Adobe Premiere Pro CS4

    Hi
    I would like to know where can I download and install Adobe Premiere Pro CS4. Would you send me the link install imm please??
    Thanks

    Check this link , it may help
    http://prodesigntools.com/download-adobe-cs4-and-cs3-free-trials-here.html
    Please do read the instruction properly , do avoid the error "Access Denied"

  • Sync when compressing HD FLV and F4V in Premiere Pro CS4

    Hi.  I'm trying to create PSAs for You Tube that were originally created with a small camera that produced HD Quicktime files.  For YouTube they don't have to be perfect but that is what I'm working with.  My computer only has 4gb of ram so I can't watch the video to test for syncronization since it just gives a slide show while editing.  It never does anything but a slide show with HD video.
    When I watch the original unedited Quicktime file the sync was way off.  When I render out the original file in an FLV and F4V format just to test the sync it is PERFECT.  Then I edited the first video taken from that session and used FLV and the sync was PERFECT.  So I'm doing the second video, tested sync on the original footage, and its PERFECT.
    So I thought it was okay to keep going.  Everything was perfect after Premiere rendered the raw footage. The first video worked, right? The second video's raw footage sync was fixed, right?
    Now that I spent all the time to edit the 2nd video, sync is TERRIBLE.  I have no idea why.  F4V was worse than FLV, but neither was great for video 2.  So I guess I have two questions:
    1) What format can I use to upload to YouTube that won't give me an unusable sync problem
    2) Is there something I can do to see continuous synchronization within Premiere Pro CS4 without updating my hardware?  I am using Vista 64 bit, 4gb ram, dual core intel.  Do I have to make a major hardware upgrade just to get HD video not to be a slide show while running Premiere?
    Thanks!

    Dave,
    Deleted all stuff...
    You might try this "TEST" at some point if you're using equipment to record sound as outlined in the following article....at any rate you might find the article interesting anyway for the future...
    ----------------------sorry I should give credit to who wrote it but you can google the first line and find it maybe -----------
    sync demuxed sound   The Problem -
    Miniature audio recorders, be they minidisc or solid state, offer a very attractive, cost effective, alternative to the traditional use of radio microphones, for the capture of remote audio sources in video recordings
    These machines record the audio in a variety of different formats - MP3, WMA, WAV, ATRAC -- and in a variety of qualities - but they all suffer from the same problem. It can be difficult to synchronise the remotely recorded audio, with the camera recorded audio.
    Although the time honoured tradition of an audio 'clapper board' works well enough to align the beginning of the two soundtracks, there is a tendency for the two tracks to appear to 'drift' out of sync over time - and the longer the recording, the worse the problem. In fact they do not actually 'drift', but the gradual loss of sync is a function of the camera and audio recorder sample clocks being slightly different frequencies.
    The simple reason for this loss of 'sync' therefore is that the audio is being recorded at different speeds. Although the recorder will specify the sampling frequency, the accuracy is then dependent on the internal crystal oscillator of the recorder - which is, of course, a different oscillator from the one controlling the camera timing. Although these crystals may typically be accurate to within 0.005% or better, even this degree of accuracy can cause the two recorded audio tracks to be out of sync by up to 300mS after 30 minutes. Even after 5 minutes, the 2 tracks can be some 60mS different in length, in a worst case scenario.
    60mS difference will cause a distinctly audible 'echo' between the two audio tracks. (Even 20mS is detectable as a separate echo).
    This difference is of course totally unacceptable, and corrections need to be applied. It is important to remember that even if your audio recorder crystal is absolutely accurate, and it is the camera clock that is slightly wrong, it is still the remote audio track that will have to be corrected. The 'wrong' camera audio track is the one in sync with the video, and has to be the 'master' track.
    The Solution
    It is important to realise that although the sample oscillators may vary with regard to each other, they tend to be remarkably accurate over time, referenced to themselves.
    This means that if you know by how much the frequency your audio recorder sample 'clock' differs from the camera 'clock', then a single correction factor will bring both tracks back into sync.
    A simple procedure is outlined below, using free programs, to enable you to calculate the correction factor required for your particular recorder.
    Programs required (all free):
    1) AoA audio Extractor --- (not necessary if you can extract the audio track from a video recording in your NLE)
    2) Audacity , a free audio editor
    3) Switch , a free audio file type converter
    Step 1: Set up your camera and audio recorder next to each other, and start both running
    Step 2: Make a good audio 'clapperboard' point by tapping a pencil firmly onto a hard surface, as close to both camera and recorder mics as possible. This will cause a fast 'edge' to become the reference point, which will be useful later.
    Step3: Let both devices run for at least 10 minutes. 20 minutes are better, but not essential.
    At the end of the period, (timing not critical), make a second similar 'clapperboard' reference point. Allow a few more seconds recording, and then stop both devices.
    Step 4: Download the video from the camera, and the audio from the recorder to your computer.
    Step 5: Open the video file in 'AoA audio Extractor', and extract the audio from the video. Convert this audio file (if necessary) to a 48KHz 16 bit LPCM (wav) file, using the 'Switch' program linked to above. This file will be your reference audio file.
    Step 6: Open the WAV file saved in the previous step in 'Audacity' - a free audio editor.
    It is now necessary to save only the part of the file between the two 'clapperboard' references, which hopefully stand out clearly (if you hit the pencil hard enough in steps 2 and 3!).
    This must be done accurately, to within 100th of a second, or better.
    Click and drag the file to highlight the beginning section, including the first 'clapperboard' waveform. Use the 'fit selection to window' tool (immediately to the right of the 'zoom' tools) to magnify. Delete as much as possible before the 'clapper' reference. Repeat the operation until you can clearly identify the first distinct waveform of the 'clapper' reference waveform. Click, hold and place the cursor directly over the first full (clipped) waveform, where it crosses the centre line. Delete every thing to the left of that point, by clicking and dragging to highlight, and then deleting with the scissors tool.
    Step 7: Repeat the above procedure for the end part of the waveform, again using the start of the second 'clapper' waveform as your reference cutting point. In this case, cut everything to the right of your selected reference point (not the left, as in the first case.)
    Step 8: It is necessary to record the exact length of this new cropped waveform. This information is listed at the bottom of the window, but in a rather inappropriate format. Locate the toolbar at the top of the window, click 'Edit'-'select all' and then 'Effects'-'change tempo' . Note the length of the file in seconds in the right hand box (the left hand box is greyed out).
    Record this figure. It is the reference file length
    Step 9: It is necessary to convert the file recorded on the audio recorder into an identical format to the camera audio track, namely 48 KHz 16 bit PCM. If the track is not already in this format, open it in Switch, a free file transfer program, and select the output encoding as 48 KHz 16 bit, mono or stereo to fit your audio file. This program will then convert whatever format your input file is (MP3, WMA, 44.1 KHz PCM, etc) into the required 48 KHz, 16 bit format required.
    Step 10: Repeat the procedures in steps 6 and 7 for this new file. Edit the 'clapper' points with as much accuracy as before, but notice that the 'clapper' waveform will appear different from the first, although hopefully with as clearly defined first ' zero crossing' point.
    Step 11: Repeat the procedure in step 8, and you will notice that the overall file length is different.
    Overwrite the original file length into the right hand box, and take careful note of the resulting figure in the percent change box. Make sure you record whether it is a plus or minus value - it could be either! This is the most important figure, because it represents the percentage variation between the two units.
    Once you have obtained this value, simply apply it to all files recorded with the same recorder and this camera. Providing you can align the start of the file with a single 'clapperboard' mark, there is no need to repeat the rest. Simply change the length of the external audio file by the correct percentage value, to allow the two audio tracks to remain synchronised.
    It may seem a long winded process, but it only needs to be done once, and could then save quite a lot of time, against the option of trying to align tracks manually in your NLE, in small sections.
    You may of course wish to use an alternative audio editor, and the details of this procedure may then be slightly different, but the principle remains the same.

  • Premiere Pro CS4.2.1 and EX1

    Hi all, I am trying to edit a project filmed with EX1 Pal 1440 using Premiere Pro CS4.2.1 to edit. I have a brand new fast system, Intel core, i7 920, 2.7gh with Window7 64bit, 12 gig ram, it was working perfectly with SD DV project but as soon I now started a HD project 50i 1440 it freezes, it loads up but as soon as I do any effect or reduce the speed of a clip it freezes. Any ides please?
    I even created the project again and again but the same problem!
    Thanks
    Mitchell

    What is the best way t oedit Canon XH-H1 HDV files, Canon 5D MarkII
    files and Sony EX1 fimes, do I have to convert them or I can use PP CS4.2.1 as is, do
    I realy need a thrid party plug in such as Cineform or another MPE
    G plugins?
    I am realy getting frustrated with Adobe-PC and regereting why I didn't buy a Mac and Finalcut, is Premiere Pro CS4 capable of editing HD and Full Hd? What is every one else is doing?
    Thanks
    Mitchell

  • Premiere Pro CS4 added contrast H.264 preview files

    Hi,
    Any help I can get with this problem would be amazing.
    I recently updated my OS to 10.6 as there were programs I wanted to run not available on 10.5, however this caused other issues with Premiere that I couldn't fix so I just decided to go back to 10.5. With both installs I reformatted the hard-drive then installed the OS. Now that I've reinstalled OSX 10.5 and updated to the most current version, and then installed Premiere Pro CS4 and updated that to the most current version (4.2.1) and also updated the codecs for Premiere, I'm having an issue with my preview/render files in my timeline that I never had before. It appears that now when I render my original H.264 files the preview/render files have added contrast/crushed blacks and blown out highlights.
    Basically I'm editing H.264 footage from a DSLR, and when I open up a project that I was working on before I began this upgrade mess it opens correctly, but if I extend a clip in my timeline to include part of the original clip that was not previously rendered, Premiere renders this clip with what appears to be increased gain and pedestal/increased contrast. I've also tried this in a new project and it still renders with much more contrast than it used to. Whether in a new project or previous project, Premiere seems to decrease pedestal so my blacks are around/below 7.5 IRE and my whites are at/above 100 IRE. it looks really messed up when this occurs in the middle of a clip that was half rendered before and half after the install. Also I'll bet it's not going to help when it comes to color correcting and it looks like I could be losing image data.
    I don't know what has caused this as it was working properly before my attempted upgrade, and I installed Premiere the exact same way as I did the last time I installed it and I'm using the same version. The only hiccup was after the install and upgrade it said media offline on my old project until it asked me to update codecs, once codecs were updated it displayed all footage in my timeline correctly and then I noticed that I could no longer render preview files to the same standard.
    Here are screen shot comparisons of a video from my timeline. These are back to back frames, the top one was rendered before the most recent install, the other rendered after. I have put a YC Waveform chart beside the image. Sorry I think the best way to see it is just to follow the link otherwise it's gonna be too small.
    http://www.flickr.com/photos/86776146@N03/8101475154/sizes/l/in/photostream/
    Also here is a screenshot of the settings I'll describe below.
    http://www.flickr.com/photos/86776146@N03/8101463115/sizes/l/in/photostream/
    Computer:
    Mac OSX 10.5.8
    Intel Core Duo
    Premiere Pro CS4 (4.2.1)
    Project Settings:
    HDV 720p
    29.97 fps
    1280 x 720
    square pixels
    30fps drop-code
    I-Frame Only MPEG  (video codec)
    I've already searched for a solution to this but come up with nothing. I read a bunch of stuff on the increase in gamma that can happen with .mov files but I don't think this applies to my situation as I would have been having that same issue with my previously rendered footage.
    Anything would be really helpful...Thanks
    Message was edited by: Mike542

    Okay so I've been looking into this in depth over the past few days and I haven't come up with a lot. I have noticed that it's not just the render files but also the inspection window where the clip displays in this manner. It looks like the luma range (as seen in YCbCr scope) is being limited between 7.5 and 92 IRE and I think this is maybe a good indicator of the problem. Why this is happening I don't understand. On my clips that were previously rendered in this timeline there is full range from 0 to 100 in the luma from the YCbCr scope. These files were rendered to an external drive from before I reinstalled Premiere, so it's any h.264 files that I am using after reinstall that are having this issue. I have attached another screen capture illustrating this (look at line to right of scope showing full luma range). Also I have some .mts files from another camera and they import with full luma range as well.
    http://www.flickr.com/photos/86776146@N03/8114886495/sizes/l/in/photostream/
    When playing my h.264 files in Quicktime or VLC they look about the same in terms of blown out whites and crushed blacks. Does Premiere rely on Quicktime for its h.264 codec or does it have it's own? Is there a way to force premiere to update its codecs/manually download and replace the h.264 codec?
    I really can't understand what's happening here and I can't do any work when imported clips are this messed up. Can someone please help out on this!!! Super frustrating and seems to constantly happen with Premiere...

  • Premiere Pro CS4 - Problem with the monitor program.

    Hi. I'm not able solving problems with the monitor using PremiereProCS4. When I drag a photo (also only one photo) in the timeline and play it in the monitor program, vision in the monitor program doesn't run:black monitor or a little part of the photo appear... sometimes distort colours. Asus P5QPRO, Intel 9550 and Sparkle Nvidia GeForce 9800 GTX+ 1024 DDR3; last gpu driver and directX are installed. Different configuration of stratch disks were tested. Where am I wrong?

    Dear Bill,
    thanks for your answer and your article. I tried with your NTSC 4:3 720x480 PAR 0.9 and, "magically", no more problem!!! I used the script pocedure in Photoshop CS4 to resize my images. Now, before starting my workflow and hoping not to overuse your patience, I would like to indicate you my equipment and my target: I use a Canon Eos 7D (generally for still images, 90% are vertical, and just some videos) and I use Premiere Pro CS4 to burn a dvd (normal, 4.7 Gb or double side, more than 8 Gb) with a 16.9 lcd tv (I'm Italian); my camera save as .jpg and .raw (but why use heavy .raw files if I've to redute to 720x480?!??).
    So, according to your "everyone wants the highest quality that they can obtain when doing theri videos..." and "your video project may vary, so you will need to plug in the dimensions for YOUR video project in that case", I've a question: which is the best for me?
    And then:
    1 - Premiere Pro CS4 havn't a batch or a script procedure for still image like PS (only for videos)!?!
    2 - Premiere does'nt allow you to import images like 4.181 Kb (a too large dimension file error appears)!
    3 - In the timeline of Premiere, after you dragged images, you can select them and right click to perform "resize to frame size": it seems to run good without problem, but what appen to the photo? Which is it's pixel?
    4 - In the general preferences of Premiere you can to optimize rendering for "memory" or not: which is the best for you?
    5 - I attached file with a screen of something strange in Premiere: dragging an image (the first of the project) in the timeline, the timeline appears distort (you can see the part in the yellow square): then, when I render the project and play in the monitor program, it becames normal.
    Thanks!

  • Can't Initialize Install of Premiere Pro CS4 Trial

    Every time I try and install the Premiere Pro CS4 Trial that I downloaded from this website, it freezes and the program doesn't initialize. But under the task manager it still takes up CPU. I extracted the premiere trial folder to my hard drive and I'm trying to run the "setup.exe" in the folder.  I then have to go into my task manager and end the process or else it keeps taking up CPU.
    Does anyone know why this is happening? It seems like it is only me.
    My operating system is 64 Bit Windows 7 Home Premium.

    Simply remove/uninstall AME CS5.

  • Premiere PRO CS4 " unexpectedly quit error" since loaded Sorenson squeeze 8.5 is there a bug fix

    Premiere PRO CS4 " unexpectedly quit error" since loaded Sorenson squeeze 8.5 is there a bug fix

    CS4 is old, and there will be no more updates, past the ones on the update site
    All Adobe updates start here and select product, read to see if you need to install updates in number order, or if the updates are cumulative for the individual product http://www.adobe.com/downloads/updates/
    Ask Sorenson if 8.5 is even supposed to work with CS4

  • Premiere Pro CS4 and JVC HM700e (Mac)

    Hey there,
    first i'd like to excuse my bad (school-)english.
    Hope you'll understand my question anyway.
    We just bought a new JVC-HM 700e Camcorder and we use the CS4 Creative Suite in our company.
    The 700e we can produce MP4 (Win) and MOV (Mac + FinalCut).
    Now we have problems to watch and import the Video to a new Premiere Pro Project.
    You have any idea how to handle those files with Mac and Premiere?
    Thank you!
    Nikolaus K.

    Is there any way that I can get Premiere Pro CS4 to recognise Encore CS5 for Dynamic Linking?
    No. The rest is probably thwartet by licensing restrictions for the MPEG and DVD stuff as it existed back then. Anyway, IMO not worth the trouble to work with DL. Due to the limited memory in 32bit apps it will be severely unenjoyable plus it had tons of bugs back then.
    Mylenium

  • Premiere pro CS4+media encoder CS4 problem encoding to WMV and MOV

    Hello,
    I am new to CS4. I lurked around the meanders of CS4 help and FAQ. In spite of the large help database I could not find a solution to my issue.
    I edited a little movie from shots I took during holidays. I edited in premiere pro cs4 and it is a bit faster than CS3 <yoohoo>
    However I want to export the movie as NTSC source to high quality download. In the Expot settings,  I wrote a file output of course so it can encode and compile the movie somewhere on my HDD and I did not touch anything in standad NTSC source to high quality download values and tabs. In the end the movie should be around 848 mega.
    I press OK, then Media Encoder pops up on screen. my project comes automatically in Media Encoder which is neat so I just had to click on start Queue but here is my problem...
    I can wait for 4 hours or more, Media Encoder status states Encoding but nothing moves forward. Elapsed time remains at 00:00:00, Estimated Remaining remains blank.
    Although something triggered my attention when I widen Media Encoder Source Name tab. It sounds like my project from Premiere Pro is placed in a temporary folder instead of using the regular save project file folder in ...>adobe>premiere pro>4>sebsofie2010b which strange.
    I try to place a picture of my issue and perhaps it will help everyone.
    This picture was taken about 1 hour and half after I tried to encode the movie for the fifth time.
    The status quotes "Encoding"...
    Thanks in advance for any help

    Hello,
    This is Song to an Illiad. I had to change Email address and password as I am switching provider soon.
    So Ok to bypass the issue at that time, I simply transfered all files to a jumpdrive and re-did the composition at a friend house. Although my problem persist and Thank you for the Wiki link it was helpful. Sherlock free ware discovered several erronous Codec. Do not ask me why, how, when please. I do not toy around with codecs and all I do is update software but I have several software going from Adobe to Autodesk series as well as Nero Light version that came with my Dvd burner.  Should I also mention I play video games when down time permits, as such I updated several time the DirectX software. Beside this, what is it called... Dvix or Xvid, well something like that... prompted me about 2 months ago to update to a newer version which I did. Finally I installed a freeware to export an avi type to another found on Cnet.com a few months ago as the file could be seen in Premiere pro but there were no Audio track seen in premiere while the client gave me his camcorder and I knew there should be an audio track, it was a sort of camcorder that records on a memory sticks which is why the camera was small. It was a canon but nothing more detailed than that. Anyway, I had the camera with no drivers whatsoever and I had a hard time to find the driver for free online which is why I found a freeware or perhaps was it a shareware or a trial (I am not sure), anyway it decoded and re-encoded the movie which it did successfully with lots of image loss quality but it was succesful. I know I deliberatly threw the shareware or trial straight in the garbage once I was done because I do not want this kind of junk on my PC. Perhaps could it be the issue with Media Encoder not able to start?!?!
    Here comes a couple of texts Copy/Past & image to describe what Sherlock found
    Codec Reporting Utility Output Text
    Date and Time: 26-Aug-2010 23:43:54
    System Information
    Operating System  = Unknown Professional (6.00.6002)
    CPU Descriptor    = Intel(R) Core(TM)2 CPU          6600  @ 2.40GHz
    CPU Clock Speed   = 2400 Mhz.
    Total Memory      = 4095 Mb.
    DirectX Version   = 10.0
    WMI Version       = 6002.18005
    ACM Version       = 5.00.0
    Video Codecs
      Adobe DVCPRO 100 Codec
         FileVersion       = 3.0.1095.1
         CompanyName       = Adobe Systems Incorporated
         FileDescription   = Adobe DVCPRO 100 Codec
         InternalName      =
         LegalCopyright    = Copyright (C) 2007
         OriginalFileName  =
         ProductName       = Adobe DVCPRO 100 Codec
         ProductVersion    = 3,0,1095,0
      Adobe DVCPRO 100 Codec
         FileVersion       = 3.0.1095.1
         CompanyName       = Adobe Systems Incorporated
         FileDescription   = Adobe DVCPRO 100 Codec
         InternalName      =
         LegalCopyright    = Copyright (C) 2007
         OriginalFileName  =
         ProductName       = Adobe DVCPRO 100 Codec
         ProductVersion    = 3,0,1095,0
      Adobe DVCPRO 100 Codec
         FileVersion       = 3.0.1095.1
         CompanyName       = Adobe Systems Incorporated
         FileDescription   = Adobe DVCPRO 100 Codec
         InternalName      =
         LegalCopyright    = Copyright (C) 2007
         OriginalFileName  =
         ProductName       = Adobe DVCPRO 100 Codec
         ProductVersion    = 3,0,1095,0
      AVI Decompressor
         FileVersion       = 6.6.6000.16386 (vista_rtm.061101-2205)
         CompanyName       = Microsoft Corporation
         FileDescription   = DirectShow Runtime.
         InternalName      = Quartz.dll
         LegalCopyright    = © Microsoft Corporation. All rights reserved.
         OriginalFileName  = Quartz.dll.mui
         ProductName       = Microsoft® Windows® Operating System
         ProductVersion    = 6.6.6000.16386
      AVI Draw
         FileVersion       = 6.6.6000.16386 (vista_rtm.061101-2205)
         CompanyName       = Microsoft Corporation
         FileDescription   = DirectShow Runtime.
         InternalName      = Quartz.dll
         LegalCopyright    = © Microsoft Corporation. All rights reserved.
         OriginalFileName  = Quartz.dll.mui
         ProductName       = Microsoft® Windows® Operating System
         ProductVersion    = 6.6.6000.16386
      Cinepak Codec by Radius
         FileVersion       = 1.10.0.11
         CompanyName       = Radius Inc.
         FileDescription   = Cinepak® Codec
         InternalName      = iccvid
         LegalCopyright    = Copyright © 1992-1995 Radius Inc., All Rights Reserved
         OriginalFileName  = iccvid.drv.mui
         ProductName       = Cinepak for Windows 32
         ProductVersion    = 1.10.0.0
      DivX 6.9.2 Codec (2 Logical CPUs)
         FileVersion       = 6.9.2.26
         CompanyName       = DivX, Inc.
         FileDescription   = DivX
         InternalName      = DivX
         LegalCopyright    = Copyright © 2000-2009 DivX, Inc. All rights reserved.
         OriginalFileName  = DivX.dll
         ProductName       = DivX®
         ProductVersion    = 6.9.2.26
      DivX 6.9.2 YV12 Decoder
         FileVersion       = 6.9.2.26
         CompanyName       = DivX, Inc.
         FileDescription   = DivX
         InternalName      = DivX
         LegalCopyright    = Copyright © 2000-2009 DivX, Inc. All rights reserved.
         OriginalFileName  = DivX.dll
         ProductName       = DivX®
         ProductVersion    = 6.9.2.26
      DV Splitter
         FileVersion       = 6.6.6000.16386 (vista_rtm.061101-2205)
         CompanyName       = Microsoft Corporation
         FileDescription   = DirectShow Runtime.
         InternalName      = Qdv.dll
         LegalCopyright    = © Microsoft Corporation. All rights reserved.
         OriginalFileName  = Qdv.dll.mui
         ProductName       = Microsoft® Windows® Operating System
         ProductVersion    = 6.6.6000.16386
      DV Video Decoder
         FileVersion       = 6.6.6000.16386 (vista_rtm.061101-2205)
         CompanyName       = Microsoft Corporation
         FileDescription   = DirectShow Runtime.
         InternalName      = Qdv.dll
         LegalCopyright    = © Microsoft Corporation. All rights reserved.
         OriginalFileName  = Qdv.dll.mui
         ProductName       = Microsoft® Windows® Operating System
         ProductVersion    = 6.6.6000.16386
      DV Video Encoder
         FileVersion       = 6.6.6000.16386 (vista_rtm.061101-2205)
         CompanyName       = Microsoft Corporation
         FileDescription   = DirectShow Runtime.
         InternalName      = Qdv.dll
         LegalCopyright    = © Microsoft Corporation. All rights reserved.
         OriginalFileName  = Qdv.dll.mui
         ProductName       = Microsoft® Windows® Operating System
         ProductVersion    = 6.6.6000.16386
      Intel IYUV codec
         FileVersion       = 6.0.6000.16386 (vista_rtm.061101-2205)
         CompanyName       = Microsoft Corporation
         FileDescription   = Intel Indeo(R) Video YUV Codec
         InternalName      = iyuv_32.dll
         LegalCopyright    = Copyright Intel Corporation 1992-1997
         OriginalFileName  = iyuv_32.dll.mui
         ProductName       = Microsoft® Windows® Operating System
         ProductVersion    = 6.0.6000.16386
      Intel IYUV codec
         FileVersion       = 6.0.6000.16386 (vista_rtm.061101-2205)
         CompanyName       = Microsoft Corporation
         FileDescription   = Intel Indeo(R) Video YUV Codec
         InternalName      = iyuv_32.dll
         LegalCopyright    = Copyright Intel Corporation 1992-1997
         OriginalFileName  = iyuv_32.dll.mui
         ProductName       = Microsoft® Windows® Operating System
         ProductVersion    = 6.0.6000.16386
      MainConcept MPEG Video Decoder
         FileVersion       = 1, 0, 0, 65
         CompanyName       = MainConcept AG
         FileDescription   = MPEG Video and Audio Decoder
         InternalName      = MCDSMPEG.AX
         LegalCopyright    = Copyright (C) 2001-2004 MainConcept AG
         OriginalFileName  = MCDSMPEG.AX
         ProductName       = MPEG Decoder
         ProductVersion    = 1, 0, 0, 65
      Microsoft RLE
         FileVersion       = 6.0.6000.16386 (vista_rtm.061101-2205)
         CompanyName       = Microsoft Corporation
         FileDescription   = Microsoft RLE Compressor
         InternalName      = msrle32.dll
         LegalCopyright    = © Microsoft Corporation. All rights reserved.
         OriginalFileName  = msrle32.dll.mui
         ProductName       = Microsoft® Windows® Operating System
         ProductVersion    = 6.0.6000.16386
      Microsoft Video 1
         FileVersion       = 6.0.6000.16386 (vista_rtm.061101-2205)
         CompanyName       = Microsoft Corporation
         FileDescription   = Microsoft Video 1 Compressor
         InternalName      = msvidc32.dll
         LegalCopyright    = © Microsoft Corporation. All rights reserved.
         OriginalFileName  = msvidc32.dll.mui
         ProductName       = Microsoft® Windows® Operating System
         ProductVersion    = 6.0.6000.16386
      MJPEG Compressor
         FileVersion       = 6.6.6000.16386 (vista_rtm.061101-2205)
         CompanyName       = Microsoft Corporation
         FileDescription   = DirectShow Runtime.
         InternalName      = Quartz.dll
         LegalCopyright    = © Microsoft Corporation. All rights reserved.
         OriginalFileName  = Quartz.dll.mui
         ProductName       = Microsoft® Windows® Operating System
         ProductVersion    = 6.6.6000.16386
      MJPEG Decompressor
         FileVersion       = 6.6.6000.16386 (vista_rtm.061101-2205)
         CompanyName       = Microsoft Corporation
         FileDescription   = DirectShow Runtime.
         InternalName      = Quartz.dll
         LegalCopyright    = © Microsoft Corporation. All rights reserved.
         OriginalFileName  = Quartz.dll.mui
         ProductName       = Microsoft® Windows® Operating System
         ProductVersion    = 6.6.6000.16386
      MPEG Video Decoder
         FileVersion       = 6.6.6000.16386 (vista_rtm.061101-2205)
         CompanyName       = Microsoft Corporation
         FileDescription   = DirectShow Runtime.
         InternalName      = Quartz.dll
         LegalCopyright    = © Microsoft Corporation. All rights reserved.
         OriginalFileName  = Quartz.dll.mui
         ProductName       = Microsoft® Windows® Operating System
         ProductVersion    = 6.6.6000.16386
      Mpeg4 Decoder DMO
         FileVersion       = 11.0.6001.7000 (longhorn_rtm.080118-1840)
         CompanyName       = Microsoft Corporation
         FileDescription   = Windows Media MPEG-4 Video Decoder
         InternalName      = mpg4dmod.dll
         LegalCopyright    = © Microsoft Corporation. All rights reserved.
         OriginalFileName  = mpg4dmod.dll
         ProductName       = Microsoft® Windows® Operating System
         ProductVersion    = 11.0.6001.7000
      Mpeg43 Decoder DMO
         FileVersion       = 11.0.6001.7000 (longhorn_rtm.080118-1840)
         CompanyName       = Microsoft Corporation
         FileDescription   = Windows Media MPEG-4 Video Decoder
         InternalName      = mpg4dmod.dll
         LegalCopyright    = © Microsoft Corporation. All rights reserved.
         OriginalFileName  = mpg4dmod.dll
         ProductName       = Microsoft® Windows® Operating System
         ProductVersion    = 11.0.6001.7000
      Mpeg4s Decoder DMO
         FileVersion       = 11.0.6001.7000 (longhorn_rtm.080118-1840)
         CompanyName       = Microsoft Corporation
         FileDescription   = Windows Media MPEG-4 S Video Decoder
         InternalName      = mp4sdmod.dll
         LegalCopyright    = © Microsoft Corporation. All rights reserved.
         OriginalFileName  = mp4sdmod.dll
         ProductName       = Microsoft® Windows® Operating System
         ProductVersion    = 11.0.6001.7000
      MSScreen 9 encoder DMO
         FileVersion       = 11.0.6001.7000 (longhorn_rtm.080118-1840)
         CompanyName       = Microsoft Corporation
         FileDescription   = Windows Media Screen Encoder
         InternalName      = wmvsencd.dll
         LegalCopyright    = © Microsoft Corporation. All rights reserved.
         OriginalFileName  = wmvsencd.dll
         ProductName       = Microsoft® Windows® Operating System
         ProductVersion    = 11.0.6001.7000
      Nero DVD Decoder
         FileVersion       = 4,11,3,7
         CompanyName       = Nero AG
         FileDescription   = MPEG-1/2/4 & AVC video decoder w/ DxVA
    What should I do? Can I just reinstall the codec from my Adobe CS4 Production Suite (Without) creating more issues and problems? It seemed the Wiki hints were helpful to pin point a problem but not always at giving solution.
    Thanks in advance,
    Seb
    P.S: Could Adobe throw a little software to download to ensure all codecs are what they should be like and prompt user to reinstall straight from our Dvds? It would be soo much easier that way.
    Seb

  • I need a definitive answer for using Premiere Pro CS4 to work with .m2ts and .mts files

    I have a Canon Vixia HF20 and a Sony HDR-XR350V.  The Canon gives me .MTS files and the Sony produces .M2TS files.  What do I need to do to be able to work with these files in Premiere Pro?  I've searched and gotten that I'll need to purchase a codec.  But are both file types going to be good with one codec?
    Also, what are the steps to getting started?  Purchase the codec, load the codec...Will there be any other steps to working with the files in Premiere?
    I'm sorry for the basic questions, I'm a photographer!  I've never worked with video before, and this is HARD!
    Thank you for your help,
    Michelle

    Hi, Michelle.
    I'm nowhere near the authority on this stuff that many of the others are here, but I have Premiere Pro CS4 and I work directly with AVCHD .mts files from my Panasonic camera. I simply browse to the directory where the .mts files are located and drag them into the project. I didn't need to purchase any additional codec, this is natively supported in Premiere CS4.
    I can't speak to m2ts files as I don't have any gear that generates them.
    One thing you do need to know, however, and this is important. Whether you're running a Mac or a PC, if you're going to work with high def footage such as AVCHD, you're going to need a fairly high performance computer with sufficient RAM, good performing hard drives and a fast CPU.
    I tried this on a PC that was fine for my recording studio (audio), fine for professional software development, but choked and stuttered working with HD material. That's not a problem with the Adobe software, it's just the nature of the beast. HD is extremely demanding stuff, so you need top flight gear to work with it. I bought a higher performance PC and now it runs just fine.
    Hope this helps,
    Chris

  • Differences between adobe premiere elements 8 and adobe premiere pro cs4

    I'm planning to download either adobe premiere elements 8 or adobe premiere pro cs4, but first would like to know their differences in regards to features that best suits me.

    I'd recommend posting to the PrE forum, per John's suggestion. The reason for that is you will get more background on PrE there, and few users in the PrPro forum know much about PrE.
    In very general terms, here are my observations:
    1.) PrPro handles everything by hand, while PrE is a "big-button" program, and much is done automatically, or semi-automatically.
    2.) With that hand-work comes great power and PrPro offers so very much more, than does PrE.
    3.) Export options are much broader in PrPro.
    4.) PrE offers a semi-automatic, limited DVD/BD authoring function, while PrPro comes with Encore, a very versatile full-featured authoring program. Little in Encore is done automatically, but one has so much more control over the Project.
    5.) PrPro allows one to edit with Sequences, which can have different types of source footage, one for each Sequence. In PrE, one can only use one type of source footage, or they have to manipulate one, and have the Project set to the other.
    If one wants things simple and easy, PrE is the choice, as it has a lot of Presets and does a lot of work behind the scenes, and is a complete package. If one wants control, and does not mind doing things by hand, and using Encore for authoring, then PrPro will allow that control and provide much more power.
    Good luck,
    Hunt

  • After Effects & Premiere Pro CS4 users: Turn off "Make text and other items larger or smaller" (Win)

    I just made a brief blog post recommending that After Effects CS4 and Premiere Pro CS4 users turn off the "Make text and other items larger or smaller" setting in Windows 7, since it causes some problems.
    Please use this thread to let us know whether this solved a problem for you or whether there are any problems with this solution.

    There isn't really an option to "turn off" the feature. Do you mean to say that it should be set to "Smaller - 100% (default)"?

  • Importing Illustrator and Photoshop files to Premiere Pro CS4 (without rastering)

    Hello,
    I've made some economics graphs in illustrator that i'm importing into premiere.
    Premiere pro cs4 doesn't import illustrator files as layers, just a single image.
    I exported from illustrator to save as a .psd to maintain the layers.
    I then imported the .psd into premiere which created a folder with all the .psd layers.
    I dragged the .psd layers onto the timeline so I could animate them with dissolves, but noticed they became pixelated.
    I rendered the layers and they still looked pixelated, even after export they were pixelated.
    From what I understand, illustrator files become rasterised when you export as .psd.
    Is there any way of maintaining the crisp vector graphics created in illustrator when importing into premiere?
    Can I avoid rastering the files?
    Thank for your help in advance
    Kind Regards
    Ant

    Thanks for your reply and welcome to the forum.
    I wondered why premiere was doing such a bad job of anti-aliasing...it turns out that all the .psd files were imported as square pixels instead of rectangular so I right clicked and selected interpret footage, then selected conform to DV PAL1.45.
    I assumed that as I set up the original Illustrator document as a video document (720x576) it would maintain the aspect ratio.
    Somewhere between exporting to .psd then to premiere the aspect ration somehow changed?
    I've found a great tutorial that appears to have a better workflow than the method I was using, by first creating a template in premiere, which can be exported directly to photoshop, maintaing  the correct aspect ratio. It means i'll have to draw up the graphs in Photoshop now instead of Illustrator.
    http://www.youtube.com/watch?v=s8HUOAJomao&playnext=2&playnext_from=PL

  • Premiere Pro CS4 and Adobe Media Encoder Problems

    I am using Adobe Premiere Pro CS4 on a Mac running 10.6, and I consistently encounter this problem when trying to export a Premiere project using Adobe Media Encoder.
    What does this mean? And has anyone else encountered this problem as well? I really need a fix if there is one, because I really need to be using Premiere. I have reinstalled several times, but to no avail. Help me please!

    Jim, thanks for testing.
    My concerns are about a)distribution and general b)compatibility.
    a) When videos are distributed most of the users will probably try to open the files with Windows Media Player. So it is not a good start to have fresh exported h.264 videos which won't run fine with the 'main' player on windows
    b) I am wondering if the Problems with Windows Media Player may also be a sign of a general compatibility issue of the h.264 video itself
    At least in case b) Adobe would have to look into this.
    Here is another test video:
    http://www.tsxn.com/storage/transfer/Serenity.zip
    Thank you
    Chris

Maybe you are looking for