Closed GoogleCodeExporter closed 9 years ago
I see that issue 4 looks to be the same issue, not sure how I missed that
earlier.
I just tried something I had tried before (completely wipe all signs of P# and
just install 1.50) and this time all tested MP3s start but a few seconds to a
few minutes in to playback, P# locks up.
You mentioned v1.51 .. is that available or should I wait patiently for the
re-release of 1.60?
Original comment by kzinn...@gmail.com
on 9 Feb 2013 at 12:29
Thanks for posting this.
I cannot replicate it with this MP3.
Last week I had a lockup too with another file, or another machine (Windows 7
too), and it does replicate.
That is why I froze the release of ver 1.6. On that machine the lock up
happened on 1.5.1 as well.
I'm not sure what it is.
It could be a faulty logic (i.e. thread dead lock) or an issue with the
underlying NAudio engine (maybe the different sound card?)
Anyway, I will investigate it and find a fix. Please be patient, it might take
a few weeks. Sorry about the inconvenience.
When I'll release it (soon) it will be ver 1.6.1.
Original comment by yuva...@gmail.com
on 9 Feb 2013 at 3:44
Issue 4 has been merged into this issue.
Original comment by yuva...@gmail.com
on 9 Feb 2013 at 3:44
[deleted comment]
UPDATE
On one machine I have zero issues, as I mentioned (Windows 7 Pro 64 bit, Lenovo
S30 with on board sound card)
But on another laptop (Windows 7 Pro 64 bit, Lenovo X230 with on board sound
card, Real tek RTKVHD64.sys) I have a strange behavior which might be seen as a
lock up - putting a debug breakpoint while running, or making the speed faster
or other similar changes, cause an internal audio thread (non managed) to
exit..!!??
In my code there is logic that selects Wasapi/DirectSound/WaveOut based on the
OS.
The older versions of PracticeSharp used DirectSound. But it wasn't stable.
I suspected it is the underlying audio library, NAudio, so I changed the Wasapi
driver to WaveOut -> I cannot replicate the issue now. Turning back to Wasapi
replicated the issue immediately.
I'm going to contact the NAudio author and try to get some help on this.
In the mean time, I'm considering releasing 1.6.1 with WaveOut driver always
selected.
Original comment by yuva...@gmail.com
on 11 Feb 2013 at 1:26
I do not know why NAudio acts the way it does.
Move back to Waveout driver for all OS - it seems stable.
It is a workaround, not a real fix, but I cannot fix NAudio. Will raise it to
NAudio author.
Original comment by yuva...@gmail.com
on 5 Mar 2013 at 1:55
Related to defect #12
Original comment by yuva...@gmail.com
on 21 Mar 2013 at 1:54
Original issue reported on code.google.com by
kzinn...@gmail.com
on 9 Feb 2013 at 12:00