Red r3d 3k fails on CUDA export Media encoder CC

Been having some problems with Red 3k.
Several times recently for some low budget stuff I have shot 3k and put it in a 720P timeline.
All of my 3k material will fail under media encoder CUDA export.....it works under software but a 20 minute CUDA encode is 7 hours with 3k in software encoding
4k 5k all work fine no problems.....just the 3k stuff. And this has been the case over several shoots for months.
It is also the same with 1080p sequences and at any frame rate, and it also fails from PPRO direct export (not queued)
Thanks
Win 8 64 core i7 6core 980 24GB ram, 2x GTX 470 1X GTX 590 SSD's

Yes, AME queue is a problem. I have a 28 minute weekly broadcast for a client that must be encoded in 6 different formats for TV Broadcast, mpeg2 DVD, vimeo, mp3, h.264 for vimeo, etc. If I attempt to encode all 6 in the queue I will have some success and also failure. If I queue several videos that all require mpeg2 (though with each requiring several different specs, i.e., upper field vs. lower field, mpeg2 dvd, mpeg2 HD, etc.) it will complete the task. Yet if I add h.264 to the mix all encodes will fail. I can encode h.264 by itself with no problems. So yes, you are not alone. Not sure what the solution is. In CS6 one could queue all of these formats and walk away. Can Adobe acknowledge these issues and then propose a solution?

Similar Messages

Long Projects exported Media Encoder 5.0.1 fail to finish

Exporting 90 minute P2 AVC-INTRA 100 sequence or a 90 Motion JPEG sequence fails to finish. Both exports fail around 50%. Media Encoder 5.0.1 fails to finish. This is reminicent of PP 2 and CS3 days when long sequences would not finish. In this case I ended up breaking up the sequence into two parts and the exports complete. Suspect that media encoder 5.0.1 over time generates error that there is not enough disk space when there actually is. Media Encoder indicates error compiling movie. Maybe not refreshing itself during the export process. Developers need to fix this asap. Memory management may also be an issue with this problem.
If anyone is having this same exporting problem suggest you break up project into chunks for now until this is fixed by Adobe.
Cannot finish long projects with this bug not being fixed.

Have not tried that. System configuration guys I talk to on a regular basis have told me that because Media Encoder is caching the project in memory that the appropriate way to to run and export via Media Encoder, when exporting your project, is to queue the export to Media Encoder from Premiere then start the encode in Media Encoder first then close Premiere CS5. Something to do with the way they link or something. However the problem I am having is exporting a long project (90 minutes). Adobe had an issue a few versions back with this same issue of exporting a large project. I suspect it has to do with the app no rechecking it's own processes or some piece of code that is stopping the export after a certain time or certain size when it should not. Reported the bug to adobe and I hope they fix it asap. I could be wrong as I am using a GTX 480 card and because mercury playback is not officially supported I could be having issues related to the card. However, until I hear someone exporting a 90 minute or 2 hour movie in AVC-INTRA 100 or motion jpeg or Cineform without a problem I am pretty sure this is a bug.

Simple sequence, export media encoder launches,then nothing.

Simple sequence, export media encoder launches,then nothing. How can I trouble shoot this. I have no idea why this is failing. I have tried a number of options etc. I am using CS4 on vista.

Harm, I followed your advice. I am new to this forum and should have looked at the wiki about the 16 questions. Once I did I noticed that the first item was remove Beta software. I had beta software for Flash Builder and Flash Catalyst that had also installed (without me noticing) media encoder CS5.
Once I removed these Beta releases, the Media Encoder went back to CS4.
Thanks for your response.

Red frames popping up after upgrade to media encoder cc

I'm having some issues with Media Encoder CC. My workflow is AMA SxS card (footage is in XDCAM HD 1080/50i) into Avid Media Composer 6, edit, and export as XDCAM HD 1080/50i mxf file into a watch folder that Media Encoder picks up and converts to SD mpeg2 (its the way the TV stations want it) that file is then ftp'd using Media Encoder. It used to work fine with Media Encoder CS6, but since I upgraded it keeps giving me red frames (cant read frame errors) usually just before or after there is a cut in the footage. I've resorted to transcoding the footage in Avid to DNxHD 120 after editing and that seems to resolve the issue, but it's just an extra step that adds loads of time to my workflow.
Avid Media Composer 6
Adobe CC
HP EliteBook 8760w
Windows 7 64bit

The whole point is that I dont want to transcode into DNxHD at all, DNxHD is the extra step. The can't read frame errors are also very inconsistent in Media Encoder CC. I might export a file and it gives me a few red frames (can't read frame errors) but if I then take the same file and rename it they sometimes work. I've tried uninstalling and reinstalling but that hasnt helped...

AE projects export Media Encoder = instant meltdown

System
Late 2013 iMac.
3.5 ghz iCore 7, 32 Gigs Ram
NVIDIA GeForce GTX 780M 4096 MB
Adobe CC - All up to date
Red Giant Plugins - latest
ME 7.2.0.43 64 bit
AE 12.2.1.5
From AE, send a simple Comp to Media encoder
Boom....Screen Flashes to black - mac has to be hard restarted.
There is no 3.
I have cleared ME prefrences.
Check Permission on Adobe Prefs Folder
This happens very time
Adobe. Please help.
Anyone else confrm this?
Thank you

There was a Red Giant bug in the Magic Bullet suite that caused problems with AME. Make sure you've fixed that.
Try a simple comp that is just a solid layer with no effects or animation and nothing else in the composition. If that works then give us all the details on your comp or try eliminating one effect at a time until you find the problem.

Memory & Export & Media Encoder

Problem 1:
Is there in CS4 a way to export a standard DV AVI file (standard DV 4:3 source material) without having to use Media Encoder? In older versions of Premiere (CS2 for example) all I had to do was "Export to Movie" which created an AVI file. Now, I use "Export to Media", Media Encoder opens and has to load the whole darn project, then "encode" my timeline .. this take a LOT LONGER than I want.
Because I'm new to CS4, am I missing something?
Problem 2:
After I work in CS4 Premiere for a while (about 2 -3 hours), I get a warning that "Adobe Premiere is Low on Memory. Please save your project and proceed with caution." ... What's that all about? I have to close the project and reopen to 'flush' the mem?
TIA,
jd

1. No.
2. It looks like either PPro or a third-party plug-in is leaking memory.
Please provide these details to help us help you.
Cheers
Eddie

Changing Frame Padding On Image Sequence Exports, Media Encoder

Hello Adobe World,
I am using dynamic link from After Effects to Media Encoder and I am trying to export an image sequence with a specific numbering system for input into software code. Is there any way to change the frame padding or change the numbering system for Image sequence exports?
We are trying to speed up our workflow by Batch rendering from AME. AE does let us set our frame numbering and gives us an option for creating sub-folders (it's surprising the AE is much more organized in it's export options that AME). We need to be able to render more than one thing at a time and need to keep working in AE while the files are rendering. I have not found a workable background rendering plug-in for CC14. We could use AME if there is a way to fix the Number system. We are working on a PC Windows 8. I can provide more system specs if it is necessary.
Side note: in AE we can use [#] to set the numbering value and in AME it does not work.
Thank you for your help!
Still looking for an answer on this.... it's been 2 months.... Adobe team? Anyone?

Change it to this?

Premiere Pro CC 2014 remove my video layers from sequence after export Media Encoder.

Every time I send the seq to Media Encoder, Premiere Pro hides my video layers and leaves only the audio layers. When I restart the project the workspace is messed up and I have to reset it. Do you guys know what is going on ?

Yes known issue.
Make a new project and drop this one into it.
See if that will help

CS4 Premiere Export Media - Encoder

Hallo,
could anybody help me whats wrong wiht my settings. Im exporting the video, but the exported video is shrinked/cropped whatever, i.e. its shown only as a mini-window of the displayed player window size... i.e. How do I get rid of the thick black frame of the exported video image ?

Thank you. I think I found the problem. At the beginning I had just chosen the wrong sequence Preset (where for example frame size, audio sampling are completely different than th source).
I solved this, just by opening a new sequence with the right preset. I already had the movie cut, so I copy&pasted the video cuts into the oter sequence.

Premiere Pro CS5 fails to export to Media Encoder CS5

Hello all,
I'm working with Adobe Premiere Pro CS5 Version 5.0.3 on two 64 bit Windows 7 computer systems (laptop and desktop). On my laptop everything works fine and has for some time. We recently installed CS5 on this desktop (new computer). Using the same settings that I use on my laptop, I can encode video by going to File->Export->Media and selecting Export. However, if I chose to Queue the media into Adobe Media Encoder version 5.0.1 it fails to work. Media Encoder opens properly, and the progress bar for exporting the media goes to 100% and disappears like it should. At that point no file appears in the queue. Any help as to what is happening? I'm not receving any error messages that could give me a hint...
Thanks!

Hi Bill,
Thanks for the response. Due to the intermittent nature of this problem I wanted to test more thorougly and can confirm that the files are PCM at 44.1Khz. The error message is, "The file format is not supported", and IIRC the files opened fine in Flash (which will be explained later). Audacity successfully opens the files.
I have resolved the issue and discovered exactly where the 'fault' lies.
Adobe determines the file type by it's filename - rather than using methods in Cocoa library or by looking at the RIFF header. My files are titled, "yyyy.mm.ddName" (Reason/Record does not automatically add the extension in this case), however some files were titled "yyyy-mm-ddName.aif". The former (with periods) would result in the filename extension being truncated from the file's name, but the file 'Kind' is still identified as an "Aif C Audio".
On OSX, any file with an unknown extension should also have it's file type checked using the Cocoa Library since the OS does keep record of the file type that can (and should) be used by applications.
A fix to this in the code is that under OSX, the Cocoa Library file methods should also consult the file type - given that many programs on OSX may happily save without explicitly using an extension in the file name.\
Flash (which didn't yield this problem) may have additional code to ascertain the filetype by seeing if it recognizes the data (given that Flash interracts with streammed data that would not have a file extension).

Media encoder freezes after 4.2 update installation

Hey guys,
I´m in a middle of a huge project and I updated premiere and media encoder to a new 4.2 version. After that I can´t get anything out of premiere cause every time I try to export media encoder totally freezes after couple of seconds after I´ve pushed start queue. I can´t do nothing but to force to quit. It happens while it is still loading the project and haven´t started to encode yet. What´s the problem here?
I´m on mac pro 8-core and cs4 master collection

How long did you wait before force quitting? If it was only a minute or two, try longer.
If that doesn't work, then remove all of the old queue items from the AME.
Then save your Pr project, and clean the media cache database from Edit | Preferences.
Reboot and try again.
If all of that fails, then trash your Pr and AME preferences and try again.
-Jeff

Adobe media encoder in acrobat proXI

I learned from tutorial video file of adobe that adobe media encoder is automatically installed when installing acrobat proXI.
So I tried to find out this software in my computer. but failed.
Is adobe media encoder included in acrobat pro XI as package ?
If yes, could you explain how to install adobe media encoder from installing CD ?
If not included, could I download from adobe home page at free ?
If yes, which version could I download for window 8.1 ?
Thanks

Pull the Matrox out. Try with a standard project and likely your problems are solved.
Matrox cards are best used in a fashion they were designed for, as a doorstopper.

Urgent : Plantage constant de Media encoder, premiere pro CC et CC2014.

Bonjour à tous !
Je rencontre de grosses difficultés avec Premier Pro et média encoder CC et CC2014.
Lorsque je veux mettre en fil d’attente mes projets que je passe par Fichier>Importer (composition After ou même Première) ou que je fasse simplement un glisser/déplacer dans Media Encoder....Une fois sur deux ça plante, ne chargeant pas Dynamique link, ou plantage de première pro..... Avec les versions CC comme 2014....Je n'ai pas de message d'erreur particulier. En revanche je suis obligé de killer les processus Dynamique link, adobe (en général : Qt32 server, Adobe ipCbrocker, PProHeadless.exe) via le gestionnaire de tache Windows. Sinon impossible de réouvrir les logiciels.
J'ai d'ailleurs remarqué que même lorsque les logiciels ne plantent pas, que je ferme premiere ou afx ou autre, les logiciels ne s’enlèvent pas des Processus, il reste ad vitam aeternam, dans les processus actif.
Lorsque j'arrive quand même à importer mes séquences dans MediaEncoder, celui-ci plante certains encodages mais pas tous....sans raison particulière et ne me disant pas pourquoi il les a planté. S’il ne les plante pas, il tourne en boucle sur la même image et je suis obligé d’arrêter moi-même l'encodage, qui ne se finira jamais. Sachant que tous mes fichiers font parties d'une série, qu'il y a donc exactement la même choses dedans en terme de montage, effet etc. Ce qui en passant n'est que du fondu....
Mes Rush sont des fichiers MXF. Et j'utilise le dynamique Link pour mes imports de séquences entre première et afx. Bien que ça me fasse exactement le même problème que j'importe directement mon première ou que je passe par dynamique Link.
Aussi, autre problème lorsqu'il accepte d'exporter (Media encoder j'entend). Il ne m'exporte pas forcement tous le son, il va m'exporter la première séquence par exemple l'intro, puis tous le reste de la vidéo qui est dans une autre séquence et compo, il ne l'exporte pas........
Je ne sais plus quoi faire la. Au prix ou est vendu cette suite franchement !
Je suis donc sur :
Windos Seven PRo 64Bits.
J'ai un i7 X980 3.33GHZ
Une Nvidia GTX480 driver 337.88 (les derniers quoi)
ET 16 Go de RAm
Mon cache n'est pas plein, je le vide régulièrement. Il est sur un disque au regard des projets, et ne bouge jamais.
Voilà, si jamais quelqu'un a le même problème, ou connait une solution, je suis preneur.
Ça tombe au plus mauvais moment, j'ai 200 vidéos à encoder pour dans 1 Mois.
Merci d'avance.
A.H
Message was edited by: aurel motiond

Il ne sert pas à grand chose ce forum, sans vouloir être offensant....

Exporting widescreen DV project to Media Encoder Fails

This is my first attempt at exporting a video using CS4's media encoder, and when I try, the encoder app seems to not be able to "find" or load the Premiere CS4 sequence. It seems to fail after a few minutes, during which the status of the job is "Waiting" and at the bottom it says "Loading xxxxx.prproj".
Any thoughts? I'm on an i5 iMac with the CS4 Production suite installed.
Here's the error it gives:
- Source File: /Users/user/Library/Caches/TemporaryItems/Wedding.prproj
- Output File: /Users/user/Video/Projects/Wedding/DVD/_Wedding.mpg
- Preset Used: Export Widescreen DVD 7Mbps CBR
- Video:
- Audio:
- Bitrate:
- Encoding Time: 00:12:19
Sun Dec 20 15:56:11 2009 : Encoding Failed
Could not read from the source. Please check if it has moved or been deleted.

FIXED!
Thanks to some points in this thread, I have solved my problem.
It was the KNOLL LIGHT FACTORY plug-in. I removed it, and the Adobe Media Encoder now works on my system. I assume that DYNAMIC LINKING between the CS4 apps also now works, but have yet to test that.
This also explains why my CS4 suite works on my MacBook Pro; I never installed KLF on my laptop.
Now I need to tell RED GIANT SOFTWARE about this problem, and either get a solution from them, or a refund.
Thanks. You can add this solution to your collective repertoires in case a future OSX user encounters this exact problem.

Why does Adobe Media Encoder fail to export Quicktime Files?

I'm using Adobe Media Encoder CC 2014 on a Windows 7 Pro 64 bit PC.
While exporting the Quicktime variant of H.264 for ATSC television broadcast files, Adobe Media Encoder fails. Non-Quicktime H.264's render correctly, but some television stations require quicktime.
Troubleshooting reveals the problem only occurs when attempting to make a 1920x1080 H.264 QuickTime file.
Using the same original file (1920x1080), Adobe Media Encoder WILL export a 720x480/486 H.264 MOV file.
More interesting still, it will ALSO export at 1280x720.
Testing this information to it's limits, I found that the cutoff for a successful render is between a frame size of 1610x906 and 1609x905.
Useless, random sizes, I know... but that's the breaking point for Adobe Media Encoder CS6 (6.0.3.1 to be precise) and H.264 Quicktime files.
Others are having a similar problem:
http://forums.creativecow.net/thread/3/934721#953485
This information did not correct the problem:
http://helpx.adobe.com/premiere-pro/kb/error-compiling-movie-warning-or.html
Any help or ideas are greatly appreciated.
OS: Windows 7 Professional 64-bit SP1
CPU: 41.6GHz (dual octo-core Intel Xeon E5-2670 @ 2.60GHz)
RAM: 64GB
GPU: NVIDIA Quadro 5000 v334.95 (2.5Gb GDDR5 RAM)
VID: Blackmagic Design DeckLink HD Extreme 3D+/Desktop Video v10.1.1
DRV: Facilis TerraBlock 16TB RAID/ATTO ExpressSAS R680 v2.19
NLE: Adobe Premiere Pro CC 2014
James Brady
Senior Editor
Results Video, Inc.
El Paso, Texas
http://www.resultsvideo.com

I'm trying to make a file with the extension ".MOV" using AME's "HD 1080i 29.97, H.264, AAC 48kHz" preset. AME fails every time with the following message:
"Encoding Failed
Export Error
Error compiling movie.
Unknown error."
Any other file extension (MP4, M4V, etc.) renders fine. The issue seems only to happen when attempting to make an MOV file. It doesn't seem to matter whether I use AME's built-in preset, or customize my own render settings--the problem always happens with any MOV larger than the size I mentioned above.
All of this used to work just fine on the same machine 2 years back with Adobe CS5, previous version of windows and QuicTime. I've been all through the Adobe and Windows possibilities, so I'm grabbing at straws here with QuickTime maybe having something to do with it.
Interesting.
Would you happen to know if Adobe has made any changes to its manner of muxing long-address MPEG-4 AVC data to the MOV file container? Since the MP4 and M4V files encode properly, have you tried opening these files in a media player and simply using the "Save As..." option to move the date to an MOV file container without transcoding audio or video data? I.e., is there any obvious relationship between the size of the MOV file encode (less than/greater than 4 GB) as a function of the resolution "break point" previously discovered?

Red r3d 3k fails on CUDA export Media encoder CC

Similar Messages

Maybe you are looking for