Linux version of NI
Linux version of NI
I would really like to see a Linux version of NI. Unfortunatly I couldn't find any information about that.
Don't think, that linux users would not pay for software. I would like to do so.
And since NI is mostly an algorithmic tool, this should not be impossible, should it?
take care, have fun
/christian
Don't think, that linux users would not pay for software. I would like to do so.
And since NI is mostly an algorithmic tool, this should not be impossible, should it?
take care, have fun
/christian
Christian,
Thank you for your comments.
Yes, it is would be very nice to have a Linux version of NI right now, immediately. However, you probably understand that developing a version of the software for every new platform is not easy in itself. Even if NI may give an impression of an algorithmic tool, the major part of the source codes are things not directly related to image processing (I/O, GUI, etc.). These things should be significantly changed when a port if made.
Also, even if there are Linux people who would pay for the software, lets face the fact that the Linux platform is not the most popular in digital imaging; Windows and Mac go first, then (maybe) Linux. Just facts: people ask us to provide a Mac version of NI 25 times more often that a Linux version. Therefore it is quite logical that a Mac version stands in our development plans much closer that a Linux version. We want to produce all these versions, and we will most likely will do that in the future.
Thank you once again for your suggestion. I believe that one day, it will be implemented.
Vlad
Thank you for your comments.
Yes, it is would be very nice to have a Linux version of NI right now, immediately. However, you probably understand that developing a version of the software for every new platform is not easy in itself. Even if NI may give an impression of an algorithmic tool, the major part of the source codes are things not directly related to image processing (I/O, GUI, etc.). These things should be significantly changed when a port if made.
Also, even if there are Linux people who would pay for the software, lets face the fact that the Linux platform is not the most popular in digital imaging; Windows and Mac go first, then (maybe) Linux. Just facts: people ask us to provide a Mac version of NI 25 times more often that a Linux version. Therefore it is quite logical that a Mac version stands in our development plans much closer that a Linux version. We want to produce all these versions, and we will most likely will do that in the future.
Thank you once again for your suggestion. I believe that one day, it will be implemented.
Vlad
Hi,
But:
Today I successfully ran NI(demo) using wine under Linux. Hopefully the Home/Pro version runs with wine, too.
So, thank you very much about offering such a great tool!
take care, have fun
/christian
Hmm, to be honest, I don't know why you develop diff'rent versions for every platform. How about using smth. like QT as a windowing toolkit, so you could maintain only one version of code. This certainly is cheaper then maintaining 2 or three platforms seperately.NITeam wrote: However, you probably understand that developing a version of the software for every new platform is not easy in itself. Even if NI may give an impression of an algorithmic tool, the major part of the source codes are things not directly related to image processing (I/O, GUI, etc.). These things should be significantly changed when a port if made.
Yeah, the gimp is not a real alternative to Photoshop, if you don't think about the price .NITeam wrote: Also, even if there are Linux people who would pay for the software, lets face the fact that the Linux platform is not the most popular in digital imaging;
Yes, I see, that sounds quite bad.NITeam wrote: Windows and Mac go first, then (maybe) Linux. Just facts: people ask us to provide a Mac version of NI 25 times more often that a Linux version. Therefore it is quite logical that a Mac version stands in our development plans much closer that a Linux version. We want to produce all these versions, and we will most likely will do that in the future.
But:
Today I successfully ran NI(demo) using wine under Linux. Hopefully the Home/Pro version runs with wine, too.
So, thank you very much about offering such a great tool!
take care, have fun
/christian
You are right and in fact, we are already looking into this direction.schlupp wrote: Hmm, to be honest, I don't know why you develop diff'rent versions for every platform. How about using smth. like QT as a windowing toolkit, so you could maintain only one version of code. This certainly is cheaper then maintaining 2 or three platforms seperately.
It should run fine, we heard about this earlier from other Linux users.schlupp wrote: Today I successfully ran NI(demo) using wine under Linux. Hopefully the Home/Pro version runs with wine, too.
Vlad
NeatImage under WINE
Unfortunately, I could not get NeatImage 2.21 Pro edition to run under WINE (20030115 release). Version 2.1 demo edition does work though, so I suppose there is some hope there. I'll have to fiddle with this some more.
Yeah, winedbg comes up with:
Yes, please send to my profile address (the file itself or a URL to download it). Thanks!
Code: Select all
Unhandled exception: illegal instruction in 32-bit code
NeatImage.exe.@@Profileviewerform@Finalize+0x3ba5: xorps %xmm0,%xmm0
I don't know enough about WINE, but I'm pretty sure that they will eventually add support for SSE (and 3DNOW and whatever other extended CPU instructions sets are out there). I am running the latest non-CVS snapshot of WINE (20030115), so SSE instructions aren't support yet.
In the meantime though, NI 2.13 Pro seems to work fine under WINE!
In the meantime though, NI 2.13 Pro seems to work fine under WINE!
Oh yeah, baby... that did the trick. For FreeBSD 4.x users, add the line "options CPU_ENABLE_SSE" to your kernel config file and do a round of buildkernel/installkernel. I don't know how this is done with Linux, but someone else can chime in.
Once the kernel is installed, verify that SSE instructions are enabled:
You should see a "1" for that variable.
Once the kernel is installed, verify that SSE instructions are enabled:
Code: Select all
% sysctl -a hw.instruction_sse
hw.instruction_sse: 1