But i wouldn't expect a similar compression advantage of a more extensive evaluation of compression parameters as FLAC achieves. Im most of my evaluations TAK's fast heuristics came very close to a brute force approach which tries most of the possible parameter combinations.
Quote from: marc2003 on 30 June, 2013, 09:28:03 PMtry foobar instead? that uses temporary filenames when encoding and then renames them when done. so it really doesn't matter whether the encoders support unicode or not.Just to note that i've converted from FLAC over 60 albums with Foobar till now and haven't experienced any problems with filenames using lots of (´ ` ~ ^ ç ...and so on) on the filename characters, it converts everything flawlessly. So maybe it really depends how the applications pass the original names to the *.tak destination file or how they use the pipe for that matter.
try foobar instead? that uses temporary filenames when encoding and then renames them when done. so it really doesn't matter whether the encoders support unicode or not.
You guys should tell the author of CUETools to start using tak_deco_lib.dll instead of piping Takc.exe's decoded output; that way, at least its verification features will not be hindered by TAK's inability to handle Unicode characters (the decoding library should have no problems handling them so long as CUETools doesn't -- this can also be observed with foobar2000's playback component).
Wine is a *really* heavy dependency to run takc (since I only use Linux). My concern is convenience, rather than ideology.
Quote from: eternaleye on 13 July, 2013, 06:03:56 AMWine is a *really* heavy dependency to run takc (since I only use Linux). My concern is convenience, rather than ideology.Heavy, how? Sure, the Arch Linux package is about 33MiB, but my ADSL line is fast enough that it doesn't bother me. It runs fast too, and doesn't seem to use too much RAM. With caudec, convenience is one of the things that I was aiming at. It makes encoding and decoding TAK files very fast and easy.
I want to thank the author, TBeck for his great work! On the Linux question, I can suggest something, yes?Has anyone tried if foobar with the the latest 2.3.0 tak decoding AND encoding work without error in Crossover 12 instead of Wine on Linux Mint or Ubuntu?That may be a way to run Tak in 64-bit Linux with least amount of unnecessary dependencies.Ive switched to Linux, too on almost all my computers but I haven't tried audacity or foobar on Linux in this way because I am still using an XP computer for audio. Perhaps somebody here has done this?
TBeckThomas, please make a 64-bit version of the library tak_deco.lib.
I love this programme, thanks you much.
I just installed on Windows7 latest 64 build and it only uses 4 cores and 8 threads where 6 cores and 12 threads are available. Is there an adjustment I can make, or a programme default?
I just finished moving my audio library (~20k files, 254GB in flac + metadata) to tak. Using the maximum preset, TAK was able to shave off 12GB!Some might say it's pretty insignificant if you look at HDD prices, but for me it's more than enough to justify moving to it as my archiving/pc listening format. One major annoyance is still present though - lack of unicode support. foobar2000/TAC/CUETools did work around filenames with foreign characters by using temporary filenames, but they can't do anything about paths with foreign characters (I'm actually surprised playback works). Those albums had to be handled manually, of course. And will have to every time I attempt to i.e. verify their integrity against CTDB.I'd be really, really, really grateful, if unicode support became a priority for the next release.
One major annoyance is still present though - lack of unicode support.
hope you're doing well.