- A perfectly flat frequency response sounds awful. So if we actually can get to a fully automatic version, then we'd need to build in an optional "smiley" curve to it. Perhaps have more than one selectable smiley to cater to various tastes.

What about re-defining flat to include the newly calibrated offsets? Then when you pick your EQ settings, you're adding to the auto-calibrated settings. Of course, I don't know how you'd do this... maybe by hacking the voladj code? Maybe it's too much work and isn't really worth it.

What about re-defining flat to include the newly calibrated offsets?

That's more complicated than it sounds. Each band has certain characteristics that aren't linear, and you can't just apply an additional correction to them without changing their characteristics. Take a look at this to give you an idea of how the various parameters interact.

I just wanted to give this great thread a bump... any updates?

I'm still working on it, although my code immersion time this week has been limited. Efforts to completely eliminate clicks resulted in significantly messier code than I liked, so I decided to undertake a major restructuring, and implemented a state machine to track the generator state and prevent clicks. The good news is that it is pretty much click proof now. The bad news is that I broke the hijack interface in doing so, and need to clean that up.

When you do, I think this project might deserve it's own thread. I'm VERY excited about this.

Yeah, what he said.

This is a great tool dude. can't wait for the next version

I had really hoped to get the next version out by today, but it wasn't to be.
The DSP's tone generator doesn't appear to work *quite* as advertised, leading to much frustration on my part. Basically the idea of flip-flopping between the 2 tone generators to be able to play multiple tones without completely stopping it each time seems to have a flaw - the part of the DSP that is supposed to allow me to mute one of the generators doesn't appear to actually work for one of them (one mutes, one won't).
Aargh.
This could have been useful - it would have allowed doubling the attack/decay time without any penalty. It would have also allowed an easy way of interuppting a long sine with the next sine as soon as we have taken a measurement, something that would have made the auto stuff quicker.
So I'll probably revert a lot of my recent changes in favour of the old scheme of doing things, ie, one at a time. (After one more sanity check of my code).
But it will have to wait a while. I'm getting on a plane to Singapore in a few hours. I might be able to get online to check the BBS, but I won't be taking the empeg, so no coding. I'll be back a week Friday.

And I'd just like to add that Tokyo airport is very civilised.

Internet access @ $6/hour.
Smoking room.
Smoking area in restaurant.
Very clean and airy.

Now why can't US airports be the same?
Oh well, just one more flight to go...another 7 hours.

Wow! Cool to see so much progress being made. Any updates?

Bump from the dead!

hijack400-sinewave.zImage

Testing wanted. Should be speaker safe. I'd like to get this submitted to Mark ASAP before his tree grows out of sync, so the more people that hit this, the better.

genixia,

I just installed the hijack401-sinewave.zImage version from your site. It seems to work fine, except that I can't get the indefinite duration tones to work. I have this in /empeg/var/config.ini:

[hijack]
sine_volume=50
sine_duration=11889


Now how about programmable sweeps? Actually, it looks like there's an ioctl interface in your patch -- do you have any sort of sample app? I don't have a toolchain installed right now, unfortunately.

In any event, thanks for this tool. I am gutting a pair of Bose enclosures that came out of my car doors and installing new drivers, and your patch has already helped me decide to plug up the resonator ports when I install the new drivers.

Sorry for the delay in response...I'm not at home at the moment so I haven't been online this past week.

The continuous sines may be currently disabled. IIRC, I did that when I was having issues with getting both tone generators to play nicely together. I'll look at getting that back in next week when I get home.

Yes, there are ioctls for this, and I do have some simple test programs. When I get home I'll clean them up, comment them and release them.

Oh, can you do me a favour? Are you running a stock 16MB player without any memory upgrades?

If so, it would be really useful if you could look for the following line in a serial boot log;

"Memory: 15016k/16M available (980k code, 20k reserved, 364k data, 4k init)"

and report what the actual numbers are. Ta.

Sure:

Memory: 15000k/16M available (992k code, 20k reserved, 368k data, 4k init)


I actually posted the whole boot log (using your kernel) in another thread -- it's here if there's anything else useful in there.