Olympus Workspace - Linux install

[mchnz]

Out of curiosity I found that Olympus Workspace can be installed under Linux by using a Wine 64 bit configuration:

WINEARCH=win64 WINEPREFIX=~/.wine64 winecfg
WINEPREFIX=~/.wine64 wine ~/Download/OWSetup_64bit.exe

It mostly seems to work just fine. But when I try to export from RAW to jpg it errors. This maybe because it appears to try to load an OpenCL dll/so, which isn't built into OpenSUSE's build of wine. Does anyone using Linux have a 64 bit Wine installed that includes OpenCL (/usr/lib64/wine/opencl.dll.so) and would like to test OW exports?

A 32 bit OW install fails with an error "Your PC does not meet the operating system requirements for the application". Which is why I'm using the OW 64 bit install.

Previously I had successfully got OV3 working under Linux wine 32 bit. Described here:

https://appdb.winehq.org/objectManager.php?sClass=version&iId=28178

OV3 also seems to want OpenCL, but only if the GPU is to be enabled. OV3 can export without OpenCL.

At some point I'll probably try and build OpenCL for 64 bit Wine or figure out why the 32 bit OW install is failing.

At the moment neither OV3 or OW is part of my normal PP workflow, but I sometimes think I'd like to be able to play with the art filters or the Olympus RAW processing engine.

 

[olyhibi]

Out of curiosity I found that Olympus Workspace can be installed under Linux by using a Wine 64 bit configuration:

WINEARCH=win64 WINEPREFIX=~/.wine64 winecfg
WINEPREFIX=~/.wine64 wine ~/Download/OWSetup_64bit.exe

It mostly seems to work just fine. But when I try to export from RAW to jpg it errors. This maybe because it appears to try to load an OpenCL dll/so, which isn't built into OpenSUSE's build of wine. Does anyone using Linux have a 64 bit Wine installed that includes OpenCL (/usr/lib64/wine/opencl.dll.so) and would like to test OW exports?

A 32 bit OW install fails with an error "Your PC does not meet the operating system requirements for the application". Which is why I'm using the OW 64 bit install.

Previously I had successfully got OV3 working under Linux wine 32 bit. Described here:

https://appdb.winehq.org/objectManager.php?sClass=version&iId=28178

OV3 also seems to want OpenCL, but only if the GPU is to be enabled. OV3 can export without OpenCL.

At some point I'll probably try and build OpenCL for 64 bit Wine or figure out why the 32 bit OW install is failing.

At the moment neither OV3 or OW is part of my normal PP workflow, but I sometimes think I'd like to be able to play with the art filters or the Olympus RAW processing engine.

I also got it working to the same point (raw export fails). I used Playonlinux to install OW 64bit (windows version = windows 7) and had to manually add mfc100u.dll to windows\system32 to be able to start the program.

I have a 64bit system (Linux Mint 18.3 mate) with wine 1.8 (from external source) and opencl.dll.so installed.

Still the same problem.

I also got OW 32bit starting, but when opening a hi-res raw file, it said "hi res raw files only supported on 64bit systems" - so I deinstalled it, because that's why I'm wanting to use OW.

Any success with the 64bit version?

 

[mchnz]

I've registered it at WineHQ. Once that makes it through registration, we might eventually get lucky and someone who knows more about debugging Wine apps might one day become interested. A bit of a long shot of course.

 

[ibd]

Now that we can have the E-m1 II and E-m1x do the RAW processing in-camera with firmware 3.0, is there actually a viable linux workflow?

 

[mchnz]

Now that we can have the E-m1 II and E-m1x do the RAW processing in-camera with firmware 3.0, is there actually a viable linux workflow?

I don't think that's likely with Wine. I think the RAW processing protocol is based on PTP or PictBridge, which I don't think Wine can access/use. I see that Workspace runs one of it's plugins called FNP_CameraRawDev.ofnp, which fails to find the camera. BTW, the export picture function still fails to function on this new version of Workspace.

I'd be willing to bet that a true version of Windows running in Virtualbox would likely work pretty well, but I'm not really that interested in going down that path. If someone would like to test that, I think there is a Microsoft site that provides limited term licensed images of it's operating systems for for developers to use for testing purposes that will happily run in a virtual machine such as vbox (in reality I've read you can use VM snapshots to work around the limited term).

I guess the RAW development protocol could probably be reverse engineered (if that's legal in your country). But that would be a lot of work.

If Olympus would be willing to open up the protocol it would be really interesting. They might even be able sell more bodies as PC/tablet/phone peripherals. Or perhaps even market some less expensive black box to do the job.

 

[rybu]

I far prefer running Windows in a virtual box. If you go down this road:

(1) Install Oracle's VirtualBox on your system. i.e. don't use the pre-packaged distributions that come with OSes like Ubuntu. This allows you to install...

(2) Oracle's extensions. Which allows you to use your USB ports through Virtualbox.

Once you have those two running, you should be able to upgrade your firmware and use Olympus Workspace without any issues.

 

[Felice62]

I far prefer running Windows in a virtual box. If you go down this road:

(1) Install Oracle's VirtualBox on your system. i.e. don't use the pre-packaged distributions that come with OSes like Ubuntu. This allows you to install...

(2) Oracle's extensions. Which allows you to use your USB ports through Virtualbox.

Once you have those two running, you should be able to upgrade your firmware and use Olympus Workspace without any issues.

I have been using DxO in a virtual Windows 10 environment under Ubuntu 18.04 with no hassle, through virtualbox

 

[Teuchter G]

Now that we can have the E-m1 II and E-m1x do the RAW processing in-camera with firmware 3.0, is there actually a viable linux workflow?

I've been using Olympus on Linux for 5 years now via Corel Aftershot Pro with no problems. I've also used Darktable successfully with my Pen, OMD E-M5ii and E-M1i.

Is there a Linux issue I've not heard of before? Curious...

PS. For "serious editing" I also have a Windows PC with DxO Photolab/Nik and Affinity Photo (& Publisher) installed but that's only used for professional work where I need a fully colour managed solution - I can't get any of the colour management suites to work with Linux apps...

 

[mchnz]

Now that we can have the E-m1 II and E-m1x do the RAW processing in-camera with firmware 3.0, is there actually a viable linux workflow?

I've been using Olympus on Linux for 5 years now via Corel Aftershot Pro with no problems. I've also used Darktable successfully with my Pen, OMD E-M5ii and E-M1i.

Is there a Linux issue I've not heard of before? Curious...

The issue would be no native access to Olympus's software via Wine. It's certainly not a major issue for me, but it would be nice to be able to play with all of what Olympus offers. Wine+OV3 works for editing, but not Wine+Workspace.

It also seems an interesting idea to use a camera body as a desktop peripheral for RAW development, much like the boxed GPU's. Perhaps RAWS could be developed on a PC at several frames per second. Perhaps in some surreal future It might be possible to shoot DNG's in a Panasonic body and then PP them on the desktop with an Olympus body.

PS. For "serious editing" I also have a Windows PC with DxO Photolab/Nik and Affinity Photo (& Publisher) installed but that's only used for professional work where I need a fully colour managed solution - I can't get any of the colour management suites to work with Linux apps...

I have no requirement to take photography seriously

Digikam does almost everything I need as a jpeg shooter. But I do feel I have to retain a WindowsXP laptop to do firmware updates in a supported manner for items under warranty.

 

[digidownunder]

It will spoil your love of doing photography for nothing. That,s after 29 yrs as a pro mind you.

 

[digidownunder]

It will spoil your love of doing photography for nothing. That,s after 29 yrs as a pro mind you.

Somehow I put this in the wrong thread .Sorry

 

[madmalkav]

Have anyone tried again to run the new 1.1 version of Workspace with WINE?

 

[mchnz]

Have anyone tried again to run the new 1.1 version of Workspace with WINE?

Yes, but it's functionality is pretty much the same - which is to say it still has the previously reported problems.

More progress might be possible If there was a way to tease out more debugging about what WS is trying to do when it runs batch processes. I know next to nothing about Windows batch commands, it may be as simple as discovering which Windows components are missing and adding them.

In terms of accessing the camera, I don't think Wine has easy access to the camera USB device - at least I couldn't find much on how to achieve that.

For USB access to the camera's raw processor the best bet would be to use some version of Windows in a virtual box. Even then, I wouldn't want to be the first one to try a firmware upgrade. I keep an old Windows XP laptop for that. As soon as Oly officially support SD card upgrades I'll retire the laptop.

 

[Felice62]

Have anyone tried again to run the new 1.1 version of Workspace with WINE?

Yes, but it's functionality is pretty much the same - which is to say it still has the previously reported problems.

More progress might be possible If there was a way to tease out more debugging about what WS is trying to do when it runs batch processes. I know next to nothing about Windows batch commands, it may be as simple as discovering which Windows components are missing and adding them.

In terms of accessing the camera, I don't think Wine has easy access to the camera USB device - at least I couldn't find much on how to achieve that.

For USB access to the camera's raw processor the best bet would be to use some version of Windows in a virtual box. Even then, I wouldn't want to be the first one to try a firmware upgrade. I keep an old Windows XP laptop for that. As soon as Oly officially support SD card upgrades I'll retire the laptop.

 

[mchnz]

Out of curiosity I found that Olympus Workspace can be installed under Linux by using a Wine 64 bit configuration:

WINEARCH=win64 WINEPREFIX=~/.wine64 winecfg
WINEPREFIX=~/.wine64 wine ~/Download/OWSetup_64bit.exe

It mostly seems to work just fine. But when I try to export from RAW to jpg it errors. This maybe because it appears to try to load an OpenCL dll/so, which isn't built into OpenSUSE's build of wine. Does anyone using Linux have a 64 bit Wine installed that includes OpenCL (/usr/lib64/wine/opencl.dll.so) and would like to test OW exports?

A 32 bit OW install fails with an error "Your PC does not meet the operating system requirements for the application". Which is why I'm using the OW 64 bit install.

Previously I had successfully got OV3 working under Linux wine 32 bit. Described here:

https://appdb.winehq.org/objectManager.php?sClass=version&iId=28178

OV3 also seems to want OpenCL, but only if the GPU is to be enabled. OV3 can export without OpenCL.

At some point I'll probably try and build OpenCL for 64 bit Wine or figure out why the 32 bit OW install is failing.

At the moment neither OV3 or OW is part of my normal PP workflow, but I sometimes think I'd like to be able to play with the art filters or the Olympus RAW processing engine.

An update...

Today I found that my existing install of OV3 2.3 can now export edited RAW files to jpeg. I suspect it had something to do with updating to Wine 5.15, but the following software versions are in play:

• OpenSUSE Tumbleweed 20200817
• OV3 version 2.3
• Wine 5.15
• Kernel 5.8
• Nvidia proprietary driver 450.57

Without the GPU enabled the export was very slow, it felt like it took about a minute and drove all CPU's to 100%. With the GPU enabled an export took 20 seconds, CPU consumption was much lower, the GPU clock rose a bit but was not heavily stressed.

My desktop hardware is as follows:

• CPU AMD FX(tm)-6300 (6 cores)
• System RAM 16 GB
• Nvidia GTX 1650 Super 4GB
• User storage SSD Samsung 860 1GB
• OS storage is an Samsung 850 250MB

There is no camera connectivity via Wine (I think it lacks native USB access).

At this level of performance OV may be good enough for playing around with the odd filter or the odd RAW tweak, but it isn't going to be something I'd want to use on a daily basis.

(BTW Olympus Workspace still cannot export RAWs - I got a bit excited when OV3 managed to use the GPU, but sadly OW is still misbehaving).

--
https://www.flickr.com/photos/digitaltrails
https://michaelhamilton.smugmug.com