Skip to main content

Topic: foobar 2000 v.1.1.11 crashes at WASAPI 32 bit data format (Read 5948 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.
  • egicar
  • [*]
foobar 2000 v.1.1.11 crashes at WASAPI 32 bit data format
Hi all,

I have a issue with my foobar2000 v.1.1.11: it crashes if I set it WASAPI (Musiland Monitor 03 US - latest stable driver) at 32 bit data format.  I enabled HDCD feature in Musiland Monitor 03 US and it can run 32 bit 384KHz.  It is connected to a USB 3.0 slot (Sapphire USB3.0 PCI-e card).  My PC runs Windows 7 64 bit always updated (ASUS P5KC - 4 Gb RAM - Intel Core 2 Duo E6600).
If I set 24 bit data format in foobar2000, everything goes OK.
I sent reports when foobar2000 crashed.

Here are my components:
Core (2012-02-04 13:05:48 UTC)
    foobar2000 core 1.1.11
foo_albumlist.dll (2012-02-04 13:04:12 UTC)
    Album List 4.5
foo_cdda.dll (2012-02-04 13:03:52 UTC)
    CD Audio Decoder 3.0
foo_converter.dll (2012-02-04 13:04:00 UTC)
    Converter 1.5
foo_fileops.dll (2012-02-04 13:03:02 UTC)
    File Operations 2.1.3
foo_freedb2.dll (2012-02-04 13:03:02 UTC)
    freedb Tagger 0.6.4
foo_input_monkey.dll (2012-03-12 21:44:36 UTC)
    Monkey's Audio Decoder 2.1.5
foo_input_std.dll (2012-02-04 13:05:10 UTC)
    Standard Input Array 1.0
foo_out_wasapi.dll (2012-03-09 21:01:39 UTC)
    WASAPI output support 2.1
foo_rgscan.dll (2012-02-04 13:03:48 UTC)
    ReplayGain Scanner 2.1.2
foo_ui_std.dll (2012-02-04 13:04:08 UTC)
    Default User Interface 0.9.5
foo_unpack.dll (2012-02-04 13:03:26 UTC)
    ZIP/GZIP/RAR Reader 1.6

Do you have any idea about a solution?

Thanks a lot in advance.
Egidio from Italy
  • Last Edit: 12 March, 2012, 07:44:32 PM by egicar

  • egicar
  • [*]
foobar 2000 v.1.1.11 crashes at WASAPI 32 bit data format
Reply #1
Maybe I was not so clear  ...
My issue consists in a crash of foobar2000 when I play a whatever bit format track (16 or 24 or 32 bit), if I set WASAPI to 32 bit data format.
When I set foobar2000 to 24 bit data format, the player works well with all bit format tracks (16, 24, 32 bit), but, I suppose, the max output resolution should be 24 bit (even if I play 32 bit tracks).
Can foobar2000 work at 32 bit data format with WASAPI? Is it a WASAPI issue or a foobar2000 issue?
My HW works great and I can play HDCD tracks without foobar2000 decoder component (the Musiland driver can do it).

Thanks again for any suggestion,

Egidio from Italy
  • Last Edit: 19 March, 2012, 05:51:39 PM by egicar

  • kode54
  • [*][*][*][*][*]
  • Administrator
foobar 2000 v.1.1.11 crashes at WASAPI 32 bit data format
Reply #2
If they're 32-bit integer format, foobar2000 is lopping off bits already anyway, since it uses 32-bit floating point internally, which does not have the precision to represent 32 bit integer numbers accurately.

  • Bonzite55
  • [*]
foobar 2000 v.1.1.11 crashes at WASAPI 32 bit data format
Reply #3
The same/similar situation with foobar crash, differ just it is not depending from sample rate choosen, more likely some other bug:

''Unrecoverable playback error: The device is not ready. (0x80070015)''

Helps usb disconection and reconecting again.

Any idea?

  • egicar
  • [*]
foobar 2000 v.1.1.11 crashes at WASAPI 32 bit data format
Reply #4
If they're 32-bit integer format, foobar2000 is lopping off bits already anyway, since it uses 32-bit floating point internally, which does not have the precision to represent 32 bit integer numbers accurately.

Thanks for the reply, kode54.

When I say crash, I mean foobar2000 closes itself (little window: foobar2000 stops to work ... etc).  When I open again foobar2000, I see a window were I can chose to start in safe mode, check the online troubleshooting or start normally.  No problems found by online troubleshooting; so I start normally and set 24 bit data format without problems palying 16/24 bit data format.
I'm sure that my hardware can manage 32 bit /384.0 KHz data format; so, I suppose that this could be an actual foobar2000 limitation.  Am I right?

Thanks again in advance.
  • Last Edit: 20 March, 2012, 02:56:51 PM by egicar

  • kode54
  • [*][*][*][*][*]
  • Administrator
foobar 2000 v.1.1.11 crashes at WASAPI 32 bit data format
Reply #5
The crashing would probably be a WASAPI limitation, or at least a limitation of the foobar2000 implementation. Try lowering the sound buffer duration?

  • egicar
  • [*]
foobar 2000 v.1.1.11 crashes at WASAPI 32 bit data format
Reply #6
The crashing would probably be a WASAPI limitation, or at least a limitation of the foobar2000 implementation. Try lowering the sound buffer duration?

I've tried the lowest (50 ms) buffer size, and now I have set 1000 ms (below this value, I read the Waring), but in both cases foobar2000 crashes (with 32 bit data format, of course).

  • kode54
  • [*][*][*][*][*]
  • Administrator
foobar 2000 v.1.1.11 crashes at WASAPI 32 bit data format
Reply #7
Maybe your drivers don't actually support 32 bit output.

  • kode54
  • [*][*][*][*][*]
  • Administrator
foobar 2000 v.1.1.11 crashes at WASAPI 32 bit data format
Reply #8
Oh, right, silly me. I forgot. Maybe the 32 bit output mode in the WASAPI driver is trying to use 32 bit floating point, not 32 bit integer. Since, you know, foobar2000 can't really output 32 bit integer precision anyway, since the floating point format does not support that much mantissa precision.

  • egicar
  • [*]
foobar 2000 v.1.1.11 crashes at WASAPI 32 bit data format
Reply #9
Oh, right, silly me. I forgot. Maybe the 32 bit output mode in the WASAPI driver is trying to use 32 bit floating point, not 32 bit integer. Since, you know, foobar2000 can't really output 32 bit integer precision anyway, since the floating point format does not support that much mantissa precision.

Thanks a lot again, kode54,

I can hear 24 bit/352.8 KHz music with great satisfaction. So I can wait for the next developements about 32 bit data format: I'm only 55 

Ciao,
Egidio

  • Bonzite55
  • [*]
foobar 2000 v.1.1.11 crashes at WASAPI 32 bit data format
Reply #10
I can not achieve more than red book default 16bit 44kHz.

This goes more or less stable.

In my case it looks like Win7 looses this USB connected DAC...

When it happened also WASAPI USB out disappearing from Foobar output setting.

Then you need to reconnect USB, restart Foobar, choose WASAPI USB output at the Foobar out settings.

  • lvqcl
  • [*][*][*][*][*]
  • Developer
foobar 2000 v.1.1.11 crashes at WASAPI 32 bit data format
Reply #11
I can hear 24 bit/352.8 KHz music with great satisfaction. So I can wait for the next developements about 32 bit data format: I'm only 55 


http://hifiduino.wordpress.com/2011/08/01/...-monitor-03-us/

Quote
The PCM1798 DAC in the Musiland 03 device is a 24 bit device. In I2S mode it accepts 24 bits of data on a 32 bit data frame as shown in the datasheet [...] Notice that there is data beyond bit 24 on either the left frame or the right frame. This indicates that 32 bits of data is delivered all the way to the DAC. The DAC, being a 24 bit device, truncates the data from 32 bit to 24 bit.


  • db1989
  • [*][*][*][*][*]
  • Global Moderator
foobar 2000 v.1.1.11 crashes at WASAPI 32 bit data format
Reply #12
I can hear 24 bit/352.8 KHz music with great satisfaction. So I can wait for the next developements about 32 bit data format: I'm only 55 

Please read #8 of the Terms of Service and bear it in mind in the future.

It is very unlikely that any given listener can distinguish such high resolutions as these from lower ones such as those of CDDA. Performing a double-blind comparison, as described at the above link, might be revealing.

  • Kohlrabi
  • [*][*][*][*][*]
  • Global Moderator
foobar 2000 v.1.1.11 crashes at WASAPI 32 bit data format
Reply #13
I can hear 24 bit/352.8 KHz music with great satisfaction. So I can wait for the next developements about 32 bit data format: I'm only 55 

Please read #8 of the Terms of Service and bear it in mind in the future.

db1989, I don't see any statement made by the user that he hears any advantages using 24bit / 352 kHz, only that he uses this setting. My impression is that this thread is only debating a technical aspect of the WASAPI output method. That these kinds of settings offer no advantage at all (from a perceptual/consumption standpoint) is a completely different discussion and was not touched here.

Don't misunderstand me, I wholeheartedly welcome your effort in trying to lead the people towards the recognition of the truth. But I think that we should not try to put down any topic mentioning high-resolutions with a simple ToS #8-hammer. In that light I'm all for a sticky topic "16bit/44khz is enough for everyone, if you don't think so, prove it." to refer people to, since I expect the future to hold many "high-res quality claims" topics on HA.
  • Last Edit: 22 March, 2012, 01:58:41 PM by Kohlrabi
It's only audiophile if it's inconvenient.

  • egicar
  • [*]
foobar 2000 v.1.1.11 crashes at WASAPI 32 bit data format
Reply #14
I can hear 24 bit/352.8 KHz music with great satisfaction. So I can wait for the next developements about 32 bit data format: I'm only 55 


http://hifiduino.wordpress.com/2011/08/01/...-monitor-03-us/

Quote
The PCM1798 DAC in the Musiland 03 device is a 24 bit device. In I2S mode it accepts 24 bits of data on a 32 bit data frame as shown in the datasheet [...] Notice that there is data beyond bit 24 on either the left frame or the right frame. This indicates that 32 bits of data is delivered all the way to the DAC. The DAC, being a 24 bit device, truncates the data from 32 bit to 24 bit.



Thanks for your specifications!  Now, I have learned another thing about my new audio device.
  • Last Edit: 22 March, 2012, 03:16:46 PM by egicar

  • egicar
  • [*]
foobar 2000 v.1.1.11 crashes at WASAPI 32 bit data format
Reply #15
I can hear 24 bit/352.8 KHz music with great satisfaction. So I can wait for the next developements about 32 bit data format: I'm only 55 

Please read #8 of the Terms of Service and bear it in mind in the future.

It is very unlikely that any given listener can distinguish such high resolutions as these from lower ones such as those of CDDA. Performing a double-blind comparison, as described at the above link, might be revealing.


I'm so sorry  . It was not my intention to make comparisons of any kind.
I'm new in the liquid music. Until today, I had not much confidence in this mode of reproduction. I always listened to music from the turntable (Pro-Ject 1 Xpression) or CD player (Onkyo DX200).
So, I am an absolute beginner and as such, I'm trying to understand, to inquire and learn.
  • Last Edit: 22 March, 2012, 03:21:02 PM by egicar

  • Kohlrabi
  • [*][*][*][*][*]
  • Global Moderator
foobar 2000 v.1.1.11 crashes at WASAPI 32 bit data format
Reply #16
So, I am an absolute beginner and as such, I'm trying to understand, to inquire and learn.

Generally, unless you have very specific reasons to use WASAPI, like for example bit-perfect output to an external receiver, it is recommended to stick to DirectSound, since it is the most tested and well behaved of the output methods. So far nobody has been able to provide definitive proof that WASAPI output (or ASIO output for that matter) offers any benefit over DirectSound output. What I mean to say is that alternative output methods lead to lots of problems without any perceptible benefits. The same is true for bit depths which exceed 16 bit resolution, and sample rates beyond 44.1 kHz.

Instead of buying into the audiophile arms race of dials which go up to eleven and sample rates which touch the MHz range, it is much easier and less of a hassle to just stick to the proved realities, and that is that CD quality audio (16bit/44.1kHz) is good enough, as is DirectSound output.
  • Last Edit: 22 March, 2012, 04:21:54 PM by Kohlrabi
It's only audiophile if it's inconvenient.

  • egicar
  • [*]
foobar 2000 v.1.1.11 crashes at WASAPI 32 bit data format
Reply #17
So, I am an absolute beginner and as such, I'm trying to understand, to inquire and learn.

Generally, unless you have very specific reasons to use WASAPI, like for example bit-perfect output to an external receiver, it is recommended to stick to DirectSound, since it is the most tested and well behaved of the output methods. So far nobody has been able to provide definitive proof that WASAPI output (or ASIO output for that matter) offers any benefit over DirectSound output. What I mean to say is that alternative output methods lead to lots of problems without any perceptible benefits. The same is true for bit depths which exceed 16 bit resolution, and sample rates beyond 44.1 kHz.

Instead of buying into the audiophile arms race of dials which go up to eleven and sample rates which touch the MHz range, it is much easier and less of a hassle to just stick to the proved realities, and that is that CD quality audio (16bit/44.1kHz) is good enough, as is DirectSound output.

Thank you very much for your considerations, Kohlrabi.
I have set WASAPI following some tips in the Musiland forum, expecially to be able to use HDCD capability of my new device.
I'll try DS in the next days, but I have not had any problem with WASAPI, until now (excluding using 32 bit output data format  ).

Ciao,
Egidio
  • Last Edit: 22 March, 2012, 05:22:36 PM by egicar

  • Kohlrabi
  • [*][*][*][*][*]
  • Global Moderator
foobar 2000 v.1.1.11 crashes at WASAPI 32 bit data format
Reply #18
expecially to be able to use HDCD capability of my new device.

kode54 has created a nice HDCD decoding component for foobar2000, which you could also try. 
It's only audiophile if it's inconvenient.