--- Log for 11.10.110 Server: kornbluth.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 8 days and 23 hours ago 00.02.51 # I wanted to test a Player sim for some other reason and the build failed in some _mp3* things. Still having the patch applied so suspected it. Now that I just reverted it, the sim seems to compile... yep 00.03.48 # so sim doesn't work or doesn't compile with my patch? 00.04.15 # doesn't compile 00.05.20 # ok I'll look at it later 00.08.11 # pixelma: did you tested recording with my patch? 00.11.57 # unfortunately not yet, I suffered the crash bug with my theme on the Ondio which was fixed today and which took quite some time testing. It's resolved now and I'll try your patch next, now that my test target is working a bit better again :) 00.11.58 Quit Luca_S (Quit: CGI:IRC (EOF)) 00.12.14 Quit simonrvn (Read error: Connection reset by peer) 00.12.33 Quit hebz0rl (Quit: Leaving) 00.15.48 Quit robin0800 (Remote host closed the connection) 00.17.30 Join earcar [0] (~carmine@93-39-245-25.ip78.fastwebnet.it) 00.17.55 Quit earcar (Client Quit) 00.22.53 # pamaury: comment added 00.24.59 # wodz: it fixes plugin loading on portalplayer (and possibly other SoCs with similar caching behaviour, not sure if we have any) for plugins that have bss variables with no-cache attribute 00.25.20 # Whether or not that maps exactly to greylib plugins, I don't know :) 00.26.23 Quit Rob2223 (Read error: Connection reset by peer) 00.26.29 # gevaerts: the Player's default WPS doesn't seem to have a progressbar. I'm preparing screenshots (from sims) to show what I mean - the Player's %pb is broken too for that matter 00.26.59 Join Rob2222 [0] (~Miranda@pD9FE3DCC.dip.t-dialin.net) 00.27.22 # that one can be shown with the shipped progressive.wps - or better by the gap in the middle of the second line which shouldn't be a gap actually... 00.28.39 Quit wodz (Quit: Leaving) 00.31.57 # pixelma: ok, I see progressive.wps behaving differently in a current sim than in 3.6 00.33.22 # so you don't need the screenshots anymore? 00.33.38 # probably not 00.33.44 # guess I'll post them anyway 00.36.22 Join Rob2223 [0] (~Miranda@pD9FE3DCC.dip.t-dialin.net) 00.37.06 Quit BHSPitMonkey (Quit: Ex-Chat) 00.39.18 Quit Rob2222 (Ping timeout: 240 seconds) 00.41.05 Join stripwax__ [0] (~Miranda@87-194-34-169.bethere.co.uk) 00.42.16 Quit stripwax (Ping timeout: 245 seconds) 00.44.07 Join simonrvn [0] (simon@209.249-ppp.3menatwork.com) 00.45.12 Quit Staphylo (Quit: Bye les gens =)) 00.49.41 Quit Judas_PhD (Quit: This is a quitting message) 00.50.56 Join Judas_PhD [0] (~kevin@misterfluffy.dsl.xmission.com) 00.56.02 Quit ender` (Quit: Only thing made by Apple that wouldn't suck would be an iVacuum.) 00.58.27 Join JdGordon| [0] (~jonno@vl10.gw.ok-labs.com) 00.58.27 Quit JdGordon| (Changing host) 00.58.27 Join JdGordon| [0] (~jonno@rockbox/developer/JdGordon) 00.59.05 Join krabador [0] (~krabador@host107-179-dynamic.3-87-r.retail.telecomitalia.it) 01.04.25 *** Saving seen data "./dancer.seen" 01.12.26 # JdGordon: can't seem to get the subline patch to apply (it's complaining about unexpected end again) 01.14.02 Quit Judas_PhD (Quit: This is a quitting message) 01.14.26 # meh bugger 01.15.23 # New commit by 03kugel (r28239): Two new lcd/multi screen api convinience functions: draw_viewport(), fill_viewport(). ... 01.17.18 # r28239 build result: All green 01.20.47 # kugel: draw_viewport() just draws a viewport border? 01.23.31 Quit JdGordon (Ping timeout: 245 seconds) 01.24.48 Quit pamaury (Remote host closed the connection) 01.25.37 # JdGordon|: yes 01.25.59 # can you rename it to "draw_viewport_border()" then please? 01.26.13 # no, why? 01.26.22 # it matches with drawrect() 01.26.22 # otherwise it could eazsily be confused with update_viewport() 01.26.37 # drawrect is obvious what it does 01.26.54 # draw_viewport_rect would even be fine 01.27.02 Quit stripwax__ (Read error: Connection reset by peer) 01.32.49 # I'm not sure how that makes it less ambigious but well 01.33.57 # without looking at the code how is anyone supposed to know what draw_viewport actually does? 01.34.11 # at least draw_vp_rect (or whatever) gives a tiny bit of indication 01.34.27 # if you say so 01.34.47 # I wouldnt have asked if I thought otherwise 01.35.08 # New commit by 03kugel (r28240): Add _rect to {draw,fill}_viewport as suggested by Jonathan Gordon to reduce the chance to confuse it with update_viewport(). 01.35.17 # JdGordon|: http://pastebin.com/8NSvwE2T seems to fix the Player progressbar issues 01.35.26 # kugel: thanks 01.35.29 Join Llorean [0] (~DarkkOne@rockbox/user/Llorean) 01.36.24 # gevaerts: I'll take your word for it :) why move those functions out of skin_display.c though? 01.36.47 # I'd prefer them go back 01.37.19 # r28240 build result: All green 01.37.43 # JdGordon|: because I needed them in skin_tokens.c. The thing is that these are a bit in between. They provide format strings (well, the fullbar() one does), *and* they set up the display to be able to render them 01.38.17 # now we could write a button widget it probably less than 10 lines 01.38.31 # The rest of the code seems to do either getting a string (skin_tokens.c) or drawing something (skin_display.c) 01.38.38 # it wont beat the awesomeness of thr yes/no buttons :D 01.38.56 # gevaerts: ok, fair enough 01.39.28 # pixelma: When a patch complains about ending unexpectedly, it usually just means whatever it was posted to mangled it by removing the newline at the end. 01.39.31 # JdGordon|: I can move them back, but I don't really see how I can move calling them out of skin_tokens 01.40.30 # Well, for %pb that might be doable, but for %pf it would be a mess I think 01.40.40 # ok, fine by me 01.40.47 # ok. Shall I commit? 01.40.55 # sure 01.43.56 Quit krabador (Ping timeout: 255 seconds) 01.46.23 # New commit by 03gevaerts (r28241): Fix charcell %pb and %pf tags, FS#11592 ... 01.48.15 # r28241 build result: All green 01.48.54 Join smtc96 [0] (smtc96@c-75-66-92-133.hsd1.tn.comcast.net) 02.05.38 Quit Bagder (Ping timeout: 276 seconds) 02.08.16 Join Bagder [0] (~daniel@rockbox/developer/bagder) 02.08.18 # kugel: stokv tagcache building the db 02.16.14 # JdGordon|: fix it :) 02.16.33 # the db scans the whole file system which is overkill in raaa 02.16.57 # we shuold use sql for tagcache on raa 02.16.59 # raaaa 02.18.30 # lets use a non-transactional database 02.18.35 # for better scalability 02.18.36 Quit Gabe_G23 (Ping timeout: 255 seconds) 02.18.54 # kugel: Are you sure about your implementation of those functions when the vp parameter is not null? Won't the lcd drivers be drawing in the current viewport, which may not be the full screen? Your original commit also seems to have some unrelated changes. 02.19.29 Join anewuser [0] (kvirc@unaffiliated/anewuser) 02.21.12 Join Gabe_G23 [0] (~gabe@bzflag/player/GabrielG) 02.21.35 # it'll draw the passed viewport, relative to the current_vp. is that wrong? every drawing is relative to current_vp 02.21.59 # You mean a viewport within a viewport? 02.22.41 # do you think it should be absolute? 02.23.03 # I thought viewports were always absolute. But maybe I've missed something in the last few months... 02.23.22 # draw_viewport_rect is equivalent to drawrect(0, 0, vp.width, vp.width) 02.23.39 # it could also be that I missed something 02.24.03 # AFAICS, you are only passing NULL to those functions at the moment? 02.24.17 # yea 02.25.28 # JdGordon|: there's also update_viewport_rect() btw 02.25.57 # linuxstb: there's no other drawing func which takes a viewport so I guess there's no convention yet 02.26.02 # which is what? update a rectangle inside the viewport? 02.26.32 # dunno 02.27.01 # kugel: Well, lcd_set_viewport() is an lcd driver function which takes a viewport parameter. 02.27.15 # that's no drawing function 02.28.32 Quit Gabe_G23 (Ping timeout: 245 seconds) 02.30.52 # Yes, I know. So what are you planning? To add more functions which take relative viewports? Your function also isn't taking account of the other values in the viewport, such as colours. 02.34.36 Join Gabe_G23 [0] (~gabe@bzflag/player/GabrielG) 02.34.46 # I'm not planning anything 02.35.42 # Do you actually need the case where vp != NULL? 02.36.05 # not yet 02.36.25 # Then I would say remove it - don't code things you don't need. 02.36.56 # that'd be consistent with clear_viewport 02.37.16 # although in the past I sometimes wished clear_viewport() would take a viewport 02.40.44 # As a relative or absolute viewport? 02.45.04 # I don't know anymore, but probably absolute 02.46.35 Quit Gabe_G23 (Quit: Server lost the game. :() 02.47.36 Join Gabe_G23 [0] (~gabe@bzflag/player/GabrielG) 02.47.50 # without the viewport parameter the _rect looks strange now 02.47.54 # kugel: I also think more thought needs to go into the names - "display->fillrect(0, 0, button_width - 1, vp.height);" is self-explanatory when you read it, but "fillrect_viewport(NULL)" isn't IMO - it's not comparable to fillrect. Your original lcd_fill_viewport was better in that case... 02.48.36 # ? 02.48.46 # maybe lcd_drawborder_viewport for the other? 02.49.11 # kugel: I was saying that due to the badly named functions, the code was easier to read before your commit. 02.49.40 # in my initial commit it didn't have the _rect (which is why I just said it looks strange now) 02.49.59 # it was fill_viewport(NULL) originally 02.51.04 # * JdGordon| didnt have a problem with fill_viewport, draw_viewport() on the otherhand was misleading 02.51.33 # kugel: Yes, I'm agreeing with you - our messages crossed (i.e. I hadn't read your line before writing mine) 02.51.57 # To be clear, my suggestion would be lcd_fill_viewport() and lcd_drawborder_viewport(). 02.52.57 # maybe lcd_fillrect_viewport() and lcd_drawrect_viewport()? 02.53.34 # * kugel would like fill_viewport and draw_viewport only but I must be the only one who doesn't see it's any more or less confusing with update_viewport() 02.54.06 # kugel: if /sdcard/rockbox/wps/ exists at all the inbuilt cabbie.wps wont work right? 02.54.15 # yes 02.54.19 Part smtc96 02.54.19 # bugger :p 02.54.34 # kugel: I think we're all agreed on lcd_fill_viewport() unless I'm misunderstanding. 02.55.06 # I think both should have a consistent name 02.55.32 Quit leavittx_ (Ping timeout: 264 seconds) 02.55.37 # consistent with each other and consistent with drawrect() and fillrect() 02.56.13 # * kugel hates that some of the older functions have no underscore between the words 02.57.13 # haha crap! dont enter the font browser in absolute mode! 02.57.14 # kugel: I understand your argument. But I also think that lcd_draw_viewport() doesn't describe what it does very well - i.e. draw a border inside the viewport. 02.57.16 # you cant get out! 02.59.50 # drawrect isn't better in that regard 03.00.17 # although I personally don't see what's wrong it, I'm not confused 03.00.42 # don't take this the wrong way, but of course you dont see the problem.. you implemeneted it 03.01.09 # and yes, the lcd funcitons are all rather messily named 03.03.48 # I think draw perfectly describes what it does (especially when I translate it into my language), I connect it with drawing lines on a paper 03.04.29 *** Saving seen data "./dancer.seen" 03.04.45 # but well, I can see your point as well. drawborder_viewport then? 03.07.08 # that would be ok 03.07.27 Join dalinkwent [0] (~423d6c5c@giant.haxx.se) 03.07.30 # I sort of wonder why this is so far down though 03.07.31 # Thinking about it some more, should they even have "viewport" in the name? The other LCD drawing functions don't. 03.09.33 # the text ones you mean? 03.10.08 # ack: hey all, was looking for info on psgroove for the fuzev2 earlier and saw some comments saying you guys were looking for testers? 03.10.31 # not psgroove... 03.11.04 # kugel: I mean all lcd functions, apart from the four that deal with setting/clearing/updating a viewport. 03.11.12 # well i think the guys working on psgroove are maybe building off your recent work with usb in rockbox? 03.11.23 Join BHSPitMonkey [0] (~stephen@unaffiliated/bhspitmonkey) 03.11.26 # IMO clear_viewport is a drawing function 03.11.53 # you can implemented it with set_foreground and fill_viewport calls 03.12.27 # set_drawmode, not set_foreground 03.12.57 # i have a fuzev2 with version r8228-101010 and if anyone needs anything tested im here to help out 03.13.06 # sorry if im interrupting 03.16.27 # "testing" is basically using the most current build available, and reporting bugs, if any. 03.16.41 # so, you're doing it just by using the device and keeping in touch. 03.17.03 # dalinkwent: ^ 03.18.04 # kugel: Yes, but the only one. That could be "lcd-clear()". But anyway, I don't want to argue all night about names... 03.18.26 # thanks :) 03.19.57 # New commit by 03kugel (r28242): Rename {draw,fill}_viewport once more (to draw_border_viewport and fill_viewport) and remove the viewport parameter as suggested by Dave Chapman. ... 03.20.08 # well i updated today with rockbox util, and i dont know if its exclusive to the newest build (havent updated in a while) but my fuze will now stay in rockbox when connected with usb, and it also shows that its charging in rockbox now 03.20.41 # dalinkwent: did you select current or release build? 03.20.53 # kugel: draw_viewport_border would be better english :) 03.20.57 # current I'm thinking...and yerah, USB was implemented a while back now. 03.21.10 # yea i used current build 03.21.42 # which means im probably using an older version than whats being worked on? 03.21.57 # nobody is working on psgroove for fuzev2 03.22.12 # considering there's 10-to-50 commits per day, yes. 03.22.16 # but not by much. 03.22.20 # r28242 build result: 148 errors, 26 warnings (kugel committed) 03.23.42 # New commit by 03kugel (r28243): Forgot to update lcd-remote.h 03.24.12 # Originally Posted by sk8r8sht View Post Over at rockbox this morning Ive noticed that they seem to have maybe found a workaround for the fuze v2 usb. This might be what alot of people are looking for. They currently need testers if anyone is interested, to get the ball rolling. 03.24.28 # thats basically the post that pointed me here 03.24.33 # this is obviously over my head 03.24.38 # just wanted to see if i could lend a hand 03.25.47 # r28243 build result: All green 03.27.03 # you can test http://www.rockbox.org/tracker/task/11664 but it has nothing to do with psgroove 03.28.54 Quit kugel (Remote host closed the connection) 03.35.57 Quit dalinkwent (Quit: CGI:IRC) 03.36.13 Join webguest41 [0] (~423d6c5c@giant.haxx.se) 03.37.41 # hmmmmm, slightly freaking out, but not really...does rockboxdev.sh automatically build arm-eabi for arm toolchain now? 03.37.50 # just realised I typed a instead of e 03.38.08 # and that e is no longer an option. 03.38.25 # I woudl say.. probably... 03.38.59 # that's what I thought, but it's *almost* complete...so I'd be pissed if I was wrong ;) 03.39.56 # hmm, we cant draw a plain rectangle in the skins currently can we? 03.40.09 Quit webguest41 (Client Quit) 03.40.14 # depends how you mean. 03.40.15 # a filled in rectangle I mean 03.40.28 # errr...not that I know of. 03.40.54 # I might need to add access to fillrect and drawrect 03.41.16 # I want a light border behind my AA but apparently cant do that without loading an image 03.41.36 # yeah...you'll need to load an image. 03.41.42 # It'll hardly cost a lot. 03.42.06 # that isnt the point 03.42.11 # I shouldnt need to :p 03.42.15 # who wrote this crap anyway?! 03.42.33 # If everyone else needs to, you do tyoo! 03.42.44 # on contraire 03.42.47 # oh* 03.43.13 Quit BHSPitMonkey (Remote host closed the connection) 03.43.13 # %d is unused right? 03.43.19 # pfffft! typical dev having his cake and eating it too, in front of the starving users ;) 03.43.57 # %dr(x,y,w,h,filled,[colour]) draw rect, optionally filled and coloured 03.44.23 # * S_a_i_n_t squints for something to complain about in there. 03.44.28 # haha 03.44.33 # you dont have to complain... :p 03.44.33 # gimme some time, I'll find it eventually. 03.44.50 # I don't *have* to ;) 03.45.00 Quit z35 (Quit: Leaving) 03.45.20 # ahem... %dr(x,y,w,h, filled?, start colour, end colour) 03.45.23 # graident fill ftw 03.45.47 # is there a gradient thingo? 03.45.56 # ah...yeah, the line selector can do it. 03.46.08 # Hmmm...nice. 03.46.11 # yeah, dunno how it works, but if it can do it there i should be able t use it 03.46.33 # (famous last words) 03.48.16 # ahem... %dr(x,y,w,h, filled?, start colour, end colour, ) 03.48.43 # maybe not :p 03.48.49 Join BHSPitMonkey [0] (~stephen@unaffiliated/bhspitmonkey) 03.49.15 # no, it'd be better (though I can't believe I'm saying this...really) to kludge that into the bar's line, not the other way around. 03.49.43 # so the bar gets and additional: filled? how? param. 03.49.54 # yeah, probably 03.49.59 # although it already has enough params 03.50.05 # though, it's not like the bars need any more optional params ;) 03.50.10 # hahah...snap. 03.50.34 # although I dont think it is unusable with all of them 03.56.39 # JdGordon|: can't you just make a viewport with a background colour? 03.56.52 # Also, more features right before a release? Really? 03.57.07 # no, because the stupid backdrop image gets in the way 03.57.19 # and no, this is a bug 03.57.22 # :) 03.57.36 # Aren't viewports with background colours drawn on top of the backdrop? 03.57.41 # how do you mean "backdrop image gets in the way"? 03.57.50 # what rasher said should indeed be possible. 03.57.56 # As an opaque rectangle, that is. 03.57.58 # I feel stupid for not thinking about it. 03.57.59 # the background colour is actually ignored by the lcd code 03.58.07 # Well *that* sounds like a bug to me 03.58.14 # Indeed. 03.58.14 # Adding a new tag, however, is certainly not 03.58.40 # It should "just work" adding a viewport behind the AA with a BG colour. 03.58.53 # the fact that it doesn't is the simpler fix here, and the real "bug" 03.59.03 # * JdGordon| isnt so sure 03.59.15 # * S_a_i_n_t is, if it doesn't work...it's broken. 03.59.17 # I could make %Vb() do that, but that could break peoples themes 03.59.18 # it used to. 03.59.36 # no, the background colour never affected anything if a backgorund image was loaded 03.59.47 # *shouldn't* %Vb() do that? 03.59.55 # isn't that what it's for? 03.59.55 Quit Rob2223 (Quit: Rob2223) 04.00.04 # well, sort of 04.00.16 Join Rob2222 [0] (~Miranda@pD9FE3DCC.dip.t-dialin.net) 04.00.19 # Does it get ignored if there's a backdrop? 04.00.24 # it sets the viewport backdrop colour, the lcd driver is the actual problem here 04.00.25 # if so, that's pretty silly. 04.01.00 # Ah, right...well, I see fixing %Vb() as the "real" issue here, personally. 04.01.12 # It will allow you to do what you want with no additions. 04.01.41 # gradient fill would still be nice (although easily added to Vb) 04.01.45 # and no "pre-release-sneaking" that'll almost certainly cause a shitstorm. 04.01.55 # Ah, yes, it would be nice. 04.01.57 # being able to draw a empty rectangle has been something I've wanted for a while also 04.02.07 # but a working %Vb() would be nice too. 04.05.12 # If you set a background colour for a viewport, it should be filled with that colour 04.05.48 # it has never worked that way though if a bg image was loaded 04.05.58 # so yes, I agree 100%, it could break peoples skins 04.06.04 # although, its a dead simple fix 04.06.23 # Huh, I never really played with it...I always load images as I very rarely, or apparently never have had a need for this. 04.06.27 # Why would people be setting a background colour anyway, if it's never actually worked? 04.06.35 # but the way rasher and I think it should work seems very sane. 04.06.40 # because it used to be required in the %V line 04.06.51 # But it allowed -, didn't it? 04.06.51 # rasher: It works, butnot if there's a backdrop. 04.06.53 # I'm agreeing 04.06.55 # I do remember this now. 04.07.13 # * JdGordon| wants a dev env right now :p 04.07.35 # I don't see why it should matter if there's a backdrop or not 04.07.55 # It shouldn't, but that's the way I remember it. 04.08.14 # ah, hmm... I dont tihnk this will actually work 04.08.28 # clearing a line, and the scroll engine wont work 04.08.48 # ENOTSOTRIVIAL 04.09.03 # I'm not arguing how it works now, just how I think it should work 04.09.04 Quit ajb (Read error: Connection reset by peer) 04.09.09 # * S_a_i_n_t looked at the scroll engine, once... 04.10.10 Quit amiconn (Disconnected by services) 04.10.11 Join amiconn_ [0] (quassel@rockbox/developer/amiconn) 04.10.29 Nick amiconn_ is now known as amiconn (quassel@rockbox/developer/amiconn) 04.10.49 Quit pixelma (Disconnected by services) 04.10.51 Join pixelma_ [0] (quassel@rockbox/staff/pixelma) 04.10.53 Nick pixelma_ is now known as pixelma (quassel@rockbox/staff/pixelma) 04.12.12 # yeah, the lcd driver needs work for this to be fixed properly 04.13.22 Quit TheSeven (Ping timeout: 265 seconds) 04.13.24 Join DerPapst1 [0] (~Alexander@p5797CFF2.dip.t-dialin.net) 04.13.37 # What's the actual issue with the LCD driver? 04.14.08 # it ignores the viewport bg_pattern if an image is loaded 04.14.22 # Maybe have something like a "show_backdrop" flag in the viewport struct? 04.14.30 Quit DerPapst1 (Client Quit) 04.14.33 # Or rather, if a backdrop is loaded, all viewports will use it. 04.14.34 # so everything that draws transparenrlty, or clears will show the wrong thing 04.14.58 # linuxstb: the latter is what is happening now 04.14.59 Quit DerPapst (Ping timeout: 265 seconds) 04.15.09 # Hmmm, if this *is* fixed, would it not allow loading a backdrop for each individual viewport? 04.15.14 # that could be kinda cool. 04.15.18 # it wouldnt 04.15.33 # bah, oh well...dreams are free. 04.15.34 # seperate issue, and annoyingly a moslty nodo 04.16.03 # JdGordon|: Yes, I know - I was just describing the current situation a different way. 04.16.10 # it's not the loading that's the issue though is it, it's where it's stored. Correct? 04.16.29 # (re: multiple BGs) 04.16.52 # Dynamic skin buffer FTW 04.17.09 Join TheSeven [0] (~TheSeven@rockbox/developer/TheSeven) 04.18.05 # multiple bg's are difficult because the way the correct pixel is got to is very simple math, having seperate images means slightly more complex math being called very very often 04.18.26 # Ah. 04.18.44 # it could be done, but I tihnk there is actually opposition to it 04.19.02 # adding a flag to make the vp ignore the bg image should be doable though 04.19.12 # As there is for most of the cool things that *could* (in theory) be done with the skin engine. 04.27.10 Join Chronon [0] (~Chronon@c-67-171-217-43.hsd1.or.comcast.net) 04.27.12 # Just because it can be done doesn't make it a good idea 04.27.55 # I disagree (both with that statement in general, and in using it with this idea) 04.28.25 # JdGordon|: You're saying that there are no bad ideas? 04.29.16 # discussion on that doesnt belong here :) 04.30.05 # Correction then: "You're saying there are no bad ideas for Rockbox changes?" 04.34.36 Quit S_a_i_n_t (Quit: I'm only going to Heaven if it tastes like caramel...) 04.34.50 Join Judas_PhD [0] (~kevin@misterfluffy.dsl.xmission.com) 04.34.51 # JdGordon|: So you're saying there's no reason we shouldn't include anything someone can think of? 04.35.03 Join S_a_i_n_t [0] (S_a_i_n_t@203.184.2.235) 04.37.13 Quit MethoS- (Remote host closed the connection) 04.39.47 # I didnt say that at all 04.41.40 # and anyone that has ever read irc or the ml knows I do entertain new ideas more freely than (apparently) lots of other people (not saying that is good or bad) 04.42.07 # * linuxstb doesn't know what we're arguing about 04.42.07 # * S_a_i_n_t personally has seen many of his "wild ideas" come to fruition. 04.43.21 # In fact, "next AA" is the only thing on my list that JdGordon| hasn't checked off...and every single one of those was "na, I don't think so" at some point. 04.46.00 # I'm just saying that there may be very valid reasons to reject an idea. 04.46.19 # Disagreeing with that seems to mean "every idea should be implemented", basically. 04.46.26 # anyone want to test viewport backgrounds on a grey target with a wps that does set %X? 04.46.43 # * JdGordon| is curious as to what happens there 04.46.59 # it doesn't mean every odea should be implemented, but, it should be considered without a closed mind. 04.47.06 # I had to really push for some of my ideas. 04.47.12 # *idea 04.47.14 # I didn't say that. 04.47.51 # adding the "basically" made it different? 04.49.19 # I have no idea what you and JdGordon| are saying. 04.50.02 Join dys` [0] (~andreas@krlh-5f72e5ae.pool.mediaWays.net) 04.50.58 # all I'm saying is no idea should be rejected outright with little more than a sentence explaining it 04.51.03 # Well, I'm saying personally that everything should be considered. Instead of immediately dismissing something as "a stupid idea" if it initially seems so. 04.51.31 Join Barahir [0] (~jonathan@frnk-590f492e.pool.mediaWays.net) 04.51.31 # I'm sure there's been plenty of past "stupid ideas" that are now parts of RB 04.52.35 # Who the hell said anything about outright rejecting ideas 04.53.17 Quit dys (Ping timeout: 276 seconds) 04.53.22 # calm down... thats how I interpretted " Just because it can be done doesn't make it a good idea" 04.54.07 # I'm perfectly calm, just incredulous as to why you're arguing a point no one made 04.54.48 Quit Barahir_ (Ping timeout: 250 seconds) 04.56.53 # I think we are both misinterpretting eachother... so lets drop it :) 05.03.37 # * JdGordon| adds a bug for the viewport ignoreing bgcolour 05.04.30 *** Saving seen data "./dancer.seen" 05.18.41 Quit anewuser () 05.19.06 Quit Chronon (Ping timeout: 265 seconds) 05.34.53 Quit ps-auxw (Ping timeout: 276 seconds) 05.40.29 Quit edboyer93 () 05.45.34 Join ps-auxw [0] (~arneb@p4FF7EB84.dip.t-dialin.net) 05.53.58 Join Nausicaa [0] (~Nausicaa@c-71-239-58-153.hsd1.il.comcast.net) 06.08.35 # pixelma: amiconn: any other CygWin users...ping? 06.09.57 # not at 5am I would bet :p 06.10.04 # Who feels like being a dear and either packagine the arm-eabi toolchain for me, or opening an FTP so I can steal it from them? 06.10.23 # hence the "any other CygWin users" bit ;) 06.10.40 # and, I *have* seen amiconn here at some odd times. 06.11.14 # remind me when I get home and I might be able to help... 06.11.28 # although you actual upload wont be able to happen till tomorow when I'm at work again 06.11.50 # you have a CygWin env? 06.12.11 # no, but I can set one up easily enough... 06.12.21 # you'd think. 06.12.31 # I seem to be failing at it. 06.12.35 # well, comp is fast enough to not worry about building toolchains :) 06.12.51 # the package manager has changed, and it was always VERY vague what was needed to make eabi 06.13.15 # I bluffed it last time, there's many a package the wiki misses. 06.13.29 # I should have fucking updated it while I knew them all. 06.14.18 # I have my doubts that it failed solely due to a failed rm action 06.14.35 # libiconv was playing some asshole games with me the last I rememebr 06.21.59 # anyone got a radio target? is .rockbox/wps/rockbox_failsafe.fms created? 06.36.10 Quit panni_ (Quit: ( www.nnscript.de :: NoNameScript 3.81 :: www.XLhost.de )) 07.03.03 Quit Judas_PhD (Quit: This is a quitting message) 07.04.32 *** Saving seen data "./dancer.seen" 07.06.02 # Hmmm...is http://www.rockbox.org/tracker/task/11663 going to mess up booting the latest build with the older bootloader? 07.06.12 # I trust a new bootloader will be released? 07.07.31 # I'm thinking it may mess things up because it touches more than the bootloader, the clickwheel driver is modified also and I'm not sure if it is backward compatible or not. 07.14.50 # is anyone aware what the issues http://svn.rockbox.org/viewvc.cgi?view=rev;revision=28164 introduced were? (the reason it was reverted) 07.15.22 # I' going over past commits, and this one isn't very well commented. 07.16.29 # I do know that the annoying hum that the LCD makes on Nano2G is bloody annoying, and it does diminish if the voltage is decreased...I never saw any issues with the screen in my own trials. 07.17.34 # With the current voltage playing rockboy for 1-to-2 hours + makes the LCD make a horrible "I'm going to die soon" crackling noise, seems to happen when the CPU is boosted for long periods. 07.20.09 Join feisar- [0] (jljhook@sienikerho.com) 07.34.38 # * S_a_i_n_t needs theme testers for iPod Video, any takers? 07.35.25 Join G4Oblivion [0] (~chatzilla@user-0c6sbe1.cable.mindspring.com) 07.36.36 # G4Oblivion: Any more luck debugging that annoying panic on Nano2G? 07.36.47 # S_a_i_n_t: The reason the commit was reverted was because a user in forums said that his nanos screen would flicker and go blank. I'm unsure if they confirmed that it was a ILI9320 LCD type problem. 07.37.15 # I deleted my config and am using the Rockbox default right now. I have not had any problems since. 07.37.36 # G4Oblivion; Ah, I see...I saw that the commit was re-commited again later, so I guess it wasn't confirmed. 07.38.01 # have you tried skipping *really* fast in the WPS? 07.38.09 # Yes. 07.38.10 # I find skipping backward seems to do it for me. 07.38.29 # It does it skipping forward also, but backward seems to do it a lot quicker. 07.39.10 # It seems to be an issue with buffering, I haven't tried reverting my config file however, I'll do that now and see if I still get the problem. 07.40.38 # G4Oblivion: Are you able to test a theme on your Nano2G for me? 07.40.58 # Sure. Just tell me what to look for. 07.43.15 # I'm basically just lookinf for any visual flaws (if any), but it would also be nice if you could test if fallbacks for cases without metadata are handled correctly. 07.43.26 # And, anything you feel could be improved. 07.43.36 # file is here: http://www.datafilehost.com/download-52cb509b.html 07.43.46 # Will do. 07.44.37 # And, after testing it'd be good if you could PM me a real name so I can add you to the credits. 07.45.45 # Ok. Just to make sure metadata is track info right? anything else metadata related? 07.47.06 # well, it *should* be displaying folder level 3 for album, and folder level 2 for artist. It assumes a sane folder layout. ie: Music - Artist - Album 07.47.17 # Just wanting to make sure that's working correctly. 07.48.03 # if it can't display those, it will display bitrate and samplerate IIRC 07.48.43 # but, if you have the correct metadata present, it should just display that. 07.49.48 # I also want to check if the "next track" queues are displaying correctly as I was having trouble with that on my units here. You should get a "Next Track" prompt display Artist and Album 15 seconds from the end of the current track. 07.51.45 # Still testing but, isn't the scrollbar color a bit dark if its supposed to look like OF? 07.53.13 # Hmm...Is song named supposed to be fixed to the right side instead of the middle like artist and album 07.53.40 # No, I guess it isn't. 07.53.56 # by scrollbar, do you mean the list scrollbar? 07.54.09 # Yes. 07.54.19 # I can't really do anything about that until there's bitmap scrollbars available. 07.54.31 # the theme.cfg should disable scrollbar. 07.55.08 Quit Nausicaa (Ping timeout: 245 seconds) 07.55.54 # Ok. On long track names it displays the name correctly. On short track names that don't need to scroll is has it fixed to the right side of the screen instead of the center. 07.56.02 # Hmmm, looking at the code, that alignment issue shouldn;t be happening. 07.56.10 # that's odd. thanks for the headsup. 07.56.40 # Is this with or without AA? 07.56.47 # (album art) 07.56.58 # Without. 07.57.10 # I don't have any album art tracks to test =/ 07.57.15 # very weird. 07.57.27 # and, that's fine..AA isn;t necessary. 07.58.19 # Next track appeared at -0:08 instead of -0:15 07.58.20 # out of curiousity, is the language on the player left to right (as in english) or right to left? 07.58.33 # left to right 07.58.50 # Ok, that's fine...at least it's popping up. I assume you have crossfade set? 07.59.06 # Only if its on by default. 07.59.20 # crossfade seems to mess with the %pE/%pS settings 07.59.30 # it does? 07.59.37 # yeah. 07.59.51 # fun :p 08.00.02 # G4Oblivion: Oh, sorry...it should be appearing at -10, not -15. My mistake 08.00.14 # but either way -8 is wrong ;) 08.00.34 # the alignment issue is a fun one...the code doesn't give me any clues why that is happening. 08.00.36 # Just tested again. It appeared at -0:10 correctly. 08.00.43 # yay! 08.03.20 # Ok, I just fixed the alignment issue...stupid typo/forgot to remove old code. 08.03.38 # Everything seems to be working with normal use. 08.03.52 # G4Oblivion: Could you check if the titlebar is displaying charging status correctly please? 08.04.16 # I have had problems with that here, and my dev environment is down at the moment so I can 08.04.28 Quit BHSPitMonkey (Ping timeout: 264 seconds) 08.04.28 # 't test on a new enough build. 08.04.51 # The build on my iPods is about a month old. 08.05.05 # I've never tried charging through rockbox. Do I need to turn on charging and plug it in? 08.05.10 # you can download from the interwebs! 08.05.33 # not with all my patches I can't ;) 08.05.51 # RB seems terrible to me without the setup I like. (no offence) 08.06.19 # G4Oblivion: Charging *should* be anabled by default. 08.06.30 # i dont tihnk it is actually... 08.06.39 # You might need to set it to "force" depending on the port you're charging through. 08.06.42 # uh, it will connect but only at 100mA i think 08.07.03 # Ah, "force" tells it its safe to grab 500 at all times. 08.07.05 # Is there a way to exit usb mode without hard reset? 08.07.15 # But you need to know it actually *is* safe to do so. 08.07.27 # unplug USB 08.08.00 # If you unplug USB and it stays on the USB screen something is horribly wrong 08.08.03 # I did still on USB screen. My computed didn't recognize it when I plugged it in either. 08.08.37 # that's usual for the Nano2g, did it just not enumerate? or did it fail to mount completely? 08.08.46 # USB HID is fucked for the Nano2G 08.09.21 # I mean, it certainly is not normal for it to stay on the USB screen if no USB is present. 08.09.22 # After reboot its working. Is it because I had a song going when I pluged it in? 08.09.26 # that's definitely a bug. 08.09.35 # It shouldn;t be. 08.09.52 # USB was still plugged into iPod but not computer. I may be at fault. 08.09.53 # It should have just stopped playback. 08.10.10 # You can also hold Menu to charge and continue use/playback 08.10.44 # that still seems wrong, plugging USB in, but not having it plugged to the PC should do nothing. 08.10.55 Join Na|L [0] (~NaiL@cigan.ynet.sk) 08.11.05 Quit JdGordon| (Quit: leaving) 08.11.05 # I see "Charging" "Current Time" and a flashing charging battery symbol. 08.11.09 # it should only know a cable is there when it detects power. 08.11.23 # yep, cool...that works then. 08.11.37 # it should switch to "Charged" when the battery is full. 08.11.39 # awesome. 08.12.00 # Mines almost dead =P 08.12.23 # Asides from obvious differences, you think I've got the look pretty close? 08.12.44 # The aim is (eventually) to not be able to tell whether it is the OF or RB 08.12.53 # hello, anybody iriver h3xx positive? simple question about restart while charging 08.12.57 # I haven't used OF in months but it seems to be pretty close. 08.13.17 # only thing left is the scrollbar, and that's not possible at present...when bitmap scrollbars can be done it should be pretty much perfect. 08.13.41 # Na|L: It's best to just ask your question. 08.13.46 # ok 08.14.03 Join n1s [0] (~n1s@nl118-174-240.student.uu.se) 08.14.10 Quit n1s (Changing host) 08.14.10 Join n1s [0] (~n1s@rockbox/developer/n1s) 08.14.34 # Text is a bit choppy. A smoother text would be nice. I'll boot into OF ad look at the differences. I can't test the OF WPS though, I have my music in my own folder not iTunes. 08.14.44 # and* 08.15.55 # yeah, I can't really do anything about the text unfortunately. that's as close as I can get it until/or if there is ever, aliased fonts in core. 08.16.18 # i put usb cable in wrong hole and result is: some smoke and player stay in "charging state" even if not, so i cant restart/poweroff player, my question is, bloking poweroff is made by SW or it's HW block? 08.16.25 # I don;t quite have the motivation to do a custom build with aliased fonts enabled just for this, maybe one day. 08.17.58 # Na|L: Sounds like you blew something up dude..as I understand it the power is detected by hardware and controlled by software 08.18.30 # basically, it is recieving incorrect info now, and thinks its always charging. 08.18.40 Join JdGord [0] (~jd@122.110.104.79) 08.19.22 # You'll need to replace whatever it is you blew up, and with a bit of luck it should return to normal function. 08.19.56 # i know i blew something probably lx2201 ... 08.20.24 # How did you manage to put the charging cable in the wrong socket? 08.21.05 # I thought they were different sizes so you specifically couldn;t do that...been a long time since I've seen an h3xx though. 08.21.17 # that was standard cable, i put it in media socket lot of time, no problem, but one day .... :) 08.21.41 # media socket? 08.21.48 # yo 08.22.11 # I'm asking, what is a "media socket"? 08.22.28 # i try make some modification to source to set state or charging permanently to "discharge" but withou luck :/ 08.22.35 # All the repeat and shuffle icons seem to appear correctly. Seems the OF has small spaces before the text on the home screen (i.e Music, Photos, Extras.) 08.23.01 # aaaaa, when player act as usb host, for downloading photos from digital camera etc 08.23.07 # Is it possible to add blank icons or something? 08.23.32 # G4Oblivion: Good idea. 08.23.45 # I hadn't thought of that actually, nice one ;) 08.24.28 # Oh, actually...I tell a lie. 08.24.50 # I have tried that and it looked weird because the line selector didn't go to the left edge. 08.25.05 # That's another thing I can only fix with a custom build. 08.25.23 # I'd need to add a space to the beginning of each menu entry. 08.25.57 # ie. so it was " Settings" as opposed to "Settings" in the .lang file 08.27.08 # Na|L: I was unaware that you were able to charge the device through the devices host USB socket. 08.27.22 # Hmm. I can't think of anything else. 08.27.39 # Na|L: I guess it may not have had anything to do with what socket you plugged in, perhaps it was just the hardwares time to fail. 08.28.41 # G4Oblivion: Thanks. Can you PM me a real name (preferably yours ;)) so I can add you to the credits please? I appreciate you doing this for me. 08.29.16 # Sure. I just right click your name and select "Open Private Chat" right? I never us IRC clients. 08.29.35 # maybe, anyway thx. 08.33.06 # You can put a blank in with the list icons 08.34.13 # Na|L: Can you reboot the device? 08.34.47 # You should be able to hold "Menu(?)" and even if the player thinks it is charging you should be able to use it. 08.35.00 # Sort of.. maybe 08.35.00 # Especially if you sent using the largest icon size 08.35.00 # I think using 24*24 icons with appropriate transparency and centering will work with smaller line heights 08.35.47 # S_a_i_n_t: just by reset button(little hole), no by poweroff butten 08.36.03 # JdGord: The problem is I need the line selector to go from one edge to the other. 08.36.15 # with icons, or transparency it won;t do that. 08.36.36 # Ah. Yes 08.36.49 # Na|L: It is possible to use the player while charging by holding a button during charger connect. 08.37.11 Join antil33t [0] (~Mudkips@124-197-51-80.callplus.net.nz) 08.37.12 # In theory, you should be able to hold this button while it boots to get it to boot into RB properly. 08.37.34 Nick dys` is now known as dys (~andreas@krlh-5f72e5ae.pool.mediaWays.net) 08.37.41 Quit G4Oblivion (Quit: ChatZilla 0.9.86 [Pale Moon 3.6.9/20100913113105]) 08.38.02 # S_a_i_n_t, Na|L : afaik, the h300 bootloader always boots the OF if it thinks a charger is connected 08.38.56 # quite possibly, but it is possible to hold a button (different for each target) that allows you to use the player while it charges. 08.39.04 # player work ok, no problem, problem is just i cant poweroff it, or it never go to standby, so batteryfiletime is .... 08.39.34 # does it charge still? 08.39.38 # yes 08.39.39 # Na|L: well, that definitely sounds like hw failure 08.39.44 # it's 08.40.11 # n1s: Smoke coming from the player usually means HW fail, yes ;) 08.40.18 # indeed 08.40.27 # i just need knoe if it's posible do SW reboot/poweroff, even if HW thin it's on charger 08.40.47 # AFAIK, no. 08.40.48 # think 08.41.07 # it will always say "charging" and prevent poweroff. 08.41.15 # poweroff/reboot 08.41.16 # with luck, you might be able to hack the pcf driver to make it ignore whatever poweron signal it thinks it gets provided that it isn't one you actually need 08.42.00 # but then it will probably kill charging. 08.42.03 Quit JdGord (Quit: Bye) 08.42.06 # So you'd need a way to toggle it. 08.42.18 # at least i need restart option in menu or something like that 08.42.20 # i remember preglow once managed to mess up the pcf config on some player and that wouldn't boot at all then :) (rescued by disconnecting the battery IIRC) 08.43.02 # Na|L: if the pcf thinks a charger is connected it will start the player as soon as you poweroff 08.43.14 # Na|L: Even if you have a reboot/poweroff option in the menu rockbox won;t let you reboot/poweroff if it thinks the player is charging. 08.43.35 # there is a splash that warns about charging, and it won;t let you reboot or poweroff. 08.43.44 # that sux :/ origin firmware do that, no poweroff but restart ist posible :( 08.43.44 # you can use rolo to fake reboot 08.43.57 # rolo? 08.44.00 # Hmmm, true. 08.44.02 # why do you need to reboot anyway 08.44.07 # Rockbox Loader 08.44.22 # database update always want to reboot to "take efect" 08.44.29 # ah 08.44.56 # well, add a second Rockbox image to the disk, and "run" it from the filebrowser. 08.45.02 # that will "fake" a reboot. 08.45.20 # you don't need a second image, you can reboot the same one if you like 08.45.23 # :D 08.45.31 # Ah, good point. 08.46.15 # hmmm 08.47.26 Join leavittx_ [0] (~lev@89.221.199.187) 08.48.33 Quit n1s (Quit: Lämnar) 08.48.40 # thx!!!!!!!!!!!!!!!!! 08.48.42 # :)) 08.49.14 # No problem, good luck in replacing the hardware you blew. 08.49.34 # it works, i named it reboot.iriver :D 08.49.35 # it shouldn;t be too difficult if you have a heat gun or a very fine nibbed soldering iron. 08.50.38 # do it is no problem, i hack my openmoko, but buy that chip is problem, i wrote some emails, but no answare yet :/ 08.50.55 Join ender` [0] (krneki@foo.eternallybored.org) 08.55.14 Quit bluebrother (Disconnected by services) 08.55.15 Join bluebroth3r [0] (~dom@rockbox/developer/bluebrother) 08.57.35 Part Na|L 09.04.33 *** Saving seen data "./dancer.seen" 09.10.24 Join JdGordon [0] (~jonno@rockbox/developer/JdGordon) 09.10.29 Quit leavittx_ (Ping timeout: 264 seconds) 09.11.24 # amiconn: you know the lcd drivers right? 09.18.22 Join hebz0rl [0] (~hebz0rl@dslb-088-065-058-252.pools.arcor-ip.net) 09.18.47 Join p3tur [0] (d408b802@rockbox/developer/petur) 09.28.30 Join Zagor [0] (~bjst@giant.haxx.se) 09.28.30 Quit Zagor (Changing host) 09.28.30 Join Zagor [0] (~bjst@rockbox/developer/Zagor) 09.34.57 Part pSiKO 09.38.02 Join Rob2223 [0] (~Miranda@pD9FE25AE.dip.t-dialin.net) 09.41.45 Quit Rob2222 (Ping timeout: 276 seconds) 09.43.52 # Can an admin remove the link in http://forums.rockbox.org/index.php?topic=25890.msg172671#msg172671 please? 09.44.05 Quit JdGordon (Ping timeout: 264 seconds) 09.44.08 Join pSiKO [0] (~tbox@213.56.158.253) 09.44.15 # the theme is nowhere near as cleverly done as mine, and sues images pulled straight from the OF 09.44.22 # *uses 09.45.01 Join JdGordon [0] (~jonno@rockbox/developer/JdGordon) 09.45.33 # * S_a_i_n_t should put his theme for iPod Video up on the themesite to satisfy the needs of people that want an OF-ish theme 09.46.52 # ish? 09.47.22 # well..."A complete rip-off/duplicate/mockery of the OF theme" ;) 09.48.33 # does the sim use lcd-16bit.c or lcd-16bit-vert.c? 09.48.38 # Mine's way better, *and* I did it without using Apple graphics, though the almost might as well be as I certainly can't tell them apart anymore, there's a reason why I painstakingly recreated them as opposed to pulling them from the OF 09.52.35 Join swilde [0] (~wilde@aktaia.intevation.org) 09.54.49 Nick p3tur is now known as petur (d408b802@rockbox/developer/petur) 09.59.09 # http://imagebin.ca/view/ZS0NsYi.html any guesses which lcd functions I've missed? I'm trying to get no background image 09.59.28 Join sasquatch [0] (~username@p4FF2D376.dip.t-dialin.net) 10.03.04 Quit utanapischti (Ping timeout: 245 seconds) 10.03.19 # woops, some ||'s inmstead of &&'s :p 10.04.22 # the transparent images still no worky, buut the text is 10.04.24 # arg 10.06.17 # ok, that was easier than expected :) 10.06.34 Quit TheSeven (Ping timeout: 240 seconds) 10.06.57 # abckground colours work in viewports when there's a backdrop loaded now? 10.07.03 # *background 10.07.59 # not yet, one lcd driver is fixed so it works 10.08.12 # Aha. 10.11.11 # woo! butt ugly progressbar 10.11.29 # cabbie? ;) 10.11.31 # dinner then fix the other drivers 10.11.47 # cabbie with red pb in the unfilled area 10.13.33 Join earcar [0] (~carmine@93-39-245-25.ip78.fastwebnet.it) 10.17.11 # amiconn: I posted in #rockbox-community, but I suppose it's more relevant here as there's a chance someone else maysee it also and be able to help. Is there a possibility you might be able to put the CygWin arm-elf-eabi toolchain up somewhere I might be able to grab it please? I would really appreciate it if you could do so, being one of the only other people I know that use CygWin dev environment. 10.20.15 # I'm about 99% sure it isn't necessary to package it as a CygWin package, just pulling the directory structure out and compressing it (not sure it's really that big to begin with actually) would work just as well. 10.34.58 Join DerPapst [0] (~Alexander@188.107.173.215) 10.42.24 # assuming the coding is correctly formatted, and sane, could someone please look at committing FS#11632 - (rockboy) Some fixes and improvements? 10.43.09 # the playback menu is not so usefull, but a few targets can potentially pull it off. the other improvements are all good though, and quite sane IMO 10.46.56 # IIRC it shouldn't use the usual playback menu, it's about the game sound volume (I believe it was discussed here) 10.47.44 # * S_a_i_n_t looks again. 10.48.39 # - I added a playback-control at the menu. Primary to change the ingame volume at rockboy. In some cases it should also be possible to play music while running rockboy, but on my player (sansa fuze v2), rockboy crashes then because there is not enought memory. Maybe somebody finds a way to catch this and makes something, that only shows the playback-menu on players, where both - gnuboy and music playing - is possible on the same time and where not only a 10.48.45 # sorry for the huge post. 10.49.29 # What he describes will only take some simple ifdeffing also, its safe to assume none of the lowmem targets will have a hope in hell of achieving playback+rockboy 10.50.08 # the beast and NAno2G should be able to do playback+rockboy 10.50.15 # *nano 10.51.10 # well, wouldn't your simple ifdeffing mean there won't be a playback menu at all on those players and then you again can't change the ingame volume? Isn't this what the author wanted? 10.51.49 # No, I mean you could remove all but the volume from the playback menu. 10.51.58 # I probably should have been more descriptive 10.52.49 # that would be very odd and I wouldn't expect to find ingame sound control in a playback menu 10.53.19 # this is true, it could be ranamed in those cases though. 10.53.26 # *renamed 10.54.00 # that would mean complicating the patch a LOT more than it is presently though. 10.54.44 # the [;ayback menu should be dropped from it completely IMO, the rest of the options the patch adds are quite useful though. 10.54.50 # *playback 10.55.57 # Only a very simple change to remove the playback menu, which would more than likely increase the chance of it being cmmitted 11.04.35 *** Saving seen data "./dancer.seen" 11.04.57 Join TheSeven [0] (~TheSeven@rockbox/developer/TheSeven) 11.14.12 # which targets use which lcd drivers? 11.14.19 # * JdGordon is going to need help testing :( 11.15.39 Join Thanatos [0] (~Nausicaa@c-71-239-58-153.hsd1.il.comcast.net) 11.18.23 Quit swilde (Quit: ERC Version 5.3 (IRC client for Emacs)) 11.30.24 Join LinusN [0] (~linus@rockbox/developer/LinusN) 11.30.30 Join kugel [0] (~kugel@e178062159.adsl.alicedsl.de) 11.30.32 Quit kugel (Changing host) 11.30.32 Join kugel [0] (~kugel@rockbox/developer/kugel) 11.31.26 # JdGordon: It's not a bug that the bg color is ignored when a backdrop is set 11.31.29 Join swilde [0] (~wilde@aktaia.intevation.org) 11.31.37 # tis! 11.31.46 Quit hebz0rl (Quit: Leaving) 11.31.50 # see the log from a few hours ago 11.32.01 # s/few/8 or so/ 11.33.54 Join openwound [0] (~g@118.216.72.158) 11.33.56 # hi 11.34.15 # can i ask some rockbox? 11.34.56 # i have a mp3; model - sansa view 11.35.34 Quit kugel (Ping timeout: 245 seconds) 11.35.58 # i really want to adapt to my mp3; sansa view 11.36.09 Quit GodEater (Read error: Operation timed out) 11.36.09 Join kugel [0] (~kugel@e178062159.adsl.alicedsl.de) 11.36.11 Quit kugel (Changing host) 11.36.11 Join kugel [0] (~kugel@rockbox/developer/kugel) 11.37.33 # JdGordon: what are you referring to? 11.37.42 # ? 11.37.47 # um.... 11.37.48 # .... 11.38.11 # kugel: we discussed the bug today here.. it is a bug 11.38.12 # openwound, afair there is not any done for sansa view yet 11.38.13 Join dfkt [0] (dfkt@unaffiliated/dfkt) 11.38.18 # gevaerts: I'm only reading this now; the issues with plugins running greylib on COP sould like caching issues. The old plugin loading code was carefully designed to handle this 11.38.36 # Greylib is special because it's running an ISR on COP, not a thread 11.38.38 # oo 11.38.59 # JdGordon: yes, I saw that. and I tell you it's not a bug 11.39.03 # openwound: what do you mean with "adapt"? Do you want to put work into porting, coding? 11.39.24 # JdGordon: yes, I saw that. and I tell you it's not a bug 11.39.36 # kugel: ok, fine, thats your opinion 11.40.04 # which you are of course entitled to 11.40.53 # sansa view is abandoned? 11.40.56 # there can only be one background. bg color or backdrop. there is no such thing like two backgrounds 11.40.59 # do any of the 2bit lcd targets have a cabbie with a background? 11.41.48 # and what you plan seems to rather abuse it as a second foreground 11.42.05 # sansa view's developments are ceased.. right? 11.42.11 # this is NOT about more than one background, this is about forcing a viepwort to not use it 11.42.19 # openwound: noone is currently working on it 11.42.33 # ok 11.42.39 # thanks 11.47.29 # JdGordon: Many of them, yes 11.47.35 # JdGordon: sure (about greyscale cabbiev2 with background) - the now playing bar and the logo in the bottom left corner are part of the backdrop usually, the slightly bigger displays also have a menu backdrop 11.48.08 # yeah, ok.. the 2 bit driver seems to be a bit trickier 11.49.05 # JdGordon: there was once a feature request about what you now declare as bug 11.49.08 # why is there a clearimgpixel() and clearpixel() 11.49.14 # JdGordon: there was once a feature request about what you now declare as bug 11.49.23 # oops 11.50.15 # oh, same as 16bit 11.50.22 Join GodEater [0] (~bibble@cl-711.lon-02.gb.sixxs.net) 11.50.22 Quit GodEater (Changing host) 11.50.22 Join GodEater [0] (~bibble@rockbox/staff/GodEater) 11.54.02 # A backdrop is always global and overrides bgpattern 11.54.08 Quit Dreamxtreme (Quit: Don't follow me) 11.54.21 # This is done by using a different set of pixel and block functions 11.55.16 # This is something I want to change, but it needs to be done efficiently 11.55.24 # if someone doesn;t want the BG colour to override/overdraw the backdrop...they can easily eacape it with a - 11.55.39 # 8escape 11.55.44 # gah. 11.55.55 # no... the only way to bypass the image is in the skin using %Vb() which is what it should do 11.56.24 # I mean, with the intended change 11.56.36 # so do I 11.56.56 # If you don't want the BG colour to draw in a viewport...if a backdrop is loaded, using a "-" should be fine. 11.56.59 # nowhere else in the code (well, currently) would override it 11.57.37 # If the BG colour will always draw over the backdrop..then this is going to suck ass. 11.57.50 # perhaps I'm getting confused though 11.58.06 # see, it's not a bug. it's just not implemented 11.58.07 # no, that is backwards... %Vb() is optional, only used if you want a solid colour instead of the image 11.58.27 # amiconn: what do you want to change? or to how? 11.58.29 # i was wondering why Rockbox is not on the View 11.59.14 # openwound: because you haven't done the work yet. 11.59.14 # S_a_i_n_t: s/perhaps// 11.59.14 # kugel: semantics 11.59.30 Part LinusN 11.59.59 # yet? 'yet' means that view is in progress? 12.00.12 # noone is working on it 12.00.21 # no, "yet" means..."you haven't done the work yet" 12.00.34 # you/noone 12.00.56 # But, if you're interested in it, and have the target...you seem like the perfect person to start. 12.02.08 Quit antil33t () 12.02.51 # openwound: See http://www.rockbox.org/wiki/NewPort for the port process in general and http://www.rockbox.org/wiki/SansaView for what is known about the View. As others have said, nobody is working on it. 12.03.02 # thanks 12.03.25 Quit timccc (Quit: Leaving.) 12.03.37 # The work is far from trivial however. 12.07.12 # how does http://pastebin.com/wFe67Jv7 look? for some reason the list icons arnt drawing properly on the 2bit lcd 12.09.06 # http://imagebin.ca/view/XEh1MEXs.html is that because the image source isnt transarent? 12.09.22 Join timccc [0] (~tim@112.166.15.141) 12.10.46 Join krabador [0] (~krabador@host212-175-dynamic.116-80-r.retail.telecomitalia.it) 12.11.22 # probably - greyscale has no transparency. The only thing that comes close is using monochrome bitmaps then you have background/foreground colour 12.11.36 # how does the default icon set look like? 12.12.21 Join LinusN [0] (~linus@rockbox/developer/LinusN) 12.12.22 # guess it'll look fine though, seeing that text works 12.13.05 # the source image looks b+w to me, but it could be 2bit? 12.13.11 Quit timccc (Quit: Leaving.) 12.13.17 # yeah text and the statusbar works so its probably ok.. 12.13.25 # 2 more drivers to go.. and then... TESTING! 12.13.48 # the tango icons? Not b/w at all 12.14.45 # ok, so that would explain it then 12.15.24 # looks like the source image is named wrong 12.16.38 # d 12.16.42 Quit openwound (Quit: Http://www.ZeroIRC.NET ¢Æ Zero IRC ¢Æ Ver 2.9G) 12.17.26 Join Openwound [0] (~g@118.216.72.158) 12.17.53 # or at least misleading 12.19.46 Quit Openwound (Client Quit) 12.20.10 Join Openwound [0] (~g@118.216.72.158) 12.20.51 Join swiftkick [0] (~swiftkick@38.106.186.56) 12.21.17 # is there a charging issue on the sansa fuze for rockbox 3.6 12.21.44 # brand new fuze v1, with fresh install of rockbox v3.6 via windows installer 12.21.53 Join timccc [0] (~tim@112.166.15.141) 12.22.02 # no music on device, all on sd card. played thru all the 1st battery charge 12.22.33 # and now, device doesnt seem to be charging. turning device on, rockbox splash screen, then powers back off because not enough battery 12.22.45 # connecting USB cable doesnt seem to do anything either 12.23.07 # whether connected to charger or computer 12.27.15 Quit Llorean (Ping timeout: 272 seconds) 12.28.49 # no access to device anymore via USB. upon inserting USB cable, windows says: "One of the USB devices connected to this computer has malfunctioned. " 12.28.54 Join robin0800 [0] (~robin0800@cpc2-brig8-0-0-cust964.3-3.cable.virginmedia.com) 12.31.16 Quit krabador (Quit: Sto andando via) 12.33.13 Quit earcar (Quit: zzzzzz) 12.34.35 Join earcar [0] (~carmine@93-39-245-25.ip78.fastwebnet.it) 12.35.34 Quit kugel (Ping timeout: 245 seconds) 12.36.23 Quit earcar (Client Quit) 12.37.09 # amiconn: you got a minute? 12.37.27 # your name is at the top of lcd-2bit.vi.c 12.38.05 Quit Openwound (Quit: Http://www.ZeroIRC.NET ¢Æ Zero IRC ¢Æ Ver 2.9G) 12.45.47 Quit Rob2223 (Ping timeout: 240 seconds) 12.46.21 Join Rob2222 [0] (~Miranda@pD9FE25AE.dip.t-dialin.net) 12.51.05 # can someone how knows the 2bit lcd drivers please look at http://www.rockbox.org/tracker/task/11665#comment37247 ? 12.51.15 # also anyone who wants to test it... 12.51.44 # JdGordon: Can I poke you about the eabi toolchain? 12.52.20 # I'll swap you for the images I've requested :D 12.52.36 Join kugel [0] (~kugel@212.23.105.133) 12.52.39 Quit kugel (Changing host) 12.52.39 Join kugel [0] (~kugel@rockbox/developer/kugel) 12.52.49 # Fair enough. 12.54.34 # S_a_i_n_t: you can poke me 12.54.59 Quit kugel (Remote host closed the connection) 12.55.11 # kugel: You have CygWin arm-elf-eabi tolchain? 12.55.46 # I don't even want to think about what you could mean otherwise!?! 12.56.08 # ...or, perhaps ;) 12.57.05 Join kugel [0] (~kugel@188.46.81.188) 12.57.07 Quit kugel (Changing host) 12.57.07 Join kugel [0] (~kugel@rockbox/developer/kugel) 13.00.18 # what's your issue with the toolchain? people successfully built it on cygwin 13.00.56 # it's a PITA, and the necessary packages for eabi aren't doccumented. 13.01.32 # I bluffed it last time with the help of someone who's nick escapes me. 13.02.26 # I don't know of any extra package needed except a host toolchain and patch,wget/curl 13.02.59 # MPFR, and GMP are two I can think of off the top of my head. 13.03.31 # I just remember it was a real PITA, one I'd like to avoid if possible. 13.03.33 # doesn't rockboxdev.sh download those? 13.04.06 # they are needed, but you don't need to install them on a Linux box 13.04.10 # If it does, it's a new addition...well, new-ish 13.04.18 # I had to add them to build it initially 13.04.38 *** Saving seen data "./dancer.seen" 13.04.56 # that's possible. I think it downloads since the official switch 13.05.58 # I'll try set it up to run again while I'm asleep, but, I'd really like to just c/p it from another source if someone feels like being kind to me. 13.06.33 # I only have access to a pretty slow machine at them moment. 13.06.50 # just executing rockboxdev.sh ought to be enough really 13.07.37 # (after installing wget and patch) 13.07.47 # I'm trying to trying to remember the name of the guy that I figured out the additional packages with...Japanese guy, doesn;t come in often, rather broken english. 13.08.00 # He did the embedded AA patch 13.08.12 # uuchida iirc 13.08.20 # that's the one. 13.08.25 # that was driving me nuts 13.16.31 Quit kugel (Quit: Yaaic - Yet another Android IRC client - http://www.yaaic.org) 13.19.25 # JdGordon: Why did you open a bug for the fact that the backdrop is _by design_ an attribute of the screen, and not the viewports on the screen? 13.20.42 Join wodz [0] (~wodz@skatol.ch.pw.edu.pl) 13.20.59 Quit Thanatos (Ping timeout: 245 seconds) 13.21.26 # because the design is wrong 13.21.32 # or has become wrong 13.22.16 # Yes, but that's not a bug. Otherwise many feature requests could be argued as bugs that way. 13.22.48 # how does it really make a difference? the patch is all that anyone should be caring about 13.23.00 # The backdrop being for the whole screen is by design, for performance reasons 13.23.13 # That's what I'm asking - why did you open a bug report, instead of just posting a patch. 13.23.41 # I would be hugely surprised if there was a 0.1% perf loss from this patch 13.23.50 # What I want to change/ add is that you can specify whether the backdrop should be used or not, by means of another draw mode bit 13.24.00 Join krabador [0] (~krabador@host212-175-dynamic.116-80-r.retail.telecomitalia.it) 13.24.39 # amiconn: thats oretty much what I;ve done, but part of the viewport which I tink is better than drawmode 13.24.54 # The drawmode *is* part of the viewport 13.26.20 Join funman [0] (~fun@rockbox/developer/funman) 13.26.25 Join Dreamxtreme [0] (~Dreamxtre@92.30.213.124) 13.26.37 # And the patch will cost quite a bit of efficiency 13.26.45 # (in its current form) 13.27.57 # JdGordon: Regarding the patch itself, I don't like the lcd_using_backdrop() function. Firstly, it's badly named (it should be viewport_using_backdrop()), and secondly, it obfuscates the fact that you're just testing the value of a boolean in the viewport struct. 13.28.04 # hi funman , any news about the sd card ? 13.28.14 # Adding an if() to the *pixel() functions ia a bad idea 13.28.35 # That's why the drivers are using those function arrays 13.29.11 # One set of functions is used when a backdrop is present, the other when there isn't 13.29.24 # an if which is hit almost never (maybe it need the [UN]LIKELY() macro) would actually add noticable difference? 13.29.51 # * JdGordon will do a lcd bench on the mini2g in a few min 13.30.30 # linuxstb: sure, that can be changed, I wanted to get it working first 13.30.57 # JdGordon: out of curiosity - can you try to view a few jpgs and bmps on your mini? 13.31.03 # That if() is hit for *every* pixel that's drawn by the respective pixel function 13.31.27 # And (UN)LIKELY doesn't help here 13.31.44 # wodz: yeah, sure 13.32.08 Join Openwound [0] (~g@118.216.72.158) 13.32.37 Join hebz0rl [0] (~hebz0rl@dslb-088-065-058-252.pools.arcor-ip.net) 13.32.40 # pSiKO: no 13.32.49 # My idea doesn't need that if() at all - but it needs clever extension of the function pointer array to allow switching between both cases quickly (i.e. without rewriting the pointers) 13.33.14 # I can't test right now if gevaerts change from yesterday fixes greylib on COP problem I am experiencing 13.35.48 Quit jfc (Ping timeout: 255 seconds) 13.37.29 # according to the wiki, the mini2g does 166.5FPS unboosted, even if that patch drops that by 1% it should be perfectly acceptable. That would give absolutly no noticable impact anywhere 13.37.59 # This has nothing to do with updating fps. It's about drawing speed 13.38.33 # Update speed is framebuffer -> lcd; this is app code -> framebuffer 13.39.13 # even more so no big deal 13.39.18 # JdGordon: The actual numbers aren't important IMO. We should always aim to write things as efficiently as possible, especially in something like the lcd driver. Effectively adding an if() inside a loop isn't good if it can be avoided, which amiconn is saying it can. 13.39.23 # Efficiency is always a deal 13.40.28 # sure, if someone were to do it fine, but in the absense of that I dont see why slightly less efficient is such a bad thing 13.40.35 # In fact I already had that functionality added half-way a year ago or so, but ran into some problem (which I don't remember anymore, unfortunately) 13.40.37 # and there is a case of overoptimising, but thats an argument I know I'll lose 13.41.25 # Ever used rb on an ipod video? 13.41.26 # there is not something like overoptimising in embedded world 13.41.49 # JdGordon: This isn't optimising, this is taking care to write something efficiently in the first place. 13.42.03 # If you di (or do) you'll see drawing speed is a real issue, at least on some targets 13.42.09 # *did 13.42.43 # I use my video occasionally... 13.43.06 # umm... if the seperate functions are there already then its simply a matter of saping the drawing funcs pointer on lcd_set_viewport 13.44.01 Part funman 13.44.33 # 2 line change instead... 13.44.34 Quit krabador (Read error: Connection reset by peer) 13.44.37 # It's not that simple 13.45.41 # surely it is? :D 13.46.07 # It is an array, and copying all pointers around isn't efficient 13.46.22 # Probably better than checking an if() for each pixel, but still 13.46.43 # in lcd_set_viewport() http://pastebin.com/015wDn3j 13.46.53 # isnt that what you were suggesting before? 13.47.04 # just make the driver think there is no backdrop 13.48.05 # Not entirelx 13.48.07 # *y 13.48.46 # What happens if you change this property (be it separate or part of the drawmode) for an existing viewport? 13.49.05 # it will take effect every time you select that viewport 13.49.18 # if you do it after calling lcd_set_viewport() you are doing it wrong 13.49.39 # That's why I want it to be part of the draw mode 13.50.11 # It should be selectable without changing the viewport 13.50.25 # so it gets checked before every draw function? 13.50.42 # no 13.50.57 # It gets set whenever you call lcd_set_drawmode() 13.52.22 # how is that really any better? if this changes during a viewports life it could cause very wierd issues, especially scrolling 13.52.27 # Actually I think the problem was the behaviour to default to, because the *wrong* default would mean that all app code has to be adapted immediately 13.52.47 # No, because scrolling has to store the drawmode anyway 13.53.44 # (and even has to modify it in some cases) 13.54.13 # nothing apart from the driver should need to be touched for this to be added 13.54.21 # default is use the image 13.55.22 # pixelma: Your try to build player sim with my patch applied spots apps/talk.c as an another place where lowlevel SH specific code survived :-) 14.00.55 Join krabador [0] (~krabador@host6-182-dynamic.27-79-r.retail.telecomitalia.it) 14.01.29 # does the playback work in hwcodec sims? 14.01.54 # there won't be sound 14.02.36 # thx, that's what I expected 14.05.40 # nuts, ok apparently it aint working :/ 14.07.01 # I think in the skin renderer though maybe 14.11.39 # JdGordon: what about jpgs/bmps on mini? 14.11.55 Quit Openwound (Quit: Http://www.ZeroIRC.NET ¢Æ Zero IRC ¢Æ Ver 2.9G) 14.12.01 # you got any I should look at? or just in general? 14.12.33 # just in general - I either got crash or screen corruption 14.13.55 # well freeze rather than crash 14.14.50 Join teru [0] (~teru@KD059133111160.ppp.dion.ne.jp) 14.15.37 # they look crap on the lcd, but no problems 14.16.02 # what revision are you using? 14.16.50 # 28243 14.16.56 # just built 14.18.29 # If this is not to much could you test revision before gevaerts change from yesterday? 14.18.56 # ok, hang on 14.19.01 # which change? 14.19.13 # about plugins loading 14.20.39 # building 14.22.02 # JdGordon: skin paraser should check viewport dimension. do you think change is correct? http://pastie.org/1212801 14.22.07 # hang/crash with lcd off 14.22.56 # teru: is that really needed? 14.23.44 # wodz: lcd backlight off I mean.. that fix apparently works 14.23.57 # JdGordon: cool 14.24.30 # i think yes. drawing something in the viewport witch is out of the screen make player crash. 14.25.11 # I was hit by this bug when I was working on png plugin. I spend a lot of time debuging my code before I found out that this is more general problem 14.34.01 # JdGordon: Didn't the viewport parser check the bounds of the viewports in the past? 14.34.21 # JdGordon: my gigabeat X30 freezes with http://pastie.org/1212817 14.34.21 Quit wodz (Quit: Leaving) 14.34.24 # I dunno 14.34.36 # The intention when I implemented viewports was that the apps code was responsibile for ensuring the viewports were within the screen. 14.34.54 # teru: run it through gdb? 14.35.36 # it used to be checked in viewport_parse_viewport() or something like that. it is one reason i think the parser should check. 14.36.28 # amiconn: what about this? http://pastie.org/1212822 It still doesnt use the draw mode, but I dont really see how doing so would make it any better 14.37.02 # JdGordon: sorry, i donno how to run gdb on target. 14.37.09 # on sim 14.38.05 # - for font?! 14.38.09 # that shouldnt be legal 14.38.49 # Anyone here willing to test the iLike theme for iPod Video? I'm wanting to see if it's up to "release quality" yet. 14.39.15 # actually, maybe it is 14.43.04 Join evilnick_B [0] (0c140464@rockbox/staff/evilnick) 14.47.26 Join webguest76 [0] (~41746602@giant.haxx.se) 14.48.09 # which computer gbc emulators accept the .sav save file from rockboy? 14.48.45 # rockboy is a port of GNUboy, so maybe that. 14.52.54 # JdGordon: i think i am able to run sim with gdb. what do you want me to do? even if viewport out of the screen doesn't hurt, i think it is better to check the viewport dimension. 14.53.29 # run gdb and see where it crashes 14.53.31 # and yeah, commit that check if you want 14.59.07 Quit webguest76 (Quit: CGI:IRC) 15.00.50 # amiconn: linuxstb: I've updated 11665 15.00.54 Join komputes [0] (~komputes@ubuntu/member/komputes) 15.04.40 *** Saving seen data "./dancer.seen" 15.05.08 Part LinusN 15.06.50 Quit JdGordon (Ping timeout: 240 seconds) 15.08.52 # New commit by 03teru (r28244): check viewport dimension when parsing viewport so that player doesn't clash with bad wps. 15.11.03 # r28244 build result: All green 15.11.45 Join domonoky [0] (~Domonoky@rockbox/developer/domonoky) 15.16.18 Join Kitr88 [0] (~Kitarist@BSN-182-113-81.dial-up.dsl.siol.net) 15.17.18 # http://www.rockbox.org/tracker/task/11664 nice. I will try this today in the evening 15.18.46 # teru: Why do VP dimensions need checking? 15.18.59 # an out-of-bounds VP won't crash the player. 15.19.05 # Or, shouldn't. 15.19.52 Quit Kitar|st (Ping timeout: 264 seconds) 15.21.02 # at least, http://pastie.org/1212817 crashes my player. 15.21.18 Quit Kitr88 (Ping timeout: 264 seconds) 15.22.04 # weird...I just tried it then, editing the VP dimension with the text editor on my ipod, and I can excede the dimensions of the screen quite easily 15.22.46 # on a 176px screen I tried displaying a 100x50VP at 0x100 and it worked fine 15.24.36 # did you put a text or image on th viewport? the clash seems to happen because lcd functions tries to draw out of lcd_framebuffer. 15.24.54 # it had a progressbar in it. 15.25.02 # so, it even dynamically updates. 15.25.05 # and, is fine. 15.26.19 Join Kitar|st [0] (Kitarist@BSN-143-105-192.dial-up.dsl.siol.net) 15.31.31 Join kugel [0] (~kugel@141.45.200.195) 15.31.33 Quit kugel (Changing host) 15.31.33 Join kugel [0] (~kugel@rockbox/developer/kugel) 15.32.45 Join piotrekm [0] (~piotrek@unaffiliated/piotrekm) 15.33.47 # S_a_i_n_t: i don't know why the result is different then. there is still no issue if you put the vp at e.g 0x500? 15.34.02 # I'll try that in a second. 15.41.25 Quit domonoky (Read error: Connection reset by peer) 15.42.35 Join domonoky [0] (~Domonoky@rockbox/developer/domonoky) 15.45.26 Join jgarvey [0] (~jgarvey@cpe-065-190-066-089.nc.res.rr.com) 15.45.34 # Any iPod Video testers present? 15.57.22 # S_a_i_n_t: The viewport params need checking because passing valid viewports to the LCD driver is the responsibility of apps/ code. The viewport parsing code used to do that, but JdGordon (I assume) removed it. 15.58.34 # it doesn't use viewport_parse_viewport anymore 15.59.07 # I think it still matters if the x,y positioning is out of bounds, but it never used to matter if the viewport extended out of bounds. 16.03.40 Join Strife89TX [0] (~cstrife89@207.144.201.128) 16.04.13 # S_a_i_n_t: Well, Rockbox should reject such viewport definitions as invalid, and IIRC it used to. 16.05.06 # * S_a_i_n_t has seen plenty of themes with incorrect viewport defs that still load. 16.05.34 # S_a_i_n_t: Recently, or when viewports were first implemented in the WPS? 16.06.09 # fairly recently, so, unless it suddenly started breaking things in the past few months or so...it still should work. 16.06.23 Quit kugel (Read error: Connection reset by peer) 16.08.39 # You say those themes load, but do they work reliably without crashing Rockbox? But that would depend on how wrong they were. 16.09.47 # Of the authors I contacted, from the themes I fixed personally...not one of them had an idea that it wasn't advisable to do so. 16.10.05 # S_a_i_n_t: This is more a "how it should be done properly" than "it doesn't happen to crash in some cases so let's not care" 16.10.18 # I even have a theme that relies on the fact that it is possible to "slide" an image onscreen via an animation. 16.10.37 Quit Strife89TX (Ping timeout: 276 seconds) 16.11.11 Join kugel [0] (~kugel@141.45.200.195) 16.11.13 Quit kugel (Changing host) 16.11.13 Join kugel [0] (~kugel@rockbox/developer/kugel) 16.11.33 # The themeeditor will need some work then, as it doesn;t care one bit about out of bounds VPs 16.11.46 # and I assume there's a lot of "new themers" using it. 16.13.52 # Question: Would it be OK to pop a theme in the Themeing and Customization Forums for testing? 16.14.01 Join Rhcp1253 [0] (~rooms@ool-18bd6cc8.dyn.optonline.net) 16.14.12 # Sure, that's what others do 16.15.11 # Awesome, I was aware others did so...but I wasn't sure if it was frowned upon at all or not. 16.15.31 # I'm just wondering, is anyone actively working on the USB driver for the nano 2g? 16.15.42 # Or currently rather 16.15.52 # Rhcp1253: How ddo you mean? 16.16.00 # what's "wrong" with it in particular? 16.16.25 # It doesn't have full control, as in no docking x 16.16.36 # Controls* 16.16.44 # how do you mean "no docking"? 16.16.51 Join Strife89TX [0] (~cstrife89@207.144.201.128) 16.16.51 # as in, it doesn't mount? 16.17.06 # When put on a dock, it resets into disk mode 16.17.25 # Rhcp1253: Hold menu 16.17.31 # It'll then charge instead 16.17.33 # that will depend entirely on the dock you use I would say. 16.17.40 # I think it is menu, check the manual 16.17.45 # Some people are using it with docks just fine. 16.18.01 # Is there anyway to get it to play music on the dock? 16.18.03 # you probably need to turn on accessory power supply 16.18.13 # some docks need to detect accessory power. 16.18.30 # Yea, I have that enabled 16.18.52 # then, your dock isn;t supported. 16.18.53 # Rhcp1253: Hold menu when plugging it in so it doesn't go to diskmode, then try 16.19.06 # there's very few accessories known to work with the iPods really. 16.19.09 # Incidently, this is nothing to do zith USB 16.19.36 # Ok, so it's my dock/configuration that's screwy? 16.19.49 # try holding Menu while docking it. 16.19.56 # failing that, yes. 16.20.01 # No, Rockbox has incomplete support for the apple accessory protocol 16.20.14 # Or maybe it is the serial driver, I forget which 16.20.22 # Ok, I'll try that an get back to you if I can. Thanks :) 16.21.01 # Nano2G USB is actually pretty solid, it's the HID that's completely borked. 16.21.53 Join leavittx_ [0] (~lev@89.221.199.187) 16.21.58 # Well, a followup question: psgroove has been ported to other rockbox'd iPods, but why not the 2nd gem nano? 16.22.10 # Gen* 16.22.29 # Because noone has done the work yet. 16.22.52 # So it's just a matter of taking the time to 16.23.00 Join beomuex [0] (~beowulf@unixboard/users/beomuex) 16.23.02 # Ok, that makes sense 16.23.09 # time/effort...people work on what they want to. 16.23.32 # Seems usual nowadays 16.24.27 # Rhcp1253: That's how Rockbox has been developed for the last 9 years... 16.25.15 Quit Strife89TX (Quit: Leaving) 16.25.49 # Well somethings going right then :) 16.26.05 # Rhcp1253: and anyway, psgroove isn't our software. They presumably have their own places to discuss it 16.27.11 # Ok, I just figured you guys would have better info on the drivers, which u did 16.27.34 Nick Rhcp1253 is now known as rhcp1253 (~rooms@ool-18bd6cc8.dyn.optonline.net) 16.29.28 # rhcp1253: All the other ipods use a different CPU and different USB driver. The hardware of the 2nd gen Nano has very little in common with the other ipods supported by Rockbox. 16.29.52 # Is there another page besides http://www.rockbox.org/wiki/CustomConfigFile with all possible key/values for the config.cfg? 16.30.17 # beomuex: All should be present there. 16.30.30 # That's probably why the exploit and development took so long 16.30.47 # sure? I cannot find the key that enables the .talk files 16.31.17 # why are you looking in the config? 16.31.25 # all you need to do is set it in the menu 16.31.28 # because my display is broken ;) 16.31.34 # Aha. 16.31.43 # ;) 16.31.45 # Don't your menus talk? 16.31.59 # reset your config, it is enabled by default. 16.32.00 Join DSStrife89 [0] (~Strife89@207.144.201.128) 16.32.16 # you may not actually have the voice files present. 16.32.20 Quit piotrekm (Quit: piotrekm) 16.32.26 # yeah. They do. But the database entries aren't. The are spelled letter by letter. 16.32.55 # you need to create .talk files for them 16.33.07 # they aren't handled the same way. 16.33.47 # already done. This page http://tinyurl.com/3yymg5p 16.33.57 # talks about an option that enables them 16.34.36 # well, if the menus are voiced, using the manual it shouldn;t be hard to find the option on the device. 16.35.13 # I g2g 16.35.26 # Thank you for the help :) 16.35.31 Part rhcp1253 16.42.33 # S_a_i_n_t, yeah sure. But this page http://www.rockbox.org/wiki/CustomConfigFile does not provide a key that has anything to do with the option mentioned in the manual. Deleting the config.cfg enables the spoken output of the main menu but does not enable file spelling (or even spoken filenames using .talk files) 16.44.24 Quit teru (Quit: Quit) 16.44.55 # beomuex: the only ones I know of are: 16.44.57 # talk dir clip: off 16.44.58 # talk dir: off 16.44.58 # talk file clip: off 16.44.58 DBUG Enqueued KICK S_a_i_n_t 16.44.58 # talk file: off 16.44.58 # talk filetype: off 16.44.58 *** Alert Mode level 1 16.44.58 # talk menu: off 16.45.33 # many thanks! 16.46.05 # obviously, you'll want to substitute off with on 16.49.10 Part Zagor 16.49.45 Join jfc [0] (~john@dpc6682208002.direcpc.com) 16.49.48 Join Zagor [0] (~bjst@rockbox/developer/Zagor) 16.54.46 Join pyro_maniac [0] (foobar@p57BB8B59.dip0.t-ipconnect.de) 16.54.59 *** Alert Mode OFF 16.57.54 Quit DSStrife89 (Ping timeout: 240 seconds) 16.59.12 Join Judas_PhD [0] (~kevin@misterfluffy.dsl.xmission.com) 17.00.01 Quit kugel (Ping timeout: 260 seconds) 17.00.57 # there seems to be an unneeded '>' in line 71. can somebody check this please? 17.02.05 Ctcp Ignored 1 channel CTCP requests in 0 seconds at the last flood 17.02.05 # * linuxstb wonders what he missed - line 71 of what? 17.02.36 # sry 17.03.14 # missed to say the file name :-S me was talking about wps/cabbiev2.176x220x16.wps 17.04.43 *** Saving seen data "./dancer.seen" 17.05.29 Part Zagor 17.08.13 # pyro_maniac: Yes, that looks wrong to me, but I know nothing about wps syntax.... JdGordon committed that change. 17.09.10 # i spotted it by using my e250 and was wondering why this > is there 17.09.26 # it's wrong and weird that the WPS isn't rejected 17.09.51 # pixelma: Wouldn't it just be interpreted as text? 17.10.14 # seems so 17.10.26 # because its shown as text 17.10.53 # But I mean, that's what I would expect to happen, unless ">" is supposed to be an illegal character in WPS text. 17.11.56 # ">" closes conditional statements, I thought all special chars are interpreted as special, no matter where they are 17.12.08 # but its the only wps with a > after Next Track: 17.12.30 # without an < before i mean 17.12.35 # otherwise you wouldn't need to escape them with % everywhere, just in some cases, where it could be confusing 17.13.17 # there was no start of a conditional on that line though 17.14.10 # a < or a > will just be treated as text unless there's a tag prepending the < 17.14.42 # That one was probably my fault, strange it took so long for someone to notice it, but, thanks. 17.15.27 # pixelma: I think that's a pretty standard behaviour for language parsers. i.e. the ">" only needs to be escaped when it is ambiguous. 17.16.37 # well, I don't care much and will go on escaping these characters everywhere 17.17.07 Join _s1gma [0] (~d.d.derp@77.107.164.131) 17.18.08 # seems unnecessary...I'm fairly certain it needn't be escaped but I'll need to check that. 17.19.05 # Hmmm...apparently it *does* need escaping. 17.19.24 # * S_a_i_n_t looks at the code to see why it's being displayed. 17.19.48 # in this case it shouldn't be there at all 17.21.01 # No, that's quite correct. 17.21.12 # It *should* choke the parser though. 17.21.21 # weird it doesn't. 17.22.08 # S_a_i_n_t: What makes you say that it does need escaping. If the ">" in that line is being displayed, then it would seem to me that it doesn't. 17.22.13 # it was just my curiousity why the WPS is not rejected, so a single ">" somewhere seems to work. For my personal use, I'll go on escaping it as then it's a "set and forget" even if I later decide to add some conditionals to the line and it could become ambiguous (just a personal opinion) 17.22.40 # linuxstb: http://download.rockbox.org/daily/manual/rockbox-ipodnano1g/rockbox-buildap2.html#x17-362000B 17.22.45 # right down the bottom. 17.23.22 # I have also concluded it wasn't me that fucked it up, so, I'm happy. 17.23.36 # S_a_i_n_t: You mean the list of "Other Tags" ? That just says that a %> displays a ">", not that you _must_ use it. 17.23.42 # Unless some bastard went and added the crazy stype for subimages. 17.24.00 # it says it needs to be escaped. 17.24.13 # or, that is the intention. 17.24.22 # Where does it say that? 17.24.27 # it has been this way since the parser (new one) was implemented 17.24.56 # well, by saying it needs to be prepended with a %, its saying "it won;t work otherwise" 17.25.09 # otherwise, it would be irrelevant to say so. 17.26.21 # all the chars used as part of arguments are *supposed* to need escaping to be displayed as text. 17.26.23 # I wouldn't read it like that. Reading it literally, it says that "%>" produces a ">", no more and no less. 17.26.31 # otherwise an argument is/should be expected 17.26.56 # linuxstb: yes, but you say that without following the development of the parser 17.27.10 # (apparently) 17.28.25 # I thought we were talking about what the manual says? 17.28.35 # if %> produces a > and > produces a >, then what is the point of even mentioning it? surely you must read into it that the intent is to say that "this is how you display a > or a < in case you're wondering" 17.28.39 # and yes, we are. 17.29.30 # all the chars that are used in arguments for the skin syntax are supposed to need escaping, otherwise an argument is expected. 17.29.36 # No, because in other computer languages, the need to escape something can depend on the context. i.e. escaping is not always compulsory. 17.29.42 # the difference is that %> always produces a ">", while a > might not do it, depending on the circumstances. 17.30.04 # ">" shouldn;t do it under any circumstances. 17.30.10 # the parser should reject it. 17.30.19 # it is very interesting that it doesn't. 17.30.51 # who says that it shouldnt ? that depends on the WPS language definition.. 17.31.34 # if I had known that it causes such a discussion, I wouldn't have askes :\ I can follow what linuxstb is saying. 17.31.34 # S_a_i_n_t: I don't feel strongly about that - but if that's the intention, the manual should say something like "The following characters are reserved and MUST be escaped if you want them to appear literally on the screen:" 17.31.54 # or asked 17.32.08 # the parser says it shouldn't. if it sees a < it should expect anything before it to be a tag, and complain if there isn't one, and if it sees a > it should be looking for the arguments it is supposed to conatin and complain if there aren;t any. 17.32.42 # So which is wrong? The parser or the manual? 17.32.53 # pixelma: I think I just wanted to say that escaping characters is not always compulsory, so it didn't surprise me that the WPS parser didn't object to the > in that line. I have no strong view about whether that's right or wrong in the case of Rockbox. 17.32.55 # or both ? :-) 17.32.58 # that's why I find it very odd it needn't be escaped, something has changed...that somehow allows it. 17.33.11 # domonoky: Hehe! 17.34.07 # linuxstb: yes, as I said I understand that and accept it 17.34.28 # there's even one thing there that's slightly wrong afaik...it says # displays a # when it should need escaping also. 17.34.41 # that's the comment char and should always be ignored. 17.34.58 # technicallly its probably because its a closing tag, and the parser didnt see a opening tag before, so its not in the code path which checks for arguments. 17.35.07 # I suspect that's atypo though. 17.36.00 # S_a_i_n_t, my Sansa 280e Shuffle is working now, thanks 17.36.35 # No worries, I'll make a note that those config options aren't in the wiki 17.36.44 # thanks for pointing it out. 17.38.26 # After you posted the vars, I found this: http://download.rockbox.org/daily/manual/rockbox-sansae200/rockbox-buildap3.html 17.38.36 # This should cover it ;) 17.39.05 Join n1s [0] (~n1s@nl118-174-240.student.uu.se) 17.39.12 Quit n1s (Changing host) 17.39.12 Join n1s [0] (~n1s@rockbox/developer/n1s) 17.40.18 # * S_a_i_n_t points Nano/Video owners to http://forums.rockbox.org/index.php?topic=25961.0 17.47.23 Join drizztbsd_ [0] (~quassel@unaffiliated/drizztbsd) 17.49.32 Quit petur (Quit: later) 17.51.02 Quit drizztbsd (Read error: Connection reset by peer) 17.55.44 Quit domonoky (Read error: Connection reset by peer) 17.59.49 # * linuxstb looks at the skin parser and sees "colour" was used everywhere instead of "color". 18.00.01 Join [sko] [0] (~sko]@p57A9B9BE.dip0.t-ipconnect.de) 18.00.07 # colour, is correct. 18.00.17 # brittish spelling my boy. 18.00.40 # No, "colour" is correct for the manual and for comments. Code uses "color" - see the lcd driver for example. 18.01.08 Nick drizztbsd_ is now known as drizztbsd (~quassel@unaffiliated/drizztbsd) 18.01.11 # So we have things like fgcolour in the skin code, and fgcolor in the lcd code. 18.01.13 # I thought *everything* was supposed to use UK english? 18.01.29 Join domonoky [0] (~Domonoky@rockbox/developer/domonoky) 18.01.33 # I have seen comments made in the tracker to fix such conventions before now. 18.01.54 # Then they were either wrong, or should have changed the lcd drivers as well. 18.02.13 # nope, only user visible stuff 18.02.15 # But are you sure they were patches to code, and not the manual? 18.02.35 # pretty sure they were code patches. 18.02.40 # code has, as linuxstb pointed out, traditionally been american spelling but i don't think there's a rule for it and it doesn't really matter imo 18.02.50 # referring to comments being prefferred in UK english. 18.04.32 # * linuxstb doesn't want to argue about it - the fact is that code has always been US English, and now it's a messy mixture. 18.05.14 # fix it? whether or not it is UK or US I'm sure it should be consistent. 18.05.34 Join Code-Zombie [0] (~Y-U-BAN-M@75-119-242-179.dsl.teksavvy.com) 18.05.36 # Hello kids 18.11.18 # I think FS#11609 can be closed with a invalid/out of date since the problem seems to be a bios bug that we don't really want to work around and the poster hasn't responded for over a month 18.11.42 # is there any hack firmware i can run on my Nano 3g? 18.11.57 # Nope. 18.12.13 # Guess ill have to look older :/ 18.12.37 # Looking older won't help, getting an older DAP might though ;) 18.12.40 # i have an old Sansa 18.12.45 # too bad its completely broken 18.12.59 Join Strife89TX [0] (~cstrife89@207.144.201.128) 18.14.39 Join sudoman [0] (92735ab9@gateway/web/freenode/ip.146.115.90.185) 18.19.15 Join toffe82 [0] (~chatzilla@maf.wirelesstcp.net) 18.22.56 Quit Strife89TX (Quit: Food get!) 18.27.15 # does anybody technical know what would need to be done for rockbox on a nano 3g to happen? 18.27.51 # I wanna know if it's just because nobody's gotten to it, or if I should be blaming apple for locking down their hardware 18.27.57 # yes, "a lot of work" 18.27.59 # * alexbobP likes blaming things on apple 18.28.09 # S_a_i_n_t: did apple put roadblocks in the way? 18.28.16 # or is it just yet another port that would have to happen 18.28.46 # sure, but, they did the same for Nano2G also...it's not like they just leave the devices wide open. 18.29.10 # alexbobP: I think the roadblocks have been mainly overcome. But there is still a lot of hard work to do to understand the hardware, write Rockbox drivers etc. And AFAIK, no-one is actively working on it. 18.29.22 # S_a_i_n_t: well they *should* leave their devices wide open, those jerks ;) 18.29.32 # linuxstb: okay, I see 18.29.44 # Email Steve Jobs and ask him why they don't. 18.29.49 # Um...yeah...think of all the money they'd make then... 18.29.58 # yeah, selling products and all that 18.30.00 # must be a pain 18.30.02 # * S_a_i_n_t looks a "this guy's crazy look" ;) 18.30.16 # on topic please chaps 18.30.38 # linuxstb: are there unnecessary duplicated now in the code due to "color" and "colour"? 18.30.48 # I was curious because I have a roommate with a 3g... I wanna indoctrinate him into the rockbox fold 18.30.51 # duplicates even 18.30.53 # I was smart and bought a sansa fuze 18.34.19 # pixelma: No, I don't think so. It's just a lot of new code uses "colour", which jumped out at me as unexpected when I read it. 18.39.12 Join panni_ [0] (hannes@ip-178-203-81-220.unitymediagroup.de) 18.39.20 Join Maggux [0] (~quassel@krlh-4d037ef7.pool.mediaWays.net) 18.40.09 # guess it increases the chance to get unneccessary duplicates and should be fixed. Now to get someone to do it... :) 18.46.41 Join Strife89TX [0] (~cstrife89@207.144.201.128) 18.47.56 Join [sko]1 [0] (~sko]@p57A99ED4.dip0.t-ipconnect.de) 18.48.34 Quit [sko] (Ping timeout: 276 seconds) 18.48.49 # * linuxstb guesses no-one feels that strongly either way, so assumes changing "colour" to "color", to be consistent with the original decision is the direction to go? 18.49.41 # probably, yes. 18.50.13 # Even though my heart tells me "color" is wrong, if the majority is "color", then so be it. 18.50.40 # grep for both, and see which one wins and run with that ;) 18.52.52 # convention is convention.... which is American English for code, British for UI and explanations in the manual 18.53.11 # as far as I know 18.53.25 # Exactly. We could of course change that convention, but does anyone want to? 18.53.26 # except in the case of Proper Nouns, where "iPod Color" always wins. 18.53.40 # else pixelma describes the convention as I recall it. 18.53.42 # soap: it doesn't 18.53.46 # * linuxstb thought Ipod Color won, or did that get changed? 18.53.46 # no? 18.54.21 # linuxstb: if you ask me, yes but it seems nothing won in that discussion yet 18.55.11 # But the manual is still using Ipod (and Iriver) isn't it? 18.55.32 Join pamaury [0] (~quassel@dhcp-128-203.residence.ens-lyon.fr) 18.55.33 Quit pamaury (Changing host) 18.55.33 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 18.55.50 # * linuxstb greps and finds both iPod and Ipod, so that obviously wasn't won... 18.55.50 # sorry - yes I typed "iPod" out of habit. I didn't mean to emphasize that, rather "Color". 18.57.04 Quit Strife89TX (Quit: Strife89TX) 18.57.05 # my bet is it's using both somewhere, the platform files which take care of most references to the players have "Ipod" though 19.02.32 Join Llorean [0] (~DarkkOne@65.104.0.180.ptr.us.xo.net) 19.02.40 Quit Llorean (Changing host) 19.02.40 Join Llorean [0] (~DarkkOne@rockbox/user/Llorean) 19.04.45 *** Saving seen data "./dancer.seen" 19.06.31 Quit beomuex (Quit: Lost terminal) 19.08.15 Quit swilde (Quit: ERC Version 5.3 (IRC client for Emacs)) 19.13.57 Quit sudoman (Quit: Page closed) 19.14.45 # * linuxstb browses the android/ directory and sees that svn:keywords was forgotten 19.15.34 # "forgotten"... probably git-svn users 19.17.12 Quit DerPapst (Quit: Leaving.) 19.19.15 Join bertrik [0] (~bertrik@ip117-49-211-87.adsl2.static.versatel.nl) 19.19.16 Quit bertrik (Changing host) 19.19.16 Join bertrik [0] (~bertrik@rockbox/developer/bertrik) 19.19.25 # * linuxstb wonders what build.sh is for, as android/README doesn't say to run it 19.23.53 Join Horscht [0] (~Horscht@p4FD4DE05.dip.t-dialin.net) 19.23.53 Quit Horscht (Changing host) 19.23.53 Join Horscht [0] (~Horscht@xbmc/user/horscht) 19.26.33 Quit robin0800 (Read error: Connection reset by peer) 19.28.18 Join pyro_maniac1 [0] (foobar@p57BB9F75.dip0.t-ipconnect.de) 19.30.50 Quit pyro_maniac (Ping timeout: 240 seconds) 19.38.06 Part Code-Zombie ("Leaving") 19.40.16 Quit [sko]1 (Remote host closed the connection) 20.03.28 Join perrikwp [0] (~980d3288@giant.haxx.se) 20.11.18 Quit S_a_i_n_t (Quit: I'm only going to Heaven if it tastes like caramel...) 20.14.34 Quit perrikwp (Quit: CGI:IRC 0.5.9 (2006/06/06)) 20.14.39 Join webguest14 [0] (~9f8f0102@giant.haxx.se) 20.14.47 Join perrikwp [0] (~980d3288@giant.haxx.se) 20.15.29 # Hey folks, question. I amplugging my iPod 5.5g with rockbox in to my office PC and it is not showing in explorer. Any ideas why? 20.15.48 # it works fine everywhere else 20.16.02 # webguest14: do other USB storage devices work there? 20.16.13 # Some office environments explicitely block these things 20.16.29 # I just plugged in a USB thumb drive and it pickd it up 20.16.34 Join S_a_i_n_t [0] (S_a_i_n_t@203.184.1.99) 20.16.46 # gevaerts, I am admin, do you know what is blocking it? the setting 20.16.51 Join DerPapst [0] (~Alexander@p4FE8F3B5.dip.t-dialin.net) 20.17.02 # no. I just know this happens in some places 20.17.10 # lol thanks 20.17.10 # If you're admin on that system, that's unlikely I think 20.17.31 # Which version of rockbox are you running? 20.17.38 # I should know considering I am the one who images the machines from scratch and does the initial setup, I cannot think of anything on my PC that should be blocking it 20.18.06 # yes, that's fairly conclusive :) 20.18.09 # 3.4 20.18.28 # webguest14: that build didn't have usb enabled in rockbox, upgrade 20.18.47 # webguest14: does it show anything on screen when you connect? 20.18.55 # n1s: true, but 3.6 also doesn't have it 20.18.57 # Strange as it works like any other usb storage device on every other machine I have ever been on 20.19.07 # And it should still reboot to in-ROM disk mode 20.19.09 # on the ipod or PC screen? 20.19.16 # gevaerts: right, i keep forgetting that... 20.19.23 # the ipod 20.20.00 # Yeah it shows the usb and then goes to the screen that says do not disconnect 20.20.09 Join [sko] [0] (~sko]@p57A99ED4.dip0.t-ipconnect.de) 20.20.23 # my PC also makes the usb connected sound but I cannot find the iPod in explorer 20.20.33 # right. That means the ipod is behaving normally. 20.20.52 # That's actually Apple's in-ROM disk mode, so if it doesn't work, we didn't break it :) 20.21.00 # Do you have itunes on the PC? 20.21.18 # absolutley not (I mean no) 20.21.46 # I don't really know then... 20.21.49 # I am pretty sure it is an issue on my PC's end 20.22.04 Quit Dreamxtreme (Quit: There are two major products that come out of Berkeley: LSD and UNIX. We don't believe this to be a coincidence.) 20.22.11 # I am going to go have lunch with one of my desktop engineers and see what he thinks, thank you very much for your help 20.22.17 Join Dreamxtreme [0] (~Dre@92.30.213.124) 20.22.22 # sounds like a plan :) 20.22.43 # Thanks again, goodbye. 20.25.04 Quit Dreamxtreme (Client Quit) 20.25.14 Join Dreamxtreme [0] (~Dre@92.30.213.124) 20.26.26 # are there fuze v1 charging issues 20.26.55 # does rockbox for fuze v1 3.6 require botting in sansa mode to get it to charge 20.27.45 # mine seems to 20.28.11 # FYI my desktop engineer had no idea. It worked on his PC (win7) and an XP test machine that is very close to my PC. 20.28.17 # Very strange. 20.28.39 # webguest14: good luck 20.29.09 # swiftkick: dunno, but a current build on my fuzev1 charges fine in rockbox 20.30.11 # webguest14: You could try different USB ports, just for fun. Sometimes front-mounted USB ports are less reliable. You could also (if you haven't already) try starting Apple's main firmware on your ipod, and plug it in when that's running. 20.30.44 # I have tried 3 ports. Won't apples main firmware want to install itunes? 20.31.23 # nls: how do you know its charging? 20.31.27 # strange. It is showing up in the 'safely remove hardware" thing under iPod(no drive letter) but not in explorer 20.31.39 # webguest14: No (to your itunes question) 20.31.59 # People happily use ipods with Windows without ever installing itunes. 20.32.03 # n1s: how do you know its charging besides the fact that the battery size indicator moves? 20.32.13 # how do I start it in apples firmware? 20.32.28 # Turn the hold switch on immediately after you turn it on. 20.32.32 # n1s: does the battery indicator blink as well when its charging? 20.32.52 # swiftkick: the debug screen may have battery charging info. I don't know if the fuze has this, but some targets show charging current there 20.33.03 Quit [sko] (Quit: Leaving.) 20.33.16 # gevaerts: i was looking there, found something about battery 20.33.23 # All I want to do is transfer my library from the iPod to my PC. Will I be able to from the Apple firmware? 20.33.42 # gevaerts: the problem is, i think, that i used the device till it ran out completely, and so thus did not have enough juice to turn on long enough to get to charging mode (!) 20.34.13 # swiftkick: no it doesn't blink, the empty space in the battery inicator is animated with a grey thing filling the space, it's very hard to see with the default theme, but i mainly know it works because the battery was almost empty when i plugged it in and it was full when i unplugged it and worked for hours today :) 20.34.25 # webguest14: yes. The Apple firmware does mass storage like anything else, at least provided you don't install itunes :) 20.35.00 # it is in the apple firmware and still is not showing up. So strange 20.36.48 # n1s , gevaerts: last night, before booting into the sansa firmware, i ran the device - for the first time since purchasing it - all the way down to the end of the battery. 20.36.48 # n1s , gevaerts: the battery ran low enough that, turning the device on, caused it to shut down immediately, cycling booting up then powering off then rebooting, until i held power switch off. 20.36.48 # n1s , gevaerts: so I tried pluging in my car charger (=12v usb power supply with a standard sansa usb cable) 20.36.48 DBUG Enqueued KICK swiftkick 20.36.48 # n1s , gevaerts: it produced the same effect. it turned the device on from an off state, but then endless reboot cycle. 20.36.55 # webguest14: Has itunes ever been installed on that PC? 20.37.29 # webguest14: You could check the running processes for "ipodservice.exe" or something similar, which may block the ipod from appearing normally. 20.37.40 # n1s, gevaerts: booting to sansa firmware and charging there, resolved the issue 20.38.07 Quit TheSeven (Ping timeout: 272 seconds) 20.38.27 # swiftkick: are you using 3.6 release or a current build? 20.38.37 # bbl 20.38.46 # n1s, gevaerts: once home i plugged it in my home computers usb, still same reboot cycle. i was able to interrupt the rebooting by hitting the down direction button and taking it off the default menu option, to either files, or to settings, but still no charging even after 2 hrs 20.39.02 # n1s: 3.6, i think, whatever rockbock utility 1.2.8 installs out of the box 20.39.18 # version on the device shows 3.6 20.40.45 # swiftkick: i would recomend trying a current build then as that works fine for me and it has fixes that were not in 3.6 20.42.09 # n1s: thank you 20.42.50 Join user890104 [0] (Venci@Venci-Notebook-LAN.ipv6.6bez10.info) 20.43.05 # is 3.7 out? 20.43.15 # no 20.43.15 # no 20.44.07 # not sure if i saw this in the faq since i didnt think about running rockboxutility again, but rockboxutility does require booting the device in sansa mode yea? 20.44.26 # no, it shouldn't 20.44.59 # it just needs a working usb mass storage connection to install a new build 20.45.11 # so either OF or rockbox usb should work 20.45.23 # n1s: thanks, my last experience was with e200 series with no native usb support 20.48.29 # when i want to update my rockbox (for some updates in the usb-stack) do i only have to apply the new firmware do i have to update some stuff in the .rockbox-dir too? 20.50.26 # installing a new rockbox version means you extract a new set of files into the .rockbox directory 20.50.56 # updating the bootloader is usually not necessary 20.50.58 # Stummi: usually you should update everything 20.51.17 # yeah, except bootloader :) 20.52.09 Join Thanatos [0] (~Nausicaa@c-71-239-58-153.hsd1.il.comcast.net) 20.52.20 Join MethoS- [0] (~clemens@134.102.106.250) 20.52.32 # i want to test this patch: http://www.rockbox.org/tracker/task/11664 20.59.47 # Stummi: What's your question? Are you asking how to use patches? 21.00.29 # no 21.00.41 # i am asking if i have to update the bootloader 21.01.30 # or just copy the .rockbox-files 21.01.47 # My guess is probably not. Or at least, you could first test with only updating Rockbox itself. 21.01.55 # i am thinking, since the patch changes the usb-stack i have to update the bootloader, right? 21.04.47 *** Saving seen data "./dancer.seen" 21.06.01 # hm, ok 21.06.01 # I don't know if the usb stack (or any usb code) is done in the bootloader. But if a bootloader update was needed, that task should have said so - the assumption is generally that it is not. 21.06.01 # But you could add a comment to that task to ask - it's a fair question. 21.06.01 Quit webguest14 (Quit: CGI:IRC (Ping timeout)) 21.06.01 # ok 21.06.01 Quit perrikwp (Ping timeout: 245 seconds) 21.06.01 # n1s or anyone: so the place to get the latest build for my player is http://build.rockbox.org/ ? 21.06.01 Ctcp Ignored 1 channel CTCP requests in 0 seconds at the last flood 21.06.01 # * gevaerts doesn't really see how that patch could be related to the bootloader 21.06.01 # linuxstb, i think, the decission to boot into the of or rb is done by the bootloader, not? 21.06.15 Join HypothesisFrog [0] (~cens0red@arguably.quitenormal.info) 21.06.20 # Stummi: Yes, but that could be a simple GPIO pin check - i.e. it may not touch the usb hardware in any way, and hence won't be affected by this patch. 21.06.33 # hi. Are there any 16GB+ mp3 players supported by RockBox? 21.06.50 Join wodz [0] (~wodz@chello087206240131.chello.pl) 21.06.56 # pixelma: ping 21.07.11 # HypothesisFrog: Many. See the list of supported devices on the frontpage of the Rockbox website. 21.07.24 # Stummi: the requested tests aren't about booting with USB plugged in. They're about plugging USB in 21.07.36 # I mean I'm looking at this page, and it shows a heap of devices, but doesn't list what their capabilities are. http://www.rockbox.org/manual.shtml 21.07.45 # linuxstb already looking at it. 21.08.52 # n1s: ok this is weird. actually the problem seems to center on the USB connector. fully charged under sansa firmware, powered down. plugged cable in and it did the reboot cycle thing again. computer says "a usb device has malfunctioned" 21.08.53 # HypothesisFrog: Try http://www.rockbox.org/wiki/DeviceChart - and be aware that very few of those devices (if any) can still be bought new. 21.08.53 # n1s: so i reboot to sansa firmware. device recognized. both drive letters present. 21.09.36 # linuxstb thanks. So rockbox is pretty far behind? 21.10.25 # HypothesisFrog: Porting Rockbox to a device is a lot of hard work - by the time it is done, the device is often discontinued. 21.10.48 # mp3 players have a relatively short lifespan before being replaced by newer models. 21.11.09 # linuxstb: You failed to mention it is a lot of fun also :-) 21.12.25 # but in some cases the newer models doesn't differ much from the old ones and the porting for this isn not so hard ;) 21.13.25 # linuxstb ty 21.13.32 # linuxstb, HypothesisFrog: the DeviceChart lacks a few newer players, e/c200s in ther v2 series, Fuzes, Clips 21.13.36 # the Cowon D2 21.14.00 # although the latter still has some problems I think 21.14.43 # On the D2, the features that are advertised as working work fine. It's just that some features that people consider to be essential aren't advertised :) 21.15.03 # The main one being that rockbox can't write to internal flash 21.15.06 # all of those don't have 16GB storage internally but most of them (except the v1/v2 Clips), it can be expanded with a microSDHC 21.15.48 # gevaerts: didn't it also have intermittent problems since the eabi switch? 21.15.52 Quit saratoga (Ping timeout: 265 seconds) 21.16.04 # pixelma: were 21.16.18 # n't those solved yet? Maybe... 21.16.29 # * gevaerts isn't sure 21.16.48 # I thought I read there are more which come and go with builds (in the new ports thread) 21.17.00 # wodz: if you want to ask about testing, sorry I didn't so far 21.17.16 # :-/ 21.18.03 # keep on nagging :) 21.18.11 Join kazaik [0] (~kazaik@pool-71-166-29-66.bltmmd.east.verizon.net) 21.18.14 Quit Thanatos (Quit: Leaving) 21.18.46 # what is multimedia keypad mode? 21.18.55 Part HypothesisFrog 21.19.39 # i just updated to the latest build and rockbox doesnt reboot endlessly 21.19.53 # but i have something on my sansa screen that says "USB Keypad Mode" 21.20.30 # swiftkick: http://download.rockbox.org/daily/manual/rockbox-sansafuze/rockbox-buildch8.html#x11-1450008.5.8 21.20.42 # thank you gevaerts: 21.21.06 # lol why is this on by default 21.21.14 # why not? 21.21.39 # swiftkick: I also just realised what was causing your reboot problem... http://forums.rockbox.org/index.php?topic=25939.msg172869 21.21.56 # well, in rockbox mode im still getting 'a device plugged into the computer has malfunctioned' and/or 'a usb device is not recognized' and no drive letters 21.22.11 # gevaerts: /me looks 21.22.24 Join kevku [0] (~kevku@2001:7d0:0:f000::135d) 21.22.33 # Basically a mismatch between 3.6 and the latest bootloader on fuze 21.23.01 # anyone here have some experience with this jtag scanner (http://elinux.org/JTAG_Finder)? 21.23.10 # * linuxstb wonders if we're feature freezing today 21.23.17 # swiftkick: you could try disabling HID, but with most systems it should work without problems 21.23.26 # linuxstb: good question :) 21.24.11 # After last weekend's bugfixes I think we can talk seriously about releasing, so I think I'm in favour 21.24.15 # gevaerts: cool i just upped to the latest build from http://build.rockbox.org/ and it recognized the drives and such after a 2nd reboot 21.24.21 # yay 21.24.27 # I guess we just need someone saying we are in freeze in a stern voice (and be taken seriously) 21.24.42 # gevaerts: Well, you seem to be the person that's looked in depth at the outstanding bugs, so I'll bow to your judgement. 21.25.07 # gevaerts: the main reason i can think of for not wanting this usb presentation mode is, what about when i plug this in my car usb power supply 21.25.10 # n1s: actually it should be off by default since it can block normal USB data transfers on some OSs 21.25.30 # swiftkick: if that's just a power supply, it won't matter at all 21.25.34 # is it going to recognize its JUST charging and not go into HID mode? 21.25.53 # gevaerts: excellent, thanks, i am hereby reassured. =) 21.26.00 # mostly because of how helpful everyones been 21.26.02 # it should 21.26.37 # pixelma: isn't that only one OS, macosx 10.4 or something? 21.27.09 # n1s: I believe some other people reported problems too, but nothing really as clear as the OSX 1.4 case 21.27.11 # that one is known and probably older ones. I still think it's important enough 21.27.30 # gaverts: thank you and everyone else who helps keep rockbox runnin, this refurb fuze v1 cost me like, $30 at the local tiger direct, and makes a truly sweet combo with rockbox 21.27.47 # well, sure, it will be annoying for users of that system 21.27.54 # was getting worried maybe it was a janky usb interface cuz its refurb 21.28.03 # as data connection is the one you really expect to work with USB on a media player, HID is just an addition 21.28.28 Join webguest14 [0] (~9f8f0102@giant.haxx.se) 21.28.30 # K folks I am back 21.29.12 # having issue with 5.5g i pod with rockbox (3.4?) installed and it will not show up in explorer on only this one machine 21.29.16 # I would say that having recurrence in skin engine (on static allocated systems) is asking for troubles. Jd asked for help in turning this into iteration. I think we should help him before we trigger another "hard to spot (TM)" bug 21.30.01 # I am looking in device manager and have found the driver for the ipod under the generic "USB mass storage device" name 21.30.31 # webguest14: that sounds right 21.30.33 # when I uninstall and plug hte ipod back in it pops up like the pc detected it but then says "device software installed successfully" 21.30.41 # I still cannot see it in explorere 21.30.42 # webguest14: Has itunes ever been installed on that PC? 21.31.04 # linux this will sound wierd but I don't know, but I don't hink so 21.31.09 # if it was it was since uninstalled 21.31.33 # You could also check the task list for any processes running with "ipod" in their name - itunes installs a service which can block disk access. 21.31.38 # I learned from my desktop engineer that this machine was most likely NOT re-imaged before I was given it 21.32.09 # linux all I see is "ipoint.exe"... nothing else that even starts with "i" 21.32.33 # well iexplore// 21.33.23 # webguest14: OK, it was just an idea... Now I'm out of those. 21.33.32 # dang.. 21.34.24 # But this is getting off-topic for this channel - as it's happening in Apple's firmware, it's highly unlikely to be something Rockbox is doing. You're welcome in #rockbox-community though (most of the people here are there). 21.35.04 # Well thank you for your help. 21.35.07 Quit webguest14 (Quit: CGI:IRC) 21.36.58 # hmm, a thought on releases: one bigish problem seems to be (to me) that we are effectively not able to support release builds as time goes by and the trunk moves forward we (or at least I) don't remember what was broken and has since been fixed or what was disabled etc in the last release and we always ask users to try with a current build when they report bugs 21.37.49 # also there has been at least a few caases of bugs reported against 3.6 in fs that are really against trunk as well as the already fixed bugs being reported several times in the releases 21.38.30 # I think we're overdoing that though. Asking users to try with a current build before reporting bugs is fine, but sometimes some people tend to point to current builds straight away, seemingly without even looking what the problem is 21.38.44 # i think this is an argument to either release often (the 4 times/year seemed to work fine) or do more point releases 21.39.12 # bugs reported agains 3.6 is FS thing - you have no possibility to point to svn revision when submitting bugreport 21.39.29 # I think it's mainly an argument for not doing sloppy released 21.39.31 # *s 21.39.36 # wodz: sure that is mostly an FS issue 21.40.13 # I'd love to see possibility to report issue/patch agains particular svn revision 21.41.02 # gevaerts: we do have the problems with things like the recently mentioned fuze bootloader that doesn't quite work with the release ( i guess that is mostly a rbutil/manual issue though) and the clip being stable, etc, people (read devs) seem to just not think about the last release 21.41.10 # wodz: me too 21.41.53 # as time goes on, as it has since 3.6, the issues accumulate 21.42.03 # n1s: Agreed, the Fuze v2 install instructions are not very clear 21.42.57 # wodz: Isn't there a "current build" option too (or daily perhaps?) 21.43.05 # There is a way to mark a bug as 'newer than the latest release' 21.43.11 # n1s: I don't think we can blame the manual or rbutil for that. We have one released bootloader, and if the stable release and the current; build have different requirements, that's a problem 21.43.49 # Llorean: IIRC there isn't 21.44.19 # there is a "daily build" you can choose 21.44.32 # as I said yesterday, I don't remember details just that I had trouble finding something suitable for my bug reports 21.44.37 # We just need to change the text on that to "recent SVN build" or something 21.44.41 Join cardamon [0] (~mute@64.134.180.174) 21.44.45 # And then ask people to specify the number in the task description 21.44.49 # Hello. 21.44.53 # gevaerts: yes but should the bootloader be fixed or the instructions/installer? 21.44.57 # I'm pretty sure the "daily build" choice includes "specify" 21.45.02 # Or "which" 21.45.18 # n1s: changing instructions or the installer won't help 21.45.59 Join Thanatos [0] (~Nausicaa@c-71-239-58-153.hsd1.il.comcast.net) 21.46.09 # Hmm. I'm still getting used to making playlists from my player itself. There's no way to really quickly add a single file to a playlist rather than the whole directory, is there? 21.46.24 # Either release a bootloader together with the new release, or release the new bootloader later, and live with the fact that it will boot to the OF for a while after we can handle USB 21.46.29 # anyway, i (now figured out that I) mean that old releases are a support burden for us and an unplesant experience for users so we need to either put some effort into making sure the release works until the next one comes around or make releases frequent enough that it doesn't matter too much 21.46.45 # cardamon: I think you can set the hotkey to add to playlist 21.46.45 Join bmbl [0] (~Miranda@unaffiliated/bmbl) 21.46.53 # cardamon: Have a shufti at the manual 21.46.55 # cardamon: Yes there is. Long-select on the file then Insert/Queue 21.47.11 # er, shufti = look :) 21.48.04 # gevaerts: if the installer downloaded the bootloader that worked for the release and the instructions told users which one to get we would be fine, and not it wasn't so serious in this case but it's an example 21.48.25 # n1s: yes, but the bootloader that worked for the release is not supported :) 21.48.25 # s/not/no/ 21.48.38 # right :) 21.49.39 # Basically the best way to have good releases is to pretend we don't have releases so the current build has to be stable at all times :) 21.50.11 # pixelma: did you have some time to see if the screen corruption issue is still there? 21.50.14 # that is the other way, right now we are not doing either of them though :) 21.50.29 # Yes. That's what's going wrong 21.51.43 # And I sometimes suspect that some people feel they can be a bit less careful because we can point people to 3.6, forgetting that we made life hard for people who stay with 3.6 as well... 21.52.23 # * gevaerts still isn't really happy about how the theme site handles the theme syntax change 21.53.13 # How was that handled? 21.53.51 # Ouch, there's an "oldsite" linked from themes.rockbox.org? 21.54.09 Join webguest14 [0] (~9f8f0102@giant.haxx.se) 21.54.41 # From memory, first 3.6 support was going to be dropped, then it there was going to be a read-only copy, and finally the current oldsite solution was done 21.54.45 # Just wanted to let you guys know that I figured it out. For some reason the iPod was naming itself drive H: and I already have a drive H mapped 21.55.03 # webguest14: why didn't it take J: then? 21.55.04 # I disconnected that drive and the iPod popped up immedietly 21.55.09 # webguest14: Ha, good work. Thanks for letting us know 21.55.16 # Something to keep in mind 21.55.18 # I have no idea why it would not take the next letter 21.55.20 # Oh, I think I've seen that too. Windows bug I'd say 21.55.23 # like it should have 21.56.18 # Yeah went to diskmanagemtn and ipod was listed as drive h. Wierd stuff. Thanks for your help all! 21.56.20 Quit S_a_i_n_t (Quit: I'm only going to Heaven if it tastes like caramel...) 21.56.30 # * linuxstb wonders if "breaking all themes" is an excuse to go to 4.0 21.58.02 Quit webguest14 (Client Quit) 21.59.02 # gevaerts: What about a unified themes site, where you select the version of Rockbox you're running, and you get compatible themes? Or was that something no-one was motivated to implement. 21.59.25 # would moving rbutil into its own "project" in flyspray and having a "reported in version" with "Release x.y" and "Current/SVN build" for both rbutil and rockbox? 21.59.38 # linuxstb: I suspect nobody thinks the theme site is very exciting to work on 21.59.38 # gevaerts: sorry, no. I admit being a bit lazy and tired of yesterday's testing session. I will try to spend some time the rest of the day and tomorrow 21.59.39 # would it make things clearer/better, i mean? 21.59.53 # pixelma: I can definitely understand that :) 22.01.28 # Speaking of flyspray, shouldn't we review then "User Interface"/"Themes" distinction? More and more of the UI is themable, so this becomes blurry 22.01.51 # gevaerts: probably 22.02.32 # yeah, I wondered in some cases which category the bugs I reported fell under 22.03.20 # merging those two into one would probably be a good idea 22.17.08 Join TheSeven [0] (~TheSeven@rockbox/developer/TheSeven) 22.19.23 # Do wps files now include a version number? 22.19.43 # * linuxstb reads an email on the -dev list from Zagor suggesting it, but no-one seemed to reply to it. 22.21.53 # * linuxstb can't find that much discussion at all about the skin changes on the list 22.21.59 Quit TheSeven (Ping timeout: 272 seconds) 22.22.31 # I think it was mostly here 22.24.55 Quit leavittx_ (Ping timeout: 264 seconds) 22.24.59 # OK. So I'm guessing there's no version number, looking at the CustomWPS page. 22.25.47 # don't think there is, no 22.25.53 Join TheSeven [0] (~TheSeven@rockbox/developer/TheSeven) 22.27.20 Quit TheSeven (Read error: Connection reset by peer) 22.27.23 # TheSeven: You have pointed me to jtag scanner - do you know/have the documents describing how it works? 22.27.24 Join TheSeven [0] (~TheSeven@rockbox/developer/TheSeven) 22.28.32 Quit n1s (Quit: Lämnar) 22.30.04 Join gourd_captain [0] (~gourdcapt@rs221138.resnet.wright.edu) 22.30.29 # I'm having some problems with my newly purchased Sansa Fuze (v2, 8GB) and my microSD card. 22.30.52 # Whenever I access a file from it, there's a noticeable (20s?) lag before playback. 22.31.25 # try turning on the directory cache 22.31.42 # gourd_captain: that's on the microSD card, and not on internal memory? 22.31.47 # Yep. 22.33.03 # Sounds like a problem for funman... 22.33.44 # I believe there are some issues with some cards on fuzev2, which some people are looking into. I don't know details though 22.33.54 # Crap. 22.34.12 # * Torne still suggests trying the directory cache though 22.34.16 # * gourd_captain had a Clip+. Had being the emphasized word - water submersion does bad things to tech. 22.34.49 # Did you use this same card in the clip+? 22.34.54 Join fdinel [0] (~Miranda@modemcable235.127-131-66.mc.videotron.ca) 22.35.06 # Yep. 22.35.07 Join soap_ [0] (~soap@rockbox/staff/soap) 22.35.17 # Didn't think water would damage it, but who knows. 22.35.45 Quit soap (Disconnected by services) 22.35.47 Nick soap_ is now known as soap (~soap@rockbox/staff/soap) 22.35.49 # Got this one for a less terrifyingly bad screen. 22.36.06 # So the card got wet too? 22.36.10 # Yeah. 22.36.16 # For like, three seconds, tops. 22.36.18 # hm, yes. Hard to say then 22.36.40 # Directory Cache seems to have improved it immensely. 22.36.45 # It could be a rockbox issue, or it could just be the card 22.36.45 Quit bmbl (Quit: Bye!) 22.37.02 # I just didn't turn it on first because it was the source of major, major stability issues on the Clip+ when enabled. 22.37.22 # it may just be that your sd card is really slow :) 22.37.43 # or yeah, it might be our problem 22.37.48 # 16 GB Sandisk? 22.37.55 # sure, lots of sd cards are slow 22.37.57 # most, in fact :) 22.37.59 # Fair enough. 22.38.07 # Most SD cards are crap. 22.38.24 # I wasn't looking for high transfer rate, just music playback. 22.38.27 # but yeah, if it reads reliably but slowly, then it could be the problem gevaerts mentioned 22.38.28 # 20 seconds sounds excessive though 22.38.46 # With Cache turned on, it works instantaneously. 22.38.48 # gevaerts: yah, but not impossible 22.38.54 # I'd say don't throw it away. A future update may improve things 22.38.55 # gevaerts: if the fs is fragmented a lot 22.38.57 # Right 22.39.03 # This SD card does have 3200 music files loaded onto it. 22.39.09 # it might be something that we can fix in the long run 22.39.23 # but if everything *works* otherwise and it's just slow then turning the dircache on is a reasonable workaround for now :) 22.39.43 # if we figure something out and the underlying problem gets fixed you can probably turn it back off then :) 22.39.59 # Memory card is mostly fixed content, and the internal flash is what I use for podcasts. 22.40.27 Join leavittx_ [0] (~lev@host-87-146-66-217.spbmts.ru) 22.40.31 # Yeah, on the Clip+ cache would cause it to segfault when I opened the database. Not a good deal. 22.43.26 # if the trouble was the card, couldn't it be tested using the OF? 22.43.54 # Yeah, well, problem there is telling the difference between the card being slow as crap and the OF being as slow as hell. 22.44.04 # It doesn't react too well to this volume of files. 22.44.33 # or a card reader maybe if you got such a thing 22.44.45 Quit wodz (Quit: Leaving) 22.44.47 # Okay - files start instantly in OF. 22.45.01 # It shows like three of my files (lack of codecs) but still. 22.45.31 # Plus side, playing doom on this is actually playable. 22.45.45 # As opposed to the hilarious dithering that results on a Clip+. 22.45.58 # * Torne still doesn't understand why anyone plays doom on rockbox. 22.46.13 # Says the one who ported frotz :) 22.46.39 Join liar_ [0] (~liar@clnet-p09-185.ikbnet.co.at) 22.46.59 # I played Slouching Torwards Bedlam on Frotz on the Clip+ once. I was REALLY bored. 22.47.19 # yeah, you must've been 22.47.29 # frotz is less terribleon players with a 4-way pad 22.47.33 # on the ipod it's just horrendous 22.47.34 Quit liar_ (Client Quit) 22.47.51 Quit gourd_captain (Quit: Leaving) 22.47.54 Quit leavittx_ (Ping timeout: 240 seconds) 22.47.54 Join liar_ [0] (~liar@clnet-p09-185.ikbnet.co.at) 22.48.42 Quit cardamon (Ping timeout: 264 seconds) 22.48.43 # in theory i ported frotz so people could use it as a target to write games rather than for people to play classic text adventures 22.48.46 # but it works, so hey 22.57.49 Join edboyer93 [0] (~eboyer93@pool-71-185-65-59.phlapa.fios.verizon.net) 23.00.22 Join leavittx_ [0] (~lev@89.221.199.187) 23.04.48 *** Saving seen data "./dancer.seen" 23.13.57 Quit Thanatos (Ping timeout: 245 seconds) 23.15.32 Quit xnyhps (Ping timeout: 276 seconds) 23.19.02 Quit Maggux (Read error: Connection reset by peer) 23.20.20 Quit kevku (Quit: KVIrc 4.0.2 Insomnia http://www.kvirc.net/) 23.21.21 Quit krabador (Quit: Sto andando via) 23.24.19 Join sudoman [0] (97cce263@gateway/web/freenode/ip.151.204.226.99) 23.26.24 Join xnyhps [0] (~xnyhps@xnyhps.nl) 23.35.20 Quit dfkt (Quit: -= SysReset 2.53=- Sic gorgiamus allos subjectatos nunc.) 23.39.47 Quit bertrik (Ping timeout: 276 seconds) 23.40.17 Quit komputes (Read error: Connection reset by peer) 23.44.59 Join perrikwp [0] (~474cadb0@giant.haxx.se) 23.49.46 Join JdGordon [0] (~jonno@rockbox/developer/JdGordon) 23.56.35 Quit ender` (Quit: Shooting is not too good for my enemies. -- Evil Overlord List #4) 23.57.25 Join Thanatos [0] (~Nausicaa@c-71-239-58-153.hsd1.il.comcast.net)