41–50 of 85 posts
This is absolutely amazing— much more polished than the alternatives—it feels like christmas.
Now I can't wait to contribute a pull request :) Thank you so much!
Earlier quoted context omitted.
Not currently; the only client right now is a native Android app[1]. However, the server[2] uses vanilla HTTP (for audio) and WebSockets (for data and eventing), so it should be relatively straight forward to build a web frontend. [1] https://github.com/clangen/musikcube/tree/master/src/musikdr... [2] https://github.com/clangen/musikcube/wiki/remote-api-documen...
Even with a web frontend, I'm not clear on how I could get the audio from, say, youtube to go over the websocket instead of to the typical playback device. With something like Pulseaudio, I believe it's possible to stream to a remote host, but then musikcube would need a pulseaudio compatibility layer
Then a web frontend could be served served audio over HTTP and play that back on the remote client.
Pulseaudio is system based audio, whereas here we are just talking about local audio to the musickube app.
Interesting idea to add pulseaudio compatability though..
Please could someone explain why it's necessary to use 24bit/192k - I thought due to Nyquist/Shannon theory that 192k was overkill. In fact, doesn't it create more ear strain listening to higher frequency sample rates?
Play lower and higher quality encodings through a decent size of sound system (2kW upwards) to discover what all those frequencies do
Anyone knows of a cli app that can play local files as well as youtube?
Too bad it doesn't do youtube. Anyone knows of a cli app that can play local files as well as youtube?
Yes, I know. Thats probably not the devs bad, but Spotify makeing it impossible to write a legal integration. Happy new DRM world.
Please could someone explain why it's necessary to use 24bit/192k - I thought due to Nyquist/Shannon theory that 192k was overkill. In fact, doesn't it create more ear strain listening to higher frequency sample rates?
For editing and production, more bits per sample and more samples per second make it possible to mix sources without reducing quality of the final output.
There is no advantage to that final output being 24/192, or 20/88.
There is no ear strain that comes from higher sample rates, though.