<zas[m]> "julian45: Protopia About Picard3..." <- got it to build on win11, but i can't figure out where `uv pip install -e .` put the executable...
2025-12-16 35054, 2025
julian45[m] was ultimately able to get my picard 3 build to open with python .\tagger.py
2025-12-16 35002, 2025
julian45[m] * was ultimately able to get the picard 3 build to open with python .\tagger.py
2025-12-16 35043, 2025
Jade[m]
<julian45[m]> "got it to build on win11, but..." <- I tend to use the uv tool commands because that puts the commands in PATH for you
2025-12-16 35008, 2025
julian45[m]
the one thing i'd suggest so far is that in the plugin install UI, the short description (well, the description field in any given plugin's MANIFEST.toml) be displayed as a column as well. in the current state, if one happens to already know what a given plugin does, great; if not, one has to know to right-click that plugin and select "info" to learn more about it
2025-12-16 35047, 2025
julian45[m]
Jade[m]: the command in the reply you quoted was in the master branch `INSTALL.md` but yeah the tool method would probably work
2025-12-16 35049, 2025
julian45[m]
well it looks like it does, but as with the other command, just running picard only causes a "select an app to open 'picard'" window to appear (tried to screenshot it but it goes away if you give anything else focus)
2025-12-16 35059, 2025
outsidecontext[m
<julian45[m]> "was ultimately able to get my..." <- It puts it in the .venv UV created. Easy method to run it is `uv run picard`. Likewise the CLI for managing plugins with `uv run picard-plugins`
2025-12-16 35028, 2025
julian45[m] facepalms, will give it another go tomorrow
2025-12-16 35038, 2025
outsidecontext[m
Didn't expect you'd still be around :)
2025-12-16 35050, 2025
julian45[m]
well, technically today, but it is effectively “late monday” for my timezone
2025-12-16 35004, 2025
julian45[m]
outsidecontext[m: mostly had to wait for my laundry cycle to finish
2025-12-16 35028, 2025
julian45[m]
downside of living in a shared house - you don’t always get to do your laundry on your desired schedule
2025-12-16 35006, 2025
outsidecontext[m
Ah yes, I know that
2025-12-16 35042, 2025
outsidecontext[m
And thanks for helping to everyone. We have been testing a lot, but these changes consist of a lot of small details
2025-12-16 35054, 2025
outsidecontext[m
I also would generally suggest to run Picard with the `-c` Parameter to use a fresh and separate config for testing. So with uv something like `uv run picard -c picard3.ini`
2025-12-16 35020, 2025
outsidecontext[m
(you can name the config file however you want)
2025-12-16 35048, 2025
zas[m]
<julian45[m]> "the one thing i'd suggest so far..." <- Actually the short description is shown in the tooltip, and long one in the Information dialog
2025-12-16 35006, 2025
julian45[m]
<zas[m]> "Actually the short description..." <- not true for my build, the short `description` only is shown for both mouse-over and double-click
2025-12-16 35014, 2025
julian45[m]
proved with checking the "Combine Performer Tags" plugin interaction behavior in the picard UI vs [its `MANIFEST.toml`](https://github.com/rdswift/picard-plugin-combine-performer-tags/blob/main/MANIFEST.toml)
2025-12-16 35006, 2025
julian45[m] uploaded a video: (4523KiB) < https://matrix.chatbrainz.org/_matrix/media/v3/download/julian45.net/Iej3gqhzF5esPIi4p4asZZPxNYykHTwu/2025-12-16_10-25-13_explorer.mp4 >
2025-12-16 35020, 2025
julian45[m]
screen recording showing as much ^
2025-12-16 35039, 2025
julian45[m]
meanwhile, let me see about testing the plugin conversion for replaygain2 since i like running that on files i process with picard
2025-12-16 35015, 2025
outsidecontext[m
I think during install it shows only the short description in both places. For installed plugins it shows the long description. I think the long description is not available at that point, it requires fetching the manifest. But maybe this actually should be done in this case.
2025-12-16 35044, 2025
julian45[m]
conversion seems to have gone alright, but plugin install fails if not a git repo, which is perhaps intentional...?
2025-12-16 35027, 2025
outsidecontext[m
yes, it needs to be a git repo currently
2025-12-16 35005, 2025
outsidecontext[m
also it is very much expected that some manual work will be required for converted plugins. The conversion makes the migration much easier, but it does not cover everything
2025-12-16 35023, 2025
julian45[m] uploaded an image: (116KiB) < https://matrix.chatbrainz.org/_matrix/media/v3/download/julian45.net/jiK6JxEVDixxDcuiJsz7ncUa0iOKI1Zc/2025-12-16_10-44-59.png >
2025-12-16 35028, 2025
julian45[m]
🤔
2025-12-16 35022, 2025
julian45[m]
after install, the plugin settings show up in options, but in the UI if I right-click an otherwise-complete release and go to the plugins section in the tooltip, all that shows up is "Unknown"
2025-12-16 35044, 2025
julian45[m]
...nor does it actually save my settings
2025-12-16 35018, 2025
julian45[m]
* my settings, like my path to rsgain executable, desired target loudness, etc.
