Go Back   Winamp & SHOUTcast Forums > Winamp > Winamp Discussion

Reply
Thread Tools Search this Thread Display Modes
Old 10th January 2016, 14:15   #241
pbelkner
Senior Member
 
Join Date: Jun 2010
Posts: 405
Quote:
Originally Posted by Aminifu View Post
In both cases, all the playback controls work as they should, including seeking back and forth within a playing track. The sound is great and the playback is smooth, without any skipping, stuttering, pops, or clicks. I've even been able reduced the size of both the ring and shared buffers, from their defaults.
Sounds perfect. Do you have any actual problem?

That the audio client is destroyed only in one case (and not in the other) is due to the WA side: only in the non-crossfading case it is issuing a "close" call leading to destruction.

EDIT: Is this the problem?
Quote:
Originally Posted by Aminifu View Post
The official DirectSound output plug-in (and the other output plug-in in my usual sound processing chain) didn't mind these flush calls being blocked, but YASAPI does (it was endlessly issuing "isplaying" requests).
BTW: The "isplaying" requests are issued from the WA side, and the question is why?

EDIT 2: Could you try it again with this updated debug version?

Last edited by pbelkner; 10th January 2016 at 16:04.
pbelkner is offline   Reply With Quote
Old 11th January 2016, 02:36   #242
Aminifu
Forum King
 
Aminifu's Avatar
 
Join Date: Aug 2011
Location: Chicago, IL
Posts: 4,612
After disabling NoFlush, I have no problems using YASAPI v1.0.0 instead of DirectSound with the other plug-ins I use in my usual Winamp configuration. An unexpected benefit of using YASAPI without NoFlush is that the working set of memory that Winamp was using has gone way down. Also if you decide to add the gapless playback feature, I wont need to use crossfading to accomplish the same effect.

I'm sorry post #240 is hard to understand. It was an attempt to explain the issue that I was talking about in post #237.

I'm not sure what you want me to try with the new debug version. Do you want traces with and without NoFlush enabled? What output level do you want me to set the trace log to?

The strangeness of what happens on the Winamp side of things is probably due to all the legacy code it contains. Resources were never allocated by AOL to rewrite many of the core routines. What I've learned over the years is that most bug fixes were accomplished by patching around things instead of making any fundamental changes. This is why it has been so hard for new developers to move things along in a timely fashion.

Winamp Pro 5.666.3516 fully-patched - Komodo X Touchscreen by Victhor skin
Windows 10 Home 64-bit desktop - Logitech Z906 5.1 speaker system
Aminifu is offline   Reply With Quote
Old 11th January 2016, 05:06   #243
pbelkner
Senior Member
 
Join Date: Jun 2010
Posts: 405
Quote:
Originally Posted by Aminifu View Post
Do you want traces with and without NoFlush enabled? What output level do you want me to set the trace log to?
What I'm interested in is a trace with the scenario that don't work. I suppose it is the one with NoFlush enabled. We may start with default level.
pbelkner is offline   Reply With Quote
Old 11th January 2016, 07:59   #244
Aminifu
Forum King
 
Aminifu's Avatar
 
Join Date: Aug 2011
Location: Chicago, IL
Posts: 4,612
Well, the sound output still stops when trying to start the next song. Winamp is still running according to the Applications tab in the Windows Task Manager. Now when I click on the stop, then play buttons, the task manager says Winamp is still running (instead of "not responding", which it said before). The trace log displays 1 more "setvolume volume: 1.00" response, but the track doesn't start playing.

Clicking stop then play again still wont make the track start. The task manager still says Winamp is running and the trace log displays 1 more "setvolume volume: 1.00" response.

Clicking the Winamp exit button causes Winamp to appear to shutdown. It disappears from the screen and from the Applications tab in the task manager, but winamp.exe is still displayed on the Processes tab after waiting several minutes. So, the only way to get Winamp to completely shutdown is to select and end the winamp.exe process. This causes several locked temp files to be left behind. They can only be deleted after re-booting.

I didn't change any of the YASAPI default settings. The debug trace runs until "loop started" when Winamp is started. Then runs until "audio client started" after starting playback. It then runs until "volume: 1.00" and stops when the next song tries to start.

PHP Code:
init
  module id
66391 (8557520)
  
plugin options created
  queue available semaphore created
  queue written semaphore created
  queue mutex created
  queue created
  store mutex created
  store available semaphore created
  store created
  event created
  waitable timer created
  thread created
  REQUEST_CREATE
  device enumerator created
  device collection created
  got device count
2
  player 
array allocated
    player device created
    id
"{0.0.0.00000000}.{4a95550d-21a8-411b-9571-a248189e991b}"
    
player property store created
    name
"Speakers (Creative SB Audigy)"
    
player options created
  player 0 created
    player device created
    id
"{0.0.0.00000000}.{a62ee8dc-6996-4d59-a38b-40e4e675a5fd}"
    
player property store created
    name
"SPDIF Out (Creative SB Audigy)"
    
player options created
  player 1 created
  device
"Speakers (Creative SB Audigy)"
  
loop started
setvolume
  volume
1.00
open
  wasapi clock
  REQUEST_OPEN
  samplerate
44100
  numchannels
6
  bitspersamp
16
  audio client created
  got device period
    
default: 100000 hns
    minimum
30000 hns
    choosen
100000 hns
  device period scaled by 7.00 
(device period700400)
  
intitializing audio client EXCLUSIVE/PUSH with 700400/0 hns
  audio client initialized
  audio clock created
  SHARED BUFFER SIZE
3528 frames
  START AUDIO CLIENT
4032 frames
  audio render client created
  RING BUFFER SIZE
17856 frames (5.06)
  
ring buffer created
  uFramesRing
4096uFramesMin4032 (17856)
  
audio client started
  stopping audio client
  uFramesRing
4664uFramesMin4032 (17856)
  
audio client started
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
setvolume
  volume
1.00 

Winamp Pro 5.666.3516 fully-patched - Komodo X Touchscreen by Victhor skin
Windows 10 Home 64-bit desktop - Logitech Z906 5.1 speaker system
Aminifu is offline   Reply With Quote
Old 11th January 2016, 09:28   #245
pbelkner
Senior Member
 
Join Date: Jun 2010
Posts: 405
Quote:
Originally Posted by Aminifu View Post
Then runs until "audio client started" after starting playback. It then runs until "volume: 1.00" and stops when the next song tries to start.
Could you please try it again with the updated debug version 1.0.2?
pbelkner is offline   Reply With Quote
Old 11th January 2016, 09:46   #246
Aminifu
Forum King
 
Aminifu's Avatar
 
Join Date: Aug 2011
Location: Chicago, IL
Posts: 4,612
Same results.
PHP Code:
init
  module id
66391 (9004888)
  
plugin options created
  queue available semaphore created
  queue written semaphore created
  queue mutex created
  queue created
  store mutex created
  store available semaphore created
  store created
  event created
  waitable timer created
  thread created
  REQUEST_CREATE
  device enumerator created
  device collection created
  got device count
2
  player 
array allocated
    player device created
    id
"{0.0.0.00000000}.{4a95550d-21a8-411b-9571-a248189e991b}"
    
player property store created
    name
"Speakers (Creative SB Audigy)"
    
player options created
  player 0 created
    player device created
    id
"{0.0.0.00000000}.{a62ee8dc-6996-4d59-a38b-40e4e675a5fd}"
    
player property store created
    name
"SPDIF Out (Creative SB Audigy)"
    
player options created
  player 1 created
  device
"Speakers (Creative SB Audigy)"
  
loop started
setvolume
  volume
1.00
open
  wasapi clock
  REQUEST_OPEN
  samplerate
44100
  numchannels
6
  bitspersamp
16
  audio client created
  got device period
    
default: 100000 hns
    minimum
30000 hns
    choosen
100000 hns
  device period scaled by 7.00 
(device period700400)
  
intitializing audio client EXCLUSIVE/PUSH with 700400/0 hns
  audio client initialized
  audio clock created
  SHARED BUFFER SIZE
3528 frames
  START AUDIO CLIENT
4032 frames
  audio render client created
  RING BUFFER SIZE
17856 frames (5.06)
  
ring buffer created
  uFramesRing
4096uFramesMin4032 (17856)
  
audio client started
  stopping audio client
  uFramesRing
4664uFramesMin4032 (17856)
  
audio client started
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
setvolume
  volume
1.00 

Winamp Pro 5.666.3516 fully-patched - Komodo X Touchscreen by Victhor skin
Windows 10 Home 64-bit desktop - Logitech Z906 5.1 speaker system
Aminifu is offline   Reply With Quote
Old 11th January 2016, 10:41   #247
pbelkner
Senior Member
 
Join Date: Jun 2010
Posts: 405
Quote:
Originally Posted by Aminifu View Post
Same results.
Thanks for trying. Then we can forget it.
pbelkner is offline   Reply With Quote
Old 11th January 2016, 10:57   #248
Aminifu
Forum King
 
Aminifu's Avatar
 
Join Date: Aug 2011
Location: Chicago, IL
Posts: 4,612
In the absence of another request from Winamp (within an appropriate delay) after a "setvolume" can you just stop and restart the audio client or recreate and start it (whichever is appropriate depending on it's previous state)?

Winamp Pro 5.666.3516 fully-patched - Komodo X Touchscreen by Victhor skin
Windows 10 Home 64-bit desktop - Logitech Z906 5.1 speaker system
Aminifu is offline   Reply With Quote
Old 11th January 2016, 11:17   #249
pbelkner
Senior Member
 
Join Date: Jun 2010
Posts: 405
Quote:
Originally Posted by Aminifu View Post
In the absence of another request from Winamp (within an appropriate delay) after a "setvolume" can you just stop and restart the audio client or recreate and start it (whichever is appropriate depending on it's previous state)?
We are able to see a sequence of "ispalying" requests. That's what is expected because they represent a "draining" of the plugin returning 1. The last "isplaying" request returns 0 in order to signal that draining is finished. Typically a "close" or a "flush" request follows shutting down or stopping, respectively, the audio client.

In your case it just continues. I now added a "stop audio client" to the final "isplaying". Could you please try another updated version 1.0.3?
pbelkner is offline   Reply With Quote
Old 11th January 2016, 11:48   #250
Aminifu
Forum King
 
Aminifu's Avatar
 
Join Date: Aug 2011
Location: Chicago, IL
Posts: 4,612
I have good news and bad news.

The audio output now continues like it should on subsequent tracks. However the progress indicator (seek bar) and the time remaining/elapsed display in the skin I'm using are not working right. They have lost sync somehow and either don't start or only start to work when next song is almost over. So, when they do start working, they indicate that the song is just starting when it is really almost over.

I seldom do it, but I'm also not able to seek within the playing song. I guess the flush request from Winamp is 1 of the things needed for that, so blocking it is not a good idea afterall.

PHP Code:
init
  module id
66391 (3499864)
  
plugin options created
  queue available semaphore created
  queue written semaphore created
  queue mutex created
  queue created
  store mutex created
  store available semaphore created
  store created
  event created
  waitable timer created
  thread created
  REQUEST_CREATE
  device enumerator created
  device collection created
  got device count
2
  player 
array allocated
    player device created
    id
"{0.0.0.00000000}.{4a95550d-21a8-411b-9571-a248189e991b}"
    
player property store created
    name
"Speakers (Creative SB Audigy)"
    
player options created
  player 0 created
    player device created
    id
"{0.0.0.00000000}.{a62ee8dc-6996-4d59-a38b-40e4e675a5fd}"
    
player property store created
    name
"SPDIF Out (Creative SB Audigy)"
    
player options created
  player 1 created
  device
"Speakers (Creative SB Audigy)"
  
loop started
setvolume
  volume
1.00
open
  wasapi clock
  REQUEST_OPEN
  samplerate
44100
  numchannels
6
  bitspersamp
16
  audio client created
  got device period
    
default: 100000 hns
    minimum
30000 hns
    choosen
100000 hns
  device period scaled by 7.00 
(device period700400)
  
intitializing audio client EXCLUSIVE/PUSH with 700400/0 hns
  audio client initialized
  audio clock created
  SHARED BUFFER SIZE
3528 frames
  START AUDIO CLIENT
4032 frames
  audio render client created
  RING BUFFER SIZE
17856 frames (5.06)
  
ring buffer created
  uFramesRing
4096uFramesMin4032 (17856)
  
audio client started
  stopping audio client
  uFramesRing
4664uFramesMin4032 (17856)
  
audio client started
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
  stopping audio client
setvolume
  volume
1.00
  uFramesRing
4096uFramesMin4032 (17856)
  
audio client started
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
isplaying
  REQUEST_ISPLAYING
  stopping audio client
setvolume
  volume
1.00
  uFramesRing
4096uFramesMin4032 (17856)
  
audio client started 

Winamp Pro 5.666.3516 fully-patched - Komodo X Touchscreen by Victhor skin
Windows 10 Home 64-bit desktop - Logitech Z906 5.1 speaker system
Aminifu is offline   Reply With Quote
Old 11th January 2016, 12:10   #251
pbelkner
Senior Member
 
Join Date: Jun 2010
Posts: 405
Quote:
Originally Posted by Aminifu View Post
However the progress indicator (seek bar) and the time remaining/elapsed display in the skin I'm using are not working right.
It's just a try: out_yasapi debug 1.0.4.

EDIT: Another try: out_yasapi debug 1.0.5.
pbelkner is offline   Reply With Quote
Old 11th January 2016, 13:07   #252
Aminifu
Forum King
 
Aminifu's Avatar
 
Join Date: Aug 2011
Location: Chicago, IL
Posts: 4,612
I think you almost nailed it with v1.0.4.

The progress bar and remaining/elapsed timer are working again. My guess about flush being needed for seeking was wrong. Seeking works fine as long as the progress bar is working.

I'm now hearing occasional distortion in subsequent songs, so I've been adjusting the buffering to see if I could stop it. That helped some, but has not stopped it. I also noticed that the timing shown in the debug trace doesn't match the timing set in the GUI.

Anyway, I'll try v1.0.5 now.

Winamp Pro 5.666.3516 fully-patched - Komodo X Touchscreen by Victhor skin
Windows 10 Home 64-bit desktop - Logitech Z906 5.1 speaker system
Aminifu is offline   Reply With Quote
Old 11th January 2016, 13:26   #253
Aminifu
Forum King
 
Aminifu's Avatar
 
Join Date: Aug 2011
Location: Chicago, IL
Posts: 4,612
It appears v1.0.5 is the charm.

Everything is running fine and sounding great. I'll let it play through another half hour or so and let you know it anything changes.

Winamp Pro 5.666.3516 fully-patched - Komodo X Touchscreen by Victhor skin
Windows 10 Home 64-bit desktop - Logitech Z906 5.1 speaker system
Aminifu is offline   Reply With Quote
Old 11th January 2016, 13:34   #254
pbelkner
Senior Member
 
Join Date: Jun 2010
Posts: 405
Quote:
Originally Posted by Aminifu View Post
It appears v1.0.5 is the charm.
Ok, that's fine! You may try it one or two days than I'll make an official bug fix release.
pbelkner is offline   Reply With Quote
Old 13th January 2016, 06:49   #255
pbelkner
Senior Member
 
Join Date: Jun 2010
Posts: 405
v1.0.6

What's new?
  • Detect end of track by respective "isplaying" request.
  • Fixed bug regarding synchronization of Share Mode and Strategy options.
Links:
pbelkner is offline   Reply With Quote
Old 13th January 2016, 18:15   #256
Aminifu
Forum King
 
Aminifu's Avatar
 
Join Date: Aug 2011
Location: Chicago, IL
Posts: 4,612
Thank you for version 1.0.6.

I just noticed on my system that the sound is not cut off in exclusive mode for system sounds and for my apps that connect to the internet. I can hear the audio and a rapid clicking noise. For example, the sound effects when deleting stuff from the recycle bin, the sound effects in the Internet Backgammon game, and when browsing an internet site and a video starts playing. This happens with both the normal and sse2 versions.

I also see that the Windows volume mixer is disabled which I assume is normal for the way you're implementing exclusive mode.

Winamp Pro 5.666.3516 fully-patched - Komodo X Touchscreen by Victhor skin
Windows 10 Home 64-bit desktop - Logitech Z906 5.1 speaker system
Aminifu is offline   Reply With Quote
Old 14th January 2016, 01:42   #257
pbelkner
Senior Member
 
Join Date: Jun 2010
Posts: 405
Quote:
Originally Posted by Aminifu View Post
I just noticed on my system that the sound is not cut off in exclusive mode for system sounds and for my apps that connect to the internet. [...] This happens with both the normal and sse2 versions.
Please double check the configuration (in particular whether you have shared instead of exclusive mode). It's working as expected on my site. Also it's close to impossible that the non-debug versions behave different from the debug version. They are compiled from the same source with just most of the tracing macros having an empty implementation. Please have in mind that each version has to be configured on their own because each version has it's own property file.
pbelkner is offline   Reply With Quote
Old 14th January 2016, 16:27   #258
Aminifu
Forum King
 
Aminifu's Avatar
 
Join Date: Aug 2011
Location: Chicago, IL
Posts: 4,612
Quote:
Originally Posted by pbelkner View Post
Please double check the configuration (in particular whether you have shared instead of exclusive mode). It's working as expected on my site. ...
If no one else reports this, then it must be unique to my system. I do have a very old soundcard and it's driver was modified to work with Windows 7.

I first noticed it with the 1.0.5 debug version and you released 1.0.6 before I could verify it was only happening when using the plug-in. Then I tested version 1.0.6 too. I even tested with the 1.0.6 debug version. I made sure all the versions were running in exclusive mode with default settings and newly created property files each time. In fact, the only way I can switch to shared mode is to edit the property files. When I switch mode in the GUI and restart Winamp, it switches back. Shared mode works as it should, sound from everything and no clicking noises.

After verifying the issue happened with default settings in each version, I tried changing a few settings (e.g. push vs. pull, different buffer sizes, write block on and off) which didn't fix it.

It's not a big deal since there are many ways to work around the issue.

Winamp Pro 5.666.3516 fully-patched - Komodo X Touchscreen by Victhor skin
Windows 10 Home 64-bit desktop - Logitech Z906 5.1 speaker system
Aminifu is offline   Reply With Quote
Old 14th January 2016, 17:12   #259
pbelkner
Senior Member
 
Join Date: Jun 2010
Posts: 405
Quote:
Originally Posted by Aminifu View Post
I first noticed it with the 1.0.5 debug version
Exactly this could happen starting from 0.16.0 until 1.0.5. I noticed it myself and fixed it (it was due to dropping the page with the device list):
  • Fixed bug regarding synchronization of Share Mode and Strategy options.
But I cannot reproduce this with 1.0.6. I even downloaded 1.0.6 from sourceforge myself before testing again to make sure I was not mixed up during upload.
pbelkner is offline   Reply With Quote
Old 14th January 2016, 20:10   #260
Aminifu
Forum King
 
Aminifu's Avatar
 
Join Date: Aug 2011
Location: Chicago, IL
Posts: 4,612
It's still happening for me. We need to wait to see if anyone else reports it. Below are the contents of the yasapi.dll v1.0.6 property file.

PHP Code:
[plugin]
id={0.0.0.00000000}.{4a95550d-21a8-411b-9571-a248189e991b}
mono2stereo=1
volume
=0
block_write
=1
format_supported
=0
audioclock
=1
visualization
=1
page
=0
posx
=737
posy
=299
[{0.0.0.00000000}.{4a95550d-21a8-411b-9571-a248189e991b}]
share_mode=1
device_period
=0
autoconvertpcm
=1
src_default_quality
=0
pull
=0
balance
=0
balance_start
=0.500000
ring_size
=5.000500
ring_fill
=1.000000
share_size
=7.004000 

Winamp Pro 5.666.3516 fully-patched - Komodo X Touchscreen by Victhor skin
Windows 10 Home 64-bit desktop - Logitech Z906 5.1 speaker system
Aminifu is offline   Reply With Quote
Old 17th January 2016, 21:59   #261
Aminifu
Forum King
 
Aminifu's Avatar
 
Join Date: Aug 2011
Location: Chicago, IL
Posts: 4,612
Quote:
Originally Posted by Aminifu View Post
An unexpected benefit of using YASAPI without NoFlush is that the working set of memory that Winamp was using has gone way down.
I just found out that the massive drop in memory usage was not due to using YASAPI (with or without NoFlush). The actual cause of the high memory usage was due to a memory leak in the Stereo Tool DSP plug-in. The current version of Stereo Tool (7.84) fixes the memory leak.

The memory usage is still high when Winamp first starts, but drops down after the 2nd or 3rd song is played. I had been living with the high memory usage for a long time (from when I started using Stereo Tool) and thought it was normal. I even added more RAM to my system to compensate.

Winamp Pro 5.666.3516 fully-patched - Komodo X Touchscreen by Victhor skin
Windows 10 Home 64-bit desktop - Logitech Z906 5.1 speaker system
Aminifu is offline   Reply With Quote
Old 19th January 2016, 15:44   #262
~aZu~
Junior Member
 
Join Date: Jan 2016
Posts: 5
Hi there, no matter which setup i chose, always came out with this error

UNKNOWN: "yasapi_session.c" (314)

Please help. I'm using Lexicon Lambda USB which has its own ASIO driver.
Attached Thumbnails
Click image for larger version

Name:	Capture.PNG
Views:	198
Size:	5.5 KB
ID:	52214  
~aZu~ is offline   Reply With Quote
Old 21st January 2016, 03:19   #263
pbelkner
Senior Member
 
Join Date: Jun 2010
Posts: 405
Quote:
Originally Posted by ~aZu~ View Post
Hi there, no matter which setup i chose, always came out with this error

UNKNOWN: "yasapi_session.c" (314)
This is the result from a call to IAudioClient::Initialize (cf. What is YASAPI?).

Could you please provide a trace (also with Test Format checked)?
pbelkner is offline   Reply With Quote
Old 21st January 2016, 03:52   #264
~aZu~
Junior Member
 
Join Date: Jan 2016
Posts: 5
Quote:
Originally Posted by pbelkner View Post
This is the result from a call to IAudioClient::Initialize (cf. What is YASAPI?).

Could you please provide a trace (also with Test Format checked)?
Hi there, how do i do a trace? Sorry bit new here.
~aZu~ is offline   Reply With Quote
Old 21st January 2016, 05:46   #265
pbelkner
Senior Member
 
Join Date: Jun 2010
Posts: 405
Quote:
Originally Posted by ~aZu~ View Post
how do i do a trace?
  1. Download the latest debug version.
  2. Switch on debug (level 1).
  3. Run the the plugin.
  4. From the debug console, copy the output into the forum's PHP tags (from the above menu).
pbelkner is offline   Reply With Quote
Old 21st January 2016, 06:09   #266
~aZu~
Junior Member
 
Join Date: Jan 2016
Posts: 5
Quote:
Originally Posted by pbelkner View Post
  1. Download the latest debug version.
  2. Switch on debug (level 1).
  3. Run the the plugin.
  4. From the debug console, copy the output into the forum's PHP tags (from the above menu).
PHP Code:
init
  module id
66391 (8478360)
  
plugin options created
  queue available semaphore created
  queue written semaphore created
  queue mutex created
  queue created
  store mutex created
  store available semaphore created
  store created
  event created
  waitable timer created
  thread created
  REQUEST_CREATE
  device enumerator created
  device collection created
  got device count
3
  player 
array allocated
    player device created
    id
"{0.0.0.00000000}.{2c153437-5caf-4127-8e7d-47399196f22a}"
    
player property store created
    name
"1 - TOSHIBA-TV (AMD High Definition Audio Device)"
    
player options created
  player 0 created
    player device created
    id
"{0.0.0.00000000}.{4a358cf8-0d89-44d9-8530-f042dfc7c9f5}"
    
player property store created
    name
"Speakers (7- USB Audio Device)"
    
player options created
  player 1 created
    player device created
    id
"{0.0.0.00000000}.{87573021-e9e7-40a2-b8fb-ae1f624ea636}"
    
player property store created
    name
"Realtek Digital Output (Realtek High Definition Audio)"
    
player options created
  player 2 created
  device
"Speakers (7- USB Audio Device)"
  
loop started
setvolume
  volume
1.00
open
  wasapi clock
  REQUEST_OPEN
  samplerate
48000
  numchannels
2
  bitspersamp
16
  audio client created
  format supported
  got device period
    
default: 100000 hns
    minimum
30000 hns
    choosen
100000 hns
  device period scaled by 7.00 
(device period700400)
  
intitializing audio client EXCLUSIVE/PUSH with 700400/0 hns
UNKNOWN
"yasapi_session.c" (314).
Error initializing audio client"yasapi_session.c" (315).
close
setvolume
  volume
1.00
open
  wasapi clock
  REQUEST_OPEN
  samplerate
48000
  numchannels
2
  bitspersamp
16
  audio client created
  format supported
  got device period
    
default: 100000 hns
    minimum
30000 hns
    choosen
100000 hns
  device period scaled by 7.00 
(device period700400)
  
intitializing audio client EXCLUSIVE/PUSH with 700400/0 hns
UNKNOWN
"yasapi_session.c" (314).
Error initializing audio client"yasapi_session.c" (315).
close 
I am using Windows 10 x64, AMD A10-7850K Processor.
~aZu~ is offline   Reply With Quote
Old 21st January 2016, 06:38   #267
pbelkner
Senior Member
 
Join Date: Jun 2010
Posts: 405
Quote:
Originally Posted by ~aZu~ View Post
PHP Code:
init 
Many thanks.

How it looks with Test Format enabled?
pbelkner is offline   Reply With Quote
Old 21st January 2016, 08:40   #268
~aZu~
Junior Member
 
Join Date: Jan 2016
Posts: 5
Quote:
Originally Posted by pbelkner View Post
Many thanks.

How it looks with Test Format enabled?
PHP Code:
init
  module id
66391 (10588712)
  
plugin options created
  queue available semaphore created
  queue written semaphore created
  queue mutex created
  queue created
  store mutex created
  store available semaphore created
  store created
  event created
  waitable timer created
  thread created
  REQUEST_CREATE
  device enumerator created
  device collection created
  got device count
3
  player 
array allocated
    player device created
    id
"{0.0.0.00000000}.{2c153437-5caf-4127-8e7d-47399196f22a}"
    
player property store created
    name
"1 - TOSHIBA-TV (AMD High Definition Audio Device)"
    
player options created
  player 0 created
    player device created
    id
"{0.0.0.00000000}.{4a358cf8-0d89-44d9-8530-f042dfc7c9f5}"
    
player property store created
    name
"Speakers (7- USB Audio Device)"
    
player options created
  player 1 created
    player device created
    id
"{0.0.0.00000000}.{87573021-e9e7-40a2-b8fb-ae1f624ea636}"
    
player property store created
    name
"Realtek Digital Output (Realtek High Definition Audio)"
    
player options created
  player 2 created
  device
"Speakers (7- USB Audio Device)"
  
loop started
setvolume
  volume
1.00
open
  wasapi clock
  REQUEST_OPEN
  samplerate
44100
  numchannels
2
  bitspersamp
16
  audio client created
  format supported
  got device period
    
default: 100000 hns
    minimum
30000 hns
    choosen
100000 hns
  device period scaled by 7.00 
(device period700400)
  
intitializing audio client EXCLUSIVE/PULL with 700400/700400 hns
UNKNOWN
"yasapi_session.c" (314).
Error initializing audio client"yasapi_session.c" (315).
close 
It happened right at the beginning of the playback. Weird thing is, playback only works after i initiate the exclusive mode via foobar Wasapi plugin. It's like Yasapi couldn't read my audio driver or something like that.
~aZu~ is offline   Reply With Quote
Old 21st January 2016, 09:22   #269
pbelkner
Senior Member
 
Join Date: Jun 2010
Posts: 405
Quote:
Originally Posted by ~aZu~ View Post
It happened right at the beginning of the playback. Weird thing is, playback only works after i initiate the exclusive mode via foobar Wasapi plugin. It's like Yasapi couldn't read my audio driver or something like that.
It's hard to tell because it's not one out of the documented error messages from IAudioClient::Initialize. Because the failing call to IAudioClient::Initialize happens on your system (and not on others, e.g. mine where it is successful) you should find out why or at least give a hint. Based on the information provided so far I'm unable to draw any conclusion.

Are you sure that FB2000 doesn't interfere in an un-expected way with YASAPI? What happens when you re-start your PC and then, without starting FB2000, just running WA with YASAPI? You should have in mind that a WASAPI exclusive connection can exist to only one process.

EDIT: Yo may consider decreasing device period. My setting is minimal Device Period scaled by 1.0 and Ring Buffer scaled by 1.5.
pbelkner is offline   Reply With Quote
Old 28th January 2016, 13:19   #270
~aZu~
Junior Member
 
Join Date: Jan 2016
Posts: 5
Quote:
Originally Posted by pbelkner View Post
It's hard to tell because it's not one out of the documented error messages from IAudioClient::Initialize. Because the failing call to IAudioClient::Initialize happens on your system (and not on others, e.g. mine where it is successful) you should find out why or at least give a hint. Based on the information provided so far I'm unable to draw any conclusion.

Are you sure that FB2000 doesn't interfere in an un-expected way with YASAPI? What happens when you re-start your PC and then, without starting FB2000, just running WA with YASAPI? You should have in mind that a WASAPI exclusive connection can exist to only one process.

EDIT: Yo may consider decreasing device period. My setting is minimal Device Period scaled by 1.0 and Ring Buffer scaled by 1.5.
Hello there, i figured out it must be something wrong with my devices or installation, as other exclusive-mode plugins on Winamp also not working properly. So i reinstalled my ASIO driver and Winamp, since then it is working as it should. Now i can enjoy my music again. Thanks for your help.
~aZu~ is offline   Reply With Quote
Old 30th January 2016, 06:32   #271
pbelkner
Senior Member
 
Join Date: Jun 2010
Posts: 405
Quote:
Originally Posted by ~aZu~ View Post
i figured out it must be something wrong with my devices or installation, as other exclusive-mode plugins on Winamp also not working properly.
Thank you for giving this feedback because it could be helpful for others as well!

Of course, in case of an error it could be YASAPI going wrong. However, as time goes on it becomes less likely and and everybody facing a problem should have in mind that also the environment could be the reason for letting a WASAPI call fail (cf. What is YASAPI?):
Quote:
Originally Posted by ~aZu~ View Post
i reinstalled my ASIO driver and Winamp, since then it is working as it should.
pbelkner is offline   Reply With Quote
Old 9th April 2016, 07:20   #272
pbelkner
Senior Member
 
Join Date: Jun 2010
Posts: 405
v1.0.7

What's new?
  • In order to have YASAPI in a well defined state from the very first beginning, reset the IAudioClient interface at start-up.
Links:
pbelkner is offline   Reply With Quote
Old 24th April 2016, 12:45   #273
carmatic
Member
 
Join Date: Jul 2001
Posts: 53
Send a message via ICQ to carmatic
i have installed your plugin on a fresh install of winamp on a fresh install of windows 10, and on the plugin list it says 'NOT LOADED'

did what i just said make any sense to you?
carmatic is offline   Reply With Quote
Old 24th April 2016, 13:47   #274
ryerman
Major Dude
 
ryerman's Avatar
 
Join Date: Mar 2010
Location: Canada
Posts: 586
Quote:
Originally Posted by carmatic View Post
i have installed your plugin on a fresh install of winamp on a fresh install of windows 10, and on the plugin list it says 'NOT LOADED'
Make sure Winamp is running in "Full Mode", not "Safe Mode"

Windows 10 Home, 64 bit, Winamp 5.666, Bento Skin
ryerman is offline   Reply With Quote
Old 5th May 2016, 19:17   #275
chros
Member
 
chros's Avatar
 
Join Date: Nov 2003
Posts: 73
Quote:
Originally Posted by pbelkner View Post
What's new?
  • In order to have YASAPI in a well defined state from the very first beginning, reset the IAudioClient interface at start-up.
Links:
Thanks for the new release. Any news about including the Default Sound device in the device list?
Thanks
chros is offline   Reply With Quote
Old 6th May 2016, 13:23   #276
pbelkner
Senior Member
 
Join Date: Jun 2010
Posts: 405
Quote:
Originally Posted by chros View Post
Any news about including the Default Sound device in the device list?
Thanks
Expect it by the end of May or in June.
pbelkner is offline   Reply With Quote
Old 6th May 2016, 13:37   #277
Stone Free
Senior Member
 
Join Date: Feb 2001
Posts: 107
Would it theoretically be possible to create a Chrome extension that allows you to forward the sound from On Demand websites through the HDMI output?

I've always loved how Media Player Classic can be setup to correctly output down HDMI so you can use it for home cinema.

Apple seems to make this easier than Windows 10 does.
Stone Free is offline   Reply With Quote
Old 6th May 2016, 14:25   #278
chros
Member
 
chros's Avatar
 
Join Date: Nov 2003
Posts: 73
Quote:
Originally Posted by pbelkner View Post
Expect it by the end of May or in June.
A huge thanks for this!
chros is offline   Reply With Quote
Old 12th May 2016, 18:41   #279
osmosis
Major Dude
 
osmosis's Avatar
 
Join Date: Jan 2006
Location: Cananada
Posts: 838
Quote:
Originally Posted by pbelkner View Post
Expect it by the end of May or in June.
Great work! Started using this recently after upgrading to Windows 10. Any chance of gapless playback making it in? Seems like the only thing missing from a well-written buffered solution like this.

Request: A little SmartView Query Language love.
osmosis is offline   Reply With Quote
Old 12th May 2016, 21:30   #280
Koopa
16-Bit Moderator
 
Koopa's Avatar
 
Join Date: Apr 2004
Posts: 4,338
Will add this to Backup Tool.

out_yasapi.ini is the only config file?
Koopa is offline   Reply With Quote
Reply
Go Back   Winamp & SHOUTcast Forums > Winamp > Winamp Discussion

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump