From: Adam Nielsen <a.nielsen@shikadi.net>
To: linux-dvb@linuxtv.org
Subject: [linux-dvb] dvbstream reliability issues?
Date: Thu, 20 Mar 2008 18:57:11 +1000 [thread overview]
Message-ID: <47E226E7.7030601@shikadi.net> (raw)
Hi all,
I've recently started using dvbstream (instead of dvbrecord) to record
shows using cron but I'm finding it to be very unreliable.
Depending on my reception quality, it has a tendency to segfault fairly
regularly - enough that I wrote a script to reload it after a segfault
so that I wouldn't miss my recording. With this set up it usually
segfaults once every 15 minutes or so, and sometimes as often as every
4-5 minutes if the reception isn't so great.
Sometimes it doesn't segfault though, it just stops recording for some
reason (the output file only grows by a few bytes a minute.) This is
worse because it doesn't terminate, so my script isn't able to reload it
to catch the rest of the recording.
For those people using dvbstream to do their recording, are any of you
having issues like this?
I'm running CVS from 2008-02-24 and I'm using -prog to record based on
the program instead of using PIDs (as our broadcasters here seem to
change their PIDs without warning every couple of months.)
I'm hoping there's some easy fix for this, because I'd rather not have
to try to get dvbrecord to work again!
Thanks,
Adam.
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next reply other threads:[~2008-03-20 8:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 8:57 Adam Nielsen [this message]
2008-03-20 9:02 ` [linux-dvb] dvbstream reliability issues? Nico Sabbi
2008-03-21 0:54 ` Adam Nielsen
2008-03-21 8:52 ` Nico Sabbi
2008-03-24 18:35 ` Nico Sabbi
2008-03-24 23:23 ` Adam Nielsen
2008-03-29 9:25 ` Nico Sabbi
2008-03-29 11:33 ` Adam Nielsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47E226E7.7030601@shikadi.net \
--to=a.nielsen@shikadi.net \
--cc=linux-dvb@linuxtv.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox