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
Opus / Re: xHE-AAC : The Death of OPUS?
Last post by shadowking -
The state of lossy music encoding is disheartening.
Developers are not robots or isolated nerds/geeks. If they can no longer sustain the efforts … pick up the skillsets where they left off and continue investing the same efforts they made. Not make a point of scolding them at every forum opportunity.

The absence of a loud and clear message expressing dissatisfaction with the current state of affairs is often mistaken for satisfaction. "People don't complain, so why bother?" And more often than not, I've seen development resume not because someone decided to dust off abandonware out of boredom, but because they faced the pain and showed empathy for those who reported how this or that change would make life easier or happier. Certainly, there are various ways to report: a hit between the eyes and a sugar-coated plea to name a few. Just as there are original editions of Mark Twain and Agatha Christie novels with words of their era like the N-word and orientals, and there are expurgated editions for a fragile, resentful mindset. For example, a few weeks ago I complained that Helix MP3 encoder, officially abandoned 20 years ago, was not capable of handling more than 16-bit input, and the miracle happened. God bless @Case for that.

Mod edit: Defused potentially offensive word.


Its a catch 22 situation. With Mp3 / AAC it can work due to high user demand.  With less popular codecs like mpc, WV, vorbis
the opposite can happen and already small userbase is further decimated . That may slow down development even more.
2
Support - (fb2k) / Re: Disable tag caching of specific tags on v2
Last post by paregistrase -
As it seems that there is not likely to be a movement in this direction in the near future, I was trying to minimize the impact in memory of excessive quantity and longitude in tags.

First, I get rid of duplicates, like the backup tags created with taggers like foo_discogs. Although some of these tags were big (like release notes, artist profile, etc) the global impact was almost unnoticed. The RAM usage was enormous, to the point that the SMP component crashes randomly without of memory or the entire player get down without even a crash log left behind.

Next step was pointing at the new foo_ID and chroma print tags. Deleting this tags reduce the usage of RAM in more than 50%
With the same number of files first foobar was always at the limit of a 32 app and crashing with every operation that requires a little bit more and without them RAM is about 1 GB,

So until a solution that allow us to unlload this tags or a 64 SMP version that allow us to not be limited by RAM comes out, It is not suitable to use this kind of functionality, at least in my case. With less than 20.000 files tagged with chroma print, I was in a stage when the crashes started to happen even playing a track or loading a playlist.
3
3rd Party Plugins - (fb2k) / Re: foo_vis_spectrum_analyzer
Last post by hormidor -
1) The calculator comes up with colors that don't actually exist in the artwork.
That's a result of the algorithm. To determine the colors in an acceptable amount of time similar colors are put in 'boxes'. Each box can only have one leading color.
2) The calculator selects 9 colors every time, even though, per changelog, "between 2 and 256 colors can be selected".
3) The colours are totally out of order in terms of brightness (which ruins the idea of an amplitude-based gradient).
What do think the settings in the Common / Artwork section are for?

Thanks, I was not aware the settings were in a different section.
4
3rd Party Plugins - (fb2k) / Re: [fb2k v2] SQL Tree (foo_uie_sql_tree)
Last post by chrisdukes -
I think I don't understand the difference between the Batch tab and the Query tab.  ¯\_(ツ)_/¯

Can you refresh if there's only a query in the Batch tab?
Can you only refresh a tree if there's a query?
Does refreshing a tree also recreate a table like executing the query in SQL Console?

If I create TableA in one tree, then I create TableB from Table A in a separate tree, how can I automatically refresh Table A before Table B when I load Foobar2000?  I guess I would want to do the same thing for Refresh All.  I have more tables that are dependent on TableA, but it doesn't matter what order they're refreshed in as long as TableA is refreshed first.

Thanks again for the awesome plug-in!
7
Support - (fb2k) / Re: Different DSD sample rates for same file on 2 devices
Last post by HornetMaX -
I have no experience with DSD or external DACs, but to narrow it down:
Which components do you have installed?
I have foo_input_sacd (1.5.10) and foo_out_asio (2.2.2_

Which output are you using in foobar2000?
For the K7 I use "ASIO : FiiO ASIO Driver" and for the do400 I use "ASIO :USB DAC ASIO".
They are the PC drivers that come with each dac/amp.

Does the SMSL DO400 ASIO driver have any configuration?
The usual stuff, more or less like the FiiO K7 ASIO Driver. I don't see any difference between the settings of the two.
In the Windows Properties dialog of each device I have the usual General/Levels/Advanced/Spatial Sound tabs.
Under Advanced, the Default Format is "32bits 44100 Hz" for both (but I don't think that should make any difference and, at any rate, seems to not bother when I play via the K7).

The dedicated control panels for each device seem to have no useful option (basically just buffer size and safe mode).

People who play DSD usually install these components:
https://sourceforge.net/projects/sacddecoder/files/foo_input_sacd/
https://sourceforge.net/projects/sacddecoder/files/foo_out_asio%2Bdsd/
These are the two I have. They seems to work perfectly fine on the K7 but not-so-perfectly on the do400 :(
8
Support - (fb2k) / Re: Different DSD sample rates for same file on 2 devices
Last post by Gus. -
I have no experience with DSD or external DACs, but to narrow it down:
Which components do you have installed?
Which output are you using in foobar2000?
Does the SMSL DO400 ASIO driver have any configuration?

People who play DSD usually install these components:
https://sourceforge.net/projects/sacddecoder/files/foo_input_sacd/
https://sourceforge.net/projects/sacddecoder/files/foo_out_asio%2Bdsd/
9
3rd Party Plugins - (fb2k) / Re: foo_vis_spectrum_analyzer
Last post by pqyt -
1) The calculator comes up with colors that don't actually exist in the artwork.
That's a result of the algorithm. To determine the colors in an acceptable amount of time similar colors are put in 'boxes'. Each box can only have one leading color.
2) The calculator selects 9 colors every time, even though, per changelog, "between 2 and 256 colors can be selected".
3) The colours are totally out of order in terms of brightness (which ruins the idea of an amplitude-based gradient).
What do think the settings in the Common / Artwork section are for?

10
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by Kraeved -
I took the liberty of writing something regarding the -TX parameter over at https://wiki.hydrogenaud.io/index.php?title=Helix_MP3_Encoder#Magical_Mystery_Switch_-TX

Thank you, @maikmerten.

a) Wiki says that -TX6 is used by default, but -H screen is missing the word default next to TX6 and -EC screen shows ec->test1 = 0 instead of 6 when no number is specified and -1 instead of 6 when -TX is not used at all. I believe the word should be added, but what do to with the number?

b) The last TX setting (eighth in a row) has no specific number on -H screen, it just says “v5.1  2005.08.09 (see CVS log for details)”. Have you found anything interesting there?

c) When Helix is called with -TX# -EC, we see “ec->test1 = #”. It accepts 0, positive and negative integers with no validation. Since we'll probably never know the essence of the experiments of the previous team associated with this flag and the default setting (-TX6) is recommended, maybe it makes sense to put it at the bottom of -H screen within a separate section like “--- Mysterious legacy (Read wiki for details) ---” to avoid potential questions from users?

Also, I noticed that you told the user which Helix settings (-V115 -HF2 -F19000) might resemble LAME -V2. Let me clarify, which transition band does Helix use in this case? For LAME 3.99.5o and 3.101 beta 3, it is 18000 Hz - 18581 Hz.