About this very useful component: https://www.foobar2000.org/components/view/foo_verifier
Hello Peter,
thank you for this useful component.
Would it be possible to make all the colums sortable ?
In a situation, like in the screenshot, it would be very easy/quickly possible to jump to the one file which has problems.
=> Sort for STATUS or WARNING and jump with keyboard shortcut to the end (or begin) of the list to immediately see the file with problem.
Now, we have to search/scroll/browse a long time to find that one single problem file.
Thank you.
Another glitch, mabe somebody can try to reproduce this?
When focused on a playlist (CUI) and pressing CRTL+A to select all files in that playlist,
all files in the open verifier-window are selected.. thats odd.
Since 1.5 beta 10 only one CPU core/thread is used (in beta 9 all 4 cores / 8 threads).
All feedback noted.
Beta 10 bug breaking Verifier acknowledged and fixed for beta 11, thanks for reporting.
New version: 1.3 beta 1
https://www.foobar2000.org/temp/Verifier-1.3b1.fb2k-component
New results view, with sorting.
Fixed Ctrl+A glitch.
Mitigated fb2k 1.5 beta bug causing single threaded scan.
All threads are used again in version 1.3 beta 1.
Sortable columns are working well (nice feature).
Ctrl+A bug seems to be fixed (I never noticed that before).
Perfect!
Maybe one small cosmetic remark:
Everytime the Verify dialogue is open, the dialogue and column widths are reset to their initial value (even if I adjust them before), producing a horizontal slider for only a small area (see fuffi's screenshot with Ctrl+A bug). So a higher value for default dialogue width would be nice (or remembering the adjustments).
1.3 beta 2
https://www.foobar2000.org/temp/Verifier-1.3b2.fb2k-component
Made dialog size and column sizes remembered.
Double clicking a list entry shows detailed information (error list etc).
1.3 beta 2 works perfectly. Thank you!
@Peter with the fixes un beta 11 can we no go back to using the stable version or will 1.3 go official soon
New results view, with sorting.
Fixed Ctrl+A glitch.
Thank you, its working great now!
Btw:
I had a keyboard-shortcut set to CTRL+A (Global NO, Type MAIN) bound to EDIT -> SELECT ALL and the glitch still occured until I removed that shortcut.
Dunno, why I had this shortcut in the first place, because this function seems to be f2k internal (maybe it was not back in the days....).
That doesn't seem fair. I've been hoping the Converter Setup would remember column sizes for at least 40 years now :)
As much as I love fb2k, some days resizing the columns does make me feel a little suicidal. ;)
Another pre-xmas-wish, which I almost forgot about:
Filenames! Can we please have an additional column for the filename?
(and
%__tagtype% would also be very useful)
That would make it more easy to quickly see, which fileformates are broken. Now, we only have the Name column, but, as you see in the screenshot, they show the same contents. Imagine a list with > 3 of the same names...
I use to convert files to other formats and for some cases, they have problems.
ATM, its not possible to get an quick overview which files are problematic.
The filename would indicate the extension and then I would know "the source".
Thank you.
As much as I love fb2k, some days resizing the columns does make me feel a little suicidal. ;)
Yeah, thats true ;-)
There are some places, where the user has to *always[tm]* resize columns,
*but* it (now) works in converter setup, as is works here, in the foo_verifier component. Thumbs up!!
EDIT:
There is a feature whish (https://hydrogenaud.io/index.php?topic=116509.msg974011#msg974011) in the "feature wish thread", which shows a nice animated gif to explain the pain of resizing ;-))
Apologies to the Mods for responding to an old thread but seeing as how this was the only one with the right plug-in name I assume it should be appropriate:
Hey Peter, I have a problem your addon could potentially help other people with. I recently had a large 2-way mirrored Storage-space using ReFS get corrupted with only one drive failure and I'm in the file recovery process now. It shouldn't have happened and certainly was a Microsoft issue, but *deep breath* here we go.
I have tens-of-thousands of FLAC files to scan for corruption, but the issue is that if I do it in batches I have to manually track what I've scanned and what I haven't scanned. Would it be possible to include the ability to track what files have already been scanned and which were corrupted? Ideally one would also be able to set a timeframe, so, say if it's been 120 days (just as an example) and the FLAC file had not been scanned sooner, File Integrity would have the option to re-scan. This probably won't help me at this point but could potentially help out some other poor souls down the road.
Thanks Peter!!
Filenames! Can we please have an additional column for the filename?
+1
Even better the full
file path, because if you're verifying a lot of files, some can have the same file name.