Rockbox Development > New Ports

Rockbox Player - Project to design and build a Free/Open hardware audio player

<< < (50/144) > >>

AlexP:
Rockbox will resume the currently playing song after booting if so desired, and also supports bookmarks.  You can set it to resume automatically on startup, or go to the menu, or filebrowser, or database (plus more) and then resume manually if you like by pressing play. All of our current players shut down after a user specified time out (with the exception of the 1st and 2nd gen iPods that cannot shutdown).  Rockbox does not currently support a sleep mode like you are talking about.

casainho:

--- Quote from: BigBambi on February 06, 2008, 06:08:13 AM ---Rockbox will resume the currently playing song after booting if so desired, and also supports bookmarks.
--- End quote ---
I think RB write some file on FAT32 file system, for recording this information, for be able to resume.


--- Quote from: BigBambi on February 06, 2008, 06:08:13 AM ---Rockbox does not currently support a sleep mode like you are talking about.

--- End quote ---
Information I gathered on TWiki pages and source code:

Information about RB API for power modes, read here:
http://www.rockbox.org/twiki/bin/view/Main/DynamicCPUFrequency

Looks like the RB have 3 power modes of operation: Idle, Normal and Boost - example frequencies on PortalPlayer(ARM based), for each mode: 24MHz, 30MHz and 80MHz. Also PortalPlayer are dual ARM core but since I know, RB just uses one core(??).

More information about the driver for PortalPlayer, where we can see the function, static void pp_set_cpu_frequency(long frequency), to set this 3 different frequencies, here - file system-pp502x.c:
http://svn.rockbox.org/viewvc.cgi/trunk/firmware/target/arm/system-pp502x.c?revision=&view=markup

In the same file, we can find the function void system_reboot(void) - for reboot, as BigBambi mention, I think.


Interesting working on hardware level, we can now see that we can boost power save with a good hardware, planned design - the good points of doing our own hardware and have full information about it!! :)

spark:
mzandrew, why do we need 2 SD card slots in the protoB?
http://www.rockbox.org/twiki/bin/view/Main/RockboxPlayerPrototypeB

isn't 1 SD card slot sufficient? we can instead focus on making it as compact as possible.
Instead, 1 SD slot and 1 on-board NAND flash chip would be better option than 2 SD slots.
you can store the songs in as many cards as you want and keep them in your pocket.

Are you thinking of a card to card copy application for the player?

NAND is optional. but if we use NAND, we can do away with the SPI flash.
using NAND will also make Linux workable, thus increasing the usability of the hardware platform.

Alternatively we can have both SPI & NAND flash and 1 SD card. with this way you can ignore soldering of the NAND chip and use SPI. Those interested in NAND can solder it if they want.

casainho:
Since Matt is working in RockboxPlayerPrototypeB, and is choosing components that he wants, I would like to start discussion for functionalities of the RockboxPlayerV1.

After Matt end the RockboxPlayerPrototypeB on mid-March 2008, we can then start working on software for RockboxPlayerPrototypeB and working on hardware for RockboxPlayerV1. When finished the software on PrototypeB, we can them go to Olimex(or others) asking help for making the V1, showing PrototypeB working.

On TWiki page of the V1 - Features:

    * Outputs: Stereo Headphone
Since the objective is to make a good recorder/audio player, I would put 2 outputs for stereo headphones! There was an Iriver player that had this functionality. I could go on train with girlfriend or any friend and being listen, showing music to them :-) - The main objective of this player, IMO, is for music fans!! and that implies easy listen and share!! - what do guys think?

    * Inputs:
          * Stereo Line-In for High Quality recording.
          * Mono integrated Mic for voice recording.
Ok, High Quality recording is a must!! There are expensive players just for professionals recording!!!

    * Internal Storage: 512MB or 1GB
512MB or 1GB is not much memory, I would prefer just to have SD card for memory. 512MB or 1GB would be like a "dead memory" in the player If will not use it because of low amount of space. SD cards have 8GB now :) - and If I want even more than 8GB, I would go for the harddrive option :-)

    * Memory Expansion Slots: 1 SD card
:-)

    * Hard Disk Drive Connector: 1 ZIF connector for connecting an optional 1.8"/2.5" Hard Disk Drive.
Very good option!

    * Display: TFT/OLED display. Size: ? Resolution: ?
As an audio player / recorder centric, It does not need a big display! - I imagine just a large display for who wants to monitor what is recording, like showing sound waves or something like that.

    * Connectivity: USB (Mass storage device with multiple mediums)
I also would like to have some wireless to connect to another devices, mainly to share music! - PCs, PDAs, mobile phones, etc, have internet where we can get music like on www.Jamendo.com, after we could copy that music to the player by wireless. The player should not have internet connection, but could connect to some other device that do that.
Bluetooth looks interesting for me because a lot of devices have it!! although is slow but can be ok for sharing musics, also for wireless headphones!!

    * Power: Li-Ion Battery
The actual main technology :-) - I just don't like to not be able to swap batteries when in travel, as I do with NiMh. 

    * Charger: 5V DC adapter input or USB
Ok.

    * Navigation Controls: ???
Not any touch sensing! I know that actual tendency of this gadgets go to them, but we must do what we really need. As an audio player / recorder, I want to have it on my pocket and put play/pause, forward/backward, volume up/down, without looking at the screen or without looking at any touch pad! We must feels in fingers the keys. This will also be important for visual impaired people that uses RB :-)

I am think in putting on TWiki a list of desirable things, ideas and a list with choosed ones with justifications.

mzandrew:
From the wiki page,

--- Quote ---Rockbox will be stored in SPI flash and be copied to ram upon bootup.
   * Anyone with knowledge of the inner workings of Rockbox know if this is feasable?  We can always slightly modify rockbox so that it saves configuration changes (or possibly a database, but that should probably be stored on the SD card in question instead) to the serial flash after a config change.  The point is that there's no file system on the spi flash, so will Rockbox work?  We could have the Rockbox bootloader at the start of the serial flash and another binary chunk that's an image of a FAT filesystem that contains the rest of Rockbox (besides RoLo) and then just pretend that the block of RAM that's a copy of this image is equivalent to the mass storage device that the Rockbox files would normally be served from.  Easy / difficult to implement this way?
--- End quote ---

comments, anyone?  I need to have this one resolved before I can continue with the design as it is now.

Okay, so one potential problem with this is that my .rockbox dir for the uisimulator is about 35 megabytes, which is greater than the available ram on the player...

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version