lofi VS projectm

Ran it on a "real" OSS project of mine (https://github.com/dvx/lofi/), and it was stuck at 99% loading for about 30 minutes. Then, when it finally parsed the codebase, when asked anything it always returns "Error: Internal error while locating sources."

At one point, this random prompt popped up: https://imgur.com/a/mYeluaU —what's "Onboard?"

In readme[0] small footprint named as an advantage instead:

> Design goals

> ≤ 100MB memory footprint

[0] https://github.com/dvx/lofi#design-goals

I do think that podcasting is ripe for disruption and a great candidate for a "super app" that can end up being people's go-to to listen to podcasts and be exposed to new ones.

Spotify did literally nothing to actually support podcasting as another vertical--which it 100% is. Podcasting isn't just "music" and it's a profound misunderstanding to believe that it is. It's honestly embarrassing to think that all they had to do is buy out Joe Rogan. To this day, I mostly listen to podcasts on YouTube. Spotify doesn't have transcripts, scrubbing, chapters, discoverability, "shorts," etc., etc. I run an open source Spotify player[1] and their API doesn't even have a podcast type/category (lol, they are actually "music videos" in the JSON payload). It's like podcasts don't even exist.

If anyone wants to build a podcasting platform, hit me up :)

[1] https://github.com/dvx/lofi/

Don't mean to hijack this thread, but I built out a mini Spotify player with visualization support: https://github.com/dvx/lofi

Even had a few folks contribute a couple of neat visualizations :)

Release notes are available here.

This is awesome! Will try to add it to the next release of https://github.com/dvx/lofi

In the words of Jerry Seinfeld, what's the deal with binary symlinking not working? Example, the ProjectM visualizer I downloaded and moved to a more static directory. It runs fine in that directory but when I symlink it via KDE's Dolphin by drag/dropping to my desktop, it does nothing. Same when I try to make a shortcut in KDE's application launcher. Why is it so to be like that for when you do it to get your shortcut?

I think this is the spiritual successor to Winamp's visualiser, ProjectM:

https://github.com/projectM-visualizer/projectm

If you're referring this this ProjectM, then it looks like Steam might be the best option.

It can also be used standalone from this github

Here you go, open-source, stand-alone version of the winamp visualiser: https://github.com/projectM-visualizer/projectm

You might give Milkdrop a try. It started as a Winamp visualization plugin. It has its own scripting language and a ton of presets you can poke at to figure out how things work. I'm not sure what state Winamp is in these days, but Milkdrop has been ported to work as a Foobar2000 plugin called ProjectM. It looks like there's also a standalone version now, too: https://github.com/projectM-visualizer/projectm