Hijack v320, available at quality websites near you (soon).

And quality, it is! Working perfectly for me now, in both home and car modes.

Mark, you are THE MAN. Thanks!

time I actually put away my paid work for half an hour

Paid? I thought Linux was free?

Holy crap!
less than 12 hours from suggestion to implementation!

Anyone who suggests that Mark is not THE MAN will be beaten up and have thier empeg removed.

I just tried out 320 and its a really cool feature, thanks for the hard work. The amount of user development for the empeg still amazes me.

Holy crap!
less than 12 hours from suggestion to implementation!

For Mark, that's actually a long time. Heck, even I went from suggestion to implementation in 3 hours tonight with a brand new program. When you catch a hacker at the right time with the right suggestion, it's almost impossible to stop.

Mark et al,

Thanks for the incredibly quick response to my request. I have only just looked at the BB again since my enquiry and there are 33 replies (34 now !) and several up-issues of Hijack to implement a solution.

If only everything in life was as reliable as the Empeg BB !

Geoff

When you catch a hacker at the right time with the right suggestion, it's almost impossible to stop.

I want to know which brands of coffee/pizza/coke you guys are on. I could use some.

I want to know which brands of coffee/pizza/coke you guys are on. I could use some.

I dunno, you did the volboost stuff, right? That was a winner. As for what I'm on, nothing really, it's just that the alternative to playing around with lrctool was to do my school work, and, well, I'm sure you know who wins that battle.

As for how Mark gets his Linux stuff done while assembling tuners, building docking stations, and implementing complex features in Hijack... AND still manages to stay very involved on the BBS... I'm just guessing he fell from another planet. Let's hope he sticks around for awhile longer before returning home!

But when rock-climbing season returns.. THEN I'm outa here!

Thank god you don't snowboard, with that and climbing you'd never be concentrating on work

Hugo

Hey, stop giving him ideas.

Oh yeah?

Thank god you don't snowboard, with that and climbing you'd never be concentrating on work

Although he might be able to get back quicker!

DAMN! Remind me to go snowboarding with you next time. Wow.

Wow !! just caught up on the BBS, reading through this thread, can't believe the capabilities of Mark.

An idea turned into reality just like that !!!
Awesome dude !

Another assurance that i bought the right MP3 player !!
(nothing else compares)

I've just loaded V320 of Hijack to take advantage of the new boot volume facility. This works great but since I've loaded it I'm getting some odd behaviour - whenever I re-start in car mode, Info reverts to Line rather than the last setting and some of my ir-translates for the Sony stalk seem to have reverted to an earlier version of my config.ini. Emplode shows config.ini as I expect and I've re-synchronised but that has not helped. It's as if it has got a back-issue of my config.ini (that it won't let me see) and is using that instead

Is this possible?
Am I going mad?

Am I going mad?

I dunno. How many legs does this elephant have?

What elephant? All I see is is an Empeg Tuner circuit diagram.

Idea for the "Previous" settings:

From my last car stereo I know the following possibility, which is quite simple but very powerful:

- store the previous volume level for each individual operation mode (player, tuner, aux) and even for traffic alarms separately

- restore to the previous volume level when switching to the operating mode, e.g. to previous level of tuner when switching to tuner or to previous level of traffic alarm when an alarms comes in (even if you are already in radio mode)

Could such a feature be part of hijack ?

Juergen

Except for the TA part, this is already implemented in hijack.

Check out the volboost_ settings in the FAQ

O.K., but I don not mean a pre-defined volume-level, which is stored in the config-file. The idea is to store the volume level, which is actually set during operation.

So if you adjust the volume during a traffic alert the same volume level will be used next time during a TA.

Juergen

The only truly feasible method for doing this in Hijack would be for Hijack to completely take over the volume controls. Completely -- not even passing the volume buttons (remote) or knob volume changes through to the player software.

It could then accurately track and maintain separate volume settings for each mixer input (AM/FM/MP3/AUX), and switch between them whenever it notices the player software selecting a different mixer input.

But where to store these?

The player software uses 7-bits each for AC/DC "master volume" memory. For Hijack to also provide AC/DC, it would need as much as four times that amount, or 56 bits in total. It can re-use the existing 7+7 bits, so we'd just need to "appropriate" an additional 42 bits (5+ bytes) of the flash savearea.

There's not much space left there to grab, and this would be a HUGE use of it, displacing other potential uses/features.

Is it worth it?

I still can't see any benefits for fossi's idea - the volboost_ parameters are relative to the current volume which makes sense to me from the user perspective. The whole motivation for the volboost_ code is to eliminate users' needs to adjust the volume when switching between MP3,FM,AM and Aux modes, and storing absolute values for each would simpy reintroduce that in many cases. People listen to their empegs at different volumes depending upon differing circumstances - time of day, speed, mood, number of passengers etc, and absolute volumes would soon become a maintenance chore.

Yeah, it would be nice to have the volboost_ parameters in flash rather than in config.ini. But that goes for a lot of other parameters too. I don't think that tweaking the volboost_ parameters should be too difficult or time consuming, although being tunerless myself, I'll defer to someone that has actually done it to confirm or deny that statement. Once it has been done well, it's not something that is likely to change often. In principle, knowing that each volboost_ step is 0.5dB for most of the usable volume range of the empeg means that you could sit in your car for five minutes, note down the adjustments that you make to the volume for each mode, and use those figures as a start point.

I'm not sure whether hijack has any obvious visibility into TA mode switches anyway. But if it does then I'd suggest that a volboost_ parameter could be added for TA mode. (And also for WB mode when the player supports it)

And I can't see any other reason to hijack the volume control completely away from the player either.

People listen to their empegs at different volumes depending upon differing circumstances - time of day, speed, mood, number of passengers etc, and absolute volumes would soon become a maintenance chore.

Not to mention, a source of heart attacks.

O.K. if memory is rare there should not be a waste of resources and for switching between MP3/AM/AUX/... predefined values are also useable.

But for the traffic alert part it would be very helpful to have a adjustable volume level, not a prestored adjustment. With this feature you could e.g. lower volume when driving with guests but still hear traffic alerts. A prestored absolut value could also be feasible but with one disadvantage: when driving in town volume level for TA will be equal as when driving on an Autobahn.

Juergen

VolBoost works very well for me (thanks, Genixia).

It took me a long time to set up, though - a day or so for each adjustment (assuming I remember to edit config.ini every time I came to work). Even if I did it as fast as possible, it's still a 5-minute round-trip to the car; add on the time to get in and boot up, and it's still quite slow.

One thing that would help would be to be able to adjust and see the volboost settings interactively, even though they won't be saved on power-down (so you can later type the right numbers into config.ini). And maybe a lock-down setting in the config file (default locked) to remove the menu item; then you'd have to understand its transience when you enable it...

It's too late to be of use to me, of course (unless I get something to plug into Aux), but I thought I'd suggest it.