--- Log for 28.06.110 Server: leguin.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 2 days and 19 hours ago 00.02.12 Quit n1s (Quit: Lämnar) 00.04.01 Quit r0b- (Read error: Connection reset by peer) 00.06.33 # New commit by 03pamaury (r27161): as3525v2-usb: rework ep listing&xfers cancelling, implement speed reporting, first try at implementing disconnection ... 00.06.53 Join pamaury_ [0] (~quassel@p5DDEF65B.dip.t-dialin.net) 00.08.03 Quit petur (Quit: Zzzzz) 00.08.10 # r27161 build result: All green 00.13.22 Join r0b- [0] (~nnscript@adsl-76-236-184-143.dsl.klmzmi.sbcglobal.net) 00.14.09 Quit domonoky (Read error: Connection reset by peer) 00.17.44 Join Zigtown [0] (~Zigtown@CPE00259ce0fdb2-CM0014f8cc807a.cpe.net.cable.rogers.com) 00.22.26 Quit Jerom (Read error: Connection reset by peer) 00.24.03 Join Jerom [0] (~jerome@95.171.137.241) 00.25.13 Join Curtman [0] (~curt@S0106c03f0e7800b3.wp.shawcable.net) 00.26.10 Part Curtman 00.26.58 Quit funman (Quit: leaving) 00.35.13 Join mt__ [0] (~mtee@41.233.145.10) 00.36.06 Quit mt (Ping timeout: 240 seconds) 00.36.08 Nick mt__ is now known as mt (~mtee@41.233.145.10) 00.42.04 *** Saving seen data "./dancer.seen" 00.48.44 Join GeekShadow [0] (Antoine@reactos/tester/GeekShadow) 00.53.37 Join GeekShado_ [0] (Antoine@78.251.112.232) 00.54.46 Join GeekShad__ [0] (~Antoine@78.251.112.232) 00.56.32 Quit GeekShadow (Ping timeout: 240 seconds) 00.58.08 Quit GeekShado_ (Ping timeout: 240 seconds) 00.59.32 Quit r0b- (Quit: ( www.nnscript.com :: NoNameScript 4.22 :: www.esnation.com )) 01.05.44 Join [blue] [0] (~blue@ip70-178-120-137.ks.ks.cox.net) 01.06.31 # <[blue]> sooo, I've got a quick question 01.07.22 # <[blue]> It says on the target status page that charging is broken or something 01.07.36 # <[blue]> for the ipod 5g 01.08.11 # <[blue]> Anyonw know the actual limitations? 01.08.33 # <[blue]> anyone** 01.09.14 # oh, does it still say that? 01.09.24 # charging is properly implemented in current builds 01.09.30 # <[blue]> nifty nifty 01.09.31 # not in the 3.6 release though 01.09.44 # i'll go update teh port page ;) 01.09.54 # <[blue]> <3<3 01.10.12 # To charge from an AC adapter you have to change the charging setting to force; see the manual 01.10.15 Quit leavittx (Ping timeout: 248 seconds) 01.10.15 Quit leavittx_ (Ping timeout: 248 seconds) 01.10.19 # but for normal PC connectiosn it just works 01.11.10 Join r0b- [0] (~nnscript@adsl-76-236-184-143.dsl.klmzmi.sbcglobal.net) 01.11.11 # <[blue]> in 3.6? or is it not in the stable release yet? 01.11.24 # it's not in the stable release 01.11.26 # it will be in 3.7 01.11.37 # <[blue]> Kickin =) 01.11.38 # you can use the current build 01.12.18 # <[blue]> Wait, to clairfy 01.12.38 # <[blue]> charging over usb works? But using an AC adapter doesn't in 3.6? 01.13.26 # No, charging does not work at all in 2.6 01.13.28 # er, 3.6 01.13.36 # <[blue]> ahhhh 01.13.47 # in current builds, USB hosts charge properly, AC adapters need a setting because we haven't got detection for that yet 01.14.24 # <[blue]> Context Menu 01.14.31 # where on the wiki does it mention the charging issue, btw? 01.15.14 Quit pamaury_ (Read error: Connection reset by peer) 01.15.15 Quit pamaury (Read error: Connection reset by peer) 01.15.16 # <[blue]> The only place I saw a "No" was on the target status page 01.15.25 # ah ok 01.15.59 # i'll change that 01.18.33 # <[blue]> also, =P 01.18.45 # <[blue]> Any news on when 3.7 is going to be released? 01.18.59 Quit GeekShad__ (Read error: Connection reset by peer) 01.19.11 # <[blue]> I'm assuming... 01.19.17 # sometimes before 3.8 is going to be released 01.19.20 Quit DerPapst (Quit: Leaving.) 01.19.21 # <[blue]> Not too soon, just noticed 3.6 was like this month 01.20.12 # yah, it's on a schedule 01.20.23 # i forget what the schedule is but you can infer it by looking at the past release dates ) 01.20.39 Join GeekShadow [0] (~Antoine@reactos/tester/GeekShadow) 01.21.00 # bedtime fo rme tho ) 01.22.42 Quit kachna (Ping timeout: 245 seconds) 01.24.17 Quit ender` (Quit: Programmer thinks that he needs to validate an e-mail address. "I know," he says, "I'll use a regexp!" Now the user has a problem.) 01.25.20 Quit GeekShadow (Ping timeout: 240 seconds) 01.25.22 Quit r0b- (Read error: Connection reset by peer) 01.26.14 Quit S_a_i_n_t (Ping timeout: 260 seconds) 01.27.56 # New commit by 03mc2739 (r27162): Part of FS#11367 by me: e200v2 enable line out ... 01.29.32 # r27162 build result: All green 01.31.04 Quit Jerom (Quit: Leaving.) 01.32.48 Join t0rc [0] (~t0rc@unaffiliated/t0rc/x-5233201) 01.32.51 Join leavittx [0] (~leavittx@cl-534.mbx-01.si.sixxs.net) 01.33.16 Join z35 [0] (~z35@ool-457a4517.dyn.optonline.net) 01.33.42 Join S_a_i_n_t [0] (S_a_i_n_t@203.184.0.108) 01.36.52 Join wombat23 [0] (~beuteltie@adsl-99-39-2-249.dsl.pltn13.sbcglobal.net) 01.37.14 Quit dfkt (Quit: -= SysReset 2.53=- Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn.) 01.37.54 Quit wombat23 (Remote host closed the connection) 01.39.34 Join r0b- [0] (~nnscript@adsl-76-236-184-143.dsl.klmzmi.sbcglobal.net) 01.40.10 Quit OverLOAD (Quit: CGI:IRC (EOF)) 01.42.48 Join BHSPitMonkey [0] (~stephen@unaffiliated/bhspitmonkey) 02.24.52 Quit sevard (Changing host) 02.24.52 Join sevard [0] (sev@unaffiliated/sevard) 02.26.27 Quit r0b- (Ping timeout: 245 seconds) 02.37.45 Join MagusG [0] (magusg@c-76-97-148-35.hsd1.ga.comcast.net) 02.42.05 *** Saving seen data "./dancer.seen" 03.08.42 Join Strife89DS [0] (~nds@adsl-80-183-75.mcn.bellsouth.net) 03.09.11 Join storm` [0] (~lol@ip98-179-182-180.ri.ri.cox.net) 03.11.52 Quit Zigtown (Quit: Leaving...) 03.15.16 Join Xerion_ [0] (~xerion@82-170-197-160.ip.telfort.nl) 03.16.36 Quit Xerion (Ping timeout: 260 seconds) 03.16.36 Nick Xerion_ is now known as Xerion (~xerion@82-170-197-160.ip.telfort.nl) 03.20.50 Quit Rob2222 (Quit: Rob2222) 03.22.13 Quit JdGordon| (Quit: leaving) 03.22.43 Join r0b- [0] (~nnscript@adsl-99-52-153-164.dsl.klmzmi.sbcglobal.net) 03.35.33 Join Rob2222 [0] (~Miranda@p4FDCB7BE.dip.t-dialin.net) 03.40.25 Quit binaryhermit (Read error: Connection reset by peer) 03.40.44 Join binaryhermit [0] (~binaryher@adsl-99-141-196-197.dsl.emhril.sbcglobal.net) 03.45.17 Quit grndslm (Quit: Leaving) 04.05.10 Join bzed_ [0] (~bzed@devel.recluse.de) 04.07.16 Quit bzed (Ping timeout: 248 seconds) 04.08.28 Join bzed [0] (~bzed@devel.recluse.de) 04.08.35 Quit r0b- (Read error: Connection reset by peer) 04.11.09 Quit bzed_ (Ping timeout: 260 seconds) 04.23.58 Join amiconn_ [0] (quassel@rockbox/developer/amiconn) 04.23.59 Quit amiconn (Disconnected by services) 04.24.13 Quit pixelma (Disconnected by services) 04.24.15 Join pixelma_ [0] (quassel@rockbox/staff/pixelma) 04.24.16 Nick amiconn_ is now known as amiconn (quassel@rockbox/developer/amiconn) 04.24.30 Nick pixelma_ is now known as pixelma (quassel@rockbox/staff/pixelma) 04.32.12 Quit Strife89DS (Quit: Bed.) 04.36.12 Join cxo [0] (~cxo@unaffiliated/cruiseoveride) 04.36.39 # Is there a like a feature/hardware support matrix page? I can't seem to find one 04.38.22 # I want to buy an mp3 player specifically to use with rockbox, but i cant figure out which one has the best support 04.42.06 *** Saving seen data "./dancer.seen" 04.44.00 Quit MethoS- (Read error: Connection reset by peer) 04.49.09 Quit TheSeven (Ping timeout: 240 seconds) 04.51.10 Join Barahir [0] (~jonathan@frnk-590feac9.pool.mediaWays.net) 04.53.04 Join TheSeven [0] (~TheSeven@rockbox/developer/TheSeven) 04.54.33 # cxo: flash-based or harddrive based? 04.54.33 # cxo: There is a buyers guide on the wiki 04.54.41 # tactile or touch? 04.54.42 Quit Barahir_ (Ping timeout: 252 seconds) 04.54.48 Join saratoga [0] (9803c6dd@gateway/web/freenode/ip.152.3.198.221) 04.55.32 # cxo: http://www.rockbox.org/wiki/BuyersGuide 04.55.41 # Anyone elses opinion is well, someone elses opinion. you know what you need better than anyone else. 04.55.44 # although its missing the newest sandisk players 04.56.11 # if you're in the US, there's an 8GB Sansa Fuze on http://sellout.woot.com for the next two hours 04.56.25 Quit BHSPitMonkey (Ping timeout: 265 seconds) 04.56.25 # for $45 (after shipping) 04.56.53 # Those things are friggin' awesome 04.57.36 # the Fuze is a bit too big for me personally :/ 04.57.48 # it's lighter than the e200 04.58.13 # and smaller than the classic form-factor, non-nano/mini iPods 04.58.13 # if you don't need a color screen or scroll wheel, the clip+ is probably the better choice 04.58.33 # saratoga: but the Fuze is on woot today 04.58.47 # 'though, if you keep an eye on Woot, they generally do have Sansas from time to time 04.59.55 # real buttons please and flash too 05.00.12 # SNR is important too 05.00.38 # buy that fuze then 05.00.40 # cxo: and the modern Sansas get glowing reviews about their sound quality 05.01.18 Quit kramer3d (Quit: Leaving) 05.01.22 # does SanDisk still make the FuzeV2s? 05.02.38 # Thats funny, not a single supported player is still in production according to that table 05.03.02 # cxo: which is why I was asking if SanDisk still makes the newer-revision Fuzes 05.03.33 # oh, and I'd be surprised if the Clip+ has been discontinued already 05.04.05 Quit advcomp2019 (Read error: Connection reset by peer) 05.04.35 Join advcomp2019 [0] (~advcomp20@unaffiliated/advcomp2019) 05.04.37 # but they're just supported/unstable (though already quite usable!) rather than supported/stable 05.04.56 # does an OF revision of 02.02.26A mean the fuse is a v2? 05.05.06 # jhMikeS: yes 05.05.07 # jhMikeS: yes. 05.05.14 # thanks 05.05.15 # the fuze and clip+ are still in production 05.05.18 # it's still *really* easy to get your paws on a Nano2G, though the Nano1G is becomming quite rare now. 05.05.47 # S_a_i_n_t: but the µSD and fm tuner are just so nice to have 05.05.57 # Where is the feature list table for rockbox? 05.05.59 # and voice mic 05.06.38 # Dhraakellian: FM and Voice mic are available for Nano1/2G...just, not without additional hardware. 05.06.58 # A pity yes, but hardly a turnoff for me at least. 05.07.25 # then that just leaves the µSD slot 05.08.07 # "bah!" S_a_i_n_t laughs in the face of removable storage ;) 05.08.30 # cxo: http://www.rockbox.org/wiki/FeatureComparison comes to mind off the top of my head 05.08.35 # heh 05.08.42 # Thanks 05.09.07 # PluginIndex is pretty cool too, to show what your player can/cannot run. 05.09.11 # * cxo wonders why he couldnt find that stuff 05.09.14 # (in the way of plugins) 05.10.04 # * Dhraakellian seems to remember the Lyre project being 100% removable based, but he could be mistaken 05.10.10 Quit tmzt (Ping timeout: 260 seconds) 05.10.50 # Lyre seems to be a bit of a myth, every now and them someone revives it...then dissappears. 05.10.52 # Where are the screenshots? 05.11.04 # cxo: In the manual. 05.11.29 # ok 05.11.43 # S_a_i_n_t: well, when I got the Clip+ from Woot a couple weeks ago as a backup DAP, it was really nice to just pop the 8GB card out of my Fuze and into the Clip+ to test it out 05.12.20 # but, before this veers any more off topic... 05.12.30 # I agree its nice, but, its not a selling point for me. I appreciate form factor more. There seems to be a lot of wasted interior space in the Fuze. 05.13.03 # yeah, if they can fit the same functionality minus wheel and screen into the clip form factor... 05.13.13 # yep. 05.13.32 # but I like having the real screen and the wheel instead of volume buttons 05.13.44 # and it also fits in my hand more comfortably than the clip 05.14.06 # and I also prefer the hold/power slider over the system the Clip+ uses 05.16.09 # I think battery life is much better in the Fuze 05.16.16 # Does checkwps check fonts in the fontpack? 05.16.21 # it *should* right? 05.16.43 # * S_a_i_n_t is puzzled by: http://forums.rockbox.org/index.php?topic=25174.msg168833#msg168833 05.16.44 # cxo: I dunno. I benched my clip+ at almost exactly 15 hours with q6 Ogg Vorbis 05.17.09 # haven't benched the Fuze recently, but 10-12 is the number I've seen quoted 05.17.23 # have there been efficiency improvements since that stat was reached? 05.17.58 # (this is with Rockbox, of course. I haven't tested it with the OF, and I'd take SanDisk's battery claims with a grain of salt) 05.18.01 # Pass. The Clip(s) are definitelt kicking ass over the OF in terms of batter life now. 05.19.40 # Well Sansa quoted times for the Fuze are better than 2x the Clip+ 05.20.00 # S_a_i_n_t: more efficient hardware than the Fuze? Or are the optimization tweaks better understood on the Clip(+) than the Fuze? 05.20.08 Join wombat23 [0] (~beuteltie@adsl-99-39-2-249.dsl.pltn13.sbcglobal.net) 05.20.25 # Dhraakellian: That's a question for funman I imagine... 05.20.49 # * Dhraakellian wonders how much the lcd+backlight vs. oled(?) part factors in 05.21.55 # JdGordon: Checkwps checks font names in the fontpack...yes? 05.24.49 Quit wombat23 (Ping timeout: 260 seconds) 05.26.52 # Fuze v1 gets bad battery life in rockbox for some reason 05.27.09 # all the amsv1 devices do, while amsv2 devices get better then the OF mostly 05.27.20 # :( 05.27.33 # in theory the amsv2 devices should be a little better then the amsv1 as well, though nothing major 05.27.51 # so the clipV1 has poor battery life too? 05.28.02 # yeah 05.28.22 # and the e200v2 worse than the e200v1? 05.28.40 # correct 05.28.55 # especially with multithreaded stuff, I'm guessing, since, iirc, the e200v1 is dual-processor? 05.29.00 # yeah 05.29.11 # i spent years optimizing for the e200v1, it'll be a while before the v2 beats it 05.29.28 # fuze v2 install went through pretty smoothly and boots pretty darn fast. is it normal for the top few pixel rows to be hidden on the lcd bezel? 05.29.35 # yeah 05.29.43 # * Dhraakellian was a bit peeved when the e200v1 ogg decoder lost its throne to the multi-threaded mp3 decoder 05.29.48 # well maybe not desired, but pretty common 05.30.06 # it was already slower then the wma decoder 05.30.15 # jhMikeS: my recommendation would be to move the statusbar to the bottom 05.30.19 # rockbox has multi-threading? 05.30.24 Join Zigtown [0] (~Zigtown@CPE00259ce0fdb2-CM0014f8cc807a.cpe.net.cable.rogers.com) 05.30.29 # of course, its an operating system 05.30.34 # hard to have one of those with just one thread 05.30.39 # Dhraakellian: thanks. never had to think about it before. :) 05.31.04 # jhMikeS: yeah, you still lose a couple pixels at most viewing angles, but it's less obvious 05.31.16 # ...or use a theme that places things a little lower 05.31.31 # on dual core targets mp3, spc and mpeg will use both cores as well 05.32.17 # saratoga: but it was nice to point to Rockbox when the naysayers claimed that Ogg Vorbis decoding was überslow compared to mp3 05.32.24 Join r0b- [0] (~nnscript@adsl-99-52-153-164.dsl.klmzmi.sbcglobal.net) 05.33.09 # bottom statusbar isn't so bad, just looks weird atm 05.33.24 # jhMikeS: you get used to it. after a while, top statusbar will look strange to you 05.33.44 # get a theme wotha propper .sbs ;) 05.33.52 # * Dhraakellian is the same way with desktops: taskbar/panel on the bottom just looks... strange to him 05.33.57 # then, statusbar will look weird fullstop. 05.34.10 # heh. I'm partial to BlueBlackness 05.34.14 # wotha? errr..."with a" 05.34.35 # S_a_i_n_t: wotha heck was that? 05.35.52 # I still need to get around to making that moodbar-compatible wps taking heavy inspiration from the e200's PlainText 05.35.53 # saratoga: fft plugin as well uses the COP 05.35.53 Quit Zigtown (Read error: Connection reset by peer) 05.36.35 # oh, and I would like to thank the dev(s) responsible for bringing USB support to the FuzeV1 05.37.11 # since that obviates the battery issue a tad by making it less of a tanj frell hassle to run the thing off of USB power 05.37.34 Quit panni_ (Quit: ( www.nnscript.de :: NoNameScript 3.81 :: www.XLhost.de )) 05.39.44 Quit S_a_i_n_t () 05.40.03 Join S_a_i_n_t [0] (S_a_i_n_t@203.184.0.108) 05.43.34 Quit anewuser (Quit: http://xrl.us/detroitVI Sixth edition of 25 samples + 48 hours + detroit party (july 31) (maybe streamed online!)) 05.43.54 Join wombat23 [0] (~beuteltie@adsl-99-39-2-249.dsl.pltn13.sbcglobal.net) 05.51.22 Quit wombat23 (Ping timeout: 264 seconds) 05.53.27 Join jennifur [0] (~jennifur@cpe-72-224-19-1.nycap.res.rr.com) 05.53.55 Join anewuser [0] (anewuser@201.248.225.97) 05.53.59 Quit anewuser (Changing host) 05.53.59 Join anewuser [0] (anewuser@unaffiliated/anewuser) 05.55.39 Join wombat23 [0] (~beuteltie@adsl-99-39-2-249.dsl.pltn13.sbcglobal.net) 06.00.13 Quit wombat23 (Ping timeout: 265 seconds) 06.02.18 Join wombat23 [0] (~beuteltie@adsl-99-39-2-249.dsl.pltn13.sbcglobal.net) 06.04.12 # cxo: did you come to any sort of decision? 06.05.27 Quit fdinel (Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org) 06.06.45 Quit wombat23 (Ping timeout: 260 seconds) 06.13.04 Quit jennifur (Ping timeout: 245 seconds) 06.19.09 Quit Xerion (Quit: ) 06.24.07 # hrm...fuze v2 doesn't come out of hold mode properly or is that intentional somehow? 06.26.46 Quit t0rc (Quit: Leaving) 06.32.09 # Dhraakellian, ah not really. It was for the car. I really hate the state of currently available head units. 06.32.40 # ah 06.32.49 # Need something with really good battery life. I'm using an Archos 605 right now and I dont think i get even 2hours with it 06.32.57 Quit anewuser (Quit: http://xrl.us/detroitVI Sixth edition of 25 samples + 48 hours + detroit party (july 31) (maybe streamed online!)) 06.32.59 # if i use it for 15mins each time and switch it off 06.33.10 # it doesnt really switch off, it only goes into a suspend 06.33.10 # well, a cigarette-->USB power adapter can help with that 06.33.20 # yeah, dont like all the wires 06.33.23 # heh 06.34.12 # Clip+ with a small bit of velcro on the clip and a short cable to the head unit's aux in? 06.34.44 # (which reminds me, I really need to get a fit kit for the aftermarket headunit I have sitting on the shelf downstairs) 06.40.22 # wireless AV kits can be reasonably cheap...though, this is a sliding scale of offtopicness. 06.40.47 # (tiny reciever in the dash, hide the DAP somewhere that works well for you.) 06.42.10 *** Saving seen data "./dancer.seen" 06.43.09 # Do you have a link for these wireless kits? 06.44.55 Join BHSPitMonkey [0] (~stephen@unaffiliated/bhspitmonkey) 06.45.08 # cxo: tape adapter would be less annoying, I'd think 06.45.12 # Not in particular. Google for "wireless AV send" (or similar) I picked mine up for under $30 06.45.18 # direct aux in even better 06.45.38 # head unit running Rockbox doubleplusbetter 06.45.51 # hmm... 06.46.17 # dash-mounted D2 with a custom LOD? 06.46.33 # dash mounted mini2440 06.46.41 # == Awesome :D 06.46.48 # * Dhraakellian isn't overly familiar with non-Sansa targets 06.47.10 # was going with the D2 because of the reasonably-sized touchscreen aspect 06.47.13 # oslt 06.47.28 # The DACs in most head units these days are pretty good, its just the interface sucks, both looks and usability 06.47.35 # mini2440 can have a 7" screen IIRC 06.48.09 # I dont like the idea of touchscreen head units in a car. I'd much prefer something with buttons, so that it can be operated without looking at the unit 06.48.09 # Dhraakellian: Since its an RB target also :http://www.friendlyarm.net/products/mini2440 06.48.27 # mini2400 == PITA, but, pure awesomeness. 06.49.11 # heh 06.50.08 # cxo: hmm... probably something without a wheel, then, if you don't want long wires that would let you actually hold it in hand 06.50.33 # * Dhraakellian actually thinks he might try that ClipPlus+velcro idea 06.50.58 # file down the nubs where the clip broke off 06.56.14 # Dhraakellian: Did you check out the specs for the mini2440? stack that up next to your favourite dedicated DAP and compare specs. 06.56.22 # and, its only 10x10cm 06.56.56 # well, the mainboard is, it can have up to a 7" screen..possibly even 11" IIRC 06.59.49 # alas, no, I only glanced 07.00.08 # *and* it runs Android ;) 07.00.25 # it really is a beast...but, a little bit of a waste for just a DAP. 07.00.48 # its a "Single-Board Computer" 07.01.02 # (they really mean that too...) 07.01.40 # Android support makes it one of the likely candidates for RAaA 07.02.04 # (at least two devs here have one IIRC) 07.08.58 Quit binaryhermit (Ping timeout: 276 seconds) 07.09.50 Join Zigtown [0] (~Zigtown@CPE00259ce0fdb2-CM0014f8cc807a.cpe.net.cable.rogers.com) 07.23.26 # is android actually useful on an arm9 core? 07.27.28 Join esperegu [0] (~quassel@145.116.15.244) 07.29.40 Join LinusN [0] (linus@giant.haxx.se) 07.29.40 Quit LinusN (Changing host) 07.29.40 Join LinusN [0] (linus@rockbox/developer/LinusN) 07.40.45 Join Buschel [0] (~~andree@p54A3EBC6.dip.t-dialin.net) 07.40.46 Quit JdGordon (Read error: Connection reset by peer) 07.42.12 Join JdGordon [0] (~jonno@rockbox/developer/JdGordon) 07.49.24 Quit Zarggg (Quit: Zarggg) 08.07.55 Join jordan` [0] (~jordan@jem75-13-78-235-252-137.fbx.proxad.net) 08.09.27 Quit cxo (Quit: Leaving) 08.12.04 Join togetic [0] (~togetic@unaffiliated/ibuffy) 08.20.31 Join Spaceghost1 [0] (~Pablo@r186-48-2-8.dialup.adsl.anteldata.net.uy) 08.21.29 # saratoga: On PP the greylib optionally uses the COP as well 08.25.01 Quit GodEater (Ping timeout: 260 seconds) 08.26.58 Quit bieber (Ping timeout: 276 seconds) 08.27.08 Join wombat23 [0] (~beuteltie@adsl-99-39-2-249.dsl.pltn13.sbcglobal.net) 08.27.15 Join bieber [0] (~quassel@162-78.97-97.tampabay.res.rr.com) 08.28.07 # New commit by 03Buschel (r27163): Remove unneeded libmad files from build. 08.29.46 # r27163 build result: All green 08.31.23 Quit S_a_i_n_t () 08.32.11 Quit wombat23 (Remote host closed the connection) 08.32.57 # Buschel: FWIW I don't think libmad is ever going to be updated again, so feel free to remove any bits you dislike :) 08.33.05 Quit Buschel (Ping timeout: 245 seconds) 08.33.15 Join Zarggg [0] (~zarggg@65-78-69-194.c3-0.eas-ubr6.atw-eas.pa.cable.rcn.com) 08.33.34 Join JdGord [0] (~jd@110.21.1.90) 08.35.48 Join ender` [0] (krneki@foo.eternallybored.org) 08.35.56 # saratoga: libmad is finished/abandoned by the original authors? 08.35.56 Quit BHSPitMonkey (Read error: Connection reset by peer) 08.36.04 Join S_a_i_n_t [0] (S_a_i_n_t@203.184.5.223) 08.36.23 # jhMikeS: last release was 2004 I think 08.36.57 # ah...well, if it's perfect what's there to change? :P 08.38.01 Quit AlexP (*.net *.split) 08.38.02 Quit aevin (*.net *.split) 08.38.29 Join flydutch [0] (~flydutch@host129-160-dynamic.15-87-r.retail.telecomitalia.it) 08.38.59 # i suppose mp3 decoding is mostly a solved problem 08.40.54 Join Zagor [0] (bjst@rockbox/developer/Zagor) 08.42.11 *** Saving seen data "./dancer.seen" 08.49.53 Join aevin [0] (eivindsy@unaffiliated/aevin) 08.52.00 Part Spaceghost1 08.56.24 Join tmzt [0] (~ircuser@99-157-224-139.lightspeed.bcvloh.sbcglobal.net) 08.58.29 Join tmzt_ [0] (~ircuser@99-157-224-139.lightspeed.bcvloh.sbcglobal.net) 08.58.37 Join AlexP [0] (~alex@rockbox/staff/AlexP) 09.04.12 Join petur [0] (d408b802@rockbox/developer/petur) 09.04.56 Join bor_ka [0] (www-data@giant.haxx.se) 09.05.51 Quit Topy44 (Ping timeout: 260 seconds) 09.08.06 Join Topy44 [0] (~topy@my.fastsh.it) 09.11.15 # ranma, hello! 09.11.33 # ranma, 4bit bus - revenge of the sansas... 09.11.38 # Fuze v1, r27128 (with 4bit wide bus). There are heavy playback glitches on mp3 - 320. When playing from the mSD - all is Ok. But when playing from the internal memory, after ~ 3-4 mins of playback skips happen: about 0.5 - 1 sec from another track, then playback continues as usual. It is definitely not garbage, but parts from other track, since I hear woman's vocal on the tracks, where it shouldn't be. I've rebuild r27128 with the 4bit initialization 09.14.06 Join wombat23 [0] (~beuteltie@adsl-99-39-2-249.dsl.pltn13.sbcglobal.net) 09.19.03 Join kachna [0] (~kachna@r4ax178.net.upc.cz) 09.19.08 Quit wombat23 (Remote host closed the connection) 09.25.16 Quit Zigtown (Ping timeout: 240 seconds) 09.29.32 Join wombat23 [0] (~beuteltie@adsl-99-39-2-249.dsl.pltn13.sbcglobal.net) 09.34.33 Quit wombat23 (Remote host closed the connection) 09.42.35 Quit JdGord (Quit: Bye) 09.46.11 Join wombat23 [0] (~beuteltie@adsl-99-39-2-249.dsl.pltn13.sbcglobal.net) 09.48.15 Join Rob2223 [0] (~Miranda@p4FDC9B9E.dip.t-dialin.net) 09.51.10 Quit wombat23 (Ping timeout: 252 seconds) 09.51.31 Join wombat23 [0] (~beuteltie@adsl-99-39-2-249.dsl.pltn13.sbcglobal.net) 09.51.45 Quit Rob2222 (Ping timeout: 260 seconds) 09.58.03 Quit wombat23 (Remote host closed the connection) 09.58.50 Join wombat23 [0] (~beuteltie@adsl-99-39-2-249.dsl.pltn13.sbcglobal.net) 10.00.08 Join Mich [0] (~M_cH@pool-71-115-199-163.spknwa.dsl-w.verizon.net) 10.00.55 Join CrankHunt3r [0] (www-data@giant.haxx.se) 10.01.04 # hello dudes! 10.03.31 # I've heard of your project and as a opensource-user and -developer I think you do a great job ... now to my question: I posses a "Watson MP3184-9" and I didn't find any version of rockbox for him! How can I build an image for my player? 10.04.30 Quit wombat23 (Ping timeout: 240 seconds) 10.09.35 # CrankHunt3r, I think, that if there is no version - then nobody made a port. 10.10.40 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 10.11.22 # Rockbox needs to be adapted for each piece of hardware. You would need to start a new port for your device - find out about the hardware it uses and start from there 10.11.25 # unless that DAP is a direct clone of another DAP that is supported, can't really build rockbox and expect it work. Needs to be able to directly support the hardware in the DAP. 10.11.49 # and what pixelma said :) 10.13.48 Join JdGord [0] (~jd@110.21.1.90) 10.16.58 Join wombat23 [0] (~beuteltie@adsl-99-39-2-249.dsl.pltn13.sbcglobal.net) 10.19.07 Quit swilde (Quit: ERC Version 5.3 (IRC client for Emacs)) 10.19.49 Join efyx [0] (~efyx@lap34-1-82-225-185-146.fbx.proxad.net) 10.21.16 Quit wombat23 (Ping timeout: 240 seconds) 10.30.46 Quit JdGord (Quit: Bye) 10.37.20 Join DerPapst [0] (~Alexander@dslb-088-069-135-024.pools.arcor-ip.net) 10.42.12 *** Saving seen data "./dancer.seen" 10.50.59 Join wombat23 [0] (~beuteltie@adsl-99-39-2-249.dsl.pltn13.sbcglobal.net) 10.59.19 # okay I understand 11.01.04 # how can I find something about the hardware? Do you use some kind of hardwarescanner? 11.02.35 Join Buschel [0] (~~andree@p54A3C9CD.dip.t-dialin.net) 11.04.30 Quit wombat23 (Ping timeout: 260 seconds) 11.04.43 Join wombat23 [0] (~beuteltie@adsl-99-39-2-249.dsl.pltn13.sbcglobal.net) 11.06.25 # usually by opening the player and look for the chips... oh, another thing necessary for a port is finding out how to load and run custom code on your unit. Theres a page about porting in our wiki, called NewPort 11.12.23 Quit wombat23 (Ping timeout: 264 seconds) 11.13.00 Join wombat23 [0] (~beuteltie@adsl-99-39-2-249.dsl.pltn13.sbcglobal.net) 11.15.42 # okay thx .. when I opened the player and looked at the systeminformation I see just "chip: 07" and also the free and avaiable memory 11.17.42 Quit wombat23 (Ping timeout: 265 seconds) 11.18.59 # CrankHunt3r: We mean open as in take it apart and look at the internals 11.23.06 Quit Buschel (Ping timeout: 276 seconds) 11.23.45 Join wombat23 [0] (~beuteltie@adsl-99-39-2-249.dsl.pltn13.sbcglobal.net) 11.25.12 # jep I got it after reading the wikipart, called NewPort 11.28.35 Quit wombat23 (Ping timeout: 264 seconds) 11.30.30 Join dfkt [0] (~dfkt@unaffiliated/dfkt) 11.31.27 Join einhirn [0] (~Miranda@bsod.rz.tu-clausthal.de) 11.35.41 Quit bieber (Ping timeout: 258 seconds) 11.35.56 Join bieber [0] (~quassel@162-78.97-97.tampabay.res.rr.com) 11.44.40 Join MethoS- [0] (~clemens@134.102.106.250) 11.46.16 # New commit by 03ranma (r27164): Enable HID support, clean up usb-drv-as3525.c a bit, add a workaround for weird Linux behaviour (don't have Windows to test with), we don't need to ... 11.47.43 # bor_ka: Your line was too long. Last I see is "I've rebuild r27128 with the 4bit initialization" and it cuts off there 11.47.58 # r27164 build result: All green 11.48.09 Join JdGordon_ [0] (6e15015a@gateway/web/freenode/ip.110.21.1.90) 11.49.37 # bor_ka: I don't see how 4bit could cause the problem you describe, it sounds like it does a read from the wrong sectors, but the sector address is part of the command, which is transfered on the cmd line (1bit), unaffected by 4bit mode 11.51.33 # ranma, I either, but... 11.51.43 # I've rebuild r27128 with the 4bit initialization commented out - all is Ok, both from mSD and internal memory. 11.52.08 Join wombat23 [0] (~beuteltie@adsl-99-39-2-249.dsl.pltn13.sbcglobal.net) 11.52.12 # That is, I have two build, one with the 4bit widebus initialization on, one with "off" 11.52.23 # the first one skips, the second one - not 11.54.26 # BTW, I have option "gather runtime data" in the database on - may it be so, that permanent writes to the internal memroy somehow corrupts read buffer or address? 11.54.50 # will try without this option in a hour 11.57.10 Quit wombat23 (Remote host closed the connection) 11.57.50 Join wombat23 [0] (~beuteltie@adsl-99-39-2-249.dsl.pltn13.sbcglobal.net) 12.03.18 Quit wombat23 (Ping timeout: 240 seconds) 12.05.04 Join wombat23 [0] (~beuteltie@adsl-99-39-2-249.dsl.pltn13.sbcglobal.net) 12.05.16 # It appears, that without the "gather runtime data" option, there are no "wrong reads" 12.16.21 Quit efyx (Remote host closed the connection) 12.16.37 Join efyx [0] (~efyx@lap34-1-82-225-185-146.fbx.proxad.net) 12.18.28 Quit MethoS- (Remote host closed the connection) 12.22.07 Join Zigtown [0] (~Zigtown@CPE00259ce0fdb2-CM0014f8cc807a.cpe.net.cable.rogers.com) 12.36.14 Join hebz0rl [0] (~hebz0rl@dslb-088-065-216-095.pools.arcor-ip.net) 12.38.30 Join swilde [0] (~wilde@aktaia.intevation.org) 12.41.21 Quit bor_ka (Quit: CGI:IRC (EOF)) 12.42.11 Nick fxb__ is now known as fxb (~felixbrun@h1252615.stratoserver.net) 12.42.16 *** Saving seen data "./dancer.seen" 12.46.07 Quit JdGordon_ (Ping timeout: 252 seconds) 12.46.51 Join JdGordon_ [0] (6e15015a@gateway/web/freenode/ip.110.21.1.90) 13.09.38 Join bor_ka [0] (www-data@giant.haxx.se) 13.11.44 Quit Mich () 13.16.20 Quit bieber (Ping timeout: 252 seconds) 13.16.36 Join bieber [0] (~quassel@162-78.97-97.tampabay.res.rr.com) 13.17.49 # New commit by 03uchida (r27165): text viewer: tv_window doesn't depend on the layout of the text viewer. ... 13.18.20 Join ucchan [0] (~ucchan@softbank126102048035.bbtec.net) 13.19.29 # r27165 build result: All green 13.20.31 Part Zagor 13.29.41 Join dfkt_ [0] (~dfkt@unaffiliated/dfkt) 13.29.56 Quit liar (Ping timeout: 258 seconds) 13.33.09 Quit dfkt (Ping timeout: 248 seconds) 13.44.53 Quit kachna (Ping timeout: 248 seconds) 13.45.55 Join robin0800 [0] (~quassel@cpc2-brig8-0-0-cust964.brig.cable.ntl.com) 13.49.28 Join jgarvey [0] (~jgarvey@cpe-065-190-066-089.nc.res.rr.com) 13.50.40 Join wodz [0] (~wodz@inet20909nc-1s.nat.umts.dynamic.eranet.pl) 13.55.21 # pixelma: ping 13.56.56 # There are some questions about the statusbar on the plugin. see: http://pastebin.com/kE3wrsdJ 13.57.21 # the above plugin is very simple plugin. (statusbar draw only). 13.57.37 # Q1) does not update battery and clock. How can I modify it, the battery/clock is changed ? 13.58.02 # Q2) when the global setting is STATUSBAR_OFF, can the statusbar be displayed from it ? 13.58.18 # please someone help me. 13.59.50 Quit JdGordon_ (Ping timeout: 252 seconds) 14.02.24 # wodz: pong 14.05.10 # pixelma: how test on ondio going? 14.13.52 # sorry, haven't tested much (or used any of my targets much last week). Only one "session" of about 1 hour straight listening which went well. Looks good so far, I'd like to test some recording too though 14.14.25 # ok 14.30.47 # ranma, any ideas why there are incorrect reads, if there is simultaneous reads and writes from the internal memory with the 4bit bus enabled? 14.31.39 Join Kitr88 [0] (~Kitar_st@BSN-143-108-185.dial-up.dsl.siol.net) 14.33.54 Join Zagor [0] (bjst@rockbox/developer/Zagor) 14.34.38 Quit Kitar|st (Ping timeout: 240 seconds) 14.36.15 Quit Kitr88 (Ping timeout: 258 seconds) 14.41.05 # bor_ka: No. I tried reproducing it, but I don't see any problems with "gather runtime data" enabled, but my C200v2 is one of the targets with very little memory, which might have an influence here 14.41.27 Join Kitar|st [0] (Kitar_st@BSN-210-251-206.dial-up.dsl.siol.net) 14.42.18 *** Saving seen data "./dancer.seen" 14.46.18 # Anyone happen to have the Apple iPod Updater 2006-01-10 lying around? 14.47.44 # ranma, Ok, c200v2 and fuze are a little bit different, I think 14.49.18 # may be funman will get it 14.50.47 # btw, is it possible, to make 2 reads in a row and abort, if they are different - like you have made with writes? It will slow the player considerably, but, may be we will get it? 14.51.11 # bor_ka: I'm writing you just a patch now :) 14.51.52 # Ok, thanks! 14.53.20 # no, "gather" doesn't help 100% - there were no glithces for almost an album, but instead different song start playing, and the player just locked up. Without any abort screen :/ 14.54.10 # that is, with "gather" off it is better, but the problem is not fixed 14.54.15 Quit ucchan (Quit: Leaving...) 14.56.31 Quit wodz (Ping timeout: 240 seconds) 14.58.58 Join funman [0] (~fun@187.131.193-77.rev.gaoland.net) 14.59.03 Quit funman (Changing host) 14.59.03 Join funman [0] (~fun@rockbox/developer/funman) 15.01.49 # bor_ka: http://pastebin.com/NYaXJFmR 15.03.51 Quit antil33t (Read error: Connection reset by peer) 15.03.58 Join antil33t [0] (~Mudkips@124-197-51-80.callplus.net.nz) 15.10.13 # did you find what was wrong with dynamic bus width? 15.11.20 # ranma, got it, but it says "patch unexpectedly ends in middle of line \n Hunk #4 succeeded at 951 with fuzz 1. " 15.11.43 # don't know what it is - will patch by hand :) 15.11.45 # bor_ka: that's ok, usually it comes from the pastebin website 15.12.09 # which adds/removes line endings. If the hunk 'succeeded' it should be allright (just check with svn diff that everything is here) 15.12.22 # funman, but it said only abou 1 hunk, but there were 4 15.13.12 # ok, all seems to be ok 15.13.49 Join komputes [0] (~komputes@ubuntu/member/komputes) 15.15.08 Join evilnick_B [0] (0c140464@rockbox/staff/evilnick) 15.17.37 Quit komputes (Max SendQ exceeded) 15.19.09 Join komputes [0] (~komputes@ubuntu/member/komputes) 15.27.01 # Ok, goneranma, imeediately got "PANIC: sd_set_widebus: tran" on bott 15.27.07 # bott -> boot 15.33.11 # ranma, can't get past boot, restoring old rockbox.sansa via OF 15.37.16 Join Buschel [0] (~~andree@p54A3EE03.dip.t-dialin.net) 15.37.16 Join t0rc [0] (~t0rc@unaffiliated/t0rc/x-5233201) 15.37.31 # JdGordon; Around? 15.40.36 # bor_ka: Hmm, it booted fine here... 15.41.22 # ranma, updating to 27165 - I have made it on 27128 15.45.16 Join MethoS- [0] (~clemens@134.102.106.250) 15.46.42 Nick dfkt_ is now known as dfkt (~dfkt@unaffiliated/dfkt) 15.48.05 # pixelma: ping? 15.50.06 # bor_ka: Slightly modifed to show more info when wait_for_tran_state failes: http://pastebin.com/iYRii7Zs 15.52.16 # S_a_i_n_t: pong 15.52.48 # pixelma: Is it possible to show a "playbar" for the tuner frequency in the .fms? 15.53.07 # * S_a_i_n_t has not played with .fms much 15.53.29 Part froggyman 15.53.59 # S_a_i_n_t: yes, use %pb with normal syntax 15.54.06 # thankyou. 15.54.20 # the wiki/manual really should include that. 15.54.23 # ranma, got r27165 - again, PANIC in sd_set_widebus : tran on boot 15.54.30 # I'll add it after I finish playing around. 15.55.02 # it uses the regions minimum and maximum frequencies for the outer limits and adjusts the bar for the current frequency 15.55.20 # * pixelma deletes answer 15.55.21 # thankyou kindly. 15.55.34 # sorry pixelma ;) 15.55.39 # mc2739 beat you. 15.55.49 # next time, promise. 15.55.52 # * mc2739 is sorry, also 15.55.53 # * pixelma feels beaten 16.00.38 Quit bor_ka (Quit: Home sweet home) 16.00.40 Quit Buschel (Ping timeout: 276 seconds) 16.08.10 Join balintx [0] (~balintx@fibhost-67-58-201.fibernet.hu) 16.08.46 # Hi. Does someone using Rockbox on Sandisk Sansa Fuze v2? 16.13.20 # Nobody? 16.13.54 # i think someone uses rockbox on fuzev2, yes. if you have a precise question about it just ask 16.14.21 # * SansaAMS v2: Until the USB driver is fully operational, file transfer support is provided by booting the Original Firmware when the USB cable is inserted. 16.14.23 # it says. 16.14.33 # I have broken my player 16.14.51 # sadly, i put the usb cable in that weird hole 16.15.16 # the screen went black, and i tried a lot of thing to switch on 16.15.24 # nothing worked. the screen is black 16.16.12 # balintx: if you plug in the headphones, do you hear it click or pop? 16.16.41 # balintx: read a few lines below on this web page, this situation is explained 16.16.49 # I try it. 16.16.50 # where should i hear? from the earphones? 16.17.23 # Sorry funman I am very angry and am afraid of losing my fuze :( 16.17.29 # http://www.rockbox.org/wiki/SansaAMSUnbrick i found only this 16.17.40 # balintx: what is "that weird hole"? 16.17.56 # the usb connector 16.18.01 # ohh lol 16.18.16 # in the player :P 16.18.20 # where I put the cable. 16.18.41 # so, the normal place to insert the USB then? 16.18.52 # balintx: yes, do you hear a click or pop in the earphones? 16.19.10 # yes 16.19.16 # a noise... 16.19.25 Nick fxb is now known as fxb__ (~felixbrun@h1252615.stratoserver.net) 16.19.42 # yes S_a_i_n_t. I have normally put the usb in. 16.20.05 # mc2739: when i plug the earphone, it has a pop noise 16.20.11 # Ok, cool. Just wondered what "that weird hole" was. 16.21.02 # a very low pop 16.21.07 # balintx: This is the problem funman has referenced. You will have to wait for the battery to drain (no more pop noises), and then when you plug in the cable it should power on and charge 16.21.18 # lol 16.21.21 # how to do it? 16.21.30 # it was on 100 % of charge.... 16.21.39 # how many months is this? 16.21.51 # wait, for quite some time potentially. 16.21.58 # its days, not months. 16.22.11 # and, will it work? 16.22.11 # ~2 or 3 16.22.22 # It has for others. 16.22.33 # and why is this? 16.22.42 # just rockbox fault of usb? 16.22.53 # it will discharge by itself, you cannot do anything to help it go faster 16.23.35 # So don't do anything, just wait? 16.23.40 # yes 16.24.22 # and if i don't hear the sound, just plug the usb in? 16.24.35 # don't hold left button or anything? 16.24.48 # balintx: it is possibly the USB. All reports I have seen of this problem come from attaching the USB cable while running Rockbox, but since there have only been just a few reports of this problem, that is not necessarily the real problem. 16.25.22 # ok 16.25.44 # balintx, yes, if no noise, do not press power, just attach cable 16.26.07 Join bluebrother [0] (~dom@g224236161.adsl.alicedsl.de) 16.26.07 Quit bluebrother (Changing host) 16.26.07 Join bluebrother [0] (~dom@rockbox/developer/bluebrother) 16.28.45 Quit MethoS- (Remote host closed the connection) 16.29.23 # http://forums.rockbox.org/index.php?topic=24992.msg168026 - sorry. I didn't search for it. But thanks for help. 16.29.43 Quit bluebroth3r (Ping timeout: 258 seconds) 16.38.05 Join stripwax [0] (~Miranda@87-194-34-169.bethere.co.uk) 16.42.20 *** Saving seen data "./dancer.seen" 16.44.07 Quit Zigtown (Read error: Operation timed out) 16.46.48 Quit stripwax (Quit: http://miranda-im.org) 16.47.25 Join stripwax [0] (~Miranda@87-194-34-169.bethere.co.uk) 16.48.55 Join marines [0] (~quassel@abzo170.neoplus.adsl.tpnet.pl) 16.54.46 Join AzureWurk [0] (opera@c-24-21-44-114.hsd1.wa.comcast.net) 17.00.31 Quit stripwax (Quit: http://miranda-im.org) 17.01.42 Quit CrankHunt3r (Quit: CGI:IRC (EOF)) 17.05.49 Join funman_ [0] (~fun@rockbox/developer/funman) 17.08.05 Part LinusN 17.08.35 Quit funman (Ping timeout: 260 seconds) 17.08.41 Nick funman_ is now known as funman (~fun@rockbox/developer/funman) 17.10.14 Quit robin0800 (Remote host closed the connection) 17.14.39 Part Zagor 17.18.36 Join sunshine [0] (www-data@giant.haxx.se) 17.19.29 # first: i'm trying to use rockbox on a 5.5 gen 80 gig iPod video, which is marked as "stable," and my OS is Ubuntu 9.10 17.20.05 # the problem is, whenever i try to play a song, it plays for about 5 seconds and gives an undefined error with a string of numbers/letters 17.20.14 # there are NO hits on google, whatsoever 17.20.33 # the OS version is irrelevant, but the rockbox version is 17.20.44 # stable. 3.6 17.20.55 # i only mentioned OS in case fixes related to it were going to be for windows ^_^ 17.20.56 # try with a current build and see if it fixes the problem 17.21.03 # funman: not that :) 17.21.15 # sunshine: if I'm allowed to guess, you installed the 80G build, and not the 30GB build, right? 17.21.15 # gevaerts: ? 17.21.22 # correct 17.21.45 # You probably have a refurbished model, with a mainboard from a 30GB player. Those have less RAM 17.21.59 # ...i do, actually. 17.22.04 # ipodzens.com 17.22.15 # should i try the 30gb build instead? 17.22.15 # there we go, gevaerts WIN! ;) 17.22.16 # gevaerts: there's still no way to detect memory size at runtime ? 17.22.17 # Try installing the 30GB build 17.22.52 # funman: still only ideas 17.23.03 # didn't it/or doesn't it still, mention that the builds are to be selected by RAM size and not drive size somewhere? 17.23.10 # IS it not immediately visible? 17.23.23 # S_a_i_n_t: it's hard to tell the RAM size by looking at the player i think 17.23.36 # Can RButil detect it? 17.23.42 # * S_a_i_n_t has never used RButil 17.24.12 # It can detect it I think, but I'm not sure if it does 17.24.21 # Ah. 17.24.28 # different USB PIDs ? 17.24.30 # i believe i had to set mine to 80gb 17.24.40 # it detected the ipod, not the type/which build to use 17.25.01 # funman: no, but a SCSI READ BUFFER command that returns a bunch of xml which includes this info 17.25.34 # ah, it seems XML is always the answer 17.27.22 # okay, so i installed the 30gb build. my second problem is, while dicking around with it before, i removed all of my music to see if it was a problem of adding too much at once, and no matter how i try and clear the cache (for lack of a better term), it still shows all the removed artists 17.27.28 # i used disktidy 17.27.38 # i went through the ./trashes1000 folder 17.27.54 # remove .rockbox/database_tcd* 17.28.00 # or reinitialize the database from the menu 17.28.49 Quit funman (Quit: free(random());) 17.29.12 # i've also noticed that, even with trying to reinstall multiple times, themes etc stay the same. complete uninstallation and reinstallation included. 17.30.04 # I believe the Rockbox Utility just installs the 30GB build to be on the safe side 17.30.41 # it used to default to the 30GB one always 17.30.50 # i dunno if the detection got implemented 17.31.03 # once i get some music on there, i'll test out the 30gb and see if that doesn't fix the problem 17.31.11 # sunshine: you installed the 3.6 release version? 17.31.30 # yes 17.32.19 # when i installed, autodetect wasn't really working, it found the mountpoint but not the type of ipod i had 17.32.23 # how do you mean "themes stay the same"? 17.32.37 # removing the .rockbox folder should kill everything. 17.32.37 # oh, i applied a theme, and even after what i thought was a freshinstall, the theme was still applied. 17.32.42 # ah. 17.32.46 # therein lies the problem. 17.32.48 # because the WPS syntax changed for the themes after the release. New themes won't work with the release version and you get the fallback theme. 17.32.56 # uninstalling only removes the files that installing created. 17.33.06 # it doesn't delete your settings, or any themes you downloaded, or any other files. 17.33.09 # "uninstalling" rockbox with rbutil only removes the bootloader on the iPods 17.33.24 # even if you completely uninstall? 17.33.26 # S_a_i_n_t: no, it removes the build as well 17.33.30 # it says files and everything as well 17.33.36 # and then you remove the bootloader separately 17.33.38 # Yes. It removes all the files we installed. 17.33.38 # new and old version themes are both available, I believe recent Rockbox Utility downloads the new ones 17.34.34 # ...well, will you look at that. 17.34.49 # looks like installing the 30gb build is what i needed all along 17.34.51 # >.< 17.35.12 # thanks for all the help, everyone. 17.35.12 Quit bieber (Ping timeout: 264 seconds) 17.35.35 # It is rather misleading, you assume it refers to drive size (and it foes), but drive size isn't the relevant factor 17.35.43 # *does 17.36.07 # haha, well, luckily there's somewhere to go and ask for help :) 17.36.18 # i keep meaning to make it check the ram size at boot 17.36.21 # haven't gotten around to it yet 17.36.48 # I *believe* the manual mentions it, but, I'm sure very few people that use RButil install whilst reading the manual step-by-step. 17.37.41 # well, there are really not thta many refurbed ones around, by comparison 17.37.49 # this affects very few people 17.38.06 # it's fair enough. if it's mentioned in the manual, it's my mistake for not checking on that. 17.39.01 # with that, i'll be off. thanks again for the help and patience! 17.39.09 Quit sunshine (Quit: CGI:IRC) 17.44.50 # Torne: How does RButil detect the presence of a previous install? IS it simply looking for a .rockbox folder? 17.45.05 # it looks for .rockbox/rockbox-info.txt i think 17.46.46 # is that left behind after an "uninstall"? I always assumed that it left the whole .rockbox folder behind during an uninstall. I haven't used it myself, but the GF does and it always complains about detecting a previous version. 17.47.09 # (this is after an uninstall) 17.48.48 # uninstall removes whatever was listed as installed in rbutil.log 17.48.57 # it doens't look like it removes rbutil.log though ;) 17.49.07 # and it uses rbutil.log to detect previous installs as well 17.49.14 # Aha. 17.49.28 # this seems generally sensible 17.50.13 # I was wondering, I mentioned it in community the other day, would it be possible to prompt users about the fact that the .rockbox folder is being left behind and give them the opportunity to remove it completely? 17.50.31 # I have seen a few people express surprise that there are "leftovers" 17.51.26 Quit flydutch (Quit: /* empty */) 17.51.48 # yes. it is possible. 17.51.50 # we await a patch :) 17.51.55 Quit pamaury (Remote host closed the connection) 17.52.05 Join stripwax [0] (~Miranda@87-194-34-169.bethere.co.uk) 17.52.27 # hehehe, graphical installers are definitely not my cup of tea ;) 17.54.19 Quit antil33t (Read error: Connection reset by peer) 17.54.25 Join antil33t [0] (~Mudkips@124-197-51-80.callplus.net.nz) 18.00.12 Quit linuxguy3 (Ping timeout: 245 seconds) 18.01.23 Join linuxguy3 [0] (~timj@adsl-75-58-38-68.dsl.emhril.sbcglobal.net) 18.02.37 Quit petur (Quit: *plop*) 18.02.52 # <_threeothree> hi, anyone ever bricked a clip or clip+ and? does it void the warranty? 18.03.21 # yes and probabl 18.03.36 # funman is our resident "Sansa Bricker". But he isn't around right now. 18.03.40 # hummm... why is the Ipod 3G pad (and only that) special in "Mazezam"? 18.03.48 # you are not likely to brick it 18.03.56 # I guess it depends what you were doing when you bricked it. 18.04.06 # If you just install rockbox the risk is miniscule :) 18.04.20 # as long as it doesn't run out of power mid-way through flashing or something, it'll be fine 18.04.48 # <_threeothree> so risk is minimal to brick it while dropping rockbox on it? 18.05.00 # Indeed. 18.05.28 # <_threeothree> can it only be bricke while installing? 18.05.31 Join flydutch [0] (~flydutch@host129-160-dynamic.15-87-r.retail.telecomitalia.it) 18.05.49 # Dropping a brick (or similarly heavy object) on it will do it too ;) 18.05.53 # Only while installing the bootloader 18.05.56 # which you only have to do once 18.05.58 # <_threeothree> :D 18.06.07 # after that, you don't need to touch the main firmware image any more 18.06.11 # Also, bashing it with a hammer etc. 18.06.25 # upgrading rockbox and so on is perfectly safe 18.06.39 # <_threeothree> ok thanks for the hints ;) 18.07.14 # Just make sure the battery is well charged before flashing and all should be well. 18.07.34 # <_threeothree> ok 18.10.06 # Torne: What is the status of FS#6272? I see recent(-ish) chatter on the tracker, but the patch is relatively old itself. 18.10.18 # the patch works 18.10.26 # modulo english.lang always conflicting, of course 18.10.32 # but it doesn't do the thing very cleverly 18.10.34 # Oh, wow...never mind. Just found the forum thread about ti. Man, that was random. 18.10.47 # i worked out with AlexP what to do about it, while at devcon 18.10.53 # i just haven't gotten around to implementing a new version yet 18.11.05 # the current one does work, but behaves slightly weirdly in some respects and makes the menus more complicated 18.11.16 # so, i want to do it differently before committing. 18.11.43 # Now worries, I know you're a busy man. I use the patch currently, I was just wondering if it was still in "active" development. 18.11.59 # well i've not done it yet 18.12.03 # so technically no :) 18.12.11 # but i intend to 18.13.24 Quit swilde (Quit: ERC Version 5.3 (IRC client for Emacs)) 18.18.11 Join liar [0] (~liar@clnet-p09-185.ikbnet.co.at) 18.19.37 Join bertrik [0] (~bertrik@rockbox/developer/bertrik) 18.20.29 # I read that accessory power support on the iPods can reduce runtime, is this by a considerable ammount? 18.20.35 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 18.20.52 # the runtime for most of the ipods is long enough that even a small drain is a measurable difference, yes 18.21.37 # accessory power is something like 0.5-2mA if i remember correctly 18.22.07 # but the ipods can manage to get down to 24mA or so with the display turned off... 18.22.22 Join Jerom [0] (~jerome@95.171.137.241) 18.22.24 # Hmmm. Thanks. So, basically if I seldom use accesories it would pay to bother to enable/disable accessory power rather than leaving it on? 18.22.43 # well, you might get half an hour or even an hour if you turn it off.. 18.23.08 # Half an hour more is half an hour more ;) thanks. 18.23.31 # Can we autodetect when to enable accessory power? 18.24.40 # no 18.24.48 Join kachna [0] (~kachna@r4ax178.net.upc.cz) 18.24.55 # at least, i don't think so. 18.25.00 # the original firmware never turns it off 18.29.40 Quit stripwax (Quit: http://miranda-im.org) 18.42.24 *** Saving seen data "./dancer.seen" 18.43.30 Join DerPapst1 [0] (~Alexander@p5099d40e.dip0.t-ipconnect.de) 18.43.31 Join pamaury_ [0] (~quassel@p5DDED774.dip.t-dialin.net) 18.43.51 Quit DerPapst (Ping timeout: 260 seconds) 18.44.20 Quit pamaury (Ping timeout: 265 seconds) 18.44.40 Join domonoky [0] (~Domonoky@rockbox/developer/domonoky) 18.49.03 Join stripwax [0] (~Miranda@87-194-34-169.bethere.co.uk) 18.54.49 Nick BSOD90|away is now known as BSOD90 (~bsod@v35177.1blu.de) 18.55.30 Join domonoky1 [0] (~Domonoky@agsb-d9bd9781.pool.mediaWays.net) 18.55.44 Nick pamaury_ is now known as pamaury (~quassel@p5DDED774.dip.t-dialin.net) 18.55.57 Quit pamaury (Changing host) 18.55.57 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 18.57.26 Quit domonoky (Ping timeout: 265 seconds) 18.58.03 Quit mt (Ping timeout: 240 seconds) 19.02.10 Join mt [0] (~mtee@rockbox/developer/mt) 19.19.44 Join Horscht [0] (~Horscht2@xbmc/user/horscht) 19.22.09 Quit DerPapst1 (Quit: Leaving.) 19.26.35 Join M3DLG [0] (~M3DLG@212.183.140.4) 19.28.03 Quit einhirn (Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org) 19.29.22 Quit jfc (Ping timeout: 245 seconds) 19.32.53 Quit stripwax (Quit: http://miranda-im.org) 19.36.04 # pixelma: ping 19.37.16 Quit M3DLG (Ping timeout: 260 seconds) 19.37.42 Join bmbl [0] (~Miranda@unaffiliated/bmbl) 19.38.02 # pixelma: If you get a chance, can you have a look at this syntax for me please? http://rockbox.pastebin.ca/1891238 19.38.41 # the uncommented line works fine, the commented lines parse, but don't display a "true" conditon 19.39.41 Join rado1 [0] (~jon@66-214-153-109.dhcp.mtpk.ca.charter.com) 19.40.54 # How do I use the USB keypad mode on my ipod mini, when I plug it in it starts to go into the USB Keypad Mode, but then it all the sudden turns into a disk and it goes away? 19.42.44 Join M3DLG [0] (~M3DLG@212.183.140.35) 19.45.49 Quit scorche (Disconnected by services) 19.45.50 Quit M3DLG (Client Quit) 19.45.59 Join scorche` [0] (~scorche@rockbox/administrator/scorche) 19.46.11 Join funman [0] (~fun@rockbox/developer/funman) 19.47.22 # amr: ping 19.48.08 # rado1: which version of Rockbox are you using? 19.48.36 # mc2739, I just installed it yesterday from the gui program 19.48.47 # I use Ubuntu Linux 10.04 19.49.21 # are you using the stable release (3.6) or one of the development builds? 19.52.17 # rado1: if you go into the System menu and select Rockbox Info, what does the vottom line show? 19.52.39 # *bottom 19.55.17 Join mk429 [0] (mk429@spoon.netsoc.tcd.ie) 19.57.52 Join jfc [0] (~john@dpc6682208002.direcpc.com) 19.59.02 Join antil33t1 [0] (~Mudkips@124-197-51-80.callplus.net.nz) 19.59.51 Quit bmbl (*.net *.split) 19.59.51 Quit liar (*.net *.split) 19.59.51 Quit antil33t (*.net *.split) 19.59.51 Quit jgarvey (*.net *.split) 19.59.51 Quit shai (*.net *.split) 19.59.52 Quit mk429_ (*.net *.split) 19.59.52 Quit topik (*.net *.split) 19.59.53 Quit z35 (*.net *.split) 19.59.53 Quit avacore^ (*.net *.split) 19.59.53 Quit godzirra (*.net *.split) 19.59.53 Quit CIA-6 (*.net *.split) 19.59.53 Quit soap (*.net *.split) 19.59.54 Quit gevaerts (*.net *.split) 19.59.54 Quit marines (*.net *.split) 19.59.54 Quit YPSY (*.net *.split) 19.59.55 Quit Guest97482 (*.net *.split) 19.59.55 Quit elcan (*.net *.split) 19.59.55 Quit FOAD (*.net *.split) 19.59.55 Quit crwl (*.net *.split) 19.59.55 Quit wombat23 (*.net *.split) 19.59.55 Quit Zarggg (*.net *.split) 19.59.56 Quit simonrvn (*.net *.split) 19.59.56 Quit cjcopi (*.net *.split) 19.59.56 Quit kadoban (*.net *.split) 19.59.56 Quit powell14ski_ (*.net *.split) 19.59.56 Quit feisar_ (*.net *.split) 19.59.56 Quit Kohlrabi (*.net *.split) 19.59.57 Quit rado1 (*.net *.split) 19.59.57 Quit t0rc (*.net *.split) 19.59.57 Quit preglow (*.net *.split) 19.59.57 Quit jhMikeS (*.net *.split) 19.59.57 Quit BSOD90 (*.net *.split) 19.59.57 Quit Dhraakellian (*.net *.split) 19.59.57 Quit Bagder (*.net *.split) 19.59.58 Quit sevard (*.net *.split) 19.59.58 Quit incant (*.net *.split) 19.59.58 Quit balintx (*.net *.split) 19.59.58 Quit [blue] (*.net *.split) 19.59.59 Quit slck (*.net *.split) 19.59.59 Quit whydoubt_ (*.net *.split) 19.59.59 Quit [keanu] (*.net *.split) 19.59.59 Quit Battousai (*.net *.split) 19.59.59 Quit Galois (*.net *.split) 20.00.00 Quit flydutch (*.net *.split) 20.00.00 Quit TheSeven (*.net *.split) 20.00.00 Quit BeFalou (*.net *.split) 20.00.00 Quit mikroflops (*.net *.split) 20.00.01 Quit kisak (*.net *.split) 20.00.01 Quit ved (*.net *.split) 20.00.01 Quit scorche` (*.net *.split) 20.00.01 Quit linuxguy3 (*.net *.split) 20.00.01 Quit hebz0rl (*.net *.split) 20.00.01 Quit Rob2223 (*.net *.split) 20.00.02 Quit blithe (*.net *.split) 20.00.02 Quit maraz (*.net *.split) 20.00.02 Quit Unhelpful (*.net *.split) 20.00.02 Quit ChanServ (*.net *.split) 20.01.18 Join topik_ [0] (awesome@wtf.grmpf.org) 20.01.18 Join scorche` [0] (~scorche@rockbox/administrator/scorche) 20.01.18 Join rado1 [0] (~jon@66-214-153-109.dhcp.mtpk.ca.charter.com) 20.01.18 Join flydutch [0] (~flydutch@host129-160-dynamic.15-87-r.retail.telecomitalia.it) 20.01.18 Join linuxguy3 [0] (~timj@adsl-75-58-38-68.dsl.emhril.sbcglobal.net) 20.01.18 Join marines [0] (~quassel@abzo170.neoplus.adsl.tpnet.pl) 20.01.18 Join balintx [0] (~balintx@fibhost-67-58-201.fibernet.hu) 20.01.18 Join t0rc [0] (~t0rc@unaffiliated/t0rc/x-5233201) 20.01.18 Join hebz0rl [0] (~hebz0rl@dslb-088-065-216-095.pools.arcor-ip.net) 20.01.18 Join wombat23 [0] (~beuteltie@adsl-99-39-2-249.dsl.pltn13.sbcglobal.net) 20.01.18 Join Rob2223 [0] (~Miranda@p4FDC9B9E.dip.t-dialin.net) 20.01.18 Join Zarggg [0] (~zarggg@65-78-69-194.c3-0.eas-ubr6.atw-eas.pa.cable.rcn.com) 20.01.18 Join TheSeven [0] (~TheSeven@rockbox/developer/TheSeven) 20.01.18 Join z35 [0] (~z35@ool-457a4517.dyn.optonline.net) 20.01.18 Join [blue] [0] (~blue@ip70-178-120-137.ks.ks.cox.net) 20.01.18 Join preglow [0] (thomj@rockbox/developer/preglow) 20.01.18 Join simonrvn [0] (simon@205.190-ppp.3menatwork.com) 20.01.18 Join jhMikeS [0] (~jethead71@rockbox/developer/jhMikeS) 20.01.18 Join avacore^ [0] (nobody@1008ds1-rdo.0.fullrate.dk) 20.01.18 Join slck [0] (Venci@Slackware.SlackPix.Com) 20.01.18 Join cjcopi [0] (~craig@adsl-70-239-1-198.dsl.bcvloh.sbcglobal.net) 20.01.18 Join BSOD90 [0] (~bsod@v35177.1blu.de) 20.01.18 Join YPSY [0] (~ypsy@geekpadawan.de) 20.01.18 Join BeFalou [0] (~mamutoi@unaffiliated/befalou) 20.01.18 Join whydoubt_ [0] (~whydoubt@ip68-12-76-9.ok.ok.cox.net) 20.01.18 Join godzirra [0] (~godzirra@c-174-49-30-11.hsd1.tn.comcast.net) 20.01.18 Join [keanu] [0] (~keanu@unaffiliated/keanu) 20.01.18 Join CIA-6 [0] (~CIA@208.69.182.149) 20.01.18 Join Guest97482 [0] (~sharp@sauropod.org) 20.01.18 Join mikroflops [0] (~yogurt@90-224-31-157-no112.tbcn.telia.com) 20.01.18 Join Battousai [0] (~bryan@gentoo/developer/battousai) 20.01.18 Join kadoban [0] (~mud@cpe-67-247-80-129.rochester.res.rr.com) 20.01.18 Join Dhraakellian [0] (~ntryon@cpe-67-240-248-41.rochester.res.rr.com) 20.01.18 Join Bagder [0] (~daniel@rockbox/developer/bagder) 20.01.18 Join powell14ski_ [0] (~powell14s@c-174-51-160-240.hsd1.co.comcast.net) 20.01.18 Join elcan [0] (user36@pr0.us) 20.01.18 Join feisar_ [0] (jljhook@irkki.fi) 20.01.18 Join blithe [0] (~blithe@72.14.176.144) 20.01.18 Join sevard [0] (sev@unaffiliated/sevard) 20.01.18 Join soap [0] (~soap@rockbox/staff/soap) 20.01.18 Join FOAD [0] (~dok@83.160.60.104) 20.01.18 Join maraz [0] (maraz@kapsi.fi) 20.01.18 Join Galois [0] (djao@efnet.math.uwaterloo.ca) 20.01.18 Join gevaerts [0] (~fg@rockbox/developer/gevaerts) 20.01.18 Join kisak [0] (~kisak@c-98-235-209-218.hsd1.pa.comcast.net) 20.01.18 Join Unhelpful [0] (~quassel@rockbox/developer/Unhelpful) 20.01.18 Join incant [0] (~philippe@zone42.rdc.uottawa.ca) 20.01.18 Join crwl [0] (~crwlll@dsl-jklbrasgw1-fe10fb00-173.dhcp.inet.fi) 20.01.18 Join ved [0] (ved@ddsbox.co.cc) 20.01.18 Join Kohlrabi [0] (~Kohlrabi@frustum.nosebud.de) 20.01.18 Join ChanServ [0] (ChanServ@services.) 20.01.18 Mode "#rockbox +o ChanServ " by leguin.freenode.net 20.04.32 Join incant_ [0] (~philippe@zone42.rdc.uottawa.ca) 20.04.38 Join preglow_ [0] (thomj@tvilling2.pvv.ntnu.no) 20.04.47 Join sevard_ [0] (sev@216.164.6.24) 20.04.52 # S_a_i_n_t: what if you just leave one %s on the line, maybe at the start? Not saying that this is the culprit but as far as I know one would do anyway, more is redundent 20.05.12 Join BSOD90_ [0] (~bsod@v35177.1blu.de) 20.05.35 # pixelma: I tried that...still, I have no idea why it doesn't work. 20.05.40 Quit BSOD90 (Write error: Broken pipe) 20.05.40 Quit preglow (Write error: Broken pipe) 20.05.41 Quit incant (Write error: Broken pipe) 20.05.41 Quit Dhraakellian (Write error: Broken pipe) 20.05.42 Quit sevard (Write error: Broken pipe) 20.06.04 # pamaury: where did you find the settings for CCU_USB_THINGY bits ? 20.06.12 # Now I'm having to resort to using %pE to switch conditional viewports, instead of having the one viewport with conditional info :/ 20.06.17 # S_a_i_n_t: %al isn't needed at all, at least it once was the default and you don't mix alignment on a line 20.06.18 # funman: in the OF 20.06.42 Join bmbl [0] (~Miranda@unaffiliated/bmbl) 20.06.50 # you remember where? i'm seeing something a bit different on clipv2 20.06.52 # pixelma: I know, it's my coding style though...old habbits die hard. 20.06.55 Join panni_ [0] (hannes@ip-95-222-52-93.unitymediagroup.de) 20.07.01 Join shai [0] (~Shai@l192-117-110-233.cable.actcom.net.il) 20.07.02 # funman: in audio_int 20.07.03 Join liar [0] (~liar@clnet-p09-185.ikbnet.co.at) 20.07.17 # it's part of the usb init sequence 20.07.39 # S_a_i_n_t: I have no idea either (and never used %pE 20.07.42 # ) 20.07.42 Join jgarvey [0] (~jgarvey@cpe-065-190-066-089.nc.res.rr.com) 20.07.42 Join mk429_ [0] (mk429@spoon.netsoc.tcd.ie) 20.08.08 # the function which sets the usb clock div clears bit 20:21 and sets bit 20 20.08.16 # I extracted it from the OF version of which you gave me the ida file. 20.08.44 # I'm not sure it's from the usb clock function but I can't remember 20.08.57 # 0x1A88 in clip+ 1.02.09 20.09.40 # I don't have a disassembly of the clip+ unfortunately, but you say it's different between fuzev2 and clip+ ? 20.10.11 # no i didn't say that 20.10.12 Join Luca_S [0] (www-data@giant.haxx.se) 20.10.25 Quit mk429_ (Ping timeout: 258 seconds) 20.11.16 # how do I adjust my ipod screen brightness? 20.11.31 # i say when USB peripheral is enabled this function is called and does some stuff with CCU_USB_THINGY bits 20.11.40 # rado1: which Ipod do you have? 20.11.53 # pixelma, mini 1st gen 20.12.00 # funman: ok, wait a minute so I look at the disassembly :) 20.12.04 Nick sevard_ is now known as sevard (sev@216.164.6.24) 20.12.10 Quit sevard (Changing host) 20.12.10 Join sevard [0] (sev@unaffiliated/sevard) 20.12.19 # rado1: I don't think you can adjust brightness on the Minis 20.12.38 # :( 20.12.48 # Ick...my %pE conditional viewport solution works...but I *really* don't like having to fix things with ugly code solutions. 20.12.49 # btw it's bits 25:24 not 21:20 20.13.02 # CCU... = (CCU... & 0x3000000) | 0x1000000; 20.13.04 # As far as I'm concerned I now have 4 more viewports than I need. :/ 20.13.25 # S_a_i_n_t: maybe it's a bug, I don't know 20.14.01 # A lot of tags seem to be quite "iffy" at the moment. As far as I'm concerned, if it parses, it should work. 20.14.15 # btw i just checked that the OF uses 48MHz as USB freq 20.14.42 Quit flydutch (Quit: /* empty */) 20.14.44 # %t %mh are acting weird in the .fms, and now I find %pE and %pS acting oddly. :/ 20.14.52 # using 48MHz in rockbox gives me a panic (wrong architecture) 20.15.08 Join Dhraakellian [0] (~ntryon@cpe-67-240-248-41.rochester.res.rr.com) 20.15.15 # I guess JdGordon has a lot on his plate with the new parser stuff...I really wish I was a better coder and could help more. 20.15.27 Quit CGL (Ping timeout: 260 seconds) 20.15.30 # pixelma, it seems strange because you can control how long it takes the backlight to fade in 20.15.37 # funman: we found out that the good clock speed is 60Mhz it seems 20.16.11 # what was wrong when using 48MHz ? 20.17.04 # when using other speed, either usb core don't init properly (all registers are zero => wrong architecture ?) or it's doesn't do data transfers. 20.17.48 # did you find the OF init code yet? 20.18.00 # rado1: yes, but that's done in a quite ineffective way (switching backlight on and off which needs quite some processing power overhead). It's ok for the relatively short fade-in or fade-out duration but always would eat quite a lot battery 20.18.10 # if I remember correctly 20.18.29 # funman: ok so in audio_isr, in my disassembly, at address 0x9878, the OF calls a function which clear bit 12, and then it calls another function which clear which mask 0x300000 20.18.38 # pixelma, gotcha 20.18.48 # s/which/with 20.19.30 # pamaury: the function i gave you is part of enable_peripheral (called at 0x9740) so technically it should happen before what you are doing 20.19.58 # rado1: I know it's unfortunate as the Mini's screen is very bright 20.20.08 # and it touches the CCU_USB_THINGY register ? 20.20.49 # Question: What do you think is an appropriate period of time to notify the user about the next track for? And how long before the end of the current track should it display? 20.20.52 # pixelma, ya I didn't want to wake my wife up with the screen brightness 20.22.00 # you could turn the backlight off and use the voice UI ;) 20.22.18 # pamaury: 0x9878? which version is that ? 20.23.09 # pixelma, good point how do I get that going? 20.23.35 # S_a_i_n_t: I personally like the idea of the Next Track info appearing during the whole of the currently playing track, in case I want to skip forwards, but obviously as space is limited this'd be best as an alternating subline 20.24.34 # funman: 2.01.16a if my files are correct 20.24.45 # pamaury: http://pastie.org/1022176 : 48MHz, no panics (unable to enumerate, device not accepting address, device descriptor read/64 error -62) 20.24.49 # evilnick_B: I have it replacing the current track info, with a ehading of "next track" so as not to confuse the hell out of people, that I cal call X seconds before the track ends. 20.24.58 # rado1: you just need to get a voice file, voicing should be enabled (it is by default unless you turned it off). By the way, our manual is a nice read and would explain to you how :) 20.25.01 # I was wondering what an appropriate X seconds is. 20.25.06 # pamaury: ok, any reason you're not reading Clip+ OF 01.02.09 ? 20.25.24 # pixelma, thanks 20.25.28 Join Buschel [0] (~~andree@p54A3A8F3.dip.t-dialin.net) 20.25.28 Join Xerion [0] (~xerion@82-170-197-160.ip.telfort.nl) 20.25.36 Join wodz [0] (~wodz@inet20909nc-3s.nat.umts.dynamic.eranet.pl) 20.25.41 # S_a_i_n_t: Sure, which is why I said that I'd *personally* want to see that information straight away, not have to wait for the outro of the first track 20.25.47 # funman: you have the ida file for this version I think 20.25.51 # *gave 20.25.57 # ...or whatever arbitrary X value you choose! 20.26.06 # pamaury: ok this is clipv2. at 0x9878 I only see a NOP though 20.27.02 # i see the functions however 20.27.23 # funman: starting from 0x9878 to 0x9894 it does what I described 20.27.35 # evilnick_B: I was trying to look for a betetr way to do it, obviously space is an issue on the Nano, and I had users complain the an alternation next/current info display way really confusing. 20.28.04 # Apparently it made them dizzy if it alternated too quickly, and confused them as to which track was up if it alternated too slowly :/ 20.28.16 # funman: however you patch is strange: you replace 0x300000 with 0x3000000 whereras I really see 0x300000 in my disassembly. But I don't know where you found the first sequence about CCU_USB_THINGY 20.28.25 # yeah this hunk is wrong, i'm testing withouyt it 20.28.41 # S_a_i_n_t: Use whichever value you personally like and they can change it if they are that bothered by it 20.28.43 # works too, just ignore the last hunk 20.28.53 # pamaury: 20:08 < funman> 0x1A88 in clip+ 1.02.09 20.29.00 # Well, you'd think so ;) 20.29.27 # Some look at WPS code as a totally foreign language 20.29.30 # pamaury: 0x191E in clipv2 02.01.16 20.30.25 # funman: okay but from where is it called ? I don't have any call to it in my disassembly 20.30.48 # S_a_i_n_t: I suppose what I'm trying to say is that you shouldn't be trying to please EVERYONE, as something like the WPS is so subjective that the task is impossible. Just go with what YOU like and either they'll put up or learn how to change it (and it'll be what? A 2/3 character change?!) 20.30.52 # it's in a table of functions to modify peripheral clock dividers 20.31.01 # table is at 0x8188 20.31.07 # in enable_peripheral ? 20.31.17 # in a function called by it 20.31.35 # 1 function at 0x2040 (called by enable_peripheral() and others) 20.31.58 # I would have liked it to be very simple to change, but a bug/code not working as I expected made me have to complicate the code to a rather ridiculous degree. 20.32.01 # one function at 0x1FE8 (called by a bunch of other clock-related functions) 20.32.15 # funman: ok I see it, I missed it the first time it seems 20.32.25 # It's "alternating conditional viewport maze hell of doom mega 10,000" 20.32.28 # So the OF uses 48Mhz clock ? 20.32.35 # i believe so 20.32.52 # let me try with you patch, to confirm it works 20.34.33 # I thought pamaury already made it work with 60 MHz ? 20.35.30 # yeah but funman found out some settings I missed in an unknown register 20.35.35 # true but i hope it fails in a different way at 48MHz, so it could help to fix the problem 20.37.06 # funman: with your setting, I don't get any setup interrupt, the same problem as before 20.37.26 # you have no msg on the host? 20.37.54 # yes I have but I have the usb analyzer which tells me the host sends setup and I have the device which says it does not see setup packet 20.38.04 # This problem was solved by using a 60Mhz clock 20.38.16 # OTOH the hardware registers are not all zero, right? 20.39.14 # yes 20.39.56 # how can i check if the setup interrupt happens? is it 'enumdone' ? 20.40.05 # * gevaerts thinks that 48MHz would be a strange clock to use for usb 20.40.28 # nope, you would see lots of messages if a setup packet is received :) 20.40.38 # pamaury: where? 20.40.40 Quit marines (Remote host closed the connection) 20.40.40 # on the host? 20.40.48 # on device, in logf 20.41.07 # i must rebuild for logf; what should i be looking for ? 20.42.12 # "usb-drv: setup on EP0 OUT" 20.42.25 Join MethoS- [0] (~clemens@134.102.106.250) 20.42.26 *** Saving seen data "./dancer.seen" 20.42.31 # S_a_i_n_t: the problem with %pE not working reminds me a bit of next track info on hwcodec at all. On these next track info is only available when part of the next track is in the buffer which is due to the small RAM size somewhen within the last 1..1.5 minute(s) of the currently playing track (depending on bitrate and when it actually starts rebuffering). Simply checking for %?Fn fails often, I work around that by forcing the line to regularly 20.42.31 # update making it a subline 20.42.34 # gevaerts: http://www.rockbox.org/irc/log-20100621#21:09:47 bertrik thinks 48MHz is not so strange, who should we believe? 20.42.42 # I'm trying different settings: 60Mhz, no ccu tweaking in you patch => works 20.42.55 # 60Mhz, ccu tweaking in your patch => doesn't work 20.43.15 # funman: the one that gives working results :) 20.43.20 # so it definitely affects clock 20.43.41 # funman: 48MHz implies 10 bits per cycle, which looks a bit weird to me 20.43.58 Join stripwax [0] (~Miranda@87-194-34-169.bethere.co.uk) 20.44.06 # S_a_i_n_t: not so nice side effect is though that changing the subline also resets scrolling but I found %t(6) is often quite suitable 20.44.19 # pixelma: I see that we have fixing bugs with overcomplicated code in common then ;) 20.44.40 # the transceiver definitely runs at either 30MHz or 60MHz. Of course that's not necessarily visible 20.44.43 # gevaerts: AMSv1 use 48MHz 20.44.48 # with the font I use on this display size 20.44.56 # The way I've made this very simple effect work is really not so simple... 20.45.02 # I know for sure that there are USB controllers using 48MHz, but it doesn't mean that it can't be 60 MHz for other controllers 20.45.35 # S_a_i_n_t: I think this bug or effect is not so easy to fix, don't know 20.46.02 # funman: no settings work, only 60Mhz without your ccu tweak works, all other combinaison fail 20.46.08 # %s seems to mess up more things than it should for no good reason. 20.46.17 # pamaury: perhaps there's another bit missing 20.46.28 # I understand the scrolling code is quite a nightmare though. 20.47.17 # I would tend to say that with have a working combinaison so it doesn't matter :) 20.48.13 # i don't know what exactly the current problem is so i'm just throwing ideas 20.48.45 # ff_imdct_half seems to be doing something wrong .. at least in wma pro :( 20.49.09 # try to rename it ff_imdct_half_pro 20.49.37 # My current problem with usb is setup packet. Something is wrong. For example, I get setup packet interrupt in a state where EP0 is not allowed to receive any data. I suspect there is kind of delayed completion accross usb reset 20.50.46 # S_a_i_n_t: would you try if adding a %t(x) and a ; at the end helps? Maybe it's such an update problem too? 20.52.24 # pixelma: I actually tried that. "%?pE(10)" works fine. But "%?pE(10)<%?Ia<%s%al%Ia|%s%al%D(1)>|%?id<%s%al%id|%s%d(1)>>" fails. 20.52.42 # pamaury: the function which clears 0x300000 is a bit more complex than that 20.53.00 Quit solrize (Changing host) 20.53.00 Join solrize [0] (~phr@unaffiliated/solrize) 20.53.02 # even "%?pE(10)<%sA|%sB>" works. 20.53.20 # So, I don't believe it to be a scrolling problem either. 20.53.39 # funman: really ? What more is the function doing ? 20.53.46 # S_a_i_n_t: and "%t(5)%?pE(10)<%?Ia<%s%al%Ia|%s%al%D(1)>|%?id<%s%al%id|%s%d(1)>>;" to force a regular update? 20.53.52 # It seems to be a problem with nesting conditionals in %pE and %pS 20.53.54 # pamaury, EP0 is really special IIRC, not sure if you can even block it from receiving data 20.54.16 # S_a_i_n_t: or metadata 20.54.30 # ah, yes. 20.54.44 # by the way - the problem on hwcodec existed as long as I can remember 20.54.59 # I tried making it a "subline" to force an update...no success there either 20.55.39 # funny thing is "true" seems to work for %pE, it just won't switch to "false" 20.55.43 # pamaury: there's a parameter or'd with the register, although it is 0 in all the calls i've found so far 20.56.04 # (unless it contains no other nested conditions) 20.56.10 # bertrik: the doc I foudn say you can and anyway where would it put the data if DMA is not running for EP0 ? 20.56.36 # well, my testing is limited...I was more intersted in getting it to work than finding out why it doesn't. 20.56.45 # funman: iirc, I kind of "inline" the call and concluded that it did what I wrote in the driver but I might be wrong 20.57.26 # pamaury, what doc are you using? can I download it somewhere? 20.57.41 # S_a_i_n_t: finding out why it doesn't might help getting it to work if it is a bug and the conditions it appears give some hints 20.58.01 # and it then can be fixed 20.58.04 # Any Nano 1st or 2nd Gen Owners interested in testing a new(-ish) theme? <--Highlight me. 20.58.07 # bertrik: the code I found which have the same controller it seems 20.58.45 # so the linux patch, the s3c driver in linux, some doc like the S3C one which describe some registers (for an older version however) 20.58.51 # pixelma: Yesh, I know. I will do some more thourough testing in a few hours, I'm really very tired now but I expect to get a second wind soon. 20.59.00 # *Yes rather 20.59.35 # pamaury, ok, I'll have a look to see if I can find that somewhere 21.00.17 # anyway, in DMA mode, it doesn't make sense, it would not trigger an interrupt and throw the data. It must be a programming error somewxhere 21.01.11 # Talking about the usb driver, nice :) 21.01.30 # Does it really use DMA for EP0? I've worked with a controller where EP0 was PIO only. 21.01.37 # yes it does 21.01.56 # well you need to setup the address for DMA 21.04.40 # ranma: did you try to run the OF on clip+ ? 21.05.11 # the only thing I see is that the driver could trigger an setup interrupt if you are waiting for some data and even if you don't setup the setup_pack_cnt to 1. Which would be a bit weird. 21.07.33 # The other strange thing is that the device misses some setup packet, don't know why 21.09.38 # * pixelma wonders if AlexP is around 21.09.49 # aye 21.10.31 # funman: Just noticed your response in the "h120 battery chaerging issue" thread...so, I'm curious...what's the battery capacity setting on the DAP for then? 21.10.38 # AlexP: did you see http://www.rockbox.org/tracker/task/11437 21.10.41 # ? 21.10.59 # S_a_i_n_t: ah, it might be different if a model is known to have different batteries types 21.11.29 # pixelma: Not hithertoo 21.11.49 # sorry? 21.11.56 # yes, that's why I said I wasn't sure if his device had it or not...but if it did, then it would be in "setting/blah/blah" 21.12.04 # funman: ^ 21.12.11 # pixelma: Sorry, mispelling: hitherto 21.12.14 # er, yet :) 21.12.27 # I guess he'll still get the idea if he reads the thread though. 21.12.32 # S_a_i_n_t: feel free to correct me 21.13.02 # Battery capacity is used to calculate remaining runtime, no? 21.13.40 # Pass. I thought it had an effect on the percentile also. 21.13.50 # Nope 21.13.55 # AlexP: ah, would be nice if you could (especially the added parts wrt language, giovanni is no native speaker either) :) 21.13.56 # One of us is wrong ;) 21.13.59 # *almost* sure not 21.14.02 # I'm willing to bet its me :D 21.14.08 # pixelma: Sure 21.15.25 # * S_a_i_n_t shall edit his post to reflect this then. 21.16.30 # AlexP: also, the "generic touchscreen actions plus something on a few hardware buttons" business is weird too. I'll try to think of something 21.16.42 # but if you have an idea... :) 21.17.22 # yes, I don't like it much either 21.18.09 # Tuchscreen targets could do with a big old section eplaining that the grid is only really a fallback, how the touchscreen regions work on cabbie 21.19.29 # hrmm that's not exactly what I meant 21.20.53 # um, that's odd - half my sentence didn't appear 21.21.22 # grid is... only a fallback, and how the touchscreen regions on cabbiev2 work 21.22.34 # it's targets that have a touchscreen and additionally a Power button for example. Those define all main \Actions in their own keymap files even though large parts is true for all touchscreen devices because (made-up example) \ActionStdCancel is something on touchscreen and also the Power button 21.22.39 Join scorche [0] (~scorche@rockbox/administrator/scorche) 21.23.34 # ah, ok 21.23.59 Quit scorche` (Ping timeout: 245 seconds) 21.24.14 # pamaury: i can't find other modifications of this register in disassembly 21.24.30 # (doesn't mean they don't exist) 21.26.14 # ok 21.29.51 Join petur [0] (~petur@rockbox/developer/petur) 21.30.42 # AlexP: would having the \ButtonPower etc. in the main platform file and then \opt{COWON_D2_PAD}{\ButtonPower} etc. in the keymap-touchscreen.tex be considered a worse hack than there is now? :) (in the hope you can follow my brief description) 21.31.48 # pixelma: Depends on how many touchscreen targets we end up with and how many physical buttons they have I suppose 21.31.59 # I don't have a strong preference either way 21.32.19 # I'd have to look I think 21.32.28 # yeah, true 21.33.05 # btw, for the FS task you mentioned, I can have a look wednesday night if that is OK 21.35.29 # the cleaner idea would be to have all \Actions that are there for the physical button only in the target's keymap file and the touchscreen one in the keymap-touchscreen.tex and find a why to combine if both exists. I don't know if that's possible though as flexible as it would be needed 21.36.28 Join yelped [0] (www-data@giant.haxx.se) 21.36.30 # Wednesday would be ok, I'd like to have a comment by the original author too 21.36.48 # s/why/way 21.36.56 Quit Jerom (Quit: Leaving.) 21.37.22 # Thanks to whoever enabled, USB HID, but it doesn't seem to work, at least not in mouse mode. 21.37.46 # nano 2g? 21.37.54 # Or OSX 21.37.56 # yelped: which is your target and on what OS? 21.38.00 Join Jerom [0] (~heidi@95.171.137.241) 21.38.04 # As it works here on gigabeat S and linux 21.38.46 # Sorry, Sansa Fuze v1 on windows 7. 21.39.18 # AlexP: HID works on later OSXs than 10.4 but on 10.5 at least it wasn't as reliable as on XP (tried with my c200) 21.39.46 # I've only ever used it on linux, and it is fine there :) 21.39.58 # XP is too 21.40.25 # windows 7 on sansa e200v1 is fine, too. 21.41.44 # but I guess it has something to do with the relatively new RockboxUSB on the AMS Sansas for yelped... * looking into ranma's, funman's etc. direction * 21.43.01 # i had missed r27164, last time i tried HID didn't work here 21.44.49 Quit linuxguy3 (Ping timeout: 245 seconds) 21.45.39 # it has no effect on ubuntu afaics 21.46.48 Join linuxguy3 [0] (~timj@adsl-75-57-198-60.dsl.emhril.sbcglobal.net) 21.47.06 # Could be that's it's enabled, but nobody set which keys should do what, which is why it's not doing anything? 21.47.46 # I try to add enchance 3D function to the WM8750 driver (as was done for beast). I get compile error which I don't understand: http://pastebin.com/pzVLmBcf 21.47.58 # do You have any clue? 21.48.27 Join Zigtown [0] (~Zigtown@CPE00259ce0fdb2-CM0014f8cc807a.cpe.net.cable.rogers.com) 21.48.53 # pamaury, the document I'm reading now (s3c6400 document) indeed shows either 30 or 60 MHz for the USB 2.0 PHY 21.49.27 # apparently you can also configure it for a USB 1.1 full speed mode, in which case the transceiver clock needs to be 48 MHz 21.49.48 # I'm not completely sure about the difference between a PHY and a transceiver 21.49.51 # isn't the controller totally different from s3c6400 ? 21.50.18 # no, I see a lot of matches 21.50.52 # From my guess it's the same controller but at an older revision; However I'm not sure 21.54.55 # This is really strange, the set address request does something special. I get two setup packet interrupts for it whereras only one exists ! 21.55.33 # do want to try r21764? 21.56.02 # yelped: no idea, we must ask ranma 21.57.33 # OK, thanks. Just wanted to see if I was the only one having this problem. 21.57.49 # lsusb -v errors out when HID is enabled 21.58.30 # Oh. 21.58.37 # Which means? 21.58.40 Join DerPapst [0] (~Alexander@p4FE8F59F.dip.t-dialin.net) 21.58.49 # :) 21.59.03 # it means exactly what I said, nothing else 21.59.14 # :) 22.00.10 # AlexP: I already had the "combine if this or that action exists" idea already for the remote control targets and still don't know if it is possible (as I imagine it) 22.00.33 # Oh yeah, I was going to prod at that :) 22.00.37 # But I forgot :) 22.01.11 # * pixelma wonders if the M:Robe500 is a touchscreen target with a physical button and a remote.. 22.01.33 # wodz, errors like that often disappear when you do a make clean 22.02.12 # wodz: a bug in dependancies or lang files generation 22.02.45 # I did make clean and no go 22.03.20 # pixelma: it is 22.03.33 # (unless I misunderstand what you mean) 22.04.38 # I also try deleting build dir but error is the same 22.04.52 # gevaerts: so it does have a touchscreen and one or more additional physical buttons and a remote? 22.05.23 # pixelma: it has a touchscreen, one (power) button, and a remote 22.05.37 # The remote has some more buttons, but I've never seen it 22.05.43 # if it has and I get the combining idea to work somehow for the manual then an M:Robe500 manual would need to combine three parts 22.06.31 # gevaerts: you should have seen the M:robe remote. roolku had one with him at DevCon2008 in Berlin ;) 22.06.51 Join dfkt_ [0] (~dfkt@unaffiliated/dfkt) 22.07.30 # or you could have :) 22.09.20 Quit dfkt (Ping timeout: 265 seconds) 22.11.00 # OK, I might have :) 22.11.52 # hmm the problem comes from the fact that this setting is treated as gigabeats specyfic in lang files 22.12.21 # then you need to add your mpio one way or the other 22.12.56 # or the WM codec 22.13.17 Quit yelped (Quit: CGI:IRC (Ping timeout)) 22.13.18 Quit esperegu (Read error: Connection reset by peer) 22.13.34 # I don't know the syntax of lang files at all :-/ 22.14.12 Nick dfkt_ is now known as dfkt (~dfkt@unaffiliated/dfkt) 22.16.19 # honestly I don't get why this is gigabeats specyfic in lang files. It is conditional anyway (based on #define magic) 22.18.16 # because every language string costs bin size - it would be included but not used <8and it would also make the voice file bigger) 22.18.28 Nick BSOD90_ is now known as BSOD90 (~bsod@v35177.1blu.de) 22.18.53 # when the system was introduced, the difference was quite obvious for some targets 22.20.10 # stuff like "gigabeats" or "lcd_color" are the so called features which control whether a string is included or not 22.22.01 # features.txt (in apps) defines when a feature will be true for a certain target (using the defines that are in the code anyway) 22.22.54 # thx, I'll look at this 22.24.01 # in this case, it might be the "correct" way to introduce a new feature "3d_enhancement" or somesuch 22.24.56 Quit dfkt (Ping timeout: 240 seconds) 22.28.21 Join dfkt [0] (~dfkt@unaffiliated/dfkt) 22.30.20 Quit S_a_i_n_t () 22.42.27 *** Saving seen data "./dancer.seen" 22.43.29 Part AzureWurk 22.46.33 Quit r0b- (Ping timeout: 265 seconds) 22.46.35 Join r0b- [0] (~nnscript@adsl-99-52-153-164.dsl.klmzmi.sbcglobal.net) 22.46.41 Join AzureWurk [0] (opera@c-24-21-44-114.hsd1.wa.comcast.net) 22.49.04 # wodz: how did you generate git-diff which stored file move in the diff output ? 22.50.32 # funman: -C I think 22.50.49 # funman, git diff has a -M option to detect renames in the man page 22.51.19 # pamaury: Still no luck with the misbeaving controller ? 22.51.21 # funman, oh -C detects copies and renames 22.51.41 # ah it's not what I want though, I want deletes to not store the full diff between the deleted file and nothing 22.51.55 Join GeekShadow [0] (~Antoine@reactos/tester/GeekShadow) 22.51.58 # Jerom: check the log this evening i found something which might be interesting about clocks 22.54.51 # can anyone with a MCF5250 (m5/x5) and another CF (e.g. h300) test this patch to the aac decoder? -> http://www.pastebin.org/363908 22.55.09 # the difference in decoding speed is of interest 22.55.43 # on PP5022: svn = 36.12 MHz, patched = 35,49 MHz 22.55.49 # ~2% 22.56.14 # funman: So the OF is using 48Mhz and we are using 60 and it's somehow working ? 22.59.43 # Buschel: I can try on MCF5249 but tomorrow 23.00.14 # wodz: great, I am just creating a FS-entry to collect the data 23.02.36 # I also see that someone had the issue than me: after connecting the usb a black screen 23.02.57 # Buschel: aac means which file from http://download.rockbox.org/test_files/ ? 23.03.36 # wodz: I used the 192 kbps file (nero_192.m4a) 23.04.25 # FS #11445 23.04.41 # ok, I'll try to download this but my poor GSM connection may be the problem 23.04.51 Quit Xerion (Quit: ) 23.04.56 # ouch 23.07.22 # good night! 23.10.15 Join S_a_i_n_t [0] (S_a_i_n_t@203.184.2.68) 23.11.16 Quit FOAD (Quit: I'll be back) 23.11.25 Join FOAD [0] (~dok@83.160.60.104) 23.12.10 Quit Buschel (Ping timeout: 265 seconds) 23.14.03 Quit bmbl (Quit: Bye!) 23.14.10 Quit hebz0rl (Quit: Ex-Chat) 23.16.57 Join Mobius-1 [0] (www-data@giant.haxx.se) 23.19.34 Quit Mobius-1 (Client Quit) 23.22.22 Quit pamaury (Remote host closed the connection) 23.24.59 Quit r0b- (Ping timeout: 260 seconds) 23.26.40 Join r0b- [0] (~nnscript@adsl-76-235-181-20.dsl.klmzmi.sbcglobal.net) 23.28.19 Quit t0rc (Quit: Leaving) 23.28.47 Join fdinel [0] (~Miranda@modemcable235.127-131-66.mc.videotron.ca) 23.30.05 Quit wombat23 (Ping timeout: 264 seconds) 23.31.36 Join wombat23 [0] (~beuteltie@adsl-99-39-2-249.dsl.pltn13.sbcglobal.net) 23.35.26 # pixelma: iPod G3 has physically different button layout 23.36.11 # I would think that more plugins on G3 would benefit from separate button maps, perhaps even some core screens 23.36.27 Quit wombat23 (Ping timeout: 260 seconds) 23.38.01 Quit Rob2223 (Quit: Rob2223) 23.38.14 Join Rob2222 [0] (~Miranda@p4FDC9B9E.dip.t-dialin.net) 23.39.08 # amiconn: would it be possible to alter lcdlinear[] in plugin to see the effect immediately? 23.41.00 # Perhaps. Right now test_grey switches linearisation off 23.42.07 # * amiconn is reminded of the grey blitting optimisation for mpio 23.43.08 Join wombat23 [0] (~beuteltie@adsl-99-39-2-249.dsl.pltn13.sbcglobal.net) 23.45.10 # amiconn: I am asking because I am not 100% satisfied with current lcdlinear[] for HD200 - it produces 'glitch' in test_fps (the gradient screen). It is very frustrating process to alter array, recompile plugins and test 23.45.32 # What kind of glitch? 23.45.47 Quit komputes (Quit: I haven't slept for ten days, because that would be too long.) 23.47.13 # it looks like 'noise line' 23.47.22 # vertical 23.47.46 # 'vertical line noise' maybe? 23.48.31 # You mean the line that slowly moves up or down? 23.48.40 # no 23.49.26 # I can try to take a photo of this (with long exposure time) 23.52.05 Part AzureWurk 23.52.53 Quit wodz (Quit: Leaving) 23.54.55 Quit wombat23 (Ping timeout: 252 seconds) 23.56.43 Quit funman (Quit: free(random());) 23.58.25 Quit Jerom (Read error: Connection reset by peer)