This program combats TV commercials on the fly by detecting ad jingles in the input audio stream and sending mute commands to a TV.
Watch AdVent in action (make sure to turn the video sound on):
advent-demo.mp4
Here AdVent is running next to a TV stream in browser, watched by a user using headphones. When an ad kicks in, AdVent cuts the sound. A bit jerky video is a result of me capturing demo video on a ten years old laptop.
Once the ads are over, AdVent turns the sound back on (not part of this demo).
Web TV is nice for testing, but the main target are conventional TV-sets. Here is an example of AdVent on a Raspberry Pi controlling a Sony BRAVIA TV-set:
AdVent functions by comparing live sound with a database of known ad jingles using open source sound recognition software Dejavu. Because of Dejavu doing all the heavy lifting, AdVent code is ridiculously small - the core consists of circa 50 lines of code; the rest being nice-to-have sugar. A database of jingles is available as a separate repository AdVent Database and is open for contributions.
There is no need to inform AdVent of an exact channel you are watching - it will probe for all known channels simultaneously.
A diagram below shows in blue a standard workflow for a person listening to a TV and muting TV sound with a remote.
AdVent is added in parallel (path in orange), using the same or similar tools for mute. The main difference is an audio source. The source should be different from the one that person hears, because AdVent needs to continue listening while the sound is muted. Obviously, this is required to be able to unmute later on. This is why a microphone is generally not a good source; it is better to feed something not affected by the Mute button of a TV. S/PDIF digital output of the TV is one good candidate.
Clearly, the approach of looking for ad jingles has inherent limitations:
- TV channels not using entry / exit jingles would not work (I do not have these in my reach);
- complex ad breaks (such as those lasting for 15 mins and employing multiple jingles in between) would likely not work well. If the pattern is regular,
--exit_jinglesoption could be used to alleviate that; - very short jingles (< 1 s) won't work out of the box (not seen in practice).
However, most TV channels I watch here in France do fall in line. So the mission was, taking into account these external limitations, make the rest working - and working well. The particular use case of interest is the evening movie watching, where ad breaks are sparsed and of simple structure.
There is also a corner case if you decide to change channel during the commercial break muted by AdVent. It has no means to detect that the channel has been changed, so you would need to unmute manually, or via some sort of timeout (like in feature #10).
The biggest problem with Dejavu is that it does not support continuous recognition from a stream. One has to define a recognition window. It kind of works when you have a four minutes song fingerprinted, and launch recognition anytime in the middle. It does not work well when your "song" is a three seconds jingle. So I opted for parallelized approach where there are overlapping threads listening for input in a sliding manner.
Side note: CPython is known to have limited support for threads, which does not work well for CPU-intense (aka "CPU-bound") tasks (see more in GIL). However, the way Dejavu works is actually closer to "I/O-bound" execution, as it spends most of the time either listening for input from PulseAudio, or querying the database for hashes, both PulseAudio and database being pools of processes on their own. For I/O-bound threads Python works fairly well. So, when talking for simplicity about AdVent threads loading the CPU, we would actually mean that AdVent threads produce enough I/O to keep CPU busy.
Question is how many threads would be needed. To understand this better I took a random three seconds jingle and tested its recognition once being split in two parts. Results:
| Part 1 | Part 2 | Recognition Confidence |
|---|---|---|
| 3 s | 0 s | 100% |
| 2 s | 1 s | 22% |
| 1.5 s | 1.5 s | 11% |
| 1 s | 2 s | 28% |
| 0 s | 3 s | 100% |
Unrelated track gives confidence of less than 10%.
From this we can draw some conclusions:
- for good recognition, having 3 seconds fingerprinted is enough (Dejavu's own estimate is that 3 seconds fingerprinted gives 98% recognition confidence);
- every contiguous 1.5 seconds (2 seconds better) shall be covered by at least one recognition attempt. Jingle minimal duration thus should not be inferior to 1.5 seconds;
- 10% confidence looks like a good cut-off for a "hit".
So we can estimate that having three recognition threads running with one second interval over three seconds window (as on figure above) should give good enough coverage. These values have been recorded as default parameters in AdVent source code (there are command line options to alter them if needed). Due to inevitable imperfections of timing, I added one more thread just in case (see more details on this below). This gives four threads in total, actively working on recognition. This means that for AdVent to perform well, it should be run on at least four cores CPU, and on such a system it would create 100% system load (four threads occupying four cores). Most of modern systems would satisfy this requirement, Raspberry Pi included.
Because recognition process is not deterministic, threads originally spaced in time might drift and come closer to each other. This would diminish coverage and decrease effectiveness of recognition. To avoid this effect, a mutex is used which would prevent any recognition operation firing too close to another one from a parallel thread.
Another side effect from threading is that two closely running threads both yielding a hit can try flipping TV, which would cause problems at TV controls unit, as well as unpleasant user experience. To prevent this, a dead time is used (30 seconds by default), during which all actions on TV are disabled.
Finally, an implicit requirement coming from threading approach is that hardware audio source shall support concurrent use from threads. This is not granted in general case (see below).
Once the threading engine was ready, in order to confirm the number of threads needed, I undertook a specific test profiling recognition process of a jingle of 3.2 seconds long. Dejavu listening interval was 3 seconds, thread spacing was 1 second, and recognition confidence was 10%. The results are shown below:
Here a green bar is the jingle; the red line is the time when the first hit was reported.
Observations:
- there is a non-negligible "deadband" in Dejavu processing (marked with blue "tips" on the graph). For every 3 seconds recognition period, the actual recognition would take anytime between 3.2 and 3.5 seconds (on a 4 x 1200 MHz machine). Apparently, the engine just listens for 3 seconds and then does its jobs in the remaining time. So this deadband (currently recorded as a 0.25 second constant in the code - see issue #24) should be taken into account in calculations;
- threads are respecting the minimal distance of 1 second between each other (mutex is working). Due to this the duty cycle of a thread is not 100% but close to 80%. This is not bad for a default setup, as it keeps machine loaded close to 100% but still leaves some time for OS to do other tasks;
- new recognition starts not exactly at 1 second interval, but anytime between 1 and 1.1 seconds (because of
sleep(0.1)when mutex cannot be taken). This error accumulates with time; but it is not very important for the purpose of the app.
Because of the above, the need for extra listening thread looks evident now. There are indeed periods of time where all four threads are active.
Another observation here is that in spite of good coverage of jingle interval, Dejavu recognition result turned out not to be as good as expected. My first thought was that Dejavu input might suffer from distortions due to concurrent access to the audio source. This has been studied in detail and multi-threading was found not to be at fault. So, maybe it was a good time to take a closer look at Dejavu itself.
Dejavu has a configuration file config/settings.py which includes a few parameters to play with. They are well documented in the file, but still, changing them requires some knowledge of Dejavu internal process. Intuitively, if we want to improve recognition quality, we need to increase fingerprinting density (number of fingerprints per second of a track). And because we are working with very short tracks, the number must be significant. The density was measured on a sample track an was found to be about 85 fingerprints per second. So the parameters were adjusted as follows:
CONNECTIVITY_MASK = 2 DEFAULT_FS = 44100 DEFAULT_WINDOW_SIZE = 1024 # was 4096 DEFAULT_OVERLAP_RATIO = 0.75 # was 0.5 DEFAULT_FAN_VALUE = 15 # was 5 DEFAULT_AMP_MIN = 10 PEAK_NEIGHBORHOOD_SIZE = 10 MIN_HASH_TIME_DELTA = 0 MAX_HASH_TIME_DELTA = 200 PEAK_SORT = True FINGERPRINT_REDUCTION = 20 TOPN = 1 # was 2
WINDOW_SIZE is a sort of a "bucket" for frequencies in Fourier transform; making it smaller allows finer granularity when telling apart different frequences. Here we make the window four time smaller. Increasing OVERLAP_RATIO will take finer slices in time (we are interested in this) and, hence, return finer offsets (this bit is not interesting - AdVent does not use offset information). Here we raise overlap from 50% to 75%. Finally, FAN_VALUE reflects a space boundary for fingerprint neighborhood; increasing it allows for more potential combinations and, hence, more fingerprints. Here, we increase the distance by a factor of three. Applying all these settings together results in 485 fingerprints per seconds, i.e. about a factor five increase in density.
Now, does this improve efficiency? I made a small synthetic test by playing a jingle in the loop with pauses not aligned to 0.1 second (this is to make sure that threads do not run fully synchronously with playback). With confidence level of 5% the difference between old and new settings is not very visible, as both demonstrate close to 100% success in matching. However, things change when we request matching confidence of, say, 50%. In this case the old set gives only 45% success rate, while the new set gives 85% success rate - almost twofold difference.
TOPN is not related to fingerprinting; it defines how many nearest matches will be returned. This is two by default, but because AdVent only uses one, it makes sense to limit it on Dejavu level and save a bit of CPU cycles.
An obvious disadvantage of having more fingerprints is that database size will grow accordingly (in this case, by a factor of five), and the matching time ("Dejavu deadband") might increase. I tested it and did not observe a noticeable change (it remains in the order of 0.4 seconds for a three seconds track). Machine load was observed to be slightly higher, but not to the extent that could be realiably measured.
Note that changing Dejavu parameters has impact on fingerprint database. It is thus better to fix and not to change them in the process, or else the entire set of jingles might need re-processing. If you plan to play with these parameters, make sure to keep around copies of your original audio files.
AdVent has got its own parameters, which could affect the success rate of recognition S:
n- number of listening threadsi- listening interval (s)c- recognition confidence
Quite obviously, success rate S should be proportional to the listening interval i (the longer we listen, the better) and inversely proportional to the recognition confidence c (higher confidence of a match would inevitably mean lower success). Similarly, success rate should be proportional to the number of listening threads n (more threads mean more hits). Unfortunately, threads tend to compete with each other and with the operating system for resources, especially when the system is close to saturation. This means that threads contribution is not proportional, but more like a square root or a logarithm: to get two times better recognition, one has to run four times more threads. In summary, we could reasonably expect success rate to be something like:
Curiously, the length of a listened track does not seem to be part of the equation. This is likely related to the fact on how recognition confidence is calculated by Dejavu. Fingerprinted confidence equals to the number of unique hashes matched related to the total number of hashes for a given track. And the latter is generally proportional to the length of the track. So it has been already indirectly taken into account. Note that it means that in order to ensure 100% recognition confidence, one has to submit the entire track for recognition.
If we draw S as a function of number of threads n, varied by confidence parameter c, we will get something like this:
From this graph we need to cut off areas which have no physical meaning: number of threads shall be no less than one and success rate of recognition shall not exceed 100%.
Actual measurement for a fixed size track gives the following:
We can see that it generally confirms the theory. 25% or less recognition confidence performs well even with a small number of threads; to obtain higher confidence one has to significantly increase the number of threads. In this case 100% confidence can never be reached (success S = 0%), because both the listening interval i and the length of the track equal to 3 seconds, and with a random start it is virtually impossible for AdVent to make Dejavu listen for the full length of the track.
Pink gradient background of the graph indicates system load - more threads mean more load. As already stated earlier, four threads on a four cores CPU would consume about 100% of the resource; ten threads would consume about 200%.
From this graph it looks like for low confidences two threads perform nearly as well as four threads, but would consume two times less the CPU; so it makes sense to make it default.
Now let's see what happens if we keep the number of threads n constant but vary the listening interval i:
We can immediately see that for low confidences the listening interval of 2 seconds performs as good as the interval of 3 seconds. It makes sense to reduce this interval when possible, because then AdVent could react faster. So the default of 2 seconds would look reasonable. One can also see the confirmation of what was said earlier - in order to get some success with 100% confidence, for a 3 seconds track one has to listen for a least 3.5 seconds. Curiously, while it makes no sense to listen for more than the track total length, increasing the interval beyond the track length appears to improve confidence.
The red area on the graph (the interval below 1 second) indicates Dejavu breakdown. Dejavu would just issue some sort of warning and return no matches. It is probably possible to overcome this by playing further with Dejavu parameters (see Dejavu Tuning), but for this task it has no interest, as jingles are normally longer than one second.
Finally, what concerns recognition confidence c, we can see that lower confidences perform much better, so one has to choose the lowest possible level where false positives do not step in. From measurements, false positives usually do not result in confidence higher than 5%, so setting default of 10% would allow for good performance and provide some margin against false positives.
In the example below a TV series 9-1-1 has been watched on the French M6 TV channel during two hours of May 2, 2023. All four ad breaks happening during that period have been detected and TV muted.
With the current sound theme M6 is a relatively "easy" TV channel to process. Most of the channels fall into this category. Few channels do exist which work less reliably, either because of irregular use of jingles or because of employing jingles with poor sound spectrum.
There are many different ways of watching TV these days. Currently supported audio inputs:
- microphone;
- video streaming in browser (via PulseAudio monitor). This is a default;
- S/PDIF digital audio out from a TV-set: optical TOSLINK or electrical RCA (RCA untested but should work).
- Nil (i.e., only emulate an action);
- PulseAudio (when watching TV on Linux). This is a default;
- Logitech Harmony Hub (deprecated);
- BroadLink Universal Remote.
- sound on / off. This is a default;
- volume lowering;
- (could be implemented if there's interest - see issue #15) changing a TV channel;
- ...
- recent Fedora (tested on Fedora 36..39). This is a default. Fedora 40 is currently not supported, as it no longer ships Python 3.7 which is needed for current DejaVu. Works to port DejaVu are planned (see denis-stepanov/dejavu#2).
- Raspbian 10. Actually, it is less laborious to support than Fedora, as many problematic points are either non-existing on Raspbian, or implemented in more user-friendly way;
- (Windows is not supported but the majority of software is in Python; should work as is, with the exception of TV controls module which would need contributions and testing - see issue #16).
Not all combinations are supported; see below for the details.
It is even possible to use unrelated inputs and outputs (e.g., to cut a sound on a real TV-set while running AdVent over a TV web cast of the same channel); however, in this case one has to accept potential time de-sync, which could be quite important (dozens of seconds, depending on a TV feed provider).
Runnig AdVent is as simple as:
(advent-pyenv) $ advent
(support to run as a daemon planned - see issue #7). Default settings are usually fine.
The output should resemble to this:
AdVent v1.6.0
TV control is 'pulseaudio' with action 'mute' for 600 s max and 1 exit jingle
TV status: unmuted, volume: 50
Recognition interval is 2 s with confidence of 10%
Started 2 listening thread(s)
Type 'h' for help
...:o::o::::::o::::::::::o::ooo
AdVent prints every second a character reflecting recognition progress. Meaning of characters:
.- no signal (usually when there's silence or no input connected at all):- a signal but no matcho- a weak matchO- a strong match, also called a "hit". When a hit happens, AdVent prints hit details and may take some action on a TV
To exit, press q. Exiting via Ctrl-C might not always work; you might want to try harder with Ctrl-\.
There is no option to select an audio source; AdVent takes a system default. See more details on audio inputs in a dedicated section.
-t TV_CONTROL option allows selecting a TV controller. The default is pulseaudio; other options are harmonyhub for HarmonyHub, broadlink for BroadLink Universal Remote, nil for TV control emulation (i.e., no real action). Emulation mode is useful during jingle fingerprinting process and when testing AdVent itself.
-a ACTION option allows selecting a desired action between mute (default) and lower_volume.
-A option allows starting TV control as if it was in the middle of AdVent action (i.e., muted or volume lowered). This option could be useful for uni-directional TV controls (such as HarmonyHub or BroadLink) to indicate to AdVent an unusual TV status, as it cannot be fetched. For bi-directional controls there is little sense in using this option, as AdVent will read the status from TV upon starting.
-V VOLUME option allows specifying a target value for volume lowering when this action is selected via -a. The meaning of the volume specifier VOLUME is TV control-specific and is passed directly to a TV controller. In the case of PulseAudio or Nil controls the parameter is interpreted as percentage of volume, and the default is -50%. Note that with PulseAudio one could go above 100%, in principle. In the case of HarmonyHub or BroadLink, one has to specify a relative change, like -2, where the number corresponds to a number of key presses of the Volume Down button on a TV remote. The default for HarmonyHub and BroadLink is -5. If you are a fan of commercials, you can specify a positive value ;-).
-d TV_CODES option allows specifying a path to a folder holding TV control codes. The default is $HOME/tv-codes. These codes are needed for BroadLink controller only; see more details on TV codes in BroadLink section.
-m MUTE_TIMEOUT option allows adjusting auto-unmute (or any other action selected) timeout, in seconds. Auto-unmute is active by default, and the default is 10 minutes (600 seconds). The timeout cannot be less than TV actuation dead time, currently set to 30 seconds. The interest of this feature is when AdVent for some reason does not detect an exit jingle and does not unmute on time, to be able to resume automatically normal TV watching at least few minutes later. It could also be of use when a microphone input is used, which by design can never unmute. If you want to disable auto-unmute altogether, pass 0 timeout.
-j EXIT_JINGLES option allows specifying a number of exit jingles to be processed before actually actuating an exit action on TV. The default is 1; i.e., any exit jingle would end the TV action in progress. This option could be useful for long ad breaks where multiple jingles could be seen.
-n NUM_THREADS option allows selecting a number of recognition threads to run. The offset between threads will be adjusted automatically. The default is two threads. Increasing this number would improve coverage of jingles in the input stream, potentially improving recognition and reactivity. However, making it significantly higher than the number of CPU cores available (which on end user computers - Raspberry Pi included - is very often 4) would likely not attain the desired result because of system starvation. Decreasing this number would decrease the system load but also decrease jingle coverage, increasing a chance to miss one. -n 1 will amount to single-thread execution, which would result in small fractions of input not submitted to recognition due to inevitable Dejavu deadband.
-i REC_INTERVAL option allows adjusting the recognition window, in seconds. Fractions like 2.5 are accepted. The default is 2 seconds, which is the lowest interval where Dejavu still performs well. Increasing this parameter would increase Dejavu confidence (because it listens for longer) in expense of decreased effectiveness of AdVent (because threads would have a lower duty cycle). In other words, with increased interval there would be less chances for detection but those succeeding would have higher confidence. This option could be useful if DeJavu knows the track but lacks a bit of confidence to recognize it. Another aspect to keep in mind is that the longer the interval is, the slower reaction of AdVent would be. With the default of 2 seconds the reaction would be nearly instantaneous; with intervals of 3+ seconds AdVent might let few seconds of ads getting in before cutting the sound. If you would like to have a longer interval but still maintain a good reaction time, consider increasing the number of threads accordingly. Going for intervals below 1 second would break Dejavu processing and so is pretty useless.
-c REC_CONFIDENCE option allows adjusting recognition confidence for a hit in the range of 0-100%. The default, selected experimentally, is 10%. Increasing this parameter would make AdVent less sensitive but more certain; decreasing it would make AdVent more sensitive but also increase a chance of having false positives. Selecting confidence of 0% would mean that anything non-silence will be taken as a hit. 5% is a typical threshold where false positives start being a nuisance. If you plan to increase confidence above 15%, consider also increasing the listening interval. To achieve confidence of 100%, the interval must be larger than the length of the jingles of interest (i.e., should be usually at least 5 seconds long - depends on TV channel theme).
Some useful presets:
| Preset | n | i | c |
|---|---|---|---|
| TV remote | 1 | 1 | 100 |
| Noise detector | 2 | 1 | 0 |
| I'm feeling lucky | 2 | 2 | 5 |
| Optimal (default) | 2 | 2 | 10 |
| Super-fast | 4 | 1 | 10 |
| Reliable | 4 | 3 | 10 |
| Confident | 4 | 5 | 50 |
| Super-prudent | 4 | 5 | 100 |
| Fast & furious | 8 | 2 | 10 |
"TV remote" preset would result in nearly no hits irrespectively of input, so AdVent could de-facto be used as a pass-through TV remote using its interactive controls.
-l LOG_LEVEL option will log recognition process into a file advent.log. Supported levels of logging are none (default), events and debug.
Debug log is useful to understand why AdVent reacted (or not). The log might look something like this:
...
2022-10-11 22:16:41,625 Thread-1 DEBUG: Recognition start=22:16:39,487, end=22:16:41,625, match FR_TFX_220906_SHERLOCKHOLMES3_1, 0% confidence
2022-10-11 22:16:42,913 Thread-2 DEBUG: Recognition start=22:16:40,697, end=22:16:42,913, match FR_W9_220830_FBI1_3, 0% confidence
2022-10-11 22:16:44,070 Thread-1 DEBUG: Recognition start=22:16:41,826, end=22:16:44,070, match FR_TF1_220219_THEVOICE5_1, 0% confidence
2022-10-11 22:16:45,216 Thread-2 DEBUG: Recognition start=22:16:43,013, end=22:16:45,216, match FR_TFX_220906_SHERLOCKHOLMES1_1, 0% confidence
2022-10-11 22:16:46,360 Thread-1 DEBUG: Recognition start=22:16:44,170, end=22:16:46,360, match FR_W9_220905_PIRATESOFTHECARRIBEAN1_3, 0% confidence
2022-10-11 22:16:47,497 Thread-2 DEBUG: Recognition start=22:16:45,317, end=22:16:47,497, match FR_W9_220830_FBI1_3, 0% confidence
2022-10-11 22:16:48,648 Thread-1 DEBUG: Recognition start=22:16:46,461, end=22:16:48,648, match FR_M6_220723_EVENING1_1, 3% confidence
2022-10-11 22:16:49,821 Thread-2 DEBUG: Recognition start=22:16:47,597, end=22:16:49,821, match FR_M6_220723_EVENING1_1, 11% confidence
2022-10-11 22:16:49,821 Thread-2 INFO: Hit: FR_M6_220723_EVENING1_1
2022-10-11 22:16:49,821 Thread-2 INFO: TV muted
2022-10-11 22:16:50,906 Thread-1 DEBUG: Recognition start=22:16:48,749, end=22:16:50,906, match FR_M6_220723_EVENING1_1, 4% confidence
2022-10-11 22:16:52,204 Thread-2 DEBUG: Recognition start=22:16:49,922, end=22:16:52,204, match FR_M6_220723_EVENING1_1, 3% confidence
...
Refer to advent -h for full synopsys.
AdVent allows recognition process steering at run-time by hitting keys in the console. Here is the summary:
h - help
t / T - emulate a hit / unconditionally
a - toggle 'in action' status
j / J - exit jingles' number decrease / increase
i / I - interval decrease / increase
c / C - confidence decrease / increase
space - TV toggle mute
m / M - TV mute / unmute
v / V - TV volume lower / raise
q - quit
t just emulates a hit. This action could be useful when AdVent for some reason would not react where it should have, so you could give it a hand. Like with any other hit, it would respect the TV dead time, i.e. will not act on TV if there has been another action happening recently. If you want to override this - e.g., to "undo" an erroneous AdVent hit which has just occured - use T.
a toggles the TV internal "in action" status, without making any specific action on a TV. This action could be useful when AdVent for some reason comes out of sync with TV status (e.g., when TV has been manually muted using its own remote).
j / J changes the number of exit jingles to be taken into account for the actual action exit.
i / I and c / C allow tuning the corresponding AdVent parameters at run-time. Interval can be changed from 0 to infinity in steps of 0.5 s (but remember that intervals below 1 s are rather useless). Confidence can be changed from 0 to 100% in 1% steps. Changing the number of threads n on the fly is currently not supported (upvote the issue #68 if you need this).
space, m / M and v / V act as TV remote buttons, i.e., send the corresponding commands directly to a TV bypassing AdVent engine. This is just a bonus, because the TV control module would allow that. However, these commands have to be used conciously, as they might cause desync in some situations, e.g., leaving TV indefinitely in "mute" while AdVent would believe it is unmuted. If you want AdVent to take into account your actions, you need to manipulate "in action" flag manually using the a command.
If AdVent would not trigger where you think it should have, you might need some manual tuning.
Run AdVent with -l debug option and inspect the log. If the matching confidence during jingle playback is less than 5%, it would mean that the jingle is likely not known to the database and would need enrollment as described in AdVent DB manual.
If the log manifests jingle confidence between 5 and 10% (10% being a default fire-up threshold), it means that AdVent knows the jingle, but is not confident enough recognizing it. You can undertake the following steps.
Use the -c parameter to AdVent (or the key c in interactive mode) to decrease matching confidence from the default 10% to the confidence you actually observe (e.g., -c 6).
If this would result in false positives firing up (e.g., jingles from another TV channel starting showing up), look at the number of threads.
Fix the -c confidence parameter at the lowest level where false positives do not creep in, and increase the number of threads from the default of 2 threads using the -n parameter (e.g., -n 4). This requires AdVent restart.
You can go as high as the number of CPU cores on your machine (see cat /proc/cpuinfo), and even somewhat higher, depending on the size of RAM you have got and on the speed of disk. With plenty of resources you might be able to go twice as CPU cores number, e.g., to 5-8 threads on a 4 CPU machine.
This would increase the matching confidence, but in a moderate way. As explained above, you would need quite a few more threads to significantly improve recognition confidence, heating up your device as a consequence. If increasing the number of threads would not help much, look at the recognition interval.
Fix the -n threads parameter to the number of CPU cores you have got and increase the recognition interval from the default of 2 s using the -i parameter (e.g., -i 3) (or the key I == Shift + i in interactive mode). Use increments of 0.5 s. You can go as high as the duration of jingles of interest (e.g, generally up to 4-6 s).
This would considerably increase recognition confidence, at the expense that AdVent would kick in quite late (i.e., letting in few seconds of ads before muting).
New jingles are fingerprinted following the regular Dejavu process (see "Generate a Hash" in AdVent-DB). After the process they end up in an SQL database. Unfortunately, Dejavu does not provide a mechanism to share database content. To facilitate manipulations with the database, a service tool db-djv-pg is included with AdVent. It allows exporting / importing jingles as text files of specific format. Dejavu supports MySQL and PostgreSQL as databases, with default being MySQL. Unluckily(?), I am much more fluent with PostgreSQL, so AdVent supports PostgreSQL only (sorry MySQL folks :-); hence the -pg in the tool name. AdVent does not alter Dejavu database schema; additional information needed for AdVent functioning is encoded in the jingle name.
The tool allows for the following operations on jingles (aka "tracks"):
list- list tracks available in the database- (planned - issue #50)
info- display track information export- export tracks from the database to files (add-dto arrange exported files in folders)import- import tracks from files to the databaserename- rename a track in the database or on disk (for disk, specify.djvextension. Caveat: for a file tree under version control this might be a disruptive action - see issue #55)delete- delete tracks from the database (file deletion planned - see issue #54)dbinfo- display database information and statistics (add-cfor health checks)vacuum- vacuum the database (add-fto run full vacuum)
Remaining parameters are jingle names, or masks using simple regular expression syntax (*, ?). import takes file names as parameters; rename may take file name or track name (without file extension), other commands operate on track names. When using track name regular expressions in shell, remember to protect them from shell expansion using quotes.
The tool by default does not overwrite existing tracks in any direction; if this is desired, pass the -o option. As overwriting is a potentially expensive operation, the tool will first check SHA1 of the source and of the target and will refuse update if they match (i.e., if update would make no difference). If this heuristic is not desired, use -O (unconditional overwrite) option.
To make sure the database is perfectly in sync with the snapshot on the file system, pass -s parameter during import. This will overwrite all tracks that appear different and delete all those not having a matching file. Similarly in opposite direction: if you specify -s during export, the file system snapshot will be aligned to the database content.
It is not uncommon to store the database of fingerprints under version control. The tool will auto-detect if it operates in a git repository and inform git about changes it does on the disk. Currently only rename operation is concerned: the renaming change will be staged and the STAGED marker printed. On export the new files will remain unstaged. If git operations are undesired, an option -G could be used to suppress them.
Long operations (such as mass import or export) are signalled with a progress bar.
Examples of use:
# List database content
(advent-pyenv) $ db-djv-pg list
# Export TF1 channel jingles
(advent-pyenv) $ db-djv-pg export "FR_TF1*"
# Export the entire database using AdVent DB file system layout
(advent-pyenv) $ db-djv-pg export -d
# Import all jingles in the current directory, overwriting existing ones
# Note that escaping shall not be used in this case
(advent-pyenv) $ db-djv-pg import -o *
# Import the entire AdVent DB snapshot and make sure the database has nothing else
(advent-pyenv) $ db-djv-pg import -s DB
# Rename a jingle (e.g., to correct flags)
(advent-pyenv) $ db-djv-pg rename FR_6TER_220903_ELEMENTARY1_1 FR_6TER_220903_ELEMENTARY1_3
# Same but on disk. Jingle name is stored inside the file, so it is better to use the tool when it comes to rename files
(advent-pyenv) $ db-djv-pg rename FR_6TER_220903_ELEMENTARY1_1.djv FR_6TER_220903_ELEMENTARY1_3.djv
# Delete one jingle
(advent-pyenv) $ db-djv-pg delete FR_TF1_220205_EVENING1_2
# Delete the entire database
(advent-pyenv) $ db-djv-pg delete \*
Refer to db-djv-pg -h for exact synopsis.
dbinfo command will show detailed information about the database content, both for Dejavu and for AdVent:
(advent-pyenv) $ db-djv-pg dbinfo
Dejavu database info:
Fingerprinted / total tracks = 117 / 117
Peak groups = 29482 (avg. ~= 252 per track)
Fingerprints = 760255 (avg. ~= 6498 per track)
Total fingerprinted time ~= 489 s (avg. ~= 4.2 s per track)
Database size ~= 117 MB (avg. ~= 1.0 MB per track)
Fingerprinting frequency ~= 1555 Hz (~= 3.53% of sampling frequency 44100 Hz)
Hash size = 10 B
Hash collisions ~= 19.74%
First update ~= 2022-10-27 23:19:34
Last update ~= 2022-10-27 23:24:19
Last vacuum ~= 2022-10-27 23:46:24
AdVent database info:
Countries = 1
TV channels = 11 (avg. ~= 11 per country)
Jingles = 117 (avg. ~= 11 per TV channel)
Pure entry / entry jingles = 36 / 70
Pure exit / exit jingles = 47 / 81
No action jingles = 0
Time coverage from = 2022-02-05
Time coverage till = 2022-10-14
(advent-pyenv) $
For explanation of Dejavu parameters see Dejavu documentation. Some of these metrics depend on parameters fixed during Dejavu tuning: DEFAULT_WINDOW_SIZE, DEFAULT_OVERLAP_RATIO and DEFAULT_FS (this latter - the sampling frequency - is actually not variable by user and is taken directly from Dejavu sources). Currently, these parameters cannot be read from Dejavu and are hardcoded, so if you make your own tuning, consider updating them in the db-djv-pg source code. Approximations ~= mean rounding or approximate calculations because the information is not stored in the database but calculated.
"Fingerprinting frequency" is not a metric originally defined in Dejavu; it corresponds to the "fingerprinting density" described above. The tool calls it frequency because it is measured in frequency units (counts per second). "Last vacuum" is a PostgreSQL-specific parameter (see database vacuuming below).
AdVent information is pretty self-describing; if you need more info, see AdVent database documentation.
If you run dbinfo with -c parameter, it will additionally execute database health checks:
Database health checks:
D0010: timestamps in future : OK
D0011: created > modified : OK
D0020: same song name, different SHA1 : OK
D0021: same SHA1, different song name : OK
D0030: fingerprinted without fingerprints : OK
D0035: fingerprint counts mismatch : OK
D0040: fingerprint hashes of variable size : OK
D0100: vacuum needed : OK
A0010: non-fingerprinted tracks : OK
A0020: low confidence tracks : OK
A0050: bad track name format : OK
A0051: bad track date format : OK
A0080: bad flags : OK
--------------------------------------------------+-------
TOTAL CHECKS : OK
Dxxx are Dejavu-specific checks and Axxx are checks specific to AdVent. A healthy database shall display OK as a summary. Most of the time failures are not critical for application functioning, but they might contribute to incorrect results or performance degradation. To fix the "vacuum needed" failure you need to run database vacuuming. Fixing other issues most likely would require deleting problematic tracks or reloading the database altogether.
Even a modest database of a few dozens of tracks could have hundreds of thousands of fingerprints. AdVent puts a stress on the database by constantly querying it from multiple threads. It is thus important to keep the database clean of old transactions and with indexes optimized. In PostgreSQL this is achieved with the help of a VACUUM command. Use this command:
(advent-pyenv) $ db-djv-pg vacuum
If you pass -f parameter, a VACUUM FULL instruction will be run. Full vacuum is not required in any regular scenario; if you run it, make sure AdVent is not running at the same time, as full vacuuming rebuilds the tables and thus needs exclusive access to the database.
Vacuum is run automatically on all operations that modify database content, so, normally, there's no need to run it explicitly.
Installation was tested on Fedora and Raspbian. The differences are marked below accordingly. Setup process is a bit long, mostly because Dejavu and its database need some dependencies and configuration. Some of these steps are covered in (a bit dated) Dejavu original manual, but I reiterate here for completeness.
#prompt means execution from root (you can usesudoinstead if it is configured on your system)$prompt means execution from user(advent-pyenv) $prompt means execution from user in a Python virtual environment
Differences in files are presented using diff notation, with < meaning old content and > meaning new content.
Fedora:
# dnf install postgresql-server ffmpeg portaudio-devel
Raspbian:
$ sudo apt-get install postgresql-11 ffmpeg libatlas-base-dev
If you happen to have PostgreSQL running already, skip this step.
Default PostgreSQL in Fedora has a ridiculously conservative setup, so you have some work to do to get it up and running. On Raspbian, this step is automatic; just skip it.
Initialize PostgreSQL:
# postgresql-setup --initdb
Allow localhost connections using password. As root, edit /var/lib/pgsql/data/pg_hba.conf to change ident method to md5:
< host all all 127.0.0.1/32 ident
---
> host all all 127.0.0.1/32 md5
Add PostgreSQL to auto-start and run it:
# systemctl enable postgresql
# systemctl start postgresql
One more word on services. Recent Fedoras bring up a particularly agressive OOMD (out-of-memory killer daemon). Despite the name, memory is not its only concern. It regularly tries shooting to death my busy Firefox in the midst of a morning coffee sip. Because AdVent is a CPU-intensive application, OOMD will try taking its life too. If you observe AdVent silently exiting after some time, you know the reason. Probably, there is a way to make an exception, but because I do not like it anyway, I just disarm:
# systemctl stop systemd-oomd
# systemctl mask systemd-oomd
Create a database user:
# sudo -u postgres createuser -P advent
Enter password for new role: (enter "advent")
Enter it again: (enter "advent")
#
Create an empty database with advent user owning it:
# sudo -u postgres createdb -O advent advent
Whoooah... so much for PostgreSQL.
On Raspbian, this step is the same, but you do not have to be root to run sudo.
The latest Dejavu mainstream does not run on Python 3.10-12 shipped with Fedora 36-39 (pull requests are welcome), so we need a virtual environment for Python 3.7:
Fedora:
# dnf install python3.7 python3-virtualenv
On Raspbian 10, Python is already - quite conveniently - 3.7, and support for virtual environment is installed by default.
Create virtual environment:
$ python3.7 -m venv --system-site-packages advent-pyenv
$ source advent-pyenv/bin/activate
(advent-pyenv) $
On Fedora, it is recommended to add wheel package to your virtual environment, otherwise you could get deprecation warnings when installing AdVent with the latest pip. On Raspbian, wheel comes installed by default.
(advent-pyenv) $ pip install wheel
My clone of Dejavu includes several minor but necessary adjustments allowing better co-habitation with AdVent. For AdVent to work you need to install that fork instead of Dejavu upstream:
(advent-pyenv) $ pip install https://github.com/denis-stepanov/dejavu/zipball/tags/0.1.3+ds1.3.0 # or any latest tag
(advent-pyenv) $ pip install https://github.com/denis-stepanov/advent/zipball/main # or any stable tag
At this moment the database is void of any schema, not to say data. One can trick Dejavu into creating database schema by asking it to scan something. The error message is not important:
(advent-pyenv) $ dejavu -f .
Please specify an extension if you'd like to fingerprint a directory!
(advent-pyenv) $
Now it's data's turn. Pull and load the latest snapshot of ad fingerprints. See more details on this in AdVent DB pages:
(advent-pyenv) $ git clone https://github.com/denis-stepanov/advent-db.git
(advent-pyenv) $ db-djv-pg import advent-db/DB
This is all what concers AdVent per se. However, depending on your audio capturing options and on preferred way to control TV you might have additional work to do. See below for instructions.
AdVent takes a system-wide default audio source as input. On modern Linux it is usually PulseAudio who takes care of sound services (yeah... Fedora has switched to PipeWire, but its PulseAudio emulation layer is good enough for our purpose). You can check the default source as follows:
Fedora:
$ pactl get-default-source
alsa_input.pci-0000_00_1b.0.analog-stereo
$
Erf... not very descriptive. You can get more details by studying a lenghty output of:
$ pactl list sources
You can also use graphical tools like pavucontrol presenting audio configuration in a more user friendly way.
To check the default source on Raspbian:
$ pacmd list-sources | grep -B1 name:
index: 0
name: <alsa_output.platform-soc_sound.iec958-stereo.monitor>
--
* index: 1
name: <alsa_input.platform-soc_sound.iec958-stereo>
$
The source marked with an asterisk * is the default. Omit grep to see more details.
Sections below detail supported inputs.
This input has an inherent limitation in the sense that AdVent will mute but never unmute, as by muting it would silence its own input. This renders AdVent semi-functional, but it could be still useful in some scenarios. Another disadvantage of using a microphone is noisy sound decreasing recognition efficiency. On the other side, this input requires no wired connection to a TV-set. Also, on systems equipped with a mike it is usually set as default audio input, so no special setup is required to use it.
Turn on TV and test recording:
$ parecord -v test.wav
Opening a recording stream with sample specification 's16le 2ch 44100Hz' and channel map 'front-left,front-right'.
Connection established.
Stream successfully created.
Buffer metrics: maxlength=4194304, fragsize=352800
Using sample spec 's16le 2ch 44100Hz', channel map 'front-left,front-right'.
Connected to device alsa_input.pci-0000_00_1b.0.analog-stereo (index: 46, suspended: no).
Time: 5.888 sec; Latency: 1888172 usec.
...
(Ctrl-C)
$
The resulting file should reproduce TV sound reasonably well. If not, try putting the microphone closer to the source, or use a better quality external microphone instead of a built-in one.
Instructions below are for Fedora. I do not have an equivalent for Raspbian, because I use Raspberry Pi to capture from a real TV rather than from Web.
Note that depending on your TV feed provider, live sound capturing might be considered as violation of provider's ToS. As a matter of fact, AdVent is not recording anything, but just listens to a live feed the same way a person would listen. To do this, we make use of PulseAudio "monitor" function, which allows using an audio output ("sink") as a source for another application.
Check the list of available audio sources:
$ pactl list short sources
45 alsa_output.pci-0000_00_1b.0.analog-stereo.monitor PipeWire s32le 2ch 48000Hz IDLE
46 alsa_input.pci-0000_00_1b.0.analog-stereo PipeWire s32le 2ch 48000Hz SUSPENDED
$
On laptops and alike, by default, the sound source used is a built-in mike (hiding behind alsa_input.pci-0000_00_1b.0.analog-stereo here). We need to switch the default to the speaker monitor (the exact label in your case may be different, but the .monitor part is important):
$ pactl set-default-source alsa_output.pci-0000_00_1b.0.analog-stereo.monitor
Big advantage of a "monitor" is that it samples sound before it goes to a sink. So muting a PulseAudio sink (see TV Controls with PulseAudio) would let AdVent continue listening to the cast, exactly as needed. And, of course, the chain is fully digital, so no sound loss or distortion occurs.
Start your web cast and test recording:
$ parecord -v test.wav
Opening a recording stream with sample specification 's16le 2ch 44100Hz' and channel map 'front-left,front-right'.
Connection established.
Stream successfully created.
Buffer metrics: maxlength=4194304, fragsize=352800
Using sample spec 's16le 2ch 44100Hz', channel map 'front-left,front-right'.
Connected to device alsa_output.pci-0000_00_1b.0.analog-stereo.monitor (index: 45, suspended: no).
Time: 4.608 sec; Latency: 608164 usec.
...
(Ctrl-C)
$
The resulting file should reproduce TV sound correctly.
Note that PulseAudio tries to remember which sources applications use, so if you happened to run AdVent before, it might still not use the new default. The easiest way to confirm the source is to launch pavucontrol while AdVent is running and check in the "Recording" tab that it uses the "monitor" input:
Here, by the way, we can observe three parallel threads at work. The fourth one has a low duty cycle, so it comes and goes, causing some flickering in apps like pavucontrol.
Supported on Raspberry Pi using HiFiBerry Digi+ I/O sound card.
With this card, one can use optical TOSLINK or coaxial RCA cables. I use an optical one, but RCA should work the same. On the following example of Sony BRAVIA the cable from the Pi needs to be connected to the port F (Digital Audio Out, Optical):
Setup compiled on the basis of the original installation instruction:
This sound card does not support Dolby Digital, so if the channels of interest in your area broadcast in Dolby, you need to enforce PCM on TV side. You can find out the audio format by looking at the TV channel information (Info, Details, etc). Refer to the instruction for your TV-set. Example of channels in PCM and in Dolby Digital:
In the case of Sony BRAVIA, adjusting the format can be done in Digital Setup > Audio Setup > Optical Out: change Auto to PCM:
Another particularity of this sound card is that it requires a carrier signal (red light in the optical cable) at all times to function. In absence of the signal, e.g., when the TV is off, it would just block itself and the application using it. For a user it would look like AdVent would stop printing progress characters, while consuming all CPU available. TV-sets often offer a choice of how turning off should be managed: a hot standby or an "eco" power down. In standby mode the optical output usually remains powered. If you plan running AdVent continuously, give preference to this mode.
Edit /boot/config.txt to enable HiFiBerry and disable all other sound devices:
57c57
< dtparam=audio=on
---
> #dtparam=audio=on
61c61
< dtoverlay=vc4-fkms-v3d
---
> dtoverlay=vc4-fkms-v3d,audio=off
65a66,67
>
> dtoverlay=hifiberry-digi
S/PDIF PCM comes sampled in 48 kHz, while PulseAudio defaults to 44.1 kHz. If the sampling rate is not matched, recorder will see garbage. In addition, Dejavu inherently works in 44.1 kHz (the frequency setting it is not just a matter of input sampling, but is also used internally during recognition process). So the easiest way is to configure PulseAudio to a primary frequency of 48 kHz and to activate software down-sampling to 44.1 kHz. Edit /etc/pulse/daemon.conf to uncomment and enable these lines:
...
> default-sample-rate = 48000
...
> alternate-sample-rate = 44100
...
Now reboot:
$ sudo reboot
Check that system can see your sound card:
$ arecord -l
**** List of CAPTURE Hardware Devices ****
card 0: sndrpihifiberry [snd_rpi_hifiberry_digi], device 0: HifiBerry Digi HiFi wm8804-spdif-0 [HifiBerry Digi HiFi wm8804-spdif-0]
Subdevices: 1/1
Subdevice #0: subdevice #0
$
Record a test track using default settings:
$ parecord -v test.wav
Opening a recording stream with sample specification 's16le 2ch 44100Hz' and channel map 'front-left,front-right'.
Connection established.
Stream successfully created.
Buffer metrics: maxlength=4194304, fragsize=352800
Using sample spec 's16le 2ch 44100Hz', channel map 'front-left,front-right'.
Connected to device alsa_input.platform-soc_sound.iec958-stereo (index: 1, suspended: no).
Time: 2.602 sec; Latency: 6901 usec.
...
(Ctrl-C)
$
The resulting file test.wav recorded in 44.1 kHz shall reproduce TV sound correctly.
Note 1: HiFiBerry manuals recommend disabling all other audio devices, so you won't be able to listen to the recorded file right on the Pi (unless you hook up something PCM-enabled - like a home theater - to the output connector of HiFiBerry). I just copy the file to another machine where I can playback. If this behavior is undesirable, play around with options in /boot/config.txt. Pay attention that the default input device remains the sound card; otherwise AdVent will not work.
Note 2: HifiBerry manuals strongly recommend against using PulseAudio in general, and against software re-sampling in particular, citing performance concerns. From my experience, PulseAudio is easy to configure (much easier than ALSA) and works well, but indeed, would consume ~5% of the Pi CPU (20% if used from four threads, the other 80% would be eaten up by Dejavu). And all that is for entire PulseAudio machinery, not just for down-sampling; I find this very affordable. For sure, for purists it should be possible to eliminate this margin by turning PulseAudio off and going down to ALSA level; however, I have not pursued these roads too far:
a) configure down-sampling on the level of ALSA (something I could not easily make, but should be possible), or
b) hack Dejavu to consume 48 kHz directly. I actually tested that it works, but the impact on recognition efficiency is unclear. Jingle fingerprints are taken at 44.1 kHz, so one might expect side effects. Dejavu has known bugs standing to date when working with sample rates different from 44.1 kHz.
Another advantage of PulseAudio is that it allows access to a sound source from multiple processes. By default, it is usually only one process which can use a sound card. This is certainly true and documented for HiFiBerry. AdVent runs several threads reading sound input in parallel. While these threads remain all part of the same process, it is unclear if it would still work through ALSA.
As mentioned above, AdVent is a CPU-intensive application. This directly translates to increase of the Pi CPU temperature. Adding a sound card shield on top does not help with ventilation either. You can check CPU temperature as follows:
$ vcgencmd measure_temp
temp=52.1'C
$ vcgencmd get_throttled
throttled=0x0
$
Be sure to observe the temperature of your setup. In my case it rises from 50 to 60℃ when AdVent is running. Anything between 70 and 80℃ is a danger zone. If throttled reads non-zero, it means you are hitting (or were hitting some time since boot) system limits, so the system fights overheating by decreasing CPU frequency. This, in turn, would decrease already capped AdVent performance. If this happens, it is better to tune AdVent to avoid going into overheating. Consider the following tips:
- delete from the database TV channels which you are not expected to watch (see database update instructions);
- vacuum the database regularly (see database vacuuming);
- reduce the number of threads (
-noption to AdVent, see recognition tuning).
Consider also tuning the hardware:
- make sure you have a good power supply (at least 3 A for Pi 4B; 3.5 A recommended);
- use heat sinks for principal chips (sold separately). I do have some; they are really helpful. If you haven't got heat sinks, at least position Pi vertically on a side with a 1-2 cm air gap at the bottom, so that convection could provide for some air flow;
- if you put the entire device in a case, foresee active cooling (a fan).
TV controls could be uni- or bi-directional. A typical example of a uni-directional control is an infra-read remote. Bi-directional controls allow AdVent fetching the current TV status, so it could start in sync. With uni-directional controls AdVent has to make assumptions about status of TV, which would be reasonable most of the time, but not always. Below is a summary of supported controls:
| TV Control | Type |
|---|---|
| Nil | Bi-directional |
| PulseAudio | Bi-directional |
| HarmonyHub | Uni-directional |
| BroadLink | Uni-directional |
(selected with -t nil option to AdVent)
This control emulates a real TV control without making any action. A TV is presented as possessing volume scale 0-100, and all operations always succeed. This mode is of interest for recognition testing purposes, in partucular when training AdVent to recognize new jingles.
(selected with -t pulseaudio option to AdVent; default)
"TV" control when watching a TV web cast on a computer consists of muting the currently active speaker. On Linux with PulseAudio it is as simple as:
$ pactl set-sink-mute @DEFAULT_SINK@ toggle
AdVent does just that. Another advantage with PulseAudio is that the application will query the status of speaker on startup and thus start in sync.
(selected with -t harmonyhub option to AdVent)
I have been using this device for TV control from a smartphone since long time. Unfortunately, it is no longer sold nor supported by Logitech, and I no longer have the device in my possession, so it might be phased out with the next major version of AdVent. The code for it is still maintained, but the last version of AdVent tested with real hardware was 1.5.0. If you happen to test a later version, please signal, or submit fixes if you encounter a problem.
Apart from the default cloud interface, Harmony Hub it can also provide a local API, which is convenient for AdVent needs.
Unfortunately, since the underlying mechanism is to send commands over IrDA (pretty much like a regular TV remote), it can offer no insight as to the current status of TV. So AdVent will assume that TV runs unmuted on startup (which should be fine in most cases) and will act on the basis of this information.
The local API is not enabled by default; you need to activate it in Harmony application as follows: Menu > Harmony Setup > Add/Edit Devices & Activities > Hub > Enable XMPP.
To talk to the Hub we will be using a nice piece of software called Harmony API. It is a NodeJS server with HTTP interface running on your Linux box (in this case, next to AdVent). Follow these steps to set it up on Fedora (on Raspbian, just replace root # ... commands with $ sudo ...):
Unfortunately, Linux installer is not yet included in any release of Harmony API, so we need to pull the latest master:
$ git clone https://github.com/maddox/harmony-api.git
Pre-configure Harmony API:
# npm install forever -g
$ ./harmony-api/script/bootstrap
Install it system-wide using root permissions:
# ./harmony-api/script/install-linux
Alas, this installation uses a non-canonical location placing executables in /var/lib, so SELinux on Fedora would be unhappy about it. Label the executable file as follows (not required on Raspbian which has got no SELinux):
# semanage fcontext -a -t var_run_t /var/lib/harmony-api/script/server
# restorecon -v /var/lib/harmony-api/script/server
Another Fedora-specific issue is its firewall which would by default block attempts to discover Hubs. Enable discovery port as follows (not required on Raspbian which has got no firewall):
# firewall-cmd --permanent --add-port=61991/tcp
Finally, we can start our server:
# systemctl start harmony-api-server
In a browser, open address localhost:8282 (if you run the browser on a different machine, use the Harmony API machine's IP-address instead of localhost). In the section "Your Hubs" you should see your hub listed:
Caveat: if you are coming out of cold boot like a power cycle, Pi might initialize itself faster than Harmony. In this case the hub would not be listed. The solution is to restart the harmony-api-server.
In a shell, run this command to test TV control:
$ curl -s -S -d on -X POST http://localhost:8282/hubs/harmony/commands/mute
It shoud mute the TV. Run it again to unmute.
Caveat2: this simplistic command will try muting all devices known to Harmony. Usually, there's only a TV, so it is not an issue. If you have got other devices hooked to Harmony, you might need to opt for a more precise path. Please open a ticket if you need support for this.
Note that AdVent relies on default Hub name which is Harmony. If your Hub name is different, the name needs to be corrected in the source code (and in the test command above). It there would be demand, it is possible to make a command line option for this (issue #17).
(selected with -t broadlink option to AdVent)
BroadLink Universal Remote can emulate a wide range of infra-red or radio signals. It also offers a local API and is remarkably reliable at the expense of being less intelligent than HarmonyHub. There are several generations and flavors available; I have RM4 Pro.
It is assumed that you have already connected the Remote to your network using BroadLink app. If not, refer to instructions from BroadLink. The Remote must be in the same network where AdVent would be running. In the default configuration, the Remote is not discoverable (BroadLink calls this a "locked device"). AdVent would need the Remote to answer to discovery queries, so you need to unlock it in the app:
Note 1: it is possible to use the Remote in locked mode, but one would need to specify an IP-address of the device. Currently it is not supported by AdVent; raise a request if you need it.
Note 2: it is assumed that there is only one Remote present in the network. If there are multiple devices present, AdVent will select the first one returned from the discovery process. Raise a request if you need finer control over this.
Similarly to HarmonyHub, the firewall on Fedora would block attempts to discover BroadLink devices, so you need to authorize it on the firewall:
# firewall-cmd --permanent --add-source-port=80/udp
No action needed on Raspbian.
A typical Remote setup from the BroadLink app would require teaching the Remote to recognize your TV-set using a remote supplied with the TV. Unfortunately, there is no way to reuse that information outside of BroadLink app (this is why I call it "less intelligent" than HarmonyHub), so you'd need to repeat the learning process specifically for the commands of interest for AdVent - that is, mute, volume down and volume up. The easiest way to do that is to use command-line tools from Python broadlink package. Again unfortunately, for some reason these tools are not included in the Python module, so you have to grab them from GitHub:
$ git clone https://github.com/mjg59/python-broadlink.git
$ cd python-broadlink/cli
Run discovery:
$ ./broadlink_discovery
Discovering...
###########################################
RM4PRO
# broadlink_cli --type 0x5213 --host 192.168.0.100 --mac aabbccddeeff
Device file data (to be used with --device @filename in broadlink_cli) :
0x5213 192.168.0.100 aabbccddeeff
temperature = 22.3
$
The broadlink_cli line above should be reused for subsequent learning process. Run broadlink_cli with your parameters, point your TV remote to BroadLink Remote and press the button of interest:
$ ./broadlink_cli --type 0x5213 --host 192.168.0.100 --mac aabbccddeeff --learnfile mute-toggle.code
Learning...
(press Mute button)
Saving to mute-toggle.code
$ ./broadlink_cli --type 0x5213 --host 192.168.0.100 --mac aabbccddeeff --learnfile volume-down.code
Learning...
(press Volume-Down button)
Saving to volume-down.code
$ ./broadlink_cli --type 0x5213 --host 192.168.0.100 --mac aabbccddeeff --learnfile volume-up.code
Learning...
(press Volume-Up button)
Saving to volume-up.code
$
Move the control codes to their final location:
$ mkdir ~/tv-codes
$ mv *.code ~/tv-codes
Note 1: do not change the names of the files, or else AdVent would not be able to find them.
Note 2: if you do not want the tv-codes folder in your home folder, you can specify a different location with -d option to AdVent, or simply make a symbolic link from your home.
Run command to test TV control:
$ ./broadlink_cli --type 0x5213 --host 192.168.0.100 --mac aabbccddeeff --send @$HOME/mute-toggle.code
It shoud mute the TV. Run it again to unmute.
Caveat: The latest version 0.19.0 of Python BroadLink support has a bug mjg59/python-broadlink#721 affecting the lower_volume mode of AdVent. The bug consists of inadvertent duplication of commands sent to the Remote. Due to this, the volume would be lowered more than asked (-V option to AdVent), and similarly raised to a greater volume in the opposite direction. The resulting volume might not necessarily be equal to the original volume.
It is possible to use AdVent for purposes other than controlling a TV - e.g., to detect some ambient sounds and to send notifications or operate domotics. The engine should be basically OK; you'd just need to fingerprint samples of the sound of interest. However, to program reactions, you'd need to write a few lines of Python to provide a fake tv_control module doing what's needed.
Note that the current setup is optimized for sounds of a few seconds length. It should work for sharp sounds less than a second long as long as you can use the listening interval of at least one second. If you'd need shorter intervals, you'd have to do your own Dejavu tuning.
TV video input is not connected nor used. Audio matching represents a completely in-memory operation (no audio recording of any kind is performed), and a local copy of the online database is used for matching (no active network connection needed), so the information on what a person is watching on TV does not leave the local controller, and is not logged in any form on its persistent storage medium.