MusicBee 3.2 is prone to crashes when enabling new plugins. Expect for it to crash up to 3 times before it becomes permanently stable.Can you expand on that and provide me with more info? I am not aware of a general issue with plugins crashing. It might be better to reply on the developers section
. Extract the files located in the "Plugins" folder to your MusicBee Plugins directory:so your plugin wont work with portable mb at all? you could store any settings under path returned by MB_GetPersistentStoragePath() API function.
C:\Users\YOUR_USERNAME\AppData\Roaming\MusicBee\Plugins
Note: If you aren't using this directory, you'll have to change the "folderPath"
variable in the source files to the appropriate destination, and then rebuild it.
Quote. Extract the files located in the "Plugins" folder to your MusicBee Plugins directory:so your plugin wont work with portable mb at all? you could store any settings under path returned by MB_GetPersistentStoragePath() API function.
C:\Users\YOUR_USERNAME\AppData\Roaming\MusicBee\Plugins
Note: If you aren't using this directory, you'll have to change the "folderPath"
variable in the source files to the appropriate destination, and then rebuild it.
hmm... not sure whats the matter, but spectrogram panel displays nothing for me (portable mb if its important). i suspect that you use predefined path for Tooltips folder (i.e. C:\Program Files (x86)\MusicBee\).
Hi.
I think I found a bug - if a track has the same Artist and Title, the plugin shows the same output for both files.
My test was "Chic - Good Times", (which is a common dupe in my library as I have a *lot* of disco.)
Over several different versions, lengths and bitrates, the files tagged "Chic - Good Times" all gave an identical image (which I think is the one from the first track with those tags that is played), but the one marked "Chic - Good Times (Original 12" Mix)" had a unique image.
My guess is that these two tags are used to tag the image in the cache for the next time its played?
Hi.
I think I found a bug - if a track has the same Artist and Title, the plugin shows the same output for both files.
My test was "Chic - Good Times", (which is a common dupe in my library as I have a *lot* of disco.)
Over several different versions, lengths and bitrates, the files tagged "Chic - Good Times" all gave an identical image (which I think is the one from the first track with those tags that is played), but the one marked "Chic - Good Times (Original 12" Mix)" had a unique image.
My guess is that these two tags are used to tag the image in the cache for the next time its played?
Useful, but it will still not replace spek that I'm using to check if song is fake mp3 or anything like that because it doesn't show numbers on any of the sides of the spectrum, so i can't guess where it goes above 16 kHz and 20khz.
IMPORTANT NOTE: MusicBee 3.2 is prone to crashes when enabling new plugins. Expect for itI suggest that you change this text since MB is -not- prone to crashes. It may be the -plugin- that causes MB to crash. Especially since you told Steven (in the developers sub-forum) that the issue was fixed.
to crash up to 3 times before it becomes permanently stable. If you continue
to have issues, try reinstalling the plugin, or reconfiguring the panels.
IMPORTANT NOTE: MusicBee 3.2 is prone to crashes when enabling new plugins. Expect for itI suggest that you change this text since MB is -not- prone to crashes. It may be the -plugin- that causes MB to crash. Especially since you told Steven (in the developers sub-forum) that the issue was fixed.
to crash up to 3 times before it becomes permanently stable. If you continue
to have issues, try reinstalling the plugin, or reconfiguring the panels.
@zkhcohen, when you revise this plug-in next, might you also be able to enable the hide/display header menu option of the pane within the layout so that the header title word "Spectrogram" can be omitted tightening up the view of the pane with the pane above it?
Thank you for your plug-in contribution!
Frequency scales would be nice. And yeah, color. Basically I was hoping for something like this: https://academo.org/demos/spectrum-analyzer/
Thank you for your work.
@zkhcohen, could you somehow colorize spectrogram? grayscale coloring is not very funny :)
EDIT: I noticed that the plugin saves the generated PNGs for every song played, to speed up display time. That's nice, but could you make it optional?
I have >40 000 files. I don't want to save a PNG for each one. On the fly generation will be enough in most cases.
It's hard to say since the linked document only specifies color schemes, without showing what they look like. But I think you can never go wrong with 'plasma'.
EDIT: I noticed that the plugin saves the generated PNGs for every song played, to speed up display time. That's nice, but could you make it optional?
I have >40 000 files. I don't want to save a PNG for each one. On the fly generation will be enough in most cases.
EDIT2: I'm interested in the frequency scales, because I don't want to use the plugin as eye candy. I want to check actual audio quality as described here: http://www.walterdevos.be/how-to-check-quality-of-mp3-file
So if the frequency scales don't scale with the display, maybe there is a way to lock the display size?
Man, this is GREAT. Almost too good to be true, haha.. Wonderful options, can't see it's missing a thing, would love to see what you've got in the drop-down boxes :)
Would it be possible to include an option to point to an already existing installation of ffmpeg.exe instead of needing to use the one in the install package?
The link in your latest post is producing the following message from MediaFire:
"The key you provided for file access was invalid. This is usually caused because the file is no longer stored on MediaFire. This occurs when the file is removed by the originating user or MediaFire."
OK, here is what is happening-- this link http://www.mediafire.com/file/5q1nciar25f6q2s/MusicBee_Spectrogram_1.5.zip/file (http://www.mediafire.com/file/5q1nciar25f6q2s/MusicBee_Spectrogram_1.5.zip/file) is still producing the page indicating the file is not available, but with a big "Download" button below the message that is linked to some non-mediafire url that takes you to a page with it's own download button that wants to install an extension--no way man. The link on your FIRST post, which is http://www.mediafire.com/file/2633b0bywddf2pm/MusicBee_Spectrogram_1.5.zip/file (http://www.mediafire.com/file/2633b0bywddf2pm/MusicBee_Spectrogram_1.5.zip/file) (different than the other one), does lead to a normal Mediafire download page and result in a download. So, is the plugin linked on that first post also the one with the newest changes? If so you should probably delete the "wonky" link in case somebody ends up with an uninvited guest.
1. Extracted the 2-file contents of the Plugins folder (ConfigurationManagerLibrary.dll and mb_Spectrogram-Display.dll) into the MB Plugins directory, and started MusicBee.
2. Without entering prefs/plugins, immediately receive message to place 3 files--ConfigurationManagerLibrary.dll, ffmpeg.exe and config.xml--into the MusicBee directory. Note that the readme says to ALSO put ConfigurationMenu.exe there, so did that as well. Then, went to prefs/plugins and enabled plugin/save. Restarted MusicBee.
3. Went to configure layout and dragged spectrogram entry to bottom of Main panel, where it appears just above the bottom panel player controls.
4. Began to play a song, no spectrogram is displayed. Opened the settings panel by clicking in upper left corner, opens fine, saved default settings and option to remove png's on restart. Still no display; however, clicking inside the empty spectrogram window does seek through the song.
5. Restarted MB, still no display. I do get a "Spectrogram images deleted" message upon restart, confirming the setting I made in its options. Just don't get any visible waveform. Tried disabling/re-enabling plugin, also removing my Classic Spectrum graphic vis from the right sidebar, still no-go. :(
If you continue to have issues with no spectrogram appearing, check the Dependencies folder and ensure that images are being created inside of the "Spectrogram_Images" folder it generates. Let me know if they don't appear there.
If you continue to have issues with no spectrogram appearing, check the Dependencies folder and ensure that images are being created inside of the "Spectrogram_Images" folder it generates. Let me know if they don't appear there.
Should I have put the actual Dependencies FOLDER into MB, instead of just the files it contains? Neither the readme.txt or the pop-up message from the plugin when first starting MB indicated to do that, just to extract the files themselves into the main MusicBee folder. If so, therein may lie the rub. I'm rather beat right now so will try again tomorrow, this time with your new release with the fixes. You mentioned also implementing my user-supplied path to ffmpeg idea, a big thank-you for that! Will let you know how it goes. Hopefully we'll get some other testers posting too by then.
@zkhcohen, when you revise this plug-in next, might you also be able to enable the hide/display header menu option of the pane within the layout so that the header title word "Spectrogram" can be omitted tightening up the view of the pane with the pane above it?
Thank you for your plug-in contribution!
Same issue--no image is being generated. Here is the setup:
1. "Dependencies" folder with all contents (config.xml, ConfigurationMenu.exe, ffmpeg.exe) placed in c:\MusicBee\Appdata as the pop-up instructed (changed I noticed from last ver. which said to place in c:\MusicBee--assume change was deliberate); the single file "mb_Spectrogram-Display.dll" from the "Plugins" directory in zip package (which formerly contained two files) placed in the MB Plugins folder.
2. Plugin enabled, settings set to default. Window inserted via layout button.
3. Play file. No image is generated, although seek works. No image exists in the "Spectogram_Images" subfolder created within c:\musicbee\appdata\dependencies. Tried inserting a path to an ffmpeg.exe elsewhere than the Dependencies folder, still no-go.
Is there something in your build like a specific Visual-C dependency?? OS here is Windows 7 SP1 32-bit, with VC redists 2008/2010/2013/2015 installed. For some reason no PNG is being generated.
Am also using the Classical Spectrum graphic vis, but disabling that yesterday made no difference so didn't do that today.
Latest NET, latest MB 3.3x update. I think the "bingo" is the Visual C++ 2017, which I as mentioned I do NOT have; will install that redist later and let you know if it does the trick, my money is on "yes."
Well I give up on this. Installed the 2017 re-dist and started over with a fresh copy of MB from my back-ups, no change, no PNG will draw. Could be something as basic as "not compatible with Windows 7", or even my video drivers. At any rate, maybe somebody else who is using Windows 7 can chime in if it's working for them. Thanks anyway zkhcohen for the effort you have put into this, much appreciated. I plan on updating to Windows 10 (and a new PC) anyway this year, so I'll revisit it then.
Well, blow me down, as Popeye used to say. FOUND IT! Found that you supply a 64-bit version of ffmpeg.exe with the plugin, which of course is not compatible with a 32-bit OS like poor me has. Yours was the only copy I used in my tests. Swapped it with my 32-bit version of ffmpeg 4.1.1, and there is the display!
Also tested the external path feature, I used "c:\ffmpeg\ffmpeg.exe" despite the note saying "use /ffmpeg in the path" (forward slash) and works just fine.
Default settings of Saturation=0 will show black & white for any color setting unless set to something other than "0"--which makes sense but maybe worth a note in the readme.
As expected, will display no image if a radio stream is played; however, this also "hangs" ffmpeg.exe which then must be killed with Task Manager before the plugin can function again with an audio file, even upon MB exit. Unfortunately, because I go back and forth between stations and files regularly, this sort of kills the usability for me. Is there a way to tell it to ignore streams (not load ffmpeg)?
Man I love it when a plan comes together though. The frequency legend is buff, BTW! 8)
It's interesting that radio streams cause it to hang for you. To be honest, I never implemented any sort of check in there because streams don't cause my ffmpeg session to hang (or even execute in the first place). Now that I know it does, I'll take a look into it.
It's interesting that radio streams cause it to hang for you. To be honest, I never implemented any sort of check in there because streams don't cause my ffmpeg session to hang (or even execute in the first place). Now that I know it does, I'll take a look into it.
Here once you switch to a stream, ffmpeg executes and hangs in memory; while no image is shown in the window, a PNG with the initial track name is indeed generated inside Spectrogram_Images. Maybe there is some way to have it recognize a url and not execute in that case. Hey man forget it for today and enjoy that flight :)
Version 5.4: streams no longer cause ffmpeg to hang. Current behavior:
1. If you start with playing a stream, no image is displayed or saved, continuing that way when switching streams (expected behavior).
2. If you then play a song, image is displayed/saved (expected) with that song title.
3. Once you switch back to a stream, no image is displayed, but an image identical to the song previously played is generated "behind the scenes" and saved with the stream's current title. Continuing to a different stream produces no additional saved images, until you play a song, and switch back to a stream, in which case the behavior repeats.
To sum up, once the spectrogram is "activated" by playing a song, when you switch to streams a non-displayed image will be generated once for the first stream that is a copy of the previously-played song's image, and named/saved with the stream title.
Of course, all images get deleted on MB restart when that option is selected. Question: is it possible to delete them instead on MusicBee's EXIT? Also, can the "images have been deleted" message be suppressed?
So, the hanging ffmpeg problem is solved (thanks!). The anomaly described above can be lived with IMO, but does generate unneeded additional images. Thanks again for your work.
Done; here's the message generated after switching to a radio stream immediately after playing a song. It first cites the previous song file's title, then shows an image being saved with the name of the radio stream instead:
(https://i.imgur.com/V0hUCNg.png)
No, there are no copies of the older plugin files around, I start every test of your new releases with a fresh MusicBee Portable backed up before I ever installed it.
SOMETHING funny is going on :-\
When I try to get the new debug file, MediaFire returns with "Download not available yet because the upload for this file is still in progress. Approximate completion time below (no time appears-svk)
Download ready soon…"
When I try to get the new debug file, MediaFire returns with "Download not available yet because the upload for this file is still in progress. Approximate completion time below (no time appears-svk)
Download ready soon…"
Another suggestion: ability to not display the "Images Deleted" popup on MusicBee opening, just delete them silently when the delete on startup option is selected.
The new color options make for some nice graphics!! https://getmusicbee.com/forum/index.php?topic=2258.msg155817#msg155817 (https://getmusicbee.com/forum/index.php?topic=2258.msg155817#msg155817)
Thanks for this plugin, I hope you are able to diagnose the problem with errant image generation when switching from file to stream.
From your *edit* message it seems like you've finally got the info you need to solve this if that's possible on your end, great!! Yes could be the API. FYI, yes I'm always running the latest Mb 3.3x patch version, and no, I don't start with anything queued up. Good luck with this!
EDIT 2: Fixed it for good by using: mbApiInterface.NowPlaying_GetFileProperty(FilePropertyType.Size) != "N/A". Will release after I do some code cleanup.
EDIT 2: Fixed it for good by using: mbApiInterface.NowPlaying_GetFileProperty(FilePropertyType.Size) != "N/A". Will release after I do some code cleanup.
Will hold off on any more testing then until I get a "go" from you here, sounds promising!
Well, I guess I better report this, dang it... Just noticed that the MusicBee error log is logging the following error every time MB is opened with the plugin active, though NOT generating any pop-up error window about it (which is why I never noticed until now--spotted an ErrorLog.dat file in my Appdata during a backup):
3/3/2019 1:38:06 AM - 6.1.7601.65536 - 3.3.6998.33948 P - System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object.
at MusicBeePlugin.Plugin.CurrentTitle()
at MusicBeePlugin.Plugin.ImgCheck()
at MusicBeePlugin.Plugin.ReceiveNotification(String sourceFileUrl, NotificationType type)
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at #=zGWVOIIfXVyqY4V9P1w==.#=z4MWx6ZgbQymW()
MB and the plugin continue functioning normally after the "stealth" error message.
Version 5.8: seems like the "money build." No errors in MB error log are written. Option to disable debug log works. Different behavior on install: when first copying plugin dll to the MB Plugins folder and starting MB, a message about where to place Dependencies folder no longer appears (no big deal if you indicate where it should go in the readme). Placed it myself in Appdata like usual, and followed normally.
Have not seen lack of image generation if minimized during a song change during an initial test, but will let you know if I ever do.
Is this branch starting from scratch as far as testing? Sort of getting "plugin fatigue" around here, so would appreciate a recommendation as to if development on the original plugin is being stopped, and continued at this new 7001+ link? What exactly is not compatible between the branches? As I am on MB 3.3.7001 now and update regularly, should I forget about ever checking the first project again and stick with this "new" one from now on? To avoid confusing first-time users, I would just remove all links to the first project and add a line like "this plugin requires MB 3.3.7001 and above" to the first post. People should be using the latest MB anyway if they expect best results.
Thanks for the reply. Can you explain what the differences are exactly between the 7001+ and the old 5.8 version, and why the 7001+ is not recommended for lower versions of MusicBee? Also, I assume all the changes/fixes you have already spent so much time on are included by default in the 7001+ version?
I appreciate your attention/patience. Just trying to get the full picture before leaving 5.8 for good for 7001+.
"Dear Readers", who may have been following the plugin's testing, I have been using the latest "7001+" version and can confirm it functions as-advertised and problem-free; now in use with MusicBee 3.3.7003. Thanks zkhcohen for all your work on this.
P.S. zkhcohen, I would encourage you to take a look at the source files of the "Winamp Classic Spectrum Analyzer" (https://getmusicbee.com/forum/index.php?topic=23345.msg154061#msg154061 (https://getmusicbee.com/forum/index.php?topic=23345.msg154061#msg154061)); what we need is the ability to invoke and use the "options" GUI without crashing MB (see thread). Maybe you can do an integerated options job on it like you've done for Spectrogram! Would be much appreciated.
In order to change the color in the preferences GUI, you have to set the "Saturation" value to something other than "0". I have mine set to 1, and Gain to 2.
First, for the life of me I can't seem to figure out how to change the size of the spectrogram window. I'm not sure if its because I'm using Album Cover view (although the other views didn't work either), but as it sits right now, the window is eating up too much vertical real estate for my liking.
Second, my legend only shows up to ~13000Hz (regardless of file format). I see in other pics it does go much higher
First, for the life of me I can't seem to figure out how to change the size of the spectrogram window. I'm not sure if its because I'm using Album Cover view (although the other views didn't work either), but as it sits right now, the window is eating up too much vertical real estate for my liking.
Second, my legend only shows up to ~13000Hz (regardless of file format). I see in other pics it does go much higher
Have you tried the bottom Main Panel location? You should be able to drag the spectrogram's title bar to whatever height you want.
As far as the spectrogram displayed frequency level, that depends on the file's encoding. If a lowpass filter was set to say 15kHz, you would see a "chopped off" area higher than that. I've found that's a lot more common than I thought!
On the color theme, mine shows up all the way down to Green, but not lower. zkhcohen may be able to help. Like you said, no big deal to me either.
My scale is numbered up to "17226.56" kHz, and continues upward to around 19000 kHz. Maybe in your case the problem is related to the inablity to move the header bar of the spectrogram window.
From the readme.txt: "Creating a file called "noheader.txt" in the Dependencies folder will disable the plugin's header/title bar the next time that you restart MusicBee. This isn't working reliably at the moment and you can't seem to resize it with the header disabled." Have to ask, did you create that file, or? IS there a header bar visible saying "Spectrogram" in its upper left corner?
<edit> playing some more and I find the legend doesn't scale well - I think I remember this being mentioned earlier. If I make the spectrogram window ~50% of my screen height than I can get ~18000Hz on the legend. If I make the spectrogram window bigger than that (say 75% of the height) then the legend shrinks down to ~11000Hz. Not sure if I'll be able to find a happy medium between size and the usability of the legend with my layout - maybe just keep this plugin for the eye candy (minus legend) and use Spek for actual analysis
@zkhcohen: Anomaly/bug noticed: if two music files of the same song with different file format and extensions but exactly the same file name are played, the spectrogram does not re-generate but remains identical to the first one played, even though restarting MB and starting with the "second" file will produce its own distinctive spectrogram from the first, as one would expect. There should be the ability for the plugin to recognize format extensions not just file names for a re-paint, or just re-calculate on the fly and not re-use an existing PNG.
@zkhcohen: Anomaly/bug noticed: if two music files of the same song with different file format and extensions but exactly the same file name are played, the spectrogram does not re-generate but remains identical to the first one played, even though restarting MB and starting with the "second" file will produce its own distinctive spectrogram from the first, as one would expect. There should be the ability for the plugin to recognize format extensions not just file names for a re-paint, or just re-calculate on the fly and not re-use an existing PNG.
My scale is numbered up to "17226.56" kHz, and continues upward to around 19000 kHz. Maybe in your case the problem is related to the inablity to move the header bar of the spectrogram window.
From the readme.txt: "Creating a file called "noheader.txt" in the Dependencies folder will disable the plugin's header/title bar the next time that you restart MusicBee. This isn't working reliably at the moment and you can't seem to resize it with the header disabled." Have to ask, did you create that file, or? IS there a header bar visible saying "Spectrogram" in its upper left corner?
OK, I'm a total dumb-ass. Starting digging around my layout settings and found I had locked the layout (disable panel resizing). Not sure why or when I did that but that was the problem with resizing.
I still have the scale problem though. On my system, playing a flac file, the scale will max at 13781.25Hz. The same file in Spek will show a scale up to 22000Hz. I tried one of my 24/96 flac files and that will push the scale up to 30000Hz, so it is somewhat working properly.
I've tried different gain settings, changing the ffmepg.exe to the 32bit version
<edit> playing some more and I find the legend doesn't scale well - I think I remember this being mentioned earlier. If I make the spectrogram window ~50% of my screen height than I can get ~18000Hz on the legend. If I make the spectrogram window bigger than that (say 75% of the height) then the legend shrinks down to ~11000Hz. Not sure if I'll be able to find a happy medium between size and the usability of the legend with my layout - maybe just keep this plugin for the eye candy (minus legend) and use Spek for actual analysis
<edit> playing some more and I find the legend doesn't scale well - I think I remember this being mentioned earlier. If I make the spectrogram window ~50% of my screen height than I can get ~18000Hz on the legend. If I make the spectrogram window bigger than that (say 75% of the height) then the legend shrinks down to ~11000Hz. Not sure if I'll be able to find a happy medium between size and the usability of the legend with my layout - maybe just keep this plugin for the eye candy (minus legend) and use Spek for actual analysis
Yeah that's a problem if the legend isn't changing to match the spectrogram sizing; when I reduce the height here it does "squish" everything down but that includes the legend and the numbering is extant. I tried a 24-bit 96kHz FLAC and the scale legend showed 37500kHz and continued up to about 44000k. You said you had the latest version, which did incorporate changes in handling that, so I don't know what could be causing that for you. zkhcohen will be checking in soon I'm sure. BTW, tried Spek per your mention and it's pretty cool, added it to my external tools in MB. I did miss the lack of a "gain" setting like zkhcohen's plugin has, which allows more subtle info to stand out better.
Thanks zkhcohen for your replies!
1. Glad to know that adding the ability to distinguish identical name/different format files will be an easy one;
2. About the "squish effect", I find that mine still holds up well "pretty squished" with the scale still showing up to 45kHz on a 24-bit 96kHz FLAC that does indeed top out around 45kHz., in other words I haven't seen the problem Mr. Trev reported, although your screenshot sequence does show that it can indeed happen. Personally I "wince" at the idea of trying to hack ffmpeg to deal with that, but it's up to you.
3. Does my "wishlist" suggestion about a user-supplied path to a static PNG that would be displayed in case of radio streams sound possible? I mean just one image picked by the user that would be used in every case, not anything unique-per-stream.
In any case, #1 will make me a happy camper! Thanks again for your efforts.
Finally, any of the colour themes from Magma on down won't show an image - not a big deal, but I thought I'd point it out
<edit> playing some more and I find the legend doesn't scale well - I think I remember this being mentioned earlier. If I make the spectrogram window ~50% of my screen height than I can get ~18000Hz on the legend. If I make the spectrogram window bigger than that (say 75% of the height) then the legend shrinks down to ~11000Hz. Not sure if I'll be able to find a happy medium between size and the usability of the legend with my layout - maybe just keep this plugin for the eye candy (minus legend) and use Spek for actual analysis
Yeah that's a problem if the legend isn't changing to match the spectrogram sizing; when I reduce the height here it does "squish" everything down but that includes the legend and the numbering is extant. I tried a 24-bit 96kHz FLAC and the scale legend showed 37500kHz and continued up to about 44000k. You said you had the latest version, which did incorporate changes in handling that, so I don't know what could be causing that for you. zkhcohen will be checking in soon I'm sure. BTW, tried Spek per your mention and it's pretty cool, added it to my external tools in MB. I did miss the lack of a "gain" setting like zkhcohen's plugin has, which allows more subtle info to stand out better.
Yeah. Check this out:
https://imgur.com/a/ELevqC9
It compresses it up until a certain point, then starts expanding it again.
I don't think I can do anything about this without actually modifying the formula in the FFMPEG source.
If you really wanted to use this for audio-analysis of FLAC files, I think you'd want to create a separate custom layout tab in MusicBee, dedicated to a MUCH larger spectrogram image.
We'll see what I can do.
Both the bug fix for same-name-different-format, and the new optional placeholder display are working BEAUTIFULLY, thank you!!
As far as color display, I can display down to and including "Green", but the choices below that (Viridis-Plasma-Cividis-Terrain) do not display. This is with a Zerranoe 32-bit build of ffmpeg. But since we already have 11 working color choices, I don't see how anyone, even me, could possibly complain! I use Rainbow at any rate.
Just wanted to let you know that the color scheme issue only affects 32 bit (I assume). I just tested every color on the 64 bit build and they all work.
I gave it a run, everything seems to be working as intended - mostly…
It did balk when I tossed a 24/192 flac at it (didn't display any image at all). I'm not going to worry much about that, I don't have many files at that sample rate.
But otherwise, the legend is staying at the max rate regardless of window size, the themes that didn't display before do now.
Now I just need to find a layout that'll work for me… (and find somebody to write a plugin that'll do DR range analysis ;) )
Thanks for your work!
Cheers
I gave it a run, everything seems to be working as intended - mostly…
It did balk when I tossed a 24/192 flac at it (didn't display any image at all). I'm not going to worry much about that, I don't have many files at that sample rate.
But otherwise, the legend is staying at the max rate regardless of window size, the themes that didn't display before do now.
Now I just need to find a layout that'll work for me… (and find somebody to write a plugin that'll do DR range analysis ;) )
Thanks for your work!
Cheers
Interesting... can you send me the 24/192 FLAC? I'd like to see if that's my problem or FFMPEG's.
DR analysis would be interesting and I don't see why FFMPEG wouldn't be able to do it - the db scale on the right of the spectrogram legend already adjusts dynamically. I'm going to look into a way of exporting some of those values directly.
It also allows you to compress the DR:
https://ffmpeg.org/ffmpeg-filters.html#compand
Would you be interested in something like this?
http://dr.loudness-war.info/
EDIT:
Just tested it with the following 24/192 flac sample and it works:
http://www.lindberg.no/hires/test/2L-125_stereo-176k-24b_04.flac
Does it have an unusually large file-size or long length? I've had some issues with that on my laptop, but not my desktop.
EDIT 2:
Uploaded a 'hotfix' for some minor image generation issues. Better support for low and high resolutions.
Since this is the only thing I'd use it for I really can't justify paying for the MAAT offline program.
Since this is the only thing I'd use it for I really can't justify paying for the MAAT offline program.
Have you tried the freeware TT DR Offline Meter 1.4a? From the same people as the Foobar plugin I believe:
http://dr.loudness-war.info/downloads/DR-Meter-1_4a.zip (http://dr.loudness-war.info/downloads/DR-Meter-1_4a.zip)
I tried running that one in conjunction with the VST support plugin for Music Bee, but I haven't had any luck yet.
Still looking into alternatives.
I tried running that one in conjunction with the VST support plugin for Music Bee, but I haven't had any luck yet.
Still looking into alternatives.
The documentation indicates that there is both a stand-alone and VST version in the TT-DR installer--did you try the standalone version? I was thinking that might be convenient to run via MB Tools on selected libray files. I'd try it myself but DR analysis has really no interest for me, but Mr. Trev might give it a shot. I did extract the installer via 7-Zip and it shows a "DR-Offline.exe" file and its own folder structure with own graphics as well as a VST dll in a separate folder.
FOR %a IN ("*.mp3") DO (ffmpeg -i "%a" -af ebur128 -f null - 2>&1 | FINDSTR /BIC:" " | FINDSTR /C:"LU")C:\Users\zacha\Downloads\Katy Perry - One of the Boys (2008)>(ffmpeg -i "01. One Of The Boys.mp3" -af ebur128 -f null - 2>&1 | FINDSTR /BIC:" " | FINDSTR /C:"LU" )
I: -5.5 LUFS
Threshold: -15.7 LUFS
LRA: 5.0 LU
Threshold: -25.6 LUFS
LRA low: -8.9 LUFS
LRA high: -3.9 LUFS
C:\Users\zacha\Downloads\Katy Perry - One of the Boys (2008)>(ffmpeg -i "02. I Kissed A Girl.mp3" -af ebur128 -f null - 2>&1 | FINDSTR /BIC:" " | FINDSTR /C:"LU" )
I: -6.5 LUFS
Threshold: -16.5 LUFS
LRA: 3.5 LU
Threshold: -26.5 LUFS
LRA low: -8.5 LUFS
LRA high: -5.0 LUFSFOR %a IN ("*.mp3") DO (ffmpeg -i "%a" -af ebur128=peak=true -f null - > %a-output.txt 2>&1)Cool, LUFS/R128 is the new standard anyway and it's great the functionality to get the readings is already in ffmpeg. I assume the "I:" value is the "Intergrated" LUFS value? Steven changed to R128 for Opus gain tagging not too long ago. What are your thoughts as far as a GUI display ? Meters or just numerical values?
Since this is the only thing I'd use it for I really can't justify paying for the MAAT offline program.
Have you tried the freeware TT DR Offline Meter 1.4a? From the same people as the Foobar plugin I believe:
http://dr.loudness-war.info/downloads/DR-Meter-1_4a.zip (http://dr.loudness-war.info/downloads/DR-Meter-1_4a.zip)
It doesn't seem like that sort of visual analysis is what's most important, though, so numerical values / tags might be better suited.
It doesn't seem like that sort of visual analysis is what's most important, though, so numerical values / tags might be better suited.
I agree. Mr. Trev will be a lot more useful at describing what users might be looking for, I admit I don't even use ReplayGain tags. BTW, you might as well start a new topic for this project! Just don't forget about Classic Spectrum Analyzer... ;)
Would it be possible to add a right-click menu to the plugin's header/title bar to open the "Configure" menu.
It sure would be a lot easier to access from there, rather than navigating to the Plugins panel everytime.
3. A message will appear telling you where to place the plugin's "Dependencies" folder; extract the whole folder there now.
Quote3. A message will appear telling you where to place the plugin's "Dependencies" folder; extract the whole folder there now.
Stuck here, no message
3.3.7003 version and latest release, musicbee see this plugin (disabled in plugins menu)
You can now access the Spectrogram Configuration Panel by right-clicking the panel.
I have just installed the plugin yesterday. Took me a while to figure out how to get it work.
My feedback on the installation process:
1. I am on Window 10. MusicBee Ver 3.2.6902 non-portable.
2. Re: Installation Instructions #3. "A message will appear telling you where to place the plugin's "Dependencies" folder; extract the whole folder there now."
After extracting the file mb_Spectrogram-Display.dll in the Plugin folder and place it in the MusicBee/Plugins, I restarted MusicBee. However, there is no message telling me where to place the "Dependencies" folder.
I spent some time reading through the forum postings and managed to find the correct folder.
The folder should be
C:\Users\YOUR_USERNAME\AppData\Roaming\MusicBee\".
For my case, it didn't work if I put it in the sub-folder \Plugin (I don't have such a folder and I created one by following the posting quoted by boroda in Reply #2).
Note: The above folder is a hidden folder and users need to enable viewing hidden folders in the window explorer options.
3. For the configuration, the chart is by default grey scale and without the "Frequency Legend" enabled. As most of us would like to see color chart with the readings on x and y axis. I would suggest the following defaults:
Saturation be 1 instead of 0
Frequency Legend enabled
Color Scheme: Plasma
Great work. Thanks!
Thanks for the feedback! I'm still out of town, but I'll work on implementing this.
As far as color display, I can display down to and including "Green", but the choices below that (Viridis-Plasma-Cividis-Terrain) do not display. This is with a Zerranoe 32-bit build of ffmpeg. But since we already have 11 working color choices, I don't see how anyone, even me, could possibly complain! I use Rainbow at any rate.
Glad to hear that the bug is fixed!
Just wanted to let you know that the color scheme issue only affects 32 bit (I assume). I just tested every color on the 64 bit build and they all work.
As far as color display, I can display down to and including "Green", but the choices below that (Viridis-Plasma-Cividis-Terrain) do not display. This is with a Zerranoe 32-bit build of ffmpeg. But since we already have 11 working color choices, I don't see how anyone, even me, could possibly complain! I use Rainbow at any rate.
Glad to hear that the bug is fixed!
Just wanted to let you know that the color scheme issue only affects 32 bit (I assume). I just tested every color on the 64 bit build and they all work.
Have found that the "nightly git build" of the Zeranoe 32-bit ffmpeg will indeed display all color options; it's only the (currently) 4.1.1 release build that will stop with "Green."
Looking forward to the dynamic seek indicator addition. Will greatly enhance the current seeking, which is already devoid of the click/pop in wasapi-exclusive some of us have experienced in that mode.
<?xml version="1.0" encoding="utf-8"?>
<ConfigMgr xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<ColorScheme>rainbow</ColorScheme>
<Saturation>1</Saturation>
<Gain>1</Gain>
<WindowFunction>hann</WindowFunction>
<ChannelMode>combined</ChannelMode>
<Scale>log</Scale>
<ClearImages>true</ClearImages>
<ShowLegend>true</ShowLegend>
<EnableDebugging>true</EnableDebugging>
</ConfigMgr>I guess what I was hoping to see by "dynamic seek" was just an indication of the playing time of the file as the mouse was dragged or hovered through the spectrogram, as opposed to another seek "bar" itself. In other words, a digital time indicator tied to the file playing time that would temporarily appear when the mouse was hovered through the display, resulting in a "seek" to that time point when "clicked." IMO, the idea of a transparency drawing through the display would be a BAD idea, obscuring the attractive display of the graphics themselves. Better just to leave it as-is in that case.
Is it possible to leave links to a couple of previous versions on the first post, instead of just the latest experimental version?
Would be nice to hear what other users' wishlists/opinions are. I know I'm not shy about mine ;D Thanks for putting up with us.
I guess what I was hoping to see by "dynamic seek" was just an indication of the playing time of the file as the mouse was dragged or hovered through the spectrogram, as opposed to another seek "bar" itself. In other words, a digital time indicator tied to the file playing time that would temporarily appear when the mouse was hovered through the display, resulting in a "seek" to that time point when "clicked." IMO, the idea of a transparency drawing through the display would be a BAD idea, obscuring the attractive display of the graphics themselves. Better just to leave it as-is in that case.
Is it possible to leave links to a couple of previous versions on the first post, instead of just the latest experimental version?
Would be nice to hear what other users' wishlists/opinions are. I know I'm not shy about mine ;D Thanks for putting up with us.
The dynamic digital time indicator that follows the mouse cursor inside the spectrogram is great! Thanks! Um, but may I mention just two things...:-X
Current behavior is that when clicking into a seek point within the image, the song correctly jumps to that time point and continues playing as expected, but the MusicBee elapsed/total track time indicator in the corner will freeze, jumping to the correct time only when the cursor is moved out of the spectrogram panel. Is it possible to synch the spectrogram seek point with the MusicBee timer so that the latter updates immediately? This is easier to see than to describe. And, to see how far out on a limb I can crawl, would be possible to have the mouse cursor while in the spectrogram retain the normal arrow pointer as it did in 1.6x instead of the "funky finger"?
I keep the plugin's own seek bar disabled as it's not needed with your new update, frees up a tiny bit more real estate, and I prefer to keep the MusicBee one available. And with a dark (black) skin you can't see it anyway.
Thanks for your work on this, and for being so open to user requests! Again, thanks for the "placeholder" option that allows the space to be used for a user-supplied image when playing radio streams, works perfect and much appreciated. If it any point you feel like these requests (from me or anybody) start to kludge up the core operation/intent of the plugin, "just say NO!"
In terms of the bug you're experiencing with seeking - I can't replicate it.
Can you attach a screenshot or video of it occurring?
In terms of the bug you're experiencing with seeking - I can't replicate it.
Can you attach a screenshot or video of it occurring?
See the GIF at the link below:
1. Song starts, time elapsed counter in lower right corner begins;
2. At the 6 seconds point I drag the cursor into the spectrogram, which immediately stops the MB time counter and MB seekbar but not the music (the plugin-generated time by cursor doesn't show on the gif--some overlay problem in my gif app, sorry!).
3. I drag the cursor to about 2/3 of the song, click it to seek, and then move it down out of the spectrogram window, which causes the MB seekbar and elapsed time to immediately jump to the right place and resume counting.
https://imgur.com/gLca5DE (https://imgur.com/gLca5DE)
System.ArgumentException: Controls created on one thread cannot be parented to a control on a different thread.In terms of the bug you're experiencing with seeking - I can't replicate it.
Can you attach a screenshot or video of it occurring?
See the GIF at the link below:
1. Song starts, time elapsed counter in lower right corner begins;
2. At the 6 seconds point I drag the cursor into the spectrogram, which immediately stops the MB time counter and MB seekbar but not the music (the plugin-generated time by cursor doesn't show on the gif--some overlay problem in my gif app, sorry!).
3. I drag the cursor to about 2/3 of the song, click it to seek, and then move it down out of the spectrogram window, which causes the MB seekbar and elapsed time to immediately jump to the right place and resume counting.
https://imgur.com/gLca5DE (https://imgur.com/gLca5DE)
Anyway, it would be great if you feel like having another bash at this, and much appreciated by me at least. But if want to consign it to the "things that cannot be fixed" category, I'm good with that too.
Thanks Mr. Trev for contributing your observations! I tried moving my player controls to the top panel--no difference. Also tried to get a hold of the Bleached Bone skin at the Skins downloads in case that made any difference, but that ends up with MediaFire being unable to generate a successful "download key" whatever that means. I have tried the stock MusicBee3 skin, same thing:
I don't know if my placement of the spectrogram makes any difference (bottom main panel) in reference to my general layout, but hopefully zkhcohen can make some progress with my uploaded layout settings I posted above. Here is what they LOOK like at any rate: https://imgur.com/vBDymN7 (https://imgur.com/vBDymN7)
Also tried to get a hold of the Bleached Bone skin at the Skins downloads in case that made any difference, but that ends up with MediaFire being unable to generate a successful "download key" whatever that means.On a positive note, here is a direct link to Bleached Bone (while MediaFire sorts out the problem) (http://www.mediafire.com/file/db876i8182qgafy/BBoneReset.zip/file)
Mr. Trev: Thanks for the screenshot! BTW cool skin. Can you confirm that you are using version 1.7.2 of the plugin zkhcohen uploaded today? Do you have any of the 2 "experimental" options enabled?
@zkhcohen:
I noticed that if you put the panel anywhere else except the bottom of the main panel, you don't get a header bar. That's either with the 'Experimental: Disable Header' off or on.
zkhcohen: also forgot to mention, when rolling back to versions 1.6.1/2, the problem vanishes--having the pointer within the spectrogram makes no difference at all to the player control time counter or progress bar; clicking within the spectrogram to seek produces an instant reaction by the latter to the seek point.
So the problem I have seems directly related to the addition of the progressive time indicator in version 1.7x
I'm still not able to replicate it with your settings, even with the Classic Spectrum Analyzer embedded.
The only think I can think of is that it's some sort of threading issue caused my the Control.MouseMove Event...
@zkhcohen:
I noticed that if you put the panel anywhere else except the bottom of the main panel, you don't get a header bar. That's either with the 'Experimental: Disable Header' off or on.
I'm not able to replicate this on multiple systems. I'm guessing that it's a settings/configuration issue, potentially.
Anyway, I have rolled back to 1.6.1 (3/24/2019 build), which doesn't have the problem, and still has the right-click for Options which I prefer and without the seekbar that I don't use anyway. But that pop-up progressive time indicator was indeed cool. If another build comes out, be sure that I will be testing again :) Thanks again for all your work.
Recently the Spectrogram Panel Plugin no longer shows a top border. How can I restore the top margin?
Disabling and restarting did not help. I hereby send the settings protocol.
https://drive.google.com/file/d/1T5BGdXQ3LhDi8Qus-n2rKZmTSL3-JrI7/view?usp=sharing
but did you check that "disable header" isn't accidently selected in the spectrogram settings?
Yes, thank you for your effort, yes in my settings, this was the check mark in disable header. I have removed and now the top bar is visible again.
Useful, but it will still not replace spek that I'm using to check if song is fake mp3 or anything like that because it doesn't show numbers on any of the sides of the spectrum, so i can't guess where it goes above 16 kHz and 20khz.
Can you please allow it to be placed here?I will look at adding support for plugins in the Now Playing panel for MB v3.5
That would be awesome, thanks a lot Steven!Can you please allow it to be placed here?I will look at adding support for plugins in the Now Playing panel for MB v3.5
I have noticed a major bug with 1.7.4; if two files of the same type (e.g. MP3) and the same Title/Artist--but different bitrates/encoding parameters--are played, the same spectrogram produced for the first one played will not change for the second one, even though the actual graph should be obviously different (and displays so in Spek).
MusicBee 3.4.7601, Windows 10 v2004 64-bit, ffmpeg 4.3.1 64-bit.
FWIW in Properties/Details of mb_Spectrogram-Display.dll, the version still says "1.7.2" instead of 1.7.4, mod date is 3/20/2020.
I think it would be more readable/usefull if it showed a scale 2kHZ/4kHZ/.../20kHZ/22kHZ like Spek does. If you show values like 17226.56 and 20671.88, its normal you think its ugly.
Also using mm:ss as time-format, like Spek, would be nice (perhaps make it optional?)
Seekbar not working atm, but no big deal atm.
Hi,
I am using the Portable Version of MB, and i am not getting this plugin to work. (even installation fails)
When copying the files to the plugins folder and starting MB, no popup. But the plugin is visible in the plugin screen. But when clicking install, an unknown error uccurs.
My MB folder is located on a D drive (portable)
Can you help?
Regards,
Rene
I have noticed a major bug with 1.7.4; if two files of the same type (e.g. MP3) and the same Title/Artist--but different bitrates/encoding parameters--are played, the same spectrogram produced for the first one played will not change for the second one, even though the actual graph should be obviously different (and displays so in Spek).
MusicBee 3.4.7601, Windows 10 v2004 64-bit, ffmpeg 4.3.1 64-bit.
FWIW in Properties/Details of mb_Spectrogram-Display.dll, the version still says "1.7.2" instead of 1.7.4, mod date is 3/20/2020.
Sorry! For some reason I stopped getting notifications for this post. Let me see what I can do.
I have noticed a major bug with 1.7.4; if two files of the same type (e.g. MP3) and the same Title/Artist--but different bitrates/encoding parameters--are played, the same spectrogram produced for the first one played will not change for the second one, even though the actual graph should be obviously different (and displays so in Spek).
MusicBee 3.4.7601, Windows 10 v2004 64-bit, ffmpeg 4.3.1 64-bit.
FWIW in Properties/Details of mb_Spectrogram-Display.dll, the version still says "1.7.2" instead of 1.7.4, mod date is 3/20/2020.
Sorry! For some reason I stopped getting notifications for this post. Let me see what I can do.
Thanks, glad to see you back!
Useful, but it will still not replace spek that I'm using to check if song is fake mp3 or anything like that because it doesn't show numbers on any of the sides of the spectrum, so i can't guess where it goes above 16 kHz and 20khz.
I think it would be more readable/usefull if it showed a scale 2kHZ/4kHZ/.../20kHZ/22kHZ like Spek does. If you show values like 17226.56 and 20671.88, its normal you think its ugly.
Also using mm:ss as time-format, like Spek, would be nice (perhaps make it optional?)
Seekbar not working atm, but no big deal atm.
zkhcohen: 1.7.5 does fix the duplicate spectrogram issue, thanks! However, I greatly prefer the "granularity" and scale of the 1.7.4 spectrogram image compared to the "rounded" images and 3-point frequency label of this one, so much so that I immediately went back to 1.7.4. I can live with the rare cases of my having duplicate artist/title/ext files. Man, I know, so much for trying to please everyone, haha! We're too "ornery"!
Thanks anyhow from all of us, I know the things I mentioned may not bother others. If you let me be a PITA for one more minute, wanted to say that the link to the zeranoe site in your first post for 32-bit ffmpeg versions is defunct, he took down the whole site a while ago. I get my builds now from gyan.dev (https://www.gyan.dev/ffmpeg/builds/ (https://www.gyan.dev/ffmpeg/builds/)) as listed at the official ffmpeg site and they are all 64-bit builds.
Roger that!
OK, this newer one (I call it 175a) successfully loses the "micky moused" look of 175! There are differences in the PNG produced from that of 174 though, not sure if those are intentional due to scaling changes you mentioned. The raw 174 PNG is 1658 X 384, while the one created by 175a is 1380 X 384, which ends up blending some of the finer detail of 174. Therefore, 174 still has a more pleasing look when actually displayed in the MusicBee GUI panel, although correct scaling trumps "pleasing look" every time. So if correcting the scaling is what caused the change, please keep it.
I have uploaded both the 174 and 175 "created" raw PNGs, and screenshots of how they look in my own MB panel, for the same song, so you can see what I refer to: https://filebin.net/x8cl6inb9m81m3hx/spectrogram.7z?t=9x1bqh5v (https://filebin.net/x8cl6inb9m81m3hx/spectrogram.7z?t=9x1bqh5v) . The upload expires after a week. Let me know what you think.
OK, glad to see you thought the new scale wasn't preferable and are reverting it. Please let us know when "175b" is ready to download and thanks a million for all the time you've spent on this!
175b is uploaded at the same url.
Whoops, spoke too soon... 175b no longer honors the existence of a placeholder.png image to be displayed in lieu of the spectrogram when playing radio stations. Otherwise just empty space, and like Nature I abhor a vacuum ;) . Any chance of a 175c that fixes the regression?
Whoops, spoke too soon... 175b no longer honors the existence of a placeholder.png image to be displayed in lieu of the spectrogram when playing radio stations. Otherwise just empty space, and like Nature I abhor a vacuum ;) . Any chance of a 175c that fixes the regression?
I'm sorry, but no placeholder appears in this version either. Just to verify, the one that works with 1.74 is in the AppData/Dependencies folder, along with the config.xml file, with the file name placeholder.png.
Yes that's the file I have. And yes, just noticed that if you switch to playing a fixed file vs. a stream and then back to a stream, the placeholder WILL appear. In 1.74, the placeholder will appear even when starting from a stream, so that version was binding to something different--any chance of reverting the binding behavior to what 1.74 used?
Is the plugin meant to stop running when the window is closed / is no longer visible?
I activate the plugin in its own window as and when I need it (arrange panels > floating window) then close it which I assume would stop it from creating spectrograms.
If I open it again I instantly get spectrograms for tracks I have played in that session including ones when the window was closed, but I get the slight pause before it shows for tracks I have not.
Nope - I didn't design it that way.
Any luck on returning placeholder display to 1.74's behavior of not needing to play a fixed file first before it will show up for radio stations? I know I'm probably an exception but I open the player first to my radio list all the time.
The spectrogram looks really squashed. Help
The spectrogram looks really squashed. Help
How it looks will depend on the frequency range and saturation thereof being "received" from each song. It's normal for some wall-of-sound type piece to produce a spectrogram like that. If you resize the spectrogram's window vertically and/or horizontally it will give the display more room and appear less dense. If you want you can compare the output with Spek (http://spek.cc/ (http://spek.cc/)).
Well now I'm altogether considering integrating Spek. It looks like it piggybacks off of ffmpeg.Hey, on small monitors (1080p), the spectrogram window takes too much space if we don't want it to look squashed. Is there a way to make the fonts look good in default spectrogram window size?
I'll take a look at this when I get a chance to tackle the other issues.
Well now I'm altogether considering integrating Spek. It looks like it piggybacks off of ffmpeg.
I'll take a look at this when I get a chance to tackle the other issues.
Cool idea, and thank you for remembering my placeholder :)
Apologies for necroing your old comment, but just wondering how the progress is coming along with this?Can you please allow it to be placed here?I will look at adding support for plugins in the Now Playing panel for MB v3.5
increase the size of the created images to any value - 500, 800, 1300 pixels (in height).
Update 2: Added height-resizing
Is there any way to change the presentation of the spectrogram image so that less than the full song (say, 10-30 seconds) is displayed at one time, and it scrolls horizontally as the music plays, perhaps with some sort of arrow indicator for the current location?Agreed this would be cool, but then it would kill the current "seek" functioning across the whole song, which I would not want to lose. As an option? Sure, especially as that type of presentaton may then be applicable to radio streams.
Is there any way to change the presentation of the spectrogram image so that less than the full song (say, 10-30 seconds) is displayed at one time, and it scrolls horizontally as the music plays, perhaps with some sort of arrow indicator for the current location?
This is an awesome feature to have in a music player, but it would be infinitely more useful if we could watch the frequency distribution in a smaller window so that we could see the spectral information of the music as it happens rather than just a birds-eye view of the spectral information of the song. Lots of interesting details get lost at this scale.
Even if this could only be implemented as a toggle-able window overlay rather than a fixed frame in the GUI (which would make sense, given the need for an aspect ratio closer to square), that would still be a huge improvement.
The plugin page statesQuoteUpdate 2: Added height-resizing
But I haven't figured out how to change the height. Neither in the player settings nor in the plugin settings. Tell me how can I do this (change the height)?
Have a look at how rekordbox's playlist does it:
https://rekordbox.com/en/feature/cloud-music-management/
(https://cdn.rekordbox.com/files/20200525192122/GUI-cmm_200525.png)
Ahh, that's a very cool idea, but the API doesn't currently support images in the tracklist like that. You could try asking Steven via a feature request.
It's been a couple years now so just wanted to ask if this will be making it in to v3.6?Apologies for necroing your old comment, but just wondering how the progress is coming along with this?Can you please allow it to be placed here?I will look at adding support for plugins in the Now Playing panel for MB v3.5
It's been a couple years now so just wanted to ask if this will be making it in to v3.6?Probably not as it's a plugin. Typically plugins are created when Steven doesn't have the time or desire to add and maintain a feature within MB.
If you check my quoted post you'd see that Steven did say they would look into adding "support for plugins in the Now Playing panel for MB v3.5". Did they change their mind?It's been a couple years now so just wanted to ask if this will be making it in to v3.6?Probably not as it's a plugin. Typically plugins are created when Steven doesn't have the time or desire to add and maintain a feature within MB.
Did they change their mind?Only Steven can answer that question. I was just expressing my thoughts based on the general purpose of plugins.
Ahh, that's a very cool idea, but the API doesn't currently support images in the tracklist like that. You could try asking Steven via a feature request.It does for 'artwork' - but only pre defined ones seemingly (added it as a thought in the feature request here: https://getmusicbee.com/forum/index.php?topic=37796.msg215785#msg215785).
ps. oh, and thirdly - if there's perf tips - as this has a very noticable impact on music playback when activated (hence the request in the other thread to store the image of the spectrum, once analyzed in an artwork slot - so one could see a saved spectrum, instead of having it generated on playback, which seems to be the perf impact.... [?] )The image is already saved by default and reused unless "Clear Images on Restart" is checked; stored in "..\MusicBee\AppData\Dependencies\Spectrogram_Images."
The image is already saved by default and reused unless "Clear Images on Restart" is checked; stored in "..\MusicBee\AppData\Dependencies\Spectrogram_Images."Interesting, thanks for the info (and the spectrum component ;)!