Re: [vdr] searching a HW problem

2013-10-20 Thread Stephan Loescher

Am 10/17/13 00:31, schrieb Klaus Schmidinger:

On 16.10.2013 21:23, Torsten Mohr wrote:

[...]


This shows you which device was used for the recording.


Is there a way to code this into the recording name?


No need to, just look it up in the log.


Oh, there could be a need to have the recording-device been noted in 
e.g. the info-file.

I had this use case:
Several months ago one of my tuners on one of my three identical cards 
went bad, resulting in drop-outs which caused pixel-artifacts and other 
errors while replaying.
I have not the time to view my recordings soon after recording, so I 
noticed the bad recordings several months after the first drop-out.
And it took me several weeks to find out the "bad card", so for this 
case it would have been very helful to see via the info-file: Ah, it's 
device number two which does always bad recodings since April with a 
little grep.

Perhaps this could be an additional feature for vdr-development. :-)
And even more helpful would be to notice the name of the card instead of 
the device number which is subject to change between reboots. Or even both.


Regards,
Stephan.

--
loesc...@gmx.de
http://www.loescher-online.de/

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] VDPAU deinterlacing

2013-10-20 Thread Füley István

2013.10.20. 16:09 keltezéssel, Tony Houghton írta:

I recorded it from the 4Seven channel because I forgot about the first
showing on C4HD, and it seems only this channel is affected. Maybe
they haven't set deinterlacing flags correctly?


You should check the following line in ~/.xine/config_xineliboutput:

# vdpau: disable deinterlacing when progressive_frame flag is set
# bool, default: 0
video.output.vdpau_honor_progressive:0

If it's set to 1, and the provider is not sending it correctly, 
xineliboutput won't make deinterlacing.


Istvan



___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


[vdr] reelchannelscan: scan abborted

2013-10-20 Thread Halim Sahin
Hi,
reelchannelscan seems not working here when trying to scan for dvb-t
channels.
Other stuff dvb-c/s not tested.
I get scan aborted and nothing happens.

Is this problem known or where can I donwload latest version of that
plugin for plain vdr?
Regards
Halim


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] [ANNOUNCE] VDR developer version 2.1.2

2013-10-20 Thread Eike
Hello!

> This sounds like great news :-) What kind of features does premashif
> have? 

I guess you know the current state of Permashift? It records to disc 
(but not to RAM) and already adds the recorded stuff to the beginning 
of an instant recording. The warning you wanted could probably be 
done with a hooked script triggered when switching. This version can be 
fetched here: 
http://ein-eike.de/vdr-plugin-permashift-english/

> Will you be able to choose where the timeshift will be written (eg
> ram)? What about if you are watching a program, and realize that you
> want to record it, will it copy the beginning of the program to the
> recording if it's in the timeshift? And if i'm watching from the
> timeshift, and i change accidentally the channel, will there be an
> option that would warn me that i'm watching timeshift? :-)

What I'm trying to do now is recording to RAM and putting this only
to disc when it's needed. While the basics are not that hard to do, 
the real time needs of the VDR system are somewhat harder to cope 
with. So I don't want to promise too much. But if it works out, it should 
fit your needs.

Ciao,
Eike


signature.asc
Description: This is a digitally signed message part.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


[vdr] VDPAU deinterlacing

2013-10-20 Thread Tony Houghton
Last night I tried to watch my recording of the final I.T. Crowd, but it
was unwatchable because of the interlacing. However, other programmes
look OK. Whatever I put for video.output.vdpau_hd_deinterlace_method and
video.output.vdpau_sd_deinterlace_method in ~/.xine/config_xineliboutput
it gets replaced with "bob". The OSD doesn't have any options for VDPAU
and none of the options it does have seem to make any difference.

I recorded it from the 4Seven channel because I forgot about the first
showing on C4HD, and it seems only this channel is affected. Maybe
they haven't set deinterlacing flags correctly? It does seem to be an
issue of interlacing being disabled when it should be enabled, because
my recording played correctly in mplayer with deinterlacing enabled.

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] Editing lock

2013-10-20 Thread Klaus Schmidinger

On 20.10.2013 13:30, Thomas Maass wrote:

Hi!
I think, VDR should implement something like an editing lock,
that prevents deleting, renaming, moving or cutting the
recording. It would make something more safe. For example
renaming or moving while cutting is active, a plugin should
not alter anything. And VDR should also be prevented, when
a plugin is doing something similar.


The new functions to queue renaming, moving and cutting recordings
already do this. And plugins can use the cRecording::IsInUse()
function just as well.

Or am I missing something?

Klaus

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


[vdr] Editing lock

2013-10-20 Thread Thomas Maass
Hi!
I think, VDR should implement something like an editing lock,
that prevents deleting, renaming, moving or cutting the
recording. It would make something more safe. For example
renaming or moving while cutting is active, a plugin should
not alter anything. And VDR should also be prevented, when
a plugin is doing something similar.

Thomas
-- 
gpg-id: D31AAEEA
https://www.setho.org/people

signature.asc
Description: This is a digitally signed message part.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] [ANNOUNCE] VDR developer version 2.1.2

2013-10-20 Thread René

On 19.10.2013 19:38 , Eike wrote:

Hello!


Do you have any idea when you will start to implement the "livebuffer"
feature into VDR?


I worked on rewriting Permashift to use a real live buffer the last weeks
and when it's finished and tested I'd be happy if Klaus would consider
adopting it.


Hi Eike,

This sounds like great news :-) What kind of features does premashif 
have? Will you be able to choose where the timeshift will be written (eg 
ram)? What about if you are watching a program, and realize that you 
want to record it, will it copy the beginning of the program to the 
recording if it's in the timeshift? And if i'm watching from the 
timeshift, and i change accidentally the channel, will there be an 
option that would warn me that i'm watching timeshift? :-)


Regards,

René

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr