Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[rpalmer68]

There seems to be a buffering issue with WMA files this last couple of builds.

Environment:
Library = on local C: drive
Output is set to Wave Out
Playing WMA lossless files back over a 802.11g wireless network


Symptom:
When skipping forward a track, playback starts for 1 second, then stops for about 1.5 seconds and then continues again.

Problem not there if using Direct Sound or when playing 192K MP3s, only when using Wave Out and WMAs.

Richard 

[JimH]

Try changing the playback settings in tools/options.  Try "more skip resistant" and "reset".

[rpalmer68]

Tried both before posting, neither fix the problem.

This used to be an issue when starting playback, but this was fixed when you did some auto buffering changes back a few versions ago.

Inital playback works fine now, just when skipping forward I get this pause  when the next track starts.

Richard

[StarBand Guy]

You've probably already checked into this as well, and I don't mean to insult by it's simplicity, however I mention it only because I've fallen prey once or twice myself:

the MTU setting for all machines on the network (if this is a network) should be set the same, and you might have better luck with something other than 1500. A little experimentation is sometimes necessary.  Some notorious programs will change the MTU without telling you.

[rpalmer68]

I don't think it's a networking issue as such otherwise MC would do the same thing with Direct Sound not just Wave Out.

Anyway I'll check what you suggest - so dumb question.... where do I find the MTU settings?

Cheers
Richard

[Alex B]

DirectSound is known to be more skip resistant on Win2k/XP.

Here is an explanation:

From http://home.revealed.net/xen/WOvsDS.txt

Q: What's the difference between DirectSound and waveOut?
 
A: Short version: you should use waveOut on win95/98/me/nt4 and DirectSound on win2k/xp.

Long version:

WaveOut is old, outdated API (Application Programming Interface) for playing digital sounds in 32bit Windows OS's. Old OS's (all win9x and nt4) have good waveOut implementation; you should use waveOut output on those for best performance. waveOut features are limited; it doesn't even natively support mixing multiple streams. It appears that waveOut is provided in win2k/xp only for compatibility with old software - win2k/xp waveOut implementation is rather bad, it doesn't use any kind of hardware acceleration; all mixing is performed by software (may interrupt sound when CPU usage is high).

DirectSound is the new "modern" sound playback API, available as redistributable for all versions of 32bit Windows OS's (though nt4 directsound is terribly broken from my experience). DirectSound natively supports mixing multiple streams, independent volume control, hardware acceleration layer & hardware emulation layer (features which aren't supported by hardware are emulated by software, so the programmer doesn't have to worry if his new l33t code will work right on old sb16). DirectSound should be generally fine to use everywhere except for nt4, as long as you have latest DirectX version for your OS and proper soundcard drivers installed. DirectSound is preferred over waveOut on win2k/xp, because their DirectSound implementation is relatively good (eats less CPU than waveOut and is free of win2k/xp waveOut implementation glitches). DirectSound was originally designed to let games utilize hardware acceleration available on your system without having to touch low-level hardware functions directly (like any other component of DirectX).

[Matt]

Tried both before posting, neither fix the problem.

This used to be an issue when starting playback, but this was fixed when you did some auto buffering changes back a few versions ago.

Inital playback works fine now, just when skipping forward I get this pause  when the next track starts.

Richard

We'll check to see if there's anything we can do on our end.

It's possible that some buffering will be unavoidable if the network can't pump the data fast enough for a lossless stream. 

[StarBand Guy]

It sounds as if I'm barking up the wrong tree here with the MTU, but for future reference you can pick up a utility that will help with this and other setting:

http://www.dslreports.com/drtcp

[rpalmer68]

Thaks Matt,

This has only just started happening in the last few builds, it used to be fine.

Maybe the updated WMA codecs that have been installed with the last builds  have changed things.

Anyway, I'm going to switch to Direct Sound anyway, so I guess it isn't that important for me.

I just thought I should let you know that it stutters now and didn't used to.

Cheers
Richard

[hit_ny]

DirectSound is known to be more skip resistant on Win2k/XP.

Funny as this may sound, i found Direct Sound more skip resistant on XP than in 2K.

While i was on 2K, Wave out was the only option that worked well.

[Alex B]

I guess your XP has newer DirectX. Probably your soundcard drivers are also newer if you have still the same HW setup.