Hijack, knob press, details

I might have missed this somewhere, but is there a reason that selecting "details" for knob press redefinition doesn't seem to work anymore? Is it just me? I press the knob and it doesn't do anything, though selecting any of the other choices for redefinition seems to work.

It doesn't work for me with 136 or 137...not sure where along the line it stopped working for me.

Ahh.. yup, broken.

Fixed in v139 (out shortly).

-ml

I think i'll just use my handy-dandy EtherFlash program to update to v129 when it comes out. hehehe. It actually works pretty nice for a VB prgram and updates WAY faster then doing it through serial, just need it to display on the empeg and make it reboot. Check it out http://www.empeg.tk
; D

-Greg

Okay, v139 was a dud (broke lots of stuff).

v140 is out, and it all seems to work for me.

Bedtime.

Okay, v139 was a dud (broke lots of stuff).

Mark,

Not to cast aspersions on your amazing skills or anything (we think you're the best thing to come to Empeg development since, well, since the Empeg), but have you considered marking certain Hijack releases as "known good"?

I'm not talking about an official alpha/beta/final system of releases if you're not interested in that kind of overhead. I'm just thinking of maybe occasionally (perhaps even several days or weeks after the fact when it's been tested and you're sure it's good), updating a link to the "last known good stable" version of Hijack for download.

That way people could choose between experimental new features and stability.

Thanks for the suggestion, Tony.

But this would defeat the development methodology being used. The chief way I find out whether things are broken or not is for people to use it and report back rapidly. This saves me time testing stuff I rarely use, and gets the latest goodies into eager hot little hands very quickly. And since I never knowingly release a buggy version..

If I start adding "verified" and "not verified" labels, things won't get tested as rapidly, which will make them harder to fix afterwards (since the code base evolves rather rapidly, 'case ya didn't notice).

The whole process works because it is a good collaboration involving me, you, the other Tony, number9, and a ton of other eager owners.

A crude way of checking for "stability" already exists: if one doesn't want to contribute to the process, then just don't download the "latest" version unless the time/date stamp is more than 3 days old. By that time, all noticeable bugs are usually crushed, and a new release issued.

Cheers

My only problem is that I'm always a release behind as you put out new versions left and right. That's a good thing, mind you.. I know for myself, I would never use a 'stable' version, as they usually are even older versions and don't have the latest and greatest features.. Not that I use some of the features anyway (like the IR-mapping stuff), but it's nice to be current..

Speaking of the "IR translation" stuff -- something I never used either -- tfabris just suggested a wonderful hack, which I now DO use the IR translation for. This is probably of general interest:

[ir_translate]

; Longpress of SEARCH invokes Search-by-artist:

20df0e.LN=20df0e,20df0e,20df0e,ffffff

cheers

wow, I like it.