getmusicbee.com
MusicBee & Add-Ons => Customizations => Visualizers => Topic started by: sveakul on November 19, 2017, 08:01:32 PM
-
Hello,
Does anyone else have some experience using this vis plugin in MB they could share? It is still downloadable here:
http://forums.winamp.com/showthread.php?postid=2182482#post2182482
NOTE(4/20/2019): Starting with MusicBee version 3.3.7049.40483, the GUI Options window can now be called up by a right-click inside its visualiser window! No need to do manual ini file edits!
(https://getmusicbee.com/forum/index.php?topic=23345.msg158033#msg158033 (https://getmusicbee.com/forum/index.php?topic=23345.msg158033#msg158033))
NOTE(10/28/2022): There is now a new version of the plugin from raul available at the MusicBee Plugins page, see the message linked here:
https://getmusicbee.com/forum/index.php?topic=23345.msg205827#msg205827 (https://getmusicbee.com/forum/index.php?topic=23345.msg205827#msg205827)
NOTE(08/06/2023): Simplified installation instructions for the new version:
https:https://getmusicbee.com/forum/index.php?topic=23345.msg206731#msg206731 (https://getmusicbee.com/forum/index.php?topic=23345.msg206731#msg206731)
Using 7-Zip, I extracted the 3 components from inside the vis_classic10.exe installer (vis_classic.dll, vis_classic.ini, and "vis_classic" folder of settings) into the MusicBee plugins folder--no need to have Winamp installed. It shows up in the vis selections and seems to run properly with wasapi. In Winamp you could right-click it, choose Properties and get a very nice GUI window with all kinds of settings--but trying this in MB will cause the whole app to hang/crash. You can however adjust the settings manually in the main vis_classic.ini file inside Plugins, and the (profile).ini inside its subfolder "vis_classic". It's tweaks to these that I would be interested in hearing about.
Right now I am using latency=10(inside vis_classic.ini), and the first section of the profile ini I'm using looks like the below; I adjusted for solid bars low freq-hi freq and started with the "blue flames" ini as a root; once you alter the latter a new ini is created called "Current Settings.ini", which is what the plugin will use for its display (Edited 05-12-2018 for equalized with peaks version):
[Classic Analyzer]
Falloff=20
PeakChange=10
Bar Width=6
X-Spacing=1
Y-Spacing=1
BackgroundDraw=0
BarColourStyle=0
PeakColourStyle=2
Effect=0
Peak Effect=0
Bar Level=1
ReverseLeft=0
ReverseRight=0
Mono=1
FFTEqualize=1
FFTEnvelope=20
FFTScale=20 (if used with sys vol control with MB volume at max, use 160-190 here)
...after this section follows the color settings from the profile ini you are modifying.
These settings look like this (GIF): https://imgur.com/pFWxZg0 (https://imgur.com/pFWxZg0)
It seems hard to find a straight-ahead bars style spectrum vis nowadays so I'm hoping this one can do until something newer comes along. Thank you for any input.[/color]
-
I should add to this rather lonely post that this visualizer does NOT cause the speeded-up tempo change with WASAPI which is a known bug when using most visualizers in WASAPI or ASIO. Granted, it is a pretty basic spectrum bar display but the control over varying bar colors and peak effects, width, falloff rate, etc is exceptional. I have it inserted under my Track Information panel in the right sidebar, height can be varied by dragging the header bar.
I modified my settings somewhat in the first post to reflect what I am using now. The color settings, which are not shown, match the stock "blue flames" ini included in the pre-defined profiles (18 choices) bundle inside the "vis_classic" folder.
-
I use this viz to replace the normal spectrum in the Maya Blue Dark Fine-Tuned skin under the Track Information:
(https://i.imgur.com/3zhoAUS.jpg)
-
Here are my "dirty notes" on what the settings options mean in the "Current Settings.ini" file inside the "vis_classic" subfolder ("Latency" setting is inside the vis_classic.ini in the main Plugins folder, for which I use a value of 10):
falloff: bar fall off rate, 20 for MB, 7 for XMPlay, 9 for Winamp (higher is faster)
peakchange(peak indicator change rate of all effects):
0=no peaks displayed
5=(fastest)(good for fall)
10=better for no fall
67=old norm for peaks (slower)
Bar Width=(I use 6)
backgrounddraw:
0=black
1=grid
2=solid color
3=flash
4=flash grid
barcolourstyle:
0=classic
1 through 4 also: soft flame, fire, solid lines, winamp fire
----------------------------------
peakcolourstyle:
0=fade (keeps same light peak color across all bars at their peak, and fades)
1=level
2=level and fade (assumes color of zone it rises to, and fades)
effect:
0=none
1=mirror
2=reflection
3=shadow
4=double shadow
5=smoke
6=refelction waves
7=fade shadow
peak effect:
0=normal (does not fall)
1=fall
2=rise
3=fall & rise
4=rise fall
5=sparks
Bar Level= 1 (other?)
ReverseLeft=0 (how to display L/R if not mono)
ReverseRight=0 (as above)
Mono=1 (doesn't mean "mono source", use 1 for single spectrum display from stereo source or "0" for L/R channel combined display)
FFTEqualize=0 (1=Equalize display, both require different FFTScale settings for best display)
-------------------------------
-
Hello Sveakul,
did you were able to change the hight of the visualization panel?
I was unable to do that and got stucked with about fixed 250 px but i would like to set around 40 px.
Currently the visualization pannel eats up almost 1/3rd of my screen now :-\ ...
(https://i.imgur.com/hrOLGoe.jpg) (https://i.imgur.com/hrOLGoe.jpg)
Would be great if anyone could help here.
Greetings
-
Hi KangNi, good to see somebody here besides me, haha.. I use the spectrum on the bottom of the Right Sidebar, under Track Information, and find that I can make its window any height I want by just dragging the top bar (Visualiser Header Menu bar) in steps.
However, when I moved it to the Bottom Panel just now, I found the same thing you did--a fixed height and no bar to drag. I also noticed that it's missing the "Visualiser" header menu--normally that IS the top bar which is draggable, and what you would expect to see where you want a visualiser element to appear. So, it MAY be that for some reason MusicBee is not correctly including a Visualiser Header Menu (bar) if the element is placed in the Bottom Panel--which might effect ANY visualiser placed there.
Curiousity may have killed the cat, but I felt lucky and tried choosing a "stock" visualiser instead, "Interference", and placed that one in the Bottom Panel above Player controls and status bar, and guess what---no header bar, and same fixed height! So, it's NOT a fault of the Classic Spectrum Analyzer.
I would consider it therefore a reportable "bug"--when a graphic visualiser element is placed in the Bottom Panel, it ends up at a fixed height with no Visualiser Header Menu bar. I will report same and we'll see what happens.
-
Resize isssue in Bottom Panel was posted as discussed above to the Bugs forum today.
BTW, KangNi what are you using for a "Latency" setting?
-
Hey Sveakul,
thank You for your engagement in this and also your investigations and the bug report. :)
I already was contemplate that the fixed height is a bug somehow.
My Blue Flame settings are currently as follows ...
[Classic Analyzer]
Falloff=30
PeakChange=67
Bar Width=6
X-Spacing=1
Y-Spacing=1
BackgroundDraw=0
BarColourStyle=0
PeakColourStyle=2
Effect=0
Peak Effect=1
ReverseLeft=1
ReverseRight=0
Mono=0
Bar Level=1
FFTEqualize=1
FFTEnvelope=20
FFTScale=200
By the way, did you now how to easely change the color for [BarColours], [PeakColours] and [VolumeColours]?
If therefor didn't exist any tool I may have to frickel something in Excel ;)
I suppose [VolumeFunction] allows the logarithmic scaling.?
Greetings and have a nice day.
-
The easiest way to change the bar and peak colors is by having access to the GUI--yep the one that crashes MusicBee. If you can install the plugin in Winamp or in XMPlay, you can right-click the viz window and get a context menu that allows you to select "Properties"--doing that brings up an excellent GUI with full slider-style controls over the colors, settings, etc., and to top it off the changes show up in real-time. Of course, the best non-color settings are going to vary between MusicBee and the other players, but what you can do is adjust the colors in the GUI within another player, then copy the profile.ini from that player to MusicBee, and replace the settings portion of the ini with what you use for MusicBee. Of course if you can come up with something in Excel that would be great too, I'm too lazy for that haha..
(https://i.imgur.com/jLrxzPN.jpg)
The GUI has another tab "Flash Function" which allows you to change "linear/log/sine/squared" curve numbers but I don't want to mess with that, I left it at default.
Actually I have no idea what "VolumeFunction" does except that by the content it must also be related to the color changes somehow. BTW, the setting for "Latency" I asked about is in the vis_classic.ini, not the profile ini.
I noticed that your FFTScale value is different than mine--what exactly does that value change in the spectrum display?
.
-
Re the discussion above, thanks to Steven the visualisation window height for Bottom Panel placement is now adjustable via the added header bar as of MusicBee 3.2.6695.
-
Hi Sveakul,
I'm a beginner to the whole modding scene and I'm somewhat confused as to how you got the visualizer working. You somehow extracted some dll's and ini files from the .exe installer and put them in the Musicbee plugin folder. and that's where I got lost. now, I couldn't even get the files from the exe but I suspect it needs an actual Winamp install to work. Is that correct? I'd love to know how to do this. Cheers! :)
-
ArachneNet: Glad to hear you're interested in this visualiser! Once you've downloaded vis_classic10.zip, unzip it and you'll find the installer, vis_classic10.exe. To extract the contents from vis_classic10.exe without actually running the installer (or needing to have a Winamp folder), you can use an application like the freeware 7-Zip (https://www.7-zip.org/ (https://www.7-zip.org/))
1. First put the exe into some non-MusicBee folder, then use 7-Zip to extract it; it will extract it as a folder named vis_classic10;
2. Inside that extracted folder you'll find a subfolder "Plugins". Inside THAT folder, you'll find 2 files and another folder: vis_classic.dll, vis_classic.ini, and the folder vis_classic;
3. Copy those 3 items--vis_classic.dll, vis_classic.ini, and the folder vis_classic--into MusicBee's own Plugins folder. It should then show up in the choice of visualisers after restarting MusicBee.
I would recommend copying either my or KangNi's settings in the posts above so you've got a starting point for future tuning to your own preferences.
If you have more questions, feel free to post them. Enjoy!
-
Bit crowded but I got it to work! Thanks!! :D
(https://orig00.deviantart.net/b779/f/2018/123/d/d/musicbeescr4_by_arachnenet-dcaii9t.png)
-
Hello Sveakul,
previously you was asking for my latency settings in the vis_classic.ini - currently I use Latency=10.
Furthermore, could You help and explain tu us how a solid background coulour can be set different from black?
BackgroundDraw=0 is black, 2 is solid - but how to set a RGB-value in here?
BackgroundDraw=20 20 20 doesn't work.
Is there a unknown variable like "BackgroundColour" (doesn't work too) or something similar?
By the way - which player do you use to get the option dialog running?
Thank you in advance.
Greetings
-
Bit crowded but I got it to work! Thanks!! :D
You can lower the height of the vis window, making it a lot less crowded, if you update to MusicBee 3.2.6695 or greater; Steven has added a header bar for bottom pane vis windows where you can drag the bar to any height you want :)
-
BackgroundDraw=0 is black, 2 is solid - but how to set a RGB-value in here?
BackgroundDraw=20 20 20 doesn't work.
Is there a unknown variable like "BackgroundColour" (doesn't work too) or something similar?
By the way - which player do you use to get the option dialog running?
Hi KangNi, I ran into the same dilemma as you with trying to use "2" in BackgroundDraw--the only color it wants to use is black, which is the same as setting it to "0". I don't have a solution at this time. If you discover something, please post.
In order to invoke the GUI options dialog, as I said in the post showing the GUI: "If you can install the plugin in Winamp or in XMPlay, you can right-click the viz window and get a context menu that allows you to select Properties." I have both of those players for various reasons. As I mentioned, it's a good way to adjust the profile in an easy-to-see-results way, and then copy the settings from that Current Settings.ini to the one in MusicBee. Be aware that non-color settings, like Falloff, PeakSpeed, etc. will NOT be the equivalent of what works best in MusicBee, so do not copy those over.
Thanks for sharing your Latency value, "10" seems spot-on for responsiveness to the actual audio in MusicBee.
-
Hi there :D
I've go it ! - The background color and everything else too ;)
BackgroundDraw=2
[VolumeColours]
0=20 20 20 > that's where the solid background color is defined
combined with some awesome shadow effects, with the investigations of Sveakul and Stevens recently patch - voila ...
(https://i.imgur.com/0AOlmEt.jpg) (https://i.imgur.com/0AOlmEt.jpg)
I call it "Red Flame" 8)
[Classic Analyzer]
Falloff=30
PeakChange=67
Bar Width=5
X-Spacing=1
Y-Spacing=1
BackgroundDraw=2
BarColourStyle=0
PeakColourStyle=2
Effect=7
Peak Effect=0
Bar Level=1
ReverseLeft=1
ReverseRight=0
Mono=0
FFTEqualize=1
FFTEnvelope=10
FFTScale=190
Greetings.
-
Just to give an impression of what settings this spectrum visualizer plug-in provides and how incredible deep they are:
(https://i.imgur.com/aKGri2V.png)
(https://i.imgur.com/45EcZ8B.png)
(https://i.imgur.com/LdhVm78.png)
(https://i.imgur.com/pyALRps.png)
(https://i.imgur.com/ATQFQEX.png)
(https://i.imgur.com/aJiMcl4.png)
I've used XMplay ...
http://support.xmplay.com/
... in combination with the following plug-in ...
http://www.nukular.ch/xmp-wavis_rev.5.zip
http://www.un4seen.com/forum/?topic=8807.msg60575#msg60575
... to be able to run Winamp visualization plug-ins.
I really would love to see getting this dialog working in MB :(
By the way, now i need MB being able to run 2 visualization plug-ins simultaneously - currently I can't run milkdrop in parallel :-X
Greetings.
-
Hi there :D
I've go it ! - The background color and everything else too ;)
BackgroundDraw=2
[VolumeColours]
0=20 20 20 > that's where the solid background color is defined
hey KangNi, great job on the spectrum settings, your "Red Flame" rocks! Congrats on solving the background color mystery too, and thanks for posting the solution! So, once BackgroundDraw=2 is specified, it's ONLY the first "0=(RGB value)" line under [VolumeColours] that needs to be changed to give the new background color, not the rest of the lines under it, correct?
Two other questions for you: what was the "stock" profile you used for the Red Flame mod? And, have you tried varying the FFTEnvelope and FFTScale settings, and what if any visible changes were noticed?
Yes it would be great if MusicBee supported the superb GUI, but I hope that someone will eventually write a native MusicBee plugin that supports the same functions. Until then at least we've got Classic Spectrum Analyzer :)
-
Hi Sveakul,
hey KangNi, great job on the spectrum settings, your "Red Flame" rocks! Congrats on solving the background color mystery too, and thanks for posting the solution! So, once BackgroundDraw=2 is specified, it's ONLY the first "0=(RGB value)" line under [VolumeColours] that needs to be changed to give the new background color, not the rest of the lines under it, correct?
Yes, it's exactly like you was written above.
Two other questions for you: what was the "stock" profile you used for the Red Flame mod?
"Blue Flame", but I've changed almost very value now ;)
And, have you tried varying the FFTEnvelope and FFTScale settings, and what if any visible changes were noticed?
Maybe first it's good to understand what FFT (Fast Fourier transform) is:
https://en.wikipedia.org/wiki/Fast_Fourier_transform
https://de.wikipedia.org/wiki/Schnelle_Fourier-Transformation
I'll try to explain it in my own word so far I understand it:
FFTEnvelope specifies in how many sections (envelops) the frequency spectrum is splitted, or in other words, how large the splitted frequency bands are.
FFTScale is just a kind of amplification value. As lower it is as higher the bars.
I suggest to use values between 1.80 (180) and 2.00 (200).
However, I strongly would give the advice to anyone who want playing with the plugin-settings: get XMplay running e.g. and retrace the change and effect of every setting LIVE! That's how I got my settings.
Yes it would be great if MusicBee supported the superb GUI, but I hope that someone will eventually write a native MusicBee plugin that supports the same functions. Until then at least we've got Classic Spectrum Analyzer :)
Whether that or we could find the developper of that plugin and convince him to join the MusicBee comunity :D
I think it would be a wast to redevelop the wheel again ;)
Greetings
-
Thanks a lot for the FFTScale tip, that's just what I needed to complete my tweaking. I had never tried changing that value real-time via XMPlay's interface to see the effect! I limit to -.5db with a VST plugin for radio streams and wanted the spectrum bars to reach the top of the window when that peak is reached on my chosen volume level--funny how "cosmetic" we can get when given enough options! ;D
-
For those who don't have access to the spectrum's GUI but want to manually adjust all the color RGB values in the profile.ini, this can be very useful in picking the numbers to use for the colors you want:
https://www.rapidtables.com/web/color/RGB_Color.html (https://www.rapidtables.com/web/color/RGB_Color.html)
Although I wouldn't envy you the task!! Good for choosing a background color though if you choose the BackgroundDraw=2 option (discussed in previous posts).
-
love the feature and I can adjust it to its height that I want!
-
Bit crowded but I got it to work! Thanks!! :D
You can lower the height of the vis window, making it a lot less crowded, if you update to MusicBee 3.2.6695 or greater; Steven has added a header bar for bottom pane vis windows where you can drag the bar to any height you want :)
Hello, where are you finding 3.2.6695? The latest I see is 3.2.6693
-
Hello, where are you finding 3.2.6695? The latest I see is 3.2.6693
Hi bsell1 and welcome to the forums! The latest versions of 3.2 are available as patches, updated almost daily, at the link here:
https://getmusicbee.com/patches/MusicBee32_Patched.zip (https://getmusicbee.com/patches/MusicBee32_Patched.zip)
I am currently running 3.2.6712. Extract the entire contents of the patch zip to your MusicBee folder, overwriting existing files.
Then, grab the spectrum from the link in this thread's first post and let us know what settings and theme work best for you! 8)
Edit: link updated 07-30-2018
-
New to MusicBee. This is my first post and would like to give this one a bump. Came looking for visualizer info and classic_spectrum_visualizer was always my favourite. Happy to see it runs under MB on Win10. (The plugin is buggy at times but once configured it is solid.) Thanks for the details in this thread I have this one up and running in very little time. Loving MB so far!!
-
Welcome to the forum Glamrlama! I'm glad that you found this thread helpful in setting up Classic Spectrum Analyzer. I echo your comment that once configured this plugin is definitely solid. My fave spectrum of all and the latency response is nearly real-time. Not to mention the multitude of looks/effects available.
-
Can't get it to work
MB version 3.2.6827
When i enable the plugin it says
"unable to initialise this plugin: Dll entry point: Initialise was not found"
pls help me
a newbie
-
Hi LoveMusic: Don't try to add/enable this visualization plugin via the Plugins/Add Plugin dialog; if you did, uninstall it, so it doesn't show up in the Plugins panel. Then, let's start clean:
1. Go to the MusicBee/Plugins folder in Windows File Manager/Windows Explorer and delete, if still present, vis_classic.ini, vis_classic.dll, and vis_classic subfolder. Then, restart MusicBee.
2. Exit MusicBee. From the original vis_classic10.exe installer, use 7-Zip to extract the same components again--vis_classic.ini, vis_classic.dll, and the vis_classic subfolder--directly into the MusicBee/Plugins folder.
3. Start MusicBee; in the menu View-->Visualiser, the choice "classic" should appear. Select it. Now you can place it using the Arrange Panels/Available Elements dialog, where it will appear as "visualiser:graphic" in the selectable elements box. It will not appear at all in the Preferences/Plugins panel.
Then experiment with its settings as described in the above thread.
-
Svaekul, can you tell me how to adjust the size? I've edited the colors and effets to my liking but the size is very big. Also musicbee is crashing, is this a common problem or I've done something wrong
EDIT: I've done it. You can resize if you choose one of the default visualizers, then switch back to the modified and it stays the same size.
-
Hi Blowout: The vis display window size was made adjustable for the Bottom Panel in MusicBee versions at or greater than 3.2.6695 (grab the top of the window border); the top of the window bar is also adjustable when the spectrum is used in the Right Sidebar. Be sure you're using the latest version of MusicBee. The FFTScale setting in the spectrum's ini file controls the height (amplitude) of the spectrum bars within the window.
I had some crashing when first setting up the spectrum to my desired look for performance/effects/size, but since then it's been completely stable for me. Of course, this could be locally affected by what other plugins are in use, skin, OS, etc. I'm glad you got your size issue resolved. If you have any more questions, feel free to post and I (and others) will try to help. I love this spectrum!
-
Source code; https://github.com/WACUP/vis_classic
It would be nice if somebody could adapt it to MB.
-
It would be nice if somebody could adapt it to MB.
You can say that again :( It would be nice to be able to use the wonderful built-in Options GUI instead having to modify the ini file by hand. I'm just glad everything still works as well as it does, considering.
-
Hi Sofocl,
are you pretty sure that the Github link you was posted is really contain the source code of THAT visualizer what was published hereinafter by "prowler7" in 2007 ?
http://forums.winamp.com/showthread.php?threadid=270809
If so - it would be awesome.
I've tried to contact the developer "prowler7", just before I've read your post. I've let him known that his work is still very popular. Of course I put some hope in it, that maybe he would/could start again to support his own plug-in.
Let's see if he respond.
Greetings
-
Hi Sofocl,
are you pretty sure that the Github link you was posted is really contain the source code of THAT visualizer what was published hereinafter by "prowler7" in 2007 ?
Yeah, also a new version from dr0 but unfortunately it doesn't work with MB at all.
I've tried to contact the developer "prowler7" in two ways, just before I've read your post. I've let him known that his work is still very popular. Of course I put some hope in it, that maybe he would/could start again to support his own plug-in again.
Let's see if he respond.
Greetings
I think\hope that some of the forum participants could prepare a version for MB, the benefit is the source code.
-
Hi there,
I've got a reply from Mike Lynch some days ago. He friendly explained that he isn't interest to put more efforts in his visualizer plugin, so thats the reason why he decided to publish the source code after he was contacted by supporters of the WACUP (WinAmp Community Update Project).
Sofocl,
you wrote "a new version from dr0 but unfortunately it doesn't work with MB at all".
I'm pretty sure that's because the code was modified to work with WACUP and the Winamp SDK 5.666.
However, in the github history the original code from Mike Lynch can be found too.
I've gave it a try, downloaded and compiled the code with MS Visual Studio 2017 (v15) - and it worked ;)
I've got a ~180 KB .dll with version 1.1.0.0 © 2007 Mike Lynch - and it just running in MussicBee.
Now we need someone who is familiar with C++ to fix the minor flaws of the plug-in, like:
- ability to open the context menu
- option for transparent background
- bug fix to work reliable with streams
Hope we can find a Stakeholder here ;)
Greetings
-
hey KangNi, great work on doing your own compilation of the dll! Do you know what changes he made from the original 1.0.0.0 version to the 1.1.0.0 one you now have? And, would you mind linking to your new dll somewhere?
Also, you mentioned one of the flaws still is an inability to work with streams; my original version works just fine with radio streams, which is 60% of what I listen to. Are you not seeing that with yours?
-
Hi there.
I haven't really compared v1.1.0.0 and v1.0.0.0., but also didn't recognized any difference in the GUI and behavior. I'm pretty sure now that all changes after V1.0.0.0 where implemented by WACUP supporters and are NOT part of the original source code release by Mike Lynch.
So, other than I mentioned in my last post, I hasn't used the oldest (original) but also not the latest source branch from Github, because in the latest one there was linked missing resources I just couldn't find anywhere.
As I've stated already, I didn't have any C++ skills. Because of that and I didn't have a glue of what I've really compiled now, I think it would not be a good idea to publish something immature.
About the flaws in connection with streams:
I've recognized that CSA* only working once after MB is started. As soon I switch to another radio station, CSA* stop working. But playing local files after that will re-animate CSA*. To get it running again with streams, MB need to get re-started. :-\
In addition - something very important, as I would say :
MB needs to get the ability running an embedded and an external visualizer in parallel !
Otherwise we won't be able to simply run i.e. MilkDrop in full screen, without disabling the "graphic visualizer" in the "Pannel Configuration" laboriously each time again. This is really a pain for everyone who would use both. :'(
If anyone would like to support this, here is the corresponding threat in the wishlist:
https://getmusicbee.com/forum/index.php?topic=25552.0 (https://getmusicbee.com/forum/index.php?topic=25552.0)
Since the source code of CSA* is published, it may also would be imaginable to implement that code into MB natively. - Steven ? :)
So far,
Greetings to everyone, and sorry for my late reply.
*CSA = Classic Spectrum Analyzer
-
About the flaws in connection with streams:
I've recognized that CSA* only working once after MB is started. As soon I switch to another radio station, CSA* stop working. But playing local files after that will re-animate CSA*. To get it running again with streams, MB need to get re-started. :-\
Thanks KangNi for the info; I can understand why you didn't put out the new build. I'm puzzled though as to your issue with CSA not staying active when switching radio streams--I don't have that problem AT ALL here. Can you try using CSA at the bottom of the Right Sidebar, instead of Bottom Panel, and see if that makes any difference? Have you tried temporarily deactivating any other plugins you are using to see if one of those is interfering? Other than being sure you're using the newest patched 3.3 MB which I'm sure you are, I don't know of any other suggestions. BTW, when you use CSA with streams on XMPlay, do you have the same issue?
-
I've updated MB to v3.3.6982 - no changes.
Regarding the stream problem:
I'v just recognized that obviously there are some specific station where the previously described problem occurs (at least for me):
- https://www.radioking.com/play/radio17bis (Radio DixSept Bis)
- http://mp3stream1.apasf.apa.at:8000/listen.pls (Radio FM4)
- http://somafm.com/fluid64.pls (Soma FM | Fluid)
Just to give a few examples.
I didn't try playing streams in XMPlay yet, maybe I do it later. I never used XMplay again after I setup CSA ;)
-
Did the stream issue start when you began using your own compilation of the CSA code, or was it also there in the original CSA download? There's nothing odd about those links, they work normally here with CSA in MusicBee and XMPlay. If rolling back to the original CSA doesn't solve it, try updating your video drivers at the manufacturer's (NOT Microsoft's) site. After that I'm outta change :(
-
Okay, I've found something:
I've disabled "increase buffer size" and it worked! ;)
It was set 2,0 seconds.
I've re-enabled this setting again to 2,0 seconds, restart MB, and it still is working :o
No idea what was wrong here.
Greetings
-
It seem that another option is the reason:
I disabled the "resample to:" option.
This seems reproducibly the reason for the misbehave of CSA at streams. :-\
Before I've re-sampled audio to 192 KHz.
Greetings
-
Hey, I'm glad to hear you got it solved! I don't resample at all so that would explain why it never happened to me. As one last check, does changing the output method (WASAPI, DS, Asio etc) but keeping resampling have any effect? I have a feeling a latency issue with the timing of when CSA receives the signal is at the bottom of this. But at least you solved the main issue.
-
Now we need someone who is familiar with C++ to fix the minor flaws of the plug-in, like:
- ability to open the context menu
- option for transparent background
Hope we can find a Stakeholder here ;)
Looks like we have some hope here: https://getmusicbee.com/forum/index.php?topic=25944.msg155952#msg155952 (https://getmusicbee.com/forum/index.php?topic=25944.msg155952#msg155952)
-
Now we need someone who is familiar with C++ to fix the minor flaws of the plug-in, like:
- ability to open the context menu
- option for transparent background
Hope we can find a Stakeholder here ;)
Looks like we have some hope here: https://getmusicbee.com/forum/index.php?topic=25944.msg155952#msg155952 (https://getmusicbee.com/forum/index.php?topic=25944.msg155952#msg155952)
Could you clarify what needs to be done?
I can probably do it but those two line-items are not descriptive.
-
Glad to see you here, sir! What we hope to see:
1. The CSA natively comes with an options-rich GUI which is meant to be invoked by right-clicking in the window area and selecting "Properties"--the screenshots farther up the thread show you what they then look like. Unfortunately, trying to do this when the CSA is loaded into MusicBee will cause MB to crash--every time. To see the GUI in action, you could load the plugin in the XMPlay player (the player requires the xmp-wadsp.dll plugin to use Winamp dsp plugins). Hopefully, the CSA source code pointed to in Sofocl's post (https://getmusicbee.com/forum/index.php?topic=23345.msg154061#msg154061 (https://getmusicbee.com/forum/index.php?topic=23345.msg154061#msg154061)) will help you find a way to adapt the GUI for use in MusicBee.
2. KangNi expressed the desire for the background of the spectrum window to have a selection for "transparent" in the Style/Background GUI options, probably to provide the option to show the MB skin behind it.
Thank you for taking a look at this.
-
Glad to see you here, sir! What we hope to see:
1. The CSA natively comes with an options-rich GUI which is meant to be invoked by right-clicking in the window area and selecting "Properties"--the screenshots farther up the thread show you what they then look like. Unfortunately, trying to do this when the CSA is loaded into MusicBee will cause MB to crash--every time. To see the GUI in action, you could load the plugin in the XMPlay player (the player requires the xmp-wadsp.dll plugin to use Winamp dsp plugins). Hopefully, the CSA source code pointed to in Sofocl's post (https://getmusicbee.com/forum/index.php?topic=23345.msg154061#msg154061 (https://getmusicbee.com/forum/index.php?topic=23345.msg154061#msg154061)) will help you find a way to adapt the GUI for use in MusicBee.
2. KangNi expressed the desire for the background of the spectrum window to have a selection for "transparent" in the Style/Background GUI options, probably to provide the option to show the MB skin behind it.
Thank you for taking a look at this.
Yeah. I can probably do this.
I don't have time to look at the source code right this second, but can you cause it to crash and then send me the associated report from your MusicBee error logs?
-
Actually the crash sequence doesn't produce an entry in the MB error log, unfortunately. Instead, you get a Windows "Program Not Responding" message:
Description:
A problem caused this program to stop interacting with Windows.
Problem signature:
Problem Event Name: AppHangB1
Application Name: MusicBee.exe
Application Version: 3.3.7011.33478
Application Timestamp: 5c894de6
Hang Signature: bb13
Hang Type: 4
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Hang Signature 1: bb1339ed19f0961c98e0ff516ad1cc8a
Additional Hang Signature 2: f9f7
Additional Hang Signature 3: f9f725122ec4d4f052ead1320d7ca78f
Additional Hang Signature 4: f095
Additional Hang Signature 5: f095ea1431772cece13db4b56e132bf5
Additional Hang Signature 6: 06cb
Additional Hang Signature 7: 06cba739a016d32254006ebbc35e5469
The sequence of events is thus:
1. Open MB with the CSA loaded and its window displayed.
2. Right-click in the CSA window; instead of then displaying a Properties/Profiles/Close/About context menu from the plugin, part of the spectrum (if playing) will freeze and nothing appears. Your song (if playing) will continue to play--if you didn't have anything playing, nothing appears either.
3. Then trying to perform any kind of activity in MB (navigate to another tab, start a song, etc.) will totally freeze it. Attempting to continue will result in the Windows error and offer to close the program.
If you don't try to pull up that right-click menu, the plugin functions (shows a spectrum) problem free, crash free every time throughout any MB navigation. Users must therefore make their changes manually to the plugin's actual ini files (yes there are TWO of 'em--"vis_classic.ini" in the Plugins folder and "Current_Settings.ini" in the vis_classic subfolder within Plugins).
I hope I haven't scared you off :-X
-
3. Then trying to perform any kind of activity in MB (navigate to another tab, start a song, etc.) will totally freeze it. Attempting to continue will result in the Windows error and offer to close the program.
If you don't try to pull up that right-click menu, the plugin functions (shows a spectrum) problem free, crash free every time throughout any MB navigation. Users must therefore make their changes manually to the plugin's actual ini files (yes there are TWO of 'em--"vis_classic.ini" in the Plugins folder and "Current_Settings.ini" in the vis_classic subfolder within Plugins).
I hope I haven't scared you off :-X
I mean, initially it seems like an easy problem but seeing as this is C++ and was compiled in 2010 (?), it's a bit messy.
Was really hoping that it would produce a usable error message.
I guess you could try installing earlier C++ Redistributables...
I can also see if recompiling magically solves the issue. Otherwise, I'll try to debug it.
-
I have the 2008-2010-2013-2017 redists so that isn't it. I think we'll have to rely on your debugging.
-
I'm still not having any luck with this one...
-
Hey man it's OK, I just appreciate that you did give it a go. Sticking with manual mods of the ini file won't kill me. We can use your skills elsewhere! :)
-
I have no clue why this started working...
(https://i.imgur.com/hiBMt0d.png)
Edit: Here's my guess...
1. Another legacy visualizer was bugging out when I enabled the panel and threw a class registration error.
2. I believe that the right-click menu might conflict with the right-click menu that allows you to switch between visualizers on the panel.
3. I believe that #1 caused the menu in #2 to be un-bound from right-click for that session, and allowed the Classic Spectrum settings to appear.
If this is the case, I might be able to change the mouse-binding and recompile the code.
-
Wow, that is great!! When you actually choose "Properties" now, do you get the Options GUI??
PLEASE do recompile and test again! Can't wait to see this in action. Wishing you luck!
-
Wow, that is great!! When you actually choose "Properties" now, do you get the Options GUI??
PLEASE do recompile and test again! Can't wait to see this in action. Wishing you luck!
Well... I leave you with that.
I recompiled in VS 2017, but I think there are just too many differences. The plugin simply doesn't work in MB or WinAmp.
I've already spent too much time beating away at this.
Someone else needs to install VS 2005, 2008 or 2010 in a VM and recompile it in its native environment.
To whoever tries to do it:
Use the OLD Windows SDK headers.
Use these as well: http://wiki.winamp.com/wiki/SDK_Contents
And use these: https://getwacup.com/sdk/
DON'T use the main Github source, use this unmodified one: https://github.com/WACUP/vis_classic/releases/tag/v1.1
Good luck. You'd be better off asking Steven to change the key-binding in the Visualize:Graphics panel.
-
Huh... for some reason if I stack the Visualizer behind another panel, and then restart MusicBee with the OTHER panel active, when I restart and then click the header to go back to the Visualizer, I get a class registration error, but then the right-click menu works every time.
It's exploiting a bug, but it works every time for me.
Could you try to replicate that?
-
I have to ask: you posted an image of it actually running in MusicBee (I assume), showing the context menu, and confirmed that it did call up the Options GUI. Is whatever configuration that produced that in your own environment something that if posted might produce the same useability for others? Or was it running in some kind of specific test environment not reproducible for ordinary use? Not being a programmer, I apologize for whatever ignorance those questions disclose.
But if that's the end of it, THANK YOU for the considerable effort you made, and the keys you left for others to follow. At least it can continue to run great as-is in MusicBee with manual edits to the ini files, GUI access or not. I have found it extremely stable and without real competition as far as what it can do. As I mentioned before, your expertise is needed for other plugins!
UPDATE: OK just saw your new post! Can you please detail the steps you took to "stack" the panel? And if once the operation is completed, the menu works every time MB is started, or does the same exploit need to be done every time? The latter would sorta kill the useability except for maybe the first set-up of the opions from the GUI.
-
UPDATE: OK just saw your new post! Can you please detail the steps you took to "stack" the panel? And if once the operation is completed, the menu works every time MB is started, or does the same exploit need to be done every time? The latter would sorta kill the useability except for maybe the first set-up of the opions from the GUI.
It's only really useful for the first configuration.
Panel Layout with stacking:
(https://i.imgur.com/oHN5zLp.png)
Gif showing steps to replicate on new launch of MusicBee:
(https://i.imgur.com/CU06Xws.gif)
-
Thanks for the details and gifs, very much appreciated.
I want to add a request in the Wishlist thread for Steven to "change the key-binding in the Visualize:Graphics panel" as you mentioned, but can you go into more detail please so he'll know exactly what action I am requesting? Then I will so post.
I like your never-say-die approach. I also appreciate recognizing when the point to "move on" has been reached. A tip of the hat to the only person who gave it a shot.
-
I want to add a request in the Wishlist thread for Steven to "change the key-binding in the Visualize:Graphics panel" as you mentioned, but can you go into more detail please so he'll know exactly what action I am requesting? Then I will so post.
"Please restrict the built-in right-click menu (for switching between visualizers) on the Visualizer:Graphics panel add-in to the Header bar, instead of the entire panel-area. In its current implementation, the right-click menu is at best, unreliable, and at worst, causes crashes with certain visualizers."
-
Hey, Steven fixed the binding and now you can call up the Options GUI with a right-click!! And make changes realtime!!
Thanks zkhcohen for working the problem and determining the issue, and to Steven for applying the fix! Everyone should now update their MusicBee here: https://getmusicbee.com/patches/MusicBee33_Patched.zip (https://getmusicbee.com/patches/MusicBee33_Patched.zip)
This thing works like a BEAST now, come one, come all, grab the download from the first post!
-
Indeed, works great. I did have an issue initially where the plugin would crash MB. I had the visualizer stacked with lyrics on the right side bar. Milkdrop visualizer worked fine, but as soon as I tried switching to this vis., MB would crash. I unstacked the visualizer and placed it under lyrics and it seems to work OK now.
Just too bad we can't have 2 visualizers running at the same time - I miss Milkdrop ;)
-
Hey, Steven fixed the binding and now you can call up the Options GUI with a right-click!! And make changes realtime!!
Thanks zkhcohen for working the problem and determining the issue, and to Steven for applying the fix! Everyone should now update their MusicBee here: https://getmusicbee.com/patches/MusicBee33_Patched.zip (https://getmusicbee.com/patches/MusicBee33_Patched.zip)
This thing works like a BEAST now, come one, come all, grab the download from the first post!
Awesome. Glad to hear this got resolved.
-
This is AWESOME ! :) Thank you! Thank you all!
Now I (supposing others too) would be pleased very much if we could care on this "problem" here:
EXTERNAL VISUALIZER + EMBEDDED VISUALIZER
https://getmusicbee.com/forum/index.php?topic=25552.msg146528#msg146528
Greetings
-
1. First put the exe into some non-MusicBee folder, then use 7-Zip to extract it; it will extract it as a folder named vis_classic10;
2. Inside that extracted folder you'll find a subfolder "Plugins". Inside THAT folder, you'll find 2 files and another folder: vis_classic.dll, vis_classic.ini, and the folder vis_classic;
3. Copy those 3 items--vis_classic.dll, vis_classic.ini, and the folder vis_classic--into MusicBee's own Plugins folder. It should then show up in the choice of visualisers after restarting MusicBee.
I would recommend copying either my or KangNi's settings in the posts above so you've got a starting point for future tuning to your own preferences.
If you have more questions, feel free to post them. Enjoy!
I did not copy any settings from KangNi's nor sveakul, just try to see if the app will run, so far i can't see anything. i'm testing it on portable version, would anyone help.
-
I did not copy any settings from KangNi's nor sveakul, just try to see if the app will run, so far i can't see anything. i'm testing it on portable version, would anyone help.
What's the point of saying it's not working if you didn't follow the instructions? Sveakul clearly stated to copy his settings. Yes, he -recommends- using his settings, but if it's not working, why ask for help until you -try- his settings. Then if it still doesn't work, ask for help.
-
I did not copy any settings from KangNi's nor sveakul, just try to see if the app will run, so far i can't see anything. i'm testing it on portable version, would anyone help.
After you performed the install instructions you quoted, what did you do next? In Panels Configuration/Available Elements, the selection "visualiser: graphic" should appear. Grab that selection and drag it left to Bottom Panel or Right Sidebar for example. Then the "Visualiser" panel header/window should show up where you put it. Populate it with the spectrum analyzer by choosing its name "classic" from the View/Visualiser menu as shown below. Then right-click the window for a "Properties" GUI where you can adjust the settings without manually editing the ini. You will need to be using a recent version of MusicBee (3.3.7049.40483+) for this. Here it's working like a charm with MusicBee 3.3.7424 Portable, Windows 10 1909 x64. Rock stable.
(https://i.imgur.com/lHBr77T.png)
-
I did not copy any settings from KangNi's nor sveakul, just try to see if the app will run, so far i can't see anything. i'm testing it on portable version, would anyone help.
What's the point of saying it's not working if you didn't follow the instructions? Sveakul clearly stated to copy his settings. Yes, he -recommends- using his settings, but if it's not working, why ask for help until you -try- his settings. Then if it still doesn't work, ask for help.
Cuz i though that will come later on for cuztomization purposes not as required to get it work, but thanks to point it out.
-
I did not copy any settings from KangNi's nor sveakul, just try to see if the app will run, so far i can't see anything. i'm testing it on portable version, would anyone help.
After you performed the install instructions you quoted, what did you do next? In Panels Configuration/Available Elements, the selection "visualiser: graphic" should appear. Grab that selection and drag it left to Bottom Panel or Right Sidebar for example. Then the "Visualiser" panel header/window should show up where you put it. Populate it with the spectrum analyzer by choosing its name "classic" from the View/Visualiser menu as shown below. Then right-click the window for a "Properties" GUI where you can adjust the settings without manually editing the ini. You will need to be using a recent version of MusicBee (3.3.7049.40483+) for this. Here it's working like a charm with MusicBee 3.3.7424 Portable, Windows 10 1909 x64. Rock stable.
(https://i.imgur.com/lHBr77T.png)
Thanks much Sveakul
It is working just as you have instructed, thanks alot :) :) :)
-
Thanks much Sveakul
It is working just as you have instructed, thanks alot :) :) :)
Glad to hear it! I love that thing.
-
So I first installed MB a few years ago and then life seriously got in the way...
Due to the unfortunate global situation we are all now living in, I am spending more time at home and have been using MB nonstop and like everyone else who has come before me - absolutely love it.
When Winamp was king, that was my go to player and I seriously missed the spectrum analyzer when it went away.
Thank you to Sveakul, KangNi and the others who have made my MB the way I like it.
I have been able to add the classic analyzer to my my main Music page in the bottom right corner in the Right Side Bar and it works flawlessly.
My question is about the Now Playing Layout. Is there any way I can add the same analyzer to the same spot toward the bottom right either under or above the 'show track information panel'? I have used the built in analyze on that page but after being able to use the old Winamp version, would like to use that here as well.
Thank you in advance,
JJZ NYC
-
Glad you are enjoying the spectrum analyzer; from your post you're using it in the same location as I do.
Unfortunately, since the "Now Playing" panel uses its own distinct layout configuration, I don't think there's any way to add it there without a re-code by Steven. I too would like to see it be an option for replacing the "stock" visualiser that is selectable from the Now Playing header menu.
-
is it possible to make it smooth like foo_musical_spectrum https://www.youtube.com/watch?v=odUeUmKDPVA
-
is it possible to make it smooth like foo_musical_spectrum https://www.youtube.com/watch?v=odUeUmKDPVA
There's an almost endless amount of adjustments you can make to it via the Properties panel (right-click on display) and see the results in real-time: FFT, fall-off rate, peak. motion type, latency, bar width, etc. You just have to experiment. BTW foo_musical_spectrum is a little different in that it is displaying musical note/tone amplitudes so the behavior will not be totally identical due to how the bands are set up.
-
it's bugged for me https://ibb.co/VVYjGgk
https://ibb.co/8BkNvRb
-
What version and type (Installer, Windows Store, Portable) of MusicBee are you using? When you installed the Spectrum, did you put all 3 elements (2 files and a folder) into the MusicBee "plugins" directory? Did you be sure to whitelist all MusicBee folders in your antivirus application(s)?
-
portable 3.3.7455 P
also 3.3.7367 P
i don't use antivirus
-
If you installed it according to the instructions given, then I'm out of ideas why you're not seeing a populated Properties GUI. Running fine here with Windows 10 x64, MusicBee Portable 3.3.7455.
-
This plugin is crashing for me on the latest MB version. I see the visualizer graph/bar for a few seconds before MB hangs.
Here's my OS/MB info:
Windows 10 Version 2004 [10.0.19041.450]
MusicBee Version 3.3.7491
I have all the required redists and even tried building from source myself using the original code and new libraries, no luck at all. Any ideas?
-
I'm running it with MusicBee 3.4.7529 Portable and it's rock-stable--as it has been for me for the last couple of years now. Windows 10 1909 x64. What type of MB are you using--Installer, Portable, or Store? In the Plugins folder, do you have two files named "vis_classic.ini" and "vis_classic.dll, AND a subfolder named "vis_classic"? Is the entire MusicBee folder structure whitelisted in your antivirus?
If you're running other 3rd-party plugins, try disabling them one at a time and see if that has any effect. Of course the "video drivers" cliché comes to mind also.
-
I'm running it with MusicBee 3.4.7529 Portable and it's rock-stable--as it has been for me for the last couple of years now. Windows 10 1909 x64. What type of MB are you using--Installer, Portable, or Store? In the Plugins folder, do you have two files named "vis_classic.ini" and "vis_classic.dll, AND a subfolder named "vis_classic"? Is the entire MusicBee folder structure whitelisted in your antivirus?
If you're running other 3rd-party plugins, try disabling them one at a time and see if that has any effect. Of course the "video drivers" cliché comes to mind also.
Using latest MB installer version, I also have all those files in the correct place you listed. And I use Windows Defender with it whitelisted (although this shouldn't make a difference since the DLL is loaded, but it just makes MusicBee hang).
No third-party plugins, fresh MB install and I'm using Nvidia drivers 451.67.
Is there a crash log somewhere that I can upload here?
-
In MusicBee, drop Help/Support/View Error Log. If there is an entry there for when the crash occured (i.e. not the whole log), copy that entry to a post here and maybe Steven can check if it contains any data that may point to why it crashes for you.
Has worked so well for me across both win 7 and 10 I can't imagine it's a MusicBee issue, but the log entry may provide a clue as to a potential clash with something else in your setup.
-
In MusicBee, drop Help/Support/View Error Log. If there is an entry there for when the crash occured (i.e. not the whole log), copy that entry to a post here and maybe Steven can check if it contains any data that may point to why it crashes for you.
Has worked so well for me across both win 7 and 10 I can't imagine it's a MusicBee issue, but the log entry may provide a clue as to a potential clash with something else in your setup.
Seems like it's not a normal crash, it's crashing with windows and not internally (i.e. the app doesnt close instantly). I might have to use an x86 debugger to narrow it down.
-
I'm not able to resize it... I have the visualiser menu bar but can't move it up and down on this or any visualiser. I'm on version 3.4.7586. Anyone have any idea what could be wrong?
-
I'm not able to resize it... I have the visualiser menu bar but can't move it up and down on this or any visualiser. I'm on version 3.4.7586. Anyone have any idea what could be wrong?
Here on 3.4.7597 Portable, with Visualiser window at the bottom of the Right Sidebar, resizes vertically fine. What panel do you have it mounted on? Bottom Panel should be fine too, those are the two I have used. You have to "grab" the top border of the bar with the mouse at the spot where you suddenly see the up/down arrows when you mouse over the line, which can be hard to see depending on the skin.
-
Just found out that this plugin has been newly resurrected by raul as the "Classic Spectrum Analyzer!" From raul on the MusicBee Add-Ons section (https://getmusicbee.com/addons/visualizer/368/classic-spectrum-analyzer/ (https://getmusicbee.com/addons/visualizer/368/classic-spectrum-analyzer/)): "Accurate, detailed, customizable spectrum analyzer. I decided to resurrect this plug-in that I originally coded in 1998."
The new vis_classic.dll was modified 12/12/2021 and is 88,064 bytes; the one this thread was originally created about was modified 4/29/2007 and is 32,768 bytes, so there has definitely been a change. The latter was posted by "Prowler7" on forums.winamp.com on May 7, 2007. Whether "our" raul and Prowler7 are the same person, I do not know.
The settings/options all seem identical, so just replacing the dll and keeping your exsiting vis_classic.ini and its related profile folder should be all you need to do to "update." However, there are a lot more "stock" profiles (35) included so I recommend adding those as well--be sure not to overwrite whatever profile you are using now or you would need to start from scratch.
I welcome raul to post about any improvements he has made to the actual dll; I'm running it now with the new components and all seems stable.
-
Hi everyone,
So I'm basically posting this for anyone experiencing similar issues.
I did a fresh install of MB (portable since it and my library is on an external SSD), and only added a couple of lyric source plugins and a few visualizers.
This one didn't seem to work for me, I can open it and view it just fine when I click on MusicBee > View > Start Visualizer - however right clicking it creates a transparent context menu which turns black as soon as I click anywhere else on MB and then it just freezes.
(https://i.imgur.com/Mmg0GU5.png)
The music will keep playing just fine but I can't do anything until I force close MB.
I tried this method (https://getmusicbee.com/forum/index.php?topic=23345.msg174042#msg174042) but at first - and only at first - I got the same error as in this gif (https://getmusicbee.com/forum/index.php?topic=23345.msg157807#msg157807). After that I can add the panel anywhere and I don't see any class errors, however the right click just doesn't work anymore while the visualizer is in the (bottom atm) panel. It only shows if I have it in a dedicated visualizer tab, and as soon as it does show, transparently, anything else I do will crash MB.
I also removed all of my other visualizers in the meanwhile - the Arrange Panels window did freeze multiple times while I was trying it out, and I think removing other visualizers might have fixed this but I'm not 100% certain. It froze differently than the context menu glitch - as that one will cause the program to not respond according to Windows, and the Arrange Panels issue just caused MB to become unresponsive, however Windows felt like everything was fine :P
Then I randomly tried switching the visualizer in the bottom panel from CSA to some default one, and when I switched back to CSA - the right click was magically working, the properties window would appear, and I could even right click it in the Visualizer tab (however this tab looks weird now since the bottom panel is showing there too, albeit empty)
(https://i.imgur.com/XvXqYxu.png)
Also, I thought the Now Playing was mostly hardcoded but the bottom panel now shows there too, with a header unfortunately, but it's there nonetheless.
(https://i.imgur.com/2eg1n74.png)
So, in conclusion, I'm not sure what exactly I did but now it works and hopefully this helps someone with a similar problem ::)
-
Also, I thought the Now Playing was mostly hardcoded but the bottom panel now shows there too, with a header unfortunately, but it's there nonetheless.
click on word "visualizer" at panel header and select "hide panel header".
-
click on word "visualizer" at panel header and select "hide panel header".
Yep that did it, not sure how I missed it. Thanks!
Did you manage to get it working on your end?
-
Did you manage to get it working on your end?
yes, but all i've done is i've added 'visualizer: graphics' to the bottom panel. now this visualizer is working and configurable both at the bottom panel and in visualizer tab.
-
Ditto to Boroda's experience. Maybe trying to summarize the install will help those who have problems with this. As always, start with the latest version of MusicBee:
1. Close MusicBee. Download the plugin at https://getmusicbee.com/addons/visualizer/368/classic-spectrum-analyzer/ (https://getmusicbee.com/addons/visualizer/368/classic-spectrum-analyzer/), and extract both the DLL and the folder inside as-is into the MusicBee Plugins folder.
2. Start MusicBee. Go into Configure Layout/Arrange Panels, and look for the choice "visualiser:graphic" in the Available Elements list.
3. Pull the "visualiser:graphic" element over to the left side to either "bottom panel" or "top panel" or "right sidebar," and hit Save. then restart MusicBee.
4. Resize the visualiser window as desired, then drop its menu and choose "classic" from the choices. Restart MB just to be on the safe side.
5. Now if you right-click within the visualiser window you will see the settings menu for the analyser. These can be adjusted in real-time while music is playing. Choose a preset from the Options tab if desired.
-
Hello Sveakul,
did you were able to change the hight of the visualization panel?
I was unable to do that and got stucked with about fixed 250 px but i would like to set around 40 px.
Currently the visualization pannel eats up almost 1/3rd of my screen now :-\ ...
(https://i.imgur.com/hrOLGoe.jpg) (https://i.imgur.com/hrOLGoe.jpg)
Would be great if anyone could help here.
Greetings
Hello, i saw this in the first pages of this thread and i like how there's a frequency spectrum as well as the complete waveform of the audio under it that is probably able to click on it to playback to another part of the song.
I'm using spotify accent skin right now, is it possible to add theses 2 to this skin? Or do i have to change for another skin? What skin is it? How would i do this?
I looked around on the forum and it seems posts are really old or i need to read through many pages of updates and people thoughts...
Is there an updated simple way to add a freq analyser and waveform display to musicbee without having to go in the crazy intense visualizer tab which i'm not interested in?
Thanks :)
-
The frequency spectrum IS the "Classic Spectrum Analyzer" plugin and is not a skin-dependent item but can be added to the bottom panel by following the 5 steps in my Reply #91 post above. The colors and bar-forms are user selectable and can be straight black and white or "crazy intense" as you choose.
The effect just below that in the screenshot you posted is the completely separate progress "Wave Bar," which is built-in to MusicBee and can be selected by right-clicking the player control bar and choosing Panel Layout->Wave Bar. It's not a skin-dependent item either, although different skins can make it appear in different colors.