Enhanced media transcoding #2576
Replies: 4 comments 2 replies
-
MA uses ffmpeg |
Beta Was this translation helpful? Give feedback.
-
MKV is a container format for video files, Music Assistant is for audio/music only |
Beta Was this translation helpful? Give feedback.
-
OK, so neither of the above addresses the core point of improvements being possible to Music Assistant through investigating what CATT could offer, only objections. Maybe some constructive feedback could be attempted? |
Beta Was this translation helpful? Give feedback.
-
So that is video, MA is audio? MA already supports local file storage and streams to cast devices (as well a a good number of others). You mention in passing the "current limitations in Music Assistant Server" yet don't say what you think those are. Again MA's purpose is to stream high quality audio to audio devices. |
Beta Was this translation helpful? Give feedback.
-
Hi,
I've recently discovered CATT (https://github.com/skorokithakis/catt) and had started writing a web-based media service to allow Google Nest Hub devices to play media file from the local LAN.
Then my husband pointed me to Music Assistant Server and it looked like it could save a lot of time as it has support for both ChromeCast and local and SMB file storage.
The major stumbling blocks, unfortunately, have been:
CATT provides much wider support - based on ffmpeg, I believe.
With both Music Assistant Server and CATT written in python, I was wondering if there could be any synergistic development between the two projects that would overcome the above (and possibly other) current limitations in Music Assistant Server and speed its development.
Thanks,
-- Peter
Beta Was this translation helpful? Give feedback.
All reactions