If you do get it working and the data is actually embedded in the file itself, I might ask for you to send me the file through CryptDrive or something so I can download it and inspect the formatting! My understanding is that there is almost definitely a way to encode the information, but making it efficient and ID3-compatible while also allowing a program to read it is probably the big thing.
The idea originally came from the fact that my husband experiences synesthesia, so songs that I think flow naturally from one to the next can be jarring to him because of a sudden transition of color or texture. Since that's not an experience I share I wanted a way for him to document that info in the metadata so I can sort by it and make better playlists for us to listen to on long drives :)
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
ninetydegrees![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png){kind=small}
(no subject)
If you do get it working and the data is actually embedded in the file itself, I might ask for you to send me the file through CryptDrive or something so I can download it and inspect the formatting! My understanding is that there is almost definitely a way to encode the information, but making it efficient and ID3-compatible while also allowing a program to read it is probably the big thing.
The idea originally came from the fact that my husband experiences synesthesia, so songs that I think flow naturally from one to the next can be jarring to him because of a sudden transition of color or texture. Since that's not an experience I share I wanted a way for him to document that info in the metadata so I can sort by it and make better playlists for us to listen to on long drives :)