Rockbox

Using the %pL Tag (in WPS) in order to simply display it or use it in a conditional tag (like in the “analog” theme yields very high values (let call it spikes) - where they should not be, while the bar-type peak meter is working fine.

Within the simulator, everithing is running smooth, as far as I could see.

I tried to have a look at the sources but that’s too much at the moment.

Does somebody have a clue ?

Regards

  Ralf

Reported Version: 3.15 not 3.14

Hello,

I am using a "SanDisk Sansa Clip+" and it seems that currently it is not possible to remove quickscreen entries when they are set, you can only overwrite them.

In the manual chapter "3.15 Quick Screen" has to be adapted, once this function has been implemented.

It would be very nice to have this possibility!

-Ramon

Player: iPod Video 5th Gen. (5.5)
Rockbox Release v. 3.9 downloaded/installed 06/28/2011

Accessory: Griffin iFM Radio Receiver for iPhone and iPod - has a doc connector, short cable to a "dongle" which is the FM tuner, with earphone jack on the dongle. No batteries or other power source.

Here's a link to the product's Amazon page:
http://www.amazon.com/gp/product/B003ERT46W

Booting into Apple firmware
1. Turned player on with nothing plugged in, the "Radio" menu item does not show up. Plugged in the Griffin iFM, the "Radio" menu item shows up, and when I select it, I get the FM frequency and dial, I can tune it, it works. I did not have to download anything at all from the Apple iTunes store.

2. Turned player on with iFM plugged in - the "Radio" menu item shows up, and from there it all works as above.

Booting into Rockbox OS 1. Turned player on with nothing plugged in, then plugged the iFM on the dock connector, the "FM Radio" item never shows up.

2. Turned player on with iFM plugged in, still no "FM Radio" on the menu.

3. Went into System then Debug then FM Radio - got message: "HW Detected: no"

So Rockbox does not detect it at all. And there's no sense expecting that any Apple/iTunes software would do anything under Rockbox.

What's interesting is, that with the player off (under both Apple and Rockbox OS), if I only plug in the Griffin iFM to the dock connector, and do nothing else, the player turns on. So there must be some kind of hardware detection there.

Actual behavior:

1. FM Tuner option never shows up on main menu (whether powering up with FM Tuner plugged in, or plugging in after power up).

2. When player is OFF, connecting the FM Tuner to the dock port turns on the player.

3. In System/Debug/FM Tuner, "HW Detected" is always "no"

Expected behavior:
1. Expected the FM Tuner option to be available on the main menu (at least when booting with the accessory plugged in to the dock port) as described in the manual.

2. Expecting to be able to tune in to FM stations and play at least through the tuner's headphones connector, if not through the player's headphones connector. Other features (displaying song information, presets, etc.) are secondary (to me).

Players: Sansa Fuze v2
R29716-110415
Note: This was happening on a build from a couple months ago to..

When I have "load last bookmark" on I can't access any other files in a folder with a file with a bookmark. Even time I hit a file it'll always load the file with the latest bookmark, the only way to play another file is to use the forward/rewind buttons.

sometimes when i click on next(or previous) button a couple of times , rockbox gets stuck and then anfter 3 or 4 secs ,it restarts .then when loaded the battery is empty.
i am not sure if this is a rockbox related issue or hardware realated cause i use my ipod for file transfer mainly .and this issue existed from version 3.3 till now( i cont know or remember about before that).

is there a way that i can somehow debug (trace) this issue?

I’m using several SD-cards with my Sansa. When switching cards
and updating the database the db entries of other cards are lost
(unless saved to the database log).

In order to differentiate between files from different cards the
easiest way is to give them different path names. So instead of
mounting each card to <microSD1> this patch takes the volume label
i.e. ‘Classic1’ of the filesystem and mounts it to <Classic1>.

The database update is modified in a way that it erases only entries
for files with a filename of a mounted filesystem. So data of other
cards isn’t erased.

So far the database search isn’t modified to handle nonexisting files,
you still get albums etc. which are currently unavailable.
The patch only makes sure that nonexisting files aren’t entered into
the current playlist.

The patch is only activated for Sansa e200, as I couldn’t test it for
other players.

When adding text via the keyboard, neither the selection function nor the done function work using the remote play button. Pressing 'play' on the main unit however, does work and has the correct behaviour.

I checked the keymap-m3.c source and I noticed that unlike the other entires, the last entry for these options refers to the main unit buttons and not the remote:

{ ACTION_KBD_SELECT, BUTTON_RC_PLAY|BUTTON_REL, BUTTON_PLAY },
{ ACTION_KBD_DONE, BUTTON_RC_PLAY|BUTTON_REPEAT, BUTTON_PLAY },

I changed the entries to the following:

{ ACTION_KBD_SELECT, BUTTON_RC_PLAY|BUTTON_REL, BUTTON_RC_PLAY },
{ ACTION_KBD_DONE, BUTTON_RC_PLAY|BUTTON_REPEAT, BUTTON_RC_PLAY },

After rebuilding and installing this change onto my M3 the keybord now works when using the remote.

Attached is the patch file for this change.

On the default FM radio screen only the pre-set name line appears to scroll if wider than the screen. Other lines don't. This occurs on all releases tested up to current r29824-110504.

To reproduce, set to a large font and go to the FM Radio (I use 32 Terminus Bold - I want to read the screen when not wearing glasses, but it still occurs to a degree with fonts smaller than this).

Example display:
Station: 101.3 ("MHz" not visible - no scrolling)
Stereo
Mode: Scan
Signal Strength (": nn dBμV" not visible - no scrolling)

On my iPod Classic (160GB), the hold switch is not being detected anymore by Rockbox.
Switching the hold switch does cause the buttons to stop responding and vice versa, but Rockbox is unaware of this event and continues to act as if it didn't happen. My backlight won't turn off when I switch hold like it's supposed to, and I can't exit plugins that have a hold switch activated menu like RockBoy.

I am using build c3c2c91, I just updated today.
This bug has been present since as early as January, and I am aware that a task already exists for it, but it's buried deep because the poster marked it as Low severity.

ROLO currently fails on these targets unless a Rockbox image is being loaded that is sufficiently similar to the one already in memory.

The sequence goes like this:

- rolo_load() loads the new image to
rolo_restart() copies the new image to the start of DRAM (to achieve this without crashing, this function is in
rolo_restart() tries to call invalidate_idcache(), but since invalidate_idcache() is in DRAM this fails as the function has been overwritten.

There are several solutions to this:

1) Move invalidate_idcache() into .icode (easy but won’t fix all targets, esp. those that don’t use IRAM)

2) Create a new .safecode section at the end of DRAM, and move these functions into it (lots of work to update every app.lds and crt0.S, and test every target)

3) Introduce target-specific rolo_restart() functions, as per imx31/rolo_restart.S (less work, as only one should be required per architecture, eg ARMv4/5 etc.)

I’m not sure which of those options is “best”. 1) is certainly the easiest, but 2) and 3) should also allow ROLO to work on targets that don’t use IRAM.

The attached patch adds an indication of the current touchscreen mode to the "classic_statusbar" skin. This is useful since some screens automatically change mode, and there's currently no indication the user when this happens. The patch does the following:

- Adds a new WPS tag (%Tm) to return the current touch mode (Absolute|Grid)
- Updates classic_statusbar.sbs to conditionally show the correct icon

The reason I've made this a Flyspray task rather than just committing it is because the additions to classic_statusbar.sbs will also apply to non-touchscreen targets (though nothing will appear on screen). While the impact on these targets is minimal, I'm not sure about committing it since it will at least cause the new touchmode.bmp to be loaded unneccesarily.

Also, feel free to design some better icons!

This patch allows the line out on the Sansa Fuze V2 to be enable/disabled by means of the existing Lineout poweroff setting (previously used on some iPods).

By assigning this setting to the quickscreen I can switch between headphones and lineout after plugging into the dock. Still no luck in finding out how to autodetect the dock.

I'm not 100% sure that re-using the "Lineout Poweroff" setting is the right thing to do here as it's not powering on/off the line-out - just switching between headphones and line out

Following my patch to control line-out on the Fuze via a setting on the quickscreen (FS#12074), I found I kept forgetting to leave the quickscreen. This meant that when I intended to change track, I was actually changing the shuffle / repeat settings etc and had to fiddle around to get back to where I wanted to - not a good idea when driving at >70mph!

The attached patch adds a configurable timeout to the quickscreen so that it returns to the WPS screen if no button is touched within N seconds. 0 (the default) will disable the timeout preserving the existing behaviour.

I've found a problem with the new autoresume feature in 3.8. I use it when listening to podcasts and sometimes find that it resumes from near the end of a new episode - e.g. on a 30 minute podcast it will resume from 28 or 29 minutes - usually about the place where a previous epidsode finished and I skipped past the end credits.

What I think is happening is that there is some code in the database that tries to resurrect the runtime statistics for files that have been deleted and then restored - as the last offset is in this data, it is reusing the last offset from an old episode.

I've put some more logf()s in tagcache.c in build_numeric_indices(). I can see that if the filenames don't match (line 2306) it then tries to match any 2 tags out of the 3: artist, album or title. For the podcasts, the artist and album are always the same (i.e. the producer and which one of their podcasts it is), but the title is different (i.e. "Episode 100", "Episode 101", etc). So if I've listened to Episode 100 and then deleted the file, and then add Episode 102 to the player, it matches the artist and album and so resurrects the wrong data from Episode 100.

I've disabled the resurrection based on tags (just commented it out) and the problem seems to have gone away. A better fix would be to ensure that all 3 tags or matched or to ensure that title is one of the matched tags

Patch against r28560.

Adds options for displaying pitches according to key (for transposing instruments) and “mixed” accidentals a la Korg (C#, Eb, F#, G#, Bb).

I’d also like to add some kind of support for alternate temperaments (perhaps even just intonation), however this isn’t trivial and I probably won’t undertake the project unless some interest is expressed.

This is the first step of being able to use the pictureflow plugin from a database search. The database now indexes the path to the coverimage for each audio file. In the database browser you can select “Cover by...” genre, artist, composer, year or all and will be presented with a list of cover image paths. (Imagine a call to the pictureflow plugin at this stage, so instead of a list of boring paths you get nice and shiny images). After selecting a path it will display the list of files that would be queued when a cover image is picked in the plugin.

Next step is to work out how to safely call the plugin without losing the context and utilise the return value from it to queue the files.

Issues so far are:

- the preferred size of 100×100 is hardcoded (this should be configurable or at least be consistent with the value in the pictureflow
the db update for covers has the same restrictions as the other tags, i.e. it will only detect changed cover art on
the coverflow plugin needs to work while music is playing (or stop playback if needs
since there is no guaranteed relation between album name and image file, the album name can’t be displayed

Neither of the tools, ipodpatcher or Rockbox Utility 1.4.0, work on macOS Catalina.

Catalina removed 32bit support.

Using ipodpatcher generates the following error:

bash-3.2$ ./ipodpatcher
bash: ./ipodpatcher: Bad CPU type in executable

And Rockbox Utility has a white circle with a line through it indicating that it does not work with this version of the OS.

(see attached file)

Please refer to forum post for full exchange: http://forums.rockbox.org/index.php/topic,52518.0.html

In summary playing ALAC will crash the unit, other codecs not as much. My reasoning is (as contained in the forum post):

Converting some of my ALAC collection to FLAC to test has given excellent results = no crashes. I am suspicious of the ALAC decoder; watching the VIEW BUFFERING THREAD there seems to be consistency:

OGG/MP3/FLAC/WAV: CPU Frequency goes up to 124 until pcm: becomes full, then drops to 45mhz and pcm: hovers (it is always active) near the top of 100%. Upon track change the cycle starts again (124mhz until pcm: becomes full). I don't seem to get crashes.

ALAC: CPU Frequency goes up to 124 until pcm: becomes full, then drops to 45mhz and pcm: quickly goes down (takes about 2 seconds) to 75%, then cpu switches to 124mhz to get pcm: back up to 100%. This goes on constantly (cpu high - low cycle) while a single track/file is playing. I am now believing this cpu going up and down constantly gives me the crashes. Note on crashes: I don't know when they will happen, sometimes after a minute or two, sometime after 10 minutes , there is no pattern I can tell.

The following link to example.m4b file which I can’t open in latest rockbox build (4c4c645) on my sansa clip+ and sansa clip zip:
https://cloud.mail.ru/public/KeHt/tmu5sr9YR

I can open it on my computer without any issues.

Hi,

I think that the problem reported on  FS#10919  is still here, or at least not completely solved.
But now, I get the feeling that the pause only happens when the buffer refill is triggered via a track skip. During normal playback, it don't seem to happen any more.

The build I tried it on is r25249.

TIA

The patch fix the multiple-language feature, maintaining the same behaviour in interactive and batch mode and with “make reconf”. Now it’s possible to build more than one voice language at once, specifying different engine and option set for each one.
So, running “make voice”, all the selected languages will be built.

To help the comprehension, here it is a batch mode sample:

../tools/configure –target=ipodvideo –ram=64 –type=av –language=italiano,espanol –tts=f,e –voice=lp_diphone –ttsopts=, –encopts=’-q 10 -c 10,-q 5 -c 5’

This is like to run:

../tools/configure –target=ipodvideo –ram=64 –type=av –language=italiano –tts=f –voice=lp_diphone –ttsopts=’ ' –encopts=’-q 10 -c 10’

../tools/configure –target=ipodvideo –ram=64 –type=av –language=espanol –tts=e –voice=lp_diphone –ttsopts=’ ' –encopts=’-q 5 -c 5’

In the first case, I set the language to italian, using festival with voice lp_diphone (female), no further festival options and some manual encoder options.
In the second case, I set the language to spanish, using espeak. Even if I set the voice, the value is ignored, since the selected TTS engine doesn’t use it.

I also added some cosmetics, like some very circumstantial indentation, blank check in rootdir too, simpler numbered menu generation, some terser command pipes.

The patch is applied to r22250.

I don’t know if it’s a really wanted feature, but the word in the script hurt me!

In the "Scroll bar width" screen, the value used to show the width selected is the previous one, not the current one. The first value change has no effect.
Anyway it seems that the right value is stored: if you select a value and exit by the screen, when you re-enter in it, the width is correct.

Priority low.

Referred to r22406.

The patch allows to use the persistent dircache even in targets that do not define HAVE_EEPROM_SETTINGS.

Starting trying to implement such a feature for my iPod Video, I "discovered" the functions dircache_load/save (I have a slight knowledge of the RB software). Investigating why it was not used on my target, I saw that it's conditioned to the define HAVE_EEPROM_SETTINGS without an apparently reason to limit them just to some targets.
So, I simply "detach" the functions definition and use from the define.
I'm using it since an hour, starting up and shutting down the DAP various times, jumping back and forth inside the dynamic play list, and I got no problems at all.

If I guess correctly the code, the dircache should be updated also when changing the DAP content, if the USB connection is done by RB and not the OF.

It's applied to r29907.

I’m having weird problems with a 160Gb 6G Classic (yes I know it’s unsupported/unstable).

With emcore and rockbox it works fine. Connecting it to my computer the USB works as expected and everything is great (copied 100Gb+ of music to it with no trouble).

However… when I connect it to either of my cars (via USB), the iPod shows the USB screen for a few seconds then goes back to the Rockbox menu and locks solid. It then needs a MENU+Select to reboot it.

Using a USB flash drive in both cars (different head units) works fine and I can navigate around the filesystem and play music. I did notice that the flash drive was partitioned, not ‘superfloppy’, so I setup my iPod with 1 partition and stuck rockbox on that…. didn’t make any difference though.

Someone suggested that the head units (Kenwood and OEM Jaguar) might be detecting the device as an iPod from the USB ID and then ‘doing something special’. So I compiled my own rockbox from git source changing the USB ID and VENDOR to 0001. I then verified the change by doing a lsusb on my Linux box and the ID showed as 0001:0001.

Sadly this makes zero difference to the iPod’s behaviour when connected to my car(s).

Does anyone have any suggestions? I’m happy to recompile, grabs logs, insert code etc

Here’s the rockbox-info.txt from the one I built:

Target: ipod6g
Target id: 71
Target define: -DIPOD_6G
Memory: 64
CPU: arm
Manufacturer: s5l8702
Version: 189148eM-130128
Binary: rockbox.ipod
Binary size: 646268
Voice format: 400
Actual size: 646260
RAM usage: 1755172
Features: accessory_supply:backlight_brightness:crossfade:dircache:headphone_detection:hold_button:hotkey:lcd_bitmap:lcd_non-mono:lcd_color:lcd_sleep:morse_input:pitchscreen:quickscreen:rtc:swcodec:tagcache:tc_ramcache:charging:usb_charging_enable:wheel_acceleration:lineout_poweroff:large_plugin_buffer:albumart:disk_storage:scrollwheel:usb_power:usbstack:hardware_click
gcc: arm-elf-eabi-gcc (GCC) 4.4.4
ld: GNU ld (GNU Binutils) 2.20.1.20100303
Host gcc: gcc (Ubuntu 4.4.3-4ubuntu5.1) 4.4.3
Host system: Linux

H120 not starting original IRiver Firmware with LCD Remote holding Rec + Play Button both on LCD-Remote.

Hi.

I noted a strange bug on mpio hd300 player. 2/3 of the times ,when i lock the player with HOLD ON button, and return to HOLD OFF, the volume keys do not work anymore,however, the others keys works OK (menu, FF,REW,PLAY and REC). only after a reset, these keys (volume) works again.

The release of RB is 3.13

I try other releases, from 3.11 to 3.12, and the problem is the same.

thanks

I found  FS#8521 (permanent pitch setting) can successfully combined with mpeg player.
Add  FS#8521  and some fix, we can use pitch function in mpeg player. This means, we can control mpeg play speed.

With  FS#8894 (speed control without pitch change) can produce similar effect and more attractive, but  FS#8894  have serious problem with gigabeat s30 and require more processer power and have lower sound quality.

This patch can patched with  FS#8607 (mpegplayer playlist).

This patch adds a changable wheel scroll speed option on ipod video.

when the FM tuner is turned on and say that you want to go to Add a Preset you cannot hear thevoice over the radio. this should be controlled where the Fm volume is turned down and the volume of the voice is turned up just like in playing regular music.

Short Next + Long Next causes a hang about 50% of the time. This was reported before and still seems to happen on the Clip Zip.

This patch makes some changes to codec_api to help remove dependencies for my project.

The unused strcasestr callback is removed.

The global_settings pointer was being used by several codecs to check whether REPEAT_ONE mode is on; this has been replaced with a callback "should_loop()".

The MOD codec has been modified not to restart the file when it reaches the end. This does not affect MOD files that use "position jump" to loop part of the song. Ideally the MOD codec would only follow such loops if should_loop() returns 1, but detecting loops is nontrivial.

Continuing from  FS#12204 , these patches remove some of the dependencies librbcodec has on the rest of Rockbox.

0001: puts equalizer settings in the parameters of dsp_set_eq_coefs, removing the need to access global_settings from dsp.c

0002: makes dsp_process yield each iteration instead of once each tick, which is tricky to do portably. If this is undesirable, I can work around it.

0003: moves some replaygain stuff around so dsp.c doesn't have to access global_settings.

0004: instead of dsp.c and tdspeed.c allocating buffers, buffers are allocated elsewhere and passed to dsp_timestretch_enable(). The necessary buffer size is determined by calling dsp_timestretch_get_buffer_size().

0005: replace get_audio_base_data_type() with audio_format_is_atomic(), removing a dependency on TYPE_PACKET_*.

0006: move autoresumable() to playback.c, removing another dependency on global_settings.

Continuing from FS#12240, these patches remove most of the rest of the dependencies librbcodec has on the rest of Rockbox.

Amend the sleep timeout behaviour to pause when the timeout matures.

This allows the idle timeout to power off the player if it remains untouched, or the sleep / pause timeout to recycle if the user unpauses before idle timeout kicks in.

Adds “Binary Skip” to the skip length menu,

This allows navigation by means of binary search within a track.

If no search key is pressed for 5 seconds, the current binary search is considered as having “finished” and pressing a search key subsequently initiates a new binary search.

This patch adds an additional menu option to the list of WPS hotkey choices, “Announce Information”. This voices basic information about the player, currently playing file and current tracklist.

This feature reads a simple definition with a single line of no more than 20 characters from the file “announce.cfg” in the .rockbox directory.

This definition consists of a string of single character tokens, each of which announces a particular canned piece of information.

The tokens are:

A - current time
B - elapsed time and total length of the current track
C - current track number and total tracks in playlist
D - battery level as a percentage
E - battery remaining in hours and minutes
F - sleep timer remaining in minutes

If more than one token is specified, more than one piece of information is announced, so:

AB

would announce the time followed by elapsed time and track length

Multiple announcements may be bound to the hotkey by separating one or more groups of tokens with a “:”

A:DF

In this example, the first time the hotkey is pressed, the time is announced. If it is pressed again within 10 seconds, the battery level and sleep timer are announced and so on.

A space between tokens adds a short pause to the announcement.

If no announce.cfg file is present, the time is announced by default.

The following set of WPS tags demonstrates:

# WPS Document
%wd
%V(0,0,-,10,2)%Vb(000000)%Vf(FFF000)
%aL%cH:%cM %ac%pv %aR%bt
%V(0,11,-,30,2)%Vb(000000)%Vf(FFF000)
%it

If you alternately insert and remove a space between the second occurence of %Vb/%Vf, the track title text appears and disappears. It appears to happen in a few other variations, but this is the shortest concrete example.

I have a Sansa e260 player and currently Rockbox 3.11.2 running on it.
I got a shuffled playlist with all of my music in it (added to the playlist using the insert function and reshuffled afterwards). When I want to listen to one or more specific songs, I enqueue them with the queue function (in play mode select song, album etc. from database → context menu → Current playlist → Queue).
This works fine in most cases but when there had already been a queue that ended the song before, the song that I want to enqueue is placed before the currently playing song (which is the first song not any more part of the former queue) instead of after it.
If I use the feature "Queue next" the song, album or whatever is correctly placed after the currently playing song. After having used "Queue next" once, other songs enqueued with the "Queue" command may be also placed correctly at the end of the new queue. I believe to remember some strange behavior though when in that case the song was also incorrectly placed as described above.
I tried mp3 and ogg files and the behavior was the same regardless of which file format was used. It also doesn't matter if the song is played from the player's memory or from micro SD card.
As soon as the second song after the queue is playing, enqueued content is correctly placed after the currently playing song again.
I have experienced this behavior for a long time now and with different Rockbox builds on my player.

To reproduce the behavior:
1. Have a reshuffled playlist (created using "Insert" command, then selecting "Playlist" → "Reshuffle" from the wps context menu) with some songs in it
2. Listen to one of these songs which is not the first or last one in the playlist
3. Enqueue a song from your database via the context menu (This song should be placed directly after the currently playing one)
4. Play the enqueued song (or a part of it)
5. Play the next song in playlist
6. Now enqueue another song (This song should now be placed directly before the currently playing song in the playlist)

I have hardly any programming experience at all but it seems to me that somehow there exists some sort of marker that indicates the end of a queue and that this marker is not erased immediately after a queue ends but "one song too late"?

On the Official Test Build for the Sansa Fuze, when playing Doom, in middle of playing, Rockbox gives a Data Abort Error. If it doesn't happen in middle of playing, it is always reproducible by entering the second Map. The most recent error i got is "Data Abort at 307B32D4". My Version is "r21704-090707".

It happened once just browsing through the Menu, but is only reproduced every time by playing Doom, which is why I filed it under Doom.

I will try to try a later revision and see if it fixes the bug.

In the "Graphic Equalizer" menu and when I connect the player to a computer to transfer the data labels are displayed incorrectly (instead of letters symbols, as in the screenshot).
The problem occurs when I use the Russian language.
The problem I see for a long time, please fix it.

Screenshot of the screen that is displayed when transferring data, I could not do.
P.S. Sorry for my bad English.

I noticed, that every time I’m in the car listening to music, and I disconnect the iPod 30G (5th gen), while its playing, and I then try to shut it down, it’ll jump to the main window and will not move away from it.

From this point on, I cannot turn off the device nor more away from the main window. Only a HR will resolve this and let the iPod come back to normal working order.

Further more, while it is in that situation (which it is right now, while I write this), the device won’t even go on sleep or turn off the monitor. So basically, it’ll stay with the screen wide awake and lit up.

The two only buttons that will work are the Hold button, which will in turn, turn off the screen and the scroll will allow me to scroll up and down and around on the main window.

Q: What sort of car connection do you use? Line-out+power, or MSC? Or the accessory
I’m not familiar with these connection and their types. All I know is that it is connected to the car stereo from back (ie. the stereo was pull out and the adapter was connected in the back). Also, that it is a connection that connects to the bottom of the iPod (ie. flat and wide connection). It gives me control from the car’s stereo and the steering wheel. When I bought it and then they hooked it up, they told me this is an iPod adapter.

This DOES NOT happen if first stop the music and go to another menu BEFORE I disconnect it from the adapter.

rockout is a sampler that can play 6 samples at a time (unlimited playback length). sample playback is 16 bit 44.1khz. you can play samples back, you can glitch samples out using the glitch sequencer, there is echo, there is distortion, backwards, and a record loop function. you can load your own samples into rockout (stereo .WAV 16bit 44.1khz files)

rockout currently works on the sansa e200 series and c200 series. don't hold your breath for other players to work, due to their greatly lower amounts of RAM.

—

rar file only includes 1 very small/crappy sample pack. more (better) sample packs available at:

1) the motherload: 10 folders of samples, almost all hand selected/cut by myself:
http://www.megaupload.com/?d=BXMTW9T8

2) individual folders:

https://docs.google.com/leaf?id=0BwiF_VSZhsHjNjY1OWQzZTQtY2M2Zi00M2NhLWJlN2EtOTI0Nzk2MTJiYjI5&hl=en_US

https://docs.google.com/leaf?id=0BwiF_VSZhsHjYjQwMGFmOTMtMjM4YS00YTZjLWJkNzUtZTEzOGEzMTU0YzI0&hl=en_US

https://docs.google.com/leaf?id=0BwiF_VSZhsHjNjE0ZTc3YTUtYTNiZS00ZGJjLThmNTQtNmQ1MWU0NTk3YjRj&hl=en_US

https://docs.google.com/leaf?id=0BwiF_VSZhsHjNjM4NzMxYzQtZTVkZC00OGZhLThiZDUtMjYyZTgzNzFmZWQ2&hl=en_US

https://docs.google.com/leaf?id=0BwiF_VSZhsHjMjFiNDk2ODQtZmU2YS00Yzk0LTg3YTMtNDY1YWMzYjU4ZmM0&hl=en_US

https://docs.google.com/leaf?id=0BwiF_VSZhsHjN2MxZWE0NTAtMmJmMS00YmZjLWFjM2YtMjM1NzlhOWUyMmMz&hl=en_US

In FAT, file name can have max 255 characters (not bytes).
A file name that have 255 characters(contains many multibyte characters) is listed in File menu, but playback can’t.

Using patched firmware\include\file.h as a test, MAX_PATH 260 up to 520, rockbox can playback the long name file.
But, changing theme causes PANIC.

I like to keep the equalizer on with the precut set to -24db, as a volume limiter. I also like the fade on stop/pause set on. When I pause there is a noticeable ‘click’ sound after the music fades out. Also a click before fading in when I resume.

This was not always the case, but I am not sure how old the version I was using, that did not do this.

By the way, this also occurs on the Gigabeat S, as well as Gigabeat F. I don’t know about other models.

Let me know if you need more information.

Various users on IRC recently reported cases of filesystem corruption. I have seen them as well, especially when using USB mode (I'm using a Sansa ClipV2, USB-enabled through  FS#11664 ).

One strangeness I've experienced is that when my system has detected filesystem corruption, it is often enough to remove the player from USB and then replug it, without repairing the filesystem and without rebooting Rockbox; on the next USB mount, the filesystem is clean. This might indicate that some buffer is flushed too late for the USB host to see.

[EDIT: Removed previously attached patch, which is now tracked separately as FS#11883.]

The attached patch implements a clean disk unmount by way of the following changes:

Patch 1: Allow disk_unmount_all to close all files and flush dirty buffers when unmounting a filesystem. (Before, we've been calling disk_unmount, which does not flush buffers because it's written to handle user-ejected storage media that aren't accessible any more.)

Patch 2: Call disk_unmount_all in the power-down and reboot paths.

Patch 3: Fix write to detect a bad file handle.

(Split out from FS#11877, in which I first theorized that an unclean filesystem may be responsible for some filesystem corruption I'm seeing, but which turned out to be a deeper problem. Related to r28693 /  FS#11774 , in which we introduced disk unmounting before entering USB mode.)

[EDIT: Attached patch for experimenting with AS3543 settings.]

When playing back audio on a Sansa ClipV2 player, there is a regular background noise that’s audible with sensitive headphones and that’s quite annoying during quite music passages. The background noise is a hissing sound that repeats about 4 times per second. The noise can be heard when there is no disk activity and even at very low volume or when playback is muted. It stops as soon as audio is paused.

The noise is not present in the original firmware (OF).

This is a long-known issue, but hasn’t been formally tracked before. It is related to FS#11907, but different in that the background noise is present when there’s no disk (SD) activity. However, I did have the impression that disk activity intensifies the noise.

This item serves to collect the various approaches people have tried to eliminate the noise, and ideas for future exploration.

I ran a series of experiments on the assumption that the audio hardware is misconfigured is some way. I worked through various settings of the AS3543 component based on its datasheet. Here is what I have tried; but nothing helped to eliminate the noise:

* Higher-quality audio settings as proposed in  FS#11304  (AUDIOSET2_HPH_QUALITY_HIGH,
Disabled DAC gain control
Bypassed mixer and disabled mixer gain control (HPH_OUT_R_HP_OUT_DAC, AUDIOSET2_AGC_off,
Mute SDI data
Enable and control DAC attenuation
Disable common mode buffer (phantom ground)
Disabled various unused mixer components (AUDIOSET3_MICMIX_off, AUDIOSET3_ADCMIX_off,
Used external clock source for DAC
Enable headphone detection
Resetting all reserved audio registers to 0

[EDIT: I have attached a patch that allows experimenting with these settings by uncommenting the relevant source lines at compile time or extending the provided debug function to toggle the setting at run time.]

Possible next steps (suggested by various people on IRC):

* As the noise is not present on the other AMSv2 targets (Clip+, FuzeV2), a dump of the AS3543 settings (as3514_regs[] array) on these targets would be helpful. I have attached a patch that adds a debug-menu function for doing this (needs a logf build).

* Someone with a JTAG could read the AS3543 configuration set by the OF.

* The issue could be unrelated to the AS3543; it could be a power-management or frequency-scaling issue.

Also attached: A dump of as3514_regs[] (logf.txt; all values in
I’ve removed the patch to dump these settings; see a later comment in this task for a more up-to-date patch to do this.]

Other ideas?

I didn't like that the "Backlight on first keypress" function ignores the first keypress no matter which key was pressed. For example, I want the volume keys to work normally even when the backlight is off (that is, they should turn on the backlight *and* change the volume).

This patch restricts "Backlight on first keypress" to certain buttons only. in other words, these buttons work normally only when the backlight is on; otherwise, they just turn on the backlight. As a proof of concept, it changes the Clip and Clip+ behavior to filter out only the Home key when the backlight is off, allowing the other keys to function normally.

It works by allowing button-target.h to define the buttons that are filtered by the "Backlight on first keypress" function. If left undefined, the function filters all buttons when the backlight is off, as in the status quo.

[EDIT: Clarified that there is no overlap with  FS#9305  - Context sensitive backlight on key press]

Split out from  FS#11748 .

This patch adds an option to prevent rewinding to the beginning of a track to avoid losing the current playback and resume position by accidentally pressing the Left key. Instead, Left always directly skips back to the previous track. This behavior can be enabled for all tracks or only for those tracks that can be autoresumed on automatic track change (which already is separately configurable).

I'm dropping this patch here for now because I see little chance right now of this being accepted into the trunk. Some developers have complained about the considerable configuration complexity of autoresume as it is, and although this additional behavior can be convenient, there is no ultimate need for it because the resume position prior to the rewind to 0:00 is preserved as long as another skip occurs within the first 15 seconds of the rewound track's playback (for example, by pressing Left again to skip to the previous track).

This change was originally contributed by Dave Slusher in  FS#11748 . I just added the configuration logic.

Patch relative to r29484.

The attached proof-of-concept patch highlights (places the cursor at) each album's last-played track in database views. The intention is to allow easy resuming of multi-track audiobooks or podcasts where they were last left off. This works best when autoresume has also been enabled.

The patch relies on runtime statistics gathering being enabled (and the DB needs to be enables as well, of course).

The current patch has some caveats that I plan to address in future revisions:

Right now, it's unconditionally enabled for all database-based track views. We might consider allowing to turn this off for regular music albums.

When the last-played track has been completed (played through to its end), we should actually highlight the next track (or the first track if the last-played track was the final track of the album). [EDIT: fixed – see latest patch in comments section]

It would be great if a similar feature was available for the file browser. I'd find it acceptable if that would require the DB as well (as that's the place where the last-played info is stored). It could benefit from an add-to-DB-as-files-are-played feature (aka FS#12073).

Comments?

[EDIT: Clarified summary. Fixed a rather severe bug in the patch to make it actually work. :) ]
[ EDIT 2: Linked to FS#12073. Addressed one caveat. ]