Re: [vdr] perfect vdr remote?
On Wed, 27 Jul 2011 09:16:17 +1000, Torgeir Veimo wrote On 27 July 2011 01:49, VDR User user@gmail.com wrote: On Tue, Jul 26, 2011 at 7:39 AM, Torgeir Veimo torg...@netenviron.com wrote: The Philips Prestigo SRT9320 seem to have a perfect key layout for VDR. Does anyone have any experience with this remote with VDR? Yes, that's the one I use on my primary VDR at the moment. I'm very happy with it and my wife is also glad that she doesn't have to deal with a remote with tons of buttons she'd actually never use. I do agree that direct buttons are better for the most commonly used buttons, but I mostly use the menu/back, arrow keys/ok and the coloured buttons, almot none others. One the remote you liked to, the coloured buttons are far away from the arrow buttons, so it can't really be nice to handle? That's the point. You really don't need too many buttons for your daily work with VDR and on the SRT9320 all these buttons are close together. Maybe even more important: You can easily distinguish these buttons due to their different shape and position. No need to switch on the backlight in the dark, no need to look at the remote at all. That's also why I'd never go for a touchscreen-only remote. What else can I say? The remote is not too large and not too heavy as it includes a cell phone battery. Only need to recharge it every 3 months or so. Still the SRT9320 is not perfect. Decide yourself if one of these things matter to you: * not programmable via PC, only via touchscreen. But usability is ok. Just rearranging the buttons is a bit of a hassle. * no way to enter custom remote codes. Codes which are not in the builtin database can only be learned from an other remote. I had to ask someone with a Logitech Harmony to get the discrete codes for the HDMI inputs of my Samsung TV (even the original remote of the TV doesn't have these codes. The AV button there opens a menu where you can select the input with up/down). * devices with just a toggle power remote command are difficult to handle. Note that some devices (like my Samsung TV) do have discrete codes for power on and power off, but the original remote doesn't feature them. The SRT9320 internal database did already know about the discrete on/off codes for my TV. * don't expect software updates from Philips. They once published an updated firmware, but when I tried to update my remote the server was unreachable. Philips support told me, the update server will be made available again when a new update becomes available... * activity concept instead of plain makro support. It's not possible to assign makros to keys. All you get is switch on and switch off makros. The concept is unusual, but in the meantime I'd even say its superior when compared to simple makros. Let me explain: The main touchscreen menu gives you two modes: Either select an individual device (something I almost never use) or an activity. When you select an activity, its switch on makro is executed. Power on the required devices, switch AV inputs, do whatever you like in this makro. You can even enter delays or configure how long an individual code has to be sent (some devices need a long key press to power it on). Each activity is associated with its own key and touchscreen layout. This is nice for multi-purpose devices as you could even define different activities for the same device, but with different sets of keys depending on what you are about to do. Just select all the keys you need from the set of devices involved in this activity. Hit the power key twice to execute the switch off makro (poweroff devices, do whatever else needs to be done). Hit the power key once and the touchscreen will give you a list of all your devices with the possiblity to switch on the devices which are involved in this activity and switch off the devices which are not involved (in case some device didn't catch the power on/off command). Changing from one activity to an other will send the switch off makro of the current and the switch on makro of the next activity. This is where you'll run into trouble with devices which support only toggle power as they will be switched off and on again. Fortunately I don't have such a device any more, but I guess you could work around it by either using different activities or by not sending the power command in the switch on/off makros. Instead power on/off manually (hit power key once and select device from list). Regards, Frank ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr-plugin-restfulapi 0.1.0
Hi everybody, today I've got the pleasure to announce my first plugin for VDR: It's a community project of the yaVDR-Team who've welcomed me in their team some time ago. But now to the important stuff: RESTFULAPI - 0.1.0 What does the plugin offer? * A modern alternative to SVDRP. * Full UTF8-Support. * MultiUser-Support * Different-Output-Formats: Json, Xml and Html * Epgsearch integration * OSD-Support * Epg-Pictures and Channel-Logo Support * and much more... Are there any Issues? * No, every known bug has been fixed before this release. But the plugin is huge and we haven't been able to test every tiny detail. * But there is one more thing: The HTML-OSD is ugly, if you have an idea for a better Theme, let us know and I will add it to the plugin. (You only have to create a new osd.css file to change the theme.) What should I do if I find bugs? * Collect all information about the plugin you can find: less /var/log/syslog | grep restfulapi Your Request And if possible a stracktrace * Create a bug-report on yaVDR-Redmine: https://bugs.yavdr.com/projects/vdr-restfulapi Where do I find the API documentation? * Download the plugin and open the API.html. It also contains a lot of examples. Where can I download the plugin? https://github.com/yavdr/vdr-plugin-restfulapi What do I need to compile the plugin? * cxxtools rev 1231 or newer (Important!! I has to be really at least rev 1231, older revisions don't work.) * VDR 1.7.18, older versions are not supported nice regards Michael ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] perfect vdr remote?
Am 26.07.2011 17:49, schrieb VDR User: Those kind of remotes are cool but I wouldn't want one for daily use. I prefer direct access to many options with one button press, not going through menus on a remote screen. From my experience, the keys I _really_ use, are: (1) Core keys: 0-9, Up/Dn/Left/Right, Menu/Ok/Exit, Color keys, Power, Vol+/- (2) Keys I often use: Timers, Recordings, EPG (3) Nice to have, but not essential: Info, Play/Pause/Stop/Rec/Ffwd/Fbwd (4) Rarely used: Mute, Ch+/-, Audio tracks, Subtitle tracks, Channel list I can use (1) and (2) and some of (3) completely blind. Having them on some kind of touch screen is not an option. And for the record, I'm using two remotes: - MD41169: Cheap but acceptable universal remote. Easy to replace if worn out. - Harmony 300: Very flexible, good price, no gimmicks, though only programmable via web site. Cheers, Udo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-plugin-restfulapi 0.1.0
API looks good. Giving it a try out now. FYI default port is 8002 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] HDHomerun and streamdev
I had the same problem until I downgraded to streamdev 0.5.0 and hdhomerun_atsc_firmware_20100828.bin. I am not sure both of these changes are necessary as I changed both at the same time. :( http://download.silicondust.com/hdhomerun/hdhomerun_atsc_firmware_20100828.bin On Jul 16, 2011 6:00 AM, vdr-requ...@linuxtv.org wrote: ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] perfect vdr remote?
On Wed, Jul 27, 2011 at 12:36 PM, Udo Richter udo_rich...@gmx.de wrote: Those kind of remotes are cool but I wouldn't want one for daily use. I prefer direct access to many options with one button press, not going through menus on a remote screen. From my experience, the keys I _really_ use, are: (1) Core keys: 0-9, Up/Dn/Left/Right, Menu/Ok/Exit, Color keys, Power, Vol+/- (2) Keys I often use: Timers, Recordings, EPG (3) Nice to have, but not essential: Info, Play/Pause/Stop/Rec/Ffwd/Fbwd (4) Rarely used: Mute, Ch+/-, Audio tracks, Subtitle tracks, Channel list I can use (1) and (2) and some of (3) completely blind. Having them on some kind of touch screen is not an option. I/we pretty much use the following daily: 0-9, up/down/left/right, ok/enter/exit, epg, recordings, timers, color keys, subtitle, play/pause/stop/ffw/rew, record, skip +/-... I also like to have a few keys available for macros. I haven't found any remote that I felt was perfect. I'd love to design one with my own specific button layout but the cost to make a custom remote exceeds my willingness to pay for it so I've got a few that are good enough. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
