User Tools

Site Tools


doc:appunti:hardware:olympus-e-m10:olympus_workspace_on_linux

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
doc:appunti:hardware:olympus-e-m10:olympus_workspace_on_linux [2022/12/20 18:13] – [Exporting RAW images to other formats] niccolodoc:appunti:hardware:olympus-e-m10:olympus_workspace_on_linux [2022/12/27 17:23] (current) – [Running the program in Wine] niccolo
Line 54: Line 54:
 If you don't configure the emulation environment using **winecfg**, you could get the following error message from Wine **//Cannot install this software in this PC. Your PC does not meet the operating system requirements for the application//**. If you don't configure the emulation environment using **winecfg**, you could get the following error message from Wine **//Cannot install this software in this PC. Your PC does not meet the operating system requirements for the application//**.
  
-So start the **configuration program** with:+So start the **Wine configuration program** with:
  
 <code> <code>
Line 61: Line 61:
  
 Then select **Applications** => **Windows Version** => "**Windows 10**" Then select **Applications** => **Windows Version** => "**Windows 10**"
 +
 +Then you have to download and install the **MSXML6.DLL** library and its dependencies (this is the CLSID 88d96a05-f192-11d4-a65f-0040963251e5); the easiest way is to use the **winetricks** tool (provided by the homonymous Debian package):
 +
 +<code>
 +WINEPREFIX=~/.wine64 winetricks msxml6
 +# Manual registration of MSXML6 not actually required.
 +# WINEPREFIX=~/.wine64 regsvr32 msxml6
 +</code>
  
 To **install** the Olympus Workspace program, run: To **install** the Olympus Workspace program, run:
Line 86: Line 94:
 As explained above, the native //Export// function (right-click on the thumbnail) of the program does not work in Wine. If you have installed an application which is registered with the **tif** extension, you can choose the menu **Photos** => **Launch registered application**. As explained above, the native //Export// function (right-click on the thumbnail) of the program does not work in Wine. If you have installed an application which is registered with the **tif** extension, you can choose the menu **Photos** => **Launch registered application**.
  
-You can download the free (but not open source) IrfanView program and install it unde the Wine environment. The default setup procedure will register the application as the handler for TIFF images into the emulated Windows 10 environment:+You can download the free (but not open source) **IrfanView** program and install it in Wine. The default setup procedure will register the application as the handler for TIFF images into the emulated Windows 10 environment:
  
 <code> <code>
-env  WINEPREFIX=".wine64wine-stable Download/iview462_x64_setup.exe+WINEPREFIX=~/.wine64 wine ~/Downloads/iview462_x64_setup.exe
 </code> </code>
  
 **WARNING**: After you have applied all the required changes to the RAW image, be sure to click over the image thumbnail itself; this will force OM Workspace to register all the changes applied to that image (there is not an actual //save// function when processing a RAW file, since every step can be reverted). Only in this way will you be sure that the image passed to the external registered application will be the processed one, otherwise the exported image will not contain the latest applied effects. **WARNING**: After you have applied all the required changes to the RAW image, be sure to click over the image thumbnail itself; this will force OM Workspace to register all the changes applied to that image (there is not an actual //save// function when processing a RAW file, since every step can be reverted). Only in this way will you be sure that the image passed to the external registered application will be the processed one, otherwise the exported image will not contain the latest applied effects.
  
-OM Workspace saves a copy of the image (in TIFF format, not compressed RAW, 16bit per RGB channel) into the ''$HOME/OM Workspace/'' directory and opens it with the registered program. If the registered image is **IrfanView** (as suggested) you have the opportunity to **save the image as JPEG** or other formats. Beware that every time you choose the //Launch registered application// function, a new copy of the image will be saved into ''$HOME/OM Workspace/'', and these images have a considerable size!+When you click the menu //Photos// => //Launch registered application//, OM Workspace saves a copy of the image (in TIFF format, not compressed RAW, 16bit per RGB channel) into the ''$HOME/OM Workspace/'' directory, so this is eventually sufficient to export the developed image. If you have installed **IrfanView** (or other similar application) you have the opportunity to **save the image as JPEG** or other formats. Beware that every time you choose the //Launch registered application// menu, a new copy of the image with a different timestamp name will be saved into ''$HOME/OM Workspace/''these images have a considerable size!
  
 OM Workspace can apply to a RAW file (in post-production) almost all the effects that the E-M10 can do in-camera, plus many others. However the result will not be an exact bit-by-bit copy of the JPEG eventually produced in-camera, the most notable difference is in the Exif tags. OM Workspace can apply to a RAW file (in post-production) almost all the effects that the E-M10 can do in-camera, plus many others. However the result will not be an exact bit-by-bit copy of the JPEG eventually produced in-camera, the most notable difference is in the Exif tags.
doc/appunti/hardware/olympus-e-m10/olympus_workspace_on_linux.1671556400.txt.gz · Last modified: 2022/12/20 18:13 by niccolo