getmusicbee.com
Support => Questions => Topic started by: alec.tron on January 22, 2018, 06:45:31 AM
-
Heya,
first time I noticed - most I have is mp3s & flacs in 44.1kHz - but there are a handfull of different file encodings / sample rate combinations - namely a few 32kHz mp3s, and a few flacs in 48kHz and 96kHz.
I just noticed it on a 32kHz one which I have had for a long time, and which play fine in everything else - but in MB 3.2 patched, these play at a much faster speed... similarly, the 96kHz play less than half the speed they are meant to be played.
I assume 44.1kHz is base-line... so 48kHz ones would be playing slightly slower as well...
Is this known / expected / intended or to-be-fixed ? Or am I the only one seeing this...
This is with ASIO only - when switching to Direct Sound or WASAPI all play fine again.
Cheers.
c.
-
It's a known issue. Search the bug reports forum, and you will find several.
-
There is an issue with speeding up for ASIO (and WASAPI?) when a BassBox graphic visualiser is active. And for ASIO some people say playing a second track at a different sample rate causes sound distortion.
But this sounds like a different issue, so can you PM me a link to one of the problem files.
Also does it happen if the only thing you do is play one of the problem files?
-
Hey - I only just remembered this thread seeing some of the other asio/kHz threads.
Here's a file with 22kHz (& 96kbps...) from a free release, playing a lot faster than intended...
https://files.fm/u/cb8h7zwt
Also, as I have read that in one of the other threads this might be a bass issues, but even with this patch:
https://getmusicbee.com/forum/index.php?topic=23992.msg140544#msg140544
I now get a fair bit of issues - first of non-descript error:
[Error
Unable To Start Playback]
After playing the above file fine first, MB won't play any other samplerate files anymore from the looks.
Oh, actually, I'm lying... now MB won't play any files anymore at all, no matter the samplerate, and all I get is the above error, even the 22kHz one is erroring now which I started with.
I'll restart MB.
After a restart, I was able to jump between different resolution files again, only lower than 44.1kHz for now, which showed the usual sped-up playback behaviour I mentined here. But, then jumping back to higher than 44.1kHz, 48kHz ones played fine, but now I get the same error:
[Error
Unable To Start Playback]
But this time around with 96kHz samplerate files only. Other lower samplerate files play this time around still (but all show the speed up / slow down issues tied to samplerate from the looks...)
So very different behaviour all together seemingly depending on what is played in which order...?
Strange.
c.
-
I noticed there has been a bassasio.dll update on 1/30/2018 posted here:
https://www.un4seen.com/stuff/bassasio.zip
You might give this a try and see if anything changes (I only use WASAPI). When Steven added the newer bassmix.dll to the 3.2 patch, it helped some people with a stop/start playlist issue so sometimes these incremental developer updates can fix odd things.
-
i have no issues using ASIO and playing files with different sample rates, including the file made available.
However, i can see there is still one difference with the ASIO handling compared to v3.1, so i will make that change for the next v3.2 update
http://musicbee.niblseed.com/V3_2/MusicBee32_Patched.zip
-
I use WASAPI because of the tempo issues with ASIO, but after this change I ran a test. I was surprised to find that I can now only play one track, and then I get an unable to start playback error when going to any other track regardless of sample rate, even tracks ripped from the same CD. Never had that happen before.
DAC is a Schiit Modi Multibit, current drivers, Win10 64 bit.
(https://i.imgur.com/iuNag1n.png)
-
h ASIO, but after this change I ran a test. I was surprised to find that I can now only play one track, and then I get an unable to start playback error when going to any other track regardless of sample rate, even tracks ripped from the same CD. Never had that happen before.
Good to hear I'm not the only one seeing/hearing these issues, the speed up/down as well as the [Error Unable To Start Playback] that started happening recently.
Churs.
c.
-
are you using the latest patch version?
-
Just updated to today's patched 3.2 version to test - played the above 22kHz file, which played but showed the usual speed-up behaviour (I'm using Native Instruments A10 card & ASIO drivers, just in case that might matter), and same behaviour as yesterday - which is as soon as I switch to another track I get the error [Error Unable To Start Playback] right away & MB requires a restart.
I'll be away for a bit & won't be able to reply for a few weeks from today onwards though. Will test again when I'm back.
Churs.
c.
-
I think i found the issue. Could you try this version:
http://musicbee.niblseed.com/V3_2/MusicBee32_Patched.zip
could you also confirm you were double clicking or skipping playback to start the following track rather than letting the current song finish to completion
-
Hi Steven,
YES, that's exactly how I was having problems (double-clicking on a file with a different sample rate). When I previously reported that it worked fine, it was playing to completion and going on to the next file in my 'sample test' playlist, which has alternating 44.1/48khz sample rates.
You're the best! 8)
-
could you also confirm you were double clicking or skipping playback to start the following track rather than letting the current song finish to completion
I was double-clicking around my library to change tracks when testing. That issue is now resolved, I can click to any track without error.
-
Hi, I'm experiencing exactly this same problem but sadly the patched files didn't fix it. Any other ideas?
I can confirm the issue occurs when I double click on another song but also when I press the Back or Next button. Additionally, if I try clicking in another part of the song, the player no longer plays any music nor the track bar advances. I hope that this can be solved, I'm one of the cases where WASAPI makes a massive positive difference in the quality of sound.
-
This thread was about ASIO issues, not WASAPI. Make sure you aren't running anything else trying to use the same audio device when you're running WASAPI.
-
My bad, I arrived here from google because the mentions of WASAPI and since the issue is identical, I thought the fix would be too. How would I ensure that the system (or anything else) is not outputting the sound while connected to a sound device on WASAPI? Muting any source of sound one by one?
-
I think i found the issue. Could you try this version:
http://musicbee.niblseed.com/V3_2/MusicBee32_Patched.zip
could you also confirm you were double clicking or skipping playback to start the following track rather than letting the current song finish to completion
Heya,
confirming:
- grabbed the latest MB 3.2 patch from 22.2.2018 v 3.2.6626
- tried 44.1 khz file, all good
- tried 32 khz file, same speed up issue as before
- tried 96 khz file, same [Error - Unable To Start Playback] error
- tried 44.1 khz file again, all good
- I am usually double clicking
- I also tried navigating by keyboard, via arrows & enter keys, same exact behaviour with speed up and [Error - Unable To Start Playback]
- I also tried navigating by media keys, same exact behaviour with speed up and [Error - Unable To Start Playback] again respectively
Cheers.
c.
-
Some feedback, looks like the update to 3.2.6679 fixed the slow down issue on files with Samplerates lower than 44.1kHz (it quite possibly was in before this patch, but the previous patch I had running before was the first version that enabled playlist folders in exported iTunes xml files (3.2.6660 ? maybe ?) and on that I still saw the slow down happening).
Also 48kHz seem to play at normal speed now as well.
There is a few 96kHz files I have, and on all of which, when attempting to play, Musicbee throws a pop-up, claiming this still:
Error
Unable to start playback
Not a big issue for me, just wanted to mention it.
Churs.
c.