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.
Topic: Slow run up time with large library & problems in playback /w WASA (Read 3441 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Slow run up time with large library & problems in playback /w WASA

Hi,

I'm having two problems:

1) I have the newest version of the foobar2000 and quite a large music library. All of my music are FLAC files. I have also made autoplaylists of all my albums. My problem is that foobar runs up very slowly when I start it. I have already deleted the mark on the "rescan on startup" option in library settings but that didn't help. It takes 36 seconds from starting that I can use foobar!

2) I'm listening music with Audiolab 8200CD via USB with WASAPI plugin. I have the newest version of that plugin. Sometimes when I start to listen music, click a track I want to listen, my Audiolab CD/DAC plays it for about one second and then it just crashes (stops playback). The foobar2000 doesn't crash itself, VU meter and playback time just stops running. There's nothing in console either after the crash. When listening with DirectSound the playback works perfectly. I don't have problems with Audiolab with any other software.

I've tried to change the buffer but it doesn't help. I have Windows Vista Home Premium SP2 32 bit and I want to use the WASAPI for optional sound quality

Help me 

Slow run up time with large library & problems in playback /w WASA

Reply #1 –
Autoplaylists make foobar2000 slow to start. This is known.

Your playback problem will probably go away when you disable WASAPI. WASAPI is experimental and although it works for most users, there are still rough edges. I recommend you read the WASAPI beta thread and try some versions out if you're having difficulties. Peter is attempting to fix it so it works for everyone.

Slow run up time with large library & problems in playback /w WASA

Reply #2 –
Quote from: Canar on
Your playback problem will probably go away when you disable WASAPI. WASAPI is experimental and although it works for most users, there are still rough edges. I recommend you read the WASAPI beta thread and try some versions out if you're having difficulties. Peter is attempting to fix it so it works for everyone.


I found this http://wiki.hydrogenaudio.org/index.php?ti.../foo_out_wasapi

Maybe I should set the buffer very low.. let's test

EDIT: 180ms seems to work fine. Can buffer that low cause other problems?

Slow run up time with large library & problems in playback /w WASA

Reply #3 –
Quote from: Masza on
I want to use the WASAPI for optional sound quality
There is no audible advantage of WASAPI over DirectSound, its main use is the ability to stream data bit-perfectly to external receivers for decoding.

Quote from: Masza on
EDIT: 180ms seems to work fine. Can buffer that low cause other problems?
A small buffer can lead to dropouts and glitches during playback, especially in cases where the data rate varies a lot, e.g. when the audio files are served on a slow network or NAS.
It's only audiophile if it's inconvenient.

Slow run up time with large library & problems in playback /w WASA

Reply #4 –
Quote from: Kohlrabi on
Quote from: Masza on
I want to use the WASAPI for optional sound quality
There is no audible advantage of WASAPI over DirectSound, its main use is the ability to stream data bit-perfectly to external receivers for decoding.
Which is not to imply that DS always alters the bitstream. WASAPI simply precludes the possibility of this occurring via Windows’ volume control, automatic resampling, etc. In any case, any difference that might occur would be insignificant both to your ears (as Kohlrabi said) and numerically.

Please refer to #8 of the Terms of Service, to which you agreed upon registration. Also see the last item of the official FAQ on foobar2000’s website. In short: (1) statements about sound quality are not welcome here unless they are corroborated by objective evidence; (2) different output methods do not result in playback of differing quality, and that is not why they exist.

Slow run up time with large library & problems in playback /w WASA

Reply #5 –
Quote from: db1989 on
Please refer to #8 of the Terms of Service, to which you agreed upon registration. Also see the last item of the official FAQ on foobar2000’s website. In short: (1) statements about sound quality are not welcome here unless they are corroborated by objective evidence; (2) different output methods do not result in playback of differing quality, and that is not why they exist.


If I want the best playback technically and numerically, why shouldn't I use WASAPI? And why can't I ask about the problems with it? It can be downloaded also from foobar2000 web site.

I didn't say that music sounds better with WASAPI, you got it wrong

Slow run up time with large library & problems in playback /w WASA

Reply #6 –
Quote
I have also made autoplaylists of all my albums.


One autoplaylist per album? If so, it's probably a good idea to browse albums with a library viewer (e.g. Facets or Album List), rather than having tons of autoplaylists that never change.

Slow run up time with large library & problems in playback /w WASA

Reply #7 –
Quote from: Masza on
And why can't I ask about the problems with it? It can be downloaded also from foobar2000 web site.
Who said that you cannot ask about the component or valid issues? No one, by my count.

Quote from: Masza on
I didn't say that music sounds better with WASAPI, you got it wrong
See:
Quote from: Masza on
I want to use the WASAPI for optional sound quality

Slow run up time with large library & problems in playback /w WASA

Reply #8 –
Quote from: db1989 on
Quote from: Masza on
And why can't I ask about the problems with it? It can be downloaded also from foobar2000 web site.
Who said that you cannot ask about the component or valid issues? No one, by my count.

Quote from: Masza on
I didn't say that music sounds better with WASAPI, you got it wrong
See:
Quote from: Masza on
I want to use the WASAPI for optional sound quality



I was talking about the best sound quality in technical terms, it has nothing to do with subjective opinnions. My Vista changes 16 bit to 24 bit when using USB, that's why I want to use WASAPI

Quote from: dhromed on
Quote
I have also made autoplaylists of all my albums.


One autoplaylist per album? If so, it's probably a good idea to browse albums with a library viewer (e.g. Facets or Album List), rather than having tons of autoplaylists that never change.


Thank you very much! How could I be so stupid that I didn't even think about that. Now it starts like a thunder from the skies

Slow run up time with large library & problems in playback /w WASA

Reply #9 –
Quote from: Masza on
I was talking about the best sound quality in technical terms

The thing is, thinking like that is meaningless. If a table has four legs, and it is stable, and you add a fifth leg... is it more stable?

But it's clear now that you didn't mean subjective quality, so I think we can let this go and focus on the real problems i.e. the stops and slow startup.

Edit
Edit-Ninja'd
 

Slow run up time with large library & problems in playback /w WASA

Reply #12 –
Lowering the playback buffer will cause audible issues if your system does anything time consuming while playing. Canar mentioned there's a newer WASAPI plugin but he neglected to mention that it works better with USB devices. You can get it from here.

Slow run up time with large library & problems in playback /w WASA

Reply #13 –
Re quality: no problem, then, but I hope you understand where Kohlrabi and I got misled by your wording! 

We leave threads open unless the starter requests that they be closed or (more rarely) the thread becomes problematic, partly in case (heh, get it?) they might play host to additional pertinent information in the future; this one is fine, but you can still ask a member of staff if you do want it locked for whatever reason.