We already have predefined actions for each target for plugins... Have
a look at lib/plugin_action.c (or whatever its called). I think
metronome and bubbles use this.
Maybe there could also be some extra work to do - something like
7084 |= 1 - to get better audio results. I have played a lot with
volume settings and i dont get it better as it is yet.
2007/5/16, Michael Sevakis <[EMAIL PROTECTED]>:
This brings up some important questions to answer: What a
This brings up some important questions to answer: What audio
processing/switching hardware exists outside the codec chip (besides this)?
Is it an established fact that the OF eq is software? Signal processing
could easily be slipped in on the I2S bus between the CPU and AS3514.
I noticed also loc
... comment AudioHardwareAPIProposal
http://www.rockbox.org/twiki/bin/view/Main/AudioHardwareAPIProposal
Thanks,
Christian
Great news folks. Very loud audio!
The secret was the stuff involving address 0x7084 and 0x7080!
Now to work on the algorithms for tuning and getting volume control to
work with the line1 in (very loud even if gain is very low)
Btw, the settings below actually mute line1 in while tuning,
My deepest apologies for the triple posting, Yahoo said the message could not be
sent due to a network problem twice so I posted through Gmane. Right after I
posted they all appeared in the mailing list :(
I looked at several plugins and they use different mappings for the same action
sometimes. I was hoping this post in the mailing list would be a first step to
standardize that somehow.
Perhaps defining several generic COMMAND_* constants in plugin.h associated to
target specific button mappings fo
If you can hear any sound, then I would assume, that the device is working.
So nothing more to be done with the radio init/powerup.
I bet, that the audio configuration is not correct yet.
In the emu I found following AS3514 init sequence after entering the radio
menu
and after setting up the tun
I looked at several plugins and the use different mappings for the same actions
sometimes. I was hoping this post in the mailing list would be a first step
towards standardizing that.
Perhaps adding generic COMMAND_* constants in plugin.h associated to target
specific button mappings would be t
I looked at several plugins and the use different mappings for the same actions
sometimes. I was hoping this post in the mailing list would be a first step
towards standardizing that.
Perhaps adding generic COMMAND_* constants in plugin.h associated to target
specific button mappings would be t
I'm quite fond of the button choices in Jewels personally.
I would suggest seeing other plugins for the menu mappings. Targets are
increasing and it is quite hard to remember all of the keymaps. e.g the Jpeg
plugin should give you an idea what button you should use to bring a menu on
each target.
On 16/05/07, Mauricio Peccorini <[EMAIL PROTECTED]> wrote:
Hi All,
I'm adding a menu system to chessbox so you can configure some options, set
the engine level, start/resume/save/restore/games, etc. Since the plugin didn't
have a menu before, I don't know what button mappings to use in the different
targets. For iPod SELECT + MENU makes sense (since
On 16 May 2007, Menachem Shapiro verbalised:
> In an effort to get it down to the minimum needed to get it to work, I
> tried this:
> SUBSYSTEMS=="scsi",
> RUN+="home/mshapiro/rockbox_scripts/rockbox_downloader.sh"
You really want it to run for *all* your SCSI devices?
> (I also tried this, in
The radio commands are well figured out. I have set the audio to
maximum output for the FM chip and maximum gain for the AS3514, but it
is still barely audible. I am almost certain that something is blocking
the audio output from the FM chip. Maybe the init is done right when
the firmware st
15 matches
Mail list logo
