Just what I need. Overall, my family has hundreds of CD and it's really tedious getting the right metadata tags. Picard looks really easy to deploy and perhaps more importantly, easy to use too. Definitely installing on the media server tonight!
It's awesome! Just check what it's assigning, and make sure it's the right stuff. Once in a while you might find a flyer where the data just wasn't analyzed properly.
If it were only that simple...for the average Joe it may be, just run and it will be perfect. However for the audiophile or perfectionist this won't do. For example you got an album from the LP of that artist. It happens that ABP just says it's the CD version. or selects another version of the album. If you got a remastered version, well it may even get trickier etc. It's just not as simple, I wish it was, but it's not just click and done.
I would expect an audiophile to definitely want more control over anything to do with their music collection, so I think for a lot of them this may not be the best option, but you can also review everything before any changes are made, and if you know it's selected the wrong album / version, then just deny that item,a nd go back to fix it manually later. The things it does match correctly could still save soem time and effort though.
I use this extensively. You have only scratched the surface of what it can do. You set up a custom folder structure and setup custom metadata tags that you can add. You can also lookup a cd with the cd lookup option or lookup a eac log file. It can take quite some time to get a music collection into a reasonable order. You can run it as a standard Linux, Windows or mac install.
100%. My goal was to show people they can run it on their headless systems with very little effort. But absolutely, this software is so extremely powerful and amazing!
I love your videos; they've certainly opened my eyes to quite a few possibilities, but why on earth would you go through the trouble to run an ephemeral application like Picard in a Docker container? I have a collection not too dissimilar to yours and served by Navidrome. I do have my audio being served up to my network via NFS, but any method of mounting that filesystem to a Windows or Linux box will do. Then, I run Picard natively on my workstation, do my tagging, and close it out. It just seems like a *ton* of overhead for what appears (to me) to be effectively no benefit. Can you enlighten me as to why running this in Docker makes sense?
Totally understand your perspective and method for doing this. My purpose is to keep my desktop / daily machine as clean as I can. This is a tool I'll use every few months at most, so just one more thing to clutter up my main machine. Figured others might like this option as well.
Think I'm gonna need to check this one out. Ended up doing data recovery on a failed drive and it restored the music, but all with hexidecimal names. Hoping this can rename and organise my collection.
How would you use this for a Jellyfin music collection? I always have trouble of cover art images being multiplicated so much that you can't see the album cover art at all after a while. I know it was an issue some time back, but hoping this option may make metadata gathering better for my Jellyfin instance, also running in Docker.
So, jellyfin may be keeping multiple copies, or doesn't know how to group things using just the tags. You may need a more folder structure organization for Jellyfin. This wouldn't move items around, I think for that you'd want something like Lidarr, which will organize your music in a way that Jellyfin can understand and work better with.
How would you compare the meta-data input feature in this app to the same features in Beets-CLI? I REALLY liked the Beets package when you made that video a while back. Cleaned up a couple hundred GBs of music in a couple afternoons!
I believe both are based on the same engine, so I imagine you'll get similar results. This package, being more up to date than the Beets install I did, though, I believe made MBP able to identify a few that Beets missed, or couldn't at the time. Both are excellent, just no update to the Beets project, which still requires a fairly old version of python to run.
I'm actually building a full Baby grand digital piano now. I'm actually refurbing a baby grand that the internals were so messed up it would have been a complete rebuild, so instead I'm refurbing the cabinet and will have a DAW and full 88 key weighted controller, and speaker system setup. I'll try to get some photos and then maybe cover some great open source DAWs when I'm done.
@@ui4lhI do a couple of things. First, I use a copy of my library to work out all the kinks in the Picard configuration. I then disarm Picard and tell it not to save the tags automatically or move files to my master music folder. Finally, once I am more comfortable with the configuration, I enable more of the automation. You can have it attempt to cluster files to get a better picture of which release of an album is being requested.
I've had good results. There is a warning to do small batches at a time. I went the extra mile and made a backup of the original files then ran it in batches of 20. Some files you have to scan multiple times. If I don't like what I see I don't save it. So far 80% accuracy. The rest I did manually
Just what I need. Overall, my family has hundreds of CD and it's really tedious getting the right metadata tags. Picard looks really easy to deploy and perhaps more importantly, easy to use too. Definitely installing on the media server tonight!
It's awesome! Just check what it's assigning, and make sure it's the right stuff. Once in a while you might find a flyer where the data just wasn't analyzed properly.
If it were only that simple...for the average Joe it may be, just run and it will be perfect. However for the audiophile or perfectionist this won't do. For example you got an album from the LP of that artist. It happens that ABP just says it's the CD version. or selects another version of the album. If you got a remastered version, well it may even get trickier etc. It's just not as simple, I wish it was, but it's not just click and done.
I would expect an audiophile to definitely want more control over anything to do with their music collection, so I think for a lot of them this may not be the best option, but you can also review everything before any changes are made, and if you know it's selected the wrong album / version, then just deny that item,a nd go back to fix it manually later. The things it does match correctly could still save soem time and effort though.
Now combine with finamp!
Might be cool. I use Navidrome, and love it.
I use this extensively. You have only scratched the surface of what it can do. You set up a custom folder structure and setup custom metadata tags that you can add.
You can also lookup a cd with the cd lookup option or lookup a eac log file.
It can take quite some time to get a music collection into a reasonable order.
You can run it as a standard Linux, Windows or mac install.
100%. My goal was to show people they can run it on their headless systems with very little effort. But absolutely, this software is so extremely powerful and amazing!
I love your videos; they've certainly opened my eyes to quite a few possibilities, but why on earth would you go through the trouble to run an ephemeral application like Picard in a Docker container?
I have a collection not too dissimilar to yours and served by Navidrome. I do have my audio being served up to my network via NFS, but any method of mounting that filesystem to a Windows or Linux box will do. Then, I run Picard natively on my workstation, do my tagging, and close it out. It just seems like a *ton* of overhead for what appears (to me) to be effectively no benefit.
Can you enlighten me as to why running this in Docker makes sense?
Totally understand your perspective and method for doing this. My purpose is to keep my desktop / daily machine as clean as I can. This is a tool I'll use every few months at most, so just one more thing to clutter up my main machine. Figured others might like this option as well.
Think I'm gonna need to check this one out. Ended up doing data recovery on a failed drive and it restored the music, but all with hexidecimal names. Hoping this can rename and organise my collection.
I hope so too. It's worth a shot for sure.
How would you use this for a Jellyfin music collection? I always have trouble of cover art images being multiplicated so much that you can't see the album cover art at all after a while. I know it was an issue some time back, but hoping this option may make metadata gathering better for my Jellyfin instance, also running in Docker.
So, jellyfin may be keeping multiple copies, or doesn't know how to group things using just the tags. You may need a more folder structure organization for Jellyfin. This wouldn't move items around, I think for that you'd want something like Lidarr, which will organize your music in a way that Jellyfin can understand and work better with.
How would you compare the meta-data input feature in this app to the same features in Beets-CLI? I REALLY liked the Beets package when you made that video a while back. Cleaned up a couple hundred GBs of music in a couple afternoons!
I believe both are based on the same engine, so I imagine you'll get similar results. This package, being more up to date than the Beets install I did, though, I believe made MBP able to identify a few that Beets missed, or couldn't at the time. Both are excellent, just no update to the Beets project, which still requires a fairly old version of python to run.
Please show some Digital Piano Projects ;)
I'm actually building a full Baby grand digital piano now. I'm actually refurbing a baby grand that the internals were so messed up it would have been a complete rebuild, so instead I'm refurbing the cabinet and will have a DAW and full 88 key weighted controller, and speaker system setup. I'll try to get some photos and then maybe cover some great open source DAWs when I'm done.
Hey look it's the software that so badly mangled my mp3 collection that I gave up on keeping my own decades old music library.
Really? I'm sorry that happened. I've been pretty fortunate so far as it's done really well getting my collection cleaned up and better.
I have tried to use it twice and the 2 times, it has f#&$ up twice my library :/ I gave up on it
@@ui4lhI do a couple of things. First, I use a copy of my library to work out all the kinks in the Picard configuration. I then disarm Picard and tell it not to save the tags automatically or move files to my master music folder. Finally, once I am more comfortable with the configuration, I enable more of the automation. You can have it attempt to cluster files to get a better picture of which release of an album is being requested.
I've had good results. There is a warning to do small batches at a time. I went the extra mile and made a backup of the original files then ran it in batches of 20. Some files you have to scan multiple times. If I don't like what I see I don't save it. So far 80% accuracy. The rest I did manually
It's not the most intuitive software but it is very handy if you persist and work it out. It can save you hundred of tedious hours.
Awesome
Indeed!