vdr May 2007

vdr@linuxtv.org

76 participants
78 discussions

Re: [vdr] Thunderstorm over Munich
by martin 28 May '07

28 May '07

Thanks all for your replys! At least I feel heard by the community. Yes, you are right - I can not address my thoughts without emotions. So we get into ITIL terminology. I will not do it 100% correct, as we need the application of ITIL to the current problem. Okay, here it comes. Some call it "features", some would call it "services". The VDR "suite" is providing vertical and horizontal services. Vertical Services are most of the time "end user services", whereas horizontal … [View More]services are "platform services". To get into detail: Vertial: * Show a live DVB stream * Record a DVB stream * Time-Shift-View * Show a recording * .. you name it, we have it .. there's a lot more! -> When we would build up a service catalogue, we would also have to make SLA's on it. This would be the case, when a service provider (that's actually me!) is providing serivces to customers (my beloved!). And here comes the story: everybody wants to have 100% availability, that's clear. I do regular service updates with my VDR, where all services are down. This I can schedule so, that there is no interference with my end customers. Okay, all services are seen as single instances. End-Users do not understand, why recording a DVB stream is linked to showing a recording! -> Please Klaus, explain - in words that my Granny will understand! Second: There is something that's called "höhere gewalt". Examples: I want to watch TV, but there is a power outage. Nobody would blame me - personally. When I want to go across the alps with my car and it snowed 2 meters over night, nobody would blame me, that i was not able to go across. When I want to get tanned by sun and it's raining, it's simply impossible. When there is a huge cloud over my sat dish, even my 85cm is too small. I can not influence the weather. Everboy will understand! Horizontal: * The socalled API It's a platform, that is not visible to the endcustomer, but totally necessary as a good software is always open for new vertical services! The hassle with this is, that end-users do not care about the API. Modules must simply link in. Klaus had a long nightmare behind about this. So API is necessary, but also a lot of work with almost no refund. Something out scope for ITIL - Patching: And then we have the BigPatch fraction. I love those guys, they do also great job. They are not building on an API, they are modifying the source. Why are they doing this - should some of you ask yourself? Answer for me is simple: I did also do a feature request, something that was already developed, Klaus only needed to include in his source. But people started discussing, that we don't need. -> If we don't need, why is there a BigPatch. So no new feature (again a vertical service), which is frustrating. -> ".. inaction is a weapon of mass destruction." If you like musik, check your mp3 library for: http://www.lyricstop.com/m/massdestruction-faithless.html So: what would be the next steps: it's clear, VDR is not able (willing or what ever, again I don't care) to split up the services, so i must find workarrounds. Make many instances of VDR running on my machine. One is doing recording, one EPG search, the other is providing "Show" Sevice. -> do I really have to do this? And how to do it? Next would be that i have to split up physically into seperate boxes .. *puh* Finally - Business Economics: Talking about the "Cost of Service" and the "Total Cost of Ownership". When I split up VDR instances, the costs increase and over the lifetime the costs get multipied. Do I take Windows or Linux -> it's just a cost fact: Linux costs me, in my environment less. Do I buy a DVB-Recorder or do I build up (custom made). Also simple: I need to compare the service catalogue. All commercial services do not offer me "noad", "vdradmin", "epgsearch", "femon". This is the reason for me to use VDR. So: I use a lot of the API, I use BigPatch to get the 10 seconds jumps. This is what make VDR unique and worth using it. But writing such a long mail is frustrating :( Martin Thanks all for your replys! At least I feel heard by the community. Yes, you are right - I can not address my thoughts without emotions. So we get into ITIL terminology. I will not do it 100% correct, as we need the application of ITIL to the current problem. Okay, here it comes. Some call it "features", some would call it "services". The VDR "suite" is providing vertical and horizontal services. Vertical Services are most of the time "end user services", whereas horizontal services are "platform services". To get into detail: Vertial: * Show a live DVB stream * Record a DVB stream * Time-Shift-View * Show a recording * .. you name it, we have it .. there's a lot more! -> When we would build up a service catalogue, we would also have to make SLA's on it. This would be the case, when a service provider (that's actually me!) is providing serivces to customers (my beloved!). And here comes the story: everybody wants to have 100% availability, that's clear. I do regular service updates with my VDR, where all services are down. This I can schedule so, that there is no interference with my end customers. Okay, all services are seen as single instances. End-Users do not understand, why recording a DVB stream is linked to showing a recording! -> Please Klaus, explain - in words that my Granny will understand! Second: There is something that's called "höhere gewalt". Examples: I want to watch TV, but there is a power outage. Nobody would blame me - personally. When I want to go across the alps with my car and it snowed 2 meters over night, nobody would blame me, that i was not able to go across. When I want to get tanned by sun and it's raining, it's simply impossible. When there is a huge cloud over my sat dish, even my 85cm is too small. I can not influence the weather. Everboy will understand! Horizontal: * The socalled API It's a platform, that is not visible to the endcustomer, but totally necessary as a good software is always open for new vertical services! The hassle with this is, that end-users do not care about the API. Modules must simply link in. Klaus had a long nightmare behind about this. So API is necessary, but also a lot of work with almost no refund. Something out scope for ITIL - Patching: And then we have the BigPatch fraction. I love those guys, they do also great job. They are not building on an API, they are modifying the source. Why are they doing this - should some of you ask yourself? Answer for me is simple: I did also do a feature request, something that was already developed, Klaus only needed to include in his source. But people started discussing, that we don't need. -> If we don't need, why is there a BigPatch. So no new feature (again a vertical service), which is frustrating. -> ".. inaction is a weapon of mass destruction." If you like musik, check your mp3 library for: http://www.lyricstop.com/m/massdestruction-faithless.html So: what would be the next steps: it's clear, VDR is not able (willing or what ever, again I don't care) to split up the services, so i must find workarrounds. Make many instances of VDR running on my machine. One is doing recording, one EPG search, the other is providing "Show" Sevice. -> do I really have to do this? And how to do it? Next would be that i have to split up physically into seperate boxes .. *puh* Finally - Business Economics: Talking about the "Cost of Service" and the "Total Cost of Ownership". When I split up VDR instances, the costs increase and over the lifetime the costs get multipied. Do I take Windows or Linux -> it's just a cost fact: Linux costs me, in my environment less. Do I buy a DVB-Recorder or do I build up (custom made). Also simple: I need to compare the service catalogue. All commercial services do not offer me "noad", "vdradmin", "epgsearch", "femon". This is the reason for me to use VDR. So: I use a lot of the API, I use BigPatch to get the 10 seconds jumps. This is what make VDR unique and worth using it. But writing such a long mail is frustrating :( Martin Thanks all for your replys! At least I feel heard by the community. Yes, you are right - I can not address my thoughts without emotions. So we get into ITIL terminology. I will not do it 100% correct, as we need the application of ITIL to the current problem. Okay, here it comes. Some call it "features", some would call it "services". The VDR "suite" is providing vertical and horizontal services. Vertical Services are most of the time "end user services", whereas horizontal services are "platform services". To get into detail: Vertial: * Show a live DVB stream * Record a DVB stream * Time-Shift-View * Show a recording * .. you name it, we have it .. there's a lot more! -> When we would build up a service catalogue, we would also have to make SLA's on it. This would be the case, when a service provider (that's actually me!) is providing serivces to customers (my beloved!). And here comes the story: everybody wants to have 100% availability, that's clear. I do regular service updates with my VDR, where all services are down. This I can schedule so, that there is no interference with my end customers. Okay, all services are seen as single instances. End-Users do not understand, why recording a DVB stream is linked to showing a recording! -> Please Klaus, explain - in words that my Granny will understand! Second: There is something that's called "höhere gewalt". Examples: I want to watch TV, but there is a power outage. Nobody would blame me - personally. When I want to go across the alps with my car and it snowed 2 meters over night, nobody would blame me, that i was not able to go across. When I want to get tanned by sun and it's raining, it's simply impossible. When there is a huge cloud over my sat dish, even my 85cm is too small. I can not influence the weather. Everboy will understand! Horizontal: * The socalled API It's a platform, that is not visible to the endcustomer, but totally necessary as a good software is always open for new vertical services! The hassle with this is, that end-users do not care about the API. Modules must simply link in. Klaus had a long nightmare behind about this. So API is necessary, but also a lot of work with almost no refund. Something out scope for ITIL - Patching: And then we have the BigPatch fraction. I love those guys, they do also great job. They are not building on an API, they are modifying the source. Why are they doing this - should some of you ask yourself? Answer for me is simple: I did also do a feature request, something that was already developed, Klaus only needed to include in his source. But people started discussing, that we don't need. -> If we don't need, why is there a BigPatch. So no new feature (again a vertical service), which is frustrating. -> ".. inaction is a weapon of mass destruction." If you like musik, check your mp3 library for: http://www.lyricstop.com/m/massdestruction-faithless.html So: what would be the next steps: it's clear, VDR is not able (willing or what ever, again I don't care) to split up the services, so i must find workarrounds. Make many instances of VDR running on my machine. One is doing recording, one EPG search, the other is providing "Show" Sevice. -> do I really have to do this? And how to do it? Next would be that i have to split up physically into seperate boxes .. *puh* Finally - Business Economics: Talking about the "Cost of Service" and the "Total Cost of Ownership". When I split up VDR instances, the costs increase and over the lifetime the costs get multipied. Do I take Windows or Linux -> it's just a cost fact: Linux costs me, in my environment less. Do I buy a DVB-Recorder or do I build up (custom made). Also simple: I need to compare the service catalogue. All commercial services do not offer me "noad", "vdradmin", "epgsearch", "femon". This is the reason for me to use VDR. So: I use a lot of the API, I use BigPatch to get the 10 seconds jumps. This is what make VDR unique and worth using it. But writing such a long mail is frustrating :( Martin Thanks all for your replies! At least I feel heard by the community. Yes, you are right - I cannot address my thoughts without emotions. So we get into ITIL terminology. I will not do it 100% correct, as we need the application of ITIL to the current problem. Okay, here it comes. Some call it "features", some would call it "services". The VDR "suite" is providing vertical and horizontal services. Vertical Services are most of the time "end user services", whereas horizontal services are "platform services". To get into detail: Vertical: * Show a live DVB stream * Record a DVB stream * Time-Shift-View * Show a recording * .. you name it, we have it .. there's a lot more! -> When we would build up a service catalogue, we would also have to make SLA's on it. This would be the case, when a service provider (that's actually me!) is providing services to customers (my beloved!). And here comes the story: everybody wants to have 100% availability, that's clear. I do regular service updates with my VDR, where all services are down. This I can schedule so, that there is no interference with my end customers. Okay, all services are seen as single instances. End-Users do not understand, why recording a DVB stream is linked to showing a recording! -> Please Klaus, explain - in words that my Granny will understand! Second: There is something that's called "höhere Gewalt". Examples: I want to watch TV, but there is a power outage. Nobody would blame me - personally. When I want to go across the alps with my car and it snowed 2 meters over night, nobody would blame me, that i was not able to go across. When I want to get tanned by sun and it's raining, it's simply impossible. When there is a huge cloud over my sat dish, even my 85cm is too small. I cannot influence the weather. Everybody will understand! Horizontal: * The so-called API It's a platform, that is not visible to the end customer, but totally necessary as good software is always open for new vertical services! The hassle with this is, that end-users do not care about the API. Modules must simply link in. Klaus had a long nightmare behind about this. So API is necessary, but also a lot of work with almost no refund. Something out scope for ITIL - Patching: And then we have the BigPatch fraction. I love those guys, they do also great job. They are not building on an API, they are modifying the source. Why are they doing this - should some of you ask yourself? Answer for me is simple: I did also do a feature request, something that was already developed, Klaus only needed to include in his source. But people started discussing, that we don't need. -> If we don't need, why is there a BigPatch. So no new feature (again a vertical service), which is frustrating. -> ".. inaction is a weapon of mass destruction." If you like music, check your mp3 library for: http://www.lyricstop.com/m/massdestruction-faithless.html So: what would be the next steps: it's clear, VDR is not able (willing or what ever, again I don't care) to split up the services, so i must find workarounds. Make many instances of VDR running on my machine. One is doing recording, one EPG search, the other is providing "Show" Service. -> do I really have to do this? And how to do it? Next would be that i have to split up physically into separate boxes .. *puh* Finally - Business Economics: Talking about the "Cost of Service" and the "Total Cost of Ownership". When I split up VDR instances, the costs increase and over the lifetime the costs get multiplied. Do I take Windows or Linux -> it's just a cost fact: Linux costs me, in my environment less. Do I buy a DVB-Recorder or do I build up (custom made). Also simple: I need to compare the service catalogue. All commercial services do not offer me "noad", "vdradmin", "epgsearch", "femon". This is the reason for me to use VDR. So: I use a lot of the API, I use BigPatch to get the 10 seconds jumps. This is what make VDR unique and worth using it. But writing such a long mail is frustrating :( Martin [View Less]

3 3

[PATCH] vdr-dvdswitch crashing when pressing an arrow key in empty image directory
by Matthias Schwarzott 28 May '07

28 May '07

Hi there! Opening DVDSwitch menu if the image directory is empty, and then pressing some arrow key crashes vdr. The attached patch solves this bug. Matthias -- Matthias Schwarzott (zzam)

1 0

[Announce] epgsearch-0.9.22
by Christian Wieninger 27 May '07

27 May '07

Hi, here's the next release of epgsearch. This time a little earlier as usual because of a new other plugin coming soon ;) 2007-05-27: Version 0.9.22 new: - new option in timer conflict check "When a recording starts": This performs a conflict check when any recording starts and informs about it via OSD if the conflict is within the next 2h. So also timers not created with epgsearch are checked, the same for instant recordings. - new service interface "Epgsearch-services-v1.0": … [View More]

1 0

Nasty effect...
by JJussi 27 May '07

27 May '07

Hi! Is there setting what "removes" effect where when camera is moving side to side straight vertical lines are "divided" to 2 - 4 "zones" (inside zone line is "whole") and those areas are at different positions (horizontaly) Like: | | | | | | | | | | | | | | | | That "cut point" is moving upvard between different frames. Screen is LCD. 1024x768 60Hz Is this something like screen is updated at wrong point (of time), … [View More]

2 1

Lightning destroyed my 4 DVB-S cards, what should I replace them with?
by Carsten Koch 27 May '07

27 May '07

I had 1 FF and 2 budget cards in one PC, 1 FF card in the other. All 4 were destroyed by lightning this morning during a thunderstorm. What are the best cards to replace them with? In an earlier post, Klaus wrote that he is working on HDTV support and that he is using a TT-budget S2-3200. Would that be a good model to replace my 2 budget cards with? Does the driver work reliably now? Is there a supported FF HDTV card? If no, would the TT-premium S-2300 be the best choice? Should I still buy … [View More]

5 5

RE: [vdr] [ANNOUNCE] VDR sync early patch
by Martin 26 May '07

26 May '07

Thanks Reinhard!Upgraded now to vdr-1.4.6-1-bigpatch + your speed up patch. It's working and I also see some increase in speed. I think now the limiting factor here on my side are the audio and video buffers of xine. If I make them too small, I get frame drops. But anyways: your tweak is putting switching speed to the limit.Regards,Martin> Date: Sun, 6 May 2007 22:23:03 +0200> From: rnissl(a)gmx.de> To: vdr(a)linuxtv.org> Subject: [vdr] [ANNOUNCE] VDR sync early patch> > Hi,&… [View More]

2 1

Thunderstorm over Munich
by Martin 26 May '07

26 May '07

Who is interested in the weather in Munich? Probably nobody, mine either as I was sitting indor to watch my favourite TV shows.Then suddenly a nice "emergency exit" .. i had this game for 15 Minutes .. I do not tell you how lucky I am that the thunderstorm is over now ..Thanks for letting me know, that vdr needs to exit, when there is a thunderstorm, while i am watching ...Have a nice day,Martin _________________________________________________________________ Windows Live Messenger: Jetzt den … [View More]

2 1

record plug-in..
by JJussi 25 May '07

25 May '07

Hi! Is there (somewhere) or is easy to produce plug-in what would save (record) all what you are watching live? Something like last 30 - 60 minutes?!? That way you could always rewind backward and that would remove that gap (of time) what now exists when you press "pause" (at least I have "problem"; when I press pause button, it takes over 10 seconds before it's actually pausing live stream) -- JJussi

3 5

Xineliboutput: can achieve similar to softdevice's mgatv option?
by Alasdair Campbell 25 May '07

25 May '07

Can vdr-xineliboutput utilize the excellent interlaced output of a Matrox G450 with VGA>SCART cable? I'm seeing what I can only describe as video stutters/shakes with interlaced video and quick movements, long camera pans. Using latest vdr-xineliboutput, DirectFB-1.0.0 & xine-lib-1.1.5 using Gentoo ebuilds. Otherwise xineliboutput is working fantastically! (well without any sound but that's another issue for another day :-) ) -- A l a s d a i r C a m p b e l l r a g a w u @ g m a … [View More]

5 32

VDR: Mantis bug tracking and a forum
by Pasi Juppo 25 May '07

25 May '07

Hi, It would be nice if there was proper bug tracking used for VDR development instead mailing list. See example from streamdev issue: http://www.vdr-developer.org/mantisbt/view.php?id=255 The tool is good for this purpose. Same actually goes for this mailing list. Proper forum is much more convenient than mailing list because of proper threading etc. features. Could someone be able to set up the forum and most importantly would this discussion move to the forum? Br, Pasi

5 4

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr May 2007