Encoding Menus - without re-encoding imported (and already encoded) mpegs

I uncerstand that its best to encode Video with Compressor and Audio with A-Pack - but once you've done that and imported the resultant .mv2 and .aac into DVDSP, its now time to compile the menus, buttons - basically the entire disc.
Well doesn't that then force DVDSP to re-encode all those already-encoded video and audio tracks?
I mean I don't get it, how can you compile/build the disc without hurting your Compressor-encoded files?
Or do you just skip the "build" and go directly to "format"?
MacBook 1 gig RAM Mac OS X (10.4.9)

Ok, not that I doubt you, but, well, how do I know
that???
Take a look at PG 230 regarding the menu issue, also
take a look at page 66 for some info.
Unfortunately, I'm on the road and don't have any of my manuals handy. Just my macbook and a 500gig hard drive.
Either way, I think I figured this whole thing out. I made a new folder, created a totally new project, encoded all my video files with Compressor and the audio with A.PACK and put everything in that new folder. Then I set-up the menus, buttons, links - everything - and did a "build" - Its very clear that DVDSP didn't touch any of the encoded files. I saw that an "mpeg" folder was created inside the new folder I had just created - but that's because of one of the template motion-menus I used in the project. Everything else stayed as is.
So, this proves beyond any doubt that building/muxing doesn't harm or re-encode previously encoded assets.
If the video is long,
or you made complicated menus or are using
transitions (which are encoded/made by DVD SP) then
things can take a good chunk of time.
I didn't know transitions slowed things down - but this totally makes sense.
as an aside, are you running the Universal Binary of
DVD SP?
Oh - I'm running version 3 of DVDSP - not up to version 4 yet - and I'm running it on a brand-new black macbook... I think this combination might be causing some problems.
Either way, things are looking pretty good right now. I haven't burned a DVD yet - which is the final test obviously - and that's coming next - but things are looking good so far. I'll know the bottom line to all this very shortly and will let you know how it went.
In the meantime, thanks a lot! I very much appreciate your assistance.
I'll probably have a Compressor question next
I'm not crazy about the quality of the image that I got by encoding with Compressor. DVDSP did it better - but that's a whole other thing - are you able to answer Q's on Compressor?

Similar Messages

I have been using CS6 for two years without incident. Suddenly the Media Encoder stops working, showing APPCRASH and displaying error message about WatchFolder.dll - I tried uninstalling and re-installing to no avail - can anyone help

I have been using CS6 for two years without incident. Suddenly the Media Encoder stops working, showing APPCRASH and displaying error message about WatchFolder.dll - I tried uninstalling and re-installing to no avail - can anyone help?

Hi Mylenium,
Thanks for your response.
Here is the error information showing up:
Problem signature:
Problem Event Name: APPCRASH
Application Name: Adobe Media Encoder.exe
Application Version: 6.0.0.382
Application Timestamp: 4f62fcf1
Fault Module Name: WatchFolder.dll
Fault Module Version: 6.0.0.382
Fault Module Timestamp: 4f62f37f
Exception Code: c0000005
Exception Offset: 0000000000007899
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 4105
Additional Information 1: 9a62
Additional Information 2: 9a620826d8ae4a2fa8b984b39290a503
Additional Information 3: 1fb3
Additional Information 4: 1fb304eee594288faeefbf1271b70d37
I am using a PC Windows 7

Premiere and Media Encoder will will no longer export my edit to any file format.

This is on a Windows 8.1 PC.
The edit exported fine until I made one big mistake.
I created a Nested Edit to make a quick alteration.
Since then the following is now the case and I cannot go back to an earlier edit to fix this.
Premiere and Media Encoder will will no longer export my edit to any file format. Using either the Export Option or Media Encoder. Get a dialog that says "Unknown Error Compiling Movie"
There is nothing wrong with my footage. This edit worked fine and I export through Media Encoder many times until I made a Nested Edit within the Premiere Project.
I have tried all sorts of searches on the net for a fix to this but nothing seems to be current or indeed works.
Any help would be appreciated as this is a show stopper.

Thanks for the reply Mark, appreciated.
I have found a work around but it still leaves a long term issue for Adobe to fix.
As to your first solution:
1). The nested edit is already in its own timeline panel. It will not export or encode via media encoder. This is the problem.
2). I will try the KEM roll feature but I have a work around see following.
3). No I do not have a nested edit within a nested edit.
I did a lot of research on the net on this issue as it happened to a colleague of mine on his machine about two weeks ago. It took me six hours to get a fix and in his case there were six video clip that had read errors. When I overwrote those clips from the original backup master it fixed the problem. However I was never able to use Media Encoder again to export his project without it failing. I could only use the Export feature. Again he had used a nested edit in his project.
I my case I do not have any nested edits within a nested edit. All I did was drag my main edit onto the New Sequence icon at the bottom of the Project Bin. This of course created a nested edit in a new Timeline Panel which is what I wanted. I then slid the entire nested edit to the right in the timeline by two seconds as all a wanted to do was add two seconds of black at the head of the edit. That was it. From that point of creating the nested edit Media Encoder and the Export option failed every time with the fore mentioned error.
The final work around was one of those I found previous mention of during my research. I created a new clean Premiere Pro CC 2014 project, I then used the import option under the file menu. I imported only the original main edit which brought in that edit along with all the required footage. This would then export to disk using the Export feature. However, Media Encoder will still not encode this new edit, it fails the same way every time, 'Unknown Error Compiling Movie'.
As a test I loaded the old corrupt edit project back up and deleted the nested edit sequence completely and re-saved it. This had no effect and did not fix the problem. This particular project file will no longer export directly or via media encoder at all no matter what I do.
This seems pretty serious to me. I worked on this edit for a whole month without issue, encoding out roughs as a went without any issue, it was only yesterday after I made the nested edit that the project file is now useless as it will not encode out at all. Yes I have a work around and was able to salvage my project and get it rendered in time for my deadline but the fact I have a partially working Project that Media Encoder will not touch does not instill me with confidence for long term use of Premiere Pro if this is going to happen again.
Is there some place I can send this project file to Adobe to see if they can find out what is wrong with it? I am not the only person having this issue I have seen other post going all the way back through CS6 it seems.

Quicktime and media encoder problem

I am trying to make a quicktime movie with Premiere CS4. The project is 870 still frames rendered from 3DS MAX. Everything works fine when I export and it sends the movie to Media Encoder's Queue. When I hit "Start Queue". the project starts to encode then quickly finishes with a green check mark next to the project, however no video is made. Please note I have tried other file formats such as AVI and it works fine. This seems to be am issue with QT. I have tried just about every QT codec as well and nothing seems to work. The codec I normally use is animation.
I have successfully done this many times in the past with no problems. Unfortunately, I recently had to replace my main harddrive which died that stored Windows XP, therefore I had to re-install Adobe Master Collection CS4. After the reinstall media encoder won't make Quicktime movies anymore. And yes I have QT installed. I had ver 7.6.2. I read somewhere that 7.5.5 works better with premiere CS4 so I found that, uninstalled 7.6.2, and installed 7.5.5, however, unfornuately it did not fix the problem. Anyone know how to fix this or having the same issues? Please see my specs below. Please let me know if you need more info. Thanks for help in advance.
Intel Quad processor
4 GIG Ram
Nvidia 8800 GTX video card
OS: Windows XP SP3
Adobe Premiere CS4
Media Encoder 4.1.0
Quicktime 7.5.5 (also tried 7.6.2 - the most recent)

There was someone having a similar problem on the www.weddingvideodoneright.com forums,and others were having various issues with ME not creating files and so I've copied this from that thread and hope it helps. Also, check out the Adobe link at the bottom-
Re: Another miserable issue with Premiere 'Pro' CS4 Any advice?
« Reply #11 on: June 04, 2009, 12:46:49 PM »
Quote Modify Remove Split Topic
Digging further, this is the "official" solution from adobe -
Quote
Do one or both of the following solutions:
Solution 1: Create a shortcut to the Premiere Pro executable file, rename the shortcut to Premiere, and move the shortcut to C:\Program Files\Common Files\Adobe\dynamiclink.
Close all Adobe applications.
In Windows Explorer, navigate to C:\Program Files\Adobe\Adobe Premiere Pro CS4. (If you installed Premiere Pro CS4 in a location other than the default of C:\Program Files\Adobe, then navigate to your custom installation location.)
Right-click on Adobe Premiere Pro.exe (which might appear without the .exe extension) and choose Create Shortcut.
Rename the newly created shortcut to just Premiere.
Important: The name of the shortcut must be exactly Premiere with no other characters.
Open a second Windows Explorer window, and navigate to C:\Program Files\Common Files\Adobe\dynamiclink.
Move the Premiere shortcut that you created into the dynamiclink folder.
Solution 2: Remove and reinstall all Premiere Pro CS4 components or all Adobe Creative Suite 4 components.
Do one of the following:
Windows XP: Choose Start > Control Panel > Add or Remove Programs.
Windows Vista: Choose Start > Control Panel > Programs and Features.
In the list of installed programs, select Adobe Premiere Pro CS4, Adobe Creative Suite 4 Production Premium, or Adobe Creative Suite 4 Master Collection.
Click Change/Remove (Windows XP) or Uninstall (Windows Vista).
Follow the on-screen instructions to remove all components of Premiere Pro CS4 (including Adobe Encore CS4 and Adobe OnLocation CS4) or to remove all components of your edition of Adobe Creative Suite 4.
Re-install your Adobe software.
The url is: http://kb2.adobe.com/cps/407/kb407106.html

Very slow Export to Media Encoder and Media Encoder connecting to dynamic link server

My flow is this: Open After Effects CC, import an image sequence, go to File > Export > Add to Adobe Media Encoder Queue...
Every other time i do this it will take 2-3 mins before Media Encoder even shows the splash screen, then it'll take another 1-2 mins to open.
Next, I'll select my custom preset over on the right side of the window, then hit the Play button to begin encoding. Sometimes nothing will happen at all, sometimes I'll see the Orange stripped bar on the lower left and the message Media Encoder connecting to dynamic link server and that'll last 5+ minutes and I end task to get out of AE and ME. Sometimes, ME will begin encoding right away and zip through the small animation sequence quickly without issue.
I have WIndows 7 Pro, I'm on a work network with access to the internet and AE has been updated 24 days ago. I have a subscription and I'm signed on. However, sometimes I do not have the Creative-Cloud icon in my systray.
Thanks,

Thanks. I have 16GB Ram, 64bit Win7, Intel(R) Core(TM) i7-3970X @ 3.50GHz 3.50GHz. AE is set to have maximum disk cache of 46GB. RAM reserved for other applications: 5GB RAM available for AE, PR, Pl, (some triangular icon [edit] which is ME ), Ps: 10GB. nothing else checked on that screen.
Typically just a mail client, 1 or 2 sessions of Firefox, 1 or 2 network folders open when i launch AE.
The last couple of times specifically, i had a 450 frame animation sequence at native 720p. then i added a curves layer on top of it in AE, then added two ~600x300px logos, one in each lower corner, then added a new solid layer which i used as a vignette. Finally over that i added a 720p still image which i held for another 15 seconds beyond the animation.
For the above, i ended-task, rebooted, brought it up again and it lauched ME quickly, then i got the stripped bar and connecting message until i ended task on that, then the 3rd time was the charm - everything opened quickly and it began to encode quickly.
The next three uses late afternoon yesterday were 150 frame animations at 480x270 and they all seemed to work fine. I created the sequence in 3ds max, then closed and went into AE. Then I'd close AE render another sequence, back into AE etc...

Premire Pro CC 2014 and Media Encoder Crash During Launch

Premire Pro and Media Encoder crash during startup and are unusable. I am using Windows 7 Ultimate and already tried reinstalling Adobe Creative Cloud from scratch and it's still happening. I also tried following Adobes KB articles directions to rename the Adobe folder in my documents and appdata to no avail. When I try to launch either application, I get a generic windows crash message "Adobe Premire Pro CC 2014.0 has stopped working" and when I click problem details, it lists this:
Problem signature:
Problem Event Name: APPCRASH
Application Name: Adobe Premiere Pro.exe
Application Version: 8.0.0.169
Application Timestamp: 536f4f89
Fault Module Name: ImageRenderer.dll
Fault Module Version: 8.0.0.169
Fault Module Timestamp: 536f2c18
Exception Code: c000001d
Exception Offset: 00000000001f5382
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
Additional Information 1: 0b2d
Additional Information 2: 0b2df4702c3fc6489bf922fb8e966350
Additional Information 3: fa9f
Additional Information 4: fa9f59f642d335ee71c6667e52000d39

I am having a similar problem.
Premiere Pro CC 2014 suddenly decided to crash every time I export to either Adobe Media Encoder or within Premiere itself.
The encode will usually go for 5-10 minutes before the programs either spits out a "serious error has occurred" window, or it just sits there frozen until I force quit.
I did find a work-around for the moment. If I open AME and FILE > OPEN, select my project and then the sequence I want, AND put it in Software render mode, it will work.
My timeline is 2K, 58 minutes in 23.976
Only effects applied are Lumetri LUTs - no third party.
I've exported as recently as a week ago without issue.
Running OSX 9.5 on an X99 board
3.75 GHz 8-core
64GB 2400 MHz RAM
EVGA Titan Black 6GB
Because I can get my renders out, I am not too concerned. Either there is something wonky with my timeline that screws with any graphics enabled rendering, or there is a bug that is have the same effect. I will try rendering on another of my edit bays that utilizes a GTX 580 that I KNOW works. The Titan is pretty new to my workflow.
Thanks Adobe, for checking this out.

Add blurary job action to files already encoded

Hi,
If I have already encoded h264 and ac3 files using bluray presets from a prores master, but I did not use the "create blurary disc job action". Is it possible to add the job action to the 2 files I already created without having to re-encode again?
How do I link the 2 files together in the batch?
I am using Compressor 4.
Thanks

Hi alexgrainger (UK) & Russ H (Boston)
Permit me to join this thread even though it is six months old and has been previously “solved”. I can’t seem to find anything close to my problem in the Apple Forum, (Compressor Community or any other)
I’d like to ask you guys how you used the Compressor job pane to link an AC.3 file and an H.264 file in the Job pane, and eventually achieve BluRay burning.
It seems as though you guys were successful and I would appreciate even a little help.
First of all, I am using Final Cut Studio 2 (FCP 7.0.2, Compressor 3.5.4, Soundtrack 3.0.1) on an Intel iMac with OS 10.6.3, and want to burn the 1920x1080 video and six channel audio from an AVCHD camcorder to BluRay.
(Maybe what I want to do can’t be done with the software I have?)
I have set up the H.264 video file (no audio) using an export from QT Conversion. I have set up a separate AC3 audio file containing six channels corresponding to the same video using Apack.
I can burn a BluRay disc of the AC3 file with no video. On playback through my Panasonic BluRay player and Yamaha Amp, the amp display indicator shows the Dolby Digital six icons, and is further confirmed with audio from all six speakers.
And I can burn a separate BluRay of the H264 file if it contains 2Ch Stereo signals.
Now, How do I get BOTH of these files (AC3 & H264 no audio) into a Compressor job pane at the same time.
I can drag one or the other of these two files to the thumbnail (area containing a down arrow), but not both at the same time. A Note in the Help Users file: “If you drag multiple files to the thumbnail area, only the last file is added to this job and all other files are ignored.”
The Inspector windows for individual video and audio files seem to be set properly, but when I check the A/V Attributes, for Video or Audio, one or the other seems blank, which confirms in sort the above statement in the Help file.
So, if you will, could you take a moment and describe how you got to a BluRay burn with Compressor, when Compressor job pane contain separate H264 and AC3 files. Is there Compressor template for this combo? Is there a special process to get both of these together?
Obviously, I’m a newbie at Compressor. I would just like to burn to BluRay the beautiful video and surround channels coming out of my new AVCHD camcorder.
Thanks in advance,
BoBo (CT)

Lightroom and GPS encoded JPGs

Can Lightroom (3.6) read GPS data from JPG files?
I've just encoded a batch of assorted JPGs and raw images with HoudahGeo and updated the files in Lightroom by reading the metadata from the files again. As far as I can tell only the raw images are showing GPS data as a result.
I know the date is there because(a) I can see it in HoudahGeo if I look at the files again and (b) Aperture picks up the locations correctly.
Is there anyway to pick these up in Lightroom?

I've used GeoSetter to add GPS data to my scanned TIFF files, as well as to JPG files, and that shows up without any problem in LR, so in principle it should work.
Have you tried creating a copy of one of the scanned JPGs, and importing that as if it were a new photo? Perhaps the reading of the metadata isn't picking up the GPS for some reason.
Marc

Saving image in windows 8.1 using stream and bitmap encoder id

Hi
var renderTargetBitmap = new RenderTargetBitmap();
await renderTargetBitmap.Render(myElementTree);
var pixels = await renderTargetBitmap.GetPixelsAsync();
var picker = new FileSavePicker();
// Picker setup
var file = await picker.PickSaveFileAsync();
// File validation
using (var stream = await file.OpenAsync(FileAccessMode.ReadWrite))
var encoder = await
BitmapEncoder.CreateAsync(BitmapEncoder.BmpEncoderId, stream);
encoder.SetPixelData(BitmapPixelFormat.Rgba8, 100, 0, 96, 96,
await renderTargetBitmap.GetPixelsAsync());
await encoder.FlushAsync();
I have already used the code snippet. Could you please tell me how to save UIElement tree by having the stream and bitmap encoder id as input?
Thanks
Satheesh

Here you go. Set up the file picker and call our CaptureElementToFile function. In this case it's passing the page to capture the whole screen:
FileSavePicker picker = new FileSavePicker();
picker.SuggestedStartLocation = PickerLocationId.PicturesLibrary;
picker.SuggestedFileName = "capture.bmp";
picker.FileTypeChoices.Add("Bitmap File",new List<string>() { ".bmp" });
StorageFile file = await picker.PickSaveFileAsync();
CaptureElementToFile(this, file);
And here's CaptureElementToFile. The BitmapEncoder needs to know information about the size and shape of the pixel buffer and it needs to have the pixels as an Array. If you want to encode to a different size you can include a BitmapTransform.
async void CaptureElementToFile(UIElement element, StorageFile file)
RenderTargetBitmap renderTargetBitmap = new RenderTargetBitmap();
await renderTargetBitmap.RenderAsync(element);
IBuffer pixelBuffer = await renderTargetBitmap.GetPixelsAsync();
DisplayInformation dispInfo = DisplayInformation.GetForCurrentView();
using (var stream = await file.OpenAsync(FileAccessMode.ReadWrite))
var encoder = await BitmapEncoder.CreateAsync(BitmapEncoder.BmpEncoderId, stream);
encoder.SetPixelData(BitmapPixelFormat.Rgba8, BitmapAlphaMode.Straight,
(uint)renderTargetBitmap.PixelWidth,
(uint)renderTargetBitmap.PixelHeight,
dispInfo.LogicalDpi,dispInfo.LogicalDpi,
pixelBuffer.ToArray());
await encoder.FlushAsync();
--Rob

Media Encoder Offline Material (that is present) and constant conforming in each PP CC open.

Hello everyone,
I have a project with several sequence that I have been working for a long time (multicam basically)
Every time I try to render/encode any of the sequence the Media encoder is giving me a:
"Offline material is present in this export and will be encoded using the Offline Media graphic"
And of course thats not useful at all
Exporting the sequence, manually without the media encoder, give me a good result.
I tried with Premiere Pro CC v7.2.2 and CC 2014, and the behavior is the same.
I also tried to offline the media and link it back again, and the issue stays.
All the media is on a local hard drive (not USB/network)
Another weird behavior, is that every time I open this project, the conforming task starts all over again (also in both PP CC versions). I also, attempted the "Save cache close to the source…" setup, but the results is the same. It conforms every time I open the project (I can see the cache files created in the file system)
This conforming takes a lot of time and is a pain in the ***.
Any recommendation on how to troubleshoot this?
I need to create the final videos soon, and doing it manually (without Media Encoder) is insane (probably a week).
Regards,

Hi guys,
As there was no reply here, I tried to open a case with Adobe, but the guy from the support chat had no idea.
I was in there 2 h, and it only asked:
"where do you have all the media files saved?"
"Ok. Are they linked?"
This was actually answered on the initial problem description.
and after the last question, it just to rapidly close the chat session, and leave me with no answer.
Can anyone point me out how should I address this problem?
Whats the best way to get support from adobe (I'm a CC user)
Regards,

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 and Media Encoder - h264 corrupted encode

Hello all
I'm writing here since I simply cannot find a solution to my problem, recently out of a sudden my adobe premiere and Media encoder have been giving me corrupt h264 encodes, the files apparently encode but adobe does not put them in a container. The .m4v file is unplayable and the same goes for the audio file; here is a sample from MediaInfo:
No matter what sequence or project I try to encode with h264 this happens while I can encode to any other extension/codec with no problems. While using the same project file and the same source files on another computer the encodes finishes without a problem. Even a simple timelapse with just JPEG pictures on the timeline results in this problem. I have no idea what to do but I simply cannot encode with anything else so any help is appreciated (P.S. the 4k resolution here is a timelapse, most encodes I try to do are 1080p @ 25fps, since most people bump at this resolution 1st)
I'm running Adobe Premiere Pro CS6 (6.0.5) updated to the latest on Windows 7 64bit.

Hello all
I'm writing here since I simply cannot find a solution to my problem, recently out of a sudden my adobe premiere and Media encoder have been giving me corrupt h264 encodes, the files apparently encode but adobe does not put them in a container. The .m4v file is unplayable and the same goes for the audio file; here is a sample from MediaInfo:
No matter what sequence or project I try to encode with h264 this happens while I can encode to any other extension/codec with no problems. While using the same project file and the same source files on another computer the encodes finishes without a problem. Even a simple timelapse with just JPEG pictures on the timeline results in this problem. I have no idea what to do but I simply cannot encode with anything else so any help is appreciated (P.S. the 4k resolution here is a timelapse, most encodes I try to do are 1080p @ 25fps, since most people bump at this resolution 1st)
I'm running Adobe Premiere Pro CS6 (6.0.5) updated to the latest on Windows 7 64bit.

Premiere Pro CS6 and Media Encoder CS6 Color shift on export

Hello,
I am working on an early 2008 Mac Pro with 2 X 3.2 GHz Quad Core Intel Xeon Processors 32 GB of RAM a NVIDIA GeForce 8800 GT 512 MB Graphics Card and I am running OS X 10.8.2.
I have the updated Version of Adobe Premiere Pro CS6 and Media Encoder CS6 through the awesome Subscription program that Adobe has started.
My footage is shot with the Canon 1D Mark IV shot 1920X1080 at 24 FPS
I am importing the camera files and then exporting them after I cut them up in to Quicktime Pro Res 422 HQ files
With the technical explination out of the way here is my problem. I have color right from the camera files that I like. and with out doing any thing to change the color I export the footage and get a dramatic color shift. The exported file looks desaturated and slightly green.
I have tried using Media Encoder CS6 to export my footage and that has the same result.
I started my career as a photographic retoucher and use photoshop and light room constantly so I am pretty confident that i know color. I also calibrate my Lacie 526 and Lacie 324i montiors monthly as well as have a sensor that will slightly shift the profile depending on the time of day.
I have attached three screen shots that show the color shift exactly. Now what I need is a solution. What I am not seeing is color settings for Premiere. I am totally open to any suggestions on what I might be doing incorrectly.
Ben

Benjamin Peterson wrote:
I started my career as a photographic retoucher and use photoshop and light room constantly so I am pretty confident that i know color. I also calibrate my Lacie 526 and Lacie 324i montiors monthly as well as have a sensor that will slightly shift the profile depending on the time of day.
I've been doing this for a few years now, and have come to some conclusions. Basically, the difference between still photography and video is like the difference between playing the trumpet and the sax. What you bring to the sax from playing trumpet is your ability to read music, what you know about composition, blending while playint with others, ect. But playing trumpet tells you nothing about how to physically play a sax. So it is with still photography and video.
For starters, your carefully calibrated computer monitor is just that, a computer monitor. It doesn't display the correct working space for video. What you need for WYSIWYG in video is a monitor that can show you the Rec.709 working space. Rec.709 has a different gamut, a different gamma, probably a different white point (D65), different phosphor colors, etc., etc., etc. Enought differences that it's difficult to make a computer monitor that can successfully display Rec.709. Yet there are a couple of computer monitors that can do this (a few Eizos, one HP). The vast majority of people doing serious color correction work in video use a production monitor for just this reason.
But a production monitor isn't enough. You also have to make sure that the signals you're sending the production monitor are correct. There's a sub-industry making signal converters for signals from NLE video cards (usually RGB based) -> signals for production monitors (usually YUV based).
That said, it is certainly possible to get a very good match between your NLE suite and a DVD / BD as displayed on an HDTV. But it's not as simple or easy as a calibrtated computer monitor for still photography use.
This is probably part of your problem. But Quicktime is probably the root of it. Quicktime is, well, I guess the polite way of saying it is that Quicktime is problematic. It gives all kinds of problems. Most people have abandoned it. You should too.

How can I get a copy of Premiere and Media Encoder CS6?

I need to be able to convert a video that has an alpha channel into an FLV file for import into Captivate 8. Captivate only works with FLV and MP4, and only FLV has an alpha channel. However, FLV was removed as an option from the CC version of Premiere/Media Encoder.
Supposedly, you can download old versions of the software from the CC desktop app, but I can't. In my CC app, there is no Old Versions option in the Filters, and there is no option to download old versions on the Install buttons, or anywhere else for that matter.
We have the Team version of CC, and our IT dept is switching us over to Enterprise, if that has anything to do with it.
So, is there any way to download and install CS6 versions of Premiere and Media Encoder?

check this thread with the same question about languages!!!
https://forums.adobe.com/message/7437370#7437370
hahahahahahahahahahaha!!!!

Suggestion: Environment and Compiler encoding settings should be merged.

I have found the following issue while trying to migrate projects from older JDev versions to JDev 10.1.3.2:
When the environment encoding setting (Tools > Preferences > Environment) is different from the compiler encoding setting (Tools > Project Properties > Environment) the application does not function properly.
The following simple test case demonstrates the problem:
Set the environment encoding to utf-8. 
Make a simple class with a method returning a string with international characters (e.g. Greek):
public class Class1 { 
public static String test() { 
return "αβγδε"; 
} 
}
Make a jsp page that uses a different encoding (e.g. windows-1253 for Greek) and make the jsp output some "fixed" html with international characters as well as the string returned from the class:
<%@ page contentType="text/html;charset=windows-1253"%> 
<html> 
<head> 
<meta http-equiv="Content-Type" content="text/html; charset=windows-1253"/> 
<title>index</title> 
</head> 
<body> 
 αβγδε 
 <%= Class1.test() %> 
</body> 
</html>
Set the compiler encoding to utf-8 and run the jsp. => The "fixed" string is replaced by spaces.
Set the compiler encoding to windows-1253, rebuild the application and run the jsp. => The returned string from the class is displayed as garbage.
This is caused because the class (.java) file is created and saved as utf-8 (using the environment encoding setting) while the jsp is saved as windows-1253.
So if these two settings must be the same why don't you merge them to just one setting?
My suggestion is that the proposed setting be a project specific setting so that we can build projects using different encodings without having to change the environment encoding each time.
Message was edited by:
parisd

I have found the following issue while trying to migrate projects from older JDev versions to JDev 10.1.3.2:
When the environment encoding setting (Tools > Preferences > Environment) is different from the compiler encoding setting (Tools > Project Properties > Environment) the application does not function properly.
The following simple test case demonstrates the problem:
Set the environment encoding to utf-8. 
Make a simple class with a method returning a string with international characters (e.g. Greek):
public class Class1 { 
public static String test() { 
return "αβγδε"; 
} 
}
Make a jsp page that uses a different encoding (e.g. windows-1253 for Greek) and make the jsp output some "fixed" html with international characters as well as the string returned from the class:
<%@ page contentType="text/html;charset=windows-1253"%> 
<html> 
<head> 
<meta http-equiv="Content-Type" content="text/html; charset=windows-1253"/> 
<title>index</title> 
</head> 
<body> 
 αβγδε 
 <%= Class1.test() %> 
</body> 
</html>
Set the compiler encoding to utf-8 and run the jsp. => The "fixed" string is replaced by spaces.
Set the compiler encoding to windows-1253, rebuild the application and run the jsp. => The returned string from the class is displayed as garbage.
This is caused because the class (.java) file is created and saved as utf-8 (using the environment encoding setting) while the jsp is saved as windows-1253.
So if these two settings must be the same why don't you merge them to just one setting?
My suggestion is that the proposed setting be a project specific setting so that we can build projects using different encodings without having to change the environment encoding each time.
Message was edited by:
parisd

Encoding Menus - without re-encoding imported (and already encoded) mpegs

Similar Messages

Maybe you are looking for