Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
A
audiowmark
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Stefan Westerfeld
audiowmark
Commits
0f10d01d
Commit
0f10d01d
authored
Jan 05, 2022
by
Stefan Westerfeld
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
README: document audiowmark get --detect-speed option.
Signed-off-by:
Stefan Westerfeld
<
stefan@space.twc.de
>
parent
7ec4b98e
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
46 additions
and
0 deletions
+46
-0
README.adoc
README.adoc
+46
-0
No files found.
README.adoc
View file @
0f10d01d
...
...
@@ -129,6 +129,9 @@ Use watermarking key from file <filename> (see <<key>>).
--strength <s>::
Set the watermarking strength (see <<strength>>).
--detect-speed::
Detect and correct replay speed difference (see <<speed>>).
[[key]]
== Watermark Key
...
...
@@ -170,6 +173,49 @@ watermark. Fractional strengths (like 7.5) are possible.
audiowmark add --strength 15 in.wav out.wav 0123456789abcdef0011223344556677
audiowmark get --strength 15 out.wav
[[speed]]
== Speed Detection
If a watermarked audio signal is played back a little faster or slower than the
original speed, watermark detection will fail. This could happen by accident if
the digital watermark was converted to an analog signal and back and the
original speed was not (exactly) preserved. It could also be done intentionally
as an attack to avoid the watermark from being detected.
In order to be able to find the watermark in these cases, `audiowmark` can try
to figure out the speed difference to the original audio signal and correct the
replay speed before detecting the watermark. The search range for the replay
speed is approximately *[0.8..1.25]*.
Example: add a watermark to `in.wav` and increase the replay speed by 5% using
`sox`.
[subs=+quotes]
....
*$ audiowmark add in.wav out.wav 0123456789abcdef0011223344556677*
[...]
*$ sox out.wav out1.wav speed 1.05*
....
Without speed detection, we get no results. With speed detection the speed
difference is detected and corrected so we get results.
[subs=+quotes]
....
*$ audiowmark get out1.wav*
*$ audiowmark get out1.wav --detect-speed*
speed 1.049966
pattern 0:05 0123456789abcdef0011223344556677 1.209 0.147 A-SPEED
pattern 0:57 0123456789abcdef0011223344556677 1.301 0.143 B-SPEED
pattern 0:57 0123456789abcdef0011223344556677 1.255 0.145 AB-SPEED
pattern 1:49 0123456789abcdef0011223344556677 1.380 0.173 A-SPEED
pattern all 0123456789abcdef0011223344556677 1.297 0.130 SPEED
....
The speed detection algorithm is not enabled by default because it is
relatively slow (total cpu time required) and needs a lot of memory. However
the search is automatically run in parallel using many threads on systems with
many cpu cores. So on good hardware it makes sense to always enable this option
to be robust to replay speed attacks.
== Short Payload (experimental)
By default, the watermark will store a 128-bit message. In this mode, we
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment