Rockbox

Hi there,

  this is another WIP plugin that I wrote last year.  It plays videogame streamed music
  using the vgmstream library. Original homepage here:
  sourceforge.net/projects/vgmstream/

  I'm a bit new to git so please forgive me for not uploading a proper patch.

  To test the plugin, simply copy the rockstream folder to the plugins folder in
  rockbox sources.  And you have to extract the data.zip file in the .rockbox folder.

  The formats.db found in data.zip is basically a list with all vgmstream supported
  extensions (at least "all" by the time I wrote the plugin).  You can add  or remove 
  new or unwanted extensions there.  The plugin will only handle the extensions found
  in the formats.db.

  Currently the plugin works as a viewer plugin, and there is only one extension associated
  with the plugin in viewers.config for testing purposes, but you can always use the 
  'open with' option from rockbox.  Once you open a file the plugin will parse all supported
  files found in the same folder.

  The vgmstream project is updated quite often, if someone wants to
  update the core library, I believe that would be very easy, since I only changed a couple
  of things to it.

  I'm not going to work on this anymore, so I decided to upload it here, and hope someone
  can make a proper patch and maybe some dev would be interested in testing it, make 
  the necessary changes and upload an stable release.

  As a last comment, I have only tested the plugin in the simulator, samsungypr0, fuze+
  and ipod nano. It only worked in the simulator and samsungypr0, so hope someone can 
  fix that.

  Please read the README file for some additional info about the plugin.

  Working on:  simulator and samsungypr0
  Commid ID: e1ea08417bca57c607df6686472fa0a86f38b6d1

This bug is sporatic “the worst kind”, has effected a 4gb fuze+ “foolsh in IRC” and an 8gb fuze+ “DmL in IRC“, but also has been confirmed to be absent from one other 4gb fuze+

Rockboy data aborts on menu key press, when the srceen is rotated left and image is stretched across the whole srceen. Also no matter what key is mapped to the menu entry it will still fail.

It never fails when aspect ratio is maintained with scale or when not scaled at all, and never aborts when rotated right or not at all.

Only four files even mention rotate in the apps/plugins/rockboy/ directory “lcd.c menu.c rockmacros.h and sys_rockbox.c”

Sometimes the failure does not happen and reaching the menu is possible, but the rockboy option file may get written and not allow the user back into the menu later to change the rotate option back. When this happens the option file must be edited or erased to make rockboy work again normally.

I'm decided to make myself useful today and hammered out most of the rest the code needed to move http://www.rockbox.org/tracker/6048 along.
I'm starting a new entry since the old one is closed.
I'm hosting all the work I do at http://foolsh.no-ip.org/projects/atari2600/wiki/Wiki

2600box Plugin

* Added the .make file
* Added keymaps for most color targets
* Added to viewer.config loads *.bin files
* Fixed screen resizing for smaller screen targets
* Compiles against HEAD/master

I'm still testing sim builds at the moment.

There is some bad news, it crashes in the sims after a minute or two, and the buttons on my fuze+ don't work for some unknown reason but they do in the sim.

Everything else is looking pretty good. I'd like to hear back from people who have real hardware and can test the keymaps.

On my Sansa c250v1, the starfield plugin crashes at the address 0x01F80394 with a data abort.
It seems that the plugin is attempting to execute data.
Strangely, it does not happen in the simulator.

Metronome plugin is not functional on Ipod 6G.

Steps to reproduce:
1) Open metronome;
2) Hold the "Select" button.

Expected:
– The metronome starts to tick in the headphones.

Observed:
– The text on the screen changes from "start: hold select" to "stop : cancel", but no sound is made.
– A short click on the Select button emits a single tick sound, but the tapped frequency cannot be captured as the Ipod 6G does not have any "Record" button.

Comment:
As single taps can be made, the metronome.c / play_tock() seems to work
and at least some sort of sound can be produced on this hardware,
maybe something is wrong with the timer_callback() ?

Bug exists in the DEV builds for, at least, Sansa Clip+, Sansa Fuze+, and iPod Video for at least a year, although I cannot confirm this as I've only just now tracked down the problem. The issue was discovered because imagemagick occasionally selects 1x2,1x2,1x2 as the chroma sampling factor when converting an image.

To recreate this bug, convert any image using imagemagick to a JPEG with that chroma sampling factor and attempt to view it in Rockbox. What you will see is a nonsensical image to the size of the original JPEG. Any desktop image viewer, like eyeofgnome, renders the picture correctly.

I've also included a sample Rockbox logo generated in the faulty fashion along with this bug. To create it, run this command in a Unix-like with imagemagick and curl installed: 'curl -J -L "https://www.rockbox.org/rockbox400.png" | convert - -sampling-factor 1x2,1x2,1x2 -quality 100 folder.jpg'

The volume settings are bypassed and is at max volume when the plugin is started. Even when putting it at -60DB it still has sound. After exiting and relaunching the app,the volume is maxed again,regardless of volume settings.

Rockboxutility barfs while creating talk files if it encounters unpronouncable charicters (japanese kanji) and does not continue afterwords resulting in talk files not being copied to the player.

[talkgenerator.cpp:156 INFO] voicing: "シマシマ" to "/tmp/talkfiles/952b0e2854336082e41fb0ef8ef8dc97.wav"
[ttsfestival.cpp:188 INFO] Voicing "シマシマ" → "/tmp/talkfiles/952b0e2854336082e41fb0ef8ef8dc97.wav"
[rbsettings.cpp:162 INFO] GET U: "festival-client/path" "/usr/bin/festival_client"
[ttsfestival.cpp:194 INFO] Client cmd: "/usr/bin/festival_client –server localhost –otype riff –ttw –withlisp –output \"/tmp/talkfiles/952b0e2854336082e41fb0ef8ef8dc97.wav\" –prolog \"/tmp/RockboxUtility.zowYwG\" - "
[:0 WARNING] QProcess: Destroyed while process ("/usr/bin/festival_client") is still running.

/
The result of this is an invalid wav file wich the the encoder bails out on and the process aborts.

[talkgenerator.cpp:235 INFO] encoding "/tmp/talkfiles/952b0e2854336082e41fb0ef8ef8dc97.wav" to "/tmp/talkfiles/952b0e2854336082e41fb0ef8ef8dc97.talk"
[encoderrbspeex.cpp:82 INFO] Encoding "/tmp/talkfiles/952b0e2854336082e41fb0ef8ef8dc97.wav" to "/tmp/talkfiles/952b0e2854336082e41fb0ef8ef8dc97.talk"
[encoderrbspeex.cpp:103 ERROR] Error: invalid WAV file
[ttsfestival.cpp:29 INFO] Destroying instance

I suggest ignoring failed encoded files and continuing encoding and copying the files that suceeded.

Unsure if this is an RBUtil isssue or a sansapatcher issue, or even a Sansa issue that can’t be solved, but according to this (http://www.rockbox.org/irc/log-20080709#02:36:38), it reports a successful install on the e200R when it hasn’t. Related to  FS#7526 ?

The following patches will allow someone running openBSD to run ipodpatcher. This is my first pass at these patches, so they cannot be integrated without some problems.

A few outstanding questions remain:

1) should I use /dev/sd0c or /dev/rsd0c?

2) why do byteorder(3) functions exist in fat32format.c?

3) how do the developers want to handle disk geometry?

I ask the last question because my patch overwrites the existing ioctl with what works for openBSD, rather than separate it out. And the patch doesn't fully use what is available in struct disklabel. I plan to re-write this one.

The fat32format.diff comments out byteorder(3) functions. The ipodio-posix.diff converts the file to openBSD disk geometry. The ipodpatcher.diff corrects the device used.

I have only tested the patches above for ipodpatcher on iPod nano 1st gen.

This task is to develop a stand alone command line interface for use with SAPI. This will be designed to run under Windows or WINE.

This will replace the platform dependent VB script currently in place adding new features and try to improve performance.

I have attached an initial release, run with -h option for usage info.

This is not completed had very litttle error handling and due to performance issues under wine I am considering a new server/client model for a future release.

The Rockbox utility generates its talk files and directory files using the filename and directory names.

If the filenames do not contain spaces, but are CamelCased, they are currently synthesized badly, for example: “I Do I Do I Do” gets pronounced eeedoyeeedoyeeedoy.

The patch to the rbutil/base/talkfile.cpp processes CamelCased filenames and directory names just before synthesis and produces much better sounding talk clips.

The manual offered by Rockbox Utility is not necessarily the version that accords with the installed (or to-be-installed) program.

E.g. select Release 3.13, and the Manual offered is http://download.rockbox.org/manual/rockbox-sansafuze.pdf not http://download.rockbox.org/release/3.13/rockbox-sansafuze-3.13.pdf .

http://www.rockbox.org/irc/log-20140124#15:41:22 says this is a bug. Since the user does reasonably expect a manual to accord with the program, I too think this is a bug. Whether it is a design bug or code bug, I cannot guess.

Note: this task says Operating System: All players but only because the actual player, Sansa Fuze, is not offered. Though this issue may indeed apply to all players.

Affected versions:
RBUtil V1.4.0
git version 2a2800b528010320ca504a39106806ec21f0220 (2016-10-12)

rbutil fails to build bootloader. Tested for Iriver H1x0 and H3x0 platforms.

Progress window shows:

Adding bootloader firmware file
Error in patching: reading firmware failed

Terminal output shows:

[httpget.cpp:230 INFO] Get URI “http://download.rockbox.org/bootloader/iriver/bootloader-h300.bin”
[httpget.cpp:200 INFO] Request started
[httpget.cpp:148 INFO] Request finished, status code: 200
[httpget.cpp:151 INFO] Data from cache: true
[bootloaderinstallbase.cpp:71 INFO] Downloading bootloader finished, error: false
/tmp/qt_temp.U16458: Resource temporarily unavailable
[selectiveinstallwidget.cpp:195 INFO] continuing install with stage 1
[selectiveinstallwidget.cpp:197 ERROR] Last part returned error.
[selectiveinstallwidget.cpp:214 INFO] All install stages done.
[rockboxinfo.cpp:27 INFO] Getting version info from rockbox-info.txt

Fired up gdb and debugged the git 2a2800b5280103… build:

The failure is in function mkboot_iriver in mkboot.c line 98:
Line 98:

  i = fread(image+16, 1, len, f);

len is calculated as 2636272.
But file size of /tmp/qt_temp.U16458 is only 2621440, resulting in a short read of 2621424 bytes. So error condition “i < len” fires and function returns without building bootloader.

I tested this on two different gentoo systems. It worked on one, but failed on the other. Both are more or less up to date, but have one significant difference: 32bit vs 64bit system.

The system that did compile and run perfectly uses:
gcc i686-pc-linux-gnu-4.9.4 (len=2636272, file size=2637824)
The system that failed uses:
gcc x86_64-pc-linux-gnu-4.9.3 (len=2636272, file size=2621440)

So, the failing rbutil creates a temporary file that is too short. I didn’t debug deeper to find out why.

cu
John

Hi,
I’m trying to record myself playing the guitar using my old, trusty FuzeV2 (both a very old version - sorry didn’t wrote it down but had to be at least a couple of years ago - and today’s version 87229a4). Recording parameters as follows:

Trigger: Repeat
TrigType: New file
Prerecord Time: 1s
Start Above: -22dB
for at least: 1s
Stop Below: -26dB
for at least: 1s
Presplit Gap: 1s (don’t really understand what it does from the manual, but it says it usually has to be the same value of the Stop Below Time, so…)

Recording starts correctly when noise is detected according to conditions; then apparently it correctly detects the silence and stops the recording. But immediately the ‘Repeat Trigger’ parameter kicks in and _immediately starts a new recording_. At this point, the trigger status and the recording status aren’t matching anymore. The recording screen shows the recording file size growing, but the Trigger status is ‘Ready’. I have confirmed that on the actual file on disk the silence is meanwhile recorded.

Did I understand any of the parameters wrong or has anybody else the same problem?

I know that the folks that added recording functions to the PP targets only did it as a proof-of-concept, which rteally works well already. I am curious if anyone has looked into the bizarre noise that is generated on the right channel, I have tested this on two different 4g grayscale ipods and on 5.5g ipod. The noise level is lower in the 5.5g than the 4g's. I have attatched a png of jamin running a "silent" recording (no mic connected) and the wavpack file. I amplified the sound to get it to register higher on my spectrum analyzer.

According to http://download.rockbox.org/manual/rockbox-sansac200/rockbox-buildch5.html#x8-930005.8 the power button is supposed to exit the recording menu, but when I press it nothing happens. I have to power off the device and power it on again to get back to the main menu.

When recording, as file size reaches 25.2MB and again at 52.4MB respectively, disk thrashing noise drowns out the recording for about 2 minutes.
This occurs at about 27.5 minutes if recording as mp3.
And about 5.25 minutes if recording as wav.

I am assuming that Rockbox is filling a cache and then dumping the file to disk all at once.

I would expect it to write quietly. Even if it where to write on the fly, the noise would be reduced to short bursts. 2 minutes of interruption is just not acceptable. I missed out on important information during those 2 minute periods.

How can we eliminate write noise altogether? Or at least in the recording itself.

Select ‘FM Radio’ Choose your station.
Then from the menu select ‘Recording’ Press ‘play’ or ‘Rec’ to begin recording.
Wait for file size to reach about 28MB. Then stop.

I can also provide recordings if necessary.

*note: I also had the USB cord attached to give better FM reception.
tested on e260 & e280
Rockbox Version: r15988-080102

Thanks

This bug currently exists as of rev 21444.

If settings are modified on the recording screen they aren't persistent after a reboot unless another setting is changed somewhere in the menu system.

The problem is that global_settings is being modified without a subsequent call to settings_save().

Attached is a fix for this problem. I've so far only tested it on the h1x0 simulator but I think it's a pretty benign change, unlikely to cause problems on other targets.

I navigate to any directory in the file tree, enter the context menu and set it as the recording directory. Then I go to the recording screen, cancel out immediately and return to the file tree.

There is now a new directory, in the same place as the directory I just set for recording. The new directory has exactly the same name except the final 3 letters have been removed, and it is this directory that has become the recording directory. The original directory is still there too, but now it does nothing.

The workaround is to create a bogus directory with 3 extra letters, then delete it once the bug creates the new directory with the truncated name.

Hi!

I’ve found very important bug in Rockbox 3.7, witch my be dangerous for both the player and the memory card (if present).
It turned out that Rockbox doesn’t react to very low battery level while voice or FM radio is recorded. It causes damage to the recorded file when finally hardware falls due to lack of energy. This corrupted file is absolutely unreadable.

What the title says.
At whatever sample rate I use (24k & 48k tested), each sample is duplicated.

On my Sansa Clip+ 4GB, with Rockbox v3.11.2

Recording a wav file through internal microphone. If the audio signal clips at the positive limit, bad things happen:
1) Most of the time the recorded signal wraps around to a full scale negative value, which makes it sound terrible.
2) Sometimes the recorded signal wraps around to a near zero value, which still makes it sound terrible but the distortion is not so loud

3) Clipping at the negative end of the range is as you would expect - a flat line which sounds like normal digital distortion, as you would expect

See attached picture of the recorded waveform showing each of the 3 situations described above.

Player Type = Sansa Clip+ (not available in chooser when submitting).
Release = 3.11.2

Recording at 48kHz results in audio that is 2.35% too fast. I believe it is recording at 49155Hz instead of 48000Hz. Recording at 44.1 kHz does not have this problem.

I have verified by putting 2 identical Clip+ in front of me, one set to rec at 44.1 other at 48.0. When playing back audio (on PC) difference in pitch is (barely) audible. And the audio falls out of sync as recording progresses (in video editor).

For now I’ll be happy to only record at 44.1kHz, but maybe 48kHz recording should either be fixed or dropped from Clip+ options.

(Confirmed this in 4c6c8cd-130926, discovered in build from several weeks earlier)

If ‘Voice Menus’ are enabled, entering the Recording menu will freeze the player…usually before the entire screen is redrawn. Although I can still hear the sound the mic is picking up, the player is locked up, and removing the battery or super-long-pressing of Power is required.

During my testing, I was able to randomly get it to -not- lock up, but it was like a 1 in 50 occurance…tried all formats/sample rates/etc. When ‘Voice Menus’ is -disabled-, all formats/rates/etc work fine.

Thinking it was a problem with my config that I’ve been using for years, I tried with a clean config.cfg (well, deleted and let it regenerate), and narrowed the cause down to the spoken ‘Voice Menus’ being enabled.

Today I've experience something which IMO should not happen.

I recorded vian the built in micro on my Sansa e200 v1, paused the recording (not stopped!). In this state, I plugged USB cable. After that, there was the following text in the system font on the display, and the player did not respond to any keys. It had to be restarted via very long pressing at On/Off.

The text is:

*PANIC*

usb_storage_init_connection
(): 00M
pc:0006B878 sp:000D3538

  A: 00069978
  A: 00069F80
  A: 0005326C

bt end

I've reproduced this three time in a row.

I have the official version 3.14 installed.

Daily build c6d5cd7-170907

An idle power off can occur in recording mode. When it does, data loss occurs. This has already bitten me a few times.

Steps to reproduce (on battery, not charging):
1. Execute Settings > Manage Settings > Reset Settings
2. Set Settings > General Settings > Startup/Shutdown > Idle Poweroff to 1 minute
3. Reboot
4. Go to Recording mode
5. Note current Volume and Gain settings and then change them to something else and note the new settings. Don't start a recording; just leave it in “stop” mode (*not* record or record-pause).
6. Wait for automatic power off
7. Power back on and check recorder settings

Expected: Settings are what they were after being changed.
Actual: Settings reverted to what they were on boot.

This can cause the loss of entire recordings, too:

8. Go back to Recording mode.
9. Wait until just before Rockbox would power off, then start a recording (if the display goes to sleep, it comes back on a bit before powering off; start the recording as soon as it comes back on).

Expected: Recording is done as usual
Actual: Rockbox powers off anyway, without warning, less than a minute into the recording. The recording is lost (or if the file is there, it's unplayable; maybe this depends on the recording format used).

Pressing the remote volume UP key on my iriver 140 in wps sometimes results in directory skip.
This is not easy to reproduce, but I was able to repeat once that problem in conditions where I'm sure that the directory skip key wasn't pressed.

I don't know if it's a hardware related problem, but I've read somewhere about another user having the same problem.

The attached patch slightly modifies the keymap of the H300 non-LCD remote to allow access to the browser from the WPS (by use of LONG PLAY).

I know that it works ok from an H300 with a non-LCD remote, but I don’t know if I’ve broken the LCD remotes completely.

Please could users of both the H100 and H300 LCD remotes try this patch and tell me that the WPS context keymap is unaffected. For reference, you can see the intended mapping here: http://www.rockbox.org/twiki/bin/view/Main/KeymapIriverHSeries

If your Ipod accessory doesn’t work with rockbox, you can report it here.

Please put your device name, Ipod model, and tested rockbox version in your post. If some but not all features work, be sure to mention that in your post.

Edit by rasher:
You should also add your results to this page page: http://www.rockbox.org/twiki/bin/view/Main/IpodAccessories

For any developers who might work on IAP support, please add patches to this task, so potential testers are notified.

I have been using Rockbox for almost 2 years now on my X5L together with the remote and I have frequently updated to the current version, so I am familiar with how it works.

I have noticed that after updating to version 20090221, my X5’s remote’s LCD behaves erratically (strange lines being displayed all over, vertically shaky image) right after booting Rockbox, then the display turns off completely after a few seconds. Strangely though, the controls still work and the blue display light comes on when working the controls, but the display is turned off (there is nothing being displayed, as if the player were turned off). If I unplug and reconnect the remote, the remote’s LCD comes on, but soon turns off again. The X5’s main LCD is working just fine.

I thought that my remote was dying on me, but decided to check if it was somehow related to the development of Rockbox. I reverted back one build after another and found that the last build that works OK for my remote is 20090210. So, in all the builds starting with 20090211 (I have thoroughly checked all from 20090211 to 20090225), the remote is practically unusable. I looked at the changes done on that day (http://www.rockbox.org/daily/changelogs/changes-20090211.html), but could not single out the probable cause.

Great software, anyway!

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.

Hi,

this patch, that takes some of the FS10494, improves dock detection and initialization.

It should correct the erratic behaviour on some hardware, and it also adds support for some remote buttons: menu, select, up_arrow and down_arrow.

The buttons arrow are not usable by now, even if they are defined. I tried severals things but i couldn't get it to work.

Any idea of which context I should use to use the button arrow to scroll through the main menu?

When connected to PC.
While transferring files from PC to Sansa e280v2.
Both source and destination folders are open.
Sansa shuts off after some time. while transfer is still happening.
this does not happen with original firmware.

Rockbox starts with remote, but doesn't respond to button presses except turning backlight on with build 6039eb05b-180313.
It works with deaeb73-161114 though.

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

rockbox 3.5: ipod doesn’t recognize the connection of usb. i understand that rockbox doesn’t support usb on a 3G ipod, but it would be nice to boot into disk-mode like it does for firewire.

Seen with r27199 on the e200 simulator.

If I place a .wps file in the root directory and “play” it from the file browser, the WPS is not loaded. I’d expect it to load but not to be saved as the setting.

The same file is loaded if it’s in the directory /.rockbox/wps, i.e. it’s not the wrong file contents that’s causing the error.

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.

When I use the "Wake Up Alarm" with the "Wake Up Screen" set to "Recording." my Nano turns on OK, but the screen starts on the FM screen. This is especially strange as there is no FM radio on this player.

I am expecting the player to turn on and start recording.

This is a 1g Nano running 3.9

Thanks.

in svn settings_apply() is called whenever a config is loaded (after boot) regardless of what is in the file. even an empty one will cause a full settings_apply() (which is slow, causes disk access and will stop music thanks to the buflib users).

This patch will apply settings individually if they have a callback registered, and if no settings without a callback are applied it doesnt bother calling settings_apply().

If loading a config file that holds all configuration settings (Settings → Manage Settings - Save .cfg File) from Rockbox 3.9.1 in Rockbox 3.10 or the daily builds for Archos Recorder with Firmware V3, the player will not bootup correctly on the next restart and show:

I 4: IllInstr

directly at booting. I then press "On" again and get:

*PANIC*
Stkov main

and the HD shuts down. If I press "On" again, the same loop continues.

The problem can only be resolved by plugging the player to USB, removing the rockbox directory and copying it again from the newest daily build or 3.10, then restart. It boots up fine again then. Doing the previous settings manually on 3.10 or the daily builds and then saving / loading them works fine and the player won´t have the boot-bug anymore.

I have attached the config file that creates the problem.

Settings such as "eq enabled" and "replaygain type" do not apply to a playing track when selected from shortcut menu, although the setting does appear to have changed when checking in the settings menu. The audio remains unchanged when changing the settings. However, when changing the same settings via the settings menu they function correctly (e.g. audio noticeably changes from loud to quiet after a few seconds).

Also, while displaying "debug info" on the wps, I noticed that %rg (replaygain value in dB) DOES change when the replaygain is changed via the shortcut menu, even though the audio doesn't change. (Both %rg and the audio change when the same setting is changed via the settings menu).

NB Some settings DO work, such as bass and treble.

Problem noticed on Sansa Clip Zip (build 2f1da04-120627), UiSimulator of Sansa Clip Zip (build fa17cb9M-120627).

Changing “Enable EQ” setting does nothing until the player is restarted. However, selecting an EQ preset does enable the EQ and take affect within a few seconds. With the new 3.13 presets I am working around this issue by simply selecting the “Flat” EQ config file to “Turn Off” the EQ. I have tried stopping playback and skipping around to other tracks forcing the buffer to refill. That doesn’t work.

I don’t know when the bug was introduced except that testing 3.11 on my Gigabeat F proved it WAS NOT present in 3.11.

I have verified the bug in 3.13 on all of these targets, so at this time I’m saying this affects all players.

Confirmed on Fuze v2, Clip v1, Clip +, Clip Zip, Gigabeat F

According to the manual, to exit the EQ settings page you press the back button on the fuze+. This doesn’t work. I tried all key combos and none work.

Hello there,

When I reboot my Rockboxed iPod nano second generation, it changes the time +5 hours.

Does anyone know why this can be? Thanks

Note: This is work in progress.
Status: Code implemented

      Manual not updated
      Wiki not updated (only after commit)

The idea of this patch is to have the same keyboard keys assign to the same actions in all platforms.

For example, have +/- keys (both on keyboard and on Numpad) are assigned to Volume Up and Volume Down keys of the original platform.
For platforms which do not have these keys, pressing the +/- keys in the simulator will do nothing.

This change will help developers to do manual regression testing on lots of platforms easily, as they do not have to memorize each platform’s key assignment.

Future development: Display key assignment on screen, and/or on console

This patch enables you to compile the Rockbox simulator with LLVM (you still need to alter the Makefile yourself though).

However, it fails at linking stage with 'file not recognized: File truncated' errors.

This patch enables you to control the simulator using a named pipe to provide simulated keypresses, rather than the keyboard.

Unfortunately there is a bug that means that not all events seem to have any effect. On the e200 sim, I can use the scroll buttons to move in the main menu, but neither RIGHT nor SELECT lets me enter any of the entries. I suspect it's related to repeat or hold/release handling, but I'm not sure how to fake that properly.