Skip to main content ↑ ↓

Notice

If you are using a Hotmail or Outlook email address, please change it now, as Microsoft is rejecting all email from our service outright.
Topic: foo_vis_projectM (Read 5051 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

foo_vis_projectM

Hi guys!

Just ported projectM visualizer (aka Winamp MilkDrop) to foobar2000 visualization.

How to use?
  • Turn on "Edit layout" mode (View->Layout->Enable layout editing mode).
  • Right-click on some foobar2000 area, then select "Replace UI element..."
  • Select "projectM" from "Playback Visualization" section.
  • Turn off "Edit layout" mode (View->Layout->Enable layout editing mode).

Re: foo_vis_projectM

Reply #1 –
Installed and working, seems stable, looks great, thanks, good job. Right click changes to the next visualisation but I couldn't find any settings / parameters / options.
Quis custodiet ipsos custodes?  ;~)

Re: foo_vis_projectM

Reply #3 –
Nice work! It would be glad to see Columns UI support for inserting the panel in layout.

Re: foo_vis_projectM

Reply #4 –
Quote from: LUR on
Nice work! It would be glad to see Columns UI support for inserting the panel in layout.
It may be inserted in any place in the layout.
Read first post in topic)

Re: foo_vis_projectM

Reply #6 –
And what do i need to do for this?
I've found this request.

Re: foo_vis_projectM

Reply #7 –
Great idea for a component, thanks for making it. Unfortunately, foobar2000 crashed for me as soon as I ran it. I've attached crashdumps to my post.

I found a Windows binary for projectM sometime last year that never worked for me either. I fear it may be my antiquated graphics hardware that is the cause (onboard Intel HD, circa 2012 if that helps.) Milkdrop runs happily in Shpeck, though I appreciate they're not entirely the same thing. I would prefer to use this if at all possible though...

Re: foo_vis_projectM

Reply #8 –
There should be some crash reports from me in the database, too. I really like your efforts. Would be nice if you could make the shortcuts work, too. Thanks for your work!

Re: foo_vis_projectM

Reply #10 –
Quote from: The Link on
There should be some crash reports from me in the database, too. I really like your efforts. Would be nice if you could make the shortcuts work, too. Thanks for your work!
Thanks for feedback! Is it ok for you to try to test official version from steam too?

Re: foo_vis_projectM

Reply #11 –
Installed the Steam standalone version, went ok. Toggles to fullscreen but not back to a window? Toggles to both displays, but not back again, does go to single screen with ctrl-f? Menu text doesn't scale down in window view. Everything else seems functional, thanks again.
Quis custodiet ipsos custodes?  ;~)

Re: foo_vis_projectM

Reply #12 –
I hope the report by 2tec is sufficient as I don't have steam installed.

Re: foo_vis_projectM

Reply #13 –
Quote from: djdron on
And what do i need to do for this?
I've found this request.
When you develop panel for Default UI you probably inherit ui_element_instance class from foobar2000 SDK.
When you develop panel for Columns UI you inherit uie::container_ui_extension (window_helper.h) or so from its own SDK
All panels that works both in DUI and CUI implement both of that interfaces

Re: foo_vis_projectM

Reply #14 –
Quote from: The Link on
I hope the report by 2tec is sufficient as I don't have steam installed.
No) I mean test crashes on your hardware with official projectM version.
There is not only steam version.
I only develop plugin for foobar2000.
2tec do you have crashes?

Re: foo_vis_projectM

Reply #15 –
Quote from: LUR on
All panels that works both in DUI and CUI implement both of that interfaces
Ok.
Is there a reason why CUI is unable to insert DUI elements?
And why i need to integrate one more SDK.
I think we all need to like this post.

Re: foo_vis_projectM

Reply #16 –
No, seems stable on my Win10 system
Quis custodiet ipsos custodes?  ;~)

Re: foo_vis_projectM

Reply #17 –
Quote from: djdron on
Quote from: LUR on
All panels that works both in DUI and CUI implement both of that interfaces
Ok.
Is there a reason why CUI is unable to insert DUI elements?
And why i need to integrate one more SDK.
I think we all need to like this post.
No, that's not the point. The fact is that almost all the "DUI only panels" are developed by the author of the foobar2000 and have a closed source code, so they cannot be modified by anyone else to support the CUI. But almost all panels developed by third-party developers that I have come across personally support both interfaces. Simply by deciding not to include support for CUI in your component, you thereby deprive a very large part of the player's audience of the opportunity to use a modern visualizer.

Re: foo_vis_projectM

Reply #18 –
Quote from: LUR on
Simply by deciding not to include support for CUI in your component, you thereby deprive a very large part of the player's audience of the opportunity to use a modern visualizer.
BTW, do you have projectM in foobar2000 menu -> View -> Visualizations ?

Re: foo_vis_projectM

Reply #19 –
Quote from: djdron on
Quote from: LUR on
Simply by deciding not to include support for CUI in your component, you thereby deprive a very large part of the player's audience of the opportunity to use a modern visualizer.
BTW, do you have projectM in foobar2000 menu -> View -> Visualizations ?
Yes. But it opens like a separate window. CUI support is required precisely for embedding the panel into the foobar2000 window for layout editing.

Re: foo_vis_projectM

Reply #20 –
Quote from: LUR on
Simply by deciding not to include support for CUI in your component, you thereby deprive a very large part of the player's audience of the opportunity to use a modern visualizer.
Development has to start somewhere. Something is better than nothing.



Quis custodiet ipsos custodes?  ;~)

Re: foo_vis_projectM

Reply #21 –
Quote from: 2tec on
Quote from: LUR on
Simply by deciding not to include support for CUI in your component, you thereby deprive a very large part of the player's audience of the opportunity to use a modern visualizer.
Development has to start somewhere. Something is better than nothing.
I totally agree. it's just a suggestion for the future. Moreover, at the very beginning of development, it is possible to expand the audience for everyday testing.

Re: foo_vis_projectM

Reply #22 –
Quote from: djdron on
Quote from: iridescentaudio on
Milkdrop runs happily in Shpeck, though I appreciate they're not entirely the same thing. I would prefer to use this if at all possible though...
Could you try to launch official projectM version from steam on this hardware?

I didn't realise there had been a more formal release of project M on Windows, that's good to see. Alas, it behaves exactly the same way as the other standalone binary I had; a window opens for half a second and immediately exits. No error message is displayed, so I'm left completely in the dark. At least this should be reassuring that your component is probably not responsible, though if you (or anyone) has any pointers for me I'd greatly appreciate it. (most likely pointer: buy a graphics card)

Quote from: LUR on
Simply by deciding not to include support for CUI in your component, you thereby deprive a very large part of the player's audience of the opportunity to use a modern visualizer.

I realise it may not be ideal for your purposes, but you could create a custom button and put that somewhere in your interface, since that way it still opens in DUI.

Re: foo_vis_projectM

Reply #23 –
the Stream app full screen toggle is working, it was just me or my settings
Quis custodiet ipsos custodes?  ;~)
 
SimplePortal 1.0.0 RC1 © 2008-2021