Hijack v245: Sony Stalk Support!

Okay, at long last..

Announcing.. Hijack v245, with Sony Stalk Support!

Well, actually, the stalk works with any version of Hijack, but as of v245 it is now fully supported for [ir_translate]. Details are on the Hijack site.

Also new in v245: the tone control init sequence has been adjusted, to hopefully allow it to work correctly in DC mode. bugs >genixia

Enjoy, keep track of the bugs, but don't bug me for the next week. Waaayyyyy too busy with important ($$) stuff for the next five days.

Cheers

-ml

HeHe, I've got a whole week to implement the volume boost stuff without the baseline shifting.

thanks for the stalk support mark.

see you in a week or so..........

Is there a chance (perhaps in future) to connect the stalk without the tuner module (serial port) ???

Does this mean I can make my remote control do the previous visual command yet?

I think mlord mentioned in a previous thread eventually implementing serial support.

The stalk is (amazingly) an analog device, not digital. So, I cannot see it plugging into the serial port without some custom A/D conversion hardware.

But perhaps the microphone port..

Yes, in theory. The default mapping for "Visual-" is "KSPrev", so if you map a Rio button (or popup) to "KSPrev", it should work.

-ml

Ooops. I got that backwards. KSPrev == Visuals+, so what you want here is "KSNext" which does Visuals- .

If you don't have a Tuner, you'll need to use fake_tuner=1 as well.

This gives:

[ir_translate]

;; make the '6' button act as "Visual-":

Six.L=Six.L,null

Six=Six.U,KSNext.N



[Hijack]

fake_tuner=1

I'll add a "Visual-" name alias to Hijack v246.

-ml

Oh.. and "Visual-" doesn't actually work when the Tuner is active, it's treated as "Seek Down" by the player software in that mode. So I guess the translation might become this:

[ir_translate]

Six.L=Six.L,null

Six.T=Six

Six=Six.U,KSNext.N

-ml

Doh, putting that in my config.ini and hitting 6 causes the player to completely lock and I have to power cycle. I put it in PopUp0 as well with the same results. I was using 246, so I tried visual- too with no difference. I tried it at home, would that make a difference since I added the fake_tuner line as well? I did force it to DC mode once as well to try that too.

Well, I've never tried it (yet) without a real tuner attached. But fake_tuner=1 should work. If not, it'll get fixed someday.

Cheers

detail also needs to be remapped.. it currently acts as info.. detail.L shows details.. at least thats my experience with it in popup0 menu..

Okay. That's it.

I'm removing all of the "convenience labels" for buttons from Hijack. From now on, only "Info" will work, not "Details". Same thing for "Zero" vs. "Shuffle", and "Cancel" vs. "Mark", and "Seven" vs. "Repeat", and "Eight" vs. "Swap" etc..

Too many people assume too much about the current convenience labels. So out they go!

Cheers

Nooooo!!! And i JUST did up that nice table too.
Well, not that it matters much... but i'd REALLY like them to stay Mark. I use them all over the place. Just because a couple of people don't get it, don't remove them for the rest of us who do! I'll edit the FAQ to be clear about having to add .L to the convenience buttons.

Personally, for the sake of consistency, I'd like to to see them go. That is of course unless they change to really mean what they say. Like, for example, details is the same as info.L

So.. is anyone with a Stalk actually using this feature yet?

Cheers

Mark, the only ones that are misleading are the ones where you have to modify with a long press (detail for instance). So most of the ones you mentioned are fine as convenience labels. They just work. It also makes it more intuitive to read the translation section of a config file. The remote itself is inconsistent as to whether a subscripted label applies to a long press or not.

Hmmm... Didn't your IR translate page used to mention that PopUps didn't support the .L modifier? I'm next to positive I had read that. Seems to be working fine. So I figure it's either something you've changed or something that's worked forever.

Bruno

Mmmm.. I know that I meant to say that popups don't support macros. But from looking at the code, they definitely DO support .L for longpresses.

Mm...

Mark, could you explain the following?

;; Min/max A/D pairs for all ten buttons on a Right mounted Stalk
;; Button order is: KOff,KSource,KAtt,KFront,KNext,KPrev,KVolUp,KVolDown,KRear,KBottom
stalk_rhs=aa,aa,bb,bb,cc,cc,dd,dd,ee,ee,ff,ff,gg,gg,hh,hh,ii,ii,jj,jj

;; min/max A/D pairs for all ten buttons on a Left mounted Stalk
stalk_lhs=aa,aa,bb,bb,cc,cc,dd,dd,ee,ee,ff,ff,gg,gg,hh,hh,ii,ii,jj,jj

i wanna add it to the FAQ, but i don't get it... at all....

In reply to:

---

Mark, could you explain the following?

;; Min/max A/D pairs for all ten buttons on a Right mounted Stalk
;; Button order is: KOff,KSource,KAtt,KFront,KNext,KPrev,KVolUp,KVolDown,KRear,KBottom

;; min/max A/D pairs for all ten buttons on a Left mounted Stalk
stalk_lhs=aa,aa,bb,bb,cc,cc,dd,dd,ee,ee,ff,ff,gg,gg,hh,hh,ii,ii,jj,jj

---

Each of those labelled buttons (KOff,KSource,...) on the Stalk are implemented in hardware with a simple resistor and a switch. The stalk interface consists of three wires: Power supply out, and two returns: one return from the "Shift" switch, and another from all of the buttons wired together. What the software sees, is an A/D conversion value based on the size of resistor attached to the button that is being pressed. This gives a number in the range 00..255. Different resistors give different numbers. Even the same resistors can give different numbers, depending upon component variations, and environmental conditions (temperature), quality of the electrical connections, etc..

There is a default "range" of acceptable A/D values from each button, wired into the player software, and also now in Hijack (the same for both).

The stalk_lhs and stalk_rhs parameters in config.ini allow the advanced user to override the built-in A/D values with a custom set of ranges, two numbers (low,high) per button. This allows compensating for an out-of-spec Stalk, or even use of a third-party (or hacked together) stalk-style control that plugs into the same hardware interface.

The reason for separate stalk_lhs (Left Hand Side) and stalk_rhs (Right Hand Side) values is just a coding convenience within Hijack.

Here is the default (built-in) setting for stalk_rhs:

stalk_rhs=0x00,0x07,0x10,0x1c,0x24,0x30,0x34,0x40,0x42,0x4e,0x54,0x60,0x68,0x74,0x7e,0x8a,0x94,0xa0,0xa0,0xb5

Note that the final two buttons listed overlap -- which is an error, but that's what the documentation on RioCar.Org claims for the player software, so the bug is faithfully duplicated in Hijack.

Cheers

okay... thanks. I've got all that. Now if i just new what A/D meant.... =]

I'd guess Analog/Digital..

What values should I put in for buttons that don't exist on my stalk? 0xff,0xff?

Yeah, 0xff or I suppose even 0x00 would be the best.

Cheers