Okay, I've just put up v64 of hijack at http://rtr.ca/empeg/.

UPDATE: now v65

Please Note: this version uses a slightly different syntax in config.ini for IR translations, so If you've already defined some, you'll need to perform some fix-ups for them to work again.

Old syntax:  ;xxxxxxxx:yyyyyyyy

New syntax:  xxxxxxxx=yyyyyyyy



Old syntax:  ;xxxxxxxx=yyyyyyyy:zzzzzzzz

New syntax:  xxxxxxxx=yyyyyyyy,zzzzzzzz

Got it?

There's now also support for a new '[hijack]' parameter section in config.ini. Currently, only the following options are implemented:

[hijack]

temperature_correction=+4    ;default value shown (thermometer correction, degrees C)

volad_low=0x1800,100,0x1000,25,60   ;default value shown

voladj_medium=0x2000,409,0x1000,27,70  ;default value shown

voladj_high=0x2000,3000,0xc00,30,80  ;default value_shown

The voladj parms are those passed to hijack_voladj_intinit(): factor_per_second, minvol, headroom, real_silence, and fake_silence (respectively).

Have Fun!

-ml

Wow!

Hey, could you also document the voladj parameters at the web site, too?

Question: Why do your parameters for config.ini have semicolons in front of them? In the "ini" notation I'm accustomed to, those are comments and are ignored by the interpreter.

>Hey, could you also document the voladj parameters at the web site, too?

Done (you were too fast for me!).

>Why do your parameters for config.ini have semicolons in front of them?

Because Emplode used to mangle any lines that it doesn't recognize, except for those with semi-colons at the front. So I used semi-colons.

But now that I'm also using the '=' syntax, Emplode seems to be happier about it, so you should do your lines without semicolons now. I'll update the webpage.

Also, I forgot to say, the ";debug" option is no longer allowed (it is now the default behaviour).

-ml

Okay, v65 will be up shortly.

The difference between v64 and v65 is that now anything after the first ';' on lines in config.ini gets ignored. So, with the new IR / options syntax, do NOT prefix lines with semi-colons anymore! (blame Tony ).

Now that the config.ini stuff got redone in hijack v64/v65, it is much easier to add new parameters for just about anything, with one-line additions to a parameters table inside hijack.c. So if you've got something you'd like to be able the change the default value of, and if it's likely to be of interest to somebody else as well, then let me know (or hack it yourself).

-ml

So how many commands can we add on? are we limited to three?

>So how many commands can we add on? are we limited to three?

Err.. I haven't actually put anything into config.ini to add new commands to the menu, although userspace can still do that (up to 16 new menu options, roughly).

But as for tuneable parameters in config.ini, I don't see any real limit as to how many can be added to the table in hijack.c.

Basic syntax is: keyword=value1[,value2 ..]

Anything that can fit that syntax (values are signed integers, decimal or hex) is very easy to add right now.

Cheers

I wasn't thinking when I wrote that.

What I meant to ask was how many IR commands are we limited to on each line?

Limits are for physicists.

The single->multiple IR translations don't have any programmed limit, so I guess you'll only be cut off by available memory (not likely).

So if you want to string 100 button presses together in response to a single button on some remote, then go for it.

Things like:
XXX=menuok,next,next,menuok,prev,menuok ;selects "transient" info

(replace words with actual IR hex codes).