Support for DNG files from Odyssey7Q.

Just upgraded my Odyssey7Q to capture 4K RAW from the FS700. Importing the DNGs into Premiere yields an extremely purple image. The DNGs import fine in After Effects.
Any chance to get this addressed in a Premiere update?

Hi Dave,
I did start the thread over on DVXUser - good to see you're working with Convergent Design on supporting their DNG files :) The odyssey 7Q is an excellent bit of kit and seems to be taking the world by storm!
Are you able to say if support for this will be in the next release and roughly when we might expect to see that?
I'm guessing we're about due for another release? Maybe for NAB time????
Cheers,
Paul.

Similar Messages

Is there any system level support for RAW files from an Olympus XZ-10 camera. I use Lion and iPhoto version 9.4.2

Is there any system level support for RAW files from an Olympus XZ-10 camera. I use Lion and iPhoto version 9.4.2

If there is I can not find it - Google provides a list of possible methods form Adobe and others
LN

Where is Aperture support for raw files from Leica X Vario?

Where is Aperture support for raw files from Leica X Vario?

It doesn't appear to exist, at this time:
http://www.apple.com/aperture/specs/raw.html

Support for DNG files with lens corrections?

Aperture 3.0.1 with the RAW Compatibility Update 3.1 now supports the lens corrections in my Olympus E-P1's native RAW format. yay!
unfortunately, since Aperture didn't support the camera for six months, I began a switch to Lightroom. consequently, I now have several thousand images that have been converted from the EP-1's native RAW format (ORF) to Adobe's so-called open RAW format (DNG). these DNGs don't load in Aperture (RAW format unsupported errors) because Aperture doesn't support DNGs with lens corrections.
Apple, can you please advise if lens corrections you support in native RAW files will also be supported in DNG conversions sometime soon? if so, I'll know it's safe to switch back to Aperture and recover the last six months of photos when the next RAW Compatibility Update happens.

Aperture 3.0.1 with the RAW Compatibility Update 3.1 does not support lens corrections. If you want lens corrections in Aperture you have to use Plugins like PTlens.
To my knowledge Aperture ignores all lens correction data in the original RAW files, just like it does with all the settings of the camera.

Did Apple remove support for DNG files generated out of Capture One?

I use Capture One to convert my Leica Dlux-4 RAW files into DNG format and then use Aperture2.1.4 as my photo processing tool.
After I ran the latest OS update - Aperture gives a "Unsupported file format" message for all the DNG files.
Is it possible that Apple removes support for photo formats in the OS updates?
Anyone encountered the same issue and found a solution?
Thx

Go in the adjustment tab, and the first thing you'll see under the histogram is "Raw fine tuning". By default, "2.0" is selected. When importing DNG, you can switch it to "2.0 DNG" this is used to read DNGs from cameras Aperture doesn't support.
Maybe the update made it go back to its default "2.0" while before you where on "2.0 DNG". If I'm right, setting it to "2.0 DNG" will fix the problem.
P.S. sorry if I said "raw precision" instead of "Raw fine tuning" in the first place. My Aperture is in French and the name in French is "Réglage de précision raw" and I did a bad translation.
Message was edited by: Manusnake

Support for DNG files?

Will aperture ever support the Adobe generated DNG file format?

No offense and I enjoyed your comments.
Thanks
CCD or CMOS sensitivity to light is non-linear. One
step of processing a DNG is to determine whether to
linearize (i.e. decode) this specific CCD/CMOS
sensitivity to a standard value. Aperture does not
support linearize and I explain why I believe this is
so below.
There are two very different versions of DNG. The
non-linearize one is little more than a wrapper,
which is why Aperture can read these DNG's as the RAW
is embedded. Now you state rightly that DNG
converters must do more than put a wrapper on, and
that is true ... but not for this type of DNG.
The other (linearize) is an interpreted RAW within a
standardized format (wrapper). Blackpoint
compensation (subraction), scaling etc. are also
manipulable variable. Aperture cannot read linear DNG
even if the RAW is supported.
Aperture RAW support is lacking and their support of
DNG is based on non-linear.
Well, then, how do SilkyPix, Lightzone and RAW Developer manage to open non-linear DNG from cameras they don't support and interpret them very well? That's what I want CoreImage to do.
Aperture need
to be vastly better at adding RAW support or telling
us their roadmap, or providing camera manufacturers
the API or ... but something!!!
100% agreed. However, since it is part of the OS we depend on OS updates which are way too slow to follow on the camera market. Moreover, I presume the release manager has other priorities in scheduling OS X updates than those pesky photographers with their marginal second cameras. I think that's a big part of the problem. The release of a RAW update for just the EOS 400 and D80 were due to too much market pressure. It also shows Apple priorities: it is not the pro or consumer status of a camera that will decide ts priority, but only its amrket share. Sorry, but that's a mistake because professional photographers tend to have different cameras and some far less prominent than the Nikon and Canon DSLRs. This is a major win for LR IMHO.
I agree with you that this is close to useless and
the situation is untenable for professionals. Oh, my
next camera is determined by Apple? Humm.
Yes, I really wonder what they are thinking.
Why would Aperture do this? Well, I believe it is
because of their very strict definitions of
"Non-Destructive" workflow. Ans so frankly I don't
see them using DNG more fully because of their
definition. This is how I believe it plays out ...
Sorry to repeat mysel, but if they could do what SilkyPix, Raw Developer and LightZone do, it would be fine.
So although you disagreed with my prior email points
as "untrue" I hope I've clarified. A linear DNG has
been decoded by something, and that something is
proprietary and therefore the resulting DNG data
content is proprietary.
I hope to have similarly clarified what I mean by DNG support
Since RAW is already manipulated data (contrary to
some belief, it is not exactly what light fell on
what pixel but has been demosaiced at the very
least), it makes the most sense to me to have the
camera manufacturer perform the convert to DNG in
camera. That way, my negative is my one, objective
source and I can select my camera on that basis and
make my adjustments on the same basis.
I agree entirely. I think it is futile to hope for major camera manufacturers to initiate a move to DNG because their marketing department probably feel (wrongly) that it comoditize their cameras. So, it is the software industry that has to impose a standard, and DNG is the closest thing we have. And a standard for RAW is needed. In that respect, I find that Apple does the worst job in the photo-related software industry.
This does not prevent me from apeciating the other qualities of Aperture, but, he entire idea being based on RAW files, not supporting them in the first place seems stupid to me.
Cheers.

When will Aperture have support for RAF files from the new Fuji XPro-1?

How long does it normally take to get the RAW file format updated? Fuji say they sent the file details to Apple many weeks ago. This is a camera being given fantastic reviews in all professional magazines worldwide - but I'm stuck with an Aperture folder full of "unsupported image format" files.
Really annoying as I use the full suite of Nik plug-ins so I can't do anything with these files until Aperture is updated.

Per an interview with a spokeswoman from Fuji, they have indeed provided Apple (and Adobe as well) all the needed technical information in order to support the RAW files (i.e. algorithmic information created by Fuji for the non-standar filter array, etc etc). Please don't spread any more misinformation about it, it's already been flamed to death on all the online camera forums. You can still choose to 'blame' whomever you wish about why it's still not supported by Apple, but you can no longer reasonably assert that Fuji hasn't done their part by providing them what they need. Nondisclosure agreements were signed as well.
Having said that, I find it ridiculous at this point that it's not supported, for several reasons, some being the seemingly similar Fuji users who also use Aperture as well as the opportunity here for Apple to take some market from Adobe (who as of yet are not producing very great output files for Fuji X-trans). Apple was/has been at a disadvantage to Adobe for a long while now, and being an outsider, I presumed Apple would want to take advantage of this (and any similar) opportunity to grab some share from Adobe. I was well wrong, and it seems that other lesser-known-used companies are now doing just that.
Well good on them. I for one will be looking at any/all (new)comers and will certainly be going with the best of those. Sorry Apple, you lost another one. There was a real competition, for me, btwn Aperture and LR4 up till this point. You'd have to pull a rabbit out of your hat to keep my Aperture biz.

Support for RAW files from Fujifilm X-T1?

I don't seem to able to view RAW files from Fujifilm X-T1 on Aperture. Is this available and if not when can it be made available?
Thanks
Michael

Michael,
sorry, no. Fujifilm X-T1 is not on the list of supported cameras, see:
Apple - Aperture - Technical Specifications - RAW Support
-- Léonie

Support for Growing files (DNxHD wrapped in MXF) from EVS in Premiere Pro?

We are using Premiere CC Pro on the Mac-plattform against a shared storage soulution. We need to be able to open growing files from an EVS system to edit soccer-highlights while the matches are still playing. The problem is that the codec is DNxHD 120 and the wrapper is MXF op1a. This works fine with a QT-wrapper, but not with a MXF-wrapper. It is not possible for us the change the wrapper on the EVS system, so we need to do something on the editing side. We have tested it, and confirmed that this works fine in Final Cut Pro and Avid, but we want to use Premiere Pro. Can you provide us with a solution? Please do not say that the solution is to use FCP... ;-) Thanks in advance for all help!

Hi Peter!
Latest version. Cc 2014 with all updates.
Mac OSX 10.10.2 Yosemite.
Error during opening. As soon as the file is closed, it opens fine.
Mvh
Marius Borge
Sendt fra min iPhone
Den 10. feb. 2015 kl. 18.40 skrev petergaraway <[email protected]<mailto:[email protected]>>:
Support for Growing files (DNxHD wrapped in MXF) from EVS in Premiere Pro?
created by petergaraway<https://forums.adobe.com/people/petergaraway> in Premiere Pro - View the full discussion<https://forums.adobe.com/message/7181513#7181513>

Error message when trying to send .dng file from Lr to Ps

If I am working in Lr (5.4) and try to send a .dng file from Lr to Photoshop CC (reinstalled latest version from Adobe.com today, 4/13/2014), I get this message: "
Adobe Photoshop CC cannot be opened because of a problem. Check with the developer to make sure Adobe Photoshop CC works with this version of OS X. You may need to reinstall the application. Be sure to install any available updates for the application and OS X."
I uninstalled and reinstalled Photoshop CC today and that did not fix the problem. I am in OS 10.8.5 on an iMac. Thanks!

Hello,
Programs that run in the background cannot address controls on the frontend. This is why you are not able to run a Program using SAP Office Integration which is a Frontend Control and can be used only with the SAP Gui. Since background process cannot make use of UI screens or actions hence it's not possible use SAP Office Integration in background processing. The reason for this is explained in note 674060. Therefore sending emails using a batch macro is not supported.
Best regards
Rico Frenzel

Error in DNG files from LR 3.2 using RW2 raw files?

I'm using DNG Profile Editor to generate appropriate profiles for infra-red images produced by converted Canon 5d and Panasonic G1 cameras.
In the case of the 5d this works fine and I've generated good profiles. However, with the G1 I get an error when trying to open the DNG files in DNG Profile Editor that the files are not valid DNG color files. I've produced DNG files from the original RW2 raw files in LR 3.2 both at time of import and using export command -- in both cases although the files are the right size (~13mb) they have dimensions of 0x0 pixels -- I'm assuming this is causing the error in Profile Editor?. When I carry out identical operations with CR2 files from the 5d I get DNG files with the correct pixel dimensions (5616x3744).
Has anyone else seen this problem? -- is it a known issue? -- is there a work-around?
Thanks for your help!
John.

Are you sure you changed the compatibility options correctly? The issue is that the G1 DNG images in the default 5.4 compatibility are using a newer DNG version not supported by the current public version of the DNG Profile Editor. That's why you need to choose the older "4.6" compatibility option, then Export the DNG again.

T-code for delete file from application server

Hi all!
Please, has any t-code for delete file from application server? For upload exist CG3Z, for download has CG3Y. And for delete? Has anyone?
I need to delete file from application server in QA system and i don't want to create a program for this because i will need to transport a request from DEV to QA.

I don't have contact with basis team.
The FM EPS_DELETE_FILE support directory name with max 60 char. My dir. has more than that. I need a transaction for this.
Anybody know if this transaction exist?

Why is there no support for RTF files in Pages?

Why is there no support for RTF files in Pages?
This is nuts!

You are not alone.
Actions speak louder than words, but Apple does manage to still distract many from what is self evident before them.
I am astonished by those who swear that non-existent features, or features that pre-exist the current version make Pages 5.2 a major upgrade.
An affect that does seem to wear off with familiarity, as each version of Pages 5 gets a boost in the App Store, only to see the disapproval rating surge back again.
Pages was always one of the top purchases in the App Store, now it doesn't even rate.
Peter

OS X support for offline files

Dear all,
I have a mixed environment of workstations running both OS X and Windows that connect to file shares hosted on Windows file servers. In order to be able to manage the storage space effectively, tape based archiving was implemented using Symantec's Enterprise Vault for File System Archiving. EV and many other archiving solutions use the Windows Offline file attribute to mark a file that has been archived off and install a filter driver into Windows so that archived files can be recalled directly from Windows Explorer without requiring additional software (this is also known as a reparse point). Please note that this is different from how Microsoft intended offline files to be used for synchronising between a roaming laptop and a network share (see KB 312717).
OS X does not have any support for offline files natively, both for how Microsoft intended it to be used and for use with archiving software as a reparse point. There are a couple of offerings on the market which add the required functionality to OS X, but recent updates to OS X have rendered these offerings non-functional:
10.6.7 - I understand that Apple replaced the SMB/CIFS modules with their own code. At this point, it no longer became possible to recall archived files using said software offerings, when connecting to a Windows file server via SMB. See Apple bug ID 10836961.
10.7.4 - a kernel update is included which means said software offerings are now not able to block the icon preview in Finder. The icon preview in Finder causes archived material to be recalled which we do not want it to do (imagine the problem when using tape as the archiving platform - this will cause a huge recall job on the tape drives)
This is going to cause significant difficulties as it effectively means that we can't use archiving with OS X to manage our storage costs.
I'm writing this as I'm hoping that someone will know of a product or solution that is able to work around the 2 difficulties noted above, or that someone from Apple is going to read this and realise that this is a serious problem. The ideal that is required is to add support for the offline files, in particular reparse points, directly into OS X.
Many thanks.
A frustrated storage engineer.

Hi Richard,
We are looking at file archiving here and have the same potential issues. We haven't evaluated this product, but it claims to solve the problem:
http://www.grouplogic.com/enterprise-file-sharing/mac-file-archiving-system/
Good luck
Mark

Olympus E-P1: Why DNG files from DNG-Converter, Lightroom or CameraRaw are invalid ?

Hello from Spain:
I've got a Olympus Pen E-P1.
I work with DNG Converter 5.5, Lightroom 2.5, CameraRaw 5.5, Photoshop CS4 with my *.ORF files with no problems, and I can convert ORF in DNG with those software smooth, but...
I can't open those DNG files with DNG Profile Editor. It display a error message "Could not open the selected image. Note that the selected image must be a valid DNG color image".
I'm trying to create a E-P1 DNG Profile using ColorChecker Passport. When I try to import a DNG file displays a similar error message "Can't open the file. Is a invalid DNG file".
What is occurring about DNG files from E-P1's ORF?.
Thank you,
Juanlu.

Hi, Beat:
Thanks for your offer.
Here you are a link to _B101110.ORF from my E-P1 for anyone who wants to try.
http://rcpt.yousendit.com/774955242/335db3525082f217660b3c7c3591df91
How can I create a DNG profile for my E-P1?.
Saludos,
Juanlu

Support for DNG files from Odyssey7Q.

Similar Messages

Maybe you are looking for