Show Posts

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.

Messages - tubescreamer

Pages: 1 2 3 45
UPDATED 21.12.17:
- removed the old text, as I have made some more findings on this issue
- so you have the latest status here

Hi Steven,

how are you ? I am still very satisfied with MusicBee and using it now since many years. I hope you can help me with the following issue.
I upgraded already to the last version of MusicBee, which is 3.1.6512. But the problem is still there.

I have problems with the playback of audio files via ASIO driver when the sample rate differs much to each other.
BTW .. its out of question whether to workaround with WASABI or ASIO4ALL, I want (and need) to use the ASIO driver.

EDIT: also I can see that MusicBee changes the sample rate properly in all cases. The RME driver settings dialog shows me this.

Whats always possible and works nicely: playback of FLAC files with 44.1 or 48 kHz sample rate, where the sample rate change are only little. But as soon as I playback audio content with differs much in terms of sample rate, then I get kind of asynchronity which resultes in distortion / noise through the speakers.

1st I thought MusicBee has a general problem playing music content with higher sample rates than 48 kHz.
This is luckily not the case !!
But to be able to play a song in i.e. 44.1 or 48 and then play another in 88.1 or 96 then I have to:
1. terminate MusicBee
2. set the new sample rate manually in the ASIO driver, like i.e. 88.2 kHz
3. then start MusicBee

Further testing shows: that I can play songs with different sample rates which do not differ too much, i.e.:
1. Close MusicBee
2. and then set ASIO driver to
- 44.1 kHz, freshly start MusicBee: plays music well with 44.1 and 48 kHz, distortion when trying to play a song @88.2/96/192 kHz
- 88.2 kHz, freshly start MusicBee: plays music well with 88.2 and 96 kHz, distortion when trying to play a song @44.1/48/192 kHz
- 192  kHz, freshly start MusicBee: plays music well with 192 kHz, distortion when trying to play a song @44.1/48/88.2/96 kHz

I see here certain similarities / a pattern: inside of the three different sample rate blocks "44.1/48", "88.2/96" and "192" MusicBee can successfully change the sample rate. But if fails when the sample rate changes "too much" between i.e. "44.1/48 and 88.2/96" or between "88.2/96 and 44.1/48".

This rings a bell .. maybe the problem has to do with this:
44.1/48 kHz content uses the same ASIO buffer size, which I have set to usually 128 samples (btw .. can be from 32 to 2048 samples).
88.2/96 kHz doubles the data rate uses a higher bandwidth, thus the ASIO driver automatically changes to 256 samples buffer.
176.4/192 kHz again doubles the data rate, thus the ASIO driver automatically changes to 512 samples buffer.

Its definitively not related to the "ASIO buffer size", in the special sense "you need to use a higher ASIO buffer size, as your HW/driver is unable to work reliable with a lower one". I have the same issues when using higher ones up to 2048.
Also I can exclude "USB transport errors", as the RME ASIO driver is very advanced and has an USB dignosis function which I had running in parallel. So I can exclude cable / USB transport errors and also improper use of maybe too low ASIO buffers.

I cross-checked with another application Foobar2000, there such problems do not occurr. With foobar2000 I can play audio content completely independend, which sample rate the content has. By this I could exclude a device, cable or driver problem and am convinced that this is indeed an application issue.

In a good case of luck its only a very small problem which hopefully could be fixed easily with not too many efforts, perhaps:
- different initialization when a new title starts or
- different parameters to ASIO library calls that you use

BTW thanks: last time you solved another issue in the area of ASIO driver, to fix the display/selection of output channels, when a device has plenty of channels. This was excellent, as my current devices have plenty out outputs ;)

Of could I can help with testing new code.
Once it works I am also happily willed to do a money contributing to your project via paypal.

My hardware:

Audio Interfaces (tested with both):
- RME ADI-2 Pro,
Both devices use the same (last) RME ASIO driver:
Usually I use the UFX+ for playback on near field monitors.
The ADI-2 Pro is then connected via AES as pure headphone amp.
But I tried the ADI-2 Pro also isolated, soleyly connected to my PC via USB.
All the same, foobar works, issues with MusicBee.

- Windows 7 SP1, Ultimate
- CPU: Intel Xeon E5-1650v3, socket 2011-3, Supermicro X10SRi-F (server mainboard)
- USB3 card: Sonnet Allegro Pro (4x FL1100 USB3 controller), for each recording device a dedicated and by RME supported USB controller
- Windows High Performance Energy Profile

Ups, you're completely right ! Many thanks :-)

This I forgot to configure after migrating from 2.x.

Doubleclick to an autoplaylist, i.e.: Format: FLAC && 5 Star rated.

Select all files.

Rightclick -> send to -> Format Konverter

It shows you a few files which shall be mp3 and cannot be converted to mp3.

But if you nail this down and i.e. only select 3 FLAC files, then the same happens.

If you want to convert these FLAC files to FLAC, then the files are selectable to convert (which makes ofc no sense).

FLAC to mp3 conversion entirely doesnt work.

Thanks upfront and hope for a fix.

Looks cool. I am starting to test picard now ...

Could you pls copy paste the complete weblink for the Bruce Lyrics, would be kind, the rest of the configuration string is truncated.

There is one problem, I found now how to enable this in the Titleinformation (enabling the weblinks in the Titelinfo display on the lower right was missing).

But it actually does not work, when I click to i.e. "MB Track", then this URL is being opened<TrackID>
<TrackID> is not being expanded.

Another thing which might disturb me when using it is, that it opens a separate webbrowser, which then hides the MusicBee window. Thats not so cool.

Read my sig for 3.1

Many thanks

1- Randomization is fixed in 3.0 and 3.1

2- ASIO config bug is still persistent in last version 3.1.6230
    I have a workaround for this, so its not so critical for me at the moment but would be nice if this could be fixed.
    See also this thread for this particular thing:

3- Also with latest version 3.1.6230 I get no clue how to use this plugin, which brings back MB 2.5 functionality.
    I can not get is visible when playing a title
    See also this thread for this particular thing:

Well I start to like the 3.1 version ..
Before entirely switching #3 is a major issue for me.
Maybe some kind soul can give me a helping hand.


That menu bar is rather nice.
Did you built it yourself ? Or is it part of an existing skin/layout ?
I'm still looking for a way to have quick access to wikipedia/song info/photos/details when needed, but have not found a good way to add them in MB in a way I liked.

Yes I built it myself.

It was a long way for me to get it into exactly this state, as you have to go through many submenues in the differnt settings dialogs until you find, that something like this is possible.

This was a screenshot of MB 2.5. Later versions do not include this automatically.
It shall be able to get this functionality back by using a plugin of the same author.

But I do not get it to work, so I am still stuck on 2.5. See this thread:

BTW .. I got the nice tip to install MB 3.x portable version in parallel, to give MB 3.x a try without messing up with my current 2.5.x installation. Maybe this is also something for you shall you have the older version installed, too.

Questions / Plugin " Similar Artists/Tracks" does not show up
« on: January 22, 2017, 10:58:05 AM »

I have problems to activate the plugin " Similar Artists/Tracks"
in MusicBee v 3.0.6132 portable version.

I copied the .dll of the plugin to MBs plugin folder and veryfied in the settings that it is enabled.

But where does it show up / how to enabled this ?

I need some instructions please.

This view I want to have like in MusicBee 2.5.*, that updates automatically with the actual played title.

Here the screenshot from the plugin page how it shall look like:

Or could this be a particular problem of Musicbee version 2.5 ?
I suggest trying the latest 3.0 or 3.1 since 2.5 is rather old at this point.

With 3.0 the problem is solved, thanks. 3.1 Beta is not yet available for the public it seems.

There are some obstacles for me to upgrade to 3.x, this is the reason why I would like to stay on 2.5 for the time being.

Would it be possible to request 2 things to become backported to 2.5 ?

- randomness fix
- hopefully upcoming fix of ASIO configuration, see bug report:

Perhaps you should download the portable version of 3.0. That way you can play with the various options and layouts without changing anything in 2.5. Note that v3 creates it's own settings file (MusicBee3Settings.ini) and doesn't touch the 2.5 settings file (MusicBeeSettings.ini.)

Thats is a very good idea and it works nicely.

Now I need still a recommendation for a plugin, how I can achieve the functionality, to see the TABs inside of MusicBee like before, I do not want to open wikipedia information by rightclick for every title.

I was very satisfied that things like this happened automatically inside of MusicBee during the playback.

I play guitar to some titles and have no hand free for this.

EDIT: it looks like it is this plugin:


my recording interface, RME UFX+, has 94 input and output channels.

In the ASIO configuration dialog the list of device channel is scrollable, so far so good.

The bug is, that the list of speakers is not scrollable and does not scroll up/down together in sync with the list of device channels. By this you can't assign i.e. the left/right channel to all device channels.

This bug was already in 2.5.* and has not yet been fixed in the 3.0 train.

The situation becomes worse if you use a 2nd device like the new USB DAC RME ADI-2 Pro (Headphone Amp).
The ADI-2 Pro uses the same RME ASIO driver like the UFX+.
The problem is, that the device channels of the 2nd device are listed at the end of the list.
So you have no chance to assign left/right channel to the ADI-2 Pro directly.

Would be nice if you could fix this ASIO configuration dialog window in 3.0 and the upcoming 3.1.

Many thanks.


I read somewhere that the design in MusicBee 3.0 changed so that some display things are not included anymore
and needs external plugins.

What I liked in v2.5 was the ability to easily click a few tabs to get various information about the currently played song / performer
- Song "Details" including Lyrics
- infos
- Fotos
- Wikipedia (DE + EN)
- Youtube
- Songfacts

Could you kindly tell me, what is additionally required in terms of plugins or whatever to be able to get these capabilities back in v3 ?
Here a screenshot how I organized my screen.

Many thanks for some tips.


my last upgrade attempt from MusicBee 2.5 to version 3 is long ago.

I think I remember that I lost i.e. my autoplay lists and some handcrafted play lists.

My Questions:

- Whats best practice for such an MusicBee release upgrade ?

- What can I do, not too loose anything in terms of playlists ?

Many thanks for your kind support upfront.

Questions / 2.5.5804: Random playing in autoplaylist is not really random
« on: January 21, 2017, 10:29:24 AM »

does somebody else have the same problem, that MusicBee plays more or less the same songs ?

I have i.e. 2 Auto Playlist
- play flac files randomly that are rated 4-5 Star with ~1000 titles
- play flac files randomly that are rated 5 Star with ~2200 titles

Surprisingly I am hearing only the same songs of the same 3-5 Bands with very little variations.

I can not see/find any mistake on my side in terms of setup of the AutoPlay Lists.
So I would like to know, whether you also have similar problems.

When I listen i.e. to the same set of files in my car, then I really get random files which is very nice.

So .. why does it work so bad for me in MusicBee ?

Does MusicBee perhaps use a "random" library function of Microsoft, that is maybe only in Windows 7 not so well working ?
Or could this be a particular problem of Musicbee version 2.5 ?

What are your experiences with playing random in MusicBee ?

Best would be to add the information MusicBee Version and OS version, to maybe recognize a certain "pattern" better, whether this is more OS or MusicBee related.

Many thanks for your kind support upfront.

MusicBee Wishlist / Re: 2 wishes
« on: April 06, 2015, 07:51:25 PM »
I found the solution. See also the last posts in this thread, where somebody supported me.

There are several issues which hindered the program to run properly inside of MusicBee:

1. besides the DLL files also is required. Its looks like C Code, so I thought this is only for docu purposes, but its actually used during runtime

2. I copied the 4 DLL files to 4 different places in the hope to get it work...
C:\Program Files (x86)\MusicBee\Codec
C:\Program Files (x86)\MusicBee
I additionally copied now the to these 4 location. Its still an open topic for me to identify, whether codec directory is sufficient.

3. it turned out when using the converter on the commandline, then also higher optimizations (-9 - -11) are possible. But then additionally the -lax option needds to be set. Higher optimization/compression than -8 turned out not to be possible when being called from within MusicBee.

4. when being called from within Musicbee then you need another commandline option, which was not required when being used in the DOS box. On the DOS box the converter can even read properly from stdin, without the need of the additional option --ignore-chunk-sizes.

5. inside of Musicbee you need to use --ignore-chunk-sizes as parameter, and higher levels than -8 are not possible, then conversion doesnt run.

The settings inside of MusicBee to make it work were for me (-> Settings -> File Converter):
- maximum Encoder Threads: 6 up to 9 (I would say this is CPU and Disk i/o dependend)
- use the converter from within MusicBees codec subdirectory where the converter, the DLLs and the (!!) need to reside (remember my open topic, I need to validate, that it can be this directory exclusively, at the moment I have this spread around 4 locations):
   C:\Program Files (x86)\MusicBee\Codec\CUETools.FLACCL.cmd.exe
- use the following arguments: -q -8 --ignore-chunk-sizes --opencl-type GPU --opencl-platform "NVIDIA CUDA" - -o [outputfile]

6. If you have an AMD graphic card, then you might need another cmd line option: --opencl-platform "AMD Accelerated Parallel Processing"

First findings in regards to performance.

With my GTX 980 I am getting an avg. GPU utilization up to 14% with few peaks up to 20%, depends on the number of encoder threads.
When converting the same APE files to FLAC with Encoders from 1..9 for my machine ~7 encoders utilize CPU and GPU best.
Using 8-9 encoders results still in some more files, but not that dramatic.
With 1 encoders I get 18, with 2 encoders I get 32 files converted within a minute.
The difference between using 6-9 encoders is only within 4-10 files more per additional encoder.

I made a 1st real life performance test by looking how many of my APE files I get converted within 4 minutes.
With FLACCL I get 314 files of 7,36 GB size in total. CPU utilization between 51-73, GPU between 2-14%.
With normal FLAC I get only 185 files of 4,47 GB size in total. CPU utilization between 37-68%, GPU of course 0%.

To convert 314 files, which FLACCL did in 4 minutes, the normal FLAC programm needs 6m35s, which is 65% more.
The size difference between the 314 files is very low 7,36 GB (FLACCL) vs 7,37 GB (flac).

So the only motivation to use this program is for speed if you have a big conversion job or if you simply like the idea being able to offload work to the GPU.

Thanks for your response and I hope you get it running as well, as it appears to me that you also spend some time on this.

MusicBee Wishlist / Re: 2 wishes
« on: April 06, 2015, 02:48:03 PM »
I tried it already with single quotes, no change. On the commandline both is possible, either single or double quotes.

The tool defaults to use the GPU ( --opencl-type GPU). If I do not specify which platform to use (amd or nvidia) then this happens:

Win7>CUETools.FLACCL.cmd.exe -o audio.flac audio.wav
Error: no OpenCL devices found that matched filter criteria.

In the DOS box I validated already, that reading input from a pipeline works using these commands. Doesn't work inside MusicBee though ..
type audio.wav | CUETools.FLACCL.cmd.exe -q -8 --opencl-platform "NVIDIA CUDA" -o audio.flac -
type audio.wav | CUETools.FLACCL.cmd.exe -q -8  --opencl-type GPU --opencl-platform "NVIDIA CUDA" -o audio.flac -

An additional idea, I try to use the CPU for conversion, then I do not require to specify the platform type,
which has the space in it ("NVIDIA CUDA") to exclude any problem in regards to potential quoting issues inside MusicBee.
But this also does not change anything.  I tested it with these argument
-q -8 --opencl-type CPU - -o [outputfile]

Location of the minus sign "-" can be before or after the -o option, this I tested already on the command line.
So its also not the order of the arguments.

I have a certain feeling that it has to do with the DLL files.
Do you think MusicBee finds them in this directory ? C:\Program Files (x86)\MusicBee\Codec ??

EDIT: I copied now the 4 DLLs (CUETools.Codecs.dll, CUETools.Codecs.FLACCL.dll, CUETools.Codecs.FLAKE.dll, OpenCLNet.dll) even to the Windows System folder. As I was not sure, whether those files are 32 or 64bit I copied them to both directories (System32 and SysWOW64) and rebooted. No change still doesn't work.

BTW registration of those DLLs - should this be required - in both directories using the proper tool failed as well.
Error message was: "Das Modul C:\Windows\System32\CUETools.Codecs.dll wurde geladen, aber der DllRegister-Eingangspunkt wurde nicht gefunden. Stellen Sie sicher, dass C:\Windows\System32\CUETools.Codecs.dll eine g├╝ltige .DLL oder .OCX Datei ist, und wiederholen Sie den Vorgang."

REM If the DLL is 32 bit: Copy the DLL to C:\Windows\SysWoW64\
%windir%\SysWoW64\regsvr32.exe %windir%\SysWoW64\CUETools.Codecs.dll
%windir%\SysWoW64\regsvr32.exe %windir%\SysWoW64\CUETools.Codecs.FLACCL.dll
%windir%\SysWoW64\regsvr32.exe %windir%\SysWoW64\CUETools.Codecs.FLAKE.dll
%windir%\SysWoW64\regsvr32.exe %windir%\SysWoW64\OpenCLNet.dll
REM if the DLL is 64 bit: Copy the DLL to C:\Windows\System32\
%windir%\System32\regsvr32.exe %windir%\System32\CUETools.Codecs.dll
%windir%\System32\regsvr32.exe %windir%\System32\CUETools.Codecs.FLACCL.dll
%windir%\System32\regsvr32.exe %windir%\System32\CUETools.Codecs.FLAKE.dll
%windir%\System32\regsvr32.exe %windir%\System32\OpenCLNet.dll

EDIT2: I found out via google that the regsvr32 error message appears, because these DLLs seem to be plain "C DLLs" no "OLE DLLs". So normal "C DLLs" do not need to be registered, they will be found automatically in \windows\system32 ....

Pages: 1 2 3 45