I know the topic of running DOpus on WINE/Linux has been discussed multiple times, and the general advice is "it might work but it is unsupported." I understand.
That being said, I've gotten the latest version (12.21) running quite easily under Crossover (also the v19.02), and it seems to work generally well. There's just one (hopefully easy) caveat, so I was hoping someone might be able to chime in.
Some filetypes work great - for instance, jpgs display with thumbnails & media columns, & can be opened in Linux's current photo viewer - but the majority of others show in DO as as "text" icons, and when double clicked, just show binary. They don't seem to be recognized as a filetype. On native Windows, I would usually solve this via right click->Open With, but under wine, that has no effect. I do see that there's the Settings->File Types dialog, but creating new ones individually for each filetype - I'm not really sure how, & it seems like each filetype has a million options, & there are also a million filetypes to be handed.
Any thoughts or ideas would be greatly appreciated
Edit: I've found that if I simply duplicate the "Jpeg" option in that dialog, & edit the "extension" & "Mimetype," that fixes it & allows me to open those files (i.e. if I duplicate jpeg & change the copy to .mp4 & video/mpeg, it lets me launch & view videos in the native external video player).
However, one remaining issue: none of the media columns work. aka DO is not able to extract frame rate, data rate, etc from videos. Presumably this requires installing some other dependency in the same wineprefix - what might that be, i.e. what does DO use for pulling that info out of media files & displaying it?
Is there any way to get a direct response from the D.O. folks?
I'm fully interested in purchasing the paid version - if I can get the media columns to work. However, it seems like they often don't respond here on the forum. My sole reason for hoping to use this on Linux is because none of the available native Linux file explorers seem to provide extensive support for media metadata (i.e. in Details view, showing info like video bitrate, frame size, framerate, etc). However, there's not much sense in buying if I can't get that feature working - and not much hope in getting it working if I can't get a response
Do you know what elements of the underlying Windows OS D.O. is leveraging to populate those media columns? That could possibly indicate what components of Windows are missing or I need to explore in order to try & get it working myself.
EDIT: I started responding to Leo's response below, but he instantly closed this thread making it impossible to even reply. Seems like there's an almost odd or angry aversion to anything WINE-related. In any case, since he won't let me properly reply, I can just edit my previous post & add the reply here - this is how I'd intended to respond to his reply below:
Linux and Windows are too different to run a Windows filemanager
Actually, it's working just fine so far - not showing the media columns is the sole thing I've noticed not working (presumably because it's trying to use a particular underlying Windows service to pull out the metadata, & that service hasn't been installed in this wine prefix).
it doesn't really make sense.
I would respectfully disagree. It might be difficult or not instantly automatic, but it makes perfect sense in that there are users of Linux who would like to benefit from certain software that's available on Windows (whether that happens to be a file manager or otherwise). Just because something was originally developed for one OS doesn't mean that it's illogical to run it through a compatibility layer on another - doing so just might require some extra considerations (i.e. differences in case sensitivity). Making "Windows components and APIs" available is precisely the purpose of WINE, which grows more complete every year. i.e. I'm currently running full MS Office, which relies heavily on various Windows components. I don't think there's anything special about a file manager that makes it nonsensical to benefit from this type of compatibility layer.
Get Windows Media Player to play the files in question first, then worry about Opus.
But WINE is absolutely not supported, so we can't and won't answer questions on it anyway. As neat as WINE is for some things, we don't want to encourage people to use WINE to run Opus, as it doesn't really make sense. Linux and Windows are too different to run a Windows filemanager (which will assume local filesystems behave according to Windows rules, and that Windows components and APIs are available) on a Linux OS.