[GH-ISSUE #605] [Feature Request] add/write file source to metadata #1831

Open
opened 2026-03-13 19:35:10 +03:00 by kerem · 3 comments
Owner

Originally created by @Snapuman on GitHub (Mar 6, 2026).
Original GitHub issue: https://github.com/afkarxyz/SpotiFLAC/issues/605

[Feature Request]

Description

pls add/write the actually used source (qobuz/tidal/amzn/deezer) for a file to the metadata.

-> e.g. as addition to comment or description field like
comment=https://github.com/afkarxyz/SpotiFLAC src: tidal
description=https://github.com/afkarxyz/SpotiFLAC src: tidal

or as FF Vorbis Comment for FLAC files
SOURCE=tidal

Use Case

For later identifying when using auto-source

That would be very awesome - especially for hi-res files with setting of auto source - to identify quality differences between sources.
Also in general for later more convenient identifying which source works better.

Originally created by @Snapuman on GitHub (Mar 6, 2026). Original GitHub issue: https://github.com/afkarxyz/SpotiFLAC/issues/605 ### [Feature Request] #### Description pls add/write the actually used source (qobuz/tidal/amzn/deezer) for a file to the metadata. -> e.g. as addition to comment or description field like comment=https://github.com/afkarxyz/SpotiFLAC **src: tidal** description=https://github.com/afkarxyz/SpotiFLAC **src: tidal** or as FF **Vo**rbis **C**omment for FLAC files SOURCE=tidal #### Use Case For later identifying when using auto-source That would be very awesome - especially for hi-res files with setting of auto source - to identify quality differences between sources. Also in general for later more convenient identifying which source works better.
Author
Owner

@mahoganyprogrammer commented on GitHub (Mar 6, 2026):

@Snapuman workaround, choose one source and download twice

<!-- gh-comment-id:4012758838 --> @mahoganyprogrammer commented on GitHub (Mar 6, 2026): @Snapuman workaround, choose one source and download twice
Author
Owner

@Snapuman commented on GitHub (Mar 7, 2026):

@mahoganyprogrammer sure, I can also check debug logs where it says which source succeed...
I even could export the log and write a script to do this more automatic afterwards.

But why not implement directly when information is already there - just one more thing to write in the metadata. :)
Hence this is a feature request :)

<!-- gh-comment-id:4016349847 --> @Snapuman commented on GitHub (Mar 7, 2026): @mahoganyprogrammer sure, I can also check debug logs where it says which source succeed... I even could export the log and write a script to do this more automatic afterwards. But why not implement directly when information is already there - just one more thing to write in the metadata. :) Hence this is a feature request :)
Author
Owner

@mahoganyprogrammer commented on GitHub (Mar 9, 2026):

@Snapuman workaround till its added. for example source can be added as comment. instead of watermark of repo

<!-- gh-comment-id:4020437085 --> @mahoganyprogrammer commented on GitHub (Mar 9, 2026): @Snapuman workaround till its added. for example source can be added as comment. instead of watermark of repo
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/SpotiFLAC#1831
No description provided.