Dng - 72 ppi when converted

Hi, I'm converting raw files from Canon 5DII, they are 180 pixels per inch and when converted to dng they come out at 72 pixels per inch. The histogram of the two images are also slightly different and so are the colours. Can anyone explain?

ppi may be irrelevant, but it is USEFUL. I asked for this some time ago, and got the same response "ppi is irrelevant - etc" from ... someone else :).
I still don't understand what's the problem with including an editable ppi value inside dng metadata.
I use it for calculating print sizes of my edited files, based on my printers settings. It makes my life easier. I can obviously live without it, but why do I have to, when even the NEF files i use give me that irrelevant-but-useful bit of info ? I could also live without any metadata altogether, but ...
My request : Just treat ppi as user-metadata if you wish, editable, irrelevant, but "there"...

Similar Messages

File size increase when converting EOS 5d Mark II 10 Mpixel Images to DNG?

Hi,
a colleague of mine is having issues when converting 10 Mpixel RAW images of his 5d Mark II to dng format. He shot the images at a smaller size in RAW format to save memory. When he converts the RAW to DNG using lightroom 2.2 the filesize increases to 39 Mb. That's almost the size of a 22 Mpixel RAW file and defeats the whole idea of shooting lower res.
My guess would be that the dng conversion doesnt take into account that the actual pixel count is lower than the full sensor res and somehow saves redundand data for the missing "sensor pixels". The dng is still 10 Mpixel large btw.
Can anyone else confirm this? Looks like a bug to me if that's the case.
Regards,
Mike

What settings is he using in the conversion? He should NOT check the linearization option and the option to include the original RAW. He should have lossless compression checked. Just use the defaults which does those things. A 12-bit 22 Mpixel dng file should be about 22 MB, not 39. I don't have any experience with sRAW though and I don't know how those are converted to dng.

Why DNG files are bigger when converting from TIFF?

When I shoot in RAW, my normal workflow is to convert all images to DNG and start editing in Lightroom. But as you know, there are some photos that need extra editing in pixel based software such as Photoshop.
When I right-click a DNG in Lightroom and chose "Edit In... » Edit in Adobe Photoshop", the photo will be opened in Photoshop as an 8-bit TIFF file for editing. For demonstration of my issue, let's assume I don't do any changes and just save the file as it is. A new TIFF file will be created next to the source DNG with "-Edit" in it's name.
Back into Lightroom, both files are almost the same, one is DNG, the other in 8-bit TIFF. From this point (assuming I did change something in Photoshop, otherwise what would be the point in opening it there) I should do my further editing in Lightroom in the TIFF and not the DNG one. Let's say I'm done with the work and export the final edited TIFF file back into a DNG (I like this format and I like to keep all metadata changes so I can easily revert back to the original). I've also exported the original DNG file for comparison.
And now I realize the following:
DNG to DNG » ~7Mb (basically the same as the original DNG)
TIFF to DNG » ~15Mb
Why such a big difference?
I didn't do any editing either in the original DNG or the Photoshop converted TIFF. Any techincal reason for this that I'm not aware or am I doing something wrong?

I did a little bit of research and:
1) The embedded previews are always JPEG files (medim or full size, doesn't matter). But now that I think about it, I don't think you were talking about the previews when you mentioned the TIFF being embedded.
2) I did a quick EXIF lookup on 3 files exported to DNG: a) Original DNG b) 16-bit TIFF converted to DNG c) 8-bit converted to DNG. Here's the EXIF results:
a)
SubfileType                     : Full-resolution Image
ImageWidth                      : 3736
ImageHeight                     : 2772
BitsPerSample                   : 16
Compression                     : JPEG
PhotometricInterpretation       : Color Filter Array
SamplesPerPixel                 : 1
b)
SubfileType                     : Full-resolution Image
ImageWidth                      : 3648
ImageHeight                     : 2736
BitsPerSample                   : 16 16 16
Compression                     : JPEG
PhotometricInterpretation       : Linear Raw
SamplesPerPixel                 : 3
c)
SubfileType                     : Full-resolution Image
ImageWidth                      : 3648
ImageHeight                     : 2736
BitsPerSample                   : 8 8 8
Compression                     : JPEG
PhotometricInterpretation       : Linear Raw
SamplesPerPixel                 : 3
This probably means something like you said... The embedded files are different and some take more space than the others. The first one is 7.220Kb, the second one (16-bit TIFF) is 44.030Kb and the third one (8-bit TIFF) is 15.284Kb.
It makes sense I guess, but I still would love to hear a more technical explanation for it but it's obvious it has something to do on how the pixels are saved in the DNG file. The keyword is probably the PhotometricInterpretation.

DNG 5.4 beta converter issues with Hasselblad H2D-39 files

I was directed to this forum when I posted a note on the DNG converter 5.4 beta, converting to use on Photoshop CS3 (see thread http://forums.adobe.com/thread/436940?tstart=0 )
The converter has a very interesting "fail pattern" when converting Hasselblad .3fr files:
First file fails (error message displayed is "Unknown error", second file converts OK, 3rd fails, 4th OK, 5th fails, 6&7 OK, 8th fails..
By about the 20th file, 5 are successfully converted in a row and then by file 30, no more failures!
So it would seem that there is not really a problem with actually reading/processing the .3fr file content. Instead looks like some form of memory or other issue in the code??
I have also noted a few cases of problems with the conversion itself, picture ends up totally posterized, see attached file which is unmodified out of raw -> PS CS3:
Finally, processing the DNG files converted still fails on Photoshop CS3 as reported earlier in this thread:
http://forums.adobe.com/thread/421742?tstart=0
If I open the DNG file in PS CS3 and save pretty much immediately, saving works. If I do almost any processing, the "Save as" freezes PS3 before the file/directory selection dialog starts. Only forcefully stopping Photoshop helps. Looks like there is something in the "Save as" dialogue that does not check for exceeding max memory allocated to Photoshop or similar?

Hi,
Thanks for responding. I thought this was the forum pointed to from the download site, was not aware of the dng forum. Though there is another post on probs with convering Hasselblad files ( http://forums.adobe.com/thread/436615?tstart=0 ), my symptoms are quite similar ("Unknown error") so I would suspect this could be related to the same prob? As I am quite keen to get rid of the Phocus software, if there is anything I can do to help you fix the bug, just send me a note.
Thanks, Håkan
Ian Lyons kirjoitti 31.05.2009 kello 11:30:
If you're using the DNG converter then raising the issue on the
appropriate
forum might get a bit more attention
http://forums.adobe.com/community/dng
>

Is it wise to keep the Nikon camera files "DSC's" after downloading them and converting to DNG files via Adobe converter for lightroom use. In other words do the DNG files have all the raw data I would ever need in processing or should I save the camera'

Is it wise to keep the Nikon camera files "DSC's" after downloading them and converting to DNG files via Adobe converter for lightroom use. In other words do the DNG files have all the raw data I would ever need in processing or should I save the camera's DSC files?

DNG files do not contain some metadata supplied by the camera, which can be used by the manufacturer's software. Thus, if you don't keep the original Raw photo, you will lose this information.
If your 1000% sure you're never going to use the manufacturer's software, then this isn't a problem. But who can be sure what software you will be using 10 years from now?

Why are hyperlinks no longer working in PDF, when converted from Word?

I have Acrobat Professional 11 and have recently upgraded my PC with a new operating system (Windows 8). I can't remember how to find out what version of Word I now have, but it should be a fairly recent version, given its new. Since the upgrade, when converting Word documents to PDF using the "Create Form" function in Adobe Pro 11, only full hyperlinks (with the @ symbol) are working in PDF, not other hyperlinks that we've renamed. Under the old operating system, ALL hyperlinks used to transfer & work when converted ... am I missing a checkbox somewhere?? HELP please, I have loads of word documents to convert and it's very time-consuming to have to do weblinks manually!!

First off, Word should show you the version on a splash screen when you launch it.
Also, what happens to the links if you just open the document in Word and save it as a PDF?

Conversion failed when converting date and/or time from character string

Hi experts,
I'm trying running a query in Microsoft Query but it gives the following error message:
"conversion failed when converting date and/or time from character string"
when asks me the data I'm inserting 31-01-2014
i've copy the query form the forum:
SELECT T1.CardCode, T1.CardName, T1.CreditLine, T0.RefDate, T0.Ref1 'Document Number',
     CASE WHEN T0.TransType=13 THEN 'Invoice'
          WHEN T0.TransType=14 THEN 'Credit Note'
          WHEN T0.TransType=30 THEN 'Journal'
          WHEN T0.TransType=24 THEN 'Receipt'
          END AS 'Document Type',
     T0.DueDate, (T0.Debit- T0.Credit) 'Balance'
     ,ISNULL((SELECT T0.Debit-T0.Credit WHERE DateDiff(day, T0.DueDate,'[%1]')<=-1),0) 'Future'
     ,ISNULL((SELECT T0.Debit-T0.Credit WHERE DateDiff(day, T0.DueDate,'[%1]')>=0 and DateDiff(day, T0.DueDate,'[%1]')<=30),0) 'Current'
     ,ISNULL((SELECT T0.Debit-T0.Credit WHERE DateDiff(day, T0.DueDate,'[%1]')>30 and DateDiff(day, T0.DueDate,'[%1]')<=60),0) '31-60 Days'
     ,ISNULL((SELECT T0.Debit-T0.Credit WHERE DateDiff(day, T0.DueDate,'[%1]')>60 and DateDiff(day, T0.DueDate,'[%1]')<=90),0) '61-90 Days'
     ,ISNULL((SELECT T0.Debit-T0.Credit WHERE DateDiff(day, T0.DueDate,'[%1]')>90 and DateDiff(day, T0.DueDate,'[%1]')<=120),0) '91-120 Days'
     ,ISNULL((SELECT T0.Debit-T0.Credit WHERE DateDiff(day, T0.DueDate,'[%1]')>=121),0) '121+ Days'
FROM JDT1 T0 INNER JOIN OCRD T1 ON T0.ShortName = T1.CardCode
WHERE (T0.MthDate IS NULL OR T0.MthDate > ?) AND T0.RefDate <= ? AND T1.CardType = 'C'
ORDER BY T1.CardCode, T0.DueDate, T0.Ref1

Hi,
The above error appears due to date format is differnt from SAP query generator and SQL server.
So you need convert all date in above query to SQL server required format.
Try to convert..let me know if not possible.
Thanks & Regards,
Nagarajan

Word 2003 crashes when converting to a PDF in Acrobat 9.3.1

OS                    :   Windows XP Pro SP3
Acrobat Version:   Acrobat Pro 9.3.1.
M.S. Product     : Word 2003
Not every file will crash Word 2003 when converting to a PDF using Acrobat Pro 9.3.1 but this particular file and some others will produce the following error:
%%[ ProductName: Distiller ]%%
%%[Page: 1]%%
%%[ Error: syntaxerror; OffendingCommand: ) '$ $ $ &$   ]%%
%%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
%%[ Warning: PostScript error. No PDF file produced. ] %%
The co-worker was receiving the same error in Adobe Acrobat Pro 9.0 before we updated her to AAP 9.1.3.
I have read some other threads similar to mine but none of them answer the question well enough to try anything listed there. My co-worker can email me the Word file and I can print the file to my Adobe PDF printer just fine. I have Acrobat Pro 7.0.
Can anyone give me help on the cause and or solution to this problem????

Hi,
- syntaxerror indicates the file contains unintelligible PostScript code.
Any discussion of postscript errors, seem to consistently point to:
http://kb2.adobe.com/cps/328/328515.html
A troubleshooting guide is down in the bottom third of the page.
Be well...

Error when converting a numeric field to XML

Hi,
When i run the Adobe intractive form,i am getting following exception
"Error when converting a numeric field to XML"
Anyone plz suggest
Regards,
vinoth

Hi Vinoth Raja,
For resolving the following exception
"Error when converting a numeric field to XML"
You have to follow the below link:-
http://www.saptechies.com/error-when-converting-numeric-field-xml/
May be it will help you
Regards,
Sushma Yadav

Error when converting a constant amount MAXBT in T511P

Dear Expert,
I am encounter error as below when run payroll for Macao,
Error when converting a constant amount MAXBT in T511P
CONVERT_TO_LOCAL_CURRENCY has been Called
Data used:
Validity end date: 28.02.2014
Constant: MAXBT
T511P Currency MOP
Currency of payroll driver HKD
Therefor, do the checking on OE00 and check the currency and validity dates for MOP currency.
Also, checked table V_T001 table the currency that assigned for the company code.
Checked the MOP currency and ISO code in V_TCURC table. And checked ISO code in V_CURC table as well.
Still encounter error as above, appreciate you advice.
Thanks,
Mel

What are the values for :
Country grouping for PA/PSA:
Currency appearing in IT0008:
Country key in IT0006:
Bank Country in IT0009:

How to preserve data when converting a Standard DSO into a Write Optimized

Hi,
I'm looking for proven strategies for preserving data when converting a standard DSO into a write optimized DSO. The data has to be dropped before the new DSO is transported into the environment.
1. The DSO is currently in synch with a cube,
2. The PSA does not have all the data which is in the DSO.
3. Data volume is incredibly high for a full reload from ECC, so we'd like to avoid that option.
Appreciate any help!

Hi Gregg,
have you considered just deleting the data? I know that sounds simple, but it might be a valid solution.
If the DSO is just receiving new data (e.g. FI documents), you can continue to deliver a logically correct delta to the cube.
Should that not be possible and you really want all data that you currently have in your DSO1 in the write optimized future of it, then how about this:
- Create a new DSO2 same structure as DSO1
- Load all data into that
- Delete all data from your DSO1 and import the transport to make it write optimized
- Load all data back into you now write optimized DSO1 from DSO2
The problem you have then, is that all data that you have already loaded into your cube is due to be delivered as a delta from DSO1 again.
Depending on your transformation / update rules that might or might not be a problem.
Best,
Ralf

How to maintain original lines when converting a word file in a PDF

Unfortunately the table lines often change when converting a word file in a PDF, e.g. dotted/broken lines into straight lines or different kinds of broken lines. How can I maintain the original lines when converting the documents?
Many thanks in advance for your advice.
Li Li

Hello,
Ok, this is the background.
I’m a publisher. Any document to end user will go as pdf. And off course it preserves the word appearance. We ship our manuals only in pdf. At this point my end users have to copy the “CODES” into his editor to run the product. So when doing it, the “Codes” copied from pdf to his editor loses its format. Editor need not be the actual one; you can also test in a notepad.
P.S: You can find the difference by copying the code from word to notepad and pdf to notepad
Hope you now understood the purpose what I’m looking at for.

How to preserve original size when converting to PDF in Preview.

I'm using Preview in Snow Leopard.
Trying to create multipage PDFs from document scans.
I'm finding that when the scanned image (tiff, png, jpg) is converted to PDF in Preview the size reduces.
Selecting 'View actual size' shows the image with sometimes drastically impaired quality.
This does not always happen. I have some images that stay the same size and quality.
What factors cause this reduction in size in some images but not in others?
I'm not sure but this could be only images that have been scanned by me. If so, what do I need to do to prevent the problem?
These are not large images, just standard size pages.
I have all the preferences to view at 100%
This is not for printing, only for viewing on-screen.

Please!!
I'm not silly...
As I said, selecting View actual size shows the image with sometimes drastically impaired quality (regardless of the window size).
I also said I have preferences set to view at 100%
It now seems as if this is only happening with scans I've made here.
Images downloaded from the internet are converting indentically, no problem. But my scans are being resized when converting.
I wonder if anyone with a bit of technical know-how can give me some clues as to why this is happening. It would seem to be something to do with the file itself.
(There was another post on here with the same problem but for some reason its been 'archived' though the last posting was this month and the query was not answered. So I've posted the question again.)

Error "Conversion failed when converting date and/or time from character string" to execute one query in sql 2008 r2, run ok in 2005.

I have a table-valued function that run in sql 2005 and when try to execute in sql 2008 r2, return the next "Conversion failed when converting date and/or time from character string".
USE [Runtime]
GO
/****** Object: UserDefinedFunction [dbo].[f_Pinto_Graf_P_Opt] Script Date: 06/11/2013 08:47:47 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
CREATE FUNCTION [dbo].[f_Pinto_Graf_P_Opt] (@fechaInicio datetime, @fechaFin datetime)
-- Declaramos la tabla "@Produc_Opt" que será devuelta por la funcion
RETURNS @Produc_Opt table ( Hora datetime,NSACOS int, NSACOS_opt int)
AS
BEGIN
-- Crea el Cursor
DECLARE cursorHora CURSOR
READ_ONLY
FOR SELECT DateTime, Value FROM f_PP_Graficas ('Pinto_CON_SACOS',@fechaInicio, @fechaFin,'Pinto_PRODUCTO')
-- Declaracion de variables locales
DECLARE @produc_opt_hora int
DECLARE @produc_opt_parc int
DECLARE @nsacos int
DECLARE @time_parc datetime
-- Inicializamos VARIABLES
SET @produc_opt_hora = (SELECT * FROM f_Valor (@fechaFin,'Pinto_PRODUC_OPT'))
-- Abre y se crea el conjunto del cursor
OPEN cursorHora
-- Comenzamos los calculos
FETCH NEXT FROM cursorHora INTO @time_parc,@nsacos
/************ BUCLE WHILE QUE SE VA A MOVER A TRAVES DEL CURSOR ************/
WHILE (@@fetch_status <> -1)
BEGIN
IF (@@fetch_status = -2)
BEGIN
-- Terminamos la ejecucion
BREAK
END
-- REALIZAMOS CÁLCULOS
SET @produc_opt_parc = (SELECT dbo.f_P_Opt_Parc (@fechaInicio,@time_parc,@produc_opt_hora))
-- INSERTAMOS VALORES EN LA TABLA
INSERT @Produc_Opt VALUES (@time_parc,@nsacos, @produc_opt_parc)
-- Avanzamos el cursor
FETCH NEXT FROM cursorHora INTO @time_parc,@nsacos
END
/************ FIN DEL BUCLE QUE SE MUEVE A TRAVES DEL CURSOR ***************/
-- Cerramos el cursor
CLOSE cursorHora
-- Liberamos los cursores
DEALLOCATE cursorHora
RETURN
END

You can search the forums for that error message and find previous discussions - they all boil down to the same problem. Somewhere in your query that calls this function, the code invoked implicitly converts from string to date/datetime. In general,
this works in any version of sql server if the runtime settings are correct for the format of the string data. The fact that it works in one server and not in another server suggests that the query executes with different settings - and I'll assume for
the moment that the format of the data involved in this conversion is consistent within the database/resultset and consistent between the 2 servers.
I suggest you read Tibor's guide to the datetime datatype (via the link to his site below) first - then go find the actual code that performs this conversion. It may not be in the function you posted, since that function also executes other functions.
You also did not post the query that calls this function, so this function may not, in fact, be the source of the problem at all.
Tibor's site

What is better when converting analog video for FCE, Canopus100/110/300/or5

All,
What is better when converting analog video for FCE, Canopus100/110/300/or500? I have a new MACPRO with FCE HD and I wanted to convert some of my older video that was recorded on a HI8 Camcorder... Thanks.

I have the ADVC-100 (older model) and ADVC-110. They are identical except that the ADVC-110 does not come with an AC power adapter. Currently sells for about $220USD. If all you need to do is convert from HI8 tapes, the ADVC100/110 will do the job quite nicely.
The ADVC300 adds some enhancements for video signal cleanup, but at a higher price. Currently sells for about $450USD. The ADVC500 is overkill for home use.

Dng - 72 ppi when converted

Similar Messages

Maybe you are looking for