Olympus E-M1 codec

Even though my Olympus E-M1 produces .mov files Premier Elements 12 can not access. Is there a codec to download for this?

viviansviews
What computer operating system is your Premiere Elements 12 running on? And, have you updated from 12 to 12.1 yet?
Be that as it may, your Olympus E-M1 appears to be offering recording using either H.264 or MotionJPEG video compression.
There should be no problems with Premiere Elements with H.264.mov. But, Premiere Elements (any version) can have
problems with the MotionJPEG video compression.
In those instances, the answers include:
a. install a utility that came with the camera in order to have the correct video codec available to the Premiere Elements project
or
b. Download and install a MotionJPEG video codec (popular as been the Morgan MotionJPEG codec.
or
c. Convert the MotionJPEG.mov to another format that will be compatible with Premiere Elements 12.
Two major confirmations from you needed:
a. You have the latest version of QuickTime installed on your computer with Premiere Elements 12.
and
b. That you set the camera to record with the MotionJPEG codec and not the H.264 codec.
Please review and consider and then we can discuss the specifics of your situation further.
Thank you.
ATR

Similar Messages

.AVI File won't play in CS4, Gspot says all Codecs are properly installed

Hello,
I'm trying to edit a video in adobe premier pro from an Olympus XZ-1 (.avi file/mpjeg) but it doesn't play at all.
I tried to find if there where any codecs missing with Gspot, but it says all codecs are in place.
What else can be the problem and how can I solve it?
Thank you very much in advance!
- Lieve

Jason,
Welcome to the forum.
Yes, there is a clearcut answer, with three possible variations.
First, the Nikon should have their version of the MJPEG CODEC on a utility disc. That CODEC might install via the camera's driver, might be a separate install from the disc, or might install as part of a utility (say an editing program) on that disc. Not sure exactly where it will be located, but I feel confident that Nikon will have provided it. That will be the best, as different camera mfgrs. tweak common CODEC's. Even if you do not plan on using an included utility, you might need to install it, just to get the Nikon MJPEG CODEC. I did that for a Canon, and a Panasonic, and got their specific CODEC's, for their AV files.
The two variations would be either the Morgan, or MainConcept MJPEG CODEC, which will be a download and install. The weakness of these CODEC's is that they are more general, and might not reflect a Nikon tweak. That is why I mentioned Nikon's version first. It WILL be as good as it gets.
Good luck, and wish that I knew exactly where the Nikon MJPEG CODEC was located, or what process installed it, but if you find it added, after an installation, I would appreciate if you would update the thread, so that others will then know what to install, to get that CODEC.
Hunt

.avi files and codecs

Hi I posted a question yesterday about .avi and there were some helpful responses. I installed GSpot and it tells me that the CODEC for the video file is MJPG/Motion JPEG, on an Olympus Pen EPL1 digital camera, and there is no CODEC required on the audio file. It then says that the MJPG CODEC is installed on my computer, so why when I import the file into Premiere Elements 9, it plays back in very poor quality?
Regards

Poor playback, when the proper CODEC is installed on one's system is often due to a mis-match between the Source Files, and the Project's Preset. The biggest killer of Quality, is when the Frame Size of the Project does not match the Frame Size of the Source Files, and Scaling is done, with Scale to Default Frame Size checked.
The next most common cause of a lack in quality is the specific CODEC itself. For MJPEG, there are two highly popular CODEC's, Morgan and MainConcept. While there are others, those two are highly recommended by many users. Many cameras, that shoot in MJPEG will also ship with the mfgr's. version of the MJPEG CODEC. As that mfgr. might well have tweaked things a bit, if one does have a utility/driver disc, I would strongly recommend installing their version of MJPEG. This might be installed along wiith the driver for the camera, as part of an editing/organizing program, or maybe as a separate install. It will just depend on the camera, and might even vary, model to model. This ARTICLE will give more background, and also some potentially useful links.
Let's go back to the first paragraph. When you ran your Source Files through G-Spot, what were the Frame Size and PAR (Pixel Aspect Ratio) listed?
How do those figures match up with your Project Preset, chosen with New Project? A mis-match here can have a very negative effect on quality. If one has Scale to Default Frame Size checked, and the Source Footage is smaller, than the Project's Frame Size, the user will not see that the program has Scaled UP the Clip(s) to match. If Scale to Default Frame Size is unchecked, then the user would see black bars around all, or parts of the Frame, with the Clip displayed smaller in the Frame.
While PrE can Scale footage UP, or DOWN, its algorithms are not the best and quality will suffer. A little bit of Scaling might go unnoticed, but if one had, say SD 720 x 480 material, in an HD 1920 x 1080 Project, then quality would go down dramatically.
One thing to consider is that if there is a mis-match, there will be a red line over the Clip(s). This shows that for the best, smoothest playback, that footage needs to be Rendered. One would press Enter to Render that Timeline. The Render could be limited to just a segment of the Timeline by using the WAB (Work Area Bar). This produces proxy files, that will give the best possible playback. This ARTICLE will give more background on Rendering. While the Program Monitor in the program, on a high-rez computer monitor is not the best viewing situation for SD material (an NTSC, or PAL, calibrated CRT monitor is the best, but those are very expensive, and the NLE program needs to support them), one can get fairly close by adjusting the Magnification (Rt-click on the Program Monitor) to 100% from Fit. To see the entire Frame, it might be necessary to adjust the Program Monitor's Panel.
As you can see, there are several things that can affect quality. If you will give us info on your Source Footage, your Project's Preset and also which version of the MJPEG CODEC, someone will be able to direct you.
Good luck, and thanks for the info.
Hunt

DNG converter 6.4 and DNG codec 1.1 for Win7 32 & 64bits released!

The DNG converter 6.4 has been released, http://www.adobe.com/products/dng/ with support for many new cameras, including:
Canon EOS 600D (Rebel T3i / Kiss X5 Digital)
Canon EOS 1100D (Rebel T3 / Kiss X50 Digital)
Fuji FinePix S200 EXR
Fuji FinePix F550 EXR
Fuji FinePix HS20 EXR
Fuji FinePix X100
Hasselblad H4D-40
Kodak EasyShare Z990
Nikon D5100
Olympus E-PL1s
Olympus E-PL2
Olympus XZ-1
Samsung NX11
Note that it is the last version to run on Power PC Macs: http://blogs.adobe.com/lightroomjournal/2011/03/dng-converter-6-4-last-to-support-powerpc- mac-systems.html
Also released today: The DNG codec 1.1 that now supports the 64bits version of Windows 7, but does not support Vista anymore.
http://labs.adobe.com/wiki/index.php/DNG_Codec
Finally, the DNG Profile Editor beta 3 is out too, and has also been updated to address bug fixes and support DNG files utilizing the updated DNG 1.3 Specification.

I just downloaded and installed this version on Windows 7 Home Premium 64bits.
I can report it works great with my Raw DNG files, from camera: Pentax K-m/ K2000.
Probably also with all other Pentax camera's.
Jan (Netherlands)

Importing WMA files from an Olympus Voice Recorder

I am considering the purchase of a digital voice recorder, possibly one of the inexpensive WMA recorders from Olympus.
I would like to be able to import the voice recording files onto my Mac, possibly for editing them in Garage Band. I may make podcasts or other voice-message multi-media projects out of the recordings.
I heard in another forum that the WMA files may be problematic to import onto my Mac. Does anyone know what the issues are? What are the possible fixes? Any freeware that can convert these kinds of files to something useful on the Mac?
A couple of possibilities I'm looking at for handheld voice recorders:
Olympus VN-6200 PC (nice deal on this model on the web)
http://www.olympusamerica.com/cpg_section/product.asp?product=1459
Olympus DS-40 (I found a nice deal on this one as well)
http://www.olympusamerica.com/cpg_section/product.asp?product=1277
Thanks in advance,
--WA

The primary issue is that Mac OS X does not natively support WMA, so you will have to convert the WMA files to another format before they can be played. Possibilities for conversion include EasyWMA or QuickTime Player and the Flip4Mac import codec (not the free version).
I'm not aware of any freeware for Mac that can convert WMA, though I can't say that none exists.

Lightroom 4.0: Troubleshooting Video Codecs? Fix grey thumbnails?

Hello.
I just purchased and installed Lightroom 4.0 - excited that it would be able to help manage my videos as well as pictures.
Everything works fine for some of my videos (from my Canon cameras), but older videos from my Olympus cameras (including an E-620 and SP-560UZ) won't generate thumbnails or play. The thumbnails are grey, and have a warning triangle with the message "Lightroom has encountered problems reading this video".
I am running Windows 7 Ultimate 64-bit, and I have K-Lite CODEC pack and just re-installed the newest version of QuickTime.
The video files that are failing are mostly AVI format, and open correctly in QuickTime Player and Windows Media Player so the necessary CODECS must be installed, but are either not compatible with Lightroom or Lightroom isn't finding them.
The Windows Control Panel and K-Lite CODEC pack both have myriad options for tweaking CODECS, but I don't really know what I'm doing.
Can anyone suggest how to troubleshoot this problem? Either to find more information on what is going wrong, or on how to fix it?
I am very happy to provide more detailed information if that would help.
Thanks in advance for any assistance,
Ian

I am having the same problem. Any ideas on how to fix it?
Thnak in advance,
Daniel

Problems opening and editing Olympus OM-D E-M1 files

Hi,
I have a new Olympus OM-D E-M1 camera. It produces (pretty great) video's of the .MOV format, H.264.
However, I am not able to open, view and edit these files in Premiere Pro CS5.
Some more information:
- Video format .MOV, H.264, 1080p 29.97fps
- Windows 7 machine, 6Gb ram, reasonably fast video card and quad core chip. Editing of other video formats with the same HD specs is no problem (e.g. mp4 or avi)
- Video's play just fine in Quick Time and in the proprietary Olympus Viewer 3 software and in Windows Media player
- Video's will import and I can put them on the timeline but very slowly.
- They usually do not open in the Source monitor, or show just 1 frame
- The sound sometimes plays fragments (as if it is reading the files very slowly)
- It does not play a preview
- I can export a sequence that I put on the timeline, for example to an MP4 which is then fine, but rendering and exporting takes forever, up to hours for 4 mins of film
I am thinking that Premiere Pro somehow does not know where to find the right codecs for importing these videos, because they must be on my computer somewhere with QuickTime and Olympus Viewer. Anyone know how to tell PP how to find/use these?
Please let me know if you need any more information to help me solve this problem.
Thanks, Bastienne

I made a screen dump of the folder in Olympus Viewer that is named Movie.
It has some files which seem to be involved in codec. Please take a look if there is anything useful there .
btw there is only one folder in Movie (AsFilter) and there is also only one folder in AsFilter (MP4), so there is no folder called MOV or similar, strangely enough.
There may be one other interesting .dll file called CodecHelper.dll in the Olympus Viewer 3 root.

Quicktime won't play .mov files recorded on Olympus recorder

I've got an Olympus pocket video recorder. but Quicktime will not play the files recorded on it. I get the error message "The document could not be opened. This media may be damaged."
However, the files play in iTunes if I import them and the preview plays if I select the icon and hit the space bar. But I need to use the Trim facility in Quicktime to do quick trimming on them.
This is the MediaInfo information for one - can anyone shed any light, please?
General
Complete name : /xxxx/xxxx/Desktop/100OLYMP/P3240029.MOV
Format : MPEG-4
Format profile : QuickTime
Codec ID : qt
File size : 296 MiB
Duration : 3mn 3s
Overall bit rate : 13.5 Mbps
Movie name/More : OLYMPUS LINEAR PCM RECORDER
Encoded date : UTC 2014-03-24 11:00:11
Tagged date : UTC 2014-03-24 11:00:11
Origin : Pcm Recorder
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : [email protected]
Format settings, CABAC : No
Format settings, ReFrames : 2 frames
Format settings, GOP : M=1, N=30
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 3mn 3s
Bit rate : 12.0 Mbps
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 29.970 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.193
Stream size : 262 MiB (89%)
Language : English
Encoded date : UTC 2014-03-24 11:00:11
Tagged date : UTC 2014-03-24 11:00:11
Color primaries : BT.601 NTSC
Transfer characteristics : BT.709
Matrix coefficients : BT.601
Audio
ID : 2
Format : PCM
Format settings, Endianness : Little
Format settings, Sign : Signed
Codec ID : sowt
Duration : 3mn 3s
Source duration : 3mn 3s
Bit rate mode : Constant
Bit rate : 1 411.2 Kbps
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 44.1 KHz
Bit depth : 16 bits
Stream size : 30.8 MiB (10%)
Source stream size : 30.8 MiB (10%)
Language : English
Encoded date : UTC 2014-03-24 11:00:11
Tagged date : UTC 2014-03-24 11:00:11

Bump, bump. Please can anybody help?

Olympus TG-1

Hiya ! I just ordered an Olympus TG-1 ( my very first video camera ! ) so I can make underwater vampire movies.
I have CS3 with winXP ( dual core 2.6ghz ) 4gig ram.
mousey computer.
Apparently the camera shoots H264 in mov wrapper.
Apparently this is similar to 5D and 7D ?
With mouse I don't think I can just re-wrap to mp4 for use in CS3.
I think maybe I should use Cineform neoscene and convert to AVI ( h264 )..which uses YUV 420?
I haven't got camera yet, but would like to start thinking of hoops I should be prepared to jump through for HD stuff on CS3.
In the 'export' stage...maybe I should use frameserver ?
Any suggestions would be appreciated. Thanks !
( batting eyelashes in a flirtatious manner )

OK...got camera today. Got sound recording thing too, but haven't even looked at THAT yet...
far as camera goes, its sorta amazing how things have advanced since the canon powershot s10 that was about 2 MP and cost me about $800.
It makes me feel good that I managed to sink so much money into tooling up this revolution.
Anyway, this thing shoots HD ( mov h264) and I shot a few secs of a test.
Then did what I could to get it into cs3 with mouse computer. used cineform to make avi ( still HD at that point ).
Didnt see that much of a difference really cause I had to render the AVI to get a green bar every time I did something ( levels etc ).
But it might work OK...just would take time I guess. I also tried jumping through hoops to downscale to ntsc 16:9...so I could IMPORT THAT to cs3 instead...but that turned into a can of worms and nothing so far has been a happy experience.
I spent the last 5 hours dealing with that 'conversion' stuff ( tried digital media converer, tempgenc and streamclip, virtualdub...whatever permutations I could think of )... and now realize I have to start over again with a clear head...
It's a good thing this camera is shock proof and I wish my computer was too, cause it wouldn't take much for me to throw both the camera and the computer into the nearby Lake with rocks tied to them.....
Just kidding... but I have to start over more methodically now to deal with it.
I'd LOVE to downscale it first...from the mov h264....to 16:9 ntsc 2997 in any codec that works good in cs3... and THEN get into editing.
I will NEVER burn blue ray with this stuff. only dvd....
anyone with advice re: how that can happen is cool with me.
One problem for me, is that I DID downscale using QT ( export from QT pro )...and when back into CS3 , or playing on computer monitor...that stuff looked horrid...
But I know from past experience, EVERYTHING interlaced on computer monitors ( ntsc, pal ) looks horrid...and I can't burn DVD's every half hour just to see how it looks on EXPORT...cause I'm not even close to EXPORT ...yet...
what a pain in the *** ....
No wonder you guys are "experts" at this stuff....dealing with a gazillion cameras and codecs and permutations...You deserve a nice fruit cake or something for all your helping in the forums... really !

Fehlender Codec

Ich habe die Testversion Premiere Elements 12 installiert, kann aber meine mit der Olympus OM-D E-M5 aufgenommenen Videofilme im .AVI (Motion JPEG) oder im .MOV (MPEG-4AVC/H.264) nicht zum Bearbeiten laden, da mir der erforderliche Codec fehlt. Bitte teilen Sie mir mit, welchen Codec ich benötige und wie oder wo ich diesen erhalten kann. Vielen Dank.

ggfb
What version of Premiere Elements are you using and on what computer operating system is it running?
Your issues could be two fold
a. MotionJPEG codec
and
b. No QuickTime (latest or any version) installed on your computer with Premiere Elements
Please go to your computer sharing section and the QuickTime choice. Do you see presets there for QuickTime?
If you do not have QuickTime installed or there is a problem with the installed QuickTime, you will not see QuickTime
presets.
As for MotionJPEG codec, that can be problematic for some, not all. The typical remedies include
a. Install a utility that came with the camera to supply any special MotionJPEG codec for Premiere Elements
b. Download, install, and maybe purchase if needed, the Morgan MotionJPEG codec
c. Convert you MotionJPEG file to another format compatible with Premiere Elements
We will be watching for further details.
Thank you.
ATR

10.6.8 stops me importing photos from Olympus camera

1. Recently bought a new Olympus VR310 digital camera. I couldn't get either Image Capture (6.0.1) or iPhoto (9.1.5) to import images from day one, onto my Mac Mini running Snow Leopard 10.6.8. However, if I took the SDHC card out of the Olympus and put it into an older Canon Ixus digital camera , and used that to upload, then both Image Capture and iPhoto worked perfectly. So it's not the card. Or the USB connection. It's something special to the Olympus and the Mac. Obviously I tried all the usual stuff about dumping plist files etc. Nothing worked.
2. The problem manifests itself, when the Olympus is connected, as Image Capture being unable to show more than one, if any, thumbnails, and it is unable to import at all. In iPhoto the problem manifests immediately it calls up the Olympus as a connected camera. The dreaded spinning beachball of death kicks off, and the program 'stops responding'. Even after I quit iPhoto and unmount the Olympus, iPhoto will not open without the spinning ball of death until I restart.
3. Anyway, I tried connecting the Olympus to my son's Macbook, (System 10.6.7, Image Capture 6.0.1 and iPhoto 9.1.1) and all worked perfectly. Hmm… so it's NOT just down to the Olympus. It's something to do with my setup.
4. I also have a bootable USB drive connected to the Mini, so I booted into that, so I then have my computer and my user preferences etc running under the bootable drives System 10.6.6, Image Capture 6.0.1, and iPhoto 9.1.5. That worked perfectly with the Olympus too. So it's not my the combination of my user settings, Image Capture 6.0.1, or iPhoto 9.15, or the Olympus.
5. My guess then was it was some corruption of the system on the Mac Mini. So I reinstalled the Mac Mini system, from the install DVD, so I had a nice fresh Snow Leopard 10.6.0. That gave me Image Capture 6.0.1 and iPhoto 9.1.5. When I attached the Olympus, everything worked perfectly. Great.
THEN, I updated the system from Apple's Oftware Update, all the way to 10.6.8, which is where I started from.
6. And guess what. Nothing works anymore. Immediately before the update, the Olympus importing worked. Immediately afterwards it didn't. I'm back where I was at the beginning, with exactly the same problem.. I can't import from the Olympus but the Canon is fine. (see 1 and 2 above)
So, it seems to me that the Upgrade straight to 10.6.8 is what caused the problem. And given I could get the Olympus to work on my son's computer (system 10.6.6) it's something between 10.6.6 and 10.6.8. Why the Canon works on all the permutations, and not the Olympus, I don't know. I don't know why the Olympus ONLY doesn't work with 10.6.8.
7. Obviously there are tedious workarounds (but none that lets iPhoto capture the photos directly) which I can use to get the images into iPhoto eventually, but hey, this is an Apple Mac, who wants to be doing tedious workarounds all the time.
I've had Macs since 1984 (I'm that old…) so I'm a fan, and I'm reasonably competent, but this has me stumped.
Any ideas, anyone.
Any help much appreciated.
Ian Waterston

You launched iPhoto and from its Preferences you selected Connecting camera opens.....

Upgraded to 10.6.8 and now can't import photos from Olympus camera

1. Recently bought a new Olympus VR310 digital camera. I couldn't get either Image Capture (6.0.1) or iPhoto (9.1.5) to import images from day one, onto my Mac Mini running Snow Leopard 10.6.8. However, if I took the SDHC card out of the Olympus and put it into an older Canon Ixus digital camera , and used that to upload, then both Image Capture and iPhoto worked perfectly. So it's not the card. Or the USB connection. It's something special to the Olympus and the Mac. Obviously I tried all the usual stuff about dumping plist files etc. Nothing worked.
2. The problem manifests itself, when the Olympus is connected, as Image Capture being unable to show more than one, if any, thumbnails, and it is unable to import at all. In iPhoto the problem manifests immediately it calls up the Olympus as a connected camera. The dreaded spinning beachball of death kicks off, and the program 'stops responding'. Even after I quit iPhoto and unmount the Olympus, iPhoto will not open without the spinning ball of death until I restart.
3. Anyway, I tried connecting the Olympus to my son's Macbook, (System 10.6.7, Image Capture 6.0.1 and iPhoto 9.1.1) and all worked perfectly. Hmm… so it's NOT just down to the Olympus. It's something to do with my setup.
4. I also have a bootable USB drive connected to the Mini, so I booted into that, so I then have my computer and my user preferences etc running under the bootable drives System 10.6.6, Image Capture 6.0.1, and iPhoto 9.1.5. That worked perfectly with the Olympus too. So it's not my the combination of my user settings, Image Capture 6.0.1, or iPhoto 9.15, or the Olympus.
5. My guess then was it was some corruption of the system on the Mac Mini. So I reinstalled the Mac Mini system, from the install DVD, so I had a nice fresh Snow Leopard 10.6.0. That gave me Image Capture 6.0.1 and iPhoto 9.1.5. When I attached the Olympus, everything worked perfectly. Great.
THEN, I updated the system from Apple's Oftware Update, all the way to 10.6.8, which is where I started from.
6. And guess what. Nothing works anymore. Immediately before the update, the Olympus importing worked. Immediately afterwards it didn't. I'm back where I was at the beginning, with exactly the same problem.. I can't import from the Olympus but the Canon is fine. (see 1 and 2 above)
So, it seems to me that the Upgrade straight to 10.6.8 is what caused the problem. And given I could get the Olympus to work on my son's computer (system 10.6.6) it's something between 10.6.6 and 10.6.8. Why the Canon works on all the permutations, and not the Olympus, I don't know. I don't know why the Olympus ONLY doesn't work with 10.6.8.
7. Obviously there are tedious workarounds (but none that lets iPhoto capture the photos directly) which I can use to get the images into iPhoto eventually, but hey, this is an Apple Mac, who wants to be doing tedious workarounds all the time.
I've had Macs since 1984 (I'm that old…) so I'm a fan, and I'm reasonably competent, but this has me stumped.
Any ideas, anyone.
Any help much appreciated.
Ian Waterston

You launched iPhoto and from its Preferences you selected Connecting camera opens.....

Photoshop CS2 obsolete with an Olympus E-3

I just received my new Olympus E-3 this week and it is a very impressive professional DSLR camera. I have to say that I am exceedingly disappointed with Adobe right now as it looks like they are no longer supporting Photoshop CS2 even though it is only one revision old. With the latest updates I can use their digital negative converter (which I wish more camera manufacturers would support) and my Photoshop Elements 5.0, including Camera RAW, works with the E-3 ORF/RAW files. Photoshop CS2 apparently has no plug-in for it, the latest Camera RAW doesn't work in it or in Bridge, and it no longer accepts new .dng files sent to it from PSE5. It is now largely useless to me as I can't used it until the photos are degraded .jpg's.
I am on Vista, so is their anything I need to do, or is my analysis above correct? CS-2 over CS had enough to make me upgrade, CS-3 over CS-2 didn't.

Nobody likes the fact that to get the latest raw support for the latest
camera (without hoop jumping) you have to upgrade Photoshop. Most of don't
think it is fair. However, there are some things to keep in mind.
1. Each new major release of Photoshop brings massive updates to ACR. These
updates would not be an easy or really cost effective thing to do for older
versions of ACR.
2. It is very likely that updates to ACR are not solely in ACR itself. I
would imagine that some changes have to be made to Photoshop to. This means
they couldn't update ACR to work with CS2 because CS2 is lacking things that
would be needed. Things that are only in CS3.
3. Even if Adobe charged $19.95 for the ACR upgrade for Photoshop CS2 if
they couldn't bring it inline with CS3's ACR but only could add support for
new cameras people would still complain.
4. There is a work around, download the latest DNG converter program, it is
free and convert your raw images to DNG. This is in my book a good thing
anyways. Just as soon as DNG becomes and ISO standard it will be the safest
raw format available. In other words it will be the most future proof raw
format we will have. Once your files are converted to DNG you can then load
them in to the ACR that comes with CS2.
Myself, I think the mistake Adobe made was not making the camera support a
plug-in for ACR. By doing this they could have simply updated ACR as they
wished giving you the new version with each new version of Photoshop, but
allowed people with the old versions to use new cameras because you would
only have to download new profile plug-ins for new cameras. I don't see new
cameras as being a major reason to upgrade ACR. I see the new features and
improvements made to each new version of ACR more of an upgrade draw than
new camera support. I think Adobe would have lost very little income by
designing ACR to support new cameras by doing plug-ins. I would still have
upgraded from CS2 to CS3.
Of course there is also the new upgrade policy. Photoshop 7 is the oldest
version you can now use to upgrade to Photoshop CS3. If you have a version
older than 7 you have to buy the full Photoshop package, you can't upgrade.
When Photoshop CS4 comes out then CS1 will be the oldest version you can use
to upgrade. So sooner rather than later unless you like to buy full packages
instead of upgrades one is going to have to upgrade anyways.
Myself I would use the DNG converter now and then upgrade Photoshop when CS4
comes out. I figure CS4 is less than a year away.

"Unknown Error" all the time, every time on render of project, any codec

Trying to render a feature length documentary for a film festival (ie.. I don't have time for this). The project timeline runs 1 hour and 20 minutes. If I try and export or queue the timeline in media encoder to h.264, QuickTime or Select "Match Sequence Settings" as my output format, the media encoder fails to render with the very informative "UNKNOW ERROR" every time at random point in the render procedure. When rendering it as an mpeg once, I am able to see one place where it crashed. It is a place in the timeline where the are no transition, not cuts, no overlays, absolutely nothing out of the ordinary. Yet, it crashed there this time. Next time, it will crash elsewhere.
I am trying to render the timeline on segment at a time. So far, each smaller segment of 20 minute blocks seems to be rending just fine and goes past the points where other renders failed. Looks like Media Encoder can't handle large projects.
Here's all the requested information for a complete diagnosis of the problem.
Error given to me by Media Encoder : "Unknown Error" --that's it. The time rendered varies between 43 minutes and 3 hours.
- Encoding Time: 00:54:04
05/03/2015 05:59:03 PM : Encoding Failed
Export Error
Error compiling movie.
Unknown error.
Adobe Premiere Pro CC 8.1 Caravan
2014.2 Release
8.2.0 (65) Build
OS X 10.10.3 (14D136)
iMac (27-inch, Mid 2011)
3.4 GHz Intel Core i7
24 GB 1333 MHz DDR3
AMD Radeon HD 6970M 2048 MB
I'm right handed, my favorite color is blue, the computer is on the Eastern TimeZone
I need this timeline rendered and I'm not interested becoming a forensic-level technical authority on Premiere to get it. This problem has come and gone now for months and is intolerable. I pay for software and I expect it to work, and at least give me something more useful than "UNKNOW ERROR." There is no such thing. As a former developer, I can say with authority that simply dumping to a message that says this is lazy and sloppy programming. Buffer underruns, stack overflows..whatever. Everything is caused by something. I can't begin to diagnose this problem unless Adobe provides software error handing that gives me some idea of what happens. Where did it happen in the timeline? What routine/subroutine gave the error? Was it a codec error? Come on....these things are not unknowable.
Adobe, PLEASE stop coming out with new features when you can't make your existing pay by the month software reliable! Maybe FCPX is worth another look.

UPDATE:
tried rending the entire project as Quicktime ProRes 422 (since that is what clips were recorded in originally anyway) and Media Encoder gto 89% complete....and the entire application CRASHED. WHO-HOO! Way to go, Adobe!!!!!
Here's part of the crash report if it means anything. Maybe I'll try it again and see if anything changes! Can't get any worse.
Process:               Adobe Media Encoder CC 2014 [864]
Path:                  /Applications/Adobe Media Encoder CC 2014/Adobe Media Encoder CC 2014.app/Contents/MacOS/Adobe Media Encoder CC 2014
Identifier:            com.adobe.dynamiclinkmanager.application
Version:               8.2.0.54 (8.2.0)
Code Type:             X86-64 (Native)
Parent Process:        dynamiclinkmanager [826]
Responsible:           dynamiclinkmanager [826]
User ID:               502
Date/Time:             2015-05-03 20:05:05.829 -0400
OS Version:            Mac OS X 10.10.3 (14D136)
Report Version:        11
Anonymous UUID:        5CCC287C-7B70-E4F9-D0E8-4180FB0681CC
Sleep/Wake UUID:       0ED73954-6C5A-4CCE-B807-974B71171E95
Time Awake Since Boot: 33000 seconds
Crashed Thread:        0 Dispatch queue: com.apple.main-thread
Exception Type:        EXC_CRASH (SIGBUS)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib         0x00007fff94c8d4de mach_msg_trap + 10
1   libsystem_kernel.dylib         0x00007fff94c8c64f mach_msg + 55
2   com.apple.CoreFoundation       0x00007fff94955eb4 __CFRunLoopServiceMachPort + 212
3   com.apple.CoreFoundation       0x00007fff9495537b __CFRunLoopRun + 1371
4   com.apple.CoreFoundation       0x00007fff94954bd8 CFRunLoopRunSpecific + 296
5   com.apple.HIToolbox           0x00007fff8ab7256f RunCurrentEventLoopInMode + 235
6   com.apple.HIToolbox           0x00007fff8ab722ea ReceiveNextEventCommon + 431
7   com.apple.HIToolbox           0x00007fff8ab7212b _BlockUntilNextEventMatchingListInModeWithFilter + 71
8   com.apple.AppKit               0x00007fff8c8fe9bb _DPSNextEvent + 978
9   com.apple.AppKit               0x00007fff8c8fdf68 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 346
10 com.apple.AppKit               0x00007fff8c8f3bf3 -[NSApplication run] + 594
11 com.adobe.exo.framework       0x00000001057f3a88 exo::app::OS_AppBase::RunEventLoop() + 56
12 com.adobe.ame.application     0x00000001000195c1 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> > > >&) + 11809
13 com.adobe.ame.application     0x0000000100049ba8 main + 440
14 com.adobe.ame.application     0x0000000100003e34 start + 52

Missing codecs for Blackmagic HD Extreme?

I just installed a new BM HD Extreme card. I installed the latest driver (6.3)
I am running QT 7.2 and FCP 6.0.1
When I launch FCP it prompts me to select a Sequence Preset.
The drop down window contains many Blackmagic options- but many others are missing. For example: I only have 3 choices of 1080i 59.94 (10bit, 10bit RGB, and 8bit). There are only 2 DVCproHD options. And there is no NTSC DV option, etc.
If I choose CANCEL I do not get a Timeline or Canvas window and they are grayed out the Window drop down menu. If I choose a preset- even one I do not want I get a complete layout.
Once inside FCP- I try Audio/Video Settings Menu.
All options including 1080i 59.94 ProRes, 1080i 59.94 DVCpro, NTSC DV, etc.
are available as Capture presets- but they are not listed under Sequence Preset menu.
If I select Easy Set-up- ALL BM presets are listed.
but when I try to edit to timeline I get a prompt telling to switch settings.
Many of these same setting options are missing from the VIEW Video Playback menu as well.
It's all very confusing. What is going on here?
I suppose my question is:
How do I get All Blackmagic presets to appear as options in all settings- including sequence preset and Video playback?

time to call black magic support. I suspect (have not had time to check) the codecs are not in the proper location like in library>application support>final cut pro>??
look for the setups you see and where they are. I think there are separate locations for easy setup and for sequence presets. I have the same thing in the B room with an older blackmagic card

Olympus E-M1 codec

Similar Messages

Maybe you are looking for