Could you change the low priority process function into that I could specific what level I want in the next version?
I find a little question in the 1.1.1beta version, the encoded file by 1.1.1beta version is be identified as 1.1.0 in foobar2000.I use foobar2000 0.9.6.3 beta1 and foo_input_tak.dll 0.4.2, maybe foo_input_tak.dll need to rebuild for this new version?
TBeck I am really impressed with TAK but I am reluctant to use it because of it being closed source. I read some time ago that you were planning to license the source under a permissive license once the code was cleaned. Is there any progress regarding that?
Code being free generally ensures longevity, because although you (and me) don't write code, almost certainly someone who can, can pick it up, keep it up to date, port it to other, newer systems, etc. In 20 years from now it's quite possible Thomas will have lost interest and we no longer use Windows on x86 machines. If the source is open, anyone who can code and has an interest can port it to whatever system he choses so that you can keep decoding your music (and encoding).
aliumalik +1I still follow tak development, but I will use flac as long as tak is closed.For pure compression/storage, I prefer to buy a new HDD than using a closed codec.I only wish I could enjoy tak's speed/compression improvement over flac.
Sigh... Every time there's a new TAK topic, someone has to bring this up...Thomas will release the source when he thinks it's the right time, this was discussed in EVERY single TAK topic.This is getting a little old don't you think?
... and everytime there is a new release it is not the right time ... sorry I have been following tak since the time it was called yalac so I have been waiting a long time ... I have been more than patient ... I recall a time when monkey audio developper was telling that he would maybe release the code ... specially as third party software developpers were asking him to do so ... it never happened ... (the source is available but the license is ... weird)
always telling: "later" is a clue that tak doesn't share the way of thinking of free software ... who care if it's bugged as long as it is instantly fixed ... free software developpers release opensourced code specially to find bugs ... the more eyes see the code, the less buggy is the code ...
years ago Tom had an excuse ... he was not releasing the code because he wanted to write a research/scientific article about his new technology & be the first to publish...at time this was a very valid excuse to me ...I never saw the article, I never saw the code ...I am not crying for the code, I am only pointing the lack of honesty ... if Tak is closed source software, so be it, but plz tell it openly ... so that I don't long for more & that I can pass my way when I see a new Tak release.
Educate me. Why are you reluctant to use TAK in its current form/release?Are there people waiting in the wings wanting to improve it? Should I worry about some backdoor/malware? Some other reason?
Quote from: aliumalik on 16 February, 2009, 06:58:04 AMTBeck I am really impressed with TAK but I am reluctant to use it because of it being closed source. I read some time ago that you were planning to license the source under a permissive license once the code was cleaned. Is there any progress regarding that?Educate me. Why are you reluctant to use TAK in its current form/release?Are there people waiting in the wings wanting to improve it? Should I worry about some backdoor/malware? Some other reason?Just curious, because personally, I can't read code well enough for it to matter to me.
Thank you for adding Low Priority option, TBack Now, I'm waiting patiently for 1.1.1 to be finalized, and then I'm going to migrate to TAK.
I think people have given most of the reasons why I want it to be OSS. For me personally ...
Could you please try, if the low priority setting fits your needs?
TAK already stores a 24-bit checksum for each and every frame, so this should not serve as a reason to re-encode.
So how does this compare to lossless formats like flac? does it encode smaller files?
If you use pipe decoding and the application reading the pipe is beeing terminated before the whole file has been read, TAKC may get into an endless loop and has to be manually killed with the task manager.