Is there a way to deactivate multithreading in Picard?
Could be with secret command line option, a config file, a global Python option, or anything.
Or a command line solution for scanning (fpcalc?) CD tracks + submitting to release recordings?
It would be helpful for me because, at the moment, I have to manually drop CD tracks (virtual files) one by one in the left-hand pane and then scan them manually Ctrl+Y one by one for AcoustID.
Because I work directly on CD in CD drive to submit AcoustID without ripping.
Update
I am also exploring the fpcalc (from libchromaprint-tools) command line method:
This does scan tracks sequencially:
/run/user/1000/gvfs/cdda:host=sr0$
for i in {1..20}; do fpcalc Track\ $i.wav; done
But there are no options to submit AcoustID to MB release recordings, yet.
For the fpcalc approach, do you have a list of recording MBIDs, or only the release MBID? I don’t see release MBIDs mentioned in the API docs at Web Service | AcoustID.
I haven’t used it before, but https://github.com/beetbox/pyacoustid looks like it can submit AcoustIDs. If you have recording MBIDs, maybe you could do something like this (from a new script in the same directory as the pyacoustid repository):
I will indeed have to call MB web service first to get recording MBID from release MBID.
I have never written or understood Python, yet.
I will keep this in mind and I will try, someday!
And USER_KEY seems to be the user key I already have in Picard options
Alternatively, in case I don’t manage to make or debug Python script (because I don’t know it at all), I could probably use curl, httpie or wget in a bash script (I have them 3 in my Debian 10 Xfce Linux, don’t know which one was pre-installed).
Maybe it would be hyper tedious but at least I know the syntax a little bit.
Run Picard from source and edit the file that creates the threadpool to change the size to 1. This should serialise all the disk I/O.
You might want to consider copying the files from CD to a temp directory first and then running acoustid on the disk copy - this is likely to be a lot faster overall.
To do the acoustid in batch, the steps would be:
Run fpcalc on the file.
Associate the file with a MB recording
Submit the acoustid
The first and last of these are easy. The second isn’t as it requires human judgement and a decent UI - which Picard provides. IMO the best way to do this might be:
Copy CD to a temp directory
Tag the files in the temp directory with Picard
Submit the acoustids
Delete the files.
Only you will be able to decide whether this is faster overall than your current workflow.