From 927303374bdf3dcc4debbd797c103a7dded15037 Mon Sep 17 00:00:00 2001 From: sandreas <2050604+sandreas@users.noreply.github.com> Date: Sun, 10 Jul 2022 04:50:44 +0200 Subject: [PATCH] Updated README.md to contain v0.0.6 --- README.md | 22 ++++++++++++---------- tone/doc/release/release-notes-v0.0.6.md | 2 +- 2 files changed, 13 insertions(+), 11 deletions(-) diff --git a/README.md b/README.md index 2038210..9bb3c22 100644 --- a/README.md +++ b/README.md @@ -68,19 +68,19 @@ This means, that downloading a single file from the [releases] page. ```bash # linux-arm -wget https://github.com/sandreas/tone/releases/download/v0.0.4/tone-0.0.4-linux-arm.tar.gz +wget https://github.com/sandreas/tone/releases/download/v0.0.6/tone-0.0.6-linux-arm.tar.gz # linux-arm64 -wget https://github.com/sandreas/tone/releases/download/v0.0.4/tone-0.0.4-linux-arm64.tar.gz +wget https://github.com/sandreas/tone/releases/download/v0.0.6/tone-0.0.6-linux-arm64.tar.gz # linux-x64 -wget https://github.com/sandreas/tone/releases/download/v0.0.4/tone-0.0.4-linux-x64.tar.gz +wget https://github.com/sandreas/tone/releases/download/v0.0.6/tone-0.0.6-linux-x64.tar.gz # macos (m1) - not working atm, see issue #6 -wget https://github.com/sandreas/tone/releases/download/v0.0.4/tone-0.0.4-osx-arm64.tar.gz +wget https://github.com/sandreas/tone/releases/download/v0.0.6/tone-0.0.6-osx-arm64.tar.gz # macos (intel) -wget https://github.com/sandreas/tone/releases/download/v0.0.4/tone-0.0.4-osx-x64.tar.gz +wget https://github.com/sandreas/tone/releases/download/v0.0.6/tone-0.0.6-osx-x64.tar.gz # untar tar xzf tone-*.tar.gz @@ -97,10 +97,10 @@ tone --help ```bash # download for windows (powershell) -iwr -outf tone-0.0.4-win-x64.zip https://github.com/sandreas/tone/releases/download/v0.0.4/tone-0.0.4-win-x64.zip +iwr -outf tone-0.0.6-win-x64.zip https://github.com/sandreas/tone/releases/download/v0.0.6/tone-0.0.6-win-x64.zip # extract tone -Expand-Archive -LiteralPath tone-0.0.4-win-x64.zip -DestinationPath . +Expand-Archive -LiteralPath tone-0.0.6-win-x64.zip -DestinationPath . # test if tone is usable .\tone --help @@ -143,7 +143,7 @@ There are some global options, that can be used to change the behaviour of the f ### `dump` - show audio metadata ```bash -tone dump --help +tone dump --help USAGE: tone dump [input] [OPTIONS] @@ -163,7 +163,8 @@ OPTIONS: --order-by --limit --include-property - --format + --format + --query ``` ### `tag` - modify audio metadata @@ -234,6 +235,7 @@ OPTIONS: --auto-import --meta-chapters-file --meta-cover-file + --meta-tone-json-file -p, --path-pattern --path-pattern-extension --meta-equate @@ -243,7 +245,7 @@ OPTIONS: --script --script-tagger-parameter -y, --assume-yes - --dry-run + --dry-run ``` #### filename to tag via `--path-pattern` / `-p` diff --git a/tone/doc/release/release-notes-v0.0.6.md b/tone/doc/release/release-notes-v0.0.6.md index 50b8e48..f3866cc 100644 --- a/tone/doc/release/release-notes-v0.0.6.md +++ b/tone/doc/release/release-notes-v0.0.6.md @@ -4,7 +4,7 @@ - add: `tone.json` serializer for `dump` command with optional `JSONPath` support (`tone dump my-file.m4b --format=json --query="$.meta.album"`) - add: support new metadata format `tone.json` including `--auto-import` (`tone tag my-file.m4b --meta-tone-json-file="tone.json" --auto-import="tonejson"`) - fix: cover tagger did not find covers under specific circumstances -- + ## known issues The following issues are known, part of an external library and already reported: