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
2
Support - (fb2k) / Re: foobar2000 v151: Update check failure: Network authentication error (80090326)
Last post by kxmp -
Did you disable the following cipher suites in the registry by accident?

TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384

Just because TLS 1.2 is enabled doesn't necessarily mean the secure handshake can be established.

Hi I sniffed the network and I only have
ecdhe_ecdsa ... aes128 sha256
ecdhe_ecdsa ... aes256 sha384

for ecdhe_rsa and dhe_rsa I don't have gcm ciphers inside

Code: [Select]
Cipher Suites (21 suites)
    Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA256 (0x003c)
    Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA (0x002f)
    Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA256 (0x003d)
    Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA (0x0035)
    Cipher Suite: TLS_RSA_WITH_RC4_128_SHA (0x0005)
    Cipher Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x000a)
    Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (0xc027)
    Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013)
    Cipher Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014)
    Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (0xc02b)
    Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 (0xc023)
    Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (0xc02c)
    Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 (0xc024)
    Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (0xc009)
    Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA (0xc00a)
    Cipher Suite: TLS_DHE_DSS_WITH_AES_128_CBC_SHA256 (0x0040)
    Cipher Suite: TLS_DHE_DSS_WITH_AES_128_CBC_SHA (0x0032)
    Cipher Suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA256 (0x006a)
    Cipher Suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA (0x0038)
    Cipher Suite: TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA (0x0013)
    Cipher Suite: TLS_RSA_WITH_RC4_128_MD5 (0x0004)

And server returned a fatal alert then connection end here.

I'm using win7 x64

I found that the foobar2000's website is using rsa certificate but I only have gcm with dsa.
Ahh!?? There might be something wrong with system.
Anyone know the cipher update patch?

2021-09-25 13:54
I found that I need kb3042058 to support rsa with gcm. Let's see will it solve the problem.

Now problem solved
Quote
Cipher Suites (26 suites)
    Cipher Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (0xc028)
    Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (0xc027)
    Cipher Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014)
    Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013)
    Cipher Suite: TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (0x009f)
    Cipher Suite: TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (0x009e)
    Cipher Suite: TLS_RSA_WITH_AES_256_GCM_SHA384 (0x009d)
    Cipher Suite: TLS_RSA_WITH_AES_128_GCM_SHA256 (0x009c)
    Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA256 (0x003d)
    Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA256 (0x003c)
    Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA (0x0035)
    Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA (0x002f)
    Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (0xc02c)
    Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (0xc02b)
    Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 (0xc024)
    Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 (0xc023)
    Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA (0xc00a)
    Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (0xc009)
    Cipher Suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA256 (0x006a)
    Cipher Suite: TLS_DHE_DSS_WITH_AES_128_CBC_SHA256 (0x0040)
    Cipher Suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA (0x0038)
    Cipher Suite: TLS_DHE_DSS_WITH_AES_128_CBC_SHA (0x0032)
    Cipher Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x000a)
    Cipher Suite: TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA (0x0013)
    Cipher Suite: TLS_RSA_WITH_RC4_128_SHA (0x0005)
    Cipher Suite: TLS_RSA_WITH_RC4_128_MD5 (0x0004)
3
Support - (fb2k) / Re: Multiple outputs - why
Last post by glong -
Well it is not quite so silent in that precise case - it fails with a 'cannot play' error message. It does not recognize that Exclusive is turned off and thus it should not display the Exclusive output option in foobar when it is off.


Thanks for reminding me that WASAPI was integrated. I dont think I was ever able to use prior WASAPI components as separate windows CPU processes in the way in which the ASIO component permitted. I have no idea whether WASAPI is modular enough to run its own thread (integrated or not), such that file searching and so on can proceed without disturbing the music output, as it currently does.

4
Support - (fb2k) / Re: Multiple outputs - why
Last post by kode54 -
Exclusive mode WASAPI was integrated recently. There is no way for it to poll whether Windows has allowed it to output in exclusive mode. Clearly from your report, it just silently fails and foobar has no idea it's not outputting sound.
5
Other Lossy Codecs / Re: exhale - Open Source xHE-AAC encoder
Last post by kode54 -
Probably similar to Fluendo's Oneplay GStreamer codec pack, which is also licenses actual Microsoft Windows Media codecs instead of using reverse engineered solutions from the FFmpeg project. It also licenses all the applicable decoder patents for as many seats as you pay for.
7
Support - (fb2k) / Re: Multiple outputs - why
Last post by glong -
Ok - the expectation was not necessarily that foobar would be the root cause of all of it but I thought the non playing of some files with the exclusive mode might be partly down to how foobar presents the data to the driver.

Given that  you did not seem to think this was internal I did some more extensive testing.  Perhaps you can answer whether the above applies - or whether this is exclusively a driver problem.

I toggled the windows control panel settings for exclusive use of the sound card since I remembered that it has Exclusive use listed.

Foobar insists on listing digital and speaker options for output irrespective of whether windows has Exclusive turned on or off.

When windows sound control panel has it turned off, foobar does not produce any sound regardless of what file is chosen (when the exclusive driver is selected as output in Foobar).

When tell windows to 'not use this device' and open foobar, sure enough no Xonar devices are displayed in the output options (neither Exclusive or otherwise).  Primary Sound driver does not produce any sound also.

The ASIO driver continues to send data to the card and sound is produced. However it too stops producing sound if the driver is fully disabled in the windows device manager.

All that answers my question of where the Exclusive is set. It does not explain why foobar still lists these exclusive drivers - even when Exclusive is turned off in the Windows control sound panel.   I have no idea whether foobar should sense this or not.

It does not explain why some files will not play when Exclusive is turned on and foobar has the Exclusive driver chosen. I can say for sure that DSD does not work when Exclusive is turned on with this driver. There are definitely some flac files which did not play, and this may be an issue to report to the driver people. Appreciate any thoughts.

All in all, this surprised me because until a year or so ago I had used ASIO and turned off all windows interaction with sound by disabling its use of the device. The big advantage of ASIO was that it ran its own distinct process which was independent of foobar. When doing foobar actions such as sorting or searching the database the sound would continue without problem. Not only that - I could assign an exclusive core on the CPU to ASIO  and even give it 'real time' priority which made it totally bullet proof from other actions on foobar or the computer. I toyed with WASAPI on the suggestion of people on this forum, which seemed to sound fuller in the midrange while not being as clean as ASIO.  

Recently as I gather WASAPI was made redundant with newer versions of foobar I started using neither.

The sound is much fuller in the mid range but I cannot say is truer -  ie Dylan in Freewheeling) sounds as if he is in a regular hard walled/floored room with full reverb - not what you would an engineer to go for intentionally.  

That said, foobar cannot sort or search without breaking seriously breaking up the sound for a second or more while sound is playing. I tend to live with this for what appears to be better sound.  

I would be nice if the sound deliver module for foobar could be kept as a separate process as with the old ASIO.  Clearly foobar is not doing an adequate job of isolating file operations from sound delivery. It would be really good if this could be achieved - somehow.   Does no one else suffer this problem during playback. It would be embarrassing if this was to happen at a public presentation for example.
8
General Audio / Re: Equalise Volumes via dbPoweramp (-db) & wxMp3gain (+db) conversion
Last post by Markuza97 -
Are you talking about MP3?
You can adjust volume in 1.5 dB steps without re-encoding the file, this can be considered lossless.
(Technically speaking, it is not lossless because you are changing bits - but the quality itself is "lossless" since there is no re-encoding.)

This wxMP3gain appears to be nothing more than a GUI for MP3Gain. That program is very old. Is it even using EBU R128 or old ReplayGain?
If it's using old ReplayGain, everything that we posted above is invalid. They are two completely different algorithms.

Stick to foobar2000 please.
SimplePortal 1.0.0 RC1 © 2008-2021