Default source scripts location on MacOS

Hello,

First post here, so sorry if I missed something obvious, but I can't find original scripts (Discogs and MusicBrainz) on MacOS. The source scripts directory (~/Library/Containers/app.mp3tag.Mp3tag/Data/Library/Application Support/Mp3tag/Sources) is empty by default it seems, so are they built-in in the application or is there a way to find them somewhere else? (I would like to try to customize the Discogs one, I see some posts from people saying they did that, so I assume the original must be made available somewhere :slight_smile: )

Thanks for your help

see here how to add custom tag sources on a Mac:

They're built-in in the application on macOS. You can still add custom tag sources (also for Discogs and MusicBrainz) via the option @ohrenkino pointed out.

Thanks for your reply Florian (and ohrenkino)
I understand how to use tag sources and how to add custom ones.
I would like to create my own by starting with the original which works 95% for me, and just modify a few fields I want to be different. I also looked at other Discogs custom scripts, but they are either not updated/maintained, and/or very complex to get started with and debug.
This recent post Discogs Release ID - Bundle with Field Composer and Performer suggested to me that at least some people have access to the original src to start developing on their own customization or am I mistaken?

Ok, I looked at Windows version and could find the original .src files that other posts mentioned.
One weird thing is that if I copy for example Discogs Release ID.src as is without any modification, just rename it to Discogs Release ID custom.src, I can see it added to the menu but when I run it I have a timeout when downloading the cover. Other tags are retrieved normally.
I have no problem with the embedded "Discogs Release ID" action, cover are downloaded normally.
@Florian any difference(s) I should be aware of between Mac version and Windows version when running source scripts?

Yes, the Windows version uses an image-caching proxy which I'm running and it's best to use the cover URLs directly for custom scripts.

So in json_foreach "images" you just use sayrest after selecting json_select "uri" instead of writing the proxy URL with the image path.

Thanks @Florian !
I could make it work and do the modification I wanted.