Skip to main content
Recent Posts
Support - (fb2k) / Visualizations not showing in Live Edit feature
Last post by Hugg Niceman -
I am running the newest version of fb2k with Columns UI installed. I am trying to use the Live Edit feature to allow me to place the visualizations on there like I had previously, but only the spectrum analyzer is available. I have them all available via the view menu, but that only brings up the visualization in its own window and I can't see a way to dock that into the actual UI. Any help would be much appreciated.
FLAC / Re: Archive tester - Tool to facilitate testing collections of archives, incl. FLAC
Last post by Thomas C. -
Version is available (big update).

Change log
Parallel testing (~multithreading)
  • Testing processes can now be ran in parallel (multithreaded). Default thread count is based on .NET's "Environment.ProcessorCount" which counts your computer's logical cores. There is a setting to change this manually too.
    Previous version was singlethreaded, relying on the fact the algorithms such as RAR5 are multithreaded. But some, for instance RAR4, are not multithreaded. This should bring a huge performance gain when testing a large number of files encoded with singlethreaded algorithms (or at least when testing algorithms are singlethreaded).
Multivolume: I still have a more flexible file extension/tester matching system in mind, but here is already something that should solve many cases.
  • *.001 are now testable through 7z.exe
  • *.r00 and *.r01 are now testable through UnRAR.exe, *.r01 is considered non testable if matching *.z00 exists in the same folder.
  • *.z00 and *.z01 are now testable through 7z.exe, *.z01 is considered non testable if matching *.z00 exists in the same folder.
  • Prevented case when all files ending with *.rar but belonging to the same multivolume archive would get tested along with each other. Which resulted in n2-1 redundant tests (if I got the formula right). Files ending with ".part1.rar" are still considered testable while all other volume, following pattern ".part[N].rar" are now considered non-testable.
  • ?: Should multivolume non-first volumes be counted as non-testable or simply ignored? For now they are counted as non-testable.
Self-extracting I still have a more flexible file extension/tester matching system in mind, but here is already something that should solve many cases.
  • *.exe are now optionally testable. *.exe first get tested with UnRAR.exe, if not a RAR archive, a *.exe file will then be tested by 7z.exe, if failed, it will be counted as failed test. There is a checkbox to test or ignore *.exe files. Default value: false.
  • Added "kB/s" indicator.
Targeting tuning:
  • In the "Inputs: Paths to be tested" field, you may now include/exclude specific files, the same way you would include/exclude a folder.
  • There is now a setting to automatically skip some folders by name (separated with "|"). Default value: System Volume Information | $RECYCLE.BIN. (In previous versions, "$RECYCLE.BIN" was hard-coded.)
  • Prevented cases when some file could be tester multiple times or counted multiple times as non testable files (typically if a folder and its parent folder were both set as inputs).
Stability and efficiency
  • Closing main form/application now more efficiently closes background threads.
  • Stopping during discovery process will now be much faster (kind of instant).
  • At first start, the input text field is now filled with a demo/tutorial, that should be able to scan you all computer if started.
  • Tests that have been stopped by clicking on "Stop" now count as skipped.
  • Possible future improvement: Progress indicators work fine is the full process is ran. Using "Skip" or "Stop" buttons result in skipping files, which may make progress indicators interpretation arguable. This does not look like a priority but may possibly be re-thought in the future. Probably in a smaller update.
UI consistency:
  • "Skip" button is now disabled during the discovery process and only activated during testing process.
  • Progress indicators that can only be evaluated after at least one file has been tested (such as "Est. total time") now read "?" before they can be evaluated, instead of "00:00:00.0000000".
  • "Launch/Testing" button now reads "Scanning" during the scanning process (instead of "Testing").
  • "Time spent on current file" is replaced with the count of active parallel tests when parallel testing.
  • .exe path text boxes and most setting buttons are now disabled while processing.
Dependencies and compatibility:
  • Tested with UnRAR.exe 5.60 and 7-Zip 18.05.
  • Update UnRAR.exe to version 5.60
Possible issue(s):
  • On my Win7 computer, stopping the testing process ("Stop" button") gets the application stuck with one running parallel test running (according to UI). This did not happen on the Win10 computer where I write the code. Cause unidentified so far.
Support - (fb2k) / Replaygain changes have instant effect - EXCEPT when using shortcut keys. Bug?
Last post by MaxDread -
Hi all

As far as I know, in the past - a month or two ago and previous to that - if you changed the replaygain setting (none, track, album) "on the fly" it had no effect  It would only take effect if the track was stopped and re-started, or when the next track came on 

So it was a pleasant surprise today when by accident I found that changing the RG setting does now make the change "on the fly" / instantly.  However, it only does this when using the drop down menu.  When I use shortcut keys to change the RG status it does not happen.  I tend to always use my shortcut keys, and I guess that's why I had not noticed the change. 

Whether it is a bug or not I don't know.  But is it something that can be fixed? 

Support - (fb2k) / Re: foobar2000 v1.4b19 - visualizations on toolbar don't have native borders anymore
Last post by j7n -
The screenshots posted by Rollin appear to be resampled, reducing the visibility of the effect, and adding new blended borders. But it is still there. The minor graphical flaw resulting from this flatness is that the bars are poorly defined where the gradient happens to randomly match the color/brightness of the window chrome - the first 25 percent of the level meter. A border is additional protection against this, why the transport icons look as they do, being white on white.

SimplePortal 1.0.0 RC1 © 2008-2018