Hello!
Thank you for your work!

I have a question.
Is there any possibility that Radiant will be ported to Linux operation systems?
Like Ubuntu or else.

Thank you.

Hi,

I'm afraid that this won't happen soon... Please see this thread on linux subject: http://www.radiantviewer.com/dicom-viewer-forum/linux-version/220

Greetings,
Maciej

So, I tryed.

Old notebook
Ubuntu 12.04 LTS
Wine 1.4
radiant 1947257
It works fine BUT:
- crashes, when trying use ellipse
- after some time mouse wheel stops work (after reloading radiant - it`s OK)

So, it`s usable.

Maybe compiling radiant against winelib would help?

A

aaaaaaaaa

Maybe.
But I don`t undastend a word, what You just said =(^__^)=

I can't promise anything, but perhaps we could give it a try and build RadiAnt with wine.lib sometime.

Ubuntu 12.04 LTS
Wine 1.6.1
radiant 1.9.14
Everything works fine.

It works, but not everything (at least for me) - the labels with measurements are not visible.

Same here, everything works except the labels. . . so close to it being so good.

What dll do you use to draw the labels? Maybe one could use the original dll.

We had a quick glance at this issue, it looks like some problems with GDI+ calls in Wine. Can't promise anything, but we'll probably give it a try, sometime in the future.

Which labels don`t work?
And what hardware do you use?
I repeat

notebook Intel t2370 GMA X3100
Ubuntu 12.04 LTS
Wine 1.6.1
radiant 1.9.14
Everything works fine.

Lukash: You probably already had Tahoma font installed in the wine installation.

Maciej: I tried playing with installing Radiant in wine on CentOS. It works perfectly. The only thing missing were the labels for the measurement. I use PlayOnLinux for all my windows apps on Linux and I tried installing the native gdiplus.dll. That didn't help. I notice the labels are there, just too small and I thought that it would be a missing font. The first thing that helped was installing the Tahoma font.

Is it true? Do you use the Tahoma font for displaying the labels?
If so, adding a hint for Linux users that they need to install it would solve the constant questions on the forum regarding linux compatibility. Radiant would be the best dicom viewer for Windows AND Linux.

BTW: Although I had little interest in the PACS capability or anything similar, I would suggest adding Structured Reports and CE certification as the next features after PACS, because with that, hospitals could start considering licensing Radiant which could boost your sales and the second brother could concentrate more on development of Radiant.
I am actually not interested in PACS or SR, what I am waiting for eagerly are 3D reconstructions with various transfer functions etc. With your machine-efficient programming skills I am expecting a lot from your product.

Aaaaaaaaaaaa, you were right about the missing fonts:

sudo apt-get install ttf-mscorefonts-installer

...and the labels magically appeared :-)
Thanks for the tip, we'll add this info to the manual with the next update.

As for the 3D features, believe me, if we were developing just for our own pleasure, this functionality would be on the top of the list. However, I'm convinced that much more people will benefit form having the possibility to download studies from PACS locations. So, we all have to wait :-)

We need to bump this workaround! I've been struggling with missing annotations/measurements for _years_ (literally).

apt-get install ttf-mscorefonts-installer is the solution.

Tahoma is still required for measurements to appear!

TRUE, I REALLY LIKE THIS SOFTWARE, BUT THE USAGE IN LINUX HAS BEEN PAINFUL

The possibility to run RadiAnt on Linux is just a "collateral" of its simple Win32 architecture. It was never designed specifically for platforms other than Windows.

I think that this is the greatest thing about radiant. The simplicity.. zero reliance on external libraries, pure win32 application. How large is the exe? No need for java net framework and all the modern programming trends. The thing is, if wine had enough devs to support the latest CUDA, everything would work. If everyone who complained here about the app not working properly on Linux would buy cemrossover, they'd have enough funds to support radiant properly. So guys this might be the way ..

CUDA is supported in wine-staging branch, in CUDA version (as far as I remember) 9.1, implemented by Sebastian Lackner ( https://github.com/slackner ), it was compliant with RadiAnt 4.6.5.
That's the guy who should be paid to implement current CUDA.


I'm the maintainer of RadiAnt on Wine AppDB, and according to my tests currently:
1) Missing measurements - there is known workaround, msttcorefonts.

2) Some windows are popping under instated of popping up - quite random bug, (GDI related?) very difficult to track, might be in wine, might be in Radiant, i somehow feel it might be related to the fact that in Radiant the window pop up (like download) might be binded to mouseDown event, which could be invoked before mouseClicked, which turns the window focus back to main window instantly (You can see the popup for a while and then it goes under the main window), it happens more often it the load of the computer is low.

I really don't know where to start here with debugging.
Wine bug #45544

3) Export to wmv (wine bug #48339 ) and mp4 (wine bug #48340 ) is simply not implemented, I've tried to fix with winetricks - does not work : (.

4) CUDA - as above, bugs #46008 and #46358. What Radiant team could potentially help here is to give us CUDA version linked to lower CUDA version, unless there are some features used that are only available in recent CUDA, and call it wine-friendly build.

5) I also haven't managed to invoke radiant from radiant:// URI, but I haven't tried to register any other wine app to URI.

That's ALL I've found - in my opinion that's not much, radiant is pretty usable in wine, I won't call it painful.
I'm currently rating RadiAnt silver under wine.

New RadiAnt issue under Linux

Hello, I'm currently unable to install 64 bit RadiAnt in my wine - despite changing to 64 bit it installs as 32 bit (in 32 bit directory), I'm able to pick 64 bit bit it is ignored in installer.

Any ideas what's wrong?
It came with new versioning system.

Boskar, what is your command line?

I ran wine64 RadiAnt-2020.1-Beta-37400-Setup.exe and encountered no problem.
I run the default wine (4.0.2) on Ubuntu 19.10.

what command line did you use?

Tried both
env WINEPREFIX="/home/boskar/.wine-radiant" /opt/wine-staging/bin/wine Pobrane/RadiAnt-2020.1-Beta-37400-Setup.exe
env WINEPREFIX="/home/boskar/.wine-radiant" /opt/wine-staging/bin/wine64 Pobrane/RadiAnt-2020.1-Beta-37400-Setup.exe


boskar@pauper:~$ /opt/wine-staging/bin/wine64 --version
wine-5.0-rc1 (Staging)
root@pauper:~# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux bullseye/sid"

Sorry boskar, I checked again, the installer only installs 32 bit version under Linux. It works fine under Windows.

PROCESSOR_ARCHITECTURE is correct (AMD64). So I do not know what method the installer uses to tell if it can install 64 bit. We need to modify this parameter in wine.

Boskar, I found a workaround, parallel to the command line to unpack ARM64 files from the installer, you can run:

WINEARCH=win64 WINEPREFIX=~/.yourprefix wine64 RadiAnt-2020.1-Beta-37400-Setup.exe /S /BITS=64

and the 64 bit version will be installed to ~/.yourprefix/drive_c/Program\ Files/RadiAntViewer64bit/

I hope this helps.

Boskar I guess this has something to do with the addition of ARM64 binaries to the installer, I think that changed the detection to support this.

So I guess the NSIS x64.nsh script will be the place to search for the thing that does not work in wine.

We'll look into the installer script before a general release is ready.

Ok guys, it seems we have nailed it. The next beta installer will install 64-bit properly.

@Radiant - thanks!

Please check the latest RadiAnt DICOM Viewer 2020.1 BETA #37581

I am able to convert it into WMV within linux (currently on PopOS 18.04 LTS. It has to be installed in a 32 bit environment (64 will work and open Dicom images but somehow only 32 bit can export into movies. Use AND MODIFY the following command to install (change "username" to your login and ".radiant32" to where you want to install the wine prefix

env WINEARCH=win32 WINEPREFIX="/home/username/.radiant32/" wine RadiAnt*-Setup.exe

Runwine tricks and make sure to install the following components (I can make it work with these):
- wmp9
- wmv9vcm
- wsh57 (autoinstalled?)

It should output a WMV from a cine DICOM file. To convert it to mp4, install ffmpeg and run this command in the directory where you output the WMV files:

for i in *.wmv; do ffmpeg -i "$i" -s svga "${i%.*}.mp4"; done; rm *.wmv

Remove the last syntax "; rm *.wmv" if you want to keep the original WMV file.

Cheers!

@Radiant

I was wondering what dependencies/windows DLL/component are needed to directly convert the DICOM images/video to MP4 for wine? I could do directly with the above script using ffmpeg but it would be wonderful if I could convert directly to MP4.

Also the annotation choices Full/Basic/Anonymous does not seem to work in the recent versions and just outputs the full annotation instead.

Thanks!

https://bugs.winehq.org/show_bug.cgi?id=48339

wmvcore.dll for WMV

https://bugs.winehq.org/show_bug.cgi?id=48340

mfplat.dll for MP4.

I've tried some winetricks few months ago, no luck.
Kind regards - Your (lazy one) package maintainer.

I've been able to output WMV successfully on the latest Manjaro GNOME and latest stable RadiAnt viewer (at the time of this post) with the above method using a 32bit architecture install and by installing wmp9 and (maybe) wmv9vcm via winetricks.

I have encountered mfplat.dll issues before and there was this post in protondb (https://www.protondb.com/app/883710) for an unrelated game that helped me resolve compatibility issues. I want to try to apply the same method to the wine container that RadiAnt runs in. I've successfully run games requiring this dll but the version requirement is a bit fickle (from a gaming standpoint).

The mfplat.dll is a file that can be found within Windows itself so extraction shouldnt be difficult. The problem is, if you do not own a Windows 7/10 license, you may not be able to source it legally.

This will probably also require some codecs. Hopefully I can make it work and figure out which ones are needed. I will post soon.

@boskar

The mfplat.dll replacement trick didnt work. There was already an existing mfplat.dll on the Wine container and replacing it just threw an error but continued to run anyway. MP4 output still didnt work.

How did you get that mfplat error anyway?


Any hints @RadiAnt?

What dependencies/windows DLL/component are needed to directly convert the DICOM images/video to MP4 for wine?

It was probably WINEDEBUG=+all

as described here: https://wiki.winehq.org/Wine_User's_Guide#WINEDEBUG.3Dchannels - You could do it more precisely, but it was good enough

mfplat.dll and mfreadwrite.dll are required for mp4 creation.