Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Recent Posts
31
FLAC / Re: Multithreading
Last post by Replica9000 -
I haven't tried gasc mode much with flaccid.  One option that seems to make encoding painfully slow is the  --analysis-apod option. 

Turns out using that option makes flaccid a pretty good stress test tool.  I've recently built a new computer with a Ryzen 9900X (@ktf, I can test avx512 instructions if you decide to implement them).

I left the system on stock PBO, but wanted to undervolt to keep temps down.  The system passed tests using Prime 95, AV1 encoding and reference flac encoding.  However, when I fired up flaccid with high settings, the program crashed or the PC froze.   The current test has been running nearly two days, and at the current rate, might take a week or two (or more!) to finish.  I think I'll call you system stable at this point.



The current command:
Code: [Select]
flaccid_avx2_noasm --in NIN_The_Fragile.wav --out NIN_The_Fragile.flac --lax --workers 24 --mode peakset --peakset-window 300 --analysis-comp 8pr15l32m --output-comp 8pr15l32m --analysis-apod tukey(5e-1);subdivide_tukey(47/1);gauss(5e-1);welch;connes --output-apod tukey(5e-1);subdivide_tukey(47/1);gauss(5e-1);welch;connes --blocksize-list 128,256,384,512,640,768,896,1024,1152,1280,1408,1536,1664,1792,1920,2048,2176,2304,2432,2560,2688,2816,2944,3072,3200,3328,3456,3584,3712,3840,3968,4096,4224,4352,4480,4608 --merge 1 --tweak 1 --queue 4608



32
General Audio / Re: The "business model" of hybrid codecs with correction files
Last post by skamp -
To be perfectly clear, at least on UNIX-like operating systems, once a hard link to a file has been made, one can move either file (the source or the hard link) as much as they want, wherever they want, as long as it’s on the same storage device.

Each file (the source or the link) will keep pointing to each other, and modifying either file (like, say, tagging) will always affect the other file, wherever it is located. That’s because they’re really just a single file, with more than one path attached to it within the filesystem.

There is no difference between the “source” and the “link”: they’re the exact same file, just referenced with different paths. As opposed to a symbolic link, which is NOT a file.

With symbolic links, as soon as you move the source, the link breaks (unless the symlink is a relative path and the new location of the source remains compatible with that relative path).

I haven’t really used Microsoft Windows since 2002 so I have no idea about what it can do.
39
3rd Party Plugins - (fb2k) / Re: JSplitter (splitter + SMP x64 alternative)
Last post by LUR -
Quote from: regor on
Win 11 + foobar v1.6.18: Crash with 4.0 version as soon as a panel is added into layout or at foobar quit.
I have exactly the same thing. It happens only with 1.6.18 and only in portable installation. In standard installation with 1.6.18 it's OK, and with 2.x everything is fine with any installation option. I haven't yet figured out why this is happening with the new JS engine (which is why 3.7.0 works fine, that's the only difference between the branches), so far it looks like an incompatibility of the libraries that foobar2000 1.6.18 itself is compiled and shipped with
40
General Audio / Re: The "business model" of hybrid codecs with correction files
Last post by skamp -
Quote from: Porcus on
* what utilities user has at their hands - one that quickly finds orphaned symlinks, or one that quickly finds "lonely .wv hardlinks"?

Maybe I misunderstood myself. If someone has orphaned symlinks because they moved their source, that's their fault. I don't know how one could find themselves with orphaned hard links, unless they decided to move (not copy) the source (or the lossy parts) to a different storage device (hard links only work on a single storage device).

Obviously, with the hard link solution, the idea is to archive / back up the whole hybrid collection, and copy the lossy files (and possibly hard linked artwork) to a different device (a digital audio player, smartphone, whatever). Those copies are indeed disposable, as long as you keep the full hybrid collection backed-up.