Before I go down a hole and end in a dead end....
I have some questions on using the -L option for "logging."
Logging in my universe means logging the audio to Dictaphone/tape/disk/CD/what
ever physical media... NOT the -v option, thats a log, not logging. :) ;)
So after reading about 30 different files on this -L option, it
appears that it
will act as A LOGGING RECORDER and RECORD the audio to disk... Great!
What I am after is to record UNKNOWN GROUPS for analysis for ID purposes....
My question(s) are what options are used with this for:
rx.py
trunk.tsv
whitelist.tsv
blacklist.tsv
ie:
rx.py example
./rx.py --args 'rtl' -N 'LNA:47' -S 2400000 -f 8xx.xxxxe6 -o 25000 -q 72
-L 4
-v 10 -T trunk.tsv -V -2 -U -O loop0 -M mysystem.json -l
http:192.168.0.26:8080 -x 3 2>> stderr.2
trunk.tsv then REQUIRES a "center frequency" for the system... 8xx.xxxx based
on the channels of the system... I've determined this for this system,
and it will just fit the way this is setup.
This will then RECORD the various groups that are NOT BLACKLISTED to disk as
WAV's from what I understand... Correct????
Ie: OP25 tunes to a group, it records it.
Anything that is exclusive of each other on this -L option with other optons
for rx.py????
Any thing I am missing in this?????
Goal is simple to log any group I've not blacklisted as known user/use..
Thanks.
Show replies by date
hello
The "-L X" (where X is the number of workers) option is used to make rx.py log
all trunked activity to a series of WAV files each containing (typically) a single
transmission. The talkgroups that get logged can be controlled as usual by blacklists and
whitelists. If you know in advance the list of TGs you want and are sure that those are
the only ones you want, use a whitelist. Conversely use a blacklist if you know in
advance the list of TGs you don't want. It's nonsensical to have both lists at
once.
Other than that I'd suggest if you have any specific questions or operation issues,
please raise them here.
Finally should note there's another option you might want to look into, Luke's
"Trunk Recorder" app may also be of interest. It's derived from OP25...
Max
On Thursday, January 17, 2019, 9:19:48 AM EST, op25(a)zellners.com
<op25(a)zellners.com> wrote:
Before I go down a hole and end in a dead end....
I have some questions on using the -L option for "logging."
Logging in my universe means logging the audio to Dictaphone/tape/disk/CD/what
ever physical media... NOT the -v option, thats a log, not logging. :) ;)
So after reading about 30 different files on this -L option, it
appears that it
will act as A LOGGING RECORDER and RECORD the audio to disk... Great!
What I am after is to record UNKNOWN GROUPS for analysis for ID purposes....
My question(s) are what options are used with this for:
rx.py
trunk.tsv
whitelist.tsv
blacklist.tsv
ie:
rx.py example
./rx.py --args 'rtl' -N 'LNA:47' -S 2400000 -f 8xx.xxxxe6 -o 25000 -q 72
-L 4
-v 10 -T trunk.tsv -V -2 -U -O loop0 -M mysystem.json -l
http:192.168.0.26:8080 -x 3 2>> stderr.2
trunk.tsv then REQUIRES a "center frequency" for the system... 8xx.xxxx based
on the channels of the system... I've determined this for this system,
and it will just fit the way this is setup.
This will then RECORD the various groups that are NOT BLACKLISTED to disk as
WAV's from what I understand... Correct????
Ie: OP25 tunes to a group, it records it.
Anything that is exclusive of each other on this -L option with other optons
for rx.py????
Any thing I am missing in this?????
Goal is simple to log any group I've not blacklisted as known user/use..
Thanks.