Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

2015-04-26 Thread BB
On 16/04/15 16:28, Gerald Dachs wrote: Am 2015-04-16 16:09, schrieb VDR User: What exactly do you think I was wrong about? You forgot already? You told that I was rude and I proofed that I was not. Gerald Sometimes even the truth may sound rudely. So you both made your points. Kind

Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

2015-04-18 Thread Andreas Baierl
Hi, Am 17.04.2015 um 20:46 schrieb VDR User: Actually cedarX hw decoding was another question I forgot in my previous post. I've read that it's working in linux but I didn't know if any output devices supported it (yet)?. Was hoping softhddevice does, or would if I sent Johns an A20. :) I

Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

2015-04-18 Thread Cedric de Wijs
Am 17.04.2015 um 20:46 schrieb VDR User: Actually cedarX hw decoding was another question I forgot in my previous post. I've read that it's working in linux but I didn't know if any output devices supported it (yet)?. Was hoping softhddevice does, or would if I sent Johns an A20. :) I suppose

Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

2015-04-18 Thread Cedric de Wijs
On 4/17/2015 6:46 PM, VDR User wrote: Actually cedarX hw decoding was another question I forgot in my previous post. I've read that it's working in linux but I didn't know if any output devices supported it (yet)?. Was hoping softhddevice does, or would if I sent Johns an A20. :) I think

Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

2015-04-17 Thread Patrick Boettcher
Hi all, On Fri, 17 Apr 2015 09:25:22 +0300 Füley István airo...@tigercomp.ro wrote: I know, it's not a proper answer for your problem, but I think at the moment the best native vdr client is a Raspberry Pi with Thomas Reufer's great plugin. It's small, cheap and (using with vdr) it's fast.

Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

2015-04-17 Thread Füley István
I know, it's not a proper answer for your problem, but I think at the moment the best native vdr client is a Raspberry Pi with Thomas Reufer's great plugin. It's small, cheap and (using with vdr) it's fast. I moved from vdr-sxfe to rpihddevice with all my 3 clients in the house. regards,

Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

2015-04-17 Thread Reiner Bühl
Hello István, which USB DVB-S2 receiver do you use on your Raspberry Pi? Best regards, Reiner. Am 17.04.2015 11:54, schrieb Füley István: 2015.04.17. 10:24 keltezéssel, Patrick Boettcher írta: Hi all, And you are using streamdev-server on your vdr-host (which has all the DVB-cards) and

Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

2015-04-17 Thread Marko Mäkelä
On Fri, Apr 17, 2015 at 09:25:22AM +0300, Füley István wrote: I know, it's not a proper answer for your problem, but I think at the moment the best native vdr client is a Raspberry Pi with Thomas Reufer's great plugin. It's small, cheap and (using with vdr) it's fast. Speaking of small and

Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

2015-04-17 Thread Füley István
2015.04.17. 13:07 keltezéssel, Reiner Bühl írta: Hello István, which USB DVB-S2 receiver do you use on your Raspberry Pi? It's an old Terratec Cinergy S2: http://www.linuxtv.org/wiki/index.php/TerraTec_Cinergy_S2 I used it several years ago on my main server, but I had a problem with it: i

Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

2015-04-17 Thread cedric.dew...@telfort.nl
Origineel Bericht Van : marko.mak...@iki.fi Datum : 17/04/2015 11:51 Aan : vdr@linuxtv.org Onderwerp : Re: [vdr] from xineliboutput to ... perhaps softhdddevice? On Fri, Apr 17, 2015 at 09:25:22AM +0300, Füley István wrote: I know, it's not a proper answer for your problem, but I think

Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

2015-04-17 Thread Marko Mäkelä
Hi Cedric, On Fri, Apr 17, 2015 at 12:08:05PM +0200, cedric.dew...@telfort.nl wrote: Write performance on the uSD card is terrible, even with a class 10 card. Updating debian on the card takes patience. AFAIU if you are not afraid of bricking the Cubietruck, you could install Debian on the

Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

2015-04-17 Thread VDR User
For those of you using Raspberry Pi or Allwinner boards, how is osd performance? If the osd is fast smooth, I'm interested in building a couple vdr setups like those (maybe Raspberry Pi 2. Rpi is just too slow). Any degrade in performance is a deal-breaker for me. Thanks

Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

2015-04-17 Thread Cedric de Wijs
On 4/17/2015 2:13 PM, VDR User wrote: For those of you using Raspberry Pi or Allwinner boards, how is osd performance? If the osd is fast smooth, I'm interested in building a couple vdr setups like those (maybe Raspberry Pi 2. Rpi is just too slow). Any degrade in performance is a

Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

2015-04-17 Thread VDR User
Actually cedarX hw decoding was another question I forgot in my previous post. I've read that it's working in linux but I didn't know if any output devices supported it (yet)?. Was hoping softhddevice does, or would if I sent Johns an A20. :) On Fri, Apr 17, 2015 at 11:17 AM, Cedric de Wijs

Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

2015-04-16 Thread Gerald Dachs
Am 2015-04-15 22:54, schrieb Lars Hanisch: Am 15.04.2015 um 18:37 schrieb VDR User: On Wed, Apr 15, 2015 at 8:03 AM, Gerald Dachs v...@dachsweb.de wrote: Proper server/client has been on the user wishlist for ages. There's no reason to be rude to someone looking for something better. If those

Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

2015-04-16 Thread VDR User
Restfulapi and dynamite were the projects I had in mind, thanks Lars. And restfulapi was a starter for even two more fellows. I've never heard of Restfulapi. Dynamite I've at least heard of but until Lars post, had no clue what it did. And just in case that you will tell now that nobody needs

Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

2015-04-16 Thread VDR User
Gerald, my opinion is my opinion - you disagreeing doesn't change anything. It's not wrong and nobody is the opinion police. Reiner, if you don't want to following something, *don't follow it*. You're not being forced to read anything. However, out of courtesy for Matthias, the OP, I won't keep

Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

2015-04-16 Thread Gerald Dachs
Am 16.04.2015 um 17:09 schrieb VDR User: Gerald, my opinion is my opinion - you disagreeing doesn't change anything. It's not wrong and nobody is the opinion police. So why you then argued against my argumentation to show that I am not rude and named me even a liar? And after I proofed that I

Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

2015-04-16 Thread Reiner Bühl
Can you please discuss this further off the list? I think this is going way beyond the purpose of the list and I think I might not be the only one that is not interested in following this argument on the list. Best regards, Reiner. Am 16.04.2015 16:09, schrieb VDR User: Restfulapi and

Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

2015-04-16 Thread Gerald Dachs
Am 2015-04-16 16:09, schrieb VDR User: What exactly do you think I was wrong about? You forgot already? You told that I was rude and I proofed that I was not. Gerald ___ vdr mailing list vdr@linuxtv.org

Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

2015-04-16 Thread Lars Hanisch
Am 16.04.2015 um 16:09 schrieb VDR User: [...] Dynamite is used by all yaVDR users. Restfulapi is now part of OpenELEC. They sound successful. Unfortunately https://github.com/yavdr/vdr-plugin-restfulapi/blob/master/README is just an advertisement for yavdr and gives no actual information

Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

2015-04-15 Thread Gerald Dachs
Am 2015-04-15 16:43, schrieb VDR User: On Wed, Apr 15, 2015 at 3:56 AM, Gerald Dachs v...@dachsweb.de wrote: While streamdev and VNSI/XVDR solve some of the issues, most notably the multi-client dependency, they create new ones. No native OSD with VNSI/XVDR, VDR configuration synchronization

Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

2015-04-15 Thread VDR User
On Wed, Apr 15, 2015 at 3:56 AM, Gerald Dachs v...@dachsweb.de wrote: While streamdev and VNSI/XVDR solve some of the issues, most notably the multi-client dependency, they create new ones. No native OSD with VNSI/XVDR, VDR configuration synchronization hassle with streamdev. use softhddevice

Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

2015-04-15 Thread VDR User
On Wed, Apr 15, 2015 at 8:03 AM, Gerald Dachs v...@dachsweb.de wrote: Proper server/client has been on the user wishlist for ages. There's no reason to be rude to someone looking for something better. If those solutions were all that great then there wouldn't be any reason to ask. Of all the

Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

2015-04-15 Thread Gerald Dachs
Am 15.04.2015 um 18:37 schrieb VDR User: On Wed, Apr 15, 2015 at 8:03 AM, Gerald Dachs v...@dachsweb.de wrote: Proper server/client has been on the user wishlist for ages. There's no reason to be rude to someone looking for something better. If those solutions were all that great then there

Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

2015-04-15 Thread VDR User
On Wed, Apr 15, 2015 at 9:56 AM, Gerald Dachs v...@dachsweb.de wrote: To not say it and miss a change to get it done is useless. Who, and what have they coded? Project names? So, you name me a liar? Would it change something if I would name projects? I'm genuinely curious who you talked into

Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

2015-04-15 Thread Lars Hanisch
Am 15.04.2015 um 18:37 schrieb VDR User: On Wed, Apr 15, 2015 at 8:03 AM, Gerald Dachs v...@dachsweb.de wrote: Proper server/client has been on the user wishlist for ages. There's no reason to be rude to someone looking for something better. If those solutions were all that great then there

Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

2015-04-15 Thread Lars Hanisch
Am 15.04.2015 um 22:49 schrieb VDR User: On Wed, Apr 15, 2015 at 9:56 AM, Gerald Dachs v...@dachsweb.de wrote: To not say it and miss a change to get it done is useless. Who, and what have they coded? Project names? So, you name me a liar? Would it change something if I would name projects?

Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

2015-04-15 Thread Gerald Dachs
Am 2015-04-15 00:55, schrieb Niedermeier Günter: Am 14.04.2015 um 09:56 schrieb Gerald Dachs: Am 2015-04-14 08:59, schrieb Matthias Wächter: While streamdev and VNSI/XVDR solve some of the issues, most notably the multi-client dependency, they create new ones. No native OSD with VNSI/XVDR, VDR

[vdr] from xineliboutput to ... perhaps softhdddevice?

2015-04-14 Thread Matthias Wächter
Hi, I am currently using xineliboutput, and I'm using it with --local=none everywhere so I can attach and detach from anywhere in the LAN, even from the PC VDR is running on. It's working quite nicely this way. Upside: No local configuration on any PC, no concurrency issues with timers,

Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

2015-04-14 Thread Niedermeier Günter
Hi, I'm in the same situation, and most of my friends, using vdr the same way, too. The only software, I currently know which works similar, is VOMP client/server. It is also independant and could be run standalone on Linux and Windows. But it is IMHO only a worst-case-replacement for sxfe. I

Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

2015-04-14 Thread Gerald Dachs
Am 2015-04-14 08:59, schrieb Matthias Wächter: While streamdev and VNSI/XVDR solve some of the issues, most notably the multi-client dependency, they create new ones. No native OSD with VNSI/XVDR, VDR configuration synchronization hassle with streamdev. use softhddevice + vdr + streamdev-client

Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

2015-04-14 Thread Niedermeier Günter
Am 14.04.2015 um 09:56 schrieb Gerald Dachs: Am 2015-04-14 08:59, schrieb Matthias Wächter: While streamdev and VNSI/XVDR solve some of the issues, most notably the multi-client dependency, they create new ones. No native OSD with VNSI/XVDR, VDR configuration synchronization hassle with