home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
Products
IR Server Suite (IRSS)
Holding a button doesn't work good
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="GazpachoKing" data-source="post: 561355" data-attributes="member: 18374"><p>I was having this problem with my receiver (philips hts3450) as well. Through many attempts to properly learn the volume up and down codes, it seems the original remote alternates between 2 codes when you press a volume button repeatedly. I'm not exactly sure how a held button is transmitted. I played with the settings for a long time, but couldn't find any settings that worked reliably enough to stop using the original remote. My IR blaster cable broke a while ago, so I stopped worrying about it, but recently I got a couple new ones, so I suspect I'm going to be running in to this problem again. I'll post my results if I get anything working better this time. I'm also annoyed by the lack of discrete codes for this receiver, (at least I haven't found any,) and I've been thinking of upgrading my surround sound system anyway, so I might end up doing that sooner, so I can have complete control from my computer.</p><p></p><p>EDIT: After reading an article on how remote codes work, I recognized what was happening and found an OK solution to my problem. Each press on the remote also sends out a parity bit, which alternates on successive presses. What I did was learn all my codes from even presses on the remote, and learn 1 code (that doesn't actually do anything) with an odd press. Then I run a macro with the button press I want, followed by a blank press. This keeps the parity alternating and the reciever responding as it should. Now I seem to be running into a different problem, when translator is set to blast an IR command for any given button press, IR server no longer reliably receives that button press. I have verified this in the debug client. When I press vol+ on my mce remote, and no actions are mapped to it in translator, all presses show up as expected in debug client. But when vol+ is set to blast to my HTS, I get unreliable results, i.e. First vol+ press, nothing happens, 2nd press, 2 vol+ blasts sent to my HTS. This also happens on mixed buttons i.e. vol+ pressed, nothing blasted, vol- pressed, vol+ then vol- sent to HTS. Is there somewhere I can get the source in order to debug this problem?</p><p>EDIT: I alleviated the above problem by having translator run a program (irblast.exe) instead of sending the signals itself, now there are no more repeats and stuck buttons.</p></blockquote><p></p>
[QUOTE="GazpachoKing, post: 561355, member: 18374"] I was having this problem with my receiver (philips hts3450) as well. Through many attempts to properly learn the volume up and down codes, it seems the original remote alternates between 2 codes when you press a volume button repeatedly. I'm not exactly sure how a held button is transmitted. I played with the settings for a long time, but couldn't find any settings that worked reliably enough to stop using the original remote. My IR blaster cable broke a while ago, so I stopped worrying about it, but recently I got a couple new ones, so I suspect I'm going to be running in to this problem again. I'll post my results if I get anything working better this time. I'm also annoyed by the lack of discrete codes for this receiver, (at least I haven't found any,) and I've been thinking of upgrading my surround sound system anyway, so I might end up doing that sooner, so I can have complete control from my computer. EDIT: After reading an article on how remote codes work, I recognized what was happening and found an OK solution to my problem. Each press on the remote also sends out a parity bit, which alternates on successive presses. What I did was learn all my codes from even presses on the remote, and learn 1 code (that doesn't actually do anything) with an odd press. Then I run a macro with the button press I want, followed by a blank press. This keeps the parity alternating and the reciever responding as it should. Now I seem to be running into a different problem, when translator is set to blast an IR command for any given button press, IR server no longer reliably receives that button press. I have verified this in the debug client. When I press vol+ on my mce remote, and no actions are mapped to it in translator, all presses show up as expected in debug client. But when vol+ is set to blast to my HTS, I get unreliable results, i.e. First vol+ press, nothing happens, 2nd press, 2 vol+ blasts sent to my HTS. This also happens on mixed buttons i.e. vol+ pressed, nothing blasted, vol- pressed, vol+ then vol- sent to HTS. Is there somewhere I can get the source in order to debug this problem? EDIT: I alleviated the above problem by having translator run a program (irblast.exe) instead of sending the signals itself, now there are no more repeats and stuck buttons. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Products
IR Server Suite (IRSS)
Holding a button doesn't work good
Contact us
RSS
Top
Bottom
