The list of modules can be exported from a DB browser. Because of the relations, a few fields are numbers instead of names…but one can find one’s way e.g. looking into “CAFList6.db”
List of supported bodies
Body.csv.zip (4.9 KB)
List of supported modules
Modules.csv.zip (1.6 MB)
How did you generate the spreadsheet (CSV) files? Which DB (presumably you mean SQL as defined by https://www.iso.org/standard/63555.html ) browser works and how does one get to the SQL DB for PL supported cameras and lenses? Note that the user interface provided at the DxO PL web site does not show any mechanism to create the CSV files (including a ZIP compressed archive of such files).
Note that I’m using a Mac and everything below therefore relates to DPL on Mac.
DB Browser:
DB with current body and module information can be found here:
/Users/ACCOUNTNAME/Library/DxO PhotoLab v6/Modules/CAFList6.db
Notes:
https://www.dxo.com/supported-cameras/
does not expose a SQL (sqlite) database for sqlitebrowser (the name of the application) . What URL reveals the database that can be converted into a CSV spreadsheet file?
The database is stored on your computer. Read my post above to find its location on Mac.
Clearly, we are not communicating. I understand that the database application you have recommended does not typically store the result of a query on the SQL server system, but on the system generating the query. However, one needs access to the SQL services of the SQL server system (DxO machines in this case). Neither I nor the SQL query generator (that will store the results on the query generating system, not the SQL server) can find a “link” (URL or other network protocol) to the SQL database on the DxO machine/s/network/s. How does one get the DxO server to recognise a SQL query from an end-user remote machine so that the data can be stored on the end-user machine (eg, as a CSV spreadsheet)?
Again, on my Macs, there is a “Modules” folder that contains a file called “CAFList6.db”, which contains the current state of body and module support. This database file is updated as new bodies and modules are supported.
If you’re on Win, you can find important file locations in this post: Useful information: User resources: Feedback, Upload & Support - Where to find Logs, etc.
“Logs” yes – automatic query and downloads from SQL servers, not as far as I can tell. Are you stating that when you installed the SQL query application on MacOS X, that application is then “automagically” used by MacOS X to query any SQL server that is behind a user interface on the Web? DxO presents a user interface that does not include “download all” but has a very cumbersome limited entry data access. Most DxO competitors have (in addition to any web page search “boxes”) a means to download a file (sometimes CSV, sometimes XLS, sometimes plain TXT) that has the complete list of supported bodies, lenses, point-and-shoots, and mobiles, typically for the current production release application (eg, for PL6 but not necessarily for PL earlier than 6). DxO does not seem to offer this for PL.
Again.
There is absolutely no need to access a server in the web.
Good morning platypus,
I already had the link for windows in my favorites, is there such information also for Mac?
best regards
Guenter
It’s a SQLite database. A database stores in a single file , no network link. SQLite is a popular opensource library that existed for years (also used in Firefox , android , etc…). There are utilities and tools for every platform out there.
Apparently , the list of all possible lenses can be fetched from the SQLite database file thats on your system of you installed dxo Photolab (and probably queried or installed at least a single lens module ).
Yes, there is/has been such a list for Mac. It was not quite correct and complete then, but maybe it has been fixed by now. Search the forum or use “easyfind” (devon tech.) or “find any file” (apple store) or use terminal.app and “find” (which is powerful, but hard to use imo) to search your Mac.
I have used MS Win 10 file explorer, starting with C: (top of the file system) and looked for a SQL file for DxO, including PL6. I have not been able to find such a file. On a MS Win system, what is the name of the lens module database file and what is the actual directory path (folder and subfolders, starting from C:) in which the file is stored, eg, C:/whatever ?
Wolfgang – thank you very much. I found the file, SQLlite opened it. I know have to figure out how to export the entire SQL database, not just one table, to a CSV file that I may open and browse in a spreadsheet application (I use LibreOffice for most things). A question: how often does using PL6E cause a query to the DxO server to update the local (C:/) CAFList6 file? (Presumably, PL7 will have a CAFList7 file, etc, into the future.)
Export the module table and replace the body id by the body name… from the body table. That’s a lot of work, but you might limit the table to the bodies you own or use.
The list is stored on your machine – per PL version. With that, why should DxO’s server be contacted, except when a unsupported camera-lens combination is detected and the user is going to download that ‘profile’?
There are two issues here.
(1) DxO has the needed module/s, the existence of these are in the database, but the actual module has not been downloaded to the platform on which the workflow is done.
(2) DxO has added support for cameras/bodies/lenses that are for PLn (n currently is 6), are in the current database file on the DxO server/s, but is not in the (now obsoleted) database file on the workflow platform.
You address (1) above. What about (2)?
note – while I know my way around, I’m no database specialist or else
In Windows with this configuration → (check box on)
I have it unchecked, but get notified as soon I hover the image in question to then decide …
