Beiträge anzeigen

Diese Sektion erlaubt es ihnen alle Beiträge dieses Mitglieds zu sehen. Beachten sie, dass sie nur solche Beiträge sehen können, zu denen sie auch Zugriffsrechte haben.


Nachrichten - derabbink

Seiten: [1]
1
Sundtek Streaming Server / Re:Sundtek Streaming Server
« am: Juni 16, 2016, 10:05:06 Vormittag »
Der streaming server (installiert zusammen mit dem OS X Treiber release von gestern http://support.sundtek.com/index.php/topic,544.msg3076.html) ist wirklich vielversprechend! Allerdings hat VLC einige Schwierigkeiten die streams zu öffnen.
Häufig dauert es sehr lange bis VLC eine Verbindung herstellen kann, und wenn es dann klappt, wird nur das erste keyframe angezeigt, ohne Folgebilder, und ohne Ton.

PS: gibt es eine Möglichkeit um den server zu stoppen? In der Web UI habe ich dazu keine Option gefunden.

2
Software / Re:Tvheadend: TS Sync byte not aligned, realigning stream
« am: Juni 10, 2014, 08:28:16 Nachmittag »
Just to sum things up after today's skype support.

1) Thank you for the expert support, Sundtek :)
2) It turned out that using a different USB port (one that's powered by a different USB controller) did the trick!
I can now watch TV with Tvheadend.

3
Software / Tvheadend: TS Sync byte not aligned, realigning stream
« am: Juni 08, 2014, 10:37:58 Nachmittag »
Hi,
I am trying to use Tvheadend with my MediaTV Pro III, but I'm having some trouble.

I modified /etc/sundtek.conf to enable full logging, and restarted the mediasrv driver. If I then I start Tvheadend, I get tons of messages like the following in /var/log/mediasrv.log: "TS Sync byte not aligned, realigning stream". The only way to make it stop is to kill Tvheadend.

When I disable logging, of course I'm not getting this flood of log messages, and I can actually use Tvheadend to scan for Muxes and services (which it successfully did before).

What is wrong with my configuration that is producing megabytes of these messages every second?

4
Drivers / Re:mediasrv startup process
« am: Mai 26, 2014, 10:23:25 Nachmittag »
Thanks for the detailed response.
What I have learned from that, is that essentially the systemd script/symlink could be deleted, as it does not play a role on ubuntu; even though the --systemdcheck option is provided in the udev script.

I tried to understand the --systemdcheck option, but mediaclient --help only sais "start via systemd if available". I don't know what that means.
The mediaclient wiki page does not mention this option either.

5
Drivers / mediasrv startup process
« am: Mai 26, 2014, 07:13:57 Nachmittag »
I installed the latest driver (May 10, 2014) on ubuntu 14.04 and ran ps aux | grep mediasrv. I found that the mediasrv driver process is running as user root, and I was wondering if this was really necessary.

So, I started looking around my system where this process is started. I found two possible places:
  • /etc/udev/rules.d/80-mediasrv-eeti.rules
    Inside this file, it sais:
    SUBSYSTEM=="usb", ACTION=="add", RUN+="/opt/bin/mediaclient --start=5 --systemdcheck"
    Which made me check the systemd directory.
  • /etc/systemd/system/multi-user.target.wants/sundtek.service which is a soft link to /usr/lib/systemd/system/sundtek.service
    First of all, this link target does not exist, so the installer must be broken/buggy for my system.
    What does exist, is the file /lib/systemd/system/sundtek.service (no /usr/ at the beginning)
    The contents of this file are (in part) ExecStart=/opt/bin/mediaclient --start=4 and ExecStop=/opt/bin/mediaclient --shutdown

I'm not entirely sure on this, but the way I think this works is the following:
mediasrv is not started during boot by the /lib/systemd/system/sundtek.service file, because the soft link /etc/systemd/system/multi-user.target.wants/sundtek.service points to the wrong file.
That leaves udev to start the service when hotplugging. Is this correct?

Coming back to my initial curiosity: "Does mediasrv have to run as root?", I think not (right?), but I'm reluctant to edit the /etc/udev/rules.d/80-mediasrv-eeti.rules file, if the service is supposed to be started by systemd. In case of the latter, can I just fix the symlink to the systemd script and change that to run mediasrv (via mediaclient) as a different user?

6
Sundtek MediaTV Pro (Europe) / Not working with VirtualBox
« am: Mai 19, 2014, 06:50:16 Nachmittag »
I have a MediaTV Pro III that I want to use for DVB-C. I currently trying to figure out how everything works using an Ubuntu 12.04 x86_64 VM, hosted by VirtualBox.
On my provider's network, at least one DVB-C channel is unprotected and freely available.

The problem I have is that scanning, using the scan and dvbscan utils, does not seem to work:
Code: [Auswählen]
$ scan /usr/share/dvb/dvb-c/nl-Ziggo
scanning /usr/share/dvb/dvb-c/nl-Ziggo
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
initial transponder 372000000 6875000 0 3
initial transponder 514000000 6875000 0 3
initial transponder 356000000 6875000 0 3
initial transponder 369000000 6875000 0 3
>>> tune to: 372000000:INVERSION_AUTO:6875000:FEC_NONE:QAM_64
WARNING: filter timeout pid 0x0011
WARNING: filter timeout pid 0x0000
WARNING: filter timeout pid 0x0010
>>> tune to: 514000000:INVERSION_AUTO:6875000:FEC_NONE:QAM_64
WARNING: >>> tuning failed!!!
>>> tune to: 514000000:INVERSION_AUTO:6875000:FEC_NONE:QAM_64 (tuning failed)
WARNING: >>> tuning failed!!!
>>> tune to: 356000000:INVERSION_AUTO:6875000:FEC_NONE:QAM_64
WARNING: >>> tuning failed!!!
>>> tune to: 356000000:INVERSION_AUTO:6875000:FEC_NONE:QAM_64 (tuning failed)
WARNING: >>> tuning failed!!!
>>> tune to: 369000000:INVERSION_AUTO:6875000:FEC_NONE:QAM_64
WARNING: >>> tuning failed!!!
>>> tune to: 369000000:INVERSION_AUTO:6875000:FEC_NONE:QAM_64 (tuning failed)
WARNING: >>> tuning failed!!!
dumping lists (0 services)
Done.

$ dvbscan /usr/share/dvb/dvb-c/nl-Ziggo
Unable to query frontend status
I installed the latest drivers from the .deb file. What I noticed is that there is currently no /etc/sundtek.conf file on my system; the installer didn't create one.
In my VirtualBox USB configuration, I have checked "USB 2.0 (EHCI) Controller". This may be relevant, considering my /var/log/mediaclient.log (see below) and this post.

How can I make this work on VirtualBox?

I set the logging level to max (/opt/bin/mediaclient --loglevel=max) and this is what I got in /var/log/mediasrv.log while trying to scan:
Code: [Auswählen]
//log corresponding to scan command
2014-05-19 18:00:20 [3232] Waking up in digital TV mode
2014-05-19 18:00:22 [3232] Power up demodulator
2014-05-19 18:00:43 [3232] SETTING DVB-C
2014-05-19 18:00:43 [3232] Setting Frequency: 369000000
2014-05-19 18:00:43 [3232] Setting Symbolrate: 6875000
2014-05-19 18:00:43 [3232] Setting Modulation: 3
2014-05-19 18:00:43 [3232] setting symbolrate: 6875
2014-05-19 18:00:43 [3232] Tuning DVB-C Frequency: 369000000
2014-05-19 18:00:43 [3232] Setting Frequency: 372000000
2014-05-19 18:00:43 [3232] Setting Symbolrate: 6875000
2014-05-19 18:00:43 [3232] Setting Modulation: 3
2014-05-19 18:00:43 [3232] setting symbolrate: 6875
2014-05-19 18:00:43 [3232] Tuning DVB-C Frequency: 372000000
2014-05-19 18:00:44 [3232] Resetting TS Port
2014-05-19 18:00:46 [3232] Resetting TS Port
2014-05-19 18:00:48 [3232] Resetting TS Port
2014-05-19 18:00:50 [3232] Resetting TS Port
2014-05-19 18:00:52 [3232] Resetting TS Port
2014-05-19 18:00:54 [3232] Resetting TS Port
2014-05-19 18:00:56 [3232] Resetting TS Port
2014-05-19 18:00:58 [3232] Resetting TS Port
2014-05-19 18:01:00 [3232] Resetting TS Port
2014-05-19 18:01:00 [3232] Setting Frequency: 514000000
2014-05-19 18:01:00 [3232] Setting Symbolrate: 6875000
2014-05-19 18:01:00 [3232] Setting Modulation: 3
2014-05-19 18:01:00 [3232] setting symbolrate: 6875
2014-05-19 18:01:00 [3232] Tuning DVB-C Frequency: 514000000
2014-05-19 18:01:07 [3232] Setting Frequency: 514000000
2014-05-19 18:01:07 [3232] Setting Symbolrate: 6875000
2014-05-19 18:01:07 [3232] Setting Modulation: 3
2014-05-19 18:01:07 [3232] setting symbolrate: 6875
2014-05-19 18:01:07 [3232] Tuning DVB-C Frequency: 514000000
2014-05-19 18:01:14 [3232] Setting Frequency: 356000000
2014-05-19 18:01:14 [3232] Setting Symbolrate: 6875000
2014-05-19 18:01:14 [3232] Setting Modulation: 3
2014-05-19 18:01:14 [3232] setting symbolrate: 6875
2014-05-19 18:01:15 [3232] Tuning DVB-C Frequency: 356000000
2014-05-19 18:01:22 [3232] Setting Frequency: 356000000
2014-05-19 18:01:22 [3232] Setting Symbolrate: 6875000
2014-05-19 18:01:22 [3232] Setting Modulation: 3
2014-05-19 18:01:22 [3232] setting symbolrate: 6875
2014-05-19 18:01:22 [3232] Tuning DVB-C Frequency: 356000000
2014-05-19 18:01:29 [3232] Setting Frequency: 369000000
2014-05-19 18:01:29 [3232] Setting Symbolrate: 6875000
2014-05-19 18:01:29 [3232] Setting Modulation: 3
2014-05-19 18:01:29 [3232] setting symbolrate: 6875
2014-05-19 18:01:29 [3232] Tuning DVB-C Frequency: 369000000
2014-05-19 18:01:36 [3232] Setting Frequency: 369000000
2014-05-19 18:01:36 [3232] Setting Symbolrate: 6875000
2014-05-19 18:01:36 [3232] Setting Modulation: 3
2014-05-19 18:01:36 [3232] setting symbolrate: 6875
2014-05-19 18:01:36 [3232] Tuning DVB-C Frequency: 369000000
2014-05-19 18:01:59 [3232] Enabling Standby

//log corresponding to dvbscan command
2014-05-19 18:06:01 [3232] Waking up device
2014-05-19 18:06:01 [3232] Waking up in digital TV mode
2014-05-19 18:06:03 [3232] Power up demodulator
2014-05-19 18:06:24 [3232] SETTING DVB-C
2014-05-19 18:06:24 [3232] Setting Frequency: 369000000
2014-05-19 18:06:24 [3232] Setting Symbolrate: 6875000
2014-05-19 18:06:24 [3232] Setting Modulation: 3
2014-05-19 18:06:24 [3232] setting symbolrate: 6875
2014-05-19 18:06:24 [3232] Tuning DVB-C Frequency: 369000000
2014-05-19 18:06:24 [3232] Setting Frequency: 372000000
2014-05-19 18:06:24 [3232] Setting Symbolrate: 6875000
2014-05-19 18:06:24 [3232] Setting Modulation: 3
2014-05-19 18:06:24 [3232] setting symbolrate: 6875
2014-05-19 18:06:24 [3232] Tuning DVB-C Frequency: 372000000
2014-05-19 18:06:39 [3232] Enabling Standby
When I looked in the /var/log/mediaclient.log, I discovered a bunch of lines similar to the following; although I'm not sure how they relate to my scanning attempts:
Code: [Auswählen]
2014-05-19 17:10:56 [20535] connection to driver service timed out

Seiten: [1]