Author Topic: Possible Bug in buffering.  (Read 564 times)

purenoise

  • Posts: 115
Possible Bug in buffering.
« on: 25 May '21 - 16:29 »
Hi,
so i encountered a small issue, and
since i feel it could be a small bug
i will describe it:

 1. playing .mp3 from local hdd
 2. at some point drive gets 100% busy without data r/w
    [ i know this is possible issue with a drive, and i think
      this is issue with a sata port/cable; had this with other
      drive too]
 3. xmplay stops sound, and at this moment i press "pause", and
    after a moment i get short sound, and stops.
    [ drive is showing normal data r/w and activity, i assume
      xmplay buffered enough data]

 4. And my expectation that when i press "play/pause", i got
    playing, but no activity, no sound [ not freezed app], but
    if i do once "forward" and then "play", it plays.

This is not a big issue, and feels like really rare occurrence, but
i feel like it unexpected no-response from xmplay.
MPC-BE at the same situation but with video file continues play.

XMPlay 3.8.5.17

Hope this info help fix the bug[ if there is one], else
Thanks.

Ian @ un4seen

  • Administrator
  • Posts: 23890
Re: Possible Bug in buffering.
« Reply #1 on: 28 May '21 - 14:11 »
When you press play at step #4, is the play button in the "playing" state but the position isn't advancing, or is the position also advancing but you don't hear anything? To perhaps narrow it down, does the problem only happen when using the default output system, or also when using the DirectSound or WASAPI output plugins?

purenoise

  • Posts: 115
Re: Possible Bug in buffering.
« Reply #2 on: 28 May '21 - 17:11 »
WASAPI using mostly,
and controling xmplay with keyboard on custom keys.

I didn't inspect the gui, so i'm not sure 100% [ next time will note
everything], but i think pos bar got blank, and button was
solid darker, not blinking, gui felt like a freezed state, until i
'forward' and 'play'.

It felt like pressing 'play' was ignored, but not 'forward', and then 'play'.
Assuming lock on play was engaged, but fail to release after buffer was filled.

Thanks.

purenoise

  • Posts: 115
Re: Possible Bug in buffering.
« Reply #3 on: 15 Jul '21 - 15:23 »
Update/Report:

[ got again HDD 100% busy, and pressed Pause]
[ HDD got in the normal state in few seconds]

 - pressing Play from keyboard has no reaction [ play/pause button keeps blinking]
 - media position not advancing [ pause still engaged]
 - and get play same/loaded media only after the rewind [ back or forward] a few secs.
 - so it feels like some block is engaged only on Pause at this situation.

Hope it helps.
Thanks.

Ian @ un4seen

  • Administrator
  • Posts: 23890
Re: Possible Bug in buffering.
« Reply #4 on: 15 Jul '21 - 17:29 »
When the sound stops, does XMPlay switch itself to the paused state (the play button is flashing) or is that only after you press the play/pause button? If the latter, does pressing the button again resume? If not, is it only the keyboard shortcut that isn't working or does pressing the play button with the mouse have no effect either?

Does it only happen when using WASAPI output? If you're unsure, can you try using XMPlay's default output and see if it ever happens then too?

purenoise

  • Posts: 115
Re: Possible Bug in buffering.
« Reply #5 on: 15 Jul '21 - 18:36 »
[ Following all was on WASAPI. xmplay 3.8.5.25]
XMPlay does not stops by itself, i initiate Pause.

Situation 1:
 
 - during hdd 100% busy i did not interacted with a xmplay, and
   sound was uninterrupted flawlessly, so no stop, or issues here.

Situation 2:
 
 - at hdd busy state i press pause/play shortcut once to cut future
   data request
 - play/pause button flashing
 - keyboard shortcut play/pause does not work [ mouse press did not tested]
 - strange thing that play/pause works after back/forward.

[ now switched to 'default']

  - will test mouse pause.

Thanks.

purenoise

  • Posts: 115
Re: Possible Bug in buffering.
« Reply #6 on: 16 Jul '21 - 07:30 »
Update/Report:
[ Win10x64, xmplay\default sound output]

 1. Did Pause on hdd-busy state, and
 [ i got short spike of sound after pause]
 2. Play resumes sound normally.