ATI Remote Wonder - STOP or Not?

[mightyt]

I am watching a recorded show ... and as usual I use the << button to Rewind, the >> button to Skip, the || button to Pause and the > button to Play. All is well ... except,

Here's the question ... When I hit the "Stop" button just below the Play button I expect to actually "Stop / Close" the recorded show I am watching. Instead it moves me to the Main Menu and continues to play the show in the upper right hand corner.

I have attached a JPG of the remote I am using which includes my plug-in button layout.

For now I have to press the "Options" button, then scroll down to "Stop / Close" and then press Enter. IMHO, too many steps to just stop playing ….

Any thoughts on why this is setup this way?

Thanks!, T.

[kny3twalker]

oh sorry make sure your ATI plug in is the newest version since stop was nto always close file

[mightyt]

Originally posted by kny3twalker
oh sorry make sure your ATI plug in is the newest version since stop was nto always close file

No problem ... Thanks for the quick reply ... I am using;

ATI Remote Wonder V1.4 (ATI Software)

ATI MMC - TV Button Launchs Sage (by hocky@x-epg.net)

ATI Remote Wonder Plugin for SageTV v 2.0.x (by Nielm)

Are these not current?

Thanks, T.

[kny3twalker]

only the newest version from neilm has the close file as stop sorry to repeat myself

I believe it use to be time scroll


by chance have you changed any of the commands/links in SageTV?

and have you tried to use stop in the original STV?

but thats all I can think though

hopefully someone else can figure it out though

[mightyt]

Originally posted by kny3twalker
only the newest version from neilm has the close file as stop sorry to repeat myself

I believe it use to be time scroll

by chance have you changed any of the commands/links in SageTV?

and have you tried to use stop in the original STV?

but that’s all I can think though

hopefully someone else can figure it out though

Do you know where I can get the most current version of nielm's software can be had??

I believe I used this one ...

http://forums.freytechnologies.com/f...0&pagenumber=2

FYI, I did not change any Sage commands and I don't remember if it worked with the original STV, I was using th Hauppauge remote then. I've been using the RW with MlbDude2 and frankly just never noticed. I am just starting to get acclimated to the RW and use its functions instead of scrolling through Sage menus.

So, when I one day hit the stop button and it didn't quit playing I was surprised and posted my question..

Thanks, T.

[Opus4]

Try using it with the original STV -- perhaps it _is_ sending the stop command & that has been changed in the custom STV?

- Andy

[ErsatzTom]

Not sure if this is the same as what you downloaded but you might want to check:

http://www.sage-community.org/~nielm...v/install.html

t

[mightyt]

Originally posted by ErsatzTom
Not sure if this is the same as what you downloaded but you might want to check:

http://www.sage-community.org/~nielm...v/install.html

t

Thanks, t ... Actually I did download nielm's STV and am currently testing / tweaking it.

However, what we are talking about here is the ATI Remote Wonder SageTV Plug in .... Nielm built that as well ...

T.

[ErsatzTom]

Oops! Skimming too fast. Sorry!

t

[mightyt]

Originally posted by ErsatzTom
Oops! Skimming too fast. Sorry!

t

Don't sweat it ... Us T's gotta stick together

Welll rememebr I am big T ... you are little t ...

Thanks ....

[ErsatzTom]

LOL. I had a book when I was a child that had a rhyme for every letter of the alphabet. For T it was:

Big T, little t
what begins with T?
Ten tiny turtles
in a tuttle tuttle tree
(or something like that... I'm working from memory).

I didn't know that there were referring to people in the
first stanza!

t

[mightyt]

Oh yea ... the only thing bigger than a big T is a MightyT ...

Sorry ... I can't seem to contain myself today ...

Stay DRY and hang on to a big "T"ree ... (noticed your location!!)

T.

[ErsatzTom]

Actually, I'm currently in NY but, stupidly, I'm driving back to FL starting tomorrow morning. I've got a reservation in GA incase my part of FL is evacuated and I have to wait for the storm to blow over. *blarg*

t

[kny3twalker]

mightyT

you ever try getting it to work/fixed

[mightyt]

Originally posted by kny3twalker
mightyT

you ever try getting it to work/fixed

No sir ... best suggestions I got were revert back to OTB Sage and see it it works again or us the newest plug-in. Unless I am wrong, I think I already am using the latest release of the ATI RW Plug-in from Nielm. I have not reverted back yet since this is my production server and the fam can only take so much down time. Hmmm, sound like work!! Guess I have to work off hours through the weekend ...

But, anyway, no ... Stop is still not stopping ...

Thanks, T.

[mightyt]

Originally posted by ErsatzTom
Actually, I'm currently in NY but, stupidly, I'm driving back to FL starting tomorrow morning. I've got a reservation in GA incase my part of FL is evacuated and I have to wait for the storm to blow over. *blarg*

t

Ah! That's my old stomping grounds! Until I left for sunny CA ...

I don't miss the blizzards. Who-da-thunk NY would be a refuge from FL's inclement weather!!! Fa-get-abot-it !!!

Hang tight ... Hope all is well ...

T.

[nielm]

Originally posted by mightyt
No sir ... best suggestions I got were revert back to OTB Sage and see it it works again or us the newest plug-in. Unless I am wrong, I think I already am using the latest release of the ATI RW Plug-in from Nielm. I have not reverted back yet since this is my production server and the fam can only take so much down time. Hmmm, sound like work!! Guess I have to work off hours through the weekend ...

But, anyway, no ... Stop is still not stopping ...

Thanks, T.

If you want to check the version number go into the ATI app, and configure the plugin -- I think it shows the version number there somewhere... The latest version is 2.0.0.2

That same screen (I belive) also shows what commands numbers each button sends -- you may have an old ini file that had the STOP button send the Home command...

Check your ini file that in the [SageTVKeys] section you have Stop=1258,1,89

[mightyt]

Originally posted by nielm
If you want to check the version number go into the ATI app, and configure the plugin -- I think it shows the version number there somewhere... The latest version is 2.0.0.2

That same screen (I believe) also shows what commands numbers each button sends -- you may have an old ini file that had the STOP button send the Home command...

Check your ini file that in the [SageTVKeys] section you have Stop=1258,1,89

Thanks Niel ... Well, my Server version of the ATI Plugin is 2.0.0.1

Interesting thing is that my Sage Client, also with 2.0.0.1, had a SageTV.ini file and it had the following section;

;; Stop == go to home screen
Stop=1258,1,89

This makes me think "Stop=1258,1,89" is the setting for going Home. I could not find another code for "Close" or "Stop"? I did find one for "Power Off" but expect that that will just Close Sage altogether.

Now, my Sage Server didn't have the ini file at all in the C:\Program Files\ATI Multimedia\RemCtrl\Plug-Ins folder like the client did. However, all of my custom button settings (A-F) created through the plugin work fine on the server.

So, should I copy the ini file from my Client to Server?? If so, would it mess up my A-F settings?

Or, if I should upgrade to 2.0.0.2, where can I get it??

Thanks, T.

[Opus4]

Just so you know: 89 is the event # for Stop; 28 is for Home.

See: Controlling SageTV Using Windows Messages.

- Andy

[mightyt]

Originally posted by Opus4
Just so you know: 89 is the event # for Stop; 28 is for Home.

See: Controlling SageTV Using Windows Messages.

- Andy

Thanks Andy ...

So it appears ini file that is on my Client (where I tested the ATI RW before moving it to the server to replace the Hauppauge remote) was not moved over. But it looks like I changed the setting to 89. So, should I copy the client ini file to the server and restart the ATI RW software? Guess I should just try it rather than ask ...

T.