vdr

vdr@linuxtv.org

6731 discussions

Dropping pixel font in VDR 1.5?
by Klaus Schmidinger 29 May '07

29 May '07

I'm currently implementing support for Freetype fonts in VDR 1.5 (based on Alexander Riedel's patch) and would like to completely drop all the pixel font stuff. Just to make sure there won't be somebody who absolutely needs the pixel fonts, please let me know if this is ok. Since probably most of you will be running VDR with UTF-8 anyway (once it is supported, which will be very soon), my guess would be that the pixel fonts are really obsolete. Klaus

5 9

How to change Pro7 SAT1 Channels via Menu
by Helmut Auer 29 May '07

29 May '07

Hello List, What is the preferred way to change the settings of the channels Pro7 ... ? I have a lot of users which do not have a pc to take the easy way (shutting down vdr and editing channels.conf) Yesterday I had a phone call with one of these and changing the channel settings via the menu is horrible, because after changing the channel some minutes later vdr replaces the channel with the old settings. Looks like he has to turn the automagic channel update off for doing this ? Now the next persons have the same problem and I don't like to spent more time on the phone then necessary ;) -- Helmut Auer, helmut(a)helmutauer.de

3 5

new video-card with h264 decoder
by Igor Nikanov 29 May '07

29 May '07

Hello what do you think about this card ? Is it good choice for future vdr with hdtv support ? http://www.hardspell.com/english/doc/sho...=622&pageid=644 From the results we can see the HD acceleration of HD2600 and HD2400 is striking. The CPU usage is only about 5% by using 1.6GHz Sempron 2800+ to decode 1080p H.264 movies.

3 5

1.5.x Shutdown
by Chris 29 May '07

29 May '07

Hi there, I recently updated from VDR 1.4.6 to 1.5.2. (with no problems so far, by the way :)) But today I noticed something which seems to me like a small bug in vdr's shutdown routines. My shutdown script checks for different running processes (or connections) and does not quit vdr if at least one of the tests returns true. But since 1.5.2 (or probably since 1.5.0) the shutdown script remains as a zombie in such cases until vdr actually quits. I haven't checked the sources yet, but I guess there's somewhere a call to close() (or pclose()) for the opened pipe(s) missing. -- Chris

3 4

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

28 May '07

and again, start separating the services .. PS: sorry for the 3-times :( saw it now .. my apologies! > Date: Mon, 28 May 2007 16:43:33 +0200> From: Klaus.Schmidinger(a)cadsoft.de> To: vdr(a)linuxtv.org> Subject: Re: [vdr] Thunderstorm over Munich> > On 05/28/07 16:44, Lars Bläser wrote:> > Klaus Schmidinger wrote:> >> On 05/28/07 11:30, martin wrote:> >>> Thanks all for your replys! At least I feel heard by the community.> >>> ...> >> [ ... lengthy pamphlet, repeated three(!) times ... ]> >>> >> Martin, why don't you simply remove the cThread::EmergencyExit(true)> >> calls from recorder.c and remux.c?> >>> > > > how about a compile or start switch for this> > I'll change this in version 1.5. This hint was just to tell> Martin how to immediately make VDR 1.4.x work the way he apparently> expects it to.> > Klaus> > _______________________________________________> vdr mailing list> vdr(a)linuxtv.org> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr _________________________________________________________________ Windows Live Messenger: Jetzt den Nachfolger vom MSN Messenger kostenlos downloaden! http://get.live.com/messenger/overview

1 0

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

28 May '07

because i'm speak some dialekts like basic or turbo pascal .. but not C :( and i am not the only one, who has got the problem. and i can't tell my granny to remove the cThread :)) > Date: Mon, 28 May 2007 14:23:04 +0200> From: Klaus.Schmidinger(a)cadsoft.de> To: vdr(a)linuxtv.org> Subject: Re: [vdr] Thunderstorm over Munich> > On 05/28/07 11:30, martin wrote:> > Thanks all for your replys! At least I feel heard by the community.> > ...> > [ ... lengthy pamphlet, repeated three(!) times ... ]> > Martin, why don't you simply remove the cThread::EmergencyExit(true)> calls from recorder.c and remux.c?> > Klaus> > _______________________________________________> vdr mailing list> vdr(a)linuxtv.org> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr _________________________________________________________________ MSN Unterhaltung: Alle TV - Highlights - Mit der MSN Programmsuche! Jetzt checken! http://tv.unterhaltung.msn.de/tv?ocid=BAN1v0

1 0

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 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

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": This allows other plugins to access and manage many components of epgsearch as searchtimers, setup values,... and execute tasks like searching for repeats (Have a look at services.h for more information). - new project homepage: http://winni.vdr-developer.org/epgsearch, many thanks to Thomas Keil, sorry, only german at the moment ;) - update for finnish translation, thanks to Rolf Ahrenberg fixes: - complete rewrite of the summary menu and its navigation to avoid problems with skins and fix some other bugs. - when testing for repeats now also the comparison with the done-file only checks the alphanumeric portions of title and episode - fixed another issue with quotes when calling commands for EPG events - some license changes and additions for integration in Debian repositories - fixed a bug in displayed time, when using user defined times and shifting with FRew/FFwd, thanks to Torsten Weigelt for reporting - the aux info about the channel was not added in 'one press timer creation'. Thanks to Rolf Ahrenberg for providing a patch. Description and download: http://winni.vdr-developer.org/epgsearch wget: http://winni.vdr-developer.org/epgsearch/downloads/vdr-epgsearch-0.9.22.tgz Have fun! Christian

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), syncing issue? Why screen is not updated progressive just before drawing.. Or is it so that video card don't know when TV is drawing the picture?!? -- JJussi

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr