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.
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.