Someone mentioned on the weekend seeing differing behaviour between playlists that had more than just the title field populated, and ones that didn't.

Hmm well I do populate many of my playlists with other stuff incl. Year and Artist. I don't see any reason why that should cause problems...

Well I just tried it out and I have some playlists that do have other stuff in them and they play fine. So I don't *think* that's it.

Sorry I wasn't clear. The playlists that had the problem (in the other person's post) were ones that DIDN'T have any other fields populated.

Bruno

How to setup Home/Work network swtiching:

1. Read this so you are all setup to edit your config.ini, and make sure you have the newest Hijack installed.

2. Open up emplode, connect, and then Under the "Tools" menu, select "Edit Config.ini", and click "Yes"

3. Find the [Network] section in your config file. You should have something like the following if you've setup a static IP in the past:

[Network]
Gateway=192.168.1.1
Netmask=255.255.255.0
IPAddress=192.168.1.20
DHCP=0

4. DHCP=1 means DHCP is on, DHCP=0 means it's off. duh.

5. add the following just above DHCP=x

;@HOME DHCP=0
;@WORK DHCP=1

or visa-versa if you have DHCP at home and static at work.

My final Network section reads as follows:

[Network]
Gateway=192.168.1.1
Netmask=255.255.255.0
IPAddress=192.168.1.20
;@HOME DHCP=0
;@WORK DHCP=1
DHCP=1

6. Hit Okay, then Sync

7. Hold down the volume knob, go to the "Home/Work Location" selection in the menu, set it, and reboot.

TADA! It works!

Hijack v181 is now available.

The only change from v180 is preliminary support for intercepting/emulating the Tuner/Stalk serial port.

By default, nothing strange should happen with v181.
But if you enable "[hijack] trace_tuner=1" in config.ini,
Hijack will dump out incoming packets from the Tuner/Stalk
serial interface (/dev/ttyS0). Eventually, I'll add button
emulation for these codes, enabling the [ir_translate]
facility to operate on them.

What, no tuner you say? No problem. Here's a way for the
curious to see what the Tuner Display would look like on
your RioCar/Empeg, as if you had a Tuner module installed:

[hijack]

fake_tuner=1

Why bother, you ask? Well.. the Sony Stalk control, which
normally plugs into the Tuner module, has at least one command
not normally available without one: "Visuals-". If we can
fake a tuner, then we can issue that command from [ir_translate]
after first assigning it to another button.. someday soon.

Cheers

-ml

But we're going to make sure to ask the empeg guys to add a new (I suppose unused) code for "visual-" right? For those without a Sony stalk, it makes a lot more sense.

I won't be surprised if one day you put your own player into the kernel.

Bruno

Do the @AC and @DC directives work on the actual [hijack] section of the config.ini? I tried to enter

[hijack]
;AC fake_tuner=1

to fake the tuner in the house, but not mess things up when I'm in the car, where I actually have a tuner. However, Hijack behaved as if the line just wasn't there.

-Aaron

They work anywhere in the config.ini file, but they do have to be spelled correctly (with the @ symbol).

[hijack] 

;@AC fake_tuner=1

-ml

Also note that I believe Hijack will behave correctly with "fake_tuner=1" even if a real tuner is installed: it will silently reset "fake_tuner=0" and continue. Or at least it does it for me.

Yeah, note the time on my post. A long sleepless night makes brain not work so good.


-Aaron

>I won't be surprised if one day you put your own player into the kernel

Good, I wouldn't want to cause a stroke or anything when it happens..

Okay, Hijack v182 is out.

This version just has some internal cleanups, but also:

"Home/Work Location" menu only appears if actually used in config.ini

new config.ini option to prevent Emplode/Emptool/etc.. from connecting to the player:

   [hijack]

   ;@WORK disable_emplode=1

Note that if you fsck up and leave out the ";@WORK" prefix, then you'll have to either FTP or revert to an older kernel to fix config.ini afterwards..

Cheers

-ml

You're a jerk, you know I do have work to do and someone might notice that I'm contiually playing with my new toy and all the awesome new features you're throwing into Hijack...



oh yeah, and thanks for writing an awesome kernel

Hijack v183 is out, to fix a BUG in v182 whereby the "Home/Work Location" menu item did not always show up when required..

Also new, the "NextSrc" virtual button code is now smoother in operation than before, unless you happen to have disabled the Kenwood remote in config.ini..

Cheers

-ml

Been too busy for the last few months to pay much attention to my empeg (other than listening to it) and so have only just started catching up on the changes to Hijack... (Had my parents visiting for a couple of months over Xmas and have been looking for and buying a new house)

With your new work on intercepting the tuner and faking the tuner... can you detect the existence of a real tuner before the player software starts...? I am currently detecting it from a user space program and then calling an ioctl to change flags in the kernel but it would be great to be able to detect it earlier from within the kernel before init is called.

Would it be possible to move the code I am currently using into the kernel to try and talk to the tuner to test whether it is there...?

Cheers

Kim

Do you really need to know BEFORE the player starts up?
If so, I can just have Hijack do the same detection sequence that the player uses, just earlier on. But if you can wait until after the player is running, I'll just pick it off from there. Either way, I can make it available in /proc

-ml

Do you really need to know BEFORE the player starts up?

Yep... as I check for the presence of a tuner to determine whether the empeg is in the car or running from mains power (my empeg's power socket is faulty and believes it is always on mains power)

I need to detect this before the player starts so I can override the power setting and make the player believe it is in the car and not blast my ears out with the wrong volume setting.

A useful extension might be to pull out the tuner ID and allow ;@ID1, ;@ID2 conditionals in your config.ini processing so those with multiple tuners/locations could run different things depending on where the empeg finds itself.

As for it being needed in /proc, the ID could be useful... but I would probably just use the value within the kernel to override the power state...

What would be excellent for me would be:

[hijack]
;@ID1 force_dc=1

Or something like that... Hope that makes sense..

Maybe at some point I will get the courage up to take to the empeg with a soldering iron and won't have this issue any more...

Cheers,

Kim