Hi All,
Sometimes I watch a TV show halfway. Then I let VDR shutdown my PC. Then I would like to watch the rest of the show. Then I have to go to the list of TV shows, and find the correct one again.
In my opinion it would be easyer for me if the half-watched shows are placed at the top of the list with TV shows. Does such an option exist? How should recordings in a sub-folder be handled? Should those be moved to the top of the list, or copied, or a shortcut be made? I would like to see a shortcut.
I would also like to see that VDR remembers the current position in the list of recordings. This is already the case during a vdr-sxfe session, but not when vdr has been restarted. After a restart, VDR goes to the top of the list.
Or I should not have so many recordings :-)
Best regards, Cedric
Hi,
Am 06.01.2013 11:31, schrieb cedric.dewijs@telfort.nl:
Sometimes I watch a TV show halfway. Then I let VDR shutdown my PC. Then I would like to watch the rest of the show. Then I have to go to the list of TV shows, and find the correct one again.
In my opinion it would be easyer for me if the half-watched shows are placed at the top of the list with TV shows. Does such an option exist? How should recordings in a sub-folder be handled? Should those be moved to the top of the list, or copied, or a shortcut be made? I would like to see a shortcut.
I would also like to see that VDR remembers the current position in the list of recordings. This is already the case during a vdr-sxfe session, but not when vdr has been restarted. After a restart, VDR goes to the top of the list.
Or I should not have so many recordings :-)
It's possible to write a plugin "lastviewed" (if not already exist) which tracks for cStatus::Replaying and remember the replayed recodings in an internal list. With the main menu entry of this plugin you can either show the list or just replay the last recording. So no need to extend vdr-core. :)
Lars.
Best regards, Cedric
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
On 01/06/2013 12:31 PM, cedric.dewijs@telfort.nl wrote:
Sometimes I watch a TV show halfway. Then I let VDR shutdown my PC. Then I would like to watch the rest of the show. Then I have to go to the list of TV shows, and find the correct one again.
Hi
I have made a small plugin to keep history of replayed recording to help find recently watched recordings. This is not exactly what you were looking for but might be useful.
Latest version of the plugin is attached. I think I'll add the plugin to vdr-developer.org.
On 01/06/2013 12:31 PM, cedric.dewijs@telfort.nl wrote:
Hi All,
Sometimes I watch a TV show halfway. Then I let VDR shutdown my PC. Then I would like to watch the rest of the show. Then I have to go to the list of TV shows, and find the correct one again.
In my opinion it would be easyer for me if the half-watched shows are placed at the top of the list with TV shows. Does such an option exist? How should recordings in a sub-folder be handled? Should those be moved to the top of the list, or copied, or a shortcut be made? I would like to see a shortcut.
Maybe by extending the current functionality of "0" key that can be used for sorting the recordings either by name or date.
Mika
Hi,
Am 06.01.2013 12:33, schrieb Mika Laitio:
On 01/06/2013 12:31 PM, cedric.dewijs@telfort.nl wrote:
Hi All,
Sometimes I watch a TV show halfway. Then I let VDR shutdown my PC. Then I would like to watch the rest of the show. Then I have to go to the list of TV shows, and find the correct one again.
In my opinion it would be easyer for me if the half-watched shows are placed at the top of the list with TV shows. Does such an option exist? How should recordings in a sub-folder be handled? Should those be moved to the top of the list, or copied, or a shortcut be made? I would like to see a shortcut.
Maybe by extending the current functionality of "0" key that can be used for sorting the recordings either by name or date.
I don't think this is the right way since the order of recordings is per directory and the last viewed recording may be in some (deep) subdirectory. And I don't see any "last viewed timestamp" at the recording info. Only hint would be the timestamp of the resume file.
Lars.
Mika
Maybe VDR should have 3 flags instead of * (unviewed) and no-* (viewed). Instead maybe we could have:
no-*: viewed !: partially viewed *: new/unviewed
Hi,
Am 06.01.2013 17:49, schrieb VDR User:
Maybe VDR should have 3 flags instead of * (unviewed) and no-* (viewed). Instead maybe we could have:
no-*: viewed !: partially viewed *: new/unviewed
Every uncut recording will be partially viewed...
Lars.
On Sun, Jan 6, 2013 at 9:37 AM, Lars Hanisch dvb@flensrocker.de wrote:
Am 06.01.2013 17:49, schrieb VDR User:
Maybe VDR should have 3 flags instead of * (unviewed) and no-* (viewed). Instead maybe we could have:
no-*: viewed !: partially viewed *: new/unviewed
Every uncut recording will be partially viewed...
Ok, maybe this then:
*: new/unviewed !: partially viewed (if viewed 5+ minutes) (nothing): viewed completely
Hi, Happy new year 2013 to Klaus and all vdr users !!
Under vdr-1.7.x and xineliboutput, I have some trouble with **tree** dvb-t HD french channels (Eiffel Tower near Paris) : - SD channels : OK - HD channels : all OK except "France2 HD", "M6HD" and "6ter" (see below).
Channels "KO" When I zap on one of them, image appears about one second, freezes, and then I get a black screen. Sometimes it's impossible to zap to another channel, vdr-sxfe can't drive vdr anymore, and I have to reload vdr. Sometimes, afert about 10s, image appears for one second, and freezes again, and then I get black screen.
Here is latest tests performed on a Wheezy x64 fresh install. Same issues (signal strenght about 82%) : - with NOVA-T-500 tuner - with TBS6280 tuner - alternating vdr-1.7.27 (+ patch ppid) and vdr-7.1.33. - With parameter menu> configuration> DVB card> update channels "NO" - With parameter menu> configuration> DVB card> update channels "name and pid"
Installation is OK, no problem under Win7. Could you please help me to find what's wrong ? Could it be a bad setting of config_xineliboutput ?
Thanks a lot ! Karim
channels.conf :@201 TF1 HD;MR5:530000:B8C34G8M64S0T8Y0:T:27500:120=27:0;130=fra@122,131=qaa@122,132= qad@122:0;140=fra,141=fra:0:1281:8442:5:0 France 2 HD;MR5:530000:B8S0Y0:T:27500:220=27:0;230=fra@122,231=qaa@122,232=qad@122:0; 240=fra,241=fra:0:1282:8442:5:0 :@206 M6HD;MR5:530000:B8C23M2S0T8Y0:T:27500:320=27:0;330=fra@122,331=qaa@122,332=q ad@122:0;340=fra,341=fra:0:1283:8442:5:0 ARTE HD;Multi 4:546000:B8C23M64T8Y0:T:27500:720=27:731=qaa@3,732=deu@3,733=qad@3,730=fra@3 :0;740=fra,741=deu,742=fra:0:1031:8442:4:0 HD1;MHD7:642000:B8C23M64S0T8Y0:T:27500:120=27:0;130=fra@122,131=qaa@122,132= qad@122:0;150=fra,151=fra:0:2561:8442:10:0 RMC DECOUVERTE;R8:770000:B8C23M64S0T8Y0:T:27500:320=27:0;330=fra@122,331=qaa@122 ,332=qad@122:0;340=fra,341=fra:0:2819:8442:11:0 Chérie 25;MHD7:642000:B8C23M64S0T8Y0:T:27500:320=27:0;330=fra@122,331=qaa@122,332=q ad@122:0;350=fra:0:2563:8442:10:0 NUMERO 23;R8:770000:B8C23M64S0T8Y0:T:27500:220=27:0;230=fra@122,231=qaa@122,232=qad @122:0;240=fra,241=fra:0:2818:8442:11:0 6ter;R8:770000:B8S0Y0:T:27500:120=27:0;130=fra@122,131=qaa@122,132=qad@122:0 ;140=fra,141=fra:0:2817:8442:11:0 L'Equipe 21;MHD7:642000:B8C23M64S0T8Y0:T:27500:220=27:0;230=fra@122,231=qad@122:0;250 =fra:0:2562:8442:10:0
vdr-sxfe Jan 6 20:29:56 pctest vdr: [4480] switching to channel 202 Jan 6 20:29:56 pctest vdr: [4792] TS buffer on device 3 thread ended (pid=4480, tid=4792) Jan 6 20:29:56 pctest vdr: [4791] buffer stats: 164688 (3%) used Jan 6 20:29:56 pctest vdr: [4791] receiver on device 3 thread ended (pid=4480, tid=4791) Jan 6 20:29:56 pctest vdr: [4802] receiver on device 3 thread started (pid=4480, tid=4802, prio=high) Jan 6 20:29:56 pctest vdr: [4803] TS buffer on device 3 thread started (pid=4480, tid=4803, prio=high) Jan 6 20:29:58 pctest vdr: [4802] [xine..put] H.264: Found NAL SPS at offset 8/152 Jan 6 20:29:58 pctest vdr: [4802] [xine..put] H.264 SPS: profile_idc 100 Jan 6 20:29:58 pctest vdr: [4802] [xine..put] H.264 SPS: pic_width: 120 mbs Jan 6 20:29:58 pctest vdr: [4802] [xine..put] H.264 SPS: pic_height: 34 mbs Jan 6 20:29:58 pctest vdr: [4802] [xine..put] H.264 SPS: frame only flag: 0 Jan 6 20:29:58 pctest vdr: [4802] [xine..put] H.264 SPS: MBAFF Jan 6 20:29:58 pctest vdr: [4802] [xine..put] H.264 SPS: cropping 0 0 0 2 Jan 6 20:29:58 pctest vdr: [4802] [xine..put] H.264 SPS: aspect_ratio_idc 1 Jan 6 20:29:58 pctest vdr: [4802] [xine..put] H.264 SPS: -> aspect ratio 1 / 1 Jan 6 20:29:58 pctest vdr: [4802] [xine..put] H.264 SPS: -> video size 1920x1080, aspect 1:1 Jan 6 20:29:58 pctest vdr: [4802] [xine..put] Detected video size 1920x1080 Jan 6 20:30:02 pctest vdr: [4501] [xine..put] Client connection 0 closed Jan 6 20:30:02 pctest vdr: [4786] [xine..put] cBackgroundWriter: TCP write error Jan 6 20:30:02 pctest vdr: [4786] [xine..put] (ERROR (tools/backgroundwriter.c,247): Mauvais descripteur de fichier) Jan 6 20:30:02 pctest vdr: [4501] [xine..put] Closing connection 0 Jan 6 20:30:04 pctest vdr: [4501] [xine..put] Client 0 connected: 127.0.0.1:57549 Jan 6 20:30:04 pctest vdr: [4501] loading /DATA/configVDR/plugins/xineliboutput/allowed_hosts.conf Jan 6 20:30:04 pctest vdr: [4501] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 6 20:30:04 pctest vdr: [4501] [xine..put] Client 1 connected: 127.0.0.1:57550 Jan 6 20:30:04 pctest vdr: [4501] loading /DATA/configVDR/plugins/xineliboutput/allowed_hosts.conf Jan 6 20:30:04 pctest vdr: [4501] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 6 20:30:04 pctest vdr: [4501] [xine..put] Data connection (TCP) requested Jan 6 20:30:04 pctest vdr: [4501] [xine..put] cBackgroundWriterI initialized (buffer 2048 kb) Jan 6 20:30:04 pctest vdr: [4501] [xine..put] cTcpWriter initialized (buffer 2048 kb) Jan 6 20:30:04 pctest vdr: [4501] [xine..put] Client connection 0 closed Jan 6 20:30:04 pctest vdr: [4501] [xine..put] Closing connection 0 Jan 6 20:30:06 pctest vdr: [4501] [xine..put] Client 0 connected: 127.0.0.1:57551 Jan 6 20:30:06 pctest vdr: [4501] loading /DATA/configVDR/plugins/xineliboutput/allowed_hosts.conf Jan 6 20:30:06 pctest vdr: [4501] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 6 20:30:06 pctest vdr: [4501] [xine..put] Client 1 connected: 127.0.0.1:57552 Jan 6 20:30:06 pctest vdr: [4501] loading /DATA/configVDR/plugins/xineliboutput/allowed_hosts.conf Jan 6 20:30:06 pctest vdr: [4501] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 6 20:30:06 pctest vdr: [4501] [xine..put] Data connection (TCP) requested Jan 6 20:30:06 pctest vdr: [4501] [xine..put] cBackgroundWriterI initialized (buffer 2048 kb) Jan 6 20:30:06 pctest vdr: [4501] [xine..put] cTcpWriter initialized (buffer 2048 kb) Jan 6 20:30:14 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) Jan 6 20:30:14 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) Jan 6 20:30:14 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) Jan 6 20:30:14 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) Jan 6 20:30:14 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) Jan 6 20:30:14 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) Jan 6 20:30:14 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) ..... ..... Jan 6 20:30:14 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) Jan 6 20:30:14 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) Jan 6 20:30:14 pctest rsyslogd-2177: imuxsock begins to drop messages from pid 4480 due to rate-limiting Jan 6 20:30:23 pctest rsyslogd-2177: imuxsock lost 804 messages from pid 4480 due to rate-limiting Jan 6 20:30:23 pctest vdr: [4501] [xine..put] Client 0 connected: 127.0.0.1:57553 Jan 6 20:30:23 pctest vdr: [4501] loading /DATA/configVDR/plugins/xineliboutput/allowed_hosts.conf Jan 6 20:30:23 pctest vdr: [4501] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 6 20:30:23 pctest vdr: [4501] [xine..put] Client 1 connected: 127.0.0.1:57554 Jan 6 20:30:23 pctest vdr: [4501] loading /DATA/configVDR/plugins/xineliboutput/allowed_hosts.conf Jan 6 20:30:23 pctest vdr: [4501] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 6 20:30:23 pctest vdr: [4501] [xine..put] Data connection (TCP) requested Jan 6 20:30:23 pctest vdr: [4501] [xine..put] cBackgroundWriterI initialized (buffer 2048 kb) Jan 6 20:30:23 pctest vdr: [4501] [xine..put] cTcpWriter initialized (buffer 2048 kb) Jan 6 20:30:28 pctest vdr: [4501] [xine..put] Client connection 0 closed Jan 6 20:30:28 pctest vdr: [4827] [xine..put] cBackgroundWriter: TCP write error Jan 6 20:30:28 pctest vdr: [4827] [xine..put] (ERROR (tools/backgroundwriter.c,247): Mauvais descripteur de fichier) Jan 6 20:30:28 pctest vdr: [4501] [xine..put] Closing connection 0 Jan 6 20:30:30 pctest vdr: [4501] [xine..put] Client 0 connected: 127.0.0.1:57555 Jan 6 20:30:30 pctest vdr: [4501] loading /DATA/configVDR/plugins/xineliboutput/allowed_hosts.conf Jan 6 20:30:30 pctest vdr: [4501] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 6 20:30:30 pctest vdr: [4501] [xine..put] Client 1 connected: 127.0.0.1:57556 Jan 6 20:30:30 pctest vdr: [4501] loading /DATA/configVDR/plugins/xineliboutput/allowed_hosts.conf Jan 6 20:30:30 pctest vdr: [4501] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 6 20:30:30 pctest vdr: [4501] [xine..put] Data connection (TCP) requested Jan 6 20:30:30 pctest vdr: [4501] [xine..put] cBackgroundWriterI initialized (buffer 2048 kb) Jan 6 20:30:30 pctest vdr: [4501] [xine..put] cTcpWriter initialized (buffer 2048 kb) Jan 6 20:30:31 pctest vdr: [4501] [xine..put] Client connection 0 closed Jan 6 20:30:31 pctest vdr: [4501] [xine..put] Closing connection 0 Jan 6 20:30:33 pctest vdr: [4501] [xine..put] Client 0 connected: 127.0.0.1:57557 Jan 6 20:30:33 pctest vdr: [4501] loading /DATA/configVDR/plugins/xineliboutput/allowed_hosts.conf Jan 6 20:30:33 pctest vdr: [4501] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 6 20:30:33 pctest vdr: [4501] [xine..put] Client 1 connected: 127.0.0.1:57558 Jan 6 20:30:33 pctest vdr: [4501] loading /DATA/configVDR/plugins/xineliboutput/allowed_hosts.conf Jan 6 20:30:33 pctest vdr: [4501] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 6 20:30:33 pctest vdr: [4501] [xine..put] Data connection (TCP) requested Jan 6 20:30:33 pctest vdr: [4501] [xine..put] cBackgroundWriterI initialized (buffer 2048 kb) Jan 6 20:30:33 pctest vdr: [4501] [xine..put] cTcpWriter initialized (buffer 2048 kb) Jan 6 20:30:38 pctest vdr: [4501] [xine..put] Client connection 0 closed Jan 6 20:30:38 pctest vdr: [4501] [xine..put] Closing connection 0 Jan 6 20:30:40 pctest vdr: [4501] [xine..put] Client 0 connected: 127.0.0.1:57559 Jan 6 20:30:40 pctest vdr: [4501] loading /DATA/configVDR/plugins/xineliboutput/allowed_hosts.conf Jan 6 20:30:40 pctest vdr: [4501] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 6 20:30:40 pctest vdr: [4501] [xine..put] Client 1 connected: 127.0.0.1:57560 Jan 6 20:30:40 pctest vdr: [4501] loading /DATA/configVDR/plugins/xineliboutput/allowed_hosts.conf Jan 6 20:30:40 pctest vdr: [4501] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 6 20:30:40 pctest vdr: [4501] [xine..put] Data connection (TCP) requested Jan 6 20:30:40 pctest vdr: [4501] [xine..put] cBackgroundWriterI initialized (buffer 2048 kb) Jan 6 20:30:40 pctest vdr: [4501] [xine..put] cTcpWriter initialized (buffer 2048 kb) Jan 6 20:30:51 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) Jan 6 20:30:51 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) Jan 6 20:30:51 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) Jan 6 20:30:51 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) .... .... Jan 6 20:30:51 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) Jan 6 20:30:51 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) Jan 6 20:30:51 pctest rsyslogd-2177: imuxsock begins to drop messages from pid 4480 due to rate-limiting Jan 6 20:31:05 pctest rsyslogd-2177: imuxsock lost 206 messages from pid 4480 due to rate-limiting Jan 6 20:31:05 pctest vdr: [4501] [xine..put] Client connection 0 closed Jan 6 20:31:05 pctest vdr: [4864] [xine..put] cBackgroundWriter: TCP write error Jan 6 20:31:05 pctest vdr: [4864] [xine..put] (ERROR (tools/backgroundwriter.c,247): Mauvais descripteur de fichier) Jan 6 20:31:05 pctest vdr: [4501] [xine..put] Closing connection 0 Jan 6 20:31:07 pctest vdr: [4501] [xine..put] Client 0 connected: 127.0.0.1:57565 Jan 6 20:31:07 pctest vdr: [4501] loading /DATA/configVDR/plugins/xineliboutput/allowed_hosts.conf Jan 6 20:31:07 pctest vdr: [4501] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 6 20:31:07 pctest vdr: [4501] [xine..put] Client 1 connected: 127.0.0.1:57566 Jan 6 20:31:07 pctest vdr: [4501] loading /DATA/configVDR/plugins/xineliboutput/allowed_hosts.conf Jan 6 20:31:07 pctest vdr: [4501] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 6 20:31:07 pctest vdr: [4501] [xine..put] Data connection (TCP) requested Jan 6 20:31:07 pctest vdr: [4501] [xine..put] cBackgroundWriterI initialized (buffer 2048 kb) Jan 6 20:31:07 pctest vdr: [4501] [xine..put] cTcpWriter initialized (buffer 2048 kb) Jan 6 20:31:08 pctest vdr: [4501] [xine..put] Client connection 0 closed Jan 6 20:31:08 pctest vdr: [4501] [xine..put] Closing connection 0 Jan 6 20:31:10 pctest vdr: [4501] [xine..put] Client 0 connected: 127.0.0.1:57567 Jan 6 20:31:10 pctest vdr: [4501] loading /DATA/configVDR/plugins/xineliboutput/allowed_hosts.conf Jan 6 20:31:10 pctest vdr: [4501] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 6 20:31:10 pctest vdr: [4501] [xine..put] Client 1 connected: 127.0.0.1:57568 Jan 6 20:31:10 pctest vdr: [4501] loading /DATA/configVDR/plugins/xineliboutput/allowed_hosts.conf Jan 6 20:31:10 pctest vdr: [4501] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 6 20:31:10 pctest vdr: [4501] [xine..put] Data connection (TCP) requested Jan 6 20:31:10 pctest vdr: [4501] [xine..put] cBackgroundWriterI initialized (buffer 2048 kb) Jan 6 20:31:10 pctest vdr: [4501] [xine..put] cTcpWriter initialized (buffer 2048 kb) Jan 6 20:31:20 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) Jan 6 20:31:20 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) Jan 6 20:31:20 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) etc..
Hi
After reading all response, there is still an open question : why vdr do not simply store inside setup.conf the latest path of played recording ? As long it keep it in memory (press play resume the replay of records) ...
You will say : what about removed records outside vdr program ? it allready does by not playing them even if on the list , in my system, I read from a vdr client under smb vdr tree of a server and remove records from client, vdr server list is not allways up to date (a touch .update fix that)
It should be nice to have this feature in the system like the xineliboutput player plugin do
Thanks and have a nice evening
Le dimanche 06 janvier 2013 11:31:54, cedric.dewijs@telfort.nl a écrit :
Hi All,
Sometimes I watch a TV show halfway. Then I let VDR shutdown my PC. Then I would like to watch the rest of the show. Then I have to go to the list of TV shows, and find the correct one again.
In my opinion it would be easyer for me if the half-watched shows are placed at the top of the list with TV shows. Does such an option exist? How should recordings in a sub-folder be handled? Should those be moved to the top of the list, or copied, or a shortcut be made? I would like to see a shortcut.
I would also like to see that VDR remembers the current position in the list of recordings. This is already the case during a vdr-sxfe session, but not when vdr has been restarted. After a restart, VDR goes to the top of the list.
Or I should not have so many recordings :-)
Best regards, Cedric
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
On Sun, Jan 6, 2013 at 11:23 AM, Dominique dplu@free.fr wrote:
Hi
After reading all response, there is still an open question : why vdr do not simply store inside setup.conf the latest path of played recording ? As long it keep it in memory (press play resume the replay of records) ...
You will say : what about removed records outside vdr program ? it allready does by not playing them even if on the list , in my system, I read from a vdr client under smb vdr tree of a server and remove records from client, vdr server list is not allways up to date (a touch .update fix that)
It should be nice to have this feature in the system like the xineliboutput player plugin do
What about when a guy watches his recording but can't finish so he stops it and will return later. Before he can return, his wife comes and watches her recording. The last recording will now be the one the wife watched and not the guy. Many VDR systems are used by multiple people, not just one person only. I think 3 "viewed" flags are fine to keep track of unviewed/partial viewed/complete viewed.
On 01/06/2013 10:07 PM, VDR User wrote:
On Sun, Jan 6, 2013 at 11:23 AM, Dominiquedplu@free.fr wrote:
Hi
After reading all response, there is still an open question : why vdr do not simply store inside setup.conf the latest path of played recording ? As long it keep it in memory (press play resume the replay of records) ...
You will say : what about removed records outside vdr program ? it allready does by not playing them even if on the list , in my system, I read from a vdr client under smb vdr tree of a server and remove records from client, vdr server list is not allways up to date (a touch .update fix that)
It should be nice to have this feature in the system like the xineliboutput player plugin do
What about when a guy watches his recording but can't finish so he stops it and will return later. Before he can return, his wife comes and watches her recording. The last recording will now be the one the wife watched and not the guy. Many VDR systems are used by multiple people, not just one person only. I think 3 "viewed" flags are fine to keep track of unviewed/partial viewed/complete viewed.
The History-plugin I posted to this thread remembers user defined number of replayed recordings so it probably easier than searching through the recording list for partially watched recordings. Replaying can be easily started from the list. The plugin also handles removed recordings appropriately.
The plugin also stores history of replayed files using xineliboutput's Media Player. Replay of these can also be started from the plugin menu.
an additional problem is the definition of "viewed". I don't normally view the end credits. Also, I have normally 10min extra in the end of each recording, just in case. So normally there are around 10-15mins in the end of a viewed recording that have not been viewed. But this would probably vary - a little different for each user.
Seems a difficult thing to do "right". Matti's plugin sounds like a working solution, instead.
yours, Jouni
On Mon, Jan 7, 2013 at 9:58 AM, Jouni Karvo Jouni.Karvo@iki.fi wrote:
an additional problem is the definition of "viewed". I don't normally view the end credits. Also, I have normally 10min extra in the end of each recording, just in case. So normally there are around 10-15mins in the end of a viewed recording that have not been viewed. But this would probably vary - a little different for each user.
Seems a difficult thing to do "right". Matti's plugin sounds like a working solution, instead.
I don't think it's difficult to do right at all to be honest. You can just make user-defined thresholds so the the user can decide himself how many mins or % of the total recording triggers the partial-view and viewed flags. For example one guy might want:
not-viewed: <5% viewed partial-viewed: 5%+ viewed viewed: 95%+ viewed
and another guy could customize it differently such as <10%, 10%+, 99%+... This way the user gets the 3 flags and gets to decide when they're triggered. I think this would satisfy the majority/most users with low difficulty to implement.
I don't think it's difficult to do right at all to be honest. You can just make user-defined thresholds so the the user can decide himself how many mins or % of the total recording triggers the partial-view and viewed flags. For example one guy might want:
not-viewed: <5% viewed partial-viewed: 5%+ viewed viewed: 95%+ viewed
and another guy could customize it differently such as <10%, 10%+, 99%+... This way the user gets the 3 flags and gets to decide when they're triggered. I think this would satisfy the majority/most users with low difficulty to implement.
Percentages would not work well as 5% is much more from 20 minute recording than 2 hour movie.
But a little related to this, I think it would be great if there could be some kind of short cut for command that one could use after watching the recording to cut away end of the recording. So when ending texts start, one key press would just cut rest away and also stop the viewing.
Mika
On 08.01.2013 22:47, Mika Laitio wrote:
I don't think it's difficult to do right at all to be honest. You can just make user-defined thresholds so the the user can decide himself how many mins or % of the total recording triggers the partial-view and viewed flags. For example one guy might want:
not-viewed: <5% viewed partial-viewed: 5%+ viewed viewed: 95%+ viewed
and another guy could customize it differently such as <10%, 10%+, 99%+... This way the user gets the 3 flags and gets to decide when they're triggered. I think this would satisfy the majority/most users with low difficulty to implement.
Percentages would not work well as 5% is much more from 20 minute recording than 2 hour movie.
But a little related to this, I think it would be great if there could be some kind of short cut for command that one could use after watching the recording to cut away end of the recording. So when ending texts start, one key press would just cut rest away and also stop the viewing.
I could imagine the following:
- define a User0 key on your remote control (or User1, 2, ... 9)
- in keymacros.conf add a line User0 0 7 0 9 2 Stop
When you press the User0 key during replay it should then
- set a mark at the current position - jump to the very beginning of the recording - set a mark at the beginning - jump back to where you stopped viewing - start the
On 08.01.2013 23:38, Klaus Schmidinger wrote:
On 08.01.2013 22:47, Mika Laitio wrote:
I don't think it's difficult to do right at all to be honest. You can just make user-defined thresholds so the the user can decide himself how many mins or % of the total recording triggers the partial-view and viewed flags. For example one guy might want:
not-viewed: <5% viewed partial-viewed: 5%+ viewed viewed: 95%+ viewed
and another guy could customize it differently such as <10%, 10%+, 99%+... This way the user gets the 3 flags and gets to decide when they're triggered. I think this would satisfy the majority/most users with low difficulty to implement.
Percentages would not work well as 5% is much more from 20 minute recording than 2 hour movie.
But a little related to this, I think it would be great if there could be some kind of short cut for command that one could use after watching the recording to cut away end of the recording. So when ending texts start, one key press would just cut rest away and also stop the viewing.
I could imagine the following:
define a User0 key on your remote control (or User1, 2, ... 9)
in keymacros.conf add a line User0 0 7 0 9 2 Stop
When you press the User0 key during replay it should then
- set a mark at the current position
- jump to the very beginning of the recording
- set a mark at the beginning
- jump back to where you stopped viewing
- start the
[ sorry, hit the wrong button here ]
- start the editing process - end replay
Of course this will only work correctly if there are no editing marks defined yet.
Klaus
On Tue, Jan 8, 2013 at 1:47 PM, Mika Laitio lamikr@pilppa.org wrote:
I don't think it's difficult to do right at all to be honest. You can just make user-defined thresholds so the the user can decide himself how many mins or % of the total recording triggers the partial-view and viewed flags. For example one guy might want:
not-viewed: <5% viewed partial-viewed: 5%+ viewed viewed: 95%+ viewed
and another guy could customize it differently such as <10%, 10%+, 99%+... This way the user gets the 3 flags and gets to decide when they're triggered. I think this would satisfy the majority/most users with low difficulty to implement.
Percentages would not work well as 5% is much more from 20 minute recording than 2 hour movie.
Percentages make the most sense to me because 1) the user can decide for himself what threshold he wants to use, and 2) using a percentage when you have recordings of different lengths is better than using a single Xmin value which would probably only work well with recordings of a single length. A playtime of 20mins might work well for an hour long show but would be ridiculous for a 30min show -- hardcoded values always suck, the user can decide what he likes without outside help.
My personal preference would be 25% / 90%.
25% of 30mins is 7.5mins 25% of 60mins is 15mins 25% of 120mins is 30mins
90% of 30mins is 27mins 90% of 60mins is 54mins 90% of 120mins is 108mins
It's reasonable to say if you've watched 7.5mins of a 30min show, you've watched it partially and if you've watched 27mins, you've watched it. Same for 15mins/54mins of a 60min show, and 30mins/108mins of a 120min show.
To me that's far better than setting one value and forcing it on every recording no matter what the length is, and it makes it possible to customize it to your own individual preference (which I'm almost always a big supporter of). Problems like this are best solved when you ask what works best for most people in most cases, because there is no "perfect" solution.
-
cedric.dewijs＠telfort.nl -
Dominique -
Jouni Karvo -
kafifi -
Klaus Schmidinger -
Lars Hanisch -
Matti Lehtimäki -
Mika Laitio -
VDR User