The relook400s for example has an option (it can be turned on or off) where a 30 minutes buffer of live tv is recorded to allow to rewind livetv.
This recording is automatically deleted when you zap to another channel, hence the Wife Acceptance Factor is very high.
Whenever my wife sees in vdr 'channel not available' she freaks out and waits for me to come back from work, and then nags how vdr is not working again.
It is nearly always instant recordings causing this and she is intimidated by the routing of deleting the recoding with the @ and then zapping.
VDR is wonderful but it would not hurt to have options (I repeat options, that can be enabled only if desired) that make it more acceptable to non-technical users.
ACK.
VDR is very nice. I've been using it for years now. But it is still very much tech focused in many areas. E.g. cutting recordings is way too complicated for non-tech persons.
I'd also like to see option where live-tv pause can be enabled/disabled. It has seldom been a problem but the whole feature is not usable for our usage.
It seriously would not hurt VDR if there were Help pages available via OSD. Yes, there are man-pages but my guess is that very very few end users will actually go to terminal to check man-pages if they have some problems with VDR how to do something. They just don't bother. And this is request for Klaus because he's the author of the VDR thus should keep the help pages of VDR up-to-date. And preferably all plugin developers would do the same.
Br, Pasi
martinez@embl.de wrote:
The relook400s for example has an option (it can be turned on or off) where a 30 minutes buffer of live tv is recorded to allow to rewind livetv.
This recording is automatically deleted when you zap to another channel, hence the Wife Acceptance Factor is very high.
Whenever my wife sees in vdr 'channel not available' she freaks out and waits for me to come back from work, and then nags how vdr is not working again.
It is nearly always instant recordings causing this and she is intimidated by the routing of deleting the recoding with the @ and then zapping.
VDR is wonderful but it would not hurt to have options (I repeat options, that can be enabled only if desired) that make it more acceptable to non-technical users.
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
On Fri, May 8, 2009 at 10:30 AM, Pasi Juppo Pasi@juppo.fi wrote:
VDR is very nice. I've been using it for years now. But it is still very much tech focused in many areas. E.g. cutting recordings is way too complicated for non-tech persons.
Could you elaborate on this? The editing in VDR is very simplistic and requires no real technical skill at all. It's nothing more then setting cut points, frame stepping, and performing the cut. The user only has to know what he wants to cut/keep so I'm not sure why anyone would say it's way too complicated. I know there are some people who mix with computers like water & oil but if you can manage to use the remote, you should be able to edit just fine. ;)
Regards, Derek
VDR User wrote:
On Fri, May 8, 2009 at 10:30 AM, Pasi Juppo Pasi@juppo.fi wrote:
VDR is very nice. I've been using it for years now. But it is still very much tech focused in many areas. E.g. cutting recordings is way too complicated for non-tech persons.
Could you elaborate on this? The editing in VDR is very simplistic and requires no real technical skill at all. It's nothing more then setting cut points, frame stepping, and performing the cut. The user only has to know what he wants to cut/keep so I'm not sure why anyone would say it's way too complicated. I know there are some people who mix with computers like water & oil but if you can manage to use the remote, you should be able to edit just fine. ;)
The problem is not how to edit but which buttons needs to be pressed to set cutting marks, which to move them, which to start actual cutting etc. If you use this feature less than once per month then it's obvious that you will not remember these buttons. I can fully understand that non-technical people don't bother to remember every little detail (such as this) but simply to use it. IF there were help pages available from, pretty much, every OSD screen it would be easy to check which buttons shall be pressed to do e.g. editing.
For example regarding MPlayer plugin. I have troubles remembering which numbers are assigned to advance or delay of sound, change of subtitles etc. These are not needed often but sometimes. It would be really nice to take a look at Help page of MPlayer plugin to check what buttons are assigned to which function etc. than to go to different room, log into VDR machine, check plugin's Readme-file and get back to the couch - oh, what was assigned to the button 7..
Small things like Help pages make a huge difference to the usability of the VDR and plugins.
Br, Pasi
On 08.05.2009 21:42, Pasi Juppo wrote:
The problem is not how to edit but which buttons needs to be pressed to set cutting marks, which to move them, which to start actual cutting etc.
I agree that the editing key mapping is not very intuitive, at least not as intuitive as the rest of VDR. I'm not sure how this can be improved the best way, but I think some 'editing mode' as opposed to normal 'playback mode' may be a good solution.
This 'editing mode' could have some (OSD visible) key mapping like red->toggle mark, green->jump to last mark, yellow->jump to next mark, blue->start editing. However, this would make jumping a lot more difficult.
Or some mini-onscreen menu? Navigate to 'toggle mark' and press ok? Too difficult.
Switchable key mappings? Not intuitive.
And how to go to editing mode? No obvious key is unused or unneeded. Give it a main menu item when in playback mode?
This is probably something that will need several incarnations as a patch to find a nice and intuitive solution. Any volunteers?
Cheers,
Udo
On 09.05.2009 21:31, Udo Richter wrote:
On 08.05.2009 21:42, Pasi Juppo wrote:
The problem is not how to edit but which buttons needs to be pressed to set cutting marks, which to move them, which to start actual cutting etc.
I agree that the editing key mapping is not very intuitive, at least not as intuitive as the rest of VDR. I'm not sure how this can be improved the best way, but I think some 'editing mode' as opposed to normal 'playback mode' may be a good solution.
This 'editing mode' could have some (OSD visible) key mapping like red->toggle mark, green->jump to last mark, yellow->jump to next mark, blue->start editing. However, this would make jumping a lot more difficult.
The color keys are already in use during replay - and I really don't see how using the color keys would be any more intuitive than using the number keys.
Or some mini-onscreen menu? Navigate to 'toggle mark' and press ok? Too difficult.
Switchable key mappings? Not intuitive.
And how to go to editing mode? No obvious key is unused or unneeded. Give it a main menu item when in playback mode?
This is probably something that will need several incarnations as a patch to find a nice and intuitive solution. Any volunteers?
The only way this could be made "intuitive" is probably by using a remote control that has dedicated keys for these functions (and making them definable in VDR, but it's already prepared for that - see keys.h).
Personally I don't find the key mapping that unintuitive. After all, the number keys are unused in replay mode, so why not use them for editing?
2=Cut
4=Move Back 6=Move Forward
7=Jump Back 8=Test 9=Jump Forward
0=Toggle
How about using a marker pen and drawing some symbols onto your remote control that indicate these actions?
Klaus
Klaus Schmidinger wrote:
On 09.05.2009 21:31, Udo Richter wrote:
On 08.05.2009 21:42, Pasi Juppo wrote:
The problem is not how to edit but which buttons needs to be pressed to set cutting marks, which to move them, which to start actual cutting etc.
I agree that the editing key mapping is not very intuitive, at least not as intuitive as the rest of VDR. I'm not sure how this can be improved the best way, but I think some 'editing mode' as opposed to normal 'playback mode' may be a good solution.
This 'editing mode' could have some (OSD visible) key mapping like red->toggle mark, green->jump to last mark, yellow->jump to next mark, blue->start editing. However, this would make jumping a lot more difficult.
The color keys are already in use during replay - and I really don't see how using the color keys would be any more intuitive than using the number keys.
I would not utilize colour keys for this purpose again.
Or some mini-onscreen menu? Navigate to 'toggle mark' and press ok? Too difficult.
Switchable key mappings? Not intuitive.
And how to go to editing mode? No obvious key is unused or unneeded. Give it a main menu item when in playback mode?
This is probably something that will need several incarnations as a patch to find a nice and intuitive solution. Any volunteers?
The only way this could be made "intuitive" is probably by using a remote control that has dedicated keys for these functions (and making them definable in VDR, but it's already prepared for that - see keys.h).
Personally I don't find the key mapping that unintuitive. After all, the number keys are unused in replay mode, so why not use them for editing?
2=Cut 4=Move Back 6=Move Forward 7=Jump Back 8=Test 9=Jump Forward 0=ToggleHow about using a marker pen and drawing some symbols onto your remote control that indicate these actions?
There are ways to get this particular feature more convenient for the end user without adding marks to the remote control. Before I continue I use this opportunity to trash a bit my (Yamaha) receiver's menu system. I have to pick up manual if I want to store tuned radio channels. Last time I did it around 8 months ago and now I don't recall anymore how to do it and the menu with a bunch of buttons is so illogical that you just cannot find the way to do store channels with trial-and-error method. This is a bad example of user interface. Good that VDR is far from it but there is still a room for improvement.
And now back to business. First a quick comment to above number mapping you have written there. 8=Test, what does it do? Without manual I cannot tell - it is not obvious to end user. Probably with just pressing and seeing end user can find out what happens - hopefully nothing bad to the precious recording he/she is editing..
Udo made a good proposal above. I just modify it a bit. Small OSD for editing mode which is on all the time during editing (OK, make visibility configurable to please everyone). In the OSD there is above written keys with text of the function and also there is the playback bar showing cut marks etc. like today. Additionally there are colour keys shown where one has Help assigned, which brings help page on top of everything. During help the playback of the recording (assuming that user is in edit mode) is put on pause as end user most likely would like to read the manual in piece.
What's the difference today's functionality? Very small. Only this time user is shown more information and is provided help (a man page, if you like) in case of need.
This was one case but same philosophy can be applied to rest of the VDR as well as to the plugins. Small additional OSD could be added to show more info if end user wants to. Pros can turn it off because they know everything already by heart - rest probably not. And now that there is a request, which hopefully gets implemented, to made OSD size match display size then there is more space available for this kind of features with new HD and HD Ready TVs.
Br, Pasi
Pasi Juppo a écrit :
What's the difference today's functionality? Very small. Only this time user is shown more information and is provided help (a man page, if you like) in case of need.
Many plug-ins would benefit from such a "core" help system.
I never managed to learn the remote keys for the DVD plugin : back to DVD menu, next/previous chapter etc... The only things I can say is that those keys are very different from cutting keys, and that trial'n'error didn't work...
On 09.05.2009 22:04, Klaus Schmidinger wrote:
This 'editing mode' could have some (OSD visible) key mapping like red->toggle mark, green->jump to last mark, yellow->jump to next mark, blue->start editing. However, this would make jumping a lot more difficult.
The color keys are already in use during replay - and I really don't see how using the color keys would be any more intuitive than using the number keys.
Users don't expect number keys to do anything else than being numbers. The color keys are more 'general use', and there's already a common way to display their meaning onscreen.
Personally I don't find the key mapping that unintuitive. After all, the number keys are unused in replay mode, so why not use them for editing?
2=Cut 4=Move Back 6=Move Forward 7=Jump Back 8=Test 9=Jump Forward 0=Toggle
Yeah, but was it 7 or 1 for jumping? Does cutting start on 2 or 8?
Don't get me wrong, I can do this blindfolded in my dreams. Its just not as obvious and easy to discover for beginner/infrequent users as the rest of VDR is.
Cheers,
Udo
Udo Richter schrieb:
On 09.05.2009 22:04, Klaus Schmidinger wrote:
Personally I don't find the key mapping that unintuitive. After all, the number keys are unused in replay mode, so why not use them for editing?
2=Cut 4=Move Back 6=Move Forward 7=Jump Back 8=Test 9=Jump Forward 0=ToggleYeah, but was it 7 or 1 for jumping? Does cutting start on 2 or 8?
Don't get me wrong, I can do this blindfolded in my dreams. Its just not as obvious and easy to discover for beginner/infrequent users as the rest of VDR is.
Please PLEASE don't change that to color keys - the number keys are perfect for taht.
What i do like is the help page idea - just that there is a possibility to quickly show a keymap like written above by Klaus, next button press switch it off. Should be easy and works. Someone tested the aide plugin ?
I haved lost count the number of times I have pressed the numbered keys on my remote by accident and then panic because I don't know how to undo what then happened.
This is definitely a trap for unsuspecting beginners.
Some kind of editing mode would be safer. Otherwise the key layout is ok.
Stuart
--- On Sat, 9/5/09, Udo Richter udo_richter@gmx.de wrote:
From: Udo Richter udo_richter@gmx.de Subject: Re: [vdr] Editing usability To: "VDR Mailing List" vdr@linuxtv.org Date: Saturday, 9 May, 2009, 9:59 PM On 09.05.2009 22:04, Klaus Schmidinger wrote:
This 'editing mode' could have some (OSD
visible) key mapping like
red->toggle mark, green->jump to last mark,
yellow->jump to next mark,
blue->start editing. However, this would make
jumping a lot more difficult.
The color keys are already in use during replay - and
I really don't see
how using the color keys would be any more intuitive
than using the
number keys.
Users don't expect number keys to do anything else than being numbers. The color keys are more 'general use', and there's already a common way to display their meaning onscreen.
Personally I don't find the key mapping that
unintuitive. After all,
the number keys are unused in replay mode, so why not
use them for
editing?
2=Cut 4=Move Back 6=Move Forward 7=Jump Back 8=Test 9=Jump Forward 0=ToggleYeah, but was it 7 or 1 for jumping? Does cutting start on 2 or 8?
Don't get me wrong, I can do this blindfolded in my dreams. Its just not as obvious and easy to discover for beginner/infrequent users as the rest of VDR is.
Cheers,
Udo
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
On Mon, May 11, 2009 at 1:36 AM, Stuart Morris stuart_morris@talk21.com wrote:
I haved lost count the number of times I have pressed the numbered keys on my remote by accident and then panic because I don't know how to undo what then happened.
This is definitely a trap for unsuspecting beginners.
I mean this in the nicest way possible but paying more attention to what you're pressing would pretty much resolve your problem.
In all honesty most of the complaints I've read have little or no real issue with VDR itself but rather the users either not paying attention to what they're doing, not bothering to read the manual & memorize the few keys involved, and/or wanting VDR to kid-proof the remote for them. It seems all of these "problems" could be eliminated with a little extra effort by the user. That being said, if there's something that could be done to help and Klaus is willing to do it then super. Or better yet if someone else takes it upon himself to create these patches so Klaus can be left to focus on the bigger fish to fry.
For the record, I have kids, who can be more like monkeys often times, and have no problem keeping the remote away from their curious fingers. I've accidentally pressed buttons that had undesired actions before as well. So, when I say these problems can be resolved with a little more effort & attention on the users part, I'm speaking from experience. Of course it's easier to decide you can't be bothered with it on your end and ask someone else to fix it for you, but truthfully speaking the user-side fix isn't exactly hard to begin with. I guess we'll have to agree to disagree as to how serious of an issue this stuff is, or whether it's even a problem with VDR itself or not.
Regards, Derek
Hi
I have also no problem with editing keys and I find this option fine, keys are easy to learn and it is intuitive. The only time I can do error when replaying recording is pressing the "2" keys who run the cutting process (that you can concel in the menu very easyly)
Maybe the solution to your problem should be to enabe those "editing" keys only when the progress bar edition is displayed like it does when you want to goto at a time point
Have a nice day and thanks Klaus for the very good job
Dom
Selon VDR User user.vdr@gmail.com:
On Mon, May 11, 2009 at 1:36 AM, Stuart Morris stuart_morris@talk21.com wrote:
I haved lost count the number of times I have pressed the numbered keys on
my remote by accident and then panic because I don't know how to undo what then happened.
This is definitely a trap for unsuspecting beginners.
I mean this in the nicest way possible but paying more attention to what you're pressing would pretty much resolve your problem.
In all honesty most of the complaints I've read have little or no real issue with VDR itself but rather the users either not paying attention to what they're doing, not bothering to read the manual & memorize the few keys involved, and/or wanting VDR to kid-proof the remote for them. It seems all of these "problems" could be eliminated with a little extra effort by the user. That being said, if there's something that could be done to help and Klaus is willing to do it then super. Or better yet if someone else takes it upon himself to create these patches so Klaus can be left to focus on the bigger fish to fry.
For the record, I have kids, who can be more like monkeys often times, and have no problem keeping the remote away from their curious fingers. I've accidentally pressed buttons that had undesired actions before as well. So, when I say these problems can be resolved with a little more effort & attention on the users part, I'm speaking from experience. Of course it's easier to decide you can't be bothered with it on your end and ask someone else to fix it for you, but truthfully speaking the user-side fix isn't exactly hard to begin with. I guess we'll have to agree to disagree as to how serious of an issue this stuff is, or whether it's even a problem with VDR itself or not.
Regards, Derek
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
On Mon, 2009-05-11 at 07:06 -0700, VDR User wrote:
On Mon, May 11, 2009 at 1:36 AM, Stuart Morris stuart_morris@talk21.com wrote:
I haved lost count the number of times I have pressed the numbered keys on my remote by accident and then panic because I don't know how to undo what then happened.
This is definitely a trap for unsuspecting beginners.
I mean this in the nicest way possible but paying more attention to what you're pressing would pretty much resolve your problem.
In all honesty most of the complaints I've read have little or no real issue with VDR itself but rather the users either not paying attention to what they're doing, not bothering to read the manual & memorize the few keys involved, and/or wanting VDR to kid-proof the remote for them. It seems all of these "problems" could be eliminated with a little extra effort by the user. That being said, if there's something that could be done to help and Klaus is willing to do it then super. Or better yet if someone else takes it upon himself to create these patches so Klaus can be left to focus on the bigger fish to fry.
For the record, I have kids, who can be more like monkeys often times, and have no problem keeping the remote away from their curious fingers.
Perhaps I should keep my remote at your house?
:)
I've accidentally pressed buttons that had undesired actions before as well. So, when I say these problems can be resolved with a little more effort & attention on the users part, I'm speaking from experience. Of course it's easier to decide you can't be bothered with it on your end and ask someone else to fix it for you, but truthfully speaking the user-side fix isn't exactly hard to begin with. I guess we'll have to agree to disagree as to how serious of an issue this stuff is, or whether it's even a problem with VDR itself or not.
Regards, Derek
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
On Sat, May 9, 2009 at 1:04 PM, Klaus Schmidinger Klaus.Schmidinger@cadsoft.de wrote:
Personally I don't find the key mapping that unintuitive. After all, the number keys are unused in replay mode, so why not use them for editing?
2=Cut
4=Move Back 6=Move Forward
7=Jump Back 8=Test 9=Jump Forward
0=Toggle
That should be perfectly fine as probably every remote had number keys and they're certainly all going to be grouped together. In my opinion those are the _only_ keys that make sense for editing. If it's really a problem for people to remember those 6 functions, you could always just display them on the osd with the press of the info button or whatever. The only key you really should make an effort to remember is 2 (cut). I've forgotten the others before but with a couple seconds of fiddling around with the other numbers, I quickly rediscovered what each did so it's never been any real issue here.
Hi Klaus, On Sa, Mai 09, 2009 at 10:04:59 +0200, Klaus Schmidinger wrote:
Personally I don't find the key mapping that unintuitive. After all,
FULLACK
the number keys are unused in replay mode, so why not use them for editing?
2=Cut 4=Move Back 6=Move Forward 7=Jump Back 8=Test 9=Jump Forward 0=Toggle
Klaus ((PLEASE)) not change this!!!!. It makes sense to use the numbers in replaymode. Building a custom remote control with more keys is not practicable. Thanks for your work. Regards Halim
On Fri, 8 May 2009, Pasi Juppo wrote:
It seriously would not hurt VDR if there were Help pages available via OSD. Yes, there are man-pages but my guess is that very very few end users will actually go to terminal to check man-pages if they have some problems with VDR how to do something. They just don't bother. And this is request for Klaus because he's the author of the VDR thus should keep the help pages of VDR up-to-date. And preferably all plugin developers would do the same.
Some plugins (all of mine for example) do have manual/help. You'll need just to press Info button to access them on plugin's active setup entry. This would be quite beneficial for core VDR too as many options are quite hard to understand at the first glance and a separate "Keymap" menu item would be a nice addition into the setup menu for averate users.
BR, -- rofa
Handling of the pause key is an intreresting issue.
There was proposal to configure the pause key as down key. This works during replay, but hitting the pause during live video changes channel.
Better solution would be to add setup option for pause key handling. I made a simple patch for this: http://www.tolleri.net/vdr/vdr/vdr-1.6.0-2-pause-0.0.1.patch
The patch adds pause key handling options to the recording setup: - do not pause live video - confirm pause live video - pause live video (default)
Please have a look if you need setup options for pause key handling. Patch is made for vanilla VDR 1.6.0-2. Plugins should be recompiled after implementing the patch.
Timo
2009/5/8 Pasi Juppo Pasi@juppo.fi
I'd also like to see option where live-tv pause can be enabled/disabled. It has seldom been a problem but the whole feature is not usable for our usage.
I like this solution
On 11/05/2009, Timo Eskola timo@tolleri.net wrote:
Handling of the pause key is an intreresting issue.
There was proposal to configure the pause key as down key. This works during replay, but hitting the pause during live video changes channel.
Better solution would be to add setup option for pause key handling. I made a simple patch for this: http://www.tolleri.net/vdr/vdr/vdr-1.6.0-2-pause-0.0.1.patch
The patch adds pause key handling options to the recording setup:
- do not pause live video
- confirm pause live video
- pause live video (default)
Please have a look if you need setup options for pause key handling. Patch is made for vanilla VDR 1.6.0-2. Plugins should be recompiled after implementing the patch.
Timo
2009/5/8 Pasi Juppo Pasi@juppo.fi
I'd also like to see option where live-tv pause can be enabled/disabled. It has seldom been a problem but the whole feature is not usable for our usage.
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
2009/5/12 Theunis Potgieter theunis.potgieter@gmail.com
I like this solution
On 11/05/2009, Timo Eskola timo@tolleri.net wrote:
Handling of the pause key is an intreresting issue.
There was proposal to configure the pause key as down key. This works
during
replay, but hitting the pause during live video changes channel.
Better solution would be to add setup option for pause key handling.
How about changing the delete functionality slightly? One could allow a recording to be tagged for deletion. An expunge would delete recordings that were marked. The recording resulting from a live tv pause would automatically be tagged for deletion.
A separate option would be to automatically expunge recordings at specific intervals, or at a certain age.
On Fri, May 08, 2009 at 08:30:24PM +0300, Pasi Juppo wrote:
I'd also like to see option where live-tv pause can be enabled/disabled.
I second this idea.
I have a large recorder host, and satellite hosts for watching live TV and recordings (via NFS), but I usually don't want to record anything at the satellites. I.e. I'd prefer to have the instant-record and pause-live-tv keys disabled there.
I could disable these remote control keys completety, but I do use the pause key while playing recordings, so this is not an option.
So, a "don't record at this host" configuration option would be nice.
Thank you.
Patrick Rother a écrit :
On Fri, May 08, 2009 at 08:30:24PM +0300, Pasi Juppo wrote:
I'd also like to see option where live-tv pause can be enabled/disabled.
I second this idea.
I have a large recorder host, and satellite hosts for watching live TV and recordings (via NFS), but I usually don't want to record anything at the satellites. I.e. I'd prefer to have the instant-record and pause-live-tv keys disabled there.
I could disable these remote control keys completety, but I do use the pause key while playing recordings, so this is not an option.
So, a "don't record at this host" configuration option would be nice.
I think the good solution for this situation would be to forward the recording request to the "large recorder host". This fits in the front-end/back-end or client/server need many users would like... This is a big issue, that have to be solved with a very good design.
On Wed, May 13, 2009 at 11:08:56AM +0200, Nicolas Huillard wrote:
Patrick Rother a écrit :
On Fri, May 08, 2009 at 08:30:24PM +0300, Pasi Juppo wrote:
I'd also like to see option where live-tv pause can be enabled/disabled.
I second this idea.
I have a large recorder host, and satellite hosts for watching live TV and recordings (via NFS), but I usually don't want to record anything at the satellites. I.e. I'd prefer to have the instant-record and pause-live-tv keys disabled there.
I could disable these remote control keys completety, but I do use the pause key while playing recordings, so this is not an option.
So, a "don't record at this host" configuration option would be nice.
I think the good solution for this situation would be to forward the recording request to the "large recorder host".
For real, I have a watchdog script does this, i.e. look for timers and remove them, but this is an ugly workaround.
As most pause key pressings are accidental, this is quite annoying.
I'd prefer to have a switch to disable recording at all.
On Sat, May 16, 2009 at 8:57 AM, Patrick Rother krd-vdr@gulu.net wrote:
As most pause key pressings are accidental, this is quite annoying.
That is user-error, not a problem with VDR.
I'd prefer to have a switch to disable recording at all.
Although you can easily resolve your problem by simply paying attention to what you're doing, I don't see a reason why Klaus wouldn't be willing to add something to help those of you who can't get it under control on your own. That's just my opinion though, nothing more. Maybe VDR should come with a helmet too! ;)
Regards, Derek
Seriously, there are many many things that are purely user error - so what! If the SW can eliminate few of those then wouldn't it be advantage of the SW?
If VDR can provide assistance to solve "user error" then why not implement it and make more users happy about VDR? Just because it is additional work it shall not be developed? Oh, please.. Especially when both parties will have exactly what they want - no change to existing functionality as a default config and for those (like myself) configuration to disable the live-TV pausing.
Instead of looking purely on software technical factors try to look things from the end user point of view - and I should add here: from multipe different skilled end users point of view.
And to put some sarcasm at the end then why don't Klaus remove remote control support from VDR. Who wants to use clumsy, usually not 100% working, with only few buttons and with batteries that drain out remote control when there are oh-so-nice keyboards and mouses available which provide every possibility there is to control VDR..
Br, Pasi
VDR User wrote:
On Sat, May 16, 2009 at 8:57 AM, Patrick Rother krd-vdr@gulu.net wrote:
As most pause key pressings are accidental, this is quite annoying.
That is user-error, not a problem with VDR.
I'd prefer to have a switch to disable recording at all.
Although you can easily resolve your problem by simply paying attention to what you're doing, I don't see a reason why Klaus wouldn't be willing to add something to help those of you who can't get it under control on your own. That's just my opinion though, nothing more. Maybe VDR should come with a helmet too! ;)
Regards, Derek
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
On 16.05.2009 22:30, Pasi Juppo wrote:
Seriously, there are many many things that are purely user error - so what! If the SW can eliminate few of those then wouldn't it be advantage of the SW?
If VDR can provide assistance to solve "user error" then why not implement it and make more users happy about VDR? Just because it is additional work it shall not be developed? Oh, please.. Especially when both parties will have exactly what they want - no change to existing functionality as a default config and for those (like myself) configuration to disable the live-TV pausing.
Instead of looking purely on software technical factors try to look things from the end user point of view - and I should add here: from multipe different skilled end users point of view.
And to put some sarcasm at the end then why don't Klaus remove remote control support from VDR. Who wants to use clumsy, usually not 100% working, with only few buttons and with batteries that drain out remote control when there are oh-so-nice keyboards and mouses available which provide every possibility there is to control VDR..
Guys, can you please just stop this bashing?!
Timo Eskola has suggested a patch that implements a setup option for this at http://www.tolleri.net/vdr/vdr/vdr-1.6.0-2-pause-0.0.1.patch, and I'm going to add this to version 1.7.8.
Klaus
Pasi Juppo a écrit :
And to put some sarcasm at the end then why don't Klaus remove remote control support from VDR. Who wants to use clumsy, usually not 100% working, with only few buttons and with batteries that drain out remote control when there are oh-so-nice keyboards and mouses available which provide every possibility there is to control VDR..
That's it : SSH + SVDRP only. With this, the remote control works from the other side of the continent.
;-)
-
dplu＠free.fr -
Halim Sahin -
Klaus Schmidinger -
Malcolm Caldwell -
martinez＠embl.de -
Nicolas Huillard -
Pasi Juppo -
Patrick Rother -
Rolf Ahrenberg -
Steffen Barszus -
Stuart Morris -
Theunis Potgieter -
Timo Eskola -
Torgeir Veimo -
Udo Richter -
VDR User