Loading Radio module

Posted by: bbowman

Loading Radio module - 08/01/2004 14:53

I've noticed while watching the empeg boot, one of the last messages says that it's loading the radio module. Since I do not have a tuner, can I eliminate that to gain (perhaps a second or so) on the boot up time? Is there a modules.autoload file or something that I could tweak?
Posted by: mlord

Re: Loading Radio module - 08/01/2004 16:18

Actually, you may be able to slightly speed up the boot time by telling Hijack to pretend that you DO have a tuner. Hijack responds instantly to the tuner commands, so any timeouts/waits that that player may do are reduced to the bare minimum. May not make more than a few milliseconds of difference, but you can time it yourself.

in the config.ini file:

[hijack]
fake_tuner=1


Cheers
Posted by: tfabris

Re: Loading Radio module - 08/01/2004 16:20

I was gonna suggest that, but could have sworn you said that you'd taken out fake-tuner support in Hijack.
Posted by: mlord

Re: Loading Radio module - 08/01/2004 16:24

fake_tuner got put back in v332. It is also currently needed for the PrevVisual function in the v3alpha series (for VisualSeek: allows forward/backward tabbing through the player's visuals)
Posted by: bbowman

Re: Loading Radio module - 09/01/2004 07:44

Thanks for the quick reply. I did that and, not surprisingly, haven't noticed much difference. It does still mention it (radio) in the boot up messages - but I surmise that we'd have to go a little deeper to get rid of that.

Posted by: tfabris

Re: Loading Radio module - 09/01/2004 12:12

It does still mention it (radio) in the boot up messages
Yes, it's always going to do that. That part is in the closed-source player software, not in open-source kernel. So that can't be changed.

What Mark's fix has done for you is to reduce the amount of time it takes to detect the radio down to its absolute minimum. Most likely, it can't get any faster than it currently is.

Remember, just because it says "loading radio module" on the screen for 1 second, doesn't mean that's the only thing it's doing for that whole second. Maybe it's only loading the radio module for the first 2 milliseconds after it prints that message, and then it's doing other stuff after that which doesn't generate an on-screen message.