--- Log for 14.11.109 Server: lindbohm.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 12 days and 16 hours ago 00.04.22 Quit BHSPitMonkey (Read error: 113 (No route to host)) 00.12.01 Quit dmb (Read error: 104 (Connection reset by peer)) 00.16.15 Join dfkt_ [0] (n=dfkt@unaffiliated/dfkt) 00.19.45 Nick fxb__ is now known as fxb (n=felixbru@h1252615.stratoserver.net) 00.21.10 Join JdGordon1 [0] (n=jonno@c-24-22-210-83.hsd1.wa.comcast.net) 00.21.32 Quit dfkt (Nick collision from services.) 00.21.37 Nick dfkt_ is now known as dfkt (n=dfkt@unaffiliated/dfkt) 00.21.55 Quit JdGordon1 (Client Quit) 00.23.09 Quit Horscht ("Verlassend") 00.23.45 Join GeekShadow [0] (n=Antoine@reactos/tester/GeekShadow) 00.33.03 Join Horscht [0] (n=Horscht2@xbmc/user/horscht) 00.39.44 Join xilinx [0] (n=chatzill@88.244.42.60) 00.40.30 Join AleMaxx_ [0] (n=enforcer@f053011211.adsl.alicedsl.de) 00.40.44 Quit AleMaxx (Read error: 110 (Connection timed out)) 00.41.18 Quit AleMaxx_ (Client Quit) 00.42.23 Quit domonoky1 (Read error: 104 (Connection reset by peer)) 00.50.31 Quit bertrik ("De groeten") 00.51.28 Quit dfkt (Read error: 110 (Connection timed out)) 01.09.23 Quit ender` (" I just found out what Alt+F4 does.") 01.11.14 Quit amiconn (Nick collision from services.) 01.11.16 Join amiconn_ [0] (i=quassel@rockbox/developer/amiconn) 01.11.26 Join pixelma_ [0] (i=quassel@rockbox/staff/pixelma) 01.11.26 Quit pixelma (Nick collision from services.) 01.11.36 Nick amiconn_ is now known as amiconn (i=quassel@rockbox/developer/amiconn) 01.11.47 Nick pixelma_ is now known as pixelma (i=quassel@rockbox/staff/pixelma) 01.14.25 *** Saving seen data "./dancer.seen" 01.20.23 Join AEnima1577 [0] (n=clbarnob@nc65211f9.cns.vt.edu) 01.21.40 Join Lynx0 [0] (n=Lynx@xdsl-78-34-223-252.netcologne.de) 01.28.41 Quit Lynx_ (Read error: 145 (Connection timed out)) 01.28.42 Nick Lynx0 is now known as Lynx_ (n=Lynx@xdsl-78-34-223-252.netcologne.de) 01.29.01 Join angerrsdfdsft [0] (n=60f88772@giant.haxx.se) 01.29.34 # is there a way to install rockbox on sansa in msc mode 01.30.40 # angerrsdfdsft, that is the only way to install rockbox 01.31.47 Join BHSPitLappy [0] (n=BHSPitLa@unaffiliated/bhspitmonkey) 01.33.55 # i mean mtp 01.34.33 # nope.. it has to be in msc mode 01.39.57 # how to fix a brick sansa 01.40.44 Quit Tomis (Read error: 104 (Connection reset by peer)) 01.40.45 Join Tomis2 [0] (n=Tomis@70.134.101.218) 01.48.10 Part toffe82 01.49.10 Quit angerrsdfdsft ("CGI:IRC (Ping timeout)") 01.50.36 Quit xilinx ("ChatZilla 0.9.85 [Firefox 3.5.5/20091102152451]") 01.50.50 Quit Lynx_ (" HydraIRC -> http://www.hydrairc.com <- Wibbly Wobbly IRC") 01.54.20 Join togetic [0] (n=togetic@unaffiliated/ibuffy) 02.00.16 Quit Galois (Read error: 113 (No route to host)) 02.09.50 Join Galois [0] (i=djao@efnet.math.uwaterloo.ca) 02.10.56 Join Strife89 [0] (n=michael@adsl-81-160-3.mcn.bellsouth.net) 02.16.34 Quit linuxstb (Read error: 113 (No route to host)) 02.23.42 Join ExcruciationX [0] (n=User@c-98-247-171-214.hsd1.wa.comcast.net) 02.24.16 Part ExcruciationX ("Leaving") 02.29.48 Nick fxb is now known as fxb__ (n=felixbru@h1252615.stratoserver.net) 03.13.48 Join midgey [0] (n=tjross@rockbox/developer/midgey) 03.14.28 *** Saving seen data "./dancer.seen" 03.24.46 Join BlakeJohnson861 [0] (n=bjohnson@c-24-118-162-123.hsd1.mn.comcast.net) 03.26.08 Quit BlakeJohnson86 (Read error: 110 (Connection timed out)) 03.44.59 Quit mc2739 ("leaving") 03.51.24 Quit GeekShadow (Read error: 104 (Connection reset by peer)) 03.51.39 Join mc2739 [0] (n=mc2739@rockbox/developer/mc2739) 03.56.12 Join T44 [0] (n=Topy44@f049037238.adsl.alicedsl.de) 03.56.13 Quit killan (Read error: 54 (Connection reset by peer)) 04.08.28 Quit Rondom (Nick collision from services.) 04.08.38 Join Rondom [0] (n=Rondom@dslb-084-057-143-080.pools.arcor-ip.net) 04.13.46 Quit Topy44 (Read error: 110 (Connection timed out)) 04.14.06 Quit LambdaCalculus37 ("Leaving") 04.14.38 Join wincent [0] (n=wincent@g228142151.adsl.alicedsl.de) 04.19.37 Quit Rob2223 () 04.25.40 Part wincent ("Kopete 0.12.7 : http://kopete.kde.org") 04.26.30 Join Rob2222 [0] (n=Miranda@p4FDCC9B9.dip.t-dialin.net) 04.40.09 Quit AEnima1577 ("Leaving.") 04.43.09 Join Zorda_ [0] (n=hi@c-71-62-228-21.hsd1.va.comcast.net) 04.56.05 Quit Zorda (Read error: 110 (Connection timed out)) 04.57.14 Join gtkspert_ [0] (n=gtkspert@124-169-252-223.dyn.iinet.net.au) 05.05.37 Quit gitster` (Read error: 145 (Connection timed out)) 05.12.35 Quit gtkspert (Read error: 101 (Network is unreachable)) 05.14.32 *** Saving seen data "./dancer.seen" 05.23.40 Join shai [0] (n=Shai@l192-117-110-233.cable.actcom.net.il) 05.33.52 Join AndyIL [0] (n=pasha_in@212.14.205.32) 05.37.21 Quit MethoS- (Remote closed the connection) 05.38.55 Join Tomis [0] (n=Tomis@70.134.87.220) 05.40.33 # i failed @ maths. we can't do 9 levels of blending with SWAR, this will require 7 free bits between components. 5 will work fine, though. 05.45.28 Quit AndyI (Read error: 110 (Connection timed out)) 05.45.41 Quit Strife89 ("Bed.") 05.48.15 Quit ps-auxw (Read error: 110 (Connection timed out)) 05.56.05 Quit Tomis2 (Read error: 110 (Connection timed out)) 06.20.11 Join AEnima1577 [0] (n=clbarnob@c-98-249-3-190.hsd1.va.comcast.net) 06.36.46 Quit martian67 (Client Quit) 06.47.32 Join Tomis2 [0] (n=Tomis@70.134.66.51) 06.49.13 Quit Tomis (Read error: 104 (Connection reset by peer)) 06.52.32 Quit gevaerts (Nick collision from services.) 06.52.44 Join gevaerts [0] (n=fg@rockbox/developer/gevaerts) 07.04.58 Quit Tomis2 (Read error: 110 (Connection timed out)) 07.14.36 *** Saving seen data "./dancer.seen" 07.19.41 Join Tomis [0] (n=Tomis@70.134.72.134) 07.26.27 Quit phanboy4 (Read error: 60 (Operation timed out)) 07.39.10 Join Horschti [0] (n=Horscht2@p4FD4E06A.dip.t-dialin.net) 07.41.44 Quit AEnima1577 ("Leaving.") 07.42.59 Join AEnima1577 [0] (n=clbarnob@c-98-249-3-190.hsd1.va.comcast.net) 07.46.25 Quit Horscht (Read error: 60 (Operation timed out)) 08.04.11 Join Rob2223 [0] (n=Miranda@p4FDCD1C5.dip.t-dialin.net) 08.21.51 Quit Rob2222 (Connection timed out) 08.22.18 Join Bagder_ [0] (n=daniel@static-93.158.79.102.got.public.icomera.com) 08.26.31 Join robin0800 [0] (n=quassel@general-ld-216.t-mobile.co.uk) 08.41.46 Join jus__ [0] (n=julian@lns-bzn-48f-81-56-223-53.adsl.proxad.net) 08.41.55 Quit jus__ (Read error: 54 (Connection reset by peer)) 08.46.49 # kugel, amiconn: another subpixel-aa font test, now with black-on-white or white-on-black: http://www.looking-glass.us/~chshrcat/rockbox/aafonttest2.png 08.50.25 # the AA'd samples are two different methods for reducing the 256-level glyphs down to 4 levels. the 4-level values are then mapped to a 5-level range, so that after mixing colors division can be done with a right-shift. i think the second sample, which favors full-on or full-off a bit more, looks slightly better... either is nice enough that i think i'll get to work on trying to actually do this in RB ;) 08.52.15 Join stoffel [0] (n=quassel@87.180.236.161) 08.52.43 Join Grahack [0] (n=chri@LCaen-151-91-3-232.w193-251.abo.wanadoo.fr) 08.56.09 Join flydutch [0] (n=flydutch@host119-166-dynamic.8-87-r.retail.telecomitalia.it) 08.58.05 Join FOAD_ [0] (n=dok@dinah.blub.net) 09.06.05 Quit FOAD (Read error: 145 (Connection timed out)) 09.06.06 Nick FOAD_ is now known as FOAD (n=dok@dinah.blub.net) 09.14.37 *** Saving seen data "./dancer.seen" 09.17.14 Quit Grahack ("Leaving.") 09.24.47 Join bmbl [0] (n=Miranda@unaffiliated/bmbl) 09.29.57 Join n1s [0] (n=n1s@rockbox/developer/n1s) 09.33.51 Join linuxstb [0] (n=linuxstb@rockbox/developer/linuxstb) 09.35.39 Join stoffel_ [0] (n=quassel@p57B4DE70.dip.t-dialin.net) 09.35.59 Quit Rob2223 () 09.38.47 Quit stoffel (Read error: 145 (Connection timed out)) 09.38.54 Join dmb [0] (n=Dmb@unaffiliated/dmb) 09.40.22 Join bertrik [0] (n=bertrik@ip117-49-211-87.adsl2.static.versatel.nl) 09.43.20 # I want to help with translations... but is it me, or does this look like a very length process? 09.44.04 # well, you need to provide translations for a fair amount of phrases. that can be lengthy, yes 09.44.08 # how else would it work? 09.46.33 # Well... I do Gallery2 translations and its been setup in such a way, that translating is just as easy as going to Setting -> Start Translation (approx.) and it'll show you English text on the left, and a space on the right to translate. You put in the word/sentence/code on the right, and click save (or was it update?). 09.47.38 # shai: I think rasher's translation page could be a great help for you then (basically a web frontend). Which languag do you want to help translating? 09.47.53 # Hebrew 09.48.39 # I found lots of English text that needs translating and other Hebrew words that don't really say the correct meaning in the context of which they were meant for 09.49.02 # http://rasher.dk/rockbox/translate/?cmd=edit&lang=hebrew 09.49.26 # I saw that page... and just noticed that link to Rasher's page 09.49.52 # As for the "Translations status" saying 0 0 0 for Hebrew, that's way outdated... like it says "As of 26 Aug 2008" 09.50.55 # http://rasher.dk/rockbox/translate/ says "4 months ago" for hebrew 09.51.09 # AFAIK there has been recent hebrew translation activity by tomers 09.51.55 # Yea, tomers and I know each other... small country. 09.51.58 # October 24th 2009 was the last hebrew update 09.52.20 # s/country/state/ 09.52.48 # 0 0 0 for Hebrew is from the wiki and that page isn't updated automatically, someone has to do it manually (and didn't for a while) 09.53.19 # Indeed. 09.53.49 # I think that even the status table on rasher's site is a bit outdated (or I missed something) 09.54.54 # How much text do you guys think I'll find to be hard-coded and untranslatable? 09.55.41 # not very much 09.55.50 # we have been translating rockbox for years 09.56.24 # And if I do find and report it... would it get fixed quickly (in a reasonable time frame)? 09.57.31 # I love QA ... don't get me wrong ... and tomers knows me and how much I do .. but if there is something I don't like in QA, is pushing on the gas in nutral. 09.58.00 # neutral* 09.58.31 # reported bugs are fixed by people that decide they want to fix them, when that happens is anyone's guess 09.59.41 # we have MANY open bugs 09.59.43 Join Rob2222 [0] (n=Miranda@p4FDCD1C5.dip.t-dialin.net) 10.01.14 # there's a fair bit in plugins, isn't there? 10.01.48 # I'm sure, I haven't really looked that closely lately 10.02.05 # * Bagder_ is circling the project at high altitude 10.02.18 # sure, and that can't be translated yet 10.02.25 # ah yes 10.02.27 # * pixelma looks around for midgey 10.06.09 # with 2-bit subpixels, glyph data should cost 6b/pixel... i could pack 5 per word and just waste the other 2, or i could just pack 2-bit subpixels 16 to a word. i think the wasted 2 bits is probably fine if dealing with whole pixels not being word-aligned would hurt performance? 10.07.13 # Unhelpful: a lot of our open bugs are also hardware specific or hard to reproduce 10.07.41 # we've had some success with tracker cleanup weeks in the past but the mod 10.07.56 # i am trying to debug why rockbox freezes on my nano 2g when i connect an usb cable, it seems like the problem isnt in the usb thread, it seems there is another thread locking up and stopping all other threads from working, how could i debug this? 10.07.58 # s/mod/most recent attempts have not done so much/ 10.09.01 Quit stoffel_ (Read error: 113 (No route to host)) 10.09.53 # every time it's suggested i go look for bugs, i find ones specific to platforms i don't have, or buried deep in code i don't know. somehow i doubt i'm the only developer, especially among the newer crop, who has found this a problem. :/ 10.11.51 # ns1, I do suppose I could always bug tomers to push in my fixes ;) 10.12.06 # Or rather fix requests ... 10.13.26 # should this *really* be a bug at all? http://www.rockbox.org/tracker/task/10694?project=1&type=2&order=dateopened&sort=desc 10.19.12 # couldn't we very easily set default foreground/background colors and a solid-fg-on-solid-bg drawmode to fix this? it's not like anything will care what the state of the gfx engine is after the panic is "done". http://www.rockbox.org/tracker/task/10665 10.19.50 Quit robin0800 (Remote closed the connection) 10.21.38 # Unhelpful: you mean 10665? 10.21.49 # ah, right 10.22.16 # 10665 sound seasy 10.22.48 # the hard part is making it panic ;) 10.29.05 # can anyone with an e200 confirm 10381? 10.30.42 # it already sets colors, actually :) 10.31.49 # so add a lcd_set_drawmode(DRMODE_SOLID)? 10.35.26 # who knows stuff sbout the fonts around here? 10.36.11 # i've learned a *bit* working on aa-fonts. i might be able to help... 10.36.20 # FS#9906 seems like a simple fix for a font error but i have nfi about those things 10.37.16 # hrm, it looks like panicf disables backdrop, clears the screen, then sets foreground and background colors. it still might be worth adding a lcd_set_drawmode to make sure it's not in DRMODE_INVERVSEVID, but i'd say it looks like this bug is already dead. 10.38.06 Quit dmb ("Leaving") 10.38.36 # There are actually two functions to consider: panicf() and UIE() 10.39.01 # 10665 looks like an UIE() example 10.40.41 # so UIE should do all of the same setup as panicf, essentially? 10.41.22 # is there a reason it doesn't just use panicf? 10.52.15 # UIE() needs to be as self contained as possible 10.53.05 # Things have already gone very wrong when it gets called. The CPU might even be in a mode where not all memory is reachable 10.53.08 Quit elcan (Remote closed the connection) 10.54.44 Join ender` [0] (i=krneki@foo.eternallybored.org) 10.55.07 # ah. so it might be a bad idea to go doing more in the way of graphics? 10.55.43 # it still does lcd_clear_display, though, at least on ARM... that can hardly be *less* likely to work than setting the colors and drawmode 10.56.34 # maybe clearing the backdrop, as I understood it this is the main problem 10.58.02 # Who does documentation updates? I noticed that the iPOD Video (5th Gen) has a current screen capture of The Playlist Submenu ... but still talks about non-existing features such as Insert Last Shuffled and Queue Last Shuffled. 10.58.12 # The PDF version. 10.58.40 Join elcan [0] (i=user36@pr0.us) 10.58.52 # non-existent features? You mean on the screenshot? 10.59.10 # I don't see them on the screen shot nor on my iPOD Video. 10.59.25 # Let me double check myself. 10.59.59 # Ack. Yes. 11.00.19 # pixelma: the report claims text over WPS, so i'm guessing that the backdrop clear was added after this report. clearing the display is probably fine, but it should, as panicf does, also set colors, and disable backdrop 11.00.20 # Those two don't exist in the screen capture nor on my iPOD. 11.00.48 # and maybe add setting the drawmode to DRMODE_SOLID to both UIE and panicf 11.01.04 Join teru [0] (n=teru@ZQ174123.ppp.dion.ne.jp) 11.01.30 # shai: when did you last update your build? Those were added fairly recently and the manual is updated daily 11.01.44 # Today (approx. 1 hour ago). 11.02.11 # I installed the Current Build using the Rockbox Utility. 11.02.14 # As I always do ... 11.02.19 # shai: are you selecting playlist file? 11.02.24 Join Tomers [0] (n=chatzill@bzq-84-109-85-100.red.bezeqint.net) 11.02.29 # No. an MP3. 11.02.32 # Tomers, Morning :) 11.02.58 # morning :-) 11.03.19 # Actually... noon ... 11.05.47 # IIUC, they are only shown when folder or pleylist file is selected. 11.05.48 Quit Bagder_ ("It is time to say moo") 11.06.29 # I selected neither... 11.06.37 # doesn't make much sense for a single file 11.06.40 # shai: Just port your new translation at FlySpray, and me or anyone else will commit, if appropriate. 11.07.02 # I would love to have feedback on Hebrew translations, and will commit promptly. 11.07.24 # Did you read the chat history? 11.07.47 Join Zarggg_ [0] (n=zarggg@65-78-69-194.c3-0.eas-ubr6.atw-eas.pa.cable.rcn.com) 11.08.06 Quit elcan (Remote closed the connection) 11.08.31 # shai: Also, working on manual stuff is highly appreciated. If you notice some screenshot changes, upload them to FS, hopefully with the same file name as used in the manual (why don't you pull RB code through SVN using TortoiseSVN in Windows)? 11.08.38 # pixelma, Understood. It does appear when selecting a folder (didn't try a playlist but I assume its the same). 11.08.38 # shai: Yes 11.09.22 # Tomers, So does your answer refelect the question about hard-coded text too? 11.09.24 Join Grahack [0] (n=chri@LCaen-151-91-3-232.w193-251.abo.wanadoo.fr) 11.09.26 # I thought TortoiseSVN can be troublesome 11.09.42 # it can 11.10.03 # pixelma: 'read-only' mode - not for commit. 11.10.03 # I personally don't like Windows for this... I'd rather use my Linux box for it... 11.10.08 # something with the whole line ending mess 11.10.41 # shai: It will be much better to handle this in Linux. Windows is hell for this purpose - I just assumed you are using only Windows 11.11.04 # Tomers: I also read about people not able to compile with a TortoiseSVN setup, commit or not 11.11.14 # Tomers, and for my question on hard-codec text ... ? 11.11.30 # shai: Lately you've complained about having non-translatable string in WPS ("Next Song:", etc.). Why not bringing it up now? I don't know what are the technical barriers preventing this from being implemented, so we should ask 11.11.49 # Indeed! 11.12.05 # So, its on the table... 11.12.16 # pixelma: Good to know. Thanks. I gave up compiling rbutil in Windows, but maybe this is not related to the fact I fetched the code in TortoiseSVN 11.13.12 # Tomers, I'm not 100% sure how much nor which text is really hard-codec ... but maybe you can fill in that gap. 11.13.25 # * gevaerts points Tomers and shai to r22837 11.13.34 Join elcan [0] (i=user36@pr0.us) 11.13.42 # shai: Also, we should push the issue of having Hebrew characters being part of some common fonts in RB, such as 12-Adobe-Helvetica, which is the default font on many targets 11.13.45 # * shai goes to find the URL to add r22837 to ... 11.14.28 # Tomers, Agreed... that's on the table too ... having the need to update two placed before you can read Hebrew is a drag. 11.14.28 # shai: Regarding Hebrew in fonts, refer to http://rasher.dk/rockbox/fontstats/ 11.14.41 *** Saving seen data "./dancer.seen" 11.14.53 # shai: I think rasher is the address regarding fonts (gevaerts: am I right?) 11.15.05 # Tomers: he does stats 11.15.20 # I don't know if he also does fonts as such 11.15.50 # Hebrew is way behind... 11.15.52 # Shai: http://svn.rockbox.org/viewvc.cgi?view=rev;revision=22837 11.16.03 # Tomers, 10x 11.16.32 # shai: Actually, I think Hebrew is in good condition. At least it is highly usable after some configuration (font, default codepage) 11.17.02 # The Log Message in that rev. is way to technical for me... 11.17.12 # Unless you have critics on the quality of translation :-) I tried to translate as much as I could, but still tried to avoid over-translation 11.17.29 # of technical terms that have no proper translations 11.18.13 # I saw a word there... that I would never put in Hebrew unless I really knew what I was doing ;) 11.18.26 # That word, is the main reason I'm here today. 11.18.39 # shai: I guess you mean גאייה which is the translation of fade-in ? 11.18.41 # But I'm up to an hour and still trying to get my head around the idea ... 11.18.47 # Nope. 11.18.58 # גומר actually... 11.19.11 # It should have been מסיים 11.20.21 # And in that context... it should have really been מעדכן 11.21.12 # Because you don't really know if its finishing the job... so the English original should also be altered (IMHO). 11.22.23 # shai: Bring the full string (english) here and ask people around - maybe they agree with you about changing this string. I'll fix the Hebrew translation 11.23.04 # gevaerts: Could you please save me some energy and briefly explain how can I use r22837 to translate, e.g. "Next Song:" ? AFAIU, what is needed to be done is changing the Cabbie theme to have that new tag instead of hard-coded string, then adding the translation in hebrew.lang? 11.23.58 # Tomers: I'd have to go and figure it out myself. I know it's there, but that's about it. 11.24.17 # gevaerts: OK. I'll dig it up myself. Thanks 11.24.36 # Not for a new topic 11.24.39 Quit Zarggg (Read error: 110 (Connection timed out)) 11.24.41 # Tomers, Is this the full translation page? http://rasher.dk/rockbox/translate/?cmd=edit&lang=hebrew 11.24.52 # s/Not/Now/ 11.24.53 # Tomers: if you have questions about it, try to catch JdGordon 11.25.04 # thanks 11.25.58 # it currently uses strings in Rockbox that are already there (for use in menus etc.), I would not want to add strings to the language file just for a WPS, not sure if the default one should be an exception. I'm just a bit afraid that this will blow up the language files 11.27.17 # pixelma, was that meant to me? 11.27.40 # no, Tomers 11.28.12 # I think it would be useful to have rbutil 'implement' some default setting depending on the language it uses. E.g. if rbutil is used on a computer where Hebrew is set as default language, and thus uses Hebrew GUI, it should install Rockbox on the DAP and (optionally ask the user for confirmation) set the DAP's language to Hebrew, and set some more related configurations, such as setting... 11.28.14 # ...default codepage to Hebrew (I found Unicode to be somewhat unusable here, as most ID3 tags are non-Unicode, but that's another story). Also might set 12H/24H clock according to the OS setting where rbutil is running on, etc. What do you guys think? 11.30.01 # pixelma: I'm +1 for having translation for default theme. But I will understand the reasons why this might be wise. Does the mechanism that will be used to translate plugins could be used for translating themes? 11.30.54 # * gevaerts thinks that a set of common phrases should be acceptable 11.31.01 # I don't know, it hasn't been committed 11.32.01 # pixelma: What hasn't been committed? 11.32.41 # the plugin translation system 11.34.17 # pixelma: I now it hasn't. But could it be used to translate themes also? When it will be committed, of course? 11.36.07 Quit AlexP (Remote closed the connection) 11.36.14 # shai: I can't find that badly translated sting anywhere (גומר) 11.36.17 Join AlexP [0] (n=alex@rockbox/staff/AlexP) 11.38.58 Join flai [0] (n=mafia@athedsl-344541.home.otenet.gr) 11.40.14 Quit flai ("NiRvAnAiR.irc.grthales.irc.gr") 11.41.13 Quit Tomers ("ChatZilla 0.9.85 [Firefox 3.5.5/20091102152451]") 11.41.32 Join tomers [0] (n=chatzill@bzq-84-109-85-100.red.bezeqint.net) 11.43.05 # how does this look? http://pastie.org/698493 11.47.10 Join domonoky [0] (n=Domonoky@rockbox/developer/domonoky) 11.51.11 # * Unhelpful *thinks* he sees a way to implement partitioned multiply-accumulate, provided the multipliers are *very* small... but probably 3 mac instructions is cheaper than 8 adds + 4 ands, plus setup? 11.51.29 # Unhelpful: I don't think clearing the backdrop or setting the drawmode in UIE() would be a problem 11.51.31 Quit AaronM (Read error: 60 (Operation timed out)) 11.51.40 # Just that UIE() shouldn 11.52.27 # 't call potentially complex functions without reason, because it increases the chance that it breaks 11.54.42 # amiconn: and clearing the backdrop is fairly simple, so that should be ok, it's just things like calling into panicf that we want to avoid? 11.56.05 Quit Grahack ("Leaving.") 12.03.39 # shai: http://forums.rockbox.org/index.php?topic=23160.0 12.08.36 # hmm, why are we ifdefing for HAVE_LCD_BITMAP in syste 12.08.49 # m-foo (where foo != sh)? 12.09.32 # n1s: in case things ever change? i can remove that if you like :) 12.10.24 Join stoffel [0] (n=quassel@p57B4DE70.dip.t-dialin.net) 12.13.59 # shai: http://forums.rockbox.org/index.php?topic=23161.0 12.14.01 Quit BHSPitLappy (Read error: 60 (Operation timed out)) 12.16.34 # Unhelpful: less useless #ifdefsa are good imho :) 12.17.41 # fine, i'll nuke those and commit, it compiles on every color or greyscale arm or coldfire, and on charcell or bitmap sh :) 12.18.00 # I'm not sure... 12.18.19 # are there mono targets aside from sh? 12.18.28 # yes 12.18.31 # the M:Robe100 12.18.48 # please don't go too far with this... 12.18.49 # And the Clip 12.18.53 # and m200 (port in progress) 12.19.12 # and DAX 12.19.25 # with what? 12.19.50 # removing support for screen types that happen not to be used right now 12.21.16 # that's a vote for leaving the extra #ifdef? 12.22.03 # Unhelpful: logik dax, it has some code in svn 12.22.26 # AlexP: sloow 12.22.51 # I would leave them in, athough I wouldn't complain about the charcell-on-non-sh ones 12.23.03 # pixelma: no, I just misread 12.23.33 # pixelma: when gevaerts said DAX I thought he replied asking what it was 12.23.34 # * Unhelpful will remove just those, then :P 12.27.43 # New commit by 03unhelpful (r23623): Set DRMODE_SOLID, uniform colors, and sysfont before clearing LCD to display panic or exception messages - see FS#10665. 12.31.22 Join kugel [0] (n=kugel@rockbox/developer/kugel) 12.37.17 # New commit by 03unhelpful (r23624): Fix dangling #endif 12.39.59 Quit yosafbridge ("Coyote finally caught me") 12.40.10 Join yosafbridge [0] (n=yosafbri@li14-39.members.linode.com) 12.45.08 # Unhelpful: I saw you're going to work on subpixel anti-aliasing? 12.45.11 # awesome :) 12.45.25 Quit tomers (Read error: 113 (No route to host)) 12.50.12 # care to look at one of those funny scrolling-lines-keep-scrolling-after-exiting-screen bugs? 12.51.40 # eh that was to kugel, iirc you fixed some of them? 12.51.54 Join kugel_ [0] (n=kugel@e178073226.adsl.alicedsl.de) 12.52.04 Quit kugel (Nick collision from services.) 12.52.10 Nick kugel_ is now known as kugel (n=kugel@e178073226.adsl.alicedsl.de) 12.58.07 Join stoffel_ [0] (n=quassel@p57B4D35C.dip.t-dialin.net) 12.59.11 Join Grahack [0] (n=chri@ip-222.net-82-216-222.rev.numericable.fr) 12.59.36 Quit kugel (Nick collision from services.) 12.59.41 Join kugel [0] (n=kugel@e178082175.adsl.alicedsl.de) 13.01.21 Quit stoffel (Read error: 110 (Connection timed out)) 13.02.05 Quit kugel (Remote closed the connection) 13.06.34 # OMG, we have both "lcd_scroll_stop" and "lcd_stop_scroll" functions 13.06.48 # haha 13.11.46 Ctcp Ping from gevaerts!n=fg@rockbox/developer/gevaerts 13.11.46 Ctcp Ping from gevaerts!n=fg@rockbox/developer/gevaerts 13.14.44 *** Saving seen data "./dancer.seen" 13.19.25 Join bimbel [0] (n=Miranda@unaffiliated/bmbl) 13.27.27 Quit bmbl (Connection timed out) 13.29.07 # yay i fixed the bug but have no idea if it's correct at all 13.38.25 # JdGordon: ping? 13.43.04 Quit Bob_C_ ("ChatZilla 0.9.85 [Firefox 3.5.4/20091016092926]") 13.50.53 # if anyone who understands this gui/scrolling code reads the logs i posted a patch that fixes the bugs i fs#10616 but i'm not sure it's correct (it even feels wrong) so i'd be happy if someone else took a look at it 13.51.28 # s/i fs/in fs/ 13.52.30 Join Omlet [0] (i=omlet05@81.241.145.38) 13.56.56 # there is also the bug that scrolling lines keep scrolling and on screen if you enter the USB screen (I believe there was a similar bug with the FM screen once, not sure how it was fixed but it was) 14.04.37 Join dfkt [0] (i=dfkt@unaffiliated/dfkt) 14.07.51 Join MethoS- [0] (n=clemens@134.102.106.250) 14.13.51 Join kugel [0] (n=kugel@rockbox/developer/kugel) 14.14.21 # n1s: heh, welcome in to the scrolling confusion :) 14.14.23 Join einhirn [0] (n=Miranda@p5DCC127E.dip0.t-ipconnect.de) 14.14.59 # stop_scroll() stops all scrolling. that should be avoided since it also stops scrolling in unrelated parts (read: custom statusbar) 14.15.04 Join ps-auxw [0] (n=arneb@dyn37.ps-auxw.de) 14.15.55 # scroll_stop() only stops scrollingin the viewport you pass. However, that must be the same viewport that was used for set_viewport() before putting the text 14.16.53 # kugel: one of those should really be renamed 14.18.09 Quit einhirn (Read error: 104 (Connection reset by peer)) 14.18.26 # kugel: did you look at the patch? the thing i think is wrong with it is that i would think the menu drawing code should handle stopping scrolling lines 14.22.22 Join bughunter21 [0] (n=bughunte@ip4da4427e.direct-adsl.nl) 14.22.22 Quit bughunter2 (Nick collision from services.) 14.22.35 Nick bughunter21 is now known as bughunter2 (n=bughunte@ip4da4427e.direct-adsl.nl) 14.24.25 Join DerPapst [0] (n=DerPapst@p4FE8EB0D.dip.t-dialin.net) 14.26.39 Join bughunter21 [0] (n=bughunte@ip4da4427e.direct-adsl.nl) 14.26.39 Quit bughunter2 (Nick collision from services.) 14.26.50 Nick bughunter21 is now known as bughunter2 (n=bughunte@ip4da4427e.direct-adsl.nl) 14.33.15 Quit MethoS- (Remote closed the connection) 14.41.55 Join killan [0] (n=nnscript@c-94fc70d5.06-397-67626721.cust.bredbandsbolaget.se) 14.42.01 Quit AEnima1577 ("Leaving.") 14.44.31 Nick bimbel is now known as bmbl (n=Miranda@unaffiliated/bmbl) 14.45.51 Quit midgey (Read error: 60 (Operation timed out)) 14.47.29 Join fdinel [0] (n=Miranda@modemcable235.127-131-66.mc.videotron.ca) 14.47.46 Join GeekShadow [0] (n=Antoine@reactos/tester/GeekShadow) 15.05.08 Join dfkt_ [0] (i=dfkt@unaffiliated/dfkt) 15.05.58 Quit stoffel_ (Remote closed the connection) 15.07.34 Quit Omlet ("( www.nnscript.com :: NoNameScript 4.22 :: www.esnation.com )") 15.14.47 *** Saving seen data "./dancer.seen" 15.20.53 Join midgey [0] (n=tjross@c-71-238-148-140.hsd1.mi.comcast.net) 15.23.10 Quit dfkt (Read error: 110 (Connection timed out)) 15.29.14 Join kugel_ [0] (n=kugel@e178119016.adsl.alicedsl.de) 15.29.28 Quit kugel (Nick collision from services.) 15.29.36 Nick kugel_ is now known as kugel (n=kugel@e178119016.adsl.alicedsl.de) 15.32.58 # Can I have the iPOD connected to the PC on one hand via USB so I can manipulate the files there (copy music on and off) while at the same time have it available to play my music? 15.36.55 Join dfkt [0] (i=dfkt@chello062178002170.1.11.univie.teleweb.at) 15.36.59 # no 15.39.06 Quit Grahack ("Leaving.") 15.41.35 Join kugel_ [0] (n=kugel@e178069115.adsl.alicedsl.de) 15.41.47 Quit kugel (Nick collision from services.) 15.41.55 Nick kugel_ is now known as kugel (n=kugel@e178069115.adsl.alicedsl.de) 15.43.34 Quit antil33t (Read error: 54 (Connection reset by peer)) 15.43.39 Join antil33t [0] (n=Mudkips@203-184-54-232.callplus.net.nz) 15.44.36 Quit kugel (Nick collision from services.) 15.44.42 Join kugel [0] (n=kugel@e178073077.adsl.alicedsl.de) 15.47.00 Quit fdinel (Read error: 110 (Connection timed out)) 15.47.24 # AlexP, too bad ... 15.47.32 Join mcuelenaere [0] (n=mcuelena@78-21-191-122.access.telenet.be) 15.52.18 Join Bob_C [0] (n=chatzill@host86-142-212-198.range86-142.btcentralplus.com) 15.52.22 Join funman [0] (n=fun@rockbox/developer/funman) 15.55.17 Quit dfkt_ (Read error: 110 (Connection timed out)) 15.56.05 Quit kugel (Nick collision from services.) 15.56.11 Join kugel [0] (n=kugel@e178085141.adsl.alicedsl.de) 15.58.54 Join Bagder_ [0] (i=daniel@dhcp-47-26.nomad.chalmers.se) 16.00.30 Quit kugel (Nick collision from services.) 16.00.36 Join kugel [0] (n=kugel@e178089219.adsl.alicedsl.de) 16.01.55 Quit kugel (Nick collision from services.) 16.02.01 Join kugel [0] (n=kugel@e178091210.adsl.alicedsl.de) 16.23.37 Quit teru ("Quit") 16.28.06 Join einhirn [0] (n=Miranda@p5DCC127E.dip0.t-ipconnect.de) 16.32.24 Quit DerPapst ("Leaving.") 16.35.43 Quit bughunter2 ("Leaving.") 16.37.15 Join Highlander [0] (n=Highland@mek33-4-82-236-45-205.fbx.proxad.net) 16.40.01 Quit kugel (Read error: 110 (Connection timed out)) 16.49.14 Join Omlet [0] (i=omlet05@38.145-241-81.adsl-dyn.isp.belgacom.be) 16.49.20 Quit Omlet (Remote closed the connection) 17.01.27 Quit Bagder_ (Remote closed the connection) 17.14.51 *** Saving seen data "./dancer.seen" 17.18.27 Quit einhirn (Read error: 104 (Connection reset by peer)) 17.19.06 Join kugel [0] (n=kugel@e178120250.adsl.alicedsl.de) 17.27.27 Join DerPapst [0] (n=DerPapst@p4FE8EB0D.dip.t-dialin.net) 17.30.50 Join Crunchie [0] (n=quassel@91-113-68-175.adsl.highway.telekom.at) 17.32.30 Join Strife89 [0] (n=Strife89@adsl-81-160-3.mcn.bellsouth.net) 17.32.55 Quit Zambezi (Read error: 60 (Operation timed out)) 17.36.48 Join Tomis2 [0] (n=Tomis@70.134.90.225) 17.41.26 Quit Tomis (Read error: 145 (Connection timed out)) 17.41.26 Nick Tomis2 is now known as Tomis (n=Tomis@70.134.90.225) 17.49.54 Join tomers [0] (n=chatzill@bzq-84-109-85-100.red.bezeqint.net) 18.05.09 Quit Llorean (Read error: 104 (Connection reset by peer)) 18.05.22 Quit bluebrother (Nick collision from services.) 18.05.23 Join bluebroth3r [0] (n=dom@rockbox/developer/bluebrother) 18.13.24 # kugel: about those statusbar bugs: are you testing on a 32bit or 64 bit machine? 18.13.34 # 64bit 18.14.10 # ok, I'm on 64 bit too, have you had a chance to try it against the mr500 sim? 18.14.16 # no, not yet 18.14.30 # doesn't gdb give any info? 18.16.13 Join derekja [0] (n=derek@cpe-69-204-247-87.nyc.res.rr.com) 18.16.19 Part derekja 18.18.07 # kugel: strange, I am trying this in a later build and it's not segfaulting 18.18.31 # maybe the segfault is not an issue 18.20.43 Quit dfkt (Excess Flood) 18.20.49 Join dfkt [0] (i=dfkt@unaffiliated/dfkt) 18.23.11 # does video now work on the nano 2g? last time I checked the sound/video was out of sync 18.23.42 Join toffe82 [0] (n=chatzill@ppp-71-138-17-48.dsl.frs2ca.pacbell.net) 18.24.23 # check with different samples 18.25.01 # works for me Crunchie 18.25.09 # i just watched a full movie on mine last night 18.25.15 # I checked it with the sample elephant dreams 18.25.20 # only took about 7% of my battery actually 18.25.34 # i was fully expecting it would take much more 18.25.41 # oh okay will check out a new revision 18.25.51 # I've noticed that most wps'es contains the string 'Next Track' while only CabbieV2 and DancePuffDuo has 'Next Song'. Is there a differentiation between 'Song' and 'Track' in wps, or is this simply an issue of lack of consistency? 18.31.28 # kugel: ok, I reproduced it on r: 23572 - I am going to see if I can pin down which revision fixed it 18.31.43 # alright 18.33.34 Quit kugel (Remote closed the connection) 18.35.08 Nick YPSY is now known as Ypsy (n=ypsy@geekpadawan.de) 18.40.16 Join Bagder_ [0] (n=daniel@static-93.158.79.102.got.public.icomera.com) 18.41.11 # hmm it's still out of sync with the latest revision 18.41.59 Join Paleskin [0] (n=Paleskin@fm-ip-118.137.90.128.fast.net.id) 18.42.07 Join kugel [0] (n=kugel@rockbox/developer/kugel) 18.42.11 # but oh well I'm glad I can run things now on my nano 2g :) 18.42.40 # really 18.42.45 # rockbox r23549-091107 on sansa fuze 18.42.59 # kugel: looks like bug 2 is no longer an issue since r23580 18.43.03 # flac playback autopause during playback 18.43.10 # and to resume need reboot 18.43.16 # is this a known bug ? 18.43.20 # i used the 310kbps encode of elephants dream i think Crunchie 18.43.22 # I updated the tracker entry to reflect that 18.43.23 # seamed fine 18.43.34 # i didn't watch it all the way through though 18.44.05 Join Grahack [0] (n=chri@ip-222.net-82-216-222.rev.numericable.fr) 18.44.22 # i encoded a full movie at 150k video and 64k audio, about an hour and a half long 18.44.24 # I'm not sure aobut your assessment on bug 3 though - we must do some clearing of the screen before going into the wps, otherwise there would be artifacts of the list everywhere 18.44.36 # I've used this http://download.rockbox.org/mpeg/elephantsdream-q6-176x128-310kbps.mpg 18.44.39 # it played fine 18.44.46 # yea, that's the one i usedd 18.46.16 # kugel: With the custom statusbar graphic glitches I have only been able to cleanly use it with the main menu, I have to disable it in the wps and re-produce the portion of the custom sbs in the wps that I would otherwise have done with a conditional in the sbs. 18.46.17 # kkurbjun: the skin engine does this clear, but not as immediately as you might think 18.46.49 # all my sbs are re-used in the wps 18.46.56 # it looks like it does the clear before the wps screen tests true 18.47.30 # I doubt that 18.47.33 # by looks I mean just from testing it form a user side 18.48.00 # if you could try those tests it would be really helpful because I would like to understand how to use it properly 18.48.12 # yea sure, once I have some time 18.48.27 # If I can't get it working right with the conditionals I don't see how anyone else will unless they get lucky 18.50.00 # what glitches are you experiencing exactly? 18.51.09 # it shows portions of the custom sbs that were supposed to only show in the lists. If those areas are not overdrawn with a viewport in the wps the artifacts show 18.51.30 # I use this tag: %?cs<%Vda| | | > 18.51.38 # where %vda should only show in the list 18.52.14 # and then I go into the wps it shows an artifact of the albumart positioning that was only supposed to show in the menu 18.52.56 Join panni_ [0] (i=hannes@ip-95-222-21-143.unitymediagroup.de) 18.53.14 # oh yeah, how do I upgrade from one build to another ? should I erase the rockbox folder on fuze, and let rockbox utilities do the rest ? 18.54.34 # you can just download and extract the latest build to the device, having it replace existing files 18.54.37 # Paleskin: no need to delete things. The new build will just overwrite things 18.55.13 # Paleskin: have you checked the filesystem? Corrupted filesystems have been known to cause really strange behaviour 18.55.38 # kkurbjun: why do you put a space there, btw? 18.56.33 Quit funman ("free(random());") 18.56.35 # I dunno, I just had it in tehre in the example - it gives the same glitches if I just do %?cs<%Vda> 18.57.52 # I'll have a look, that glitches shouldn't happen of course 18.58.09 Join phanboy4 [0] (n=benji@c-24-98-43-198.hsd1.ga.comcast.net) 18.58.50 # @gevaerts, how do I check my filesystem ? 18.58.53 # kkurbjun: 18.59.02 # disk utility Paleskin 18.59.12 # (oops) do you have something between %Vi and the folling %V[l]? 18.59.23 # oh sorry 18.59.25 # wrong room 18.59.26 # lol 18.59.42 # @Tomis, control panel -----> adm-----> storage ? 18.59.59 # this is the sbs I am seeing the glitches with: http://www.rockbox.org/tracker/task/10771?getfile=20892 19.00.02 # i was thinking i was in one of the mac channels, sorry 19.00.21 # oic 19.00.38 # I'm using xp dual boot with 7 19.02.02 # let say If I deleted the rockbox folder first, then telling rockbox utilities to upgrade, so there aren't any leftover files, will something bad happens ? 19.02.12 # kugel: with that sbs I see a couple of graphic glitches, the left side of the wps backdrop seems to be from teh list backdrop, I have a small box that also appears to be from the list backdrop and then the album art from the list still shows 19.02.38 # i dont see why anything would be wrong with that Paleskin 19.02.45 # you're just deleting files and writing new ones 19.03.14 # should I reinstall the boot loader ? 19.03.32 # kkurbjun: basically, the problem is that the sbs can't just clear everything, it's not really proper if the wps does this either 19.04.08 # if the sbs clears out everything, it could clear list/wps area. and the wps could clear sbs area 19.04.55 # I'm not sure how feasible/possible doing it right is 19.05.02 Join nawks [0] (n=matt@va-67-233-123-218.dhcp.embarqhsd.net) 19.05.13 # kugel, couldn't the sbs be re-drawn after the wps screen is entered and the screen is cleared? 19.05.50 # IIRC that's being done. maybe it's not 19.08.05 # you could try inserting a send_event(GUI_EVENT_REFRESH, NULL) somewhere in the if (restore ...) block 19.08.52 # kugel: what file are you referring to? I am not familiar with the skin code at all 19.08.55 # or better, in gui_wps_display() before the skin_redraw call 19.09.11 # wps.c and skin_display.c 19.10.44 # hmm, I get compile errors with send_event(GUI_EVENT_REFRESH, NULL); 19.10.55 # it says that GUI_EVENT_REFRESH’ undeclared 19.11.52 # #include "appevents.h" 19.12.58 # :), it gets rid of the sbs glitches, but nothing shows in the wps till I go to the next trach 19.13.00 # tack 19.13.04 # track 19.13.35 # I just added that call to gui_wps_display 19.13.47 # right above return 19.14.55 *** Saving seen data "./dancer.seen" 19.15.51 # strange 19.17.19 # kugel, if I add it in the if(restore block it gets rid of the albumart glitch and the wps shows mostly correct, but the left side of the backdrop still appears to have the list backdrop used - it appears to be equal to the scrollbar width 19.17.27 Join MaadMan [0] (n=MaadMan@188-192-221-19-dynip.superkabel.de) 19.17.36 Part Paleskin 19.17.52 # yea, the wps backdrop is set in gui_wps_display, that's why 19.17.55 # and I still have an unexplicable box right next to the now playing area 19.18.30 # * kugel doesn't understand why the wps is be empty 19.24.06 # kkurbjun: that doesn't happen here 19.24.18 # ah yea, I see why 19.24.28 # bloody remotes :/ 19.29.31 # itunes to restore 19.29.33 # what do i do 19.29.37 # i cant get itunes :< 19.29.54 # why not 19.30.34 # Because it dosnt run on this computer i alreaty told you tomers >.> isnt there another option? 19.30.59 # it only needs windows or a mac 19.31.03 Quit Prot (Read error: 113 (No route to host)) 19.31.20 # tomers it dosnt run on my computer i alreaty told you somewhere else 19.31.22 # :/ 19.31.43 # if you need to restore to the factory state, you need itunes, or restore from a backup, if you made one before installing rockbox 19.31.46 # Zorda_: s/tomers/Tomis/ :-) 19.31.55 # sorry 19.32.37 # do you really want to go back to the factory firmware? 19.32.48 # Tomis Do i have a choice? 19.32.52 # or is it just that's what the ipod is displaying on it's screen 19.33.16 # thats what its saying. 19.33.45 # but do you want go back to the factory firmware 19.33.49 # if you don't care 19.33.49 # Not really. 19.34.01 # then you can just blow the thing away 19.34.08 # and put on rockbox? 19.34.12 # yea, exactly 19.34.24 # cool thanks 19.34.26 Join hillshum [0] (n=hillshum@75-165-230-226.slkc.qwest.net) 19.34.32 # thats what i was wondering ifi could do 19.34.48 # yea it's just showing that message because something got messed up 19.35.03 # something probably went wrong during your rockbox instal 19.35.23 # just go through the process again 19.39.56 # kkurbjun: I think I have a good patch soon 19.40.06 # cool 19.41.08 Quit phanboy4 (Read error: 104 (Connection reset by peer)) 19.43.09 Join vodi [0] (n=vodi@91-113-68-167.adsl.highway.telekom.at) 19.44.07 # hmmm its in disc mode but ipodpatcher isnt identying it.. 19.45.46 # did i brick it? lol 19.46.21 # kkurbjun: http://pastie.org/698833 should do it 19.48.02 Quit jfc^3 (Read error: 104 (Connection reset by peer)) 19.48.15 # it doesn't seem to remove the list backdrop parts here, which is weird since clear_display() and lcd_update() is called 19.48.58 Part vodi 19.49.39 Join jfc [0] (n=john@dpc6682208002.direcpc.com) 19.50.40 # on a theme which didn't have this problem before :S 19.51.34 Join Zambezi [0] (i=Zulu@80.67.9.2) 19.52.53 Quit ender` (" First things first, but not necessarily in that order.") 19.56.51 # heh 19.56.54 # i dindt backup 19.57.02 # guess thats the end of my ipod 19.57.03 # w/e 19.58.25 # unlikely 19.59.16 # or i could do the obious thing and take my netbook to where i can get itunes 19.59.28 # well 19.59.37 # it still works as a flashdrive 19.59.37 # lol 19.59.38 # just blow it away and resinstal rockbox 19.59.48 # tried didnt work 20.00.16 # what ipod is it 20.00.28 # nano second gen 20.00.39 # do a manual instal 20.00.46 # i did 20.01.08 # here, lemme find the instructions i used 20.01.31 # ipodpatcher didnt like mine either 20.01.38 # i went with iloader and it works fine 20.02.28 Join ender` [0] (i=krneki@foo.eternallybored.org) 20.02.35 # http://l4n.clustur.com/index.php/ILoader 20.02.44 # follwo those isntructions for the bootloader instal 20.03.08 # then follow rockbox's instructions for manual instal of rockbox, ignoring the rockbox bootloader instal 20.08.04 # meh 20.09.15 # on my nano 2g(with rockbox) there is a thread which locks up and stops everything from working. how could i find out which one it actually is? 20.17.00 # Zorda_: have a look at http://www.rockbox.org/wiki/IpodManualRestore 20.17.19 # * gevaerts doesn't know why people say you need itunes for this 20.20.04 Join phanboy4 [0] (n=benji@c-24-98-43-198.hsd1.ga.comcast.net) 20.20.57 Join domonoky1 [0] (n=Domonoky@g229153129.adsl.alicedsl.de) 20.22.29 # because it's the manufacturer's way and it's easy gevaerts , that'd be my guess 20.23.10 # i'm surprised apple hasn't sent a c&d to the guy hosting the firmware files though 20.23.35 # Tomis: possibly, but then "if you need to restore to the factory state, you need itunes, or restore from a backup, if you made one before installing rockbox" is just spreading misinformation 20.24.22 # yea i forgot about the manual way to restoring it 20.27.49 # gevaerts: but what about the FTL? is that saved on the flash where the files are saved or anywhere else? 20.28.26 # kkurbjun: did you try that patch? 20.30.47 # gevaerts it dosnt have my model 20.30.53 Quit MaadMan ("Leaving") 20.31.03 # could i just go with first gen nano? 20.32.04 # it does Zorda_ 20.32.23 # liar: the FTL sites between the flash and the filesystem 20.32.44 # you were talkin abiut the list of firmwares at the linked page? 20.33.16 # Zorda_: no. They're different. If you're really stuck, I'd recommend waiting aroud for TheSeven (although I really have no idea when he will be online again) 20.37.03 # gevaerts: what i mean is: if you put a backup back on your flash the ftl will be restored too? 20.37.46 # liar: I don't think so. I think it needs to be reset explicitely, but I don't really know (no 2nd gen nano here) 20.38.09 # gevaerts: yeah so the itunes way is more save 20.38.12 Join stoffel [0] (n=quassel@p57B4E894.dip.t-dialin.net) 20.38.16 Quit domonoky (Read error: 110 (Connection timed out)) 20.47.40 Quit stoffel (Remote closed the connection) 20.49.16 Quit thegeek (Read error: 104 (Connection reset by peer)) 20.50.08 Quit Tomis () 20.53.51 Join Tomis [0] (n=Tomis@70.134.90.225) 21.07.34 # New commit by 03kugel (r23625): Fix peakmeter from delaying the initial display of the wps. Also change HZ/100 to TIMEOUT_NOBLOCK which is more appropriater in the get_action() call ... 21.07.39 Quit kugel (Remote closed the connection) 21.08.03 Join kugel [0] (n=kugel@rockbox/developer/kugel) 21.08.32 # kugel: Can you please give me feedback on "FS#10783 - WPS translation" ? 21.09.35 # what kind of feedback? I'm for it, if you mean that :) 21.10.15 # not sure if I like %Sr, but that's minor anyway 21.10.20 # tomers: definitely commit the "next track" bit! 21.10.42 # kugel: Thanks. Just want to ask several developers first... 21.11.08 # kugel, gevaerts: I would rename it to whatever you think appropriate 21.12.31 # gevaerts: There are two other phrases - 'Next', and 'of'. I think they can also go in - just a total three strings for this purpose is cheap :-) 21.13.03 # kugel, that patch does appear to fix the conditional viewport problem, the left size backdrop issue still seems to be there 21.13.16 # Regarding the lang file, I use 'user: core' and also the asterisk for the phrases. Is it OK? 21.13.20 # tomers: I mean FS#10782. I don't have an opinion yet on the others 21.13.22 # /s/size/side 21.13.24 # kkurbjun: yea, I can't explain that 21.14.02 # there's still that little box that is clipped too 21.14.07 # gevaerts: I will commit FS#10782 now.... 21.14.20 # I suspect a bug somewhere else. a clear/update entire display really shouldn't leave that over 21.14.58 *** Saving seen data "./dancer.seen" 21.15.00 # I did find that it doesn't show if I disable the custom statusbar when going into the wps screen with %wd 21.15.13 # the left side glitch that is 21.15.28 # it doesn't show with the built-in statusbar either 21.15.50 # well, the patch does that combo 21.16.27 # you aren't unfamiliar with the lcd drivers, any idea how that could leave parts of the display untouched? 21.16.57 # The onlything I can figure is that a clear was called before the new backdrop is set 21.17.04 # New commit by 03tomers (r23626): FS#10782 - WPS: Rename 'Next Song' to 'Next Track' ... 21.17.38 # kkurbjun: I tried explicit calls to display->clear_display() and display->update() too. that changed nothing except giving the expected flicker 21.17.40 # the backdrop is just done with a pointer and the lcd routines use that when doing any operations with fonts, transparencies, and clearing 21.18.38 Quit linuxguy3 (Remote closed the connection) 21.18.49 Join linuxguy3 [0] (n=timj@adsl-75-57-190-229.dsl.emhril.sbcglobal.net) 21.20.23 # it would have to be something where that portion of the screen is drawn when the backdrop is set to the list backdrop rather than the wps 21.23.31 # tomers: I think I like FS#10783, with two caveats : (a) I have no opinion on WPS tag names (see other people for that), and (b) maybe MrSomeone should do a survey on the theme site to find a list of common strings, so we can actually support more than just cabbie (of course the commit doesn't necessarily have to wait for this) 21.23.53 # kugel: do you know when lcd_set_backdrop is called with respect to clearing the screen? 21.24.21 # and is there a chance that it is called pointing to the list backdrop after the wps is entered? 21.25.13 # ah I see what you mean 21.25.21 # the backdrop must be set before clearing 21.26.27 Quit Grahack (Read error: 113 (No route to host)) 21.26.37 # kkurbjun: that works for me now http://pastie.org/698927 21.28.36 # kugel, nice that is working properly now 21.30.03 # ahh 21.30.22 Join TheSeven [0] (n=theseven@rockbox/developer/TheSeven) 21.30.39 # I think I found what is happening to the touchscreen buttons - it looks like they are being offset when the custom sbs is loaded and enabled on the wps screen 21.30.51 # they are shifted down from the positions specified 21.31.24 # I'm not sure why that is happening though with respect to the code implementation 21.31.56 Join Grahack [0] (n=chri@ip-222.net-82-216-222.rev.numericable.fr) 21.32.04 # oh, I wonder if it has to do with the UI viewport setting 21.32.15 # it looks like they are slightly offset down too 21.32.30 # and it seems to be approximately equivalent to the UI viewport setting 21.32.40 # arent the coordinates absolute? 21.33.01 # they should be 21.33.44 # sorry the second offset note should read right rather than down 21.33.50 # on a related note, someone should look into changing the touch button handling, so that the sb can have touchregions 21.34.06 # they are offset down and to the right about the same amount as the ui viewport offset from the top left of the screen 21.34.33 # that would be nice 21.36.00 # it also looks like the buttons that are defined outside of the ui viewport are not able to be pressed 21.36.53 # yeah, with the slider if I slide it to the right I can only use the area that overlaps with the ui viewport setting 21.37.57 # I can't see where the code is wrong 21.38.25 # ah well I can 21.39.06 Quit Bagder_ ("It is time to say moo") 21.39.08 # JdGordon recently made a change so that the default viewport of the wps is (potentially) a lot smaller 21.39.44 # the touchregion code natuarlly checks if the press is within the viewport the touchregion is defined in 21.40.12 # if that happens to be the default viewport, the touchregion might be capped 21.40.52 # I don't consider this wrong, you should use a special viewport for the touchregion instead 21.41.04 # (that's the only thing I can imagine right now) 21.41.18 # which viewport should be used for the touchregion? 21.41.29 # I mean what do I need to do in the wps/sbs? 21.41.47 # gevaerts: Thanks for reviewing! I don't know who to ask regarding the name of the skin tag... Any idea? 21.41.49 # define the touchregion after a viewport you have control over 21.42.06 # or rather "more control" 21.42.57 # hmm 21.43.26 # got the new mdct to at least compile in rockbox, now to make it actually work 21.43.50 # that wouldn't explain why it adds an offset though, and I assume the volume bar isfully drawn too (that would be strange since that also exceeds the viewport) 21.44.10 Quit Strife89 ("Leaving") 21.44.27 # So right now it doesn't look like the ui viewport is used when you are in the list view with respect to the touchscreen handling, and then when you are in a wps it is used in some strange way 21.44.58 # gevaerts: Maybe I should commit, and later rename if someone has a better suggestion? 21.45.08 # because I thikn it is ready 21.45.11 # well the volume slider is displayed in its own user defined viewport 21.45.18 Quit Tomis () 21.45.24 # put the touchregion there then :) 21.45.46 # * kugel isn't sure anymore whether the coordinates are display or viewport relative, I would assume the latter 21.45.50 # tomers: I wouldn't commit if there's a good chance it has to be renamed 21.46.04 # tomers: what name of the skin tag? What is it used for? 21.46.11 # yeah, I try do that as a workaround, but it seems like the logic is broken to me 21.46.19 # tomers: on the other hand, only one person has objected so far, so maybe he can propose an alternative :) 21.47.11 # kkurbjun: maybe it's clearer when you read the dev ml thread 21.47.29 # I read that thread between you and jdgordon 21.48.10 # the default viewport of the wps uses the ui vp, I don't see how that's broken logic (I argued against that but both logics are reasonable) 21.48.51 # that one was never guaranteed to be fullscreen actually 21.49.08 # huh - what is the thinking for having the wps use the ui vp for the default? 21.49.27 # ask JdGordon :) 21.50.24 # anyway, this vp can't be fullscreen or it gets in the way of statusbars (classic and custom) 21.50.32 Join maffe [0] (n=Miranda@77-21-34-47-dynip.superkabel.de) 21.50.46 # ok, I'll ask him about that 21.50.52 # pixelma: http://www.rockbox.org/tracker/task/10783 - New conditional skin token 'Sr' which checks whether the currently loaded language is an RTL language (Hebrew/Arabic). It uses lang_is_rtl(). 21.51.17 # so it looks like the graphic glitches are fixed at least on the wps - when I'm in the list view and I hit resume I still get a glitch after the noting to resume message times out 21.51.29 # if %T is viewport relative, then having it in the default vp was always wrong (no matter of UI vp or sbs) 21.51.49 # kugel, but the ui viewport might be dynamic in a sense - like I was trying to implement 21.52.04 Join Tomis [0] (n=Tomis@70.134.90.225) 21.52.08 # huh? 21.52.09 # so that you could have a status area while you are in the lists that goes away when you go to the wps 21.52.20 # I mean the ui viewport doesn't change size 21.52.30 # but the area that I would want it to take effect is less 21.52.46 # actually, in the wps I would not want the ui viewport used at all 21.52.57 # you can do that, but you can't rely on the default wps viewport then 21.52.59 # but I guess that's a matter of debate 21.53.19 # yeah, I gotcha it makes more sense now that I understand what it's doing 21.53.26 # New commit by 03tomers (r23627): Updated Hebrew language 21.53.47 # I think that the behavior is confusing if you don't know what the underlying code is doing though. 21.54.20 # I guess you can imagine what bad things happen if the default wps viewport overlaps with sbs (that also happens with specified viewports but that's considered as user fault) 21.55.27 # JdGordon wanted to get rid of having 2 default setups (the %Vi and the UI vp one) 21.55.43 # gevaerts,pixelma: I won't commit "FS#10783 - WPS translation" now. I'll let it cook until tomorrow.... 21.55.48 # * tomers Good night 21.56.27 # kugel: I don't understand having two setups though - doesn't the %Vi tag do the same thing that the cfg one in some sense? 21.56.31 Quit tomers ("ChatZilla 0.9.85 [Firefox 3.5.4/20091028153816]") 21.56.52 # it seems like allowing the user to define one outside of the theme is a good way to break things as this touchscreen stuff shows 21.57.10 # the code didn't quite do what it suggested to do, there was set_fullscreen() which was %Vi or really fullscreen minus the area used by the classic sb. then there was _set_defaults which was UI vp or the result of set_fullscreen() 21.58.39 # now there's just set_fullsscreen which is really fullscreen and set_defaults which is the UI vp intersected with %Vi (or fullscreen if neither is set) 21.59.28 # so %Vi doesn't specify the UI viewport? 21.59.45 # no 21.59.50 # ok... 21.59.53 # it's the viewport that doesn't overlap with the sbs 22.00.10 # I'm not using the UI viewport then I was using the wrong terminology in the above messages 22.00.34 # so the wps' default viewport is as big as %Vi 22.00.45 # ... 22.01.01 # if you want to overlap that because you know what you're doing, then you need to specify viewports 22.01.04 # but that's different from the UI viewport? 22.02.07 # * kugel thinks the better way of doing is to handle all this stuff within the sbs 22.02.33 # you seem to be deactivating parts of the sbs in favor of filling that space from the wps? 22.03.06 # so consider this case. The wps disables the sbs when you go into it because it wants the default viewprot to be the fullscreen expecting to set touchscreen positions relative to the fullscreen. then the user sets a ui viewport setting with a cfg - what happens to the touchscreen areas? 22.03.22 # yeah, that's what I was doing 22.04.38 # why don't you do that in sbs? 22.05.19 # do what? 22.05.38 # fill that space from the sbs instead of from the wps 22.05.49 # the album art is larger in the wps 22.06.03 # I give a smaller area for album art in the list 22.06.19 # and then when you go to the wps I only want to show the time section of the sbs 22.06.28 # with that conditional setting 22.07.06 # then then the expectation I have is that you can use the area that does not have an active viewport in the sbs 22.07.20 # which works now with that patch 22.07.24 # yea, that's how I did it originally 22.07.29 # but the touchscreen stuff gets all offset 22.07.39 # which is fine if you know what your doing 22.07.51 # you really shouldn't be having touchregions in the default wps viewport 22.08.00 # but the concern I have is with the cfg ui viewport setting 22.08.24 # having them in a specified viewport is not only a work around, it's the only way to get a guaranteed vp 22.09.16 # if you want a fullscreen one you can always put a "%V|0|0|-|-|-|-|-|" at the very beginning 22.10.17 # it worked fine before with the standard statusbar, the other concern I have is how do you effectively communicate this to a theme author - after talking to you and jdgordon I have an understanding of how this all fits together, but it's extremely confusing/looks like a bugs if you don't know what the code is doing 22.12.13 # yeah, the %V|0|0|-|-|-|-|-| tag worked 22.12.19 Join Jaykay [0] (n=chatzill@p5DDC5997.dip.t-dialin.net) 22.12.20 # my initial commit didn't change that behavior, if you had %wd you got it very fullscreen. JdGordon changed that 22.12.46 # but, if you don't have a UI vp, and %wd and still don't get fullscreen now, it's a bug 22.13.57 # kugel, what if the custom sbs doesn't specify a %vi tag though and the wps enables the statusbar and you have a cfg setting for the ui viewport 22.14.30 # the UI vp is used for the wps 22.14.32 # that would generally be an invalid case I would agree, but there's nothing stopping an author from doing that to my knowledgte 22.15.06 # not having %Vi easily leads to problems, I don't disagree here. I think CustomWPS is explicit about that 22.15.11 # and that breaks the theme if they use the default viewport for the touch offsets 22.15.26 # that's bound to be broken, really 22.16.00 # I consider such a theme badly coded no matter of ui vp/sbs/whatever 22.16.12 # I bet I could make a pretty usable sbs that doesn't specify the %vi tag 22.16.24 # kkurbjun: that's why it isn't required ;) 22.17.18 # and if I didn't know better there would be nothing stopping me, but when you throw the ui viewport cfg in the mix it can start breaking all kinds of things in the wps depending on how it is made 22.17.58 # we obviously can't make everybody happy 22.18.32 # what we have now certainly gives the best freedom and good fall back mechanisms 22.18.55 # I guess my point is it seems that the %vi tag should be the only thing that changes the display - that way the theme/skin author can make sure that everything plays nice 22.19.13 # and ignore the ui vp? 22.19.25 # when you let the end user that didn't have a hand in the creation of the theme or skin set those things it's setup for confusion 22.19.36 # don't confuse %Vi with making things look nice. it's the tag to make an sbs portable 22.23.25 # I guess I would count myself confused :-D 22.23.49 # is somewhere mentioned that %Vi is the UI viewport? 22.24.15 # "This viewport is used as Custom UI Viewport in case the theme doesn't have a ui viewport set in the theme.cfg" 22.24.21 # http://www.rockbox.org/wiki/WebHome?topic=CustomWPS 22.24.40 # yea, that's correct 22.24.51 # so %vi is the ui viewport? 22.25.05 # only " in case the theme doesn't have a ui viewport set in the theme.cfg" 22.25.25 # * gevaerts thinks that that line is actually meaningless 22.25.39 # and it's not something you can rely one, since you can interchange wps's and sbs's 22.25.48 # yeah.. that makes sense so the theme can set it in the cfg or the sbs 22.25.52 # The actual used viewport is the intersection between UI viewport and %Vi, right? 22.26.00 # maybe it should be worded to make clear that it's used as a fallback rather 22.26.04 # hm, wait, this is about WPS 22.26.08 # * gevaerts doesn't know then 22.26.12 # haha 22.26.55 # but the user could also set it in their cfg independent of the theme, sbs, or wps 22.27.15 # kkurbjun: %Vi is designed to make SBSs work with themes that aren't designed for it, to not cause redraw problems 22.27.15 # yes, but that doesn't mean it's a good idea 22.27.43 # if you want to align stuff to the backdrop, then that's unrelated to the sbs, then the ui viewport setting should be used 22.27.57 # oh wait, it's not wps, it's sbs... 22.28.14 # * gevaerts thinks that the %Vi description is misleading 22.28.38 # but %Vi wouldn't accomplish that with a wps that really used viewports to their full extent 22.29.33 # of course not 22.29.39 # the wps needs to make sure itself 22.30.08 # by using %wd for example (although that doesn't protect against the UI viewport) 22.30.10 # kugel: if the UI viewport is not set, the UI behaves as if the UI viewport is set to fullscreen, right? If so, isn't the effect *always* that the used viewport is the intersection of %Vi and UI viewport? 22.30.22 # so what is the expectation from the user side - it sounds like the intent is for sbs's to be portable, but they, in reality are not if you use viewports in the wps 22.30.37 Join toffe82_ [0] (n=chatzill@adsl-76-240-236-30.dsl.frs2ca.sbcglobal.net) 22.30.37 # gevaerts: sounds about right 22.30.55 # kkurbjun: I can't follow that conclusion 22.31.27 # * gevaerts thinks that in an sbs world a wps shouldn't enable the status bar 22.32.41 # so consider all the themes that use the %we tag because of the builtin statusbar and it uses viewports in the wps - then they load up a custom sbs that sets a %vi tag to try and be "portable" which doesn't really accomplish anything 22.32.50 # isn't the biggest problem when you don't use own viewports in the WPS and rely on the default viewport? 22.33.14 # i.e. draw stuff in it 22.33.25 # the only way that %vi is portable is if you exclusively rely on the default viewport 22.33.41 # I mean have a wps that exclusively relies on it 22.34.05 # or have a wps that disables the statusbar 22.34.07 # kkurbjun: that's the wps' fault, not the sbs one 22.34.11 # not really, because the wps might also rely on a certain minimum size 22.34.18 Join bomber227 [0] (n=48e593b7@giant.haxx.se) 22.34.31 # of course we can't have *everything* just work 22.34.31 # wassup 22.34.41 # gevaerts: how do you mean? 22.35.30 Quit shai ("Leaving") 22.35.43 # kkurbjun: in the old days, the status bar always had the same size so the wps could take that into account. In the %Vi days, the left-over space can easily be too small to show the wps in any sensible way 22.35.57 # and the wps author can't really do anything about that 22.36.04 # i finally got my sansa fuze in the mail and now have a clipv2 thats not in use. now i was wondering if there's any way i could help with the clipv2 developement? i can't think of how but id like to help anyways 22.38.23 # kugel: I see the point of having the flexibility from the developer/skin author standpoint, but it puts alot of burden on the end user when we offer menus for selecting your custom sbs and wps in the same menu screen 22.38.36 # I disagree 22.39.29 # and mixing/matching them does not work right - how are they supposed to understand the intricacy of what they just did to their interface 22.39.49 # bomber227: hows your c programming? 22.40.27 # 0. i have started learning BASIC, though.... 22.40.30 # * kugel thinks kkurbjun is too user centric ;) 22.40.42 # don't forget our ideal to not care about them :) 22.40.44 # basically the current way can work with independent backdrop+UI viewport (i.e. the "list theme"), sbs, and wps, *as long as* the wps does not show the status bar. I think that that's sufficient to warrant the flexibility, but yes, it would be nice to make wps+random sbs work 22.41.12 # if we pulled those menu items and only allowed these to be set from a "theme" it would allow all that flexibility while preventing the user from making all kinds of bad combinations 22.41.32 # :) 22.41.42 # "preventing the user from making all kinds of bad combinations" is simply impossible 22.41.49 # and we don't need that 22.41.56 # bomber227: well without the ability to program developing isn't going to be possible 22.42.13 # well it would at least make it more difficult for a novice user to destroy the usability of their player 22.42.15 # i suppose if you're not using the player you could see if any developers were interested in working on it 22.42.19 # The user has been able to pick bad combinations forever, with much worse results than are possible with the sbs+wps mess 22.42.29 # yeah. i was thinking maybe testing or soemthing 22.42.32 Join BHSPitLappy [0] (n=BHSPitLa@unaffiliated/bhspitmonkey) 22.43.16 Quit kugel (Remote closed the connection) 22.43.32 # when I say user I'm talking about the person that loads up a bunch of themes on their player and starts messing with the theme menu - I'm not talking about someone developing a new theme 22.44.14 # /loads up a bunch of themes with rbutil/ after installing rockbox that is 22.44.14 # kkurbjun: how can they destroy the usability of their player? I mean, they might have an unreadable wps if they pick a bad combination, but they can still get out, and return to the settings menu. That's *a lot* better than what happens if they pick bad colour combinations 22.44.51 # if you have a %vi setting and a cfg setting that only overlap with one pixel that would be a touch interface to navigate 22.45.06 # tough that is 22.45.36 # hm, true. That could be solved by having some sort of minimum and refusing to load the sbs 22.46.59 Quit toffe82 (Read error: 110 (Connection timed out)) 22.47.12 # alright well i guess i cant help 22.47.28 # I'm sure there are other ways to solve it, I'm just saying that it's a potential nightmare for the end user. only allowing them to set these through the cfg seems like a good way to give the most flexibility while protecting the user to some degree. 22.47.53 Quit Jaykay ("ChatZilla 0.9.85 [Firefox 3.5.5/20091102152451]") 22.48.32 # it definitely protects them, but should it? There are dozens of other settings that can have bad effects if combined in certain ways, should we block all of those? 22.48.51 # what settings are you referring to? 22.49.51 # there are some UI things (backlight off, or colour combinations), there's the EQ that can't handle too many bands on slow CPUs, there's the traditional party mode support issue, ... 22.50.06 Quit bomber227 ("CGI:IRC") 22.53.51 # in the case of the EQ it seems to make sense that the number of bands should be limited if the cpu cannot keep up with it - generally I thought backlight off is disabled on targets that you can't physically read the screen - colour combinations might make sense to be in the theme 22.54.31 # in the EQ you can't limit it, because the amount of available CPU also depends on the codec used. You might be able to do five bands with flac, but not with ape 22.55.03 # on PP a better solution would be to move the EQ to the second core 22.55.13 # then you'd probably be ok with everything but maybe MP3 22.55.14 # I think it's reasonable to do some things such as a guaranteed minimum viewport (maybe just implemented by just falling back to built-in everything, although fancier ways might be doable), so that the user can always get back to the settings menu, but I really don't like the idea of just dropping nearly all theme related settings 22.55.30 # saratoga: yes, on PP :) 22.55.51 # are there other targets too slow for 5 band EQ on most formats (APE excluded)? 22.57.01 # I mean, picking a theme you like and then changing the menu backdrop should be possible. It can cause bad combinations, but I'd expect this to be a reasonably common thing to do for people who can handle computers but don't want to edit theme .cfgs by hand 22.57.03 # I thought colour combinations are checked and not settable but the problem would be colours on backdrops 22.58.39 # only making settings possible in a package through themes doesn't necessarily protect against errors - it could be that the theme author did a mistake 22.59.50 # pixelma: I agree, the theme author could have messed up but I am counting them more in the power-user category they at least know about the different file types and know what to change 23.00.26 # saratoga: from looking at CodecPerformanceComparison I suspect that AAC might get in trouble as well, but my point was really that trying to set always safe limits is a bad idea 23.00.42 # gevaerts: I agree that could be a possibility, but I don't know where the target is for reasonable 23.00.43 # AAC on what? 23.01.45 # saratoga: on coldfire it seems to be between 115% and 160%. 115% doesn't really sound enough to add five bands of EQ 23.02.50 # kkurbjun: "there's enough room to find a menu". That could mean enough room for two lines of 22 characters, and compile with HAVE_LCD_CHARCELLS :) 23.02.53 # according to that page its about 60MHz, which leaves another 65MHz for EQ 23.03.02 # i don't think our EQ is that slow 23.03.08 # though AAC+ is another story 23.03.14 # and one that i hope to get to soonish 23.03.35 # gevaerts: that also depends on the font size.. 23.03.53 # actually i'm hoping to get some AAC benchmarks from the new IMDCT lib this weekend 23.03.53 Quit Grahack ("Leaving.") 23.04.05 # and that would fail on the mr500 remote in any case 23.04.09 # kkurbjun: true, but the "use built-in everything" should handle that 23.04.16 # i think coldfire performance will hopefully get a lot better, particularly if I can get someone to give me a few lines of ASM 23.04.30 # saratoga: I was looking at the last set of results on the page 23.04.42 # the first set are the most current i think 23.04.51 # ah indeed 23.05.07 # the last set are a couple days before I put the new MDCT into AAC :) 23.05.21 # anyway, if you can handle AAC with five band EQ, I'll just add timestretch and compression :) 23.05.36 # are those features slow? 23.05.45 # I don't know! 23.06.14 # I'm just pointing out that there can be lots of "bad" combinations of settings that we can't easily detect and block 23.06.32 # i think with some more optimization we could have most/all SWCODEC able to use full DSP effects on all sane formats 23.06.57 # But there's no law that forces people to use sane formats 23.07.15 # true, but the insane ones probably won't play real time at all 23.08.29 # i just realized i have no idea how to turn on eq 23.08.30 # APE tends to have a just-better-than-realtime profile for most targets. It's not always the same one of course 23.09.27 # i'm benchmarking EQ right now 23.11.34 # about 5MHz per EQ band 23.11.38 # (on PP) 23.11.46 # so 5 bands is just 25MHz 23.13.12 # not too bad 23.13.29 # so basically PP should be able to use 5 EQ bands for all formats which it can decode in realtime except probably ATRAC3 23.14.16 # still putting them on the second core would give a nice battery life boost 23.14.38 # i should ask Blue_Dude hard that would be to do 23.15.01 *** Saving seen data "./dancer.seen" 23.15.11 # it would definitely be nice 23.15.35 Join thegeek [0] (n=nnscript@s168c.studby.ntnu.no) 23.17.17 # there's also the eternal ipod video and its relatively slow LCD update that would really benefit from this 23.21.17 # * amiconn hands saratoga a 'how' 23.33.36 Ctcp Ping from gevaerts!n=fg@rockbox/developer/gevaerts 23.35.05 Quit gevaerts (Nick collision from services.) 23.35.14 Join gevaerts [0] (n=fg@rockbox/developer/gevaerts) 23.36.14 Quit linuxstb (Read error: 60 (Operation timed out)) 23.36.49 Quit Highlander ("Quitte") 23.39.44 Quit bmbl ("Bye!") 23.48.06 Join linuxstb [0] (n=linuxstb@rockbox/developer/linuxstb) 23.58.02 Join Quintasan [0] (n=quintasa@ubuntu/member/quintasan) 23.58.58 # Hiho, I'd like to package RBUtil for Ubuntu, on what license is rbutil released, I'd like to know if it uses any other licenses for some files