31
Questions / Re: Issues when analysing / writing replay gain tags of my FLAC archieve
« on: April 28, 2019, 11:54:10 AM »
I only know of Ctrl-Shift-V, which is what I use.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
I have this issue as well.
I found its related to the sound card and higher sample rates. My device supports upto 96 driverless, and 192 with drivers, but when playing asio 192khz I get crazy distortion, then when I play 172khz I get distortion as well. When I play 96 then play 172 it plays fine (I think the device is down sampling it since it doesn't support it)
I'm not entirely sure this is musicbee's fault, since all <96khz works no mater how fast I change songs, sounds more hardware related.
Strictly from a technical interested point of view, and not to discredit your request:
What specifically would mess-up your workflow or results if you would set MusicBee to use Wasapi for your ADI-2 Pro?
I would really appreciate if the people behind MusicBee and its ASIO driver would take a deeper look:Just to clarify: there are no "people" behind MB. It is developed and maintained by one person - Steven. He does this in his spare time and asks for nothing in return. Users who offer him money as an incentive to fix something are wasting their time, and will more than likely get ignored. Users who badger him to fix/add things will also likely get ignored. Users who bump their issue every six hours are likely to be ignored. Steven implements new features and fixes bugs as he sees fit. With the complexity and time involved being key factors. Note that I don't speak for him but I just wanted you to have a fuller understanding of who is behind MB and how he operates
if it would be the driver then it would cause issues also with foobar2000, but with foobar2000 all is fine.Not necessarily. In very simplified terms, the stream of data being fed into the driver has a source, and not all source/driver combinations get along. Incompatibilities often manifest as a digitally distorted audio stream, such as the one you described. If MB was the source of the problem, large numbers of other users would be experiencing the issue as well, and that simply isn't evident in the forums. So, it's more likely that the issue is unique to your setup. This is why the driver is suspect, most users of the hardware you have are not using MB so the driver probably isn't used with MB often.
Please note that I've taken time out of my day to offer assistance. If you are going to dismiss a simple and basic troubleshooting step out of hand, you're not as likely to receive additional assistance from others here. We're all volunteers, including the developer.
Nice dac tubescreamer!
The asio component that BASS (MB's audio-engine) is using, is already a few years old, and doesn't seem to get a lot of support or updates.
Not sure if the cause of your well-explained issue is related to that, but it might.
A thought: have you tried the asio4all driver?
It's manufacturer-independent, but even some manufacturers 'that can't be bothered' to improve their asio drivers point to it.
(not that I would suspect RME of doing such?)
You'll have to wait and see if MusicBee's developer sees something in your report that would get him interested to investigate this.