Skip to main content

Topic: 1.1.13, playback may hang on 0:00 after double click (Read 1968 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.
  • stickfish
  • [*]
1.1.13, playback may hang on 0:00 after double click
Using WASAPI with a USB DAC (PCM2707) and 1.1.13, music playing, when I double click on a different music file, the current song stops, foobar opens the double clicked song, playing arrow appears next to the song on the playlist, but sometimes the playback is stuck on 0:00. File format does not seem to matter, I was able to reproduce with mp3, flac, and tta. Pressing play or double clicking again will start playing. Clicking on the seek bar does not skip to that part of the song. Problem can happen on the same or different playlist. No errors found in console, with the last entry being "Opening track for playback: *."  Sleeping HDD does not wake up, so the program isn't accessing the HDD. The music files reside on the main OS drive, which is an SSD, and I was able to reproduce with files on a separate HDD. If left alone playing, there are no problems, but I haven't played music for an extended period yet.

I have had no issues when I installed Windows 7 in March, so I assume the version I was using is 1.1.11. I feel that it may be an issue with communication between foobar and the USB DAC. Or maybe something up with file buffering, which I currently set to 8GB so it fills up the cache in RAM (fb2k's memory usage is usually never above 1GB, depending on whether the portion or whole file is cached) and prevents waking up the HDD, which does work to an extent.

Apparently there's a 3.0 beta for WASAPI, maybe I'll give that a try.

Code: [Select]
Windows 7 SP1, with most of the recent upgrades installed, foobar2000 updated once from 11 to 13
Component list:
Core (2012-06-07 18:37:46 UTC)
   foobar2000 core 1.1.13
foo_albumlist.dll (2012-06-07 18:36:18 UTC)
   Album List 4.5
foo_cdda.dll (2012-06-07 18:36:12 UTC)
   CD Audio Decoder 3.0
foo_converter.dll (2012-06-07 18:35:52 UTC)
   Converter 1.5
foo_dsp_std.dll (2012-06-07 18:36:20 UTC)
   Standard DSP Array 1.0
foo_fileops.dll (2012-06-07 18:35:14 UTC)
   File Operations 2.1.3
foo_input_std.dll (2012-06-07 18:35:58 UTC)
   Standard Input Array 1.0
foo_input_tak.dll (2010-01-10 01:11:58 UTC)
   TAK Decoder 0.4.4
foo_input_tta.dll (2010-10-27 17:50:20 UTC)
   TTA Audio Decoder 3.2
foo_out_asio.dll (2012-02-04 20:59:56 UTC)
   ASIO support 2.1.1
foo_out_wasapi.dll (2009-05-20 04:45:18 UTC)
   WASAPI output support 2.1
foo_rgscan.dll (2012-06-07 18:35:56 UTC)
   ReplayGain Scanner 2.1.2
foo_ui_std.dll (2012-06-07 18:36:16 UTC)
   Default User Interface 0.9.5
foo_unpack.dll (2012-06-07 18:35:28 UTC)
   ZIP/GZIP/RAR Reader 1.6
foo_unpack_7z.dll (2011-08-14 00:27:58 UTC)
   7-Zip reader 1.8

  • Kohlrabi
  • [*][*][*][*][*]
  • Global Moderator
1.1.13, playback may hang on 0:00 after double click
Reply #1
Using WASAPI with a USB DAC (PCM2707) and 1.1.13

Please test with DirectSound output. If this only happens with WASAPI, this problem belongs into a WASAPI thread, which leads to...
Apparently there's a 3.0 beta for WASAPI, maybe I'll give that a try.

I'd strongly suggest to try the beta version, which supposedly fixes a lot of problems for most users, especially USB DAC users.
  • Last Edit: 20 June, 2012, 03:16:06 AM by Kohlrabi
It's only audiophile if it's inconvenient.

  • stickfish
  • [*]
1.1.13, playback may hang on 0:00 after double click
Reply #2
Haven't run into problems with the beta yet, but I'll report back if I encounter problems. Now I'm running into ASIO4ALL (2.11 beta 1) and timeout problems, which I believe is similar to my original problem.

Event-driven WASAPI also gives clicks when I browse directories in Explorer, whenever a sound file plays.
  • Last Edit: 25 June, 2012, 06:23:05 PM by stickfish

  • Kohlrabi
  • [*][*][*][*][*]
  • Global Moderator
1.1.13, playback may hang on 0:00 after double click
Reply #3
Now I'm running into ASIO4ALL (2.11 beta 1) and timeout problems, which I believe is similar to my original problem.

There is virtually no reason to use ASIO, especially not ASIO4ALL, if WASAPI or DirectSound works on your system, quoth the official components page for the ASIO output component:
Quote
Please note that this component is meant for systems where ASIO is the only available output method. It is highly recommended to use the default output modes instead of ASIO. Contrary to popular "audiophile" claims, there are NO benefits from using ASIO as far as music playback quality is concerned, while bugs in ASIO drivers may severely degrade the performance.

It's only audiophile if it's inconvenient.

  • stickfish
  • [*]
1.1.13, playback may hang on 0:00 after double click
Reply #4
I like ASIO4ALL and 2048 samples buffer, simply because the spectrum visualization's bars are much more snappier compared to regular DirectSound/WASAPI. It's nice to look at every now and then, especially if I ever have thoughts of including a bigger spectrum in a custom layout/theme for fb2k.

Back in March, my newly built desktop (i5-2500K rig) had problems with WASAPI causing one of my CPU cores to spike close to 100% for 1-3 seconds every 15-120 seconds. Using ASIO wasn't as bad, with smaller spikes happening every 15 seconds. Disabling HPET brings the spikes to much more manageable levels for both WASAPI and ASIO. For non-custom computers affected by this and are unable to turn off HPET due to BIOS restrictions, I fear that this may be an issue. I still need to experiment and test with other recent computers.

  • stickfish
  • [*]
1.1.13, playback may hang on 0:00 after double click
Reply #5
Just reporting that the problem is still present with the beta WASAPI. This time, the seek box cursor (to jump to a particular time) is flashing repeatedly at 0:00, suggesting constant file loading. Nothing in console reflects this, only a single playback entry. This is with 1.1.13 final.

  • hkwong
  • [*]
1.1.13, playback may hang on 0:00 after double click
Reply #6
I also have this problem, my sound card is 0404usb