I store the album art by putting a folder.jpg file in the album's directory.
Any WPS on other players shows the cover pictures properly if album art is enabled in the theme.

I am aware of caveats like progressive jpgs, that are not supported by RB.

In the attached zip file, there are four directories with a folder.jpg file and a free opus file for demonstration purposes.

All pictures show up fine on my Sansa E200 (v1) using CabbieV2 or lebellium_Samsung-like.
However, on my XduOO x3ii the pictures are not displayed for the examples 1 - 3, but show for example 4.

None of the jpgs are progressive and I cannot figure out a difference between 1-3 and 4.

I don't know how to debug this further myself, but would be happy doing any furter experiments.

This is true for the current dev builds, e.g. b450707955.

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.

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.

at least r30058
On the Sansa E280 v1 with a playback speed of 200% the playback restarts at bookmark plus about 2 seconds.

On my iPod video, when I choose to load the WPS on startup (either in the Settings menu or in the alarm menu), it doesn't work. The player stays on the main (root?) screen.

I had to tweak root_menu.c (which I join) to get the alarm to work with the WPS. This is not a patch, but a quick and dirty workaround that I did just to be waked up on time tomorrow…

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.

Hi,

I’m experiencing an issue with WMA Pro playback on my Clip Zip.

I’ve got the lastest stable build of Rockbox 3.13. Files were encoded with dbpoweramp.

Some files playback normally, but majority of tracks skips. Always at the same point if not forwarding or rewinding.

Here’s a sample. The track skips at 2.15.

decode_packet in wmaprodec.c returns -1 almost immediately, most likely due to being passed corrupted data by the ASF parser, although I have not confirmed that to be the case. I've seen similar issues in WMA Std. Theres probably some ASF feature we do not correctly implement.

Player = Sansa ClipZip
Rockbox current build :

Hello World :)
Attached is a VBR WMA music file, which fails to play correctly on my “RockPod” iPod Nano.
The same file decodes perfectly using the latest ffmpeg build.
Therefore I can only assume there is something about this file which triggers a bug in the Rockbox-specific WMA decoder.
Also attached is a microphone recording of the sound which comes out of my iPod when Rockbox attempts to play the faulty WMA.

I have over 3000 WMA tracks, all encoded using an identical method, all of which will not play correctly in rock box, so if you would like any more examples, or information, please ask.

Thanks for all your help :)
(If there is any way I can help debug/update the code for the wma decoder, please let me know where to start, I understand the C source code pretty well)

~Andrew

Latest version of rockbox installed on both Sansa e200 2GB and Sansa Clip Zip 4GB. (3.13) Sorry, release 3.12 was the only one available in the reported version pulldown.

Windows 7 Pro 16GB RAM, i5-2500K, 3.3GHz/ 3.6 GHz, 64-bit. 7.3 Windows Experience Index. OS is otherwise stable and up-to-date.

Blue Screen of Death only happens when I try to connect first one Sansa Device via USB to Windows, transfer mp3’s or update a theme, unplug it, then connect a second Sansa different device. It doesn’t matter whether I start with the e200 or the Clip Zip or vice versa. Upon immediately connecting via USB with the second device, I get a BSOD. I have two e200 devices. It can happen sometimes even when I connect first one e200, then the other.

I can disconnect and reconnect the starting device (for instance the Clip Zip) as often as necessary, but if I want to connect to the e200 (for instance to update a theme), I have to reboot the computer in order to avoid the BSOD.

(./version.tex)) [2] [3]
1.

Class scrreprt Warning: \float@addtolists
You should use the features of package
instead of
Support for \float@addtolists may be removed
`scrreprt’ soon .

This is the warning text I get. We should probably update the syntax before it get broken.

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.

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?

So far there's still two problem which have never been fixed on Android:
1.When opening Rockbox, its volume bump to max automatically whatever it was when last quit;
2.On most HTC(and probably other) devices one can't use physical volume keys to adjust. Volume bars in WPS and SBS work well however.

Hopes the fixes!

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.

When the battery is nearly empty and the iriver H10 is about to shutdown, the volume sometimes suddenly increases progressively, as if the volume UP button was pressed and held down, all the way up to the maximum.

This has happened to me about 3-4 times so far. Pressing the volume DOWN button somewhat counters this bug, but only for as long as the DOWN button is used - the volume keeps increasing.

This occurs with Rockbox Release 3.5 (not 3.4 as the Report Version field of the ticket says).

I installed release 3.3 on my Sansa e260. 3.2 worked. On 3.3, volume controls work fine in normal playback mode, but when I switch to FM Radio, they are ignored. If I switch back to normal playback mode, I can set the volume level again, just not while listening to the radio.

Rockbox doesn't speak in the FM mode with voice configured. I tried it in my local language (spanish) and in english with same results. Apparently it is not a problem of the translation, because sometimes (only 2 or 3 times in at about one year that I'm using the player) the player speak some words. This works correctly in release version.
My actual version is 0f89b04, but it happend in all dev versions.

Voicing of menus will work fine on the default font. However, if 08-Namil is used, the voicing dies upon reboot.

See also http://forums.rockbox.org/index.php/topic,51408.0.html .

http://web.mit.edu/mgg6/www/cover.jpg

This file is correctly decoded and displayed in the Fuze+ simulator, but testing on device results in playback stopping. Interestingly, nothing crashes, playback just stops. In theory we should be able to decode this, the resizer does not need to load more than a few lines of the image at once, which should easily fit in memory. Alternatively, if it is too large (or rather wide given that its decoded line by line) for the available space, it should probably just be rejected.

Consider the following theme markup:

%Vl(progressbar,306,156,10,80,-)
%pb(0,0,10,80,progressbar.bmp,vertical)

That draws a vertical progress bar that will get filled from bottom to top. When a song starts to play, the progress bar is one pixel high, at the correct position (at the bottom of the viewport). That 1px-high image quickly jumps up one pixel (moves up by one pixel), then comes back down one pixel (at the correct position) whenever the progress percentage is high enough. The progress bar then displays normally and grows as the song is playing. See attached screenshots.

Expected behavior: the position of the progress bar (relative to the viewport) should not change. The bug has been observed in the iPod Classic and Clip Zip sims (builds 1bc89bd and 77bfff5) as well on the actual devices. Inverting the progress bar (with the "invert" parameter) shows the correct behavior (inverted bar with no such glitch).

Affected themes: Ash (iPod Classic), SugarBrown (Clip Zip).

I noticed various RDS-related issues on my Clip Zip and Samsung R0

1) Sansa Clip Zip
With the latest builds (for example version 341e2c4-120929) I noticed the RDS text just behaves crazy, like blinking for no reason and displaying strange characters. Besides, the RDS name won't display most of time or at least needs much time to display.
When reverting back to an older build (0c4bd3a-120406 for example), the RDS name displays quickly and for all stations now and the RDS text is just displaying and scrolling normally.
Tested and noticed with my theme lebellium Samsung -like: http://themes.rockbox.org/index.php?themeid=1681 and with the various DFKT Minimum Zip themes (this one for example: http://themes.rockbox.org/index.php?themeid=1539 )
screenshots of the issue: http://imageshack.us/a/img855/8724/dump120926124155.png http://imageshack.us/a/img837/2154/dump120926124439.png

2) Samsung YP-R0
In addition to the RDS issues reported for the Zip above that also exist on the R0, it seems that the RDS text makes the device crash after a few seconds or minutes with my theme lebellium Samsung-like (version 1.60 beta to download in attachment).
I found 2 unsatisfying ways to bypass this annoying crash:
-Remove the %s scrolling tag for the RDS text, that is to say replace "%s%ac%tz" by "%ac%tz". But that's not a good solution since then the RDS text is cut off. The %tz tag only makes sense when associated with a %s tag and all other themes supporting RDS use it and work well that way.
-Replace the RDS text font (currently 20-DroidSans-Bold.fnt) by another font from the Rockbox Font Pack. As I want a nice anti-aliased font, the only acceptable alternative I found is the Ubuntu Bold font. But this font makes the device crash too…

So I just hope there is a bug somewhere that can be fixed?

I recognize some problem with USB support.

When I’m connecting my player first time, it’s work correct - computer’s mounting device propertly. BUT When I disconnecting it, turn on playing and while music is still playing I’m connecting player once more - Rockbox is crashing and give information about “unidentified instruction at… “. Now player looks like dead - I must reset it and Rockbox start correctly.
When I’m not turning on songs - all works fine.

Sorry for my english…I’m still learining It

As the title suggests, fun things like: https://plus.google.com/102855057878446061693/posts/FkQ4wQZb8VD can happen in this instance.

Initially reported here: http://www.rockbox.org/irc/log-20130113#07:14:49

[Saint]

USB is broken on mr500. I’ve tried r31467, but this has been the case since at least a few weeks ago.

Enabling logf in the relevant places causes rockbox not to boot, so wasn’t helpful.

I’ve seen this bug on 3.9.1 and 3.10 on Sansa Fuze. If I set the language to Russian and connect the device to USB, I see a message consisting of squares with the only word “USB” being readable. Choosing another font in the settings makes no difference.

When the language is set to English, the message reads: “USB Keypad Mode: Multimedia”. However, the size and look of the font does not depend on the font selected in the settings. This is wrong.

If there is a real need in having a special font for the USB keypad mode text (which I doubt), that font should have glyphs for all supported languages.

Using a bootloader from  FS#9955 , a USB connection is not made if Start Screen is set to WPS, and the user boots Rockbox by inserting a USB cable.

This is possibly also true for other values of Start Screen.

Tested on e280, but I expect it’ll likely be the case on other PP targets with USB

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.

With r30907 (and also back to at least r30809 which I tested as well) I experience unneeded mass storage accesses on my iPod nano2G. I do not see this effect on my iPod Video.

Use case:
- Create a playlist from either DB or file browser
- Let buffering finish
- Skip forward track by track
(I use mpc/mp3/aac with embedded album art.)

Effect seen: For some skips I see short flash accesses (much shorter than full rebuffering).

This only happens if dircache is off. With activated dircache this effect is gone.

As such mass storage accesses are severely impacting the battery runtime on HDD targets I hope we get this figured out before v3.10.

Version: 3.13

Variable ‘tmp’ on line 565 is possibly not initialised (found by cppcheck).

Hello, all
There's a problem with viewing files in some circumstances in iPod 5.5G last 3.9 release.

When I:
playing something in /Music/Artist/Track.flac,
pause playback,
connect USB cable.
rename /Music/Artist to /Music/ArtistSOMETHING, then disconnect USB cable

I just cannot turn playback on ("~Do not exist" or something message appears, it's OK, I know),
BUT
when I trying to enter in "Files" menu - there's no reaction at all. Just nothing. I can't play of any other existing track or change to any directory without restarting device, or:

just go to Playlists → VIew catalog → select some playlist, then some music appears. But it's too long imho.

Is "it" bug or not?.. :)

Thanks,
sorry for my english,

The player (Sansa Clip Zip) appears to refuse or unable to play some of my WMA tracks; as far as I can tell, the problem is specific to my WMA Pro files only as it plays none of them (but works with WMA2 successfully). I have attached one of the examples.

I understand that a similar issue was reported recently (in  FS#12619 ) although, in my case, the player doesn’t start playing and skips to the next immediately, rather than playing part of the track.

Click on the music file and die

All i know is that this happened on 590mb tta file and after cutting it with cue splitter there was no problems with playback.

SVN:31187

recent %Tl and %T changes need adding to the manual… didnt want to fiddle with the table.

The change is now that both those tags accept as their first param a label which links them.

%T(foo, 0,50,25,25, volup)
%?Tl(foo, 1)<helllo|goodbye>

So that conditional will only go true when that foo region is pressed. the label is optional on both, if it is missing on the %Tl then it acts as now (timeout since last press on anywhere on the screen)

When my Fuze+ is charged and it's still connected to the charger, it seems it keeps toggling between charging and discharging.

I think the problem is that it reacts to some voltage to stop charging. When it's charging it measures up to 4.35 V. But when it stops charging it changes to 4.25V, and says something like 96-99% charged, and which point it changes to charging again, and so on.

So it's basicly toggling between charging and discharging very often, and I don't think that's very good for the battery. Once it's charged it should stop charging as long as the charger is connected. (This might apply to other devices too.)

This was with version 2ef7a54-130111

Kurt

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

While in the fm radio screen, a ticking noise can be heard in the background. When pressing the power button in the radio screen the noise disappears.

Every time I try to set my theme to ThinBasic in Rockbox 3.11.2 on my nano 1g, a panic occurs.
I only tried this in 3.11.2 so I'm not sure if older versions have this problem too.

When a WPS defines a touch area combining %T and setting_inc or setting_dec, although the themesite parser does not show any problems and allows the theme to be loaded normally, the themesite doesn't display the theme. Some examples to be found in this forums thread : http://forums.rockbox.org/index.php?topic=25098.msg173725#msg173725

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.

The Sazanami-Mincho-Regular-*.fnt includes 7128 characters.
However, there are about 7500 character not included in the Sazanami-Mincho-Regular-*.fnt though it is included in the sazanami-mincho.ttf font (This font is a font that became an origin when the Sazanami-Mincho-Regular-*.bdf font is made).

Please look at “List.txt” file about the character not included in the Sazanami-Mincho-Regular-*.fnt.

The cause of this problem is in “fontForge”(http://fontforge.sourceforge.net)
used when the bdf file is made from the ttf file.

When the bdf file was made by using　”Otf2bdf”(http://www.math.nmsu.edu/~mleisher/Software/otf2bdf/) instead of “fontForge”, all characters included in the ttf file were able to be taken out.

However, when you make the Sazanami-Mincho-Regular-*.fnt by using Sazanami-mincho-Regular-*.bdf that applies the patch,
The interval between the line and the line opens from present Sazanami-Mincho-Regular-*.fnt a little.

Please report by using new Sazanami-Mincho-Regular-*.fnt(in new-Sazanami-Mincho-Regular-fonts.zip).

since build 31646 text viewer stops bookmarking or saving the last position on any file it shows bookmark added when i press the center+down buttons but doesn’t actaully save it.
seems to have a problem writing to the file tv_file.dat.

It seems that operators are discarded when used in a tagnavi.config (or tagnavi_custom.config) format line condition.

For example,

%format “fmt_abtitle” “*%s - %02d:%02d” title Lm Ls ? playcount > “0” & lastoffset == “0” %format “fmt_abtitle” “%s - %02d:%02d” title Lm Ls Now if we used “fmt_abtitle” instead of “fmt_title” in the default tagnavi file, we would expect all tracks with a playcount greater than 0 and lastoffset equal to zero to be prefixed by three asterixes (*). Instead ALL the tracks with a playcount greater than zero are prefixed, leading me to think that the & lastoffset == “0” part is discarded. If I make the following change:

%format “fmt_abtitle” “***%s - %02d:%02d” title Lm Ls ? lastoffset == “0” & playcount > “0” %format “fmt_abtitle” “%s - %02d:%02d” title Lm Ls

Now all tracks with a lastoffset equal to zero are prefixed, which again proves that the and operator was clearly ignored and unparsed.

I am running 3.4 on a 5.5G iPod modified with a 240gb drive. Rockbox is stock 3.4 with LBA48 added in and the max sector size turned off. The database was working ok on 3.3. Only issue was it took forever to add new files. After upgrading to 3.4 I noticed every time I powered on rockbox would lock up in the menus for up to 10 minutes before functioning normally. So I completely removed the .rockbox dir (including the database files of course) and re-expanded a fresh copy. I then tried to init the db. It runs until it is around ~44k files and 99% and then just sits there. If left alone it will eventually just turn it self off. When I turn it back on it will ask me to init the db again. I have seen it try to commit once or twice but it never takes. I am not really sure how to debug this at this point. Also in the debug disk info area, it things my drive is 131071MB. Under Rockbox Info it says 223GB which is better, but these two things are the same as in 3.3. All my Oggs are converted via a script I wrote from my flacs. I do not believe my flacs have any art, I am not even sure you can store art in a flac tag and even them I don’t think the ogg encoder is transferring them. I ran a tag dump (ogginfo) against my oggs and do not see anything to do with album art. I had 4 files on the device with album art. They were all in a directory with a database.ignore file. So they should not have been noticed. Just in case I removed that directory and rebuilt. It went though 44k files, commited 1-9 and then went back to “scanning” but the disk activity had stopped. Upon reboot it asked me to init the db again.

This is not a patched build. I simply changed the config to include large drive support. This is an issue that needs to be looked at. Please check into it, I will be happy to test any ideas.

I have only tested this on my H120 with an 18007 build. I have been using the APE codec for some time now and never had a problem in the past.

After reformatting my hard drive and installing the current build I found that rockbox has 2 problems with my APE files

1. The parser for APE files no longer recognizes my APE files encoded with version 8,9 of Jriver Media Center. Result is that files don't play when selected in the file browser and these files do net get added to the database.

2. When switching APE tracks one of two possible behavior occur. a) the Iriver freezes completely. b) On switching tracks there is a loud hiss and then playback of the next track resumes.

Cheers

  Thomas

Playing 320K MP3s pauses often in Version 3.15 and daily build 7d00533 also UI becomes unresponsive
Version 3.14 or older does not reproduce the issue in either 44 or 48khz sampling rate and same sound options
Is not reproducible under OF or Version 3.15 running on IPOD 6G
seems to be a cpu usage issue as compiling a version of rockbox with much higher than stock CPU clocks seems to alleviate the issue to an extent but there is still occasional pauses that is not present after reverting to 3.14 and stock 80 mhz clock speed.

On Gogear sa9200, when hold is switched to off(means in the middle), the play stops.
Maybe because the hold and the on/off share the same swtich.

Stereo width of >0% can cause stutter in the form of an audible click.

Bypassed by setting stereo width of 0% or monophonic channel configuration.