hiveeyes / saraswati Goto Github PK

Hi there,

at [1], @MKO1640 outlined some problems connecting to his Synology Diskstation using rsync with SSH key-based authentication.

With kind regards,
Andreas.

[1] https://community.hiveeyes.org/t/system-fur-kontinuierliche-audio-aufzeichnung-bob-projekt-phase-2/4048/11

Hi there,

at [1], it was suggested by weef to make the lossless WavPack codec available to the Saraswati recording subsystem. The corresponding GStreamer element would be wavpackenc.

With kind regards,
Andreas.

[1] https://community.hiveeyes.org/t/developing-saraswati-a-robust-multi-channel-audio-recording-transmission-and-storage-system/924/19

Hi again,

at https://community.hiveeyes.org/t/system-fur-kontinuierliche-audio-aufzeichnung-bob-projekt-phase-1/728/71 ff, @ClemensGruber and @MKO1640 are discussing whether it will make sense to also support storing recorded audio into an .ogg container instead of an .mka (Matroska).

With kind regards,
Andreas.

Hi there,

extending the scope of Saraswati, we discussed a feature to make it possible to tap into a recording channel (i.e. GStreamer pipeline) in playing state. For this to happen, we need two mechanisms:

• A signalling pathway to tell a running Saraswati instance about an interest on one or more specific audio channels.
• A subsystem to attach another sink element to an existing GStreamer pipeline in order to output/send the selected audio channels to another system which, in turn, will be able to broadcast the audio stream to any number of "live" listeners.

With kind regards,
Andreas.

Hi there,

in order to reduce wear on the SD card when running Saraswati on SBC-like computer systems, the spool directory /var/spool/saraswati should be able to be configured as RAM disk, see [1].

It would be sweet to make those configuration steps available under the saraswati setup subcommand.

With kind regards,
Andreas.

[1] https://github.com/hiveeyes/saraswati/blob/0.6.0/doc/setup-production.rst#using-a-ram-disk

Hi there,

when invoking sudo saraswati setup --systemd, Saraswati installs itself as a systemd unit. For that, it uses the saraswati.service systemd unit definition file.

@MKO1640 reported a problem with that at https://community.hiveeyes.org/t/installation-von-saraswati-auf-einem-industrie-pc-mit-upload-auf-synology-nas/4048/39:

There is also a small problem with the USB microphones. They are not always recognized by the GStreamer after a reboot. They have to be unplugged once and plugged in again.

With lsusb, the microphones are also always recognized. But it also recognizes 2 internal Linux USB hubs.
With my test computer I could not reproduce the problem so far.

He already offers a probable suggestion for the root cause:

I guess that the service starts before the USB is initialized and therefore it doesn't work. So it might be enough to restart ALSA and GStreamer before Saraswati.

With kind regards,
Andreas.

/cc @ClemensGruber