Overclocking causes jitter in Premiere playback, slows Adobe Media Encoder

I was doing some overclocking on my system last night in order to test the limits. I found some strange results while encoding in Media Encoder and playing back in Premiere. Things actually got worse not better.
When my system was clocked to the defaults video playback was smooth in the preview window and while encoding a segment I checked the log to see how long it took. After the overclocking procedure the video picked up a slight tick or jitter on playback. Media encoder also took about 20 per cent longer to encode the same material? Any ideas? I've noticed people complaining about jitter on playback and being told to overclock to correct the problem. I think some timing issue might be causeing some systems to jerk.
My system:
AMD Phenom II X6 1090T Black Edition
Asus M5A88-V (AM3+)
Memory is 16GB GSkill (2-2x4) at 1666Mhz.
Video: EVGA nvidia GTS 450 hacked into the "support" list.
Things run fine at 232x16, 3.712 Ghz and also slower at 3.2Ghz
but when I did a little performance boosting my Passmark Rating sure went up (>8710) but these other things went slower (or ticked) when I thought they should have been going faster.
I notice the problem at 205X20, 4.11 GHz, voltage 1.476.
What have I done wrong?
~m

Are you talking about the PassMark Rating or the CPU Mark? I guess CPU Mark, and not System Mark. The Phenom is just too slow to achieve such a System Mark IMO.
FYI, the best Phenom II X6 1090T comes out at rank # 329, bested only by 328 Intel systems and the bulk of the AMD systems come out between rank # 400 and # 750. See Benchmark Results
I think that by overclocking you are overly stressing your disk I/O system, causing it to skip sectors and introducing latency on reads for playback. I would just reduce your overclock to something that plays back smoothly, since you will not notice any performance degradation with such a CPU.

Similar Messages

Premiere Pro and Adobe Media Encoder running slow

Hello everyone,
I'm having trouble with CS4, which is running significantly slower than CS3 did on a older machine. The CS4 suite is installed on a Dell Precision M6400:
Windows Vista 64-Bit
Intel Core 2 Duo CPU T9400 @ 2.53 GHz
8 GB RAM
NVIDIA Quadro FX 2700M Graphics with 512MB dedicated memory
The OS is running on a 57.5 GB HD (C:) and the Adobe suite is installed on a 298 GB Solid State HD (D:), except for Adobe Media Encoder, which is installed on the C: drive.
My project has 4 15-16 minute sequences. The sequences are in DV NTSC, 29.97 fps, My scratch disks are set to a folder on the C: drive. Media Cache Files and the Media Cache Database points to a folder on the D: drive.
These are some of the problems I'm having:
- Premiere Pro CS4 generates peak files every time I open a project
- It then takes 3-5 minutes to render before I can preview a 16-minute sequence
- Adobe Media Encoder takes 5 hours to render a 16-minute sequence (as flv) that has been previously rendered
- AME takes 1 hour to render every 15 minute sequence that has never been rendered before
Are my settings affecting their performance? Is there any way to improve it? Thanks.
(Premiere Pro is the only app that is slow)

The data rate for replay is one thing, the data rate from disk to memory then from memory to CPU and back the other way are different matters and ought not to be confused. It is well-established that for a computer to edit AVCHD you need top end components, and note that I said there were three tasks to distinquish with increasing hardware requirements, namely merely replaying the video, specifying edits in the editor and then the rendering. It is commonly accepted by all the industry vendors that to do remotely commercial AVCHD rendering you need a minimum Quadcore CPU then that eats data fast, in order to not let it go to waste you need a fast motherboard bus fast memory and in order for none of those to go to waste you need the fastest disk set-up you can manage. I in fact have a 4-disk RAID0 volume using SATA (I think the disk model is SATAII but I have to await return from the repair center before I can confirm). For this RAID0 volume I have run speed test software from BlackMagic because I have one of their HDTV capture cards. It recorded that this volume which remember is doing parallelised IO is just fast enough to receive a encoded HDTV stream from the BlackMagic card but too slow to receive an uncompressed HDTV stream, indeed when I tried both I found the volume did keep up with compressed but fell behind with uncompressed. Remember that with a RAID0 volume of 4 SATAII disks a given file gets spread over the four disks and hence IO is spread over those 4 3G/s data lanes. Also remember with these disks 3G/s is just a burst speed, for AVCHD we are interested in sustained serial IO which is much less.
Before my machine broke down, I found that it took 5 hours to render 33 minutes of HDTV albeit as it went along it transcoded from AVCHD to a Microsoft HD format for Vista-only. Another interesting thing is that I found that the longer this render ran the slower it became, the estimated time started at 3 hours but the actual was five and the last one third took maybe 3 hours. Because the machine broke after that run I couldn't figure the bottleneck. For my machine bear in mind that at the repair shop we found that the Quadcore had only half the necessary electrical power plugged in, the monitor software showed however that it constantly ran around 90% of whatever capacity that reduced power supply permitted. Now then we can puzzle over why it got slower and slower and yet CPU consumption remained consistent and near to full capacity, memory was not the bottleneck because that was constant at 6.4G. But you can say that this was maybe performing like a Dualcore and was hitting some sort of wall, if you had a 1 hour render with that rate of degeneration of performance factored in what would happen to the render time, and for 3 hours you could be running indefinitely. I hope when the machine comes back the correct power supply will make it behave like a Quadcore should for this type of application. Anyway I have two theories for the degradation. First is just that PrProCS4 was getting its knickers in a twist and thereby just doing more computation per minute of video to be rendered as time went by, maybe internal resource management related to OO-type programming maybe, or related to disk IO falling behind, both these theories have problems, for the latter the CPU usage should then have dropped also.
Anyways, you need really a Quadcore system and blazing fast disk to work fully with AVCHD commercially, we found an external SATAII disk so if I were you I would just go get one and move on with your life.
Message du 03/06/09 16:08
De : "Jim Simon"
A : "JONES Peter"
Copie à :
Objet : Premiere Pro and Adobe Media Encoder running slow
For AVCHD you MUST have FAST disks.
AVCHD actually has a lower data date than DV. You need lots of CPU muscle, but disk speed is really not a factor specific to AVCHD. Anything that works for DV will work just as well for AVCHD (and HDV as well).
>

I cannot import .mov files to Premiere Pro or Adobe Media Encoder.

I cannot import .mov files to Premiere Pro or Adobe Media Encoder.
How do I around this problem?

We need to know a lot more if we're going to help you.
What happens when you try? Do you get an error message? If so, exactly what does it say?
What version of Premiere Pro? Have you installed the recent updates? What operating system?
Does this happen for all .mov files or just some? Has this ever worked before? What version of QuickTime do you have installed?
Here's a page written for After Effects, but the information is relevant to Premiere Pro and AME, too:
http://blogs.adobe.com/toddkopriva/2011/02/troubleshooting-quicktime-errors-with-after-eff ects.html

Mac Pro restarts with kernel panic error during Adobe Premiere CS6 or Adobe Media Encoder CS6 render/encode.

Multiple times this week, my Mac Pro at work has been restarting during renders in Adobe Media Encoder CS6 and Adobe Premiere CS6. This seems to be specific on this computer only. Identical computers don't have this problem. Here is the system report after it reboots to OS X:
Interval Since Last Panic Report: 252068 sec
Panics Since Last Report:          2
Anonymous UUID:                    7DF9A04B-0693-5FC4-60CF-4BC6ABDB3C1E
Fri May 17 15:37:07 2013
panic(cpu 0 caller 0xffffff8009ab7e95): Kernel trap at 0xffffff8009e1b814, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x00000000000000b8, CR3: 0x000000000c3d3000, CR4: 0x00000000000206e0
RAX: 0x0000000000000001, RBX: 0xffffff8039ebfb98, RCX: 0xffffff800a08eb00, RDX: 0xffffff82413abde8
RSP: 0xffffff82413abde8, RBP: 0xffffff82413abe20, RSI: 0x00000000000000b8, RDI: 0x0000000000000001
R8: 0x0000000000000000, R9: 0x00000000000003ff, R10: 0xffffffffffffffff, R11: 0x00000000ffffffff
R12: 0x000000000000004a, R13: 0x0000000000000371, R14: 0xffffff8040611cb0, R15: 0xffffff80404ec008
RFL: 0x0000000000010206, RIP: 0xffffff8009e1b814, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x00000000000000b8, Error code: 0x0000000000000002, Fault CPU: 0x0
Backtrace (CPU 0), Frame : Return Address
0xffffff82413aba80 : 0xffffff8009a1d626
0xffffff82413abaf0 : 0xffffff8009ab7e95
0xffffff82413abcc0 : 0xffffff8009acd4dd
0xffffff82413abce0 : 0xffffff8009e1b814
0xffffff82413abe20 : 0xffffff7f8bcf4d54
0xffffff82413abe60 : 0xffffff7f8bcf72f1
0xffffff82413abf20 : 0xffffff8009d86e2b
0xffffff82413abf60 : 0xffffff8009a3dcfe
0xffffff82413abfb0 : 0xffffff8009ab2977
      Kernel Extensions in backtrace:
         com.apple.nke.asp_tcp(7.0)[78FAA01C-ABC4-3AD3-8D9A-6187F7911E1A]@0xffffff7f8bce f000->0xffffff7f8bcfbfff
BSD process name corresponding to current thread: kernel_task
Mac OS version:
12D78
Kernel version:
Darwin Kernel Version 12.3.0: Sun Jan 6 22:37:10 PST 2013; root:xnu-2050.22.13~1/RELEASE_X86_64
Kernel UUID: 3EB7D8A7-C2D3-32EC-80F4-AB37D61492C6
Kernel slide:     0x0000000009800000
Kernel text base: 0xffffff8009a00000
System model name: MacPro5,1 (Mac-F221BEC8)
System uptime in nanoseconds: 76945023460235
Model: MacPro5,1, BootROM MP51.007F.B03, 8 processors, Quad-Core Intel Xeon, 2.4 GHz, 20 GB, SMC 1.39f11
Graphics: ATI Radeon HD 5770, ATI Radeon HD 5770, PCIe, 1024 MB
Memory Module: DIMM 1, 4 GB, DDR3 ECC, 1066 MHz, 0x857F, 0x463732353155363446393333334700000000
Memory Module: DIMM 2, 4 GB, DDR3 ECC, 1066 MHz, 0x857F, 0x463732353155363446393333334700000000
Memory Module: DIMM 3, 1 GB, DDR3 ECC, 1066 MHz, 0x80CE, 0x4D33393142323837334648302D4348392020
Memory Module: DIMM 4, 1 GB, DDR3 ECC, 1066 MHz, 0x80CE, 0x4D33393142323837334648302D4348392020
Memory Module: DIMM 5, 4 GB, DDR3 ECC, 1066 MHz, 0x857F, 0x463732353155363446393333334700000000
Memory Module: DIMM 6, 4 GB, DDR3 ECC, 1066 MHz, 0x857F, 0x463732353155363446393333334700000000
Memory Module: DIMM 7, 1 GB, DDR3 ECC, 1066 MHz, 0x80CE, 0x4D33393142323837334648302D4348392020
Memory Module: DIMM 8, 1 GB, DDR3 ECC, 1066 MHz, 0x80CE, 0x4D33393142323837334648302D4348392020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0 (5.106.98.100.16)
Bluetooth: Version 4.1.3f3 11349, 2 service, 18 devices, 1 incoming serial ports
Network Service: Ethernet 1, Ethernet, en0
PCI Card: ATI Radeon HD 5770, sppci_displaycontroller, Slot-1
Serial ATA Device: HL-DT-ST DVD-RW GH41N
Serial ATA Device: WDC WD1001FALS-41Y6A1, 1 TB
USB Device: Keyboard Hub, apple_vendor_id, 0x1006, 0xfd300000 / 2
USB Device: Apple Keyboard, apple_vendor_id, 0x024f, 0xfd320000 / 3
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x5a100000 / 2
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8215, 0x5a110000 / 3
FireWire Device: built-in_hub, 800mbit_speed

That doesn't look like a complete panic report. Is there any more to it? Regardless, I suggest you run the extended form of the Apple Hardware Test. If it fails to identify a fault, remove the RAM upgrade and test with the original RAM.

Queuing from Premiere Pro to Adobe Media Encoder no longer working? CS6

Hi there,
Just very recently adobe media encoder has stopped accepting que's from premiere. I choose export in premiere, setup the export details and hit que, adobe media encoder launches, but then it flashes once (like disappears reappears, very quickly) and then it just simply does nothing. No item appears in the que. I have tried opening the premiere sequence directly from adobe media encoder but it does nothing either. If I drag the premiere project directly onto a preset in adobe media encoder, it crashes every time. (though not sure if it would of done this previous to my problem arising)
Anyway, very frustrating as I usually work on a different project whilst media encoder is rendering something out. Now i'm stuck with huge down times as I wait till the render is finished.
Recently updated to Mac OSX 10.8.3 - I think this is when the problem began.
Just updated the CUDA driver to 5.0.45 but this has not changed anything.
Working on a Mac Pro 5,1, 2x2.4Ghz 24GB RAM, EVGA GTX 660 FTW,

Some suggestions and answer at least the 16 questions at the end of the Wiki article.

Rendering in Premiere CS5 vs Adobe Media Encoder? Which is better?

Exactly what the question says. Is there a difference between rendering in Premiere CS5 to rendering in Adobe Media Encoder? Leave your thoughs. Thanks!

Then I have made a mistake. I thought that the AV Export function under File>Export had been fully moved to AME. Obviously, I am incorrect.
No, you're correct: there is not Export > Movie command any longer, and hasn't been since CS3. With CS4, that particular functionality was eliminated, as all exports went through AME, and were logged in the AME queue.
Things have changed yet again with CS5. There is still no Export > Movie as there was in CS3 and earlier; everything still must be encoded through AME. However, in CS5, when you initiate the export, you have two options: Export and Queue. The latter option does what CS4 exports did: they go into the AME queue for sequential export. The former option basically launches a "headless" version of AME and exports as a one-off. The export is still being performed by AME; it's just that you don't have the virtue of it working in the background as it does with the Queue button. I've also encountered some weirdness with Export when it comes to cropping and using hardware MPE, but that's a different story. I haven't done any hard-and-fast tests of which is faster--Export or Queue--but I'd take Harm at his word that Queue is the faster option.

Premiere Pro CC / Adobe Media Encode CC not using GTX980 EVGA

Generation of movies using h.264 encoding is not using GPU. Based on the logs from video card there is no usage even if the selected renderer is Mercury Playback Engine GPU Acceleration (CUDA). How can I enable its usage?

Hi mate, same here.. I can't do it work, simply.. I select GPU in Premiere and AME (gtx 970 in my PC and gt755M in my laptop, neither is working), GPU is 0% of use to do a simple video conversion.
To show that is a Adobe problem, this guy create his own exporter plugin ( SHAME ON YOU ADOBE!). With it AME work very, very fast, but i have issues too when change the video format to MP4.
NVidia GPU-accelerated H264-encoder plugin, ready for public testing
I don't know what i do. I think Nvidia and Adobe messed up very bad this feature.. Nice Adobe, i have a good GPU but i have to wait very long times (1hr videos conversion) because you guys can't do a simple exporter plugin that use GPU power.. So, stop collecting our money only and GO TO IMPLEMENT OUR NEEDS! Have a nice day.

Horrible video output quality with Premiere Pro CS4 + Adobe Media Encoder

I am trying to make some changes to a DV format file, and output as the same DV format. When the video is brought into Premiere, it looks crisp in the left-hand video box. But, when playing it on the right window and when encoding it, it comes out as a mess with substantial compression artifacts.
What confuses me is, I have experimented with a lot of codecs--even uncompressed AVI. There is no change in the video resolution--source is 720x480, as is output. I am keeping all the pixel aspect ratios the same as the source footage.
What is creating this distortion? I have no scaling of the video whatsoever in the sequence...
Is there some compression box I'm not seeing here?
I've attached a screenshot of a still from the video. As you can see, substantial artifacting around the lettering, making the text unreadable.

Some suggestions and answer at least the 16 questions at the end of the Wiki article.

Long load times normal for Adobe Media Encoder from Premiere CS5?

When I export a sequence from Adobe Premiere CS5 using Adobe Media Encoder, the system freezes for several minutes before giving me the exporter screen. Then, when I've loaded my settings and clicked "export," the system again freezes for several minutes before beginning to encode. I'm using a system with an Intel I7 CPU 930 @ 2.80Ghz 2.80 Ghz., 24 GB of ram, Windows 7 Ultimate 64 bit operating system and an Nvidia quadro FX4800 graphics card.. Everything else is fast, but AME is slow. Is this normal? Should I reinstall AME?

Not sure what you mean about the process. From Premiere CS5, I click on "export" which brings up a menu. I select "media" from the menu which brings up the Adobe Media Encoder. I adjust my settings and click "export" from the bottom of the screen to immediately render the Premiere file. Clicking "Queue" would put the program into the AME Queue. Am I missing something? On the slowness issue, looks like I need to reinstall AME. I've been reluctant to do that, partially because I'm using some Matrox hardware and I'll have to reinstall the Matrox softare to populate the matrox settings into the media encoder. Looks like it may be worth it.
Thanks.

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

Adobe Media Encoder stops responding

I have Adobe CS4 master collection installed here and I've run into a serious problem trying to get it Adobe Media Encoder to do what it's meant to do...encode.
I export the project and in the initial export options window I can set everything up. I proceeed to Adobe media Encoder to finish the job and it opens and shows my video in the que, however, when I click to change the preset, or even click to start rendering, Adobe Media Encoder will simply hang forever. It just stops responding. It never used to do this.
I'm running an intel core2quad q8400 @2.66gHz
on fully updated windows 7 professional, 32 bit.
Nvidia geForce 8400 GS,
3.25 Gig useable RAM
It's not project-specific because i've tried it with another project and it does the same thing. Tried restarting, tried to reinstall Premiere pro and adobe media encoder, tried to reinstall the entire creative suite, tried the premiere-shortcut-in-the-dynamic-link-folder thing...I'm at wits end and I nearing deadline.
Anybody out there who might have conquered this problem under similiar circumstances? Please help...

When I was having this problem, I ended up having to search the entire
sequence for the problem area, a video or image that was causing the encoder
to fail. After narrowing it down to a certain section of the timeline, I
worked through elimination to find the problem video, removing one video,
image or image sequence at a time and encoding the problem area again....on
the two occasions I've had to do this, I found one corrupt video and one
large sequence of images that, which for some reason the encoder didn't
like...re-encoding the problem video and putting it back into the project
solved it for me.

AME Adobe Media Encoder Cuda GPU Acceleration not activated, How do I activate it

Mac Pro Early 2009 4.1, Processor 2.93 GHz Quad-Core Intel Xeon, Memory 16 GB 1066 MHz DDR3 ECC, Graphics NVIDIA GeForce GTX 680 2048 MB, Software OS X 10.9.2 (13C64)
Adobe CS6 suite up to date all programs as of 3-18-14
NVidia Cuda Driver 5.5.47 installed, Open CL and GL capable
I read this article http://blogs.adobe.com/kevinmonahan/2013/09/13/enabling-cuda-for-the-mercury-playback-engi ne-in-the-macbook-pro-retina/. it shows GPU acceleration through AME (see below). In my AME que window I do not see this

Todd:
(edit)
Just reread - sorry, CS6 vs CC.
What about AME CC?
http://blogs.adobe.com/kevinmonahan/2013/09/13/enabling-cuda-for-the-m ercury-playback-engine-in-the-macbook-pro-retina/
So, CUDA acceleration in AME and OpenCL is supported. Anyway to monitor this? I get FAILED when I try either (on a box with nVidia, or a box with AMD).
Found this: http://helpx.adobe.com/media-encoder/using/whats-new-media-encoder-7-1.html#gpu-accelerati on
GPU acceleration
Adobe Media Encoder now takes advantage of GPU for rendering purposes. Both CUDA and OpenCL are supported. The latest release of AME uses the GPU for the following renders:
Scaling (HD to SD; SD to HD)
Timecode filter
Pixel format conversions
Deinterlacing
Aspect ratio changes
All effects in the Effects tab
GPU accelerated effects in Premiere Pro
If you are rendering a Premiere Pro sequence, Adobe Media Encoder will use the GPU render preference you have set for the project. All GPU rendering capabilities of Premiere Pro are utilized.The limited set of GPU renderable tasks in Adobe Media Encoder is only for renders that originate in Adobe Media Encoder.
If you are rendering a sequence with native sequence support, the GPU setting in AME is used and the project setting is ignored. In this case, all GPU rendering capabilities of Premiere Pro are utilized directly in AME.
If your project uses 3rd party VSTs (Virtual Studio plugins), the GPU setting in the project is used. The sequence is encoded through headless Premiere Pro just as in earlier versions of Adobe Media Encoder. If Enable Native Premiere Pro Sequence Import option is unchecked, headless Premiere Pro will always be used and the GPU setting is used.

Adobe Media Encoder CC 7.2.2 Update Installation failed. Error Code: U44M1P7

So, I get this strange error when I try to update AME CC 7.2.2. What to do?
Adobe Media Encoder CC 7.2.2 Update
Installation failed. Error Code: U44M1P7

[ Mac 10.9.3 / Indesign CC update fail / Premiere update fail / Adobe Media Encoder 7.2.2 update fail ]
AME:lle ei ole omaa unistalleria, vaan sen asentavat muut CC:n ohjelmat käyttöönsä.
Mulla ei onnistunut ID CC:n ja Premierin päivitys. Niihin olisi ollut tulossa vain tuo AME:n päivitysosa. Ainakin mulla ongelmia näytti aiheuttavan MCMHMPEGVideoCodec.framework, joka esti AME:n päivittämisen. Poistin sen käsin AME:n sisältä.
Poistin Premieren (uninstall) ja asensin sen uudestaan. Buuttasin koneen. Sen jälkeen molempien päivitys onnistui.
There's no separate uninstaller for AME. My ID CC and Premiere couldn't be updated (for the AME7.2.2 update). MCMHMPEGVideoCodec.framework seemed to be the factor.
I uninstalled Premiere (only), after having manually removed MCMHMPEGVideoCodec.framework from inside AME. After boot I installed it again and voilà, both (ID & Premiere) updates went trough fine. The MCMHMPEGVideoCodec.framework was on place inside AME too.

Adobe media encoder CS4 - alised graphics and small black bars at 480x360 for web---HELP!

I recently installed the CS4 premiere software with Adobe Media encoder. I encode video for the web.
I have been a professional web video producer for over 10 years and have been using adobe products my whole career
My issues are:
1) I can not get clean edges on my graphics when exporting a flash video (.flv or .f4v) using "field order: progressive" as it should be for web output. All my graphics are high quality and I have tryed many formats (.eps, .psd, .gif ,jpg, .pnd) but once I change the field order drop down in the encoder settings to "(none) progressive" the graphics become alised...
2) My videos which are a size of 480x360 now have small black bars at the top and bottom after encoding the original down to 480x360. I have tried to crop the video so the bar go away but the whole video get fuzzy...WTF
I have spent so many hours reading and searching trying to fix these two issued and I am thinking that I am going back to my old software and discrediting the new adobe product every chance i get!!!!!!!!!!
I was previously using premiere pro 1.5, editing video and graphics and then exporting an uncompressed .mov file and then used Flash 8 Video Encoder to render a .flv file. This produced great video with crisp graphics.
PLEASE HELP

Stan,
I was using the on2VP6 codec at data rates from 275k to 400k with good results. -- with the new CS$ endcoder i am used h.264 at 500k to 700k, video quality looks good but the graphic overlays look like alised crap. In the encoder settings the edges of the graphics get jaged when I make the field order progresive...
I am starting with DV NTSC video at 720x480.
I am going to go back to my old work flow and test it. The settings are a bit different from premiere pro 1.5 to CS4 -- in 1.5 i could export out an unconpressed .mov with square px and then bring that large file to flash media encoder to create the .flv

Adobe Media Encoder and Macromedia Flash MX 2004

I already posted this question here: http://forums.adobe.com/thread/777473?tstart=0
When I first posted I thought it had something to do with Premiere but now think it has something to do with the Adobe Media Encoder.
If you want to delete that message then feel free.
I'm using Adobe Premiere Pro 2.0 and have recently installed Macromedia Flash MX 2004.
Now when I go to export to Flash I don't get the Adobe Premiere's Flash Export dialog box when I press "Options" from the Export Settings. I get the Flash MX Professional 2004 "Flash Video (FLV) Exporter." It doesn't allow me to change any of the parameters.
I then un-installed Macromedia Flash MX 2004 but still get the same "Flash Video (FLV) Exporter."
Any ideas on how to get the Premiere exporter back?
I uninstalled all macromedia programs, Dreamweaver, Extention Manger, and FreeHand.
I now I get this message when selecting Macromedia Flash Video from the export settings:
"Cannot find Flash Video export Module for QuickTime. Please install and retry."
So I un-installed and re-installed QuickTime and got the same message:
"Cannot find Flash Video export Module for QuickTime. Please install and retry."
No quite sure if the above message was talking about reinstalling QuickTime or Premiere, so I uninstalled and reinstalled Premiere again, agian and got this message:
"Cannot find Flash Video export Module for QuickTime. Please install and retry."

Well there is no answer to my question, but I did finally get the Adobe Media Encoder dialog box to come back again.
After uninstalling Premiere and QuickTime, then shutting down the computer, rebooting and logging on to the Admin account, shutting down again, rebooting again, logging in to the Admin account again ...
I then went in to the registry and removed all the Entries that had either of these in it:
C:\Program Files (x86)\Common Files\Adobe\DVA\COM
C:\Program Files (x86)\Common Files\Adobe\DVA\FLASH
and these as well
C:\Program Files (x86)\QuickTime\QTComponents\FLV.qtx
C?\Program Files (x86)\QuickTime\QTComponents\FLV.qtx
Rebooted the computer, logged back in to Admin.
I then re-installed QuickTime, and rebooted.
I then installed Premiere and the Adobe Media Encoder Flash dialog now shows up.
I'd be careful messy with the registry if you are trying to fix this type of problem. Try uninstalling quicktime and premiere and do the above shutdown, reboot sequence a number of times before doing anything to the registry.
I'm not sure what I'm going to do about that Flash Website I've working on...

Overclocking causes jitter in Premiere playback, slows Adobe Media Encoder

Similar Messages

Maybe you are looking for