this post was submitted on 23 Oct 2023
1757 points (97.4% liked)
memes
10383 readers
2852 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to !politicalmemes@lemmy.world
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads
No advertisements or spam. This is an instance rule and the only way to live.
Sister communities
- !tenforward@lemmy.world : Star Trek memes, chat and shitposts
- !lemmyshitpost@lemmy.world : Lemmy Shitposts, anything and everything goes.
- !linuxmemes@lemmy.world : Linux themed memes
- !comicstrips@lemmy.world : for those who love comic stories.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Its a shame that you NEED a secondary lossy archive. You can only do true on-the-fly functionality when the syncing and music app are not seperate. Currently i use MusicBee for the transcoding and resilio for the syncing. I should propably switch over to syncthing too tho.
I have several terabytes of free space on my server so I have no issue sacrificing a few gigs to have the lossy archive be portable and independent of the music software.
It gives me the freedom to drop the lossy archive to whatever device I want (SyncThing to make it automatic and wireless) and use whatever music play I choose.
I could, and have thought about, switching the script to use hardlinks for the MP3s which means the only storage used is for the transcoded MP3s. Plus it would get rid of the requirement to sync any updated MP3s from the original archive to the lossy one, the hardlinks would just update with the original.
I think musicbee had a plugin that could do that, havnt had any quick success with it.