mirror of
https://github.com/koel/koel.git
synced 2026-04-26 09:15:59 +03:00
[GH-ISSUE #466] Music Transcoding & Storage #327
Labels
No labels
Authentication
Dependencies
Documentation
Feature Request
Flac
Help Wanted
Installation/Setup
Integration
Mobile
PR Welcome
Pending Release
Performance
Playlist
S3
Search
Sync
[Pri] Low
[Pri] Normal
[Status] Keep Open
[Status] Needs Author Reply
[Status] Needs Review
[Status] Stale
[Status] Will Implement
[Type] Blessed
[Type] Bug
[Type] Duplicate
[Type] Enhancement
[Type] Help Request
[Type] Question
[Type] Task
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/koel-koel#327
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ArcheTwist on GitHub (Sep 26, 2016).
Original GitHub issue: https://github.com/koel/koel/issues/466
I was wondering if you could incorporate music transcoding for mobile devices to help save data and bandwidth.
Also, with Koel is it possible to mount a drive like Amazon Cloud Drive to a VPS and have Koel sync through that directory? I think mounting with FUSE it's only owned by root though it might be owned by the Koel user if I mount it on the Koel user.
Just out of curiousity Phanan, what sort of setups have you seen using Koel? Like storage sizes, RAM sizes and CPU amounts? I am just curious to know what I need to run. What is the most resourcive intensive part of this application?
@phanan commented on GitHub (Sep 27, 2016):
Music transcoding is currently available for FLAC only. Actually, @alex-phillips has implemented the API support for standard audio types transcoding, but Koel's client doesn't support it yet. Maybe some time in the future.
For your second question, I've not tried such an installation, but my gut feeling is yes. As long as the directory/volume is accessible and readable by Koel, I don't see why not. Performance, though, can be an issue, for example when scanning. If you use AWS S3, koel-aws might be a better solution.
For the last question, I don't have an exact idea of what sort of setups is there in the wild obviously ;) but here is my personal setup:
The most resource intensive part would be media scanning. Koel uses progressive scan to minimize memory overhead, though, and you can always watch and sync on the fly with
inotifywaitinstead of running full scans. You can also add swap files for extra virtual memory.@alfureu commented on GitHub (Jun 1, 2019):
I would also vote for transcoding options, especially as many users would love to listen to music on their phones, and there are great codecs avaialble, e.g. Opus
@FluffyDiscord commented on GitHub (Feb 7, 2026):
@phanan transcoding to Opus is crucial for me, is thwt out of question? Opus can be transcoded realtime AFAIK
@phanan commented on GitHub (Feb 7, 2026):
@FluffyDiscord Koel supports Opus.