--- Log for 28.12.111 Server: wolfe.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 16 days and 0 hours ago 00.06.37 Quit factor (Ping timeout: 240 seconds) 00.12.52 Quit kevku (Ping timeout: 268 seconds) 00.21.38 Join factor [0] (~factor@74.197.205.204) 00.23.50 Quit [Saint_] (Read error: Connection reset by peer) 00.24.09 Join [Saint] [0] (~Saint]@unaffiliated/saint/x-8516940) 00.27.07 Quit Strife89 (Ping timeout: 248 seconds) 00.28.03 Join Strife89 [0] (~Strife89@66.251.199.43) 00.28.48 Part jlbiasini 00.30.01 # try ebay 00.34.44 Join perrikwp [0] (~quassel@cpe-024-163-024-033.triad.res.rr.com) 00.35.52 Quit n1s (Quit: Ex-Chat) 00.48.47 Join jlbiasini [0] (~metaphys@d86-32-96-55.cust.tele2.at) 00.49.48 Join user890104_ [0] (Venci@31.211.134.13) 00.50.07 # gevaerts: wont the DSP always show 2 channels? 00.50.54 Quit user890104 (Ping timeout: 252 seconds) 00.51.01 # JdGordon_: assuming the simulator works for this, no. It seems to work ;) 00.53.28 # JdGordon_: I'm not sure about the proper name for this tag. It's not actually metadata in the "new" implementation 00.53.44 # Also the name of the define should be different because of this 00.54.10 # ok 00.54.10 Quit bertrik (Ping timeout: 268 seconds) 00.54.19 # I just thought the dsp would always downmix to 2 channels :) 00.54.25 # and yeah, change the wps tag 00.54.39 # well yes, it *down*mixes. It just doesn't upmix :) 00.55.12 # i.e. it shows 1 or 2 00.56.25 Quit Keripo (Quit: Leaving.) 00.57.03 # the dsp code should probably handle downmixing as well, rather then making the codecs do it 00.57.13 # but i'm not sure what the overhead would be like 00.57.43 # gevaerts: so its more a stereo/mono tag? 00.57.49 # yes 00.58.24 # I'm not actually sure what we want here. Both stereo/mono and number of channels seem useful 01.00.37 # if you say so :) 01.00.47 # Well, if any of them are! 01.01.34 Quit Strife89 (Ping timeout: 252 seconds) 01.01.48 # One says something about whether you'll miss something by only listening on one side, the other says something about whether it's worth it to go out and buy a surround sound set :) 01.02.03 Part jlbiasini 01.03.26 # why not add another stereo tag that indicates the codec is downmixing? DSP_SET_STEREO_DOWNMIX_MODE 01.03.53 Join JdGord [0] (~AndChat@122.110.125.153) 01.03.56 # would still have to fix the codecs, but not that many even do >2 channels 01.05.26 Quit captainkwel (Quit: Ex-Chat) 01.06.16 # Maybe. I'm not really familiar enough with codec/metadata/wps interaction to have a decent opinion 01.13.43 Join Topy44 [0] (~Topy44@89.207.248.89) 01.16.14 Quit JdGord (Ping timeout: 240 seconds) 01.26.51 Join Keripo [0] (~Keripo@CPE0022b0d4bdb7-CM001a6680d4fe.cpe.net.cable.rogers.com) 01.33.35 *** Saving seen data "./dancer.seen" 01.58.51 Quit GeekShadow (Ping timeout: 255 seconds) 02.00.50 Quit lebellium (Quit: ChatZilla 0.9.88 [Firefox 10.0/20111221135037]) 02.03.44 Join GeekShadow [0] (~antoine@184.215.192.77.rev.sfr.net) 02.05.15 Quit GeekShadow (Excess Flood) 02.07.35 Quit Keripo (Quit: Leaving.) 02.08.33 Join T44 [0] (~Topy44@89.207.248.89) 02.08.48 Join GeekShadow [0] (~antoine@201.134.197.77.rev.sfr.net) 02.10.32 Quit Topy44 (Ping timeout: 255 seconds) 02.11.22 Join anewuser [0] (~anewuser@186.93.131.58) 02.11.22 Quit anewuser (Changing host) 02.11.22 Join anewuser [0] (~anewuser@unaffiliated/anewuser) 02.12.31 Quit dfkt (Quit: -= SysReset 2.55=- Sic gorgiamus allos subjectatos nunc.) 02.28.13 Join Keripo [0] (~Keripo@CPE0022b0d4bdb7-CM001a6680d4fe.cpe.net.cable.rogers.com) 02.33.40 Join Strife89 [0] (~Strife89@66.251.199.43) 02.34.46 Nick user890104_ is now known as user890104 (Venci@31.211.134.13) 02.58.48 Quit Strife89 (Ping timeout: 240 seconds) 03.27.30 Join webguest08 [0] (~3af6444a@www.haxx.se) 03.29.01 Quit webguest08 (Client Quit) 03.33.39 *** Saving seen data "./dancer.seen" 03.36.58 Quit advcomp2019_ (Ping timeout: 268 seconds) 03.50.10 Join advcomp2019 [0] (~advcomp20@unaffiliated/advcomp2019) 04.00.07 Quit user890104 (Ping timeout: 252 seconds) 04.26.19 Quit amiconn (Disconnected by services) 04.26.21 Join amiconn_ [0] (quassel@rockbox/developer/amiconn) 04.26.25 Nick amiconn_ is now known as amiconn (quassel@rockbox/developer/amiconn) 04.26.54 Join JdGord [0] (~AndChat@58.108.125.128) 04.28.42 Quit pixelma (Disconnected by services) 04.28.44 Join pixelma_ [0] (quassel@rockbox/staff/pixelma) 04.28.46 Nick pixelma_ is now known as pixelma (quassel@rockbox/staff/pixelma) 04.29.36 Quit [7] (Disconnected by services) 04.29.46 Join TheSeven [0] (~TheSeven@rockbox/developer/TheSeven) 05.27.01 Join ChickeNES [0] (~ChickeNES@72.173.173.26) 05.27.37 Quit ChickeNES (Read error: Connection reset by peer) 05.28.23 Join ChickeNES [0] (~ChickeNES@72.173.173.26) 05.29.49 Join Rob2223 [0] (~Miranda@p4FFF29D0.dip.t-dialin.net) 05.33.40 *** Saving seen data "./dancer.seen" 05.33.49 Quit Rob2222 (Ping timeout: 252 seconds) 05.40.36 Quit ChickeNES (Quit: Computer has gone to sleep.) 06.11.42 Quit perrikwp (Read error: Connection reset by peer) 06.13.48 Join perrikwp [0] (~quassel@cpe-024-163-024-033.triad.res.rr.com) 06.27.09 # [Saint]: free to test a patch? 06.27.38 # <[Saint]> Nup. Sorry :-S 06.27.58 # you suck! 06.55.07 # New commit by 03jdgordon (r31452): protect the yes/no screen from extra keypresses (which can happen if you display 2 yes/no screens too quickly) 06.55.16 # hopesfully that doesnt make things worse :p 06.57.25 # r31452 build result: All green 07.15.21 # [Saint]: if oyu can be bothred... fs#12474 is worth a go 07.15.22 # http://www.rockbox.org/tracker/task/12474 3[PATCH] Database: Support for multiple search roots. (patches, new) 07.17.38 Quit JdGord (Quit: Bye) 07.19.04 # <[Saint]> Runnin' it now. 07.19.54 # <[Saint]> Oh...nup. 07.20.08 # <[Saint]> I'm using it prior to your contribution. 07.33.44 *** Saving seen data "./dancer.seen" 07.36.52 Join chkktri_ [0] (~user@83.149.48.18) 07.48.51 Quit saratoga (Quit: Page closed) 07.49.17 Quit bieber (Read error: Connection reset by peer) 08.16.15 Join kevku [0] (x@2001:470:28:773::) 08.50.52 Quit ze (Ping timeout: 268 seconds) 08.54.23 Join ze [0] (ze@ze.yi.org) 08.54.23 Quit logbot (Ping timeout: 252 seconds) 08.54.23 *** ERROR: (Closing Link: giant.haxx.se (Ping timeout: 252 seconds)) from wolfe.freenode.net 08.54.23 *** Cleanup 08.54.23 *** Cleanup 08.54.23 *** Saving seen data "./dancer.seen" 08.54.23 *** Exit 08.54.25 *** Started Dancer V4.16 08.54.25 *** Connected to irc.freenode.net on port 6667 08.54.25 *** Logfile for #rockbox started 08.54.28 Mode "logbot :+i" by logbot 08.54.31 *** Server message 501: 'logbot :Unknown MODE flag' 08.54.32 Join logbot [0] (~rockbox@giant.haxx.se) 08.54.32 Join ze [0] (ze@ze.yi.org) 08.54.32 Join kevku [0] (x@2001:470:28:773::) 08.54.32 Join chkktri_ [0] (~user@83.149.48.18) 08.54.32 Join perrikwp [0] (~quassel@cpe-024-163-024-033.triad.res.rr.com) 08.54.32 Join Rob2223 [0] (~Miranda@p4FFF29D0.dip.t-dialin.net) 08.54.32 Join TheSeven [0] (~TheSeven@rockbox/developer/TheSeven) 08.54.32 Join pixelma [0] (quassel@rockbox/staff/pixelma) 08.54.32 Join amiconn [0] (quassel@rockbox/developer/amiconn) 08.54.32 Join advcomp2019 [0] (~advcomp20@unaffiliated/advcomp2019) 08.54.32 Join Keripo [0] (~Keripo@CPE0022b0d4bdb7-CM001a6680d4fe.cpe.net.cable.rogers.com) 08.54.32 Join anewuser [0] (~anewuser@unaffiliated/anewuser) 08.54.32 Join GeekShadow [0] (~antoine@201.134.197.77.rev.sfr.net) 08.54.32 Join T44 [0] (~Topy44@89.207.248.89) 08.54.32 Join [Saint] [0] (~Saint]@unaffiliated/saint/x-8516940) 08.54.32 Join factor [0] (~factor@74.197.205.204) 08.54.32 Join Scromple [0] (~Simon@119.225.209.134) 08.54.32 Join plush [0] (~quassel@82.131.56.111.cable.starman.ee) 08.54.32 Join fs-bluebot [0] (~fs-bluebo@g226068208.adsl.alicedsl.de) 08.54.32 Join bluebrother [0] (~dom@rockbox/developer/bluebrother) 08.54.32 Join adnap [0] (~adnap@rrcs-71-42-140-57.sw.biz.rr.com) 08.54.32 Join mystica555_ [0] (~Mike@71-211-210-11.hlrn.qwest.net) 08.54.32 Join nosa-j [0] (~m00k@adsl-74-235-42-181.clt.bellsouth.net) 08.54.32 Join amithkk [0] (u4289@2buntu/writers/amithkk) 08.54.32 Join ender| [0] (~ender1@2a01:260:4094:1:42:42:42:42) 08.54.32 Join Xerion [0] (~xerion@5419A30B.cm-5-2c.dynamic.ziggo.nl) 08.54.32 Join Sundiver [0] (~angel@174-124-6-86.dyn.centurytel.net) 08.54.32 Join parafin [0] (parafin@paraf.in) 08.54.32 Join rasher [0] (~rasher@rockbox/developer/rasher) 08.54.32 Join FOAD [0] (~foad@unaffiliated/foad) 08.54.32 Join tah [0] (~thomas@aktaia.intevation.org) 08.54.32 Join TBCOOL [0] (~tb@c-c63471d5.09-42-73746f22.cust.bredbandsbolaget.se) 08.54.32 Join bug2000 [0] (~bug@unaffiliated/bug2000) 08.54.32 Join fyrestorm [0] (~nnscript@cpe-24-90-84-81.nyc.res.rr.com) 08.54.32 Join scorche [0] (~scorche@rockbox/administrator/scorche) 08.54.32 Join ps-auxw [0] (~arneb@2001:470:c807:0:1532:4e5f:2ad3:4123) 08.54.32 Join scanf [0] (~x32@unaffiliated/scanf) 08.54.32 Join beta2k [0] (~Beta2K@d24-36-128-84.home1.cgocable.net) 08.54.32 Join remlap [0] (~Patrick@190.28.169.217.in-addr.arpa) 08.54.32 Join tmr [0] (jake@irc.turha.org) 08.54.32 Join JdGordon_ [0] (~jonno@rockbox/developer/JdGordon) 08.54.32 Join CIA-88 [0] (~CIA@cia.atheme.org) 08.54.32 Join Guinness` [0] (Slayer@c-68-55-111-159.hsd1.va.comcast.net) 08.54.32 Join mc2739 [0] (~mc2739@rockbox/developer/mc2739) 08.54.32 Join Poodlemastah [0] (~Poodlemas@h-241-205.a218.priv.bahnhof.se) 08.54.32 Join funman [0] (~fun@rockbox/developer/funman) 08.54.32 Join bzed [0] (~bzed@devel.recluse.de) 08.54.32 Join jhMikeS [0] (~jethead71@rockbox/developer/jhMikeS) 08.54.32 Join antil33t| [0] (~Ahurhurr@101.98.150.103) 08.54.32 Join froggyman [0] (~froggyman@unaffiliated/froggyman) 08.54.32 Join tchan [0] (~tchan@lunar-linux/developer/tchan) 08.54.32 Join Rondom [0] (~rondom@2a01:488:66:1000:b24d:4f2f:0:1) 08.54.32 Join zu_ [0] (~zu@ks387228.kimsufi.com) 08.54.32 Join maraz [0] (maraz@kapsi.fi) 08.54.32 Join kkit [0] (~quassel@li135-248.members.linode.com) 08.54.32 Join thegeek_ [0] (~thegeek@87.37.34.95.customer.cdi.no) 08.54.32 Join GodEater [0] (~bibble@rockbox/staff/GodEater) 08.54.32 Join Bagder [241] (~daniel@rockbox/developer/bagder) 08.54.32 Join crwl [0] (~crwlll@dsl-jklbrasgw1-ffb9c300-103.dhcp.inet.fi) 08.54.32 Join Galois [0] (djao@efnet-math.org) 08.54.32 Join ack [0] (~ack@mingbai.org) 08.54.32 Join pjm0616 [0] (~user@114.200.203.101) 08.54.32 Join sinthetek [0] (~sinthetek@unaffiliated/sinthetek) 08.54.32 Join Zambezi [0] (Zulu@unaffiliated/zambezi) 08.54.32 Join preglow [0] (thomj@tvilling2.pvv.ntnu.no) 08.54.32 Join guymann [0] (~charles@69.182.30.160) 08.54.32 Join nomada [0] (~nomada@irc.consciente.de) 08.54.32 Join lembas [0] (toastin@inafire.com) 08.54.32 Join soap [0] (~soap@rockbox/staff/soap) 08.54.32 Join eintopf|28c3 [0] (~eintopf@zzz.strace.org) 08.54.32 Join tmzt [0] (~tmzt@76.244.152.58) 08.54.32 Join Slasheri [0] (miipekk@rockbox/developer/Slasheri) 08.54.32 Join n17ikh [0] (~peter@c-174-56-150-44.hsd1.sc.comcast.net) 08.54.32 Join qnm [0] (~qnm@2001:44b8:3110:f300:208:9bff:fec0:179a) 08.54.32 Join Torne [0] (~torne@rockbox/developer/Torne) 08.54.32 Join kugel [0] (~kugel@rockbox/developer/kugel) 08.54.32 Join ruskie [0] (ruskie@sourcemage/mage/ruskie) 08.54.32 Join jordan`` [0] (~gromit@2001:660:3302:2826:225:90ff:fe20:d9a8) 08.54.32 Join Misanthropos [0] (~Misanthro@testomat.ee.ethz.ch) 08.54.32 Join Unhelpful [0] (~quassel@rockbox/developer/Unhelpful) 08.54.32 Join lmh [0] (lmh@nat/redhat/x-akwpetrhgkztlaee) 08.54.32 Join Barahir [0] (~Barahir@fb08schindler24.anorg.chemie.uni-giessen.de) 08.54.32 Join topik [0] (awesome@wtf.grmpf.org) 08.54.32 Join jae [0] (~jae@dedicated.jaerhard.com) 08.54.32 Join Farthen [0] (~Farthen@2a01:4f8:101:2a4:0:bc28:b2e1:9) 08.54.32 Join Zoiah [0] (zoiah@matryoshka.zoiah.net) 08.54.32 Join polemon [0] (mcp@polemon.org) 08.54.32 Join orzo [0] (~joe@ps38852.dreamhost.com) 08.54.32 Join Bawitdaba [0] (~Sphinx@cpe-184-153-55-166.nycap.res.rr.com) 08.54.32 Join yosafbridge [0] (~yosafbrid@li125-242.members.linode.com) 08.54.32 Join knittl [0] (~knittl@unaffiliated/knittl) 08.54.32 Join trompette [0] (~bob@punch.chezmerlet.net) 08.54.32 Join dionoea [0] (~dionoea@videolan/developer/dionoea) 08.54.32 Join linuxguy3 [0] (~timj@24-148-61-208.c3-0.lem-ubr1.chi-lem.il.cable.rcn.com) 08.54.32 Join alexbobp [0] (~alex@108.60.198.57) 08.54.32 Join mikroflops [0] (~yogurt@h-34-156.a238.priv.bahnhof.se) 08.54.32 Join nsx [0] (jm@epicsol.org) 08.54.32 Join ukleinek [0] (~ukl@2001:6f8:1178:2:21e:67ff:fe11:9c5c) 08.54.32 Join simabeis [0] (~simabeis@lobmenschen.de) 08.54.32 Join gevaerts [0] (~fg@rockbox/developer/gevaerts) 08.54.32 Join desowin [0] (~desowin@ip-69-162-133-251.static.chi2.systeminplace.net) 08.54.32 Join Utchybann [0] (~Utchy@rps6752.ovh.net) 08.54.32 Join freqmod [0] (~quassel@2001:700:300:1430:226:18ff:fe82:1a24) 08.54.32 Join ved [0] (~ved@2001:41d0:1:5914::2) 08.54.32 Join Naked [0] (~naked@naked.iki.fi) 08.54.32 Join ranmachan [0] (~ranma@2a01:4f8:130:9321::2) 08.54.32 Join Elfish [0] (amba@2a01:4f8:100:90a1:abc:abc:abc:abc) 08.54.32 Join mystica555 [0] (~mystica@mystica.mobi) 08.54.32 Join rjg [0] (~robert@odie.tomelliott.net) 08.54.32 Join SynrG [0] (~synrg@debian/developer/synrg) 08.54.32 Join martii [0] (martii@sokrates.zagrodzki.net) 08.54.32 Join aevin [0] (eivindsy@unaffiliated/aevin) 08.54.32 Join scorche|sh [0] (~scorche@squisch.net) 08.54.32 Join Staphylo [0] (~Staphylo@mareo.fr) 08.54.32 Join efyx [0] (~efyx@lap34-1-82-225-185-146.fbx.proxad.net) 08.54.32 Join @ChanServ [0] (ChanServ@services.) 08.54.32 Join rudi_s [0] (~simon@austria125.server4you.de) 08.54.32 Join Lalufu [0] (~sun@unaffiliated/lalufu) 08.55.06 Quit Scromple (Read error: Connection reset by peer) 08.56.21 Join ender` [0] (~ender@foo.eternallybored.org) 09.10.32 Quit chkktri_ (Ping timeout: 252 seconds) 09.23.12 Join stoffel [0] (~quassel@pD9E415C0.dip.t-dialin.net) 09.32.13 Join tails___ [0] (~user@ip-78-139-196-175.danet.in) 09.48.28 Quit tails___ (Ping timeout: 240 seconds) 10.01.21 Join bluefoxx [0] (fuzzylomba@S0106e0cb4e0a6d8a.vs.shawcable.net) 10.02.32 Join tails___ [0] (~user@83.149.48.113) 10.02.45 Nick tails___ is now known as tails_ (~user@83.149.48.113) 10.05.15 Quit factor (Read error: Connection reset by peer) 10.09.10 Quit T44 (Ping timeout: 244 seconds) 10.11.45 Quit ze (Ping timeout: 252 seconds) 10.14.24 Join dv_ [0] (~quassel@chello080108009040.14.11.vie.surfer.at) 10.21.55 Join factor [0] (~factor@74.197.205.204) 10.33.23 Join bertrik [0] (~bertrik@rockbox/developer/bertrik) 10.36.07 Join pamaury [0] (~quassel@vit94-1-82-67-248-70.fbx.proxad.net) 10.36.08 Quit pamaury (Changing host) 10.36.08 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 10.36.13 Join lorenzo92 [0] (~chatzilla@host64-44-dynamic.50-82-r.retail.telecomitalia.it) 10.36.32 # kugel: 25 hours for the R0 ;) 10.36.46 # kugel: quite impressive...isn't it? 10.37.24 Quit lorenzo92 (Client Quit) 10.44.47 Join ze [0] (ze@ze.yi.org) 10.48.28 # what capacity is the battery? 10.49.53 # <[Saint]> I wanted to ask that too, but he left immediately. 10.54.28 *** Saving seen data "./dancer.seen" 10.57.33 Quit Keripo (Ping timeout: 264 seconds) 10.59.22 Quit bluefoxx (Ping timeout: 252 seconds) 11.10.30 Join bluefoxx [0] (fuzzylomba@S0106e0cb4e0a6d8a.vs.shawcable.net) 11.17.28 Quit bluefoxx (Ping timeout: 240 seconds) 11.17.42 Join n1s [0] (~n1s@rockbox/developer/n1s) 11.19.44 Join bluefoxx [0] (FuzzyLomba@S0106e0cb4e0a6d8a.vs.shawcable.net) 11.24.54 Quit stoffel (Remote host closed the connection) 11.25.03 Join Topy44 [0] (~Topy44@tum-party-visitors.vipri.net) 11.27.07 Join lebellium [0] (~chatzilla@i02m-212-194-176-149.d4.club-internet.fr) 11.29.12 Quit sinthetek (Ping timeout: 276 seconds) 11.29.25 Join stoffel [0] (~quassel@pD9E415C0.dip.t-dialin.net) 11.32.32 # meh, after a silly spree of "make-local-things-static" in jpeg_decoder.c, I suddenly get: ‘bs.get_buffer’ may be used uninitialized in this function 11.40.22 Join sinthetek [0] (~sinthetek@unaffiliated/sinthetek) 11.42.35 # bertrik, isn't that a good thing? 11.42.53 Quit tails_ (Ping timeout: 252 seconds) 11.45.55 # I guess so ... but I'm not familiar enough with this code to really decide if it's harmful or not 11.46.09 # <[Saint]> Errors aren't so fun...but, why was said spree "silly"? 11.47.15 # [Saint], it doesn't really solve a known bug, just tidies things up a bit 11.47.51 # <[Saint]> Which, from some code I've laid eyes on...is very un-silly. :) 11.52.21 # bertrik: from a quick look it looks ok but an init to 0 where the other fields of the struct are inited shouldn't hurt 11.53.17 # n1s, yes that's what I thought too, I'll try if jpeg still works after this 11.54.39 Quit Topy44 (Ping timeout: 255 seconds) 11.55.11 # yeah, it calls the check_bit_buffer function before get_bits or peek_bits everywhere which then shifts in new data if there isn't tenough left and the bits_left field is inited to 0 11.55.55 Quit thegeek_ (Read error: Connection reset by peer) 11.56.05 Join thegeek [0] (~thegeek@87.37.34.95.customer.cdi.no) 11.56.24 # kind of odd that this would be uncovered by making stuff static since the struct is a local var anyway 11.56.54 # I guess gcc works in mysterious ways 11.57.01 # indeed :) 11.57.10 # <[Saint]> Guess?!? ;) 12.05.36 Join tails_ [0] (~user@ip-78-139-196-175.danet.in) 12.07.30 Join Topy44 [0] (~Topy44@tum-party-visitors.vipri.net) 12.16.23 Join einhirn [0] (Miranda@vpn10.rz.tu-clausthal.de) 12.22.25 Join liar [0] (~liar@clnet-p09-185.ikbnet.co.at) 12.28.33 Join lorenzo92 [0] (~chatzilla@host64-44-dynamic.50-82-r.retail.telecomitalia.it) 12.29.43 Join Misan [0] (~Misanthro@adsl-84-226-243-88.adslplus.ch) 12.29.58 Join Thra11 [0] (~thrall@87.114.177.46) 12.32.23 # New commit by 03bertrik (r31453): plugins: another round of making local things static and adding missing #includes 12.34.49 # r31453 build result: 0 errors, 50 warnings (bertrik committed) 12.35.00 # ai 12.38.24 Quit stoffel (Ping timeout: 252 seconds) 12.39.50 Quit einhirn (Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org) 12.40.28 # lorenzo92: nice :) 12.40.37 Quit Topy44 (Ping timeout: 240 seconds) 12.40.41 # kugel: hey 12.40.47 # kugel: yeah nice indeed 12.41.02 # kugel: BUT I have a bad news...the bench plugin recorded only 16 hours .( 12.41.07 # no clue why! 12.42.10 # can you post the file anyway? 12.42.19 # <[Saint]> What capacity is the battery? 12.43.20 # http://dl.dropbox.com/u/38710278/battery_bench.txt 12.43.24 Join user890104 [0] (Venci@31.211.134.13) 12.43.25 # 600 mAh 12.43.43 # it lasted 25 hrs, so about 24 mA of drain... 12.43.52 # lorenzo92: it says "reason: power off" 12.43.56 # strange 12.44.00 # kugel: I needed to do that 12.44.09 # otherwise it went under 3,450 12.44.17 # I tought it was dangerous 12.44.42 # kugel: anyway in some minutes I'll give you also the bench of charging 12.44.56 # 16:37:09, 59829, 007%, 00:-1, 3626, -, - 12.44.56 # --Battery bench ended, reason: power off-- 12.45.15 # it says it powered off at 3626mV 12.45.25 # yeah strange....I don't know why 12.45.30 # or it did lose 200mv very quickly :) 12.45.34 # nono 12.45.58 # I confirm: from midnight 27th to 1 am 28th 12.46.00 # :) 12.46.16 # then I needed to switch it off manually... 12.46.21 # I implemented that it should power off at 3450mV I thought 12.46.44 # eh I'm not sure it does... 12.47.35 # <[Saint]> Easy to test. 12.47.36 # New commit by 03bertrik (r31454): Fix warnings from r31453 12.48.01 # kugel: okay. Done with cahrging...now I switch rockbox off right? 12.48.18 # you can exit battery_bench in some way 12.48.30 # try to run it again 12.49.18 # r31454 build result: All green 12.50.02 # shit...# --File already present. Resuming Benchmark--# Battery bench run for Samsung YP-R0 version r31443M-111226# Rockbox has been running for 00:00:11--Battery bench ended, reason: power off-- 12.50.19 # no data at all :( 12.50.30 # lorenzo92: another bench, this time with backlight on all the time (brightness at the default value), would be nice 12.50.45 # lorenzo92: uhh :( 12.51.14 # kugel: I guess I did some mess with the build, could it be that I updated only the rockbox executable and not also plugins? 12.51.39 # that could be a problem 12.52.29 # <[Saint]> Don't the plugins just outright refuse to run if there's a missmatch making the build/plugin incompatible? 12.52.54 # only if you update the version defines proeprly 12.53.01 # <[Saint]> Ah. 12.54.30 *** Saving seen data "./dancer.seen" 12.54.40 # so I guess I'm wrong :)...anyway I will repeat these bench of course 12.55.03 # lorenzo92: do the one with backlight first 12.55.07 # so: one discharging, one charging, then discharging with backlight on right? 12.55.09 # okay! 12.55.12 Quit user890104 (Remote host closed the connection) 12.55.19 # it's enough to map voltage to percentage 12.55.22 # at level? default? 12.55.27 # yea 12.56.08 Quit bluefoxx (Quit: 5a 65 75 73 73 2d 73 6f 64 64 69 74 2d 66 75 63 6b 2c 20 49 27 6c 6c 20 62 65 20 62 61 63 6b 2e 2e 2e) 12.57.55 # kugel: ok. ready to start 13.03.33 Quit bug2000 (Ping timeout: 248 seconds) 13.05.22 Join bluefoxx [0] (fuzzylomba@S0106e0cb4e0a6d8a.vs.shawcable.net) 13.10.27 Join Sleepy_Coder [0] (majic@unaffiliated/sleepycoder/x-938672) 13.10.32 # Oh hey I found it :D 13.11.05 # <[Saint]> The internet? 13.11.26 # So I'm a picky person to buy things for. Dad surprised me with a Sansa Clip Zip on Christmas and I realized that it was missing 2 things I had hoped for: a more common USB plug (the one on the Clip+ not the Clip Zip) and the ability to transfer files from the SD card to the internal HD 13.12.00 # So my question for #rockbox is what would be considered the more avaluable player from the modifications perspective: Sansa Clip+ or Sansa Clip Zip 13.12.18 # I don't really see the need for the color screen of the Clip Zip. Who cares about album art. :\ 13.12.30 # I just really dislike that slim uncommon micro usb variant of a plug. 13.12.50 # <[Saint]> Its actually the opposite of uncommon. 13.13.01 # <[Saint]> Its *very* common ;) 13.13.25 # I find the micro usb port on the Clip+ to be more common. A lot of my wifi cards have that one instead of the one on the Clip Zip... but hmm. 13.13.49 # I've been debating if I should just ignore the internal HD since I don't want to be bothered keeping that one unique plug with the device all the time and just using the microsdhc slot. 13.14.18 # Aside from the display, it seems like all the features of the Clip Zip are being added to Rockbox in support of the Clip+ 13.14.40 # <[Saint]> Ok...right. I've not laid eyes on the ClipZip, I assumed you actually meant standard microUSB sorry. 13.15.02 # I see the DRM-free AAC playback is supported (with Rockbox) on the Clip+, I see that RDS radio funcionality is "in the workd"... I'm just not sure if there is anything about the Clip+ (aside from the unnecessary color screen) that I would really want over the Clip+ 13.15.09 # in the works* :> 13.15.41 # Hoping that someone knows something secretly awesome about the Clip Zip to make me want to keep it instead of going out and buying the Clip+ instead (and I talk too much, yes) 13.16.55 Join bug2000 [0] (~bug@DSL212-235-89-188.bb.netvision.net.il) 13.16.55 Quit bug2000 (Changing host) 13.16.55 Join bug2000 [0] (~bug@unaffiliated/bug2000) 13.17.26 # <[Saint]> I wouldn't bother finding a Clip+, personally. You've got a Clip Zip, it has a functional port... 13.17.44 # http://en.wikipedia.org/wiki/SanDisk_Sansa#Sansa_Clip_Zip -- 1.1" oled display, better physical button layout (which I really like but wouldn't be hurt to give up), (a stopwatch????), RDS radio support, DRM-free AAC playback 13.18.01 # Well see I had a Clip+ a couple months ago when I was much poorer and I took it back because I couldn't justify at the time spending $40 13.18.03 # the Zip has a shitty display contrary to the Clip+ ;) 13.18.16 # Yeah, I find the Clip+ much clearer to read, even if the res is much smaller 13.18.23 # monochrome displays are sexy 13.18.47 # I mean I wish the battery life were better for constant FLAC, but what can you do. :\ 13.18.58 # 15-hour battery life @ 128kbps mp3, afaik 13.19.59 # <[Saint]> Check the runtime stats page...I'm pretty sure even the old data on there paints a much better picture of runtime for Clip+ 13.20.03 # Does anyone happen to know if Rockbox adds the ability to transfer files from the the microsdhc card to the internal hd? That would really make all this worth it. 13.20.20 # <[Saint]> Yes, it does. 13.20.30 # Okay thank you :} 13.21.29 # Also I would just like to say that even though I talk a lot I'm happy to see that not all freenode support channels are filled with bureacratic elitists more willing to shun than answer questions <3 13.21.37 # * Sleepy_Coder begins absorbing the wiki 13.23.15 # Sleepy_Coder: the manual might be more useful ;) 13.24.48 # lorenzo92: hope it works this time 13.24.49 # <[Saint]> The wiki *should* have runtime data and codec comparisons, though. Not sure the manual includes that info. 13.25.33 # Shush, you're so distracting, geniuses >8| 13.25.57 # kugel: well lebellium noticed that I still have an issue with languages in my build, so I don't know. I leave it testing, then I will rebuild the entire svn 13.27.39 Quit bug2000 (Read error: Operation timed out) 13.28.14 # Sleepy_Coder, I like the clip zip better than the clip+, but they're not that different actually, biggest difference is indeed the display 96x96x16 for the clip zip and 128x64x1 for the clip+ 13.29.19 # kugel: I don't know this evening I'll be away...it is safe to leave r0 working? also if it doesn't shutdown automaticly? 13.29.31 # there should be an hw protection...isn't it? 13.30.19 # <[Saint]> Modern batteries generally handle deep discharge quite well. 13.31.49 # ;) 13.32.13 # http://download.rockbox.org/daily/manual/rockbox-sansaclipplus/rockbox-buildch12.html#x15-17600012.1.7 Now see this is just excessive. 13.32.15 # * bertrik doubts that without seeing evidence 13.32.50 # bertrik: I had not noted the exact differences in dimensions of their screens, I had only been thinking of the color aspect. That makes it clear, thank you, I definitely need the Clip+ 13.33.11 # When i was using the Clip Zip earlier I was annoyed that a lot of my songs were off the screen because they were so long in title length 13.34.04 # Have you tried rockbox on the zip already? 13.34.24 # I have not, I was deciding if I should keep it or find a Clip+ 13.34.48 # (which technically isn't hard, places around here have it in stock as one of those "old mp3 players they can't get rid of" 13.35.11 # It seemed like someone talking earlier had been hinting that they were relatively rare now :> 13.35.19 Quit lorenzo92 (Quit: ChatZilla 0.9.88 [Firefox 8.0/20111115183813]) 13.36.32 # I really wish I could find the info on runtime under various formats 13.36.46 # * Sleepy_Coder is having trouble navigating rockbox' site :x 13.37.33 Join dfkt [0] (dfkt@unaffiliated/dfkt) 13.37.37 # http://www.rockbox.org/wiki/CodecPerformanceComparison oh there we are 13.37.41 # we don't really have *one true standard* for doing runtime benchmarks 13.38.56 # Just needed a rough estimate :] 13.39.12 Quit sinthetek (Ping timeout: 276 seconds) 13.42.59 # most common codecs should be fine , he aac and high compression ape are the really slow ones 13.43.08 # <[Saint]> Fwiw, your track titles will be off the screen on a Clip+ also. 13.43.34 # <[Saint]> An 8pt font only allows 16 chars max on Clip+ 13.44.09 # <[Saint]> Your track titles are likely longer, and will have to scroll. 13.44.12 Join bug2000 [0] (~bug@unaffiliated/bug2000) 13.44.23 # Hmm looks like I had misread, I thought Rockbox added RDS radio to the Clip+ also, which with the proprietary firmware is only added on the Clip Zip 13.44.45 # * Sleepy_Coder doesn't know exactly what RDS radio is though :\ So not sure if want. 13.45.35 # <[Saint]> Its embedded metadata, in radio. Things like the station name, track title, etc. 13.47.06 # oh so it's not something hardware-dependant 13.47.09 # that's good to hear 13.47.11 # :] 13.47.23 # It is 13.47.32 # The tuner chip has to support it 13.47.32 # <[Saint]> It is hardware dependant. 13.47.43 # this saddens me :< 13.48.11 # brb, cats are revolting again 13.48.47 Quit factor (*.net *.split) 13.50.41 Join sinthetek [0] (~sinthetek@unaffiliated/sinthetek) 13.54.51 Join factor [0] (~factor@74.197.205.204) 13.59.13 # Sleepy_Coder: Clip+ has mini-USB, Clip zip has micro-USB. Both are official standards, but mini-USB is deprecated nowadays. That's very likely the reason why Sandisk switched to micro-USB for the Clip zip 14.05.43 Quit ender` (Quit: The problem with political jokes is they get elected. -- Henry Cate, VII) 14.13.32 Join ender` [0] (~ender@foo.eternallybored.org) 14.18.39 Quit liar (Read error: Connection timed out) 14.20.47 Quit Misan (Ping timeout: 244 seconds) 14.32.55 Quit bluefoxx (Ping timeout: 240 seconds) 14.33.08 Join Misan [0] (~Misanthro@adsl-89-217-195-136.adslplus.ch) 14.40.32 Quit kevku (Quit: KVIrc 4.0.4 Insomnia http://www.kvirc.net/) 14.43.05 # amiconn: oic :o 14.43.16 # I have a lot of mini-USB cords, what's why I was fussing over this 14.43.38 # all but one of my wifi cards (7) uses mini-usb on their end and regular usb on the other 14.44.00 # the exception to the norm actually has a micro-usb cord, so yaaaay 14.44.15 # I don't have to worry about losing the micro-usb cord for the clip zip 14.46.47 # still can't decide. rds radio is very useful when you want to go home and torrent what you heard on the radio later 14.46.59 # but the clip+ has 32 more pixels (horizontally) to work with 14.47.17 # that's really all it comes down to for me. :\ 14.49.49 # don't expect *too* much from RDS, many stations put all kind of random blah in the RDS stream (at least here in the netherlands) 14.51.20 # the public stations generally behave w.r.t. RDS, showing the station name and program name correctly without interleaving it with other messages 14.51.49 # hmm. 14.52.10 # would be fun to make your own fm transmitter and spam nearby rds-capable devices with stuff. 14.52.23 # "Eat at Joe's Crab Shack" 14.52.24 # etc. 14.52.43 # <[Saint]> Until you were arrested. 14.52.58 # bertrik: did you try if pf still works? 14.53.13 # kugel, no 14.53.18 # IIRC someone already tried static-ifying it and it didnt work anymore 14.53.36 Quit Zambezi (Read error: Connection reset by peer) 14.53.54 # Bagder: ping 14.54.18 # [Saint]: They sell FM-transmitters for devices here all the time that are capable of outtaking the radio stations for 100 feet... I don't see how it would be illegal :> But perhaps that is a discussion for another time/channel ;< 14.54.33 *** Saving seen data "./dancer.seen" 14.55.07 # http://www.amazon.com/SanDisk-Sansa-Player-Refurbished-Packaging/dp/B004CMI2UC <3 14.56.22 Join Zambezi [0] (~Zulu@bnc.fran.dotbnc.se) 14.56.46 # yeah move that chat to #rockbox-community or something please 14.58.20 Join jlbiasini [0] (~metaphys@d86-32-96-55.cust.tele2.at) 14.59.25 # kugel, browsing albums still seems to work as before, I'm now rebuilding the cache and see if that still works 15.03.24 Quit Misan (*.net *.split) 15.03.38 Join Misan [0] (~Misanthro@adsl-89-217-195-136.adslplus.ch) 15.05.31 # do smaller sizes than 14 exist of the beautiful nimbus font? anyone knows of an inofficial version? 15.05.44 # s/14/10 15.05.47 # dfkt: I've remade the photo you gave me in svg. For a beginner I guess the result is not that bad. Anyway I need a few direction on svg file would you have a little time to help me? Obviously files in manual/rockbox_interface/images have a single layout text with all info regarding button on it. But I cannot found any layout for the player's picture itself... 15.06.23 # my image is in a layout 15.07.12 # do I have to transfert it into some backgroung? or is the image layout hidden? 15.13.07 Quit [Saint] (Remote host closed the connection) 15.13.55 Join [Saint] [0] (~Saint]@unaffiliated/saint/x-8516940) 15.22.33 Quit sinthetek (Ping timeout: 276 seconds) 15.23.14 Join bluefoxx [0] (FuzzyLomba@S0106e0cb4e0a6d8a.vs.shawcable.net) 15.34.20 Quit bluefoxx (Quit: rebooting...) 16.00.02 # ok I've got it: I have to import the image and then build my button on a layout 16.06.19 Join sinthetek [0] (~sinthetek@cpe-174-111-026-094.triad.res.rr.com) 16.06.19 Quit sinthetek (Changing host) 16.06.19 Join sinthetek [0] (~sinthetek@unaffiliated/sinthetek) 16.26.37 Join captainkwel [0] (~jason@207-237-110-248.c3-0.nyr-ubr2.nyr.ny.cable.rcn.com) 16.26.56 Join nosa [0] (~m00k@adsl-74-235-79-60.clt.bellsouth.net) 16.27.48 Quit nosa-j (Ping timeout: 240 seconds) 16.27.48 Nick nosa is now known as nosa-j (~m00k@adsl-74-235-79-60.clt.bellsouth.net) 16.28.29 Join liar [0] (~liar@clnet-p09-185.ikbnet.co.at) 16.34.27 Join Horscht [0] (~Horscht@p5DD57D7E.dip.t-dialin.net) 16.34.27 Quit Horscht (Changing host) 16.34.27 Join Horscht [0] (~Horscht@xbmc/user/horscht) 16.35.12 Join Topy44 [0] (~Topy44@tum-party-visitors.vipri.net) 16.42.17 Join chkktri [0] (chkktri@unaffiliated/chkktri) 16.42.40 # test 16.43.00 # test 16.43.12 # chkktri: SUCCESS 16.43.18 # <[Saint]> #test 16.43.37 Join chkktri_ [0] (chikakitaa@ip-78-139-196-175.danet.in) 16.43.41 # damn 16.43.51 # and i thought why nothing sends =\ 16.44.03 # forgot to join channel =_= 16.44.42 # . 16.44.47 # exit 16.44.51 Quit chkktri (Client Quit) 16.44.55 # uh 16.45.12 # console version of xcat ialmost unusable 16.45.17 # xchat* 16.45.43 # <[Saint]> You know what channel you're in, yeah? 16.45.52 # whops 16.45.54 # sorry 16.46.24 # <[Saint]> No worries, just checking. :) 16.47.38 Quit liar (Read error: Connection timed out) 16.54.37 *** Saving seen data "./dancer.seen" 16.54.44 Quit [Saint] (Quit: I know its a sin to kiss and swallow.) 16.59.59 Join [Saint] [0] (~Saint]@unaffiliated/saint/x-8516940) 17.06.15 # New commit by 03theseven (r31455): iPod Classic: HDD endianness change ... 17.08.07 # r31455 build result: All green 17.11.34 # TheSeven: how's USB on classic now ? 17.12.13 # funman: still flaky 17.12.17 # TheSeven: btw pamaury had written a PIO driver for amsv2, and HID was working fine 17.12.26 # no idea why though - doesn't seem to be much worse than before your patch 17.12.34 # seems like this might actually be coming from the ATA layer 17.21.16 # is emCORE the only bootloader? 17.22.58 # until now yes 17.23.24 # I hope this will change one day, but so far we haven't found a sane way to run code on these devices 17.23.47 # the only way is to reflash the NOR (boot) flash using DFU mode 17.36.52 # funman: HID works in pio mode btu 17.36.57 # but not in dma mode ? 17.38.13 Quit sinthetek (Ping timeout: 248 seconds) 17.38.50 # no 17.39.10 # pamaury: i didnt test pio though but you said it did 17.39.20 # HID doesnt work on nano2g either (using dma) 17.44.48 # pamaury: not sure if the linux driver can use dma at all (it has dma code though) 17.45.00 # not sure how we could use PIO for interrupt endpoints also 17.49.09 Join benedikt93 [0] (~benedikt9@unaffiliated/benedikt93) 17.51.53 Join sinthetek [0] (~sinthetek@cpe-174-111-026-094.triad.res.rr.com) 17.51.54 # why not ? interrupt is like bulk 17.51.56 Quit sinthetek (Changing host) 17.51.56 Join sinthetek [0] (~sinthetek@unaffiliated/sinthetek) 17.57.14 Quit sinthetek (Ping timeout: 268 seconds) 17.59.43 Quit dfkt (Quit: -= SysReset 2.55=- Sic gorgiamus allos subjectatos nunc.) 18.00.28 # no 18.00.35 # bulk works and interrupt doesnt 18.03.39 Quit factor (Read error: Connection reset by peer) 18.07.08 Join user890104 [0] (~Venci@213.226.63.151) 18.14.36 Join marcol07 [0] (~4e628860@www.haxx.se) 18.14.37 # hi guys 18.15.33 # funman: that's really strange because there is really no difference 18.16.03 # gevaerts hypothetized that the bug could be im hid driver or somewhere else 18.16.24 # can i ask u something? i just uploaded theme but i forgot to write some description. is there any chance to update it? 18.17.05 # marcol07: if you upload it again with the same theme name and the same email address, it will update it 18.17.08 Join y4n [0] (y4n@unaffiliated/y4ndexx) 18.17.53 # ok thanks 18.19.39 Join factor [0] (~factor@74.197.205.204) 18.24.05 Quit benedikt93 (Quit: Bye ;)) 18.24.44 Quit user890104 (Ping timeout: 252 seconds) 18.28.11 Join sinthetek [0] (~sinthetek@unaffiliated/sinthetek) 18.31.37 Join remlap1 [0] (~Patrick@190.28.169.217.in-addr.arpa) 18.32.23 Quit remlap1 (Client Quit) 18.32.48 Quit remlap (Ping timeout: 240 seconds) 18.38.34 Quit marcol07 (Quit: CGI:IRC (EOF)) 18.38.51 Join marcol07 [0] (~4e628860@www.haxx.se) 18.50.29 Quit sinthetek (Ping timeout: 248 seconds) 18.54.40 *** Saving seen data "./dancer.seen" 18.55.13 # funman, perhaps you can have a look at the hack that is currently still used for clip zip with lcd type 0? 18.59.16 # also, I still wonder if we also need to swap the R and B intensities in function oled_brightness (because we also swapped from RGB to BGR as pixel format) 19.01.10 # bertrik: rather quickly, i didnt find lcd code in OF 19.01.25 # or rather i found it but not the drawing code 19.01.50 # perhaps there s a delay needed for the row/col to update properly 19.03.54 Join rafazafar [0] (~74c50628@www.haxx.se) 19.04.17 # hey guys/gals 19.05.09 # why not port rockbox for Android/iOS aswell? 19.05.17 Quit rafazafar (Client Quit) 19.05.26 # rafazafar: works on android already. interested in doing the iOS port yourself? 19.05.57 Join sinthetek [0] (~sinthetek@unaffiliated/sinthetek) 19.08.27 # funman, my memory is a bit fuzzy, I think I found an lcd_update_rect-like function, but almost no calls to it 19.08.55 # pamaury: any news from the bootloader? Anyway my image for fuze+ are ready at the end, any suggestion? http://dl.dropbox.com/u/43468173/images%20Fuzeplus/sansafuzeplus-front.svg, http://dl.dropbox.com/u/43468173/images%20Fuzeplus/sansafuzeplus-front.png, http://dl.dropbox.com/u/43468173/images%20Fuzeplus/sansafuzeplus-front.pdf 19.09.13 # bertrik: iirc some of the calls came from other 'modules' , not the first firmware block 19.09.32 # yes, sounds plausible 19.10.22 # I only looked at the main firmware block and the one that does radio, but didn't look into cross-links between them 19.11.12 # this took me the whole day but they looks ok I think 19.11.59 Join GermanMushroom [0] (~c@s5146db6a.adsl.wanadoo.nl) 19.12.36 Join stoffel [0] (~quassel@pD9E415C0.dip.t-dialin.net) 19.13.39 Quit stoffel (Remote host closed the connection) 19.14.07 Quit factor (Ping timeout: 240 seconds) 19.14.11 Join stoffel [0] (~quassel@pD9E415C0.dip.t-dialin.net) 19.24.04 Quit sinthetek (Ping timeout: 244 seconds) 19.28.16 Join liar [0] (~liar@clnet-p09-185.ikbnet.co.at) 19.35.21 Quit bluebrother (Disconnected by services) 19.35.23 Join bluebrother^ [0] (~dom@rockbox/developer/bluebrother) 19.36.23 Quit marcol07 (Quit: CGI:IRC (EOF)) 19.37.30 Quit fs-bluebot (Ping timeout: 244 seconds) 19.38.36 Join fs-bluebot [0] (~fs-bluebo@g224237049.adsl.alicedsl.de) 19.44.38 # TheSeven: alert! splashf() 19.44.43 # from firmware is a nogo 19.47.21 # heh, that's what was suggested to me by some people back in october... 19.47.23 # jlbiasini: looks nice 19.47.26 # how else could this be handled? 19.47.45 # jlbiasini: perhaps the bottom of the square can move a bit to the top or be rounded? 19.48.26 Join dfkt [0] (dfkt@unaffiliated/dfkt) 19.48.26 # TheSeven: panicf() ? 19.49.24 # check ata_swap in apps and issue a splash from there 19.49.32 # or issue no splash at all :) 19.50.51 # funman: it isn't fatal 19.51.05 # kugel: hm, where in apps would I check that to notify the user on boot? 19.51.20 # i tried to keep that hack local to that file 19.52.42 # funman: you mean on the grid? 19.53.05 # jlbiasini: yes the grid is a bit out of the player 19.53.35 # I thougt it would better like that: one can see this is a virtual grid 19.53.43 # TheSeven: main.c perhaps 19.53.58 # compat code isn't necessarily a hack 19.54.28 # [23815.060745] BUG: unable to handle kernel NULL pointer dereference at 0000000000000008 19.54.31 # [23815.060760] IP: [] sd_revalidate_disk+0x30/0x2a0 19.55.27 Join remlap [0] (~Patrick@190.28.169.217.in-addr.arpa) 19.55.36 # with clipv1 19.55.38 # I'm unsure if a warning is necessary at all, though. Especially since it recommends upgrading to a not-yet-existing emCORE version which will format the drive 19.55.56 # yeah that seems overkill 19.55.58 # people might prefer bad performance over an empty disk 19.57.52 # I would probably remove the splash and make it a panicf after some time if you really want to remove the compat code 20.01.23 Quit y4n (Quit: HOLY SHIT! WE'RE ALL JUST LIVING ON A GINORMOUS FUCKING SPINNING ROCK FLOATING THROUGH SPACE CIRCLING A BIG FUCKING BALL OF FIRE!!!) 20.04.31 # funman: right, after mofication it's nicer (same adress if you want to check 20.06.35 # indeed looks better 20.08.39 # * TheSeven wonders how many people are even affected by this 20.09.53 # and the patch has already been applied to emcore, it's just that there hasn't been any official release since that point 20.10.05 # (but this will happen during the next week) 20.10.13 # or rather this week 20.13.45 Quit stoffel (Ping timeout: 276 seconds) 20.16.03 # dfkt, It failed >.> Still crashes. 20.20.12 # bug2000: ping 20.20.23 # funman: pong 20.20.26 # was the crash in skin_render_line ? 20.20.40 # funman, I unno. Same error it seems to me. 20.20.57 # Same than what? I was talking about the crash reported on flyspray 20.21.18 # funman, If they say so. I only know the code I got from rockbox. 20.21.27 # funman, dfkt told me to try fresh start. So I've done full format and reinstalled it. But no go :\ 20.22.01 # what is FS# again? 20.22.54 # FS#12475 20.22.55 # http://www.rockbox.org/tracker/task/12475 3Crash while playing audio (bugs, unconfirmed) 20.23.38 # funman, Also didn't manage to be here when JdGordon_ is here. 20.23.40 # New commit by 03funman (r31456): remove superfluous ifdef 20.24.14 # JdGordon_ is in australia so timezone might conflict 20.25.34 # r31456 build result: All green 20.29.48 # JdGordon_: FS#12475 needs your advice 20.29.48 # http://www.rockbox.org/tracker/task/12475 3Crash while playing audio (bugs, unconfirmed) 20.31.21 Quit GermanMushroom (Read error: Connection reset by peer) 20.32.16 # funman, He is away for sleeping. 20.32.25 # bug2000: we know that 20.32.38 # gevaerts, Whats the time in australia now anyway? 20.32.39 # He will probably wake up again at some point though 20.32.46 # gevaerts, Hopefully. 20.33.37 # gevaerts, I still find waking up weird. Becasue it feels like you just went to sleep except everything moved around you. 20.33.53 # * gevaerts looks at the topic 20.34.09 Quit liar (Read error: Connection timed out) 20.35.29 # gevaerts / funman; Anything else I can try to help with on debugging this? 20.37.06 # yes, don't forget to ask JdGordon_ to look at it 20.37.42 # funman, Might be tad complex for me to do that. 20.38.36 # funman, How'd you manage to crash it? Which player did you crash? 20.39.43 # funman: I also understood how to simplify curves and now this is totally smooth 20.40.01 # well images are ready 20.40.14 # Now I can go on the manual 20.40.50 # funman, No ponies in pony. 20.42.10 # bug2000: i wrote the details in the FS 20.42.40 # funman, I ment. What did you do for it to happen, not what is the data abort location. 20.45.29 # New commit by 03funman (r31457): USB HID: cosmetics / simplifications ... 20.45.54 # bug2000: that detail is in FS as well 20.46.11 # funman, O_O. How did I miss that part of the line? 20.46.54 # funman, Anyway, just tried DFKT theme with a different font [for sake of trying]. Nothing changes. 20.47.03 # funman, Thanks again for your support about it. Good night. 20.47.21 # r31457 build result: All green 20.48.58 # i see that the sansa fuze+ is mostly suported, all except the installer support. i was told yesterday that it was added, but not yet updated. i was wondering if i should go and buy this or if i should find the original fuze. is there anything thats not realy suported? 20.51.03 # i found both on overstock for the same price 20.51.11 # nosa-j, USB plugging. 20.51.20 # ahh okay thanks 20.51.22 # hmm 20.51.24 # huh? 20.51.39 # As far as I know USB works fine on the fuze+ 20.51.49 # i see 20.52.46 # gevaerts, Really? For what I've tracked SamsaV2 has no USB file transfer. 20.52.54 # gevaerts, It reverts to OF for that. 20.53.00 # bug2000: fuze+ isn't AMSv2 20.53.29 Quit soap (Remote host closed the connection) 20.53.29 # gevaerts, Got the impression Clip+ is, so I thought it's the same. But in that case it means the fuze+ is better. 20.54.42 *** Saving seen data "./dancer.seen" 20.54.49 # and current builds have USB working jsut fine on amsv2 20.54.52 # usb file transfer works fine on clip+ 20.54.52 # rockbox usb works fine on the clip+ 20.54.55 # jinx :) 20.55.04 # team work! :) 20.55.43 # funman, Really? was the page I read outdated? 20.55.47 # * bug2000 goes to check the wiki again. 20.56.06 # dfkt, By the way, do you run your dfkt theme on the original clip or clip+? 20.56.07 # wiki's can't keep up with funman 20.56.23 # bug2000, if you use the current v4.0 bootloader and a current build, then you should have no issues 20.57.02 # bug2000, as i said, i only use my themes on all my players... and none of my players crash (2x clipv1, 2x clip+, 1x clip zip) 20.57.18 # dfkt, You really love the clips :P 20.57.25 # yep 20.57.48 # dfkt, So do I. Small, efficent and no weird usb port. 20.58.20 # nosa-j, http://www.rockbox.org/wiki/SansaFuzePlusPort 20.59.20 # As for my bad[?] information about USB; From 3.10 release log: USB is still too unstable on the FuzeV2?, ClipV2? and Clip+ and is disabled in this release 20.59.29 # That's 3.10 20.59.49 # And irrelevant for the fuze+ anyway 21.00.04 # You might it's fixed in the nightlys? Good to know. 21.00.16 # [And 3.10 isn't THAT old yet. Not even a month] 21.00.22 # We don't do nightly builds, but yes 21.00.37 # * gevaerts knows exactly how old 3.10 is. He's the one who did the release builds 21.00.54 # good stuff often comes soon after an official release 21.00.58 # Erm yeah. Incorrect term you are right. It's not nightly it's 2minutes realse 21.01.06 # topik, How unfair is that? 21.01.15 # it's not 21.01.22 # bug2000: you'd prefer buggy releases? 21.01.22 # it's in the next 21.01.42 # gevaerts, Acctaully I'm not sure why I moved to the stable ones. The unstable ones were fun. 21.02.37 # unstable in rockbox lingo is far from unusable 21.03.07 Join soap [0] (~soap@cpe-76-181-78-156.columbus.res.rr.com) 21.03.37 Quit soap (Changing host) 21.03.37 Join soap [0] (~soap@rockbox/staff/soap) 21.03.59 # * gevaerts would like to point out that "unstable" means something quite different in rockbox 21.05.03 # gevaerts, May I ask, if the bootloader was updated to support USB completly on those targets. Why was the Major Changes on the wiki not updated? Or is it not major? 21.05.40 # bug2000: you should ask funman 21.05.44 # wiki's can't keep up with funman 21.06.01 # * bug2000 laughs a bit. 21.06.07 # clip + or clip zip? 21.06.16 # both 21.06.35 # .. 21.06.46 # dfkt, How good is the Zip? Should I get one? [I managed to crack a bit the cover plastic of the screen on my v1] 21.06.55 # much more fun to fix problems than update documentation 21.07.05 # topik, True. True. 21.07.27 # clip zip is a clip+ with a color screen and micro usb 21.07.40 # the clip+/clipzip have very cheaply made cases 21.08.02 # in fact, i fried one wiping it with a barely dampened tissue 21.08.07 # not waterproof at all 21.08.12 # Oh yeah, did they get the hold sliver back onto the clipzip? 21.08.22 # no 21.08.22 # scanf, :( So the original is sturdier by that much? 21.08.32 # *slider 21.08.36 # no i think they are probably all that way 21.08.49 # bt i am abot to buy a new one i think 21.09.01 # clip+ for $21 or clip zip for $28 (USD) 21.09.04 # Why did they do something so annoying as removing the hold slider? 21.09.09 # clip zip feels more plastic-y than clip+ 21.09.56 # Please, try to keep this channel on-topic. People read backlogs, and they don't want to read speculation about why some manufacturer did something 21.10.10 # gevaerts, Yeah. Sorry. 21.10.34 # gevaerts, Got a bit sidetracked. 21.13.27 Quit soap (Quit: soap) 21.13.39 # extract from clip v2 manual: "The Clip v2 is available in multiple versions," I suppose this should be "The Clip is available in multiple versions..." 21.15.24 # hm, good point 21.15.47 # pamaury, funman: seems like there's timing involved with the classic usb issues 21.16.03 # adding splashf()s for debugging purposes makes it fail consistently 21.16.45 # jlbiasini: can you submit a bug report? This is pretty obviously wrong, but fixing it properly needs some thinking 21.17.14 # yes this is what I just saw... ok I will 21.18.27 Join markun [0] (~markun@rockbox/developer/markun) 21.22.54 Join Keripo [0] (~Keripo@CPE0022b0d4bdb7-CM001a6680d4fe.cpe.net.cable.rogers.com) 21.23.06 Join kevku [0] (x@2001:470:28:773::) 21.23.58 Join B4gder [0] (~daniel@81-235-141-52-no63.tbcn.telia.com) 21.23.58 Quit B4gder (Changing host) 21.23.58 Join B4gder [241] (~daniel@rockbox/developer/bagder) 21.24.57 # gevaerts: any idea what it means if I get a couple of "scsi inquiry 0" and "ums: set config" pairs (6 times total), but nothing else after that? 21.26.46 # TheSeven: is this related to a change to the ata driver? 21.27.01 # no, it seems to be related to a timing change 21.27.14 # gevaerts: done. However there is no clip specific section for bugs FS#12491 21.27.14 # http://www.rockbox.org/tracker/task/12491 3[clip v2] version is attached to the player name wich can lead to some uncoherence (bugs, unconfirmed) 21.27.26 # (before I added some logging it seemed to get through to some sector accesses at least) 21.27.42 # jlbiasini: good, because the issue isn't clip-specific. It also applies to fuze, c200 and e200 :) 21.27.55 # TheSeven: do you intend to fix the splashf usage? 21.28.19 # kugel: yes, but I'm not yet sure what's the best way to handle this 21.28.35 # okay 21.31.39 # TheSeven: this looks like it tries to enumerate several times, getting pretty far. "ums: set config" implies the "basic" enumeration is done, and it's going on to the scsi bits. The "scsi inquiry 0" is the first bulk request expected, so either the SCSI_INQUIRY response is wrong (hence my question about ata), or the SCSI_INQUIRY response doesn't reach the host, which would mean an issue with outgoing bulk transfers 21.31.58 # gevaerts: shouldn't those too section be mixed using /playerman instead of the MPIO website and iriver website https://gist.github.com/1529584? 21.32.50 # gevaerts: possibly an excessively low timeout value on the host side? 21.33.15 # the funny part is that the last request i'm getting is a set config and not an inquiry one 21.33.28 # jlbiasini: gevaerts: at least the head of it 21.34.00 # TheSeven: you never know, but I wouldn't think so. Spec-wise there isn't any timeout on these, so usually the timeout is in seconds or tens of seconds (if not more) 21.35.02 # jlbiasini: I'm not sure here. Yes, it would be shorter, but it could easily make the \opt{} structure more complicated 21.36.42 # gevaerts: The first part could be common and the stuff about where to go separate but the code is certainly more readable like tha 21.36.44 # t 21.36.58 Join factor [0] (~factor@74.197.205.204) 21.37.43 # jlbiasini: feel free to submit a patch, so other manual people can have a look at it. No promises though, so this could be lost work 21.39.20 Join soap [0] (~soap@cpe-76-181-78-156.columbus.res.rr.com) 21.39.46 Quit soap (Changing host) 21.39.46 Join soap [0] (~soap@rockbox/staff/soap) 21.40.12 # gevaerts: yes I think I rather first do the fuze+ manual then I'll be ready for messing with manual itself 21.40.20 # Good idea :) 21.43.58 # gevaerts: so to go on: wtf is swcodec is fuze+ concerned? I saw quite a discussion on the mailling list and still not understood what it is... For what I get: swcode = new player, hdcodec = old player which should mean fuze+ = swcodec? 21.44.54 # jlbiasini: hwcodec means there's a dedicated decoder chip for mpeg audio, swcodec means that decoding happens on the main cpu 21.45.08 # You should be able to deduce the answer from that :) 21.45.57 Join sinthetek [0] (~sinthetek@cpe-174-111-026-094.triad.res.rr.com) 21.45.57 Quit sinthetek (Changing host) 21.45.57 Join sinthetek [0] (~sinthetek@unaffiliated/sinthetek) 21.46.52 # gevaerts: so just the oposite of what I wrote? 21.47.11 # no :) 21.47.28 # hwcodec in practice are the archoses 21.47.33 # ah ok like those archos that can only read mp3!! 21.47.51 # hm, this does indeed look like bulk in endpoint breakage 21.47.55 # Not *only* mp3! They also do mp2 and related 21.48.04 # i never get a transfer completion of the inquiry response, even though it is sent out 21.50.45 # gevaerts: ok thx :) 21.52.35 Quit Keripo (Ping timeout: 240 seconds) 21.54.42 # TheSeven: the difference between bulk and itnerrupt made me think about timing problem too 21.54.54 # funman. Why am I not sleeping yet? Anyway, it seems to NOT crash with current build. 21.55.05 # TheSeven: since you're in usb, how about we merge the 2 drivers; so we can make one single bugfix ? 21.59.00 Join marcol07 [0] (~4e628860@www.haxx.se) 22.01.08 # dfkt, Is your clip1 with 3.10 or whateveryoucallit build? 22.02.45 # cen somebody test theme for sansa clip? its name is simpleawesome... 22.03.13 # bug2000, no, running some recent-ish patched build 22.03.49 # dfkt, Can you check for a moment if 3.10 crash for you? Because the recent-ish build doesn't crash with your theme. 22.04.04 # yeah, i can try 22.08.20 Join Keripo [0] (~Keripo@CPE0022b0d4bdb7-CM001a6680d4fe.cpe.net.cable.rogers.com) 22.16.13 # New commit by 03theseven (r31458): usb-s3c6400x: Fix some more confusion between DEPCTL_stall and DEPCTL_naksts 22.16.34 # * TheSeven wonders if that actually fixed anything 22.18.22 # r31458 build result: All green 22.18.24 Quit B4gder (Quit: It is time to say moo) 22.18.26 # bug2000, 3.10 works fine so far, skipped around some 10 tracks so far 22.18.37 # dfkt, No clue in that case. 22.18.56 # dfkt, But yeah, the build seems to not crash for me with your theme. 22.19.00 # i see my bootloader is 2.0 - no idea if that is the recent one for amsv1 22.20.57 # dfkt, Same. 22.27.53 # TheSeven: cqn you check usb-drv-as3525 too ? 22.29.44 # funman: you mean as3525v2? 22.30.11 # yeah 22.30.40 # yeah, same bug there 22.31.12 # or at least same mismatch to my old code - no idea whether that one was correct 22.32.12 # so it seems that I will need to talk to some manual guru. Does anyone know one? 22.32.51 # jlbiasini: as usual, just ask :) 22.33.16 # It depends on the guruness you need 22.34.30 # TheSeven: can you fix it too ? 22.34.42 # well i'm not sure if it's even broken :) 22.34.52 # but you changed it for nano2g ?? 22.35.01 # yeah, but that didn't seem to have any effect 22.35.09 # i just made it consistent with how it used to be in the old driver 22.35.14 # well change both drivers so they don't diverge too much 22.36.13 # if it breaks things we'll know it pretty fast as there are much more sansa users 22.36.18 # hm, this was the only place where naksts was used at all 22.36.22 # that's a bit suspicious 22.37.05 # New commit by 03theseven (r31459): usb-srv-as3525v2: backport r31458 22.37.23 # thanks 22.37.52 # i was thinking of making at least a file with the common parts before we merge the two 22.38.19 # or do the merge in several steps, and at the end have one driver, and the PHY part in ipod / sansa files 22.38.59 # r31459 build result: All green 22.41.08 # ok so the installation part of the manual is scripted in manual/getting_started/installation.tex.For bootloader manual installation on Sansas this call then: either sansa_install.tex for taget relying on sansapatcher or sansaAMS_install.tex for those relying on mkamsboot. 22.44.13 # Fuze+ rely on mkimxboot that was written to be fully consistent with mkamsboot. So I could insert the fuze+ in the sansaAMS_install.tex quite easely. A few change would have to be made however because mkamsboot is sometime hard written and should rather be change into some /bootloaderprogam variable 22.44.36 # hm, there's definitely timing involved here 22.46.01 # anyway this would breaks the consistency of the file's name: sansaAMS_install.tex. 1) because it would be no more AMS file. 2) because mkimxboot should handle non-sansa device in the near future. 22.46.48 Join Thra11_ [0] (~thrall@87.112.142.132) 22.48.03 # jlbiasini: I'd use a new file 22.48.15 # so the question is: do I do a new IMX233.tex file that is quite a perfect copy of sansaAMS_install.tex (conditionnal code for other player being removed) or do we try to have some unification. 22.48.47 # Although it may be good to get pixelma's and bluebrother 22.48.49 # 's opinion 22.49.18 # gevaerts: that's what I made. But this is quite a copy of everything from the former file 22.49.32 # those are the manuals guru? 22.49.41 # yes 22.50.06 # ok I will try to reach them then thank you again! 22.50.45 Quit Thra11 (Ping timeout: 268 seconds) 22.51.34 # funman: hm, this is either a timeout or a lost interrupt 22.51.55 # TheSeven: i had adde a panic on unhandled interrupts 22.52.16 # lost in terms of accidentally ACKed without being handled (race condition?) 22.54.01 # pixelma: bluebrother: are you there any idea on this? 22.54.23 # TheSeven: don't we write the status register only after the interrupt was handled? 22.54.43 *** Saving seen data "./dancer.seen" 23.00.49 # so for the record the resulting file is this https://gist.github.com/1530005 23.01.40 # funman: well, in theory... 23.07.55 Quit pamaury (Remote host closed the connection) 23.20.22 Join notben [0] (~ben@99-122-85-101.lightspeed.spfdmo.sbcglobal.net) 23.20.33 Nick notben is now known as iamben (~ben@99-122-85-101.lightspeed.spfdmo.sbcglobal.net) 23.20.47 Part iamben 23.22.00 # gevaerts: jlbiasini: I'd use a file for the installation method, similar to how Rockbox Utility 23.23.24 # bluebrother^: ok I've started so anyway but this is really the very same... 23.23.49 # IMX233_install.tex is a good name? 23.24.12 Join Strife89 [0] (~Strife89@207-144-19-39.cstel.net) 23.24.17 # bluebrother^: hello 23.31.23 Quit perrikwp (Read error: Connection reset by peer) 23.33.34 Join perrikwp [0] (~quassel@cpe-024-163-024-033.triad.res.rr.com) 23.33.37 Quit Thra11_ (Quit: kthxbai) 23.39.16 Quit perrikwp (Read error: Connection reset by peer) 23.45.25 Quit ender` (Quit: I'm a complex person. I have a real and an imaginary part.) 23.47.30 # gevaerts: do i remember correctly that a NAK isn't critical at all in a USB system? 23.47.48 Join Scromple [0] (~Simon@119.225.209.134) 23.48.02 # is there some timeout after how many naks a transfer will retire as failed on the host side? 23.49.08 # no 23.49.31 # Well, it shouldn't, anyway 23.50.49 # i've seen transfers fail if we receive data before we have set up the endpoint accordingly... so these must be stalls then? 23.51.17 # stalls or no response, presumably 23.51.36 # isn't there always some response? 23.52.09 Quit Keripo (Ping timeout: 256 seconds) 23.52.13 # If everything works properly, yes. If the endpoint isn't set up yet I'd claim that isn't the case 23.52.40 # hm, what would that be then? 23.52.56 # What would what be? 23.53.22 # "no response" in terms of no electrical interaction with the bus at all? 23.53.36 # i thought no response == NAK, essentially 23.54.34 # In a well set-up system, yes 23.55.04 # so if there's no response at all, how would the HC react? retire after 3 attempts? 23.55.11 # that would match the behavior i'm observing 23.55.30 Quit [Saint] (Ping timeout: 268 seconds) 23.55.33 # That's definitely possible, yes 23.55.49 # I'm not sure if the number of retries in such a case is specified 23.56.10 # anyway it's probably rather low 23.56.28 # and I think I've seen something about 3 retries somewhere 23.56.33 # so it looks like the "idle" state of our EPs might not be correct? 23.57.29 # I'd guess so, yes. The error rate on a USB bus is supposed to be very low, and (again in a well working system) a flipped bit or similar is the only real way to get such a situation, so retrying twice should be enough 23.58.08 # and there are usually higher-level protocols on top of it that can handle a failed transfer anyway 23.58.18 Quit GeekShadow (Ping timeout: 252 seconds) 23.58.22 # but probably not properly if windows is involved :)