Mike Giacomelli | 23 Nov 03:36 2014
Picon

g#922 (new DSP effects)


Does anyone mind if I commit these?  Code looks good to me, but Mike S is the DSP engine expert.

Mike
Pierluigi Vicinanza | 1 Oct 01:16 2014
Picon

Rick Dangerous coming to Rockbox... a new (old) game for the best DAP firmware ever! :)

Hi all!

I'd like to introduce you xrick - a clone of the game Rick Dangerous, which has now been officially ported to Rockbox.
You can find more info about it on wikipedia:
http://en.wikipedia.org/wiki/Rick_Dangerous

and on the original xrick author's website:
http://www.bigorno.net/xrick/

This port is based on my own "fork" of xrick, which has undergone substantial changes to accommodate the needs of non-desktop environments, plus several bugfixes.

You can see a video of it running here:
http://www.youtube.com/watch?v=FKpxQzKP5ss

Sources and iPod/iRiver binaries can be downloaded from:
https://github.com/pierluigi-vicinanza/xrick/releases/tag/2.0.0-Rockbox



Please find below some notes/questions:

--------------------------------------------------------
= About code review/integration into main Rockbox tree =

How best to proceed from here? Should I open a new bug/feature in Flyspray? Should I just push a new commit to gerrit following the steps mentioned in "www.rockbox.org/wiki/UsingGit"?
What's the preferred way to integrate my code into git repo? I am no git expert, but I was thinking about doing a subtree merge into "${ROCKBOX_DIR}/apps/plugins/xrick" folder... or maybe a adding a submodule... What do you guys suggest?
Ideally I'd like to keep all commit history and allow any future fixes eventually done on my repo to be easily merged back into Rockbox.

---------------
= Legal stuff =

All hardcoded data (graphics, text, etc) has been removed from source files -data is now loaded from external resource files- to (hopefully) avoid any legal troubles in integrating xrick sources.
I've spoken to the original author of xrick and He's planning to tweak the README to reflect all this.
In the meanwhile, any feedback/suggestion to ease this integration is highly appreciated.

------------------
= Current status =

The port has been tested on iRiver H320 and iPod Video, on these targets it's fully working and complete.
I've added support for grayscale targets and been able to successfully compile and run the game on iRiver H120 Simulator.
All other targets are untested. It would be nice if someone could test and report which targets are capable to run current code.


Last but not least, a big thank you to all Rockbox developers for providing such an awesome firmware.

Pierluigi Vicinanza

Diaz Soho | 11 Sep 17:30 2014
Picon

ff_imdct_calc cause SIGSEGV error

Hi All, 

when I try to merge fixed point wma decoder from Rockbox to ffmpeg libavcodec, I got the problem.
ff_imdct_calc() cause SIGSEGV while decodeing audio data .
my OS is linux.
Does any one have ideas?
What I can check in advance?

Thanks a lot for any input!!
Diaz Soho | 2 Sep 11:32 2014
Picon

how to merge fixed point wma decoder to libav 0.7.6

Hi All, 

Is there anyone have idea about how to merge fixed point wma decoder to libav 0.7.6?
because my cpu does not include fpu, when use the wma decoder in libav , it take a lot of cpu time.

Or is anyone have merge fixed point wma decoder to libav?


Thanks for any input!!
Peter | 23 Jul 08:48 2014
Picon

slovak lang update

Hello All,
I am very sorry that i am doing lang update  in this way, I totally
forgot my login data to patchtracker. Attached is Slovak language update.
With best regards
Peter
Copyright by individual Rockbox contributors
See
http://git.rockbox.org/?p=rockbox.git;a=history;f=apps/lang/slovak.lang;hb=HEAD
for details.
May be distributed under the terms of the GNU GPL version 2 or later
This file generated by http://translate.rockbox.org/

This translation was based on git hash 43e52e34ed7c9a9b08ab706b75dd608f53d0b4cc of the original.

--- apps/lang/slovak.lang	2013-07-16 06:13:06.000000000 -0700
+++ apps/lang/slovak.lang.6.new	2014-07-22 23:44:58.000000000 -0700
 <at>  <at>  -12265,15 +12265,15  <at>  <at> 
   user: core
   <source>
     *: none
-    gigabeats: "Band %d Gain"
+    gigabeats,samsungypr1: "Band %d Gain"
   </source>
   <dest>
     *: none
-    gigabeats: "Šírka Pásma %d"
+    gigabeats,samsungypr1: "Hlasitosť Pásma %d"
   </dest>
   <voice>
     *: none
-    gigabeats: "Šírka pásma"
+    gigabeats,samsungypr1: "Hlasitosť Pásma"
   </voice>
 </phrase>
 <phrase>
 <at>  <at>  -12282,15 +12282,15  <at>  <at> 
   user: core
   <source>
     *: none
-    gigabeats: "Wide"
+    gigabeats,samsungypr1: "Wide"
   </source>
   <dest>
     *: none
-    gigabeats: "Široké"
+    gigabeats,samsungypr1: "Ĺ irokĂ˝"
   </dest>
   <voice>
     *: none
-    gigabeats: "Široké"
+    gigabeats,samsungypr1: "Ĺ irokĂ˝"
   </voice>
 </phrase>
 <phrase>
 <at>  <at>  -12299,15 +12299,15  <at>  <at> 
   user: core
   <source>
     *: none
-    gigabeats: "Narrow"
+    gigabeats,samsungypr1: "Narrow"
   </source>
   <dest>
     *: none
-    gigabeats: "Ăšzke"
+    gigabeats,samsungypr1: "Ăšzky"
   </dest>
   <voice>
     *: none
-    gigabeats: "Ăšzke"
+    gigabeats,samsungypr1: "Ăšzky"
   </voice>
 </phrase>
 <phrase>
 <at>  <at>  -12330,15 +12330,15  <at>  <at> 
   user: core
   <source>
     *: none
-    gigabeats: "Advanced Tone Control Settings"
+    gigabeats,samsungypr1: "Advanced Tone Control Settings"
   </source>
   <dest>
     *: none
-    gigabeats: "Pokročilé Nastavenia Tónu"
+    gigabeats,samsungypr1: "Pokročilé Nastavenia Tónov"
   </dest>
   <voice>
     *: none
-    gigabeats: "Pokročilé nastavenia tónu"
+    gigabeats,samsungypr1: "Pokročilé Nastavenia Tónov"
   </voice>
 </phrase>
 <phrase>
 <at>  <at>  -12347,15 +12347,15  <at>  <at> 
   user: core
   <source>
     *: none
-    gigabeats,mpiohd200,mpiohd300,sansafuzeplus,creativezenxfi2,creativezenxfi3: "3-D Enhancement"
+    depth_3d: "3-D Enhancement"
   </source>
   <dest>
     *: none
-    gigabeats,mpiohd200,mpiohd300,sansafuzeplus,creativezenxfi2,creativezenxfi3: "3-d Rozšírenie"
+    depth_3d: "3-D Rozšírenie"
   </dest>
   <voice>
     *: none
-    gigabeats,mpiohd200,mpiohd300,sansafuzeplus,creativezenxfi2,creativezenxfi3: "3-D Rozšírenie"
+    depth_3d: "3-D Rozšírenie"
   </voice>
 </phrase>
 <phrase>
 <at>  <at>  -12364,15 +12364,15  <at>  <at> 
   user: core
   <source>
     *: none
-    gigabeats: "Band %d Frequency"
+    gigabeats,samsungypr1: "Band %d Frequency"
   </source>
   <dest>
     *: none
-    gigabeats: "Frekvencia Pásma %d"
+    gigabeats,samsungypr1: "Frekvencia Pásma %d"
   </dest>
   <voice>
     *: none
-    gigabeats: "Frekvencia pásma"
+    gigabeats,samsungypr1: "Frekvencia Pásma"
   </voice>
 </phrase>
 <phrase>
 <at>  <at>  -12381,15 +12381,15  <at>  <at> 
   user: core
   <source>
     *: none
-    gigabeats: "Band %d Width"
+    gigabeats,samsungypr1: "Band %d Width"
   </source>
   <dest>
     *: none
-    gigabeats: "Šírka Pásma %d"
+    gigabeats,samsungypr1: "Šírka Pásma %d"
   </dest>
   <voice>
     *: none
-    gigabeats: "Šírka pásma"
+    gigabeats,samsungypr1: "Šírka Pásma "
   </voice>
 </phrase>
 <phrase>
 <at>  <at>  -12415,15 +12415,15  <at>  <at> 
   user: core
   <source>
     *: none
-    gigabeats: "Tone Controls"
+    gigabeats,samsungypr1: "Tone Controls"
   </source>
   <dest>
     *: none
-    gigabeats: "Nastavenia TĂłnu"
+    gigabeats,samsungypr1: "Ovládanie Tónov"
   </dest>
   <voice>
     *: none
-    gigabeats: "Nastavenia tĂłnu"
+    gigabeats,samsungypr1: "Ovládanie Tónov"
   </voice>
 </phrase>
 <phrase>
 <at>  <at>  -13033,3 +13033,121  <at>  <at> 
     *: "Vyberte Priečinky Pre Prehľadávanie"
   </voice>
 </phrase>
+<phrase>
+  id: LANG_LIST_SEPARATOR_COLOR
+  desc: line between lines in lists
+  user: core
+  <source>
+    *: "Line Separator Colour"
+  </source>
+  <dest>
+    *: "Farba OddeÄľovaÄŤov Riadkov"
+  </dest>
+  <voice>
+    *: "Farba OddeÄľovaÄŤov Riadkov"
+  </voice>
+</phrase>
+<phrase>
+  id: LANG_LIST_SEPARATOR
+  desc: line between lines in lists
+  user: core
+  <source>
+    *: "Line Separator"
+  </source>
+  <dest>
+    *: "OddeÄľovaÄŤ Riadkov"
+  </dest>
+  <voice>
+    *: "OddeÄľovaÄŤ Riadkov"
+  </voice>
+</phrase>
+<phrase>
+  id: LANG_SYSFONT_EQUALIZER_BAND_Q
+  desc: in the equalizer settings menu
+  user: core
+  <source>
+    *: none
+    swcodec: "Q"
+  </source>
+  <dest>
+    *: none
+    swcodec: "Q"
+  </dest>
+  <voice>
+    *: none
+    swcodec: "Q"
+  </voice>
+</phrase>
+<phrase>
+  id: LANG_VOLUME_LIMIT
+  desc: in sound_settings
+  user: core
+  <source>
+    *: "Maximum Volume Limit"
+  </source>
+  <dest>
+    *: "Obmedzenie Maximálnej Hlasitosti"
+  </dest>
+  <voice>
+    *: "Obmedzenie Maximálnej Hlasitosti"
+  </voice>
+</phrase>
+<phrase>
+  id: LANG_FILTER_ROLL_OFF
+  desc: in sound settings
+  user: core
+  <source>
+    *: "DAC's filter roll-off"
+  </source>
+  <dest>
+    *: "roll-off DAC filtra "
+  </dest>
+  <voice>
+    *: "roll-off DAC filtra "
+  </voice>
+</phrase>
+<phrase>
+  id: LANG_COMPRESSOR_ATTACK
+  desc: in sound settings
+  user: core
+  <source>
+    *: none
+    swcodec: "Attack Time"
+  </source>
+  <dest>
+    *: none
+    swcodec: "ÄŚas ZaÄŤiatku"
+  </dest>
+  <voice>
+    *: none
+    swcodec: "ÄŚas ZaÄŤiatku"
+  </voice>
+</phrase>
+<phrase>
+  id: LANG_FILTER_SHARP
+  desc: in sound settings
+  user: core
+  <source>
+    *: "Sharp"
+  </source>
+  <dest>
+    *: "Výrazný"
+  </dest>
+  <voice>
+    *: "Výrazný"
+  </voice>
+</phrase>
+<phrase>
+  id: LANG_FILTER_SLOW
+  desc: in sound settings
+  user: core
+  <source>
+    *: "Slow"
+  </source>
+  <dest>
+    *: "PomalĂ˝"
+  </dest>
+  <voice>
+    *: "PomalĂ˝"
+  </voice>
+</phrase>
Jonathan Gordon | 3 Jul 15:21 2014
Picon

Please help test gerrit#890

Hi all,

Over the last few days I've been working on redoing how the skin engine manages its buffers. My goal is to finally get rid of all the semi-random skin issues and this is the first step.


This patch adds some error handling and will also make any issues blow up in a more debug-able way (hopefully a data abort!).

This first version should work with all tags except the skinned lists (which hasn't seen much use anyway) but that will happen over the weekend.

A side benefit of this is a slightly smaller binary (seems to be about 5K smaller on the ipod video build).


Please let me know if you find any crashes - or even better if this fixes any crashes with your troublesome skins!

Thanks
Jonathan
Thomas Orgis | 19 Jun 08:19 2014

Extending the metronome plugin

Hi,

I would like to start a new attempt at improving the metronome plugin
in Rockbox. There are two main points:

1. Support config files with programmed songs (sequences of patterns
with different meters / tempi). I guess it would make sense to use the
"tempo map" format of http://das.nasophon.de/klick/ for this.

2. Have an optical mode, flashing the display (or parts of it) instead
of or in addition to playing a sound.

An Editor for these tempo maps inside the plugin would be bonus, but
for starters I would consider the maps coming from elsewhere. My
platform is a Sansa Clip+. My questions for the seasoned Rockbox devs
are these:

1. Is there an API call to get a file selection dialog or should the
plugin instead register as handler/codec for tempo map files to be started
from the main "files" menu? Excuse me for not finding that answer
myself, I didn't find an obvious place where API/plugin design is
documented. Pointers welcome, of course.

2. Is using the display as flashing indicator LED feasible? I guess it
should be for the Clip+, as it's just a little grid of OLEDs. But the
question would be if it can be done quickly in a timely manner to serve
as metronome (thinking of switching the whole upper or lower half for
opposing tick/tock). Since there is no background illumination, it
should be rather power conservative to have all black pixels most of
the time, right? And regarding the speed/latency: I remember running
Doom on that display, so that should technically work;-)

I'm a seasoned C developer (some might recognize me for maintaining
mpg123 over the last 8 years) and am confident to get the job done for
giving Rockbox an awesome metronome, once I got the starting points. I
did read the source of the existing metronome plugin and would start
from there.

Alrighty then,

Thomas
Marcin Bukat | 18 Jun 08:13 2014
Picon

Release

Hi rockboxers!

There have been long time since we did 3.13. We are in the state where first thing we advice when someone pops up with problem is to install development build. Moreover there are quarrels among devs comming from the fact that we are not in feature freeze but some think we should be. The only solution IMO is to do release outright. The commit rate is low and this are mostly fixes. Current builds seems to be in good shape. Having release would allow us to integrate quite invasive synopsys patch which would bring us back usb on nano2g and classic. Now the question comes - do we still have release manager (Alex?)

Marcin Bukat (wodz)
Marcin Bukat | 2 Apr 20:43 2014
Picon

DevCon2014

Hi chaps!

Last year we missed DevCon oportunity, it would be a pitty not to meet You again this year. I'd like to offer hosting of DevCon in Warsaw Poland. If You find it interesting we should start thinking about suitable date. Looking forward for feedback.

Marcin Bukat (wodz)
Richard Quirk | 23 Mar 18:30 2014
Picon

Updating Lua plugin to upstream 5.2.3

I've updated the Lua plugin code to use the upstream 5.2.3 release.
For comparison, the current code uses Lua 5.1.4.

It's quite a large change, though mostly due to changes in the core
Lua code. I've tried to minimise the differences between Lua upstream
and modifications for Rockbox, while also trying to keep churn between
what we had before and this new version to the strictly necessary.
http://gerrit.rockbox.org/774

I've tested this on a clip zip and in the simulator.

Regards,
Richard

Frank Gevaerts | 9 Feb 13:06 2014
Picon

Archos devices: time to let them rest?

Hi all,

When rockbox started about twelve years ago, the Archos Jukebox was
still a shiny new device, only slightly outclassed by the Recorder with
its wonderful bitmap display.

Rockbox pushed these devices far beyond what anyone could have imagined
when they were released.

Rockbox now runs on many more devices than these old Archoses, and with
each new device, new challenges and opportunities arose. We now support
colour screens, CPU decoding, touchscreens, and many features that were
inspired by new and more powerful hardware.

These newer devices are now vastly more popular than the Archoses, and
this combined with the Archoses being different in some important ways
(using a hardware codec, and for the Jukebox, using a character cell
display) has meant that during the last few years Rockbox for the
Archoses has not had the maintenance it really needs. This is e.g.
visible on the build page [1], where you can see that the build for the
Archos Recorder has been broken for more than a year, due to it (and
soon, probably, some of its siblings) really needing to move to a
different way of booting (a move the non-Archos ports made back when
they started).

The work needed to keep the Archos port alive is not impossible, but at
least for the past two years, nobody has stepped up. We don't even know
if anyone still has one of these devices in active use.

I think it's now time to let the Archos port rest. Without it, rockbox
would not have existed, but the way we treat it currently is not what it
deserves. We don't want people to Rockbox on the Archoses as an
annoyance that keeps breaking the build.

Let us try to remember Rockbox on the Archos in its glory days, when it
showed the world what a digital audio player could really do.

I propose we let 3.13 be the last rockbox release that supports the old
Archos devices, and that we won't try to force them into the 3.14
release again.

I also propose we stop auto-building the Archos ports right away, and
that we consider any HWCODEC or CHARCELL code to be available for
cleanup after 3.14 has been released (such cleanup can destabilise the
code, and we want 3.14 out soon)

Thoughts?

Frank

[1] http://build.rockbox.org/dev.cgi

--

-- 
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan


Gmane