Live data from Hacker News

Musikcube, a cross-platform, terminal-based library, player and server

github.com

11–20 of 23 posts

Re: Musikcube, a cross-platform, terminal-based library, player and server

#11

I tried Musikcube a week ago and it's pretty good aside from that, though once it crashed for some reason. Looks more polished than most TUI applications, though. Nothing can replace Clementine for me. It can stop playback automatically once a song is finished playing. Imho this is the best feature since the invention of playlists and I don't know why nobody else implements this (except for I think foobar2000 but tha…

How do you mean “stop a song playing automatically”?

I always assumed that was the default behaviour of music players and that Spotify was the outlier on continuing to play related songs after your playlist had ended (it being a “feature” of Spotify).

Re: Musikcube, a cross-platform, terminal-based library, player and server

#13
post #11

I tried Musikcube a week ago and it's pretty good aside from that, though once it crashed for some reason. Looks more polished than most TUI applications, though. Nothing can replace Clementine for me. It can stop playback automatically once a song is finished playing. Imho this is the best feature since the invention of playlists and I don't know why nobody else implements this (except for I think foobar2000 but tha…

How do you mean “stop a song playing automatically”? I always assumed that was the default behaviour of music players and that Spotify was the outlier on continuing to play related songs after your playlist had ended (it being a “feature” of Spotify).

They probably meant a function where the playback stops after the current song.

I know this from my podcast app with a "Zzzz" Icon where you can stop playback after the current episode or after a certain time (e.g. 15 minutes).

Re: Musikcube, a cross-platform, terminal-based library, player and server

#14
post #4
post #2

Reminds me a lot of the mpd (music player daemon) ecosystem. Some mpd clients look just like that: https://www.musicpd.org/clients/

and I wonder what the advantage is vs. MDP. It was a pretty ok "product" when I ran it 10years ago on an old Pentium III notebook with 256MB of memory. I think it still would work if I booted it now.

The "D" in MPD stands for daemon — so typically it is something where you have a "jukebox"-style computer hooked up to some sound system and multiple (network) clients that can control the playlist etc. MPD is basically a audio player with playlist managment that exposes all controls via network API.

The client could be an app on your phone, or a web-frontend served from that jukebox server etc.

We have a box like that at work, where multiple people are meant to add music, stop and queue it without having to stand up.

Re: Musikcube, a cross-platform, terminal-based library, player and server

#15
Hmm, wasn't there a music player called musickube or musikube or similar? I remember this being very lightweight and one of the only decent ones back before switching to Grooveshark. Can't find it when searching now, probably I'm getting the ck wrong and its SEO must be terrible compared to the various companies with names like this.

Re: Musikcube, a cross-platform, terminal-based library, player and server

#16
post #15

Hmm, wasn't there a music player called musickube or musikube or similar? I remember this being very lightweight and one of the only decent ones back before switching to Grooveshark. Can't find it when searching now, probably I'm getting the ck wrong and its SEO must be terrible compared to the various companies with names like this.

it's by the same developer Casey Langen. Instead of creating another win32 UI app he went cross-platform and console-based.

The original musikcube was an eyeopener to me, demonstrating sqlites performance.

Re: Musikcube, a cross-platform, terminal-based library, player and server

#17
post #11

I tried Musikcube a week ago and it's pretty good aside from that, though once it crashed for some reason. Looks more polished than most TUI applications, though. Nothing can replace Clementine for me. It can stop playback automatically once a song is finished playing. Imho this is the best feature since the invention of playlists and I don't know why nobody else implements this (except for I think foobar2000 but tha…

How do you mean “stop a song playing automatically”? I always assumed that was the default behaviour of music players and that Spotify was the outlier on continuing to play related songs after your playlist had ended (it being a “feature” of Spotify).

It's an old school playlist management feature from the Amarok Era, it's for when you're thinking "this is the last song I'm listening to, but I do want to finish it". Once that song gets hit in your playlist, it'll automatically stop playback at the end of it.

And by playlist I more mean active queue. Making it sound complex but it's a very intuitive UI if you try it out.

The whole design of Amarok/Clementine is so far ahead of modern players like Spotify, just being able to browse songs off your play list while keeping your playlist visible would be nice, but stuff like "queue as next" vs "queue as last" is awesome. These days Electron UIs confuse me so much I'm not sure what I can even drag and drop.

Re: Musikcube, a cross-platform, terminal-based library, player and server

#18
post #17
post #11

Earlier quoted context omitted.

How do you mean “stop a song playing automatically”? I always assumed that was the default behaviour of music players and that Spotify was the outlier on continuing to play related songs after your playlist had ended (it being a “feature” of Spotify).

It's an old school playlist management feature from the Amarok Era, it's for when you're thinking "this is the last song I'm listening to, but I do want to finish it". Once that song gets hit in your playlist, it'll automatically stop playback at the end of it. And by playlist I more mean active queue. Making it sound complex but it's a very intuitive UI if you try it out. The whole design of Amarok/Clementine is so…

> It's an old school playlist management feature from the Amarok Era, it's for when you're thinking "this is the last song I'm listening to, but I do want to finish it". Once that song gets hit in your playlist, it'll automatically stop playback at the end of it.

That's just the "play once" option that exists in 99% of music player's, isn't it? Supported by all default music players on Windows, macOS, Android and iOS, as far as I can see.

Re: Musikcube, a cross-platform, terminal-based library, player and server

#19
I use Musikcube a lot, it works great on macOS and Linux, and is snappy even on very cheap or old systems. It has very good mouse support (if your terminal emulator supports it), it's the first time I saw a TUI app with a right click menu, or that you can scroll through.

My one major complaint is that there is no way I know of to import/export playlists: https://github.com/clangen/musikcube/issues/141

Another similar program I use when I am unable or unwilling to install musikcube for some reason is cmus: https://cmus.github.io/

Re: Musikcube, a cross-platform, terminal-based library, player and server

#20
post #18
post #17

Earlier quoted context omitted.

It's an old school playlist management feature from the Amarok Era, it's for when you're thinking "this is the last song I'm listening to, but I do want to finish it". Once that song gets hit in your playlist, it'll automatically stop playback at the end of it. And by playlist I more mean active queue. Making it sound complex but it's a very intuitive UI if you try it out. The whole design of Amarok/Clementine is so…

> It's an old school playlist management feature from the Amarok Era, it's for when you're thinking "this is the last song I'm listening to, but I do want to finish it". Once that song gets hit in your playlist, it'll automatically stop playback at the end of it. That's just the "play once" option that exists in 99% of music player's, isn't it? Supported by all default music players on Windows, macOS, Android and iOS…

What I mean is basically like a delayed "pause" button that triggers once the currently playing song ends. It can be set during playback and doesn't affect any other playback setting or queued songs.

The alternative is either abruptly stopping playback or staring at the progress bar and waiting a couple minutes for the right moment to click a button. In other words, it's one of those simple but tedious things you'd want to automate.

I wish every standard player had this, but as far as I have seen that is not the case.

Post reply on HN