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
1
Support - (fb2k) / Re: V2 beta 26 [x86] not listing DSD tracks
Last post by glong -
Thanks - absolutely no question is dumb when users like me can do dumb things - or simply  when unexpected stuff starts to happen.

I made some progress meantime after your prompt  regarding .dsf  but not .ISO

First - to reiterate about the problem. I never actually set up anything other than choosing all my Music folders.
What I was finding was - when I add new folders and files to one of those folders - they appeared instantly in the album listings - as long as they contain music files. Meaning a folder which is listed in the  'Music folders' will not be listed as an album if it merely contains just jpegs or excel files etc.

Something somewhere decides what file extension to consider music content before listing the files and that over the years that has worked with ISO and .dsf  with earlier versions of FB and the components I have used.

Upgrading with prior settings to V2 beta presumably imported rather than recreated from scratch.

I was adding new music to existing drives/folders (not .dsf I don't think) which did appear instantly.   But the .dsf files on there were missing.

My progress was to find that if I deleted folders in foolbar - restarted and then and asked it to re database the same folders - the .dsf albums now are listed.

So that is progress - but I tried the same with .iso files and no luck there.

 .iso files I drag into the playlist window still list all contents and play - but are not recognized by FB in the album list

I am assuming that the DB file listing in the v2 beta version simply does not have a .iso listing

... or is this the sacd component's remit

Oh and another observation from my recent tests :   DVD-A iso actually plays (if ISO is listed as a foobar filetype and it is double clicked) -  but unlike other it wont give me a file listing of all the tracks - if dragged into the playlist. Perhaps there is a DVD-A component I need to update.
4
3rd Party Plugins - (fb2k) / Re: [REQUEST USER-COMPONENT] foo_fanart
Last post by TT -
Quote from: MordredKLB on
Anyway TT has convinced me that I should probably get off my lazy ass and just do this so once I finish off georgia-http for http-control (which is coming along AMAZINGLY so far) I'll probably try and knock it out and then let TT add something similar to Reborn.

I'm eagerly waiting for your stuff man... can't wait! It's also good to hear that some ass-kicking helps,
actually I did that on purpose to revamp your motivation and I'm not sorry at all :))

- TT


 
5
Other Lossy Codecs / Re: Quite OK Audio (QOA)... anyone ?
Last post by Kamedo2 -
Possible improvements include:
  • Adding noise shaping
  • Use vector quantization, like E8 lattice, or PVQ to minimize the average root-mean-square error.
  • Use QMF (Quadrature mirror filter) to split the input into subbands, and encode each subbands separately, like aptx do.
9
General - (fb2k) / Re: foobar2000 v2.0 bugs
Last post by Porcus -
fb2k 1.x operates with 32-bit float internally, and so it cannot do 32-bit integer in a lossless manner.

Version 2 is still at beta stage, so I'd be patient. It can verify 32-bit integer FLAC files, but I have no idea what it can output.
(For DACing it doesn't matter, there is still nothing that can deliver the 25th bit, had it even been audible. There is a chip that boasts 140 dB dynamic range (in mono only!) - but in real measured environments it doesn't fully hit 20 bits: http://archimago.blogspot.com/2017/06/measurements-oppo-sonica-dac-ess-sabre.html )
10
MP3 - Tech / Re: LAME compiled executable slow!
Last post by 145dBSPL -
Using -march=native usually is most advantageous when just running on the compiling machine.

Current CPU's support a lot of "special" instructions/instruction sets older ones do not.
The differences between AMD/Intel architectures not to forget. So, using -march=native is
kind of a gamble if the binary should run across several different platforms.

The lowest common denominator would rather be -march=x86-64(-v2|-v3|-v4), depending on the target system.
Or you might choose the -mtune settings. The GCC manual details the different options.

For personal purposes, i also compiled the Lame binary for several years now. Aim was always to get
the fastest binary possible, that runs on every CPU - let's say - of the past decade. I also use GCC,
as it provides a solid performance and does not favor Intel over AMD as the ICL did (at least until last year).
It is even able to outperform ICL and MSVC builds speedwise, according to my experience and tests.