Dear Curtis,
of course I know about the licenses (we exchanged opinions several times about this topic). However, the differences in this respect between ImageJ-1 and ImageJ-2 (not to speak of Fiji) can't be denied and are even reflected by <http://imagej.net/Licensing>. However, licenses are not crucial for my preference of ImageJ-1. (Sadly enough, I don't have extremely advanced IJ-plugins to sell...) Thanks for the hint with the command line! I also found this hint on the web but it makes no difference. The problem appears to be more complex, at least for the Mac-platform. Best Herbie ::::::::::::::::::::::::::::::::::::::::::: Am 01.07.16 um 04:05 schrieb Curtis Rueden: > Hi Herbie, > >> I could not simply sell my extremely advanced IJ-plugins bundled with >> ImageJ-2, but I could with ImageJ-1. > > Actually, you can. See: > http://imagej.net/Licensing > > Commercial use is permitted, as is withholding the source. That is why the > BSD class of licenses are known as "permissive" licenses. > http://imagej.net/BSD > > We chose BSD for ImageJ2 because it was one of the most permissive possible > choices, so that the libraries could be used in all ways similar to ImageJ1. > >> java -jar /Applications/ImageJ/ij.jar -ijpath /Applications/ImageJ/ > -Djava.library.path=/Applications/ImageJ/libffmpeg.dylib >> doesn't work > > The java.library.path must point at directories, not files. > > Regards, > Curtis > > -- > Curtis Rueden > LOCI software architect - http://loci.wisc.edu/software > ImageJ2 lead, Fiji maintainer - http://imagej.net/User:Rueden > Did you know ImageJ has a forum? http://forum.imagej.net/ > > > On Thu, Jun 30, 2016 at 9:42 AM, Herbie <[hidden email]> wrote: > >> Dear Jan, >> >> evidently I can't take your reply too seriously but it is interesting that >> you care about my answer to a merely curious question of Adrian. >> >> 2. >> Maybe an OS is an application, maybe not. >> >> 1. >> ImageJ-1 lacks any licenses, ImageJ-2 doesn't. >> Of course there are IJ-PlugIns--that do not come preinstalled with >> ImageJ-1--that come with a more or less restrictive license, but I'm free >> to use or to avoid them. >> >> In fact, if I wanted to, I could not simply sell my extremely advanced >> IJ-plugins bundled with ImageJ-2, but I could with ImageJ-1. >> >> >> With respect to the more important FFMPEG-question I haven't been >> successful. >> >> The command line >> >> java -jar /Applications/ImageJ/ij.jar -ijpath /Applications/ImageJ/ >> -Djava.library.path=/Applications/ImageJ/libffmpeg.dylib >> >> doesn't work and I tried quite some other suggestions found on the web. I >> shall stop with this problem for now because it isn't relevant for me. >> >> >> Good day >> >> Herbie >> >> :::::::::::::::::::::::::::::::::::::::::: >> Am 30.06.16 um 15:44 schrieb Jan Eglinger: >> >> Dear Herbie, >>> >>> On 29.06.2016 20:21, Herbie wrote: >>> >>>> >>>> The answer is simple: >>>> First, I like lean solutions. >>>> Second, I like applications that are in the public domain. >>>> >>> >>> First, "public domain" is a concept that exists mainly in the US and is >>> nonexistent in other jurisdictions (sorry for the wording, I'm not a law >>> expert). Both ImageJ2 and Fiji are open source and under permissive >>> licenses. >>> >>> Second, I wonder why you're using a Mac, as OSX is obviously not in the >>> public domain. >>> >>> >>> My interest in integrating FFMPEG to ImageJ is minor, because personally >>>> I see no problem in converting videos by using one of the available free >>>> tools or by using FFMPEG from the terminal. Finally, I mostly deal with >>>> avi-files and don't need any video conversion. >>>> >>>> >>> Thanks for your contribution to this discussion. >>> >>> Jan >>> >>> >>> >>> >>>> :::::::::::::::::::::::::::::::::::::::::: >>>> Am 29.06.16 um 20:11 schrieb Adrian Daerr: >>>> >>>>> Dear Herbie, >>>>> >>>>> Does that mean it is impossible to use "libffmpeg.dylib" with ImageJ >>>>>> 1.x? >>>>>> >>>>>> Where does "FFMPEG_IO.jar" (which works) expect "libffmpeg.dylib" on a >>>>>> Mac? >>>>>> >>>>>> Apparently "1.6.0.jdk > Contents > Libraries" isn't the correct place. >>>>>> >>>>> >>>>> You may have to play with environment variables and/or use otool and >>>>> install_name_tool so that the libraries are found: >>>>> >>>>> http://www.chilkatforum.com/questions/4235/how-to-distribute-a-dylib- >>>>> with-a-mac-os-x-application >>>>> >>>>> http://superuser.com/questions/282450/where-do-i-set-dyld-library-path-on-mac-os-x-and-is-it-a-good-idea >>>>> >>>>> >>>>> >>>>> >>>>> https://developer.apple.com/library/mac/documentation/DeveloperTools/Conceptual/DynamicLibraries/100-Articles/UsingDynamicLibraries.html >>>>> >>>>> >>>>> >>>>> >>>>> Maybe a solution using FFMPEG as a compiled command line tool >>>>>> instead of >>>>>> platform-specific libraries would be a better solution but there may be >>>>>> reasons to not follow this straightforward approach. >>>>>> >>>>> >>>>> I'm just being curious: what are your reasons not to follow the other >>>>> straightforward approach of using Fiji (which, I am sure you know, Is >>>>> Just ImageJ, and which strives at being compatible with imagej 1) ? >>>>> >>>>> good luck, >>>>> Adrian >>>>> >>>>> >>> >> -- >> ImageJ mailing list: http://imagej.nih.gov/ij/list.html >> > > -- > ImageJ mailing list: http://imagej.nih.gov/ij/list.html > -- ImageJ mailing list: http://imagej.nih.gov/ij/list.html |
Free forum by Nabble | Edit this page |