Re: [vdr] irc/matrix/mastodon
Martin Dummer kirjoitti maanantaina 14. marraskuuta 2022 12.16.56 EET: > Am 14.11.22 um 10:55 schrieb Mikko Tuumanen: > > Are there any vdr-related irc channels or matrix rooms? > I know about #gentoo-vdr on libera.chat but it's a quiet place I created a Matrix space: #vdr:ellipsis.fi and a chatroom there. I also added #gentoo-vdr to the space. See joinmatrix.org and matrix.org for more info about Matrix. ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] irc/matrix/mastodon
Hello Are there any vdr-related irc channels or matrix rooms? Which hashtag we should use when mentioning VDR on Mastodon? ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Need help for LIRC + remote on serial COM port on recent Linux distrib
> - lirc_serial move out of staging (is no longer part of the kernel) > and/or rename to serial_ir. Here are my notes about those lirc changes from March 2019. You still need to release the serial port from normal serial driver: setserial /dev/ttyS0 uart none Load serial_ir module, no need for lirc_serial. serial_ir will create a /dev/lircN device, and also a /dev/input/eventM Load one of the ir_*_decoder modules too, for example ir_rc5_decoder or ir_rc6_decoder depending on the type of your remote. This way you'll probably don't need to teach remotes to lircd with irrecord, but can just read events from /dev/input/eventM Do a cat /sys/class/rc/rc*/protocols That will show you list(s) of supported remote models and you can change the model by writing your choice back to the protocols file. Before I knew all this, I tried to teach remote to lircd with irrecord, like irrecord -H default -d /dev/lircN This way I couldn't get irrecord to learn about a Technotrend remote I have. After I chose rc-5 with the protocols file, I started to get events from /dev/ input/eventM. This wasn't enough to get lircd to react to the events, so I had to teach them to lircd by running irrecord -H devinput -d /dev/input/eventM After that I ran lircd with lircd -e lirc -H devinput \ -d /dev/input/by-path/platform-serial_ir.0-event-ir \ /etc/lircd.conf And now lirc works again! Unfortunately I still couldn't figure out how I could use the Technotrend remote with built-in ir receiver of CT2-4400. There is a /dev/input/event- device for it, but no events come through. ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Multiple vdr peers on same machine
> Actually it should be possible to run several VDRs on the same machine > without any exta efforts. All you need to do is use separate SVDRP ports > via the --port option. I was missing address of the machine from the other svdrphosts.conf. 127.0.0.1 there didn't help, because peering doesn't use that address. ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Multiple vdr peers on same machine
I have two vdr instances running on the same machine, one for recording and other for viewing. Then I wanted them to use the new vdr peer system to be able to edit timers from the viewing side. Running two vdr's didn't work because they both want to bind the 6419 port, so I made a work-around with network namespaces like this: First, a helper script to create a network namespace if not already created and run a command there: /usr/local/sbin/Nsenter_vdr2 #!/bin/bash mp=/home/vdr/vdr2/netns addr=192.168.8.2/24 gw=192.168.8.1 if ! mountpoint -q $mp ; then unshare --net=$mp true || exit 1 ip link add vdr2eth type veth peer name eth0 netns $mp nsenter --net=$mp sh -c "ip link set eth0 up \ && ip a add $addr dev eth0 \ && ip link set lo up \ && ip -4 route add default via $gw" fi if test -n "$SUDO_USER" -a "$SUDO_USER" != root ; then exec nsenter --net=$mp sudo -u "$SUDO_USER" "$@" else exec nsenter --net=$mp "$@" fi The name space mount point is a reqular file (empty) and not a directory. Nsenter script creates a veth pair named vdr2eth on the outside and eth0 inside. I used /etc/network/interfaces to set vdr2eth address, but it coud be done in the Nsenter script too. allow-hotplug vdr2eth iface vdr2eth inet static address 192.168.8.1 netmask 255.255.255.0 Then I run the recording instance of vdr normally on the outside and add permissions for 192.168.8.2 in svdrphosts and streamdevhosts. Viewing vdr is run in the network namespace something like this: #!/bin/bash if test "$1" = "nsentered" ; then shift exec vdr -D- "-Psofthddevice -f" -i 1 -Pstreamdev-client "$@" exit 1 fi while true ; do sudo Nsenter_vdr2 "$0" nsentered "$@" done I don't need to peer the viewing vdr to other computers in the local network. If that were the case, then the outside end of the veth pair would need to be bridged with the physical network card of the machine. ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Race condition when executing recording hook
torstaina 14. joulukuuta 2017 8.26.29 EET Harald Milz kirjoitti: > I don't know how to handle this properly. My suggestion would be to ignore > the channel pid change during an active recording on this channel, and > defer the change until the recording is finished _if_ "-r something" is set How about starting recording hooks with "pidchange" when stopping is caused by pid change and "after" only when recroding has stopped because the timer end time has been reached? YLE channels change their pids all the time. Different programmes have different sets of audio and subtitle pids. Ignoring a pid change might mean missing a subtitle or audio track from the recording. Ideally VDR should be able to add/remove pids from ongoing recording without temporarily stopping it. Couple of years ago I tried to see how adding new pids on the fly could be done, but it was not trivial. For YLE channels, pid changes are frequent but predictable. One could stop VDR from changing pids automatically and set all the possible pids statically to channels.conf. But if some other broadcaster also changes pids frequently but in an unpredictable way, then this doesn't help and pid changes mustn't be ignored. ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Using a rasberry pi as vdr client
+ streamdev and rpihddevice (which additional plugins ?) The second way seems to be more complicated to configure, and I'm not sure it suits my project, but the rpihddevice is well maintained though. Could you tell me more please ? I haven't tried the fbfe, but I borrowed a raspberry pi model B from work and tried with rpihddevice and streamdev. I have the main vdr machine running streamdev server and I also mounted the video directory on the pi with nfs4. Sometimes this setup seems slow. I suggest using a raspberry pi 2 just because it has more cpu power. I might also get a gigabit usb-ethernet adapter for the pi. I hope that would make fast forward/rewind smoother when playing HD. With rpihddevice you need to buy an mpeg2 license for the pi to watch mpeg2 channels. I didn't (because the pi is not mine) so I havent' tried any mpeg2 stuff on the pi. rpihddevice can output interlaced signal to hdmi so deinterlacing can be done on the tv. You should install svdrpservice and remoteosd to the pi and svdrposd to the server. That way it's easy to create timers and manage other things on the server. See http://vdr.schmirler.de/ Editing recordings on the pi through nfs is painfully slow. If I have time, I'll write a script to be run from reccmds.conf that will ssh to the server and run vdr --edit the recording there. Other option would be to use svdrp to start the remote editing. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Kernels oops with PCTV nanostick 290e
Moving from VDR 1.6 to 2.06 for HD (DVB-T2) and seeing regular kernel oops w ith the PCTV nanostick 290e when using DVB-T2. The kernel is 3.0.76 (SLES 11 SP3) There have been some fixes to the nanostick driver after 3.0. If you are not sure that they have been backported to 3.0, try 3.3 or later. https://patchwork.linuxtv.org/patch/9139/ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] RFE: Make VDR more friendly when using combinations of DVB-S, DVB-T and DVB-C
Once version 2.0 is finished, I'm planning on dealing with the same channel from multiple sources problem. There is a related problem with the PCTV nanostick T2-usb receiver. The nanostick T2 can receive C/T/T2 though the same antenna connector. Change between C and T is done the normal way and the stick works perfectly with vdr as long as the setup is simple enough. However, there seems to be no way of telling the driver or vdr whether the nanostick is connected to C or T antenna cable. As far as I know I have the following alternatives: 1) Combiner. Build a combiner to connect both signals to the nanostick at the same time. I guess that would require me to measure the signal levels and use an attenuator or aplifier to match the levels. Then I'd need to build some band pass circuitry to select VHF and UHF frequencies from the T antenna and some others from cable. I don't exactly know how to do that and I don't have the necessary tools to measure the signal levels. However, if somebody is willing to do the math and design such a combiner I would definetly try to build one. 2) Fix the driver. Add a kernel module parameter to the driver that can be used to limit the available delivery systems visible to applications. This solution might need some extra work if order of the usb devices change randomly at each boot. 3) Vdr config. Make each channel use a certain receiver in vdr. This would be easy, but too limiting. For example if I had 2 receivers connected to T and 1 to C, I wouldn't like to pin the T-channels to a dedicated receiver when there are more than 2 T-multiplexes in the air. 4) Make some changes to vdr? Perhaps, but I think the option 2 would be better idea. Here in Turku we have some channels that are FTA-available only on DVB-C and a channel that is FTA-available only on DVB-T2. The driver fix together with a fix to the same channel from multiple sources would help greatly in this situation too. A side note: There is a bug or feature with the nanostick that has helped me a lot with my setup. A DVB-T channel marked to be DVB-T2 will work just fine. Due to some antenna issues, I can't receive some T multiplexes with my old receivers, but the nanosticks can receive them ok. I have set these channels to be DVB-T2 in channels.conf. Vdr selects one of the nanosticks when they need to be received. If this bug didn't exist, the same setup wouldn't be possible. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Filesystem hierachy standard patch needs review.
In real life we all spread our things all over the house to keep them in order. Exactly. And the point of spreading files all over the directory tree (not filesystem) is to be able to easily: - split the tree into several filesystems that have different properties such as size, speed, availability when the network is up, etc. - make part of the tree read only (to protect it from some problems) - make part of the tree shared between computers - and some parts shared between computers of different cpu architectures For example it should be possible to make /usr read only and share /usr/share between different cpu architectures. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] IS there a working UPnP-AV/DLNA support for VDR?
i am still working on it. I have a feature reuqest for the vdr dlna server. I bought a tv and fast forwarding through the dlna is terribly slow (tried minidlna) and there are no skip one minute or goto hh:mm etc. functionality at all. Skipping minute forward, backward and goto hh:mm like vdr does could be implemented in the dlna server. Then the user could send these commands to te server which would do the skipping (its easy when we have the vdr index files). Of course controlling can't be done with the dlna client remote control and doing this with multiple dlna clients is not so simple (need separate remote control for each client, etc). Another idea: Vdr in a cheap computer that is not able to decode and deinterlace the video properly. Connect a dlna cabable tv to the dvi output of the computer and the tv to the same network as the computer. Then it will be possible to create a cDlnaDevice that will draw osd on an X11 window and send all video to the dlna client. If the tv is remote controllable through serial port or ethernet then switching from video to osd and back could be automatic. Of course it wouldn't be osd any more, but menus could be used anyway. Unfortunately subtitles wouldn't work at all unless the tv supported them. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] What are recommended versions for a dxr3 setup ?
What is the latest kernel that dxr3 driver works on? 2.6.37 AFAIK With which patches? Any url to pull from? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] What are recommended versions for a dxr3 setup ?
I got a dvb card, installed it in my vdr box and it didn't work. So I decided to compile the driver, but alas, I had accidentially deleted the kernel compile tree. So it seems it's time to upgrade everyting: kernel, vdr, dxr3 driver and dxr3plugin. But what are the recommended versions at the moment? What is the latest kernel that dxr3 driver works on? And where should get the dxr3 driver from? Is the vdr-dxr3-0.2.12 in vdr-developer.org the latest and greatest version of the plugin or should I pull from git or hg somewhere? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] nvidia-vdr closed driver or open source?
to, 2010-08-19 kello 08:57 -0700, VDR User kirjoitti: Nouveau is that there are no plans to support VDPAU. That drivers seems like a case of too little too late. I've just tried to use a tnt2 card with the nvidia legacy drivers because a couple of capacitors blew up on my newer card. It didn't work, undefined symbol. Same thing with ati cards. For example my work computer had an ati card and fglrx support for it went away before warranty of the computer expired. Open source drivers are needed so that old cards can be put to use even after the manufacturer doesn't care to support them anymore. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-webvideo 0.3.1
Running an external commad after a download is finished sounds like a good idea. I'll implement it in the next version. Great, thanks. Those who have their tv still connected to FF-card tv output will have to transcode sooner (with the external command) or later (mplayer plugin, etc) anyway. I'd prefer to transcode after download and have the downloaded videos in the same list as the recorded programmes. Then they could be watched and deleted with vdr's own player just like normal recordings. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-webvideo 0.3.1
ma, 2010-08-02 kello 18:41 +0300, Antti Ajanki kirjoitti: Only xineliboutput is supported at the moment, sorry. How about transcoding or remultiplexing the downloaded videos to normal vdr recordings? Is there a way to run a command (like vdr's -r) after a video has been downloaded? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Subtitling descriptor in ts recordings
Hello. VLC 1.0 doesn't even try to show subtitles from ts recordings, because vdr sets subtitling type to zero in remux.c If you want to watch dvb-subtitled ts recordings with vlc, try this patch: http://users.utu.fi/mijutu/digitv/vdr/vdr-1.7.8-subtitling_descriptor_for_vlc_1.0.diff.bz2 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Status of WinTV-HVR-4000 card!!
I have one Hauppauge WinTV-HVR4000 DVB-S/S2/T/Hybrid [card=68,autodetected] at work. Currently there is - Debian 5.0.1 (lenny) with - self compiled 2.6.29.2 - dvb drivers from hg, pulled around 11.5. - vdr-1.7.7 - streamdev-server from vdr-developer.org CVS With this setup I am finally able to tune and receive DVB-S2 channels. I don't know what was the problem, but all earlier attempts failed for some reason. These are not minimum requirements for version numbers to get it working, just an example of something that works. For example these two channels can be received: ANIXE HD;BetaDigital:11302:hC23M5O35S1:S19.2E:22000:255=27:0;259=deu:0:0:4900:1:1007:0 ASTRA HD +;BetaDigital:11302:hC23M5O35S1:S19.2E:22000:511=27:0;515=deu:0:0:4901:1:1007:0 If you want to use this card for both sat and dvb with vdr, I suggest you to buy 2 different card I agree. AFAIK the HVR-4000 can't receive DVB-T and DVB-S/S2 at the same time, so it would be a good idea to buy a (cheaper) S/S2-only-card and a separate card for T. VDR doesn't seem support the DVB-T side of the HVR-4000. Now that I tried, I get a channel not available when trying to switch to a T channel. It is probably because VDR doesn't open the adapterX/frontend1 device that is used to control the DVB-T receiver. The DVB-T side of the card works fine with tzap or any application that can be told to use the frontend1 device. Analog parts of the card are also supported. I haven't tried analog tv, but the composite input gets me some kind of picture. There is also a /dev/radio0, and it can produce at least static. BTW, has anybody succeeded in decoding anixe hd or astra hd+ with vdpau? Every time I've tried, the result has been mostly garbage and usually kill -9 to Xserver and xine is needed. Popcorn hour networked media tank decodes those channels much better. So far I have only tried using xine, mplayer, etc through streamdev, (not xineliboutput yet) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] DVB-H
ke, 2009-05-13 kello 15:55 +0200, Theunis Potgieter kirjoitti: Hi, is dvb-h a subset of dvb-t? our country decided to switch on dvb-t, we receive dvb-t and dvb-h with h.264. Any hints? I wrote some instructions for receiving DVB-H: http://users.utu.fi/mijutu/digitv/dvb-h/index-en.html I guess it would be possible to write a dvbh-plugin that would set up dvbnet, receive the rtp packets, wrap the h.264 elementary stream into ts packets and feed them to vdr. Or how about using VLC for rfc3984 - rfc2250 conversion and then receiving the stream back to VDR with the iptv-plugin. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] 1.7.3
Hello.
I've tried to play the new ts recordings with vlc and it seems that
there is a typo in remux.c.
--- remux.c.orig2009-01-16 12:22:43.0 +0200
+++ remux.c 2009-01-16 12:23:39.0 +0200
@@ -320,7 +320,7 @@
uchar *cPatPmtGenerator::GetPmt(int Index)
{
if (Index numPmtPackets) {
- IncCounter(patCounter, pmt[Index]);
+ IncCounter(pmtCounter, pmt[Index]);
return pmt[Index++];
}
return NULL;
Good news is that vlc does show dvb subtitles from the ts recordings.
BTW, here is a quick and ugly hack to get streamdev to compile with
1.7.3.
http://users.utu.fi/mijutu/digitv/vdr/streamdev-pes_commented_out_for_vdr-1.7.3.diff
This is not worth merging anywhere, but works if you want to try to
record with 1.7.3 in a computer without actual dvb adapters.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
