option -Q explained differently in -h help and manpage? Add an option to not query.

[musger]

Hi,
on Debian with jack 4.0+git20241202.3410dc1 the -h help lists the -Q option as

--no-query-now, -Q 
don't do metadata query when starting

while the manpage gives
-Q, --query-now

It seems that -Q will query, as will --no-query-now, and sometimes it takes a very long time to query databases, coming up with no results ("MusicBrainz did not return releases") for unknown CDs. It would be helpful to have a command line option to not query at all up front. At current, I am much faster with shutting down networking before running jack to get around this problem.

[zzarne]

All toggle options can be negated with --no. Help takes the current system or user defaults into account while the man page doesn't. So both are correct. What you're probably looking for is --no-query-if-needed.
BTW: you can search options, but if there is an exact match, like in jack --help query, only that is shown. jack --help quer would show all matches, as would jack --help '*query*' from 52ad07e on.

[musger]

Thanks for you reply Arne! I have tried all the following optios $ jack --no-query-if-needed $ jack --query-if-needed=no $ jack --no-query but only $ jack --no-query-now will make jack not query the servers. I checked my ~/.jack4rc (formerly ~/.jack3rc) and it contains the two lines cont_failed_query query_on_start but I was under the impression that CLI flags take precedence over them(?). Btw, is the --cont-failed-query flag (continue without FreeDB data if query fails) still applicable? Since there are now inexact matches displayed, it is difficult to tell what it means "to fail". Let me tell you that I am proudly using jack since more than ten years and am very happy and want to thank you for writing/maintaining this valuable software! best, Peter * zzarne ***@***.***> [2025-08-24 02:17]:

…

zzarne left a comment (jack-cli-cd-ripper/jack#61) All toggle options can be negated with --no. Help takes the current system or user defaults into account while the man page doesn't. So both are correct. What you're probably looking for is `--no-query-if-needed`. BTW: you can search options, but if there is an exact match, like in `jack --help query`, only that is shown. `jack --help quer` would show all matches, as would `jack --help '*query*'` from 52ad07e on. -- Reply to this email directly or view it on GitHub: #61 (comment) You are receiving this because you authored the thread. Message ID: ***@***.***>

[musger]

I am replying to my last post here. When running $ jack --no-query-now on an 18.track unknown CD it will take about 1min30s for jack to create the jack-xyzzz directory and another 20s for it to start ripping. I feel this is new behavior since I upgraded to jack 4.0. Is this due to my CD or is there still some network-related timeout? Cdparanoia starts the extraction after a few seconds... All ideas are much appreciated, thanks a lot! P * Peter P. ***@***.***> [2025-08-25 19:09]:

…

Thanks for you reply Arne! I have tried all the following optios $ jack --no-query-if-needed $ jack --query-if-needed=no $ jack --no-query but only $ jack --no-query-now will make jack not query the servers. I checked my ~/.jack4rc (formerly ~/.jack3rc) and it contains the two lines cont_failed_query query_on_start but I was under the impression that CLI flags take precedence over them(?). Btw, is the --cont-failed-query flag (continue without FreeDB data if query fails) still applicable? Since there are now inexact matches displayed, it is difficult to tell what it means "to fail". Let me tell you that I am proudly using jack since more than ten years and am very happy and want to thank you for writing/maintaining this valuable software! best, Peter * zzarne ***@***.***> [2025-08-24 02:17]: > zzarne left a comment (jack-cli-cd-ripper/jack#61) > > All toggle options can be negated with --no. Help takes the current system or user defaults into account while the man page doesn't. So both are correct. What you're probably looking for is `--no-query-if-needed`. > BTW: you can search options, but if there is an exact match, like in `jack --help query`, only that is shown. `jack --help quer` would show all matches, as would `jack --help '*query*'` from 52ad07e on. > > -- > Reply to this email directly or view it on GitHub: > #61 (comment) > You are receiving this because you authored the thread. > > Message ID: ***@***.***>

[pimzand]

The delay you are seeing might be libdiscid trying to read metadata like CATALOG and ISRC from old CD's that do not contain them.
Try a recent CD and see if ripping starts faster. Check jack.toc to see whether CATALOG or ISRC data was found.

[musger]

Thanks for your suggestion Pim, indeed, jack ripping a CD from 2010 starts faster. I'd like to propose a startup flag to disable libdiscid's reading of CATALOG and ISRC for old disks and CDRs. Thanks again! Peter * Pim Zandbergen ***@***.***> [2025-08-26 14:38]:

…

pimzand left a comment (jack-cli-cd-ripper/jack#61) The delay you may be seeing is libdiscid trying to read metadata like CATALOG and ISRC from old CD's that do not contain them. Try a recent CD and see if ripping starts faster. -- Reply to this email directly or view it on GitHub: #61 (comment) You are receiving this because you authored the thread. Message ID: ***@***.***>