Premiere Pro and Audition workflow problem (urgent!!!)

Hello! These is my problem: I need to Edit clip in Adobe Audition but with many clips of an interview, fix noise problem, save and back to premiere whit those clips remain linked. There is a way to do this?
I use CS6 version!
Sorry for my bad, really bad english! Thanks!!

Master Collection, Production Premium and Creative Cloud should include both PP and Audition.

Similar Messages

Suites containing Premiere Pro and Audition

Hi folks
Sorry for the odd question. I'm curious to know exactly which suites Adobe offers that include Premiere Pro and Audition. Is it only the Master Collection or are there others where fewer apps are included?
I'm trying to configure a PC with just what I need on it and acquiring Master Collection is simply overkill and a bit like swatting a fly with a bazooka.
Cheers... Rick

Master Collection, Production Premium and Creative Cloud should include both PP and Audition.

Speaker buzz and interference in Premiere Pro and Audition CS5.5

Several months ago I upgraded to an Asus G10AC PC for my editing. When I first started using the Asus I was using a basic 5.1 computer speaker system plugged in using the 3.5mm headphone jack for sound. I noticed right away that when I opened Premiere Pro or Audition I would hear some interference similar to when you put a cell phone too close to a wireless transmitter (buzzing and beeps). I assume it is picking up something from the hard drive(s) or MoBo. The noises didn't show up in my exported files so I lived with it.
Recently I added a Behringer Q802USB mixer and some PreSonus monitors for more accurate audio editing. So now all of my audio is more defined and easier to hear accurately. The beeps and buzzing don't seem to be an issue but what I hear now is a constant high pitch sound from both speakers but more from the left than the right.
But what is strange is that the high pitch sound is only there when either of the 2 Adobe windows (Pp or Au) are active. I can use windows explorer, QuickTime and windows movie maker to play audio and video files and they are clean. As soon as I click away from the Adobe windows the high pitch sound disappears. I can even RAM preview clips in After Effects and the sound is clean. When I plug in headphones to the PC I constantly hear the buzzes and beeps no matter what is open, but the high pitch sound isn't there or it is at least not as noticeable. I also tried disconnecting the USB cable from the mixer and reconnected using a 1/8" male from the headphone that splits the signal out to 2 1/4" male outputs to connect to an input on the mixer. Same noise issue all around so from what I can tell the issue isn't the USB connection or the mixer.
To double check that it wasn't a mixer issue I connected it to my Sager laptop using the USB and everything is crystal clear no matter what I play the audio on (Pp, Au, windows explorer, YouTube, QT, etc). This laptop is usually connected to the same mixer but using one of the headphone cables that splits to the 2 1/4" males.
This sounds like an issue with my PC but I wanted to check here since the issue only occurs when Pp or Au are open. Is there something that these 2 programs gain access to that the other sound producing programs do not? And to clarify, it isn't only when playing audio in these 2 programs. The noise begins as either program begins loading and is constant until I click to a different window. Sometime I actually have to close out of Pp to get it to stop. Could it have something to do with these 2 programs having access to the microphone function? And I am not tech savvy enough to understand if the 2 Adobe programs use the same drivers as the other programs that do not have the sound issue.
I briefly attempted trouble shooting the audio drivers but the computer says that I my driver is up to date. I tried manually replacing it and switching to ASIO but couldn't get it to accept it so I went back to the original driver and setting.
Any insight would be greatly appreciated.
Cole

Thanks for the fast response Richard.
I thought that too but what is causing it to only happen when engaging these 2 programs? It seems if it was a grounding problem it would be universal for all programs that produce sound. It is only when these 2 programs begin loading and while they are selected.
Do you have any theory about what component they are accessing that brings this interference into play? At first I figured it must be sound card related but wouldn't the other programs that produce sound also call upon the same hardware and drivers when playing audio?

Update problems with Premiere Pro and AAM (Adobe Applications Manager)

I am using Premiere Pro CS6 via a Creative Cloud subscription and am having a problem. AAM (Adobe Application Manager) says that Premiere Pro needs updating to 6.0.1 but if I run Premiere Pro and check it's version, it says it already is 6.0.1 - so how would AAM fail to understand that PP is at 6.0.1 when PP knows that it is already there??
So guess the real question is what does AAM use to decide what version the different apps are at and then tell you which updates you need to install? And how might it have gotten confused?
And most of all, how to "un-confuse" AAM?
Please don't suggest uninstalling PP - because with CC and AAM, then you have to re-download the entire app once again from inside AAM - it doesn't keep the install media around after it has installed it, but insists on downloading the same version yet again, and taking another hour or two to get back to where it was the last time it downloaded the app.
Any suggestions??
Thanks ...
-Bob

Hi Bob,
I was having a similar issue.
I was getting a dialog, when exporting from Pr informing me that there was a codec update available for Pr, and that I should update via help. But the AAM kept telling me that everything was up to date.
I just tried to repeat the problem to respond to your post ... and it isn't happening anymore!
It may not be happening anymore because I opened Adobe Media Encoder CS6 outside of Pr this morning. That is all I have done outside my normal rutine since the last time I had the annoying dialog...
Kind of grabbing at straws.
Cheers,
DK

Why is "edit in Audition" greyed out in Premiere Pro and After Effects?

Since the CC 2014 launch, the option in in Premiere Pro and After Effects to "edit in Audition" is greyed out. Right-clicking a clip in Premiere Pro doesn't have an option for Audition. I cannot send my compositions, sequences or clips to Audition for audio editing. I contacted an Adobe Support personnel earlier this evening. They suggested to go into my Mac's System Preferences and enable a root user, log out of my account, log into the root user, shut down and boot up into safe mode. None of these scenarios worked. It is still greyed out, in both user accounts.
Is this a known issue? I even uninstalled and reinstalled Audition. Still nothing. All my Adobe apps are updated. My Mac is updated. Again, never had this issue before.
I'd appreciate any assistance!
Thank you!
Cheers,
Evan Lockhart

I may have an answer for you, but not sure if my resolution will work for Macs.
First, here's my system and initial info. I'm using a work computer, operating system is Windows 7. I just upgraded to Adobe CC 2014 about a week ago, and I also uninstalled the previous versions of all my Creative Cloud programs after installing the new versions (CC 2014 doesn't just update the previous version, it installs a new program and doesn't automatically uninstall the previous CC programs). Not sure if the uninstall is necessary, for this resolution to work.
Anyway, after I installed Premiere Pro CC 2014 and Audition CC 2014, the Edit Clip in Adobe Audition command was available from the Edit menu in the Menu bar, but was disabled in the right-click menu for the sequence (for the right-click menu, it was visible, but greyed out and disabled). When I tried to use the command from the Edit menu in the Menu bar, it gave me a dialog box to fill out and it created a new folder (titled "Adobe Audition Interchange"). So, the command, when selected from the "Edit menu" obviously uses a different process than the command from the right-click menu. Anyway, I didn't want a new folder created or to fill out a dialog box, I just wanted it to behave like it used to. Basically, when I right-click the sequence and select Edit Clip in Adobe Audition from the right-click menu, it just opens Audition and the audio waveform is visible.
I was able to resolve this and get the right-click command working by reading a couple of articles on this same issue from Adobe CC (not CC 2014) and using those to figure out how to fix this in Adobe CC 2014.
Here's what I did:
I had to locate my .sesx files in my system. They are NOT in the same location as they were for the previous version of CC (at least, they weren't for me). I had to use the Search command and look for .sesx extensions to locate them.
Found them under the path C:>Users>Public>Public Documents>Adobe>Audition>7.0>Session Templates. Note that (for me), there was a folder titled 6.0 on the same level as the 7.0 folder. I selected the 7.0 folder as that folder contained the most recent set of .sesx files. I checked the 6.0 folder and those were the .sesx files from the previous version, so I deleted that folder just as a clean-up step.
I right-clicked on one of the .sesx files in the Session Templates folder and then selected Open with from the right-click menu. The Open with dialog box displays and provides a list of programs.
I selected Adobe Audition CC 2014 from the list of programs (you may have to browse to find it) and then selected Always use the selected program to open this kind of file. I then clicked OK to submit the configuration command and close the Open with dialog box.
I restarted Premiere Pro CC 2014 and the Edit Clip In Adobe Audition command was now enabled on the right-click menu and was working properly.
I wept with joy..... OK, not really, but I'm always irritated at ridiculous regression errors and a lack of thorough testing of new software versions, so I am happy to resolve frustrating issues.
Don't know if this will help you, or if you already resolved your issue. Either way, good luck!
~ Jim

Problem with premiere pro and encore with win7 enterprise 64-bit.

We are a college with approx 500 pc's running win7 enterprise 64-bit. Premiere pro and Encore will only open with admin login, not user login. All other packages ok. Any suggestions as to why this is?

Our lab has just had CS6 installed on it, running Win 7 enterprise. A user account will open a Premiere Pro project. I've done it. That was only to check that everything worked ok. I edited a couple of clips and stuck them on a sequence (16:9 PAL DV) and it played them ok and the project was saved back to the USB hard drive OK.
I have also opened up encore, made a new project and saved it to the USB HDD. No assets were added to it, just checking that the preference files had copied from the central server to the machine, so that users have certain options already pre-selected.
What exactly are the problems with Win 7 enterprise?
Andrew

Premiere pro and media encoder CC problem

Hi guys,
I hope some of you can help me, I installed new version of premiere pro and media encoder CC and now none of them works, I can edit in premiere but as soon as I press export message apears ''sorry a serious error has occurred that requires adobe premiere to shut down'' when I try to open encoder it shut down on startup.
I'm using old IMac 2.4ghz intel core duo, 2gb 667 mhz ddr2 sdram, ATI Radeon HD 2600 Pro 256 MB, OS X 10.8.5.
This is the error report, please help:
Process:
Adobe Media Encoder CC [946]
Path:
/Applications/Adobe Media Encoder CC/Adobe Media Encoder CC.app/Contents/MacOS/Adobe Media Encoder CC
Identifier:
com.adobe.ame.application
Version:
7.2.0.43 (7.2.0)
Code Type:
X86-64 (Native)
Parent Process: launchd [136]
User ID:
501
Date/Time:
2014-02-10 08:44:28.001 +0100
OS Version:
Mac OS X 10.8.5 (12F45)
Report Version: 10
Interval Since Last Report:
1264 sec
Crashes Since Last Report:
1
Per-App Interval Since Last Report: 24 sec
Per-App Crashes Since Last Report:   1
Anonymous UUID:
7E711766-8C55-00D3-811F-852F73421407
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
terminate called throwing an exception
abort() called
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib
0x00007fff9483c212 __pthread_kill + 10
1   libsystem_c.dylib
0x00007fff8d74ab24 pthread_kill + 90
2   libsystem_c.dylib
0x00007fff8d78ef61 abort + 143
3   libc++abi.dylib
0x00007fff96ff79eb abort_message + 257
4   libc++abi.dylib
0x00007fff96ff539a default_terminate() + 28
5   libobjc.A.dylib
0x00007fff8f49d887 _objc_terminate() + 111
6   libc++abi.dylib
0x00007fff96ff53c9 safe_handler_caller(void (*)()) + 8
7   libc++abi.dylib
0x00007fff96ff5424 std::terminate() + 16
8   libc++abi.dylib
0x00007fff96ff658b __cxa_throw + 111
9   com.adobe.dvacore.framework
0x000000010022814d dvacore::filesupport::DirHelper::Create() + 813
10 com.adobe.AMEAppFoundation.framework
0x0000000104f285e9 AME::foundation::AppUtils::GetUserPresetDir(bool) + 425
11 com.adobe.Batch.framework
0x0000000105c0a842 AMEBatch::Initialize() + 2194
12 com.adobe.ame.application
0x00000001000273cb AME::app::AMEAppInitializer::AMEAppInitializer(exo::app::AppInitArgs&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >&) + 811
13 com.adobe.ame.application
0x000000010000ad6a AME::app::AMEApp::InitApplication(exo::app::AppInitArgs&) + 2426
14 com.adobe.exo.framework
0x000000010513e77a exo::app::AppBase::Initialize(exo::app::AppInitArgs&) + 1066
15 com.adobe.ame.application
0x00000001000141a8 AME::RunTheApp(exo::app::AppInitArgs&, std::vector<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >, std::allocator<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > > >&) + 1576
16 com.adobe.ame.application
0x0000000100056a38 main + 424
17 com.adobe.ame.application
0x0000000100003f74 start + 52
==========================
Edited by moderator to trim the crash report down to the essentials. Since these forums do not support attaching file (due to legal and security issues), we recommend uploading files using Acrobat.com’s Sendnow (https://sendnow.acrobat.com) or similar services (YouSendit.com, etc.)

Hi mawe81,
Thanks for posting on Adobe forums,
Please follow this document http://adobe.ly/1f2EHCg
and let us know if this fix your issue or not.
Regards,
Sandeep

Premiere Pro to Audition Export (CS6)

I'm trying to edit an audio clip from to Premiere Pro in Audition. I am able to open the clip in Audition and edit it, but when I try to select "Export to Premiere Pro" from the Multitrack menu option, it won't allow me to click on it. I've watched numerous videos and in all of them, there is a window that pops up asking Export options before the clip even opens in Audition. That window never pops up for me, it just opens straight into Audition. I'm sure this has the be the cause of the problem. Has anyone else experienced this problem? And how would you go about solving it? Thank you.

I might be wrong, but I thought you could only do what you're asking when you send the entire sequence over to Audition, not just a clip.

Premiere Pro and Media Encoder crash while rendering H.264

Very recently, a problem's popped up where Premiere Pro and Media Encoder (CC) will crash while rendering H.264.
It's only while rendering H.264 - other formats seem to work fine.
And I don't mean that it returns an error, I mean it hard crashes with a Windows "Adobe Premiere Pro CC has stopped working" popup.
It doesn't crash at a consistent time during the render, even on the same project. Occasionally, it won't crash at all, but this is usually not the case.
I've tried disabling CUDA and my overclock to no avail. Please help!

On the topic of opening a project on the exact same version of Premiere Pro CC 2014 (yes it is definitely up to date, and the 2014 version), to overcome this export crash problem that ZachHinchy has brought up - you can't. Technically speaking, one should easily be able to open a Premiere Pro CC 2014 project from one system on another system running the exact same up to date, legitimate version of Premiere Pro CC 2014 without any kind of error. But for some reason, this has been disallowed(?) by Adobe. It has facepalm written all over it. Does anyone agree that this is at least a little bit silly?
I have tried exporting a Final Cut Pro XML from my project to try and open the sequence at uni on a Mac, so I can render my project when I finish my edit. It half works - the clips are there, but the sequence is gone - i.e. 12 hours of painstaking sequencing and micro-edits that had me at several points in time wanting to insert my hand through my monitor with enough force to make a large hole. I really cannot afford redo this sequence, as my assignment is due tomorrow, and I have to work at 6 oclock in the morning, so I also cannot afford to stay up till the early hours of tomorrow morning. Wish me luck that some miraculous event has taken place overnight that will somehow allow me to just open my project, on the same version of Premiere, on a Mac, without hassle. (Apple OS is not friendly to anything but its own selfish nature, so I am having doubts).
Adobe please, if you can do anything at all to help, you will save my assignment, and my faith will be restored. Otherwise, I'll just get my money back and buy Final Cut instead.
I cant even
If I find a way to fix either of these problems, I will post straight away.

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).
>

Coordinating Premiere Pro with Audition

I have a video I'm editing. I've completely thrown out the camera sound track and I'm creating the audio from scratch from various sound clips. In some cases I want to coordinate the editing of my video clips with the sound track, and in other places I want to coordinate the sound (e.g. foley) with the video. Can anyone suggest a work flow for this?

A general video on working with PPro and Audition (from CS5.5)
http://tv.adobe.com/watch/no-stupid-questions-with-colin-smith/premiere-pro-to-audition/
Another (more recent) video from Niels:
http://tv.adobe.com/watch/creative-week-how-tos/adobe-audition-cs6-for-audio-sweetening/
Even though it is called "Speech Alignment," I've successfully used this in foley to match up my foley footsteps (and other sounds) with what was from the on-set sound.
http://tv.adobe.com/watch/sound-your-best-adobe-audition/how-to-use-auto-speech-alignment- in-audition/

Premiere Pro 6.5 Installation Problems

So I'm having a problem with my CS5 and CS6.5 Premiere Pro. All of it installs correctly so it says, but every time I try to open 6.5 it starts and then quits. I installed it on a wiped clean computer. I work at a non-profit and we have older computer but it's running on a 2009 iMac:
Processor: 1.83 GHz Intel Core Duo
Memory 2 GB 667 MHz DDR2 SDRAM
I know very little about the internal workings of a computer, but there's celtx on this computer and that's about it. There isn't much else on the hard drive. I tried CS6, and found out that it isn't compatible with my iMac, so I got the 6.5 and the CS5, and I've tried it on two different computers, both with the same processor and memory as well 2009 iMac.
Any help would be great, I haven't found anything that was helpful, just to wipe my computer clean, which it already was when I received it.
Please help! I've been working on this problem for awhile now and there aren't any answers.

Where did you buy the CS5 version? Like I said, there is no such thing as Premiere Pro CS6.5. The only "6.5" that ever existed was the old Premiere version (before there was "Premiere Pro"). If your purchased product contains a Premiere Pro version 6.5, then you have been sold a counterfeit copy of Premiere Pro and you should get your money back ASAP.
If you have Premiere (not Pro) version 6.5 (not CS6.5), then you can try to activate CS5. However, I don't hold out much hope because even if Adobe allowed an old Premiere-6.5-to-Premiere-Pro-CS5 upgrade at one point, it was likely a limited-time offer and the current activation servers may not allow it. If you were sold your copy of CS5 with only Premiere 6.5 as the source of validation, you should still try to get your money back, because at this point in time it's likely not a legitimate source of CS5 activation.
Jeff

I can´t download Premiere Pro and it wont appear on creative cloud

I was looking for a good software to download because I recently went to a trip and I recorded a lot of footage so I wanted to edit that and make it just one video (I use Windows 7). So I looked for After effects first, I downloaded Creative Cloud but I couldn´t find the After Effects app so I downloaded Prelude. While I was using Prelude, I looked for more information on how to use it and I realized that I must have Premiere Pro, and I am kind of familiar with the software so I said "why not?" When I looked for it I couldn´t find it on Creative Cloud either and I don´t know why. I already tried to look for FAQs and nothing answers my question and I want to know if any of you have the same problem.

you need a 64 bit computer.

PREMIERE PRO CS5.5 Gamma problem while exporting project to mjpeg A or B

Dear Sir,
I'm in a big ****. I've directed and edited 1h documentary for Finnish television, also, the technical specs requested by the TV Channel is all production Broadcast masters must be encoded with Apple ProRES codec or MJPEG A or B.
As i'm working on PC (win7), the ProRES codec doesn't exist on PC system, so i've done the export to MJPEG. The problem is i have a different gamma level when i watch the final export with Quicktime or VLC. Of course i can adjust the level in those players, but it doesnt effect the file. When i import the Qt file into a Premiere sequence, the gamma level is still **** and different from my original level i have from my timeline and preview window. If i export the project to H264 1920x1080p25, then the gamma is perfect with Qt, VLC and WinMedia player. But the TV station don't wanna work with H264. Deadline is on next monday, and i can't send a Qt MJPEG file with wrong gamma !!!Any chance to find a solution to fix it ??? After reading different forum, i can see this problem exist since many years and never been solved.
What can i do ??
Denis.

Things is my prpject includ few effect plugins i bought, so what ever i could find a mac, not your i could export xml project to finalcut with plugins it dont have
Denis
Sent from my iPad.
Le 31 mai 2013 à 15:20, Fuzzy Barsik <[email protected]> a écrit :
Re: PREMIERE PRO CS5.5 Gamma problem while exporting project to mjpeg A or B
created by Fuzzy Barsik in Premiere Pro - View the full discussion
If it were me, I wouldn't encode to MJPEG.
So as to encode to ProRes on Windows you can utilise any solution based on ffmpeg/ffmbc or better yet find a Mac with Final Cut or Compressor installed for delivering critical work.
Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/5368019#5368019
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/5368019#5368019
To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/5368019#5368019. In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in Premiere Pro by email or at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

Nvidia CUDA driver update fixes crashes for Premiere Pro and other applications

We are seeing reports that the CUDA 5.5.47 driver update released today addresses the crashing problems introduced by the CUDA 5.5.43 driver update in Premiere Pro and other applications. So, if you have an Nvidia GPU, please update your drivers to use the most recent version of the CUDA driver.
Thanks!

It should be added that only Macs and Quadros need the CUDA driver. That is not required for use with GeForce cards on Windows.

Premiere Pro and Audition workflow problem (urgent!!!)

Similar Messages

Maybe you are looking for