-
-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Record plugin #327
base: develop
Are you sure you want to change the base?
Record plugin #327
Conversation
Has this been tested? I've applied your changes and don't get any alarms afterwards. So there seems to be a problem with the splitting of the audio stream (via tee) for multimon. Can you help me? The log file doesn't show any alarms. |
Could this be a problem with buffering of pipe/tee? |
Any ideas @Schrolli91 @dk5ra ? I'm trying to find out where the problem is for three days now.. |
@grinsekatze003 The problem concerning the scrambled voice is more a problem of decoding (switch -M and option fm or nfm) |
@grinsekatze003 whats your os? this record plugin works only on linux. tested on raspbian and ubuntu 17.10 you need to make sure that this is set Its just a quick and dirty plugin. Don't know how we can record the stream without play and record from the .monitor device. |
@dk5ra OS is raspbian. Yes I did start in daemon mode. rtl_fm and multimon gets started fine, but multimon doesn't detect any alarms. It appears to me that the pipe construct causes problems and multimon doesn't get any input from rtl_fm. Yes, I've set up the pulseaudio sink as you suggested, but I don't think that this is the problem because multimon doesn't detect any alarms before. So you say that the plugin is perfectly fine working for you and you still get the alarms with multimon? @flothi I've answered you in the issue. |
Okay, after further investigating, I can say that there is something wrong with this plugin. But I don't know why. Using this plugin makes the detection rate of alarms worse. This has to do something with the I've used your plugin for 12 hours now and no alarm was detected. Afterwards I removed the plugin, restarted boswatch and it detects alarms again - without touching/moving the antenna/raspberry. The strange thing is that I nevertheless have received alarms using your plugin too - so it works but it makes the whole thing flaky for me. Do you have any ideas what I can try @dk5ra @Schrolli91 @flothi ? |
Until now I didn't test anything regarding this plugin due to a lack of time But maybe I can take a closer look at it during the next few days, but a comment from the author would be the best... @dk5ra |
@flothi That'd be great! I'm struggling a few days now. Maybe it's a deadlock / buffer situation of pipe in combination with tee. Who knows. |
Short and dirty record-plugin which records into a directory a wave file with a specified time(config file)
to use it its important to use pulseaudio
ADD THIS TO YOUR Pulseaudio config file /etc/pulse/default.pa
load-module module-null-sink sink_name=playbackstream
update-sink-proplist playbackstream device.description=playbackstream
load-module module-loopback sink=playbackstream
set-default-sink playbackstream
set-default-source playbackstream.monitor
Created a copy of the rtl_fm.stdout pipe and piped it to paplay and multimon-ng
aplay playes the sound to the default sink and parecord records from the default sink
WARNING: on the alsa-utils standard rpi deb 1.0.28 parecord does not quit byself and create many useless files. I tested 1.1.13 and 1.1.14. You can compile that quick an the rpi
To access to the records you can setup a "cloud" like seafile,owncloud,syncthing and so on and access from the mobile to it. Did not implement some sending feature for telegram,email or so. Because you need to wait until the recording is finished and then send it. Could implement but this would be a very very dirty script maybe some of you have a idea
feel free to be critical and discuss