--- Log for 30.07.104 Server: zelazny.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16p1 Started: 1 day and 21 hours ago 00.02.44 # amiconn: how's the mod? 00.03.14 # zeekoe: Still soldering (these 0805 smds are damn small beasts) 00.03.20 # :P 00.03.38 Join AciD [0] (~acid@longchamp44-1-82-67-133-87.fbx.proxad.net) 00.04.16 # smaller than this one? i made this: http://home.student.utwente.nl/r.teune/micpreamp.jpg 00.04.17 # :P 00.04.53 # whoops, you can forget the "i made this", copied a bit too much from the logs (it is true though) 00.07.23 Join edx [0] (edx@pD9EAA9FB.dip.t-dialin.net) 00.08.31 # Quite a bit smaller. That mic preamp seems to be made mostly of conventional parts (except the chip) 00.08.41 # yep 00.08.54 # Unfortunately I broke the solder pads of one of the leds :( 00.09.01 # that's really bad 00.09.19 # if it's so small, can you fix it? 00.09.24 # So I have to glue it into place, and wire it to the contacts 00.09.47 # ok 00.09.58 # (I have to wire anyway, since I have to put each of the 2 leds of either side in parallel instead of in series 00.10.37 # the white ones need higher voltage? 00.11.10 # you shouldn't be doing this kind of stuff at 00:10 am :) 00.12.45 # Yes, they need higher voltage. And no, 00:10 am is a good time to do such stuff ;-) 00.25.06 # It works!! :-)) 00.27.29 # cool 00.27.38 # you have white backlight now? 00.28.16 # and it only took you one and a half hours :P 00.29.09 # and my video is ready too 00.29.14 # after about five hours 00.29.40 # and 16 empty batteries 00.32.59 # oh boy 00.33.05 # it's even in sync 00.36.52 *** Saving seen data "./dancer.seen" 00.40.09 # http://arnold-j.bei.t-online.de/Rockbox/WhiteBacklight1.jpg and http://arnold-j.bei.t-online.de/Rockbox/WhiteBacklight2.jpg :)) 00.42.18 # nice :) 00.43.02 # the light seems to be brighter than [IDC]Dragon's 00.43.48 # This may be caused ba another backlight / ambient light brightness ratio when taking the photos 00.43.54 # s/ba/by/ 00.43.59 # yeah, brobably 00.44.52 # can you post a grayscale picture? 00.51.28 # http://amiconn.dyndns.org/WhiteBacklight3.jpg 00.52.07 # (Too bad my digicam has no macro capabilities) 00.52.41 # :) 00.52.47 # looks ghosty :) 00.53.04 # and you modded the two other leds too? 00.53.43 # I modded the 4 backlight leds only 00.55.01 # but the ready led seems white too 00.55.42 # The red led isn't active in any of my pics, it's only the backlight that shines through 00.56.39 # i guess the green led is a bit overillumanited and so it looks white 00.57.36 # Watching video is much more fun than before - I'm now able to distinguish very dark shades of gray :) 00.58.46 # cool 00.59.00 # but white leds are expensive i guess 00.59.25 Join midk [0] (~midk@c66-235-14-120.sea2.cablespeed.com) 00.59.27 # € 1.69 per led 01.00.08 # s/white leds/conrad 01.00.19 # yup 01.00.52 # I bought them at Schuricht. However, they sell 10 pieces minimum 01.01.18 # ok 01.01.28 # at my school i can order stuff from farnell 01.01.34 # So I have 6 leds left now, as I broke none (unlike I thoguht) 01.01.41 # ok 01.01.52 # so you can sell them :) 01.01.54 # s/thoguht/thought/ 01.03.59 # for school i had to solder some stuff once, varicap diodes 01.04.12 # only smd in a really small package was available 01.04.26 # i ordered 10, broke 7, and needed 2 :) 01.06.57 # haha! 01.07.00 # HAHAHA! 01.07.06 # * midk laughs wickedly 01.07.19 # mwahahaha 01.07.45 # ssh before i egg your house 01.08.04 # me? 01.08.20 # yes 01.08.23 # you 01.09.04 # ssh as in secure shell? 01.09.09 # shh. 01.09.17 # ok 01.09.23 # and what does egging a house mean? 01.09.55 # i throw raw eggs at your house 01.09.56 # it gets messy 01.10.28 # fine 01.10.36 # come here if you like 01.12.01 # have you already seen amiconn's 1337 archos mod? 01.12.08 # nope 01.12.39 # now i have :) 01.12.44 # nice!! 01.12.44 # WOW 01.13.25 # what's on the screen in #3? 01.14.38 # i asked for a grayscale picture 01.15.38 # a picture of a bus? :) 01.15.44 # no, an office 01.15.53 # ... 01.16.02 # well, it looked like an office 01.16.03 # it's a bus 01.16.10 # now i see it too 01.16.14 # midk: It's a part of an image showing a fire-brigade truck (or how that's called in English) 01.16.25 # ah 01.16.34 # zeekoe, how could you interpret that as an office? 01.16.38 # dunno 01.16.46 # you're weird/. 01.16.50 # i saw something like a chair and a bureau 01.16.57 # is bureau correct english? 01.17.09 # no, my eyes are bad 01.18.01 # i really thought of it as an office, but now i know it's a bus i can't figure how i've seen it before 01.18.30 # * midk stares at zeekoe 01.18.57 Join dstar5 [0] (Lee@ACC1395D.ipt.aol.com) 01.19.06 # my jukebox is here :) 01.19.07 # dstar5!!!! 01.19.12 # tri-vi-a! 01.19.15 # jukebox? 01.19.19 # archos 01.19.25 # archos? 01.19.25 # The original image is here: http://amiconn.dyndns.org/Feuerwehr.jpg 01.20.12 # aha! 01.20.23 # the drive in this one is REALLY quiet 01.20.39 # dstar5: what did you do to it? 01.20.59 # and it has the HD MP3 RECORDER written above the buttons, like the old blue recorders had 01.21.43 # i have HD MP3 RECORDER too 01.21.47 # but it isnt blue 01.21.50 # its blackish 01.22.18 # it is black 01.23.17 # the guy thta had it must have taken good care of it, no damage at all, and the little plastic sticker is still on the screen 01.24.04 # so... why all this excitement??? did i miss something?? 01.30.59 # did you buy a new recorder or so? 01.31.15 # on ebay 01.31.21 # ok 01.31.34 # recorder v1? 01.32.07 # yes 01.32.22 # i hope it is flashable 01.32.28 # :) 01.32.29 # never got one before? 01.32.34 # i am copying the dudes music on my HD incas ei want it 01.32.39 # then i am goign to reformat 01.32.41 # heh 01.32.42 # install rockbox 01.32.48 # and flash if i can 01.32.57 # then the long process of copying my msuic.... 01.33.13 # no i had a recorder before 01.33.45 # what is "dream weaver" 01.34.04 # he had it on the drive 01.34.15 # ok 01.34.19 # dream weaver? 01.34.25 # maybe dreamweaver 01.34.34 # that's an html editor 01.34.51 # weird 01.36.39 # ? 01.38.15 # so he didnt even format the drive before selling it..? 01.39.56 # no 01.40.10 # does not bother me... i like free msuic :) 01.40.14 # :P 01.40.18 # and it al appears to be nice quality 01.40.21 # what kind of music is on the drive? 01.40.22 # 224 kbs 01.40.25 # cool 01.40.33 # acustic mostly 01.40.38 # ok 01.41.02 # mostly live... 01.41.09 # too bad for the guy he never heard of rockbox 01.41.13 # i know 01.41.15 # lol 01.45.18 Join BlueChip [0] (~bluechip@cpc3-colc1-3-0-cust61.colc.cable.ntl.com) 01.46.22 # yo BC! 01.46.37 # yo d5 :) 01.51.51 # i dont like BlueChip 01.51.52 # bye 01.51.56 # :-P 01.52.02 # byee 01.52.04 # nah, just need to sleep 01.52.14 # see you 01.52.23 # later zeeker 01.52.30 # zeek_oe_ 01.52.39 # ZYKERR!?! 01.52.43 # like manatee 01.53.02 # zeeker. 01.54.32 # die 01.54.44 # zeekoe? 02.03.53 Join amiconn_ [0] (~jens@pD9E7F44B.dip.t-dialin.net) 02.04.52 Quit amiconn (Nick collision from services.) 02.04.53 Nick amiconn_ is now known as amiconn (~jens@pD9E7F44B.dip.t-dialin.net) 02.05.09 # i see amiconn has the situation under control. 02.05.18 # midk: Huh? 02.05.37 # the duplicate nicks 02.05.40 # never mind :) 02.06.01 # I just got disconnected by my provider (T-Online disconnects all users at least once per day) 02.06.22 # right. and you ghosted the other one so i said you had it under control.. 02.06.34 # Yep 02.07.25 Join Lee_ [0] (Lee@ACC69349.ipt.aol.com) 02.08.02 Quit dstar5 (Nick collision from services.) 02.08.16 Nick Lee_ is now known as dstar5 (Lee@ACC69349.ipt.aol.com) 02.08.28 # i see dstar5 has the situation under control. 02.10.35 # why does bash, uname, and this other thing always want to connect to the inter net when i start cygwin? 02.11.56 # take it you're using the full cygwin install 02.12.25 Quit zeekoe (Read error: 60 (Operation timed out)) 02.12.41 # yes 02.12.45 # atm 02.12.59 # Still no one tried Rombox on a v2 ? 02.13.10 # v1, unflashable, sorry 02.17.50 # ohh no 02.18.06 # flash: M=?? D=?? 02.18.26 # dstar5: unflashable :( 02.21.40 # well.. i do have a good chip in my old board... 02.21.49 # i not sure if i would want to replace it 02.21.56 # that chip is so small 02.23.17 # You should have some experience with smd soldering if you're going to do this 02.23.41 Quit mecraw ("Trillian (http://www.ceruleanstudios.com)") 02.23.56 # no smd soldering... 02.24.22 # Today I did the white backlight mod. It wasn't easy to solder those tiny beasts called smd leds... 02.24.52 # I even broke the soldering pads for one of the leds 02.25.13 # ill be back later 02.25.19 # time to play with my archos a bit 02.25.23 Quit dstar5 ("Leaving") 02.25.36 # I guess it's time to sleep now 02.25.48 # Nite all 02.25.53 # nite 02.26.11 Part amiconn 02.28.12 Quit edx () 02.29.01 Join tpelliott [0] (telliott@208-251-255-120.res.evv.cable.sigecom.net) 02.31.00 # is it possible to get "incompatible version" from plugins when you are using an AJZ and rocks from the same bleeding edge build? 02.31.32 # tpelliott, is it when you try to flash? 02.32.01 # It happened even when I rolo'd the AJZ 02.32.22 # right 02.32.25 # try erasing everything and unzipping your own "make zip" 02.32.28 # but when you play a ucl right? 02.33.44 # It happened when I played "rockbox.ucl" 02.34.04 # correct. i get the problem too. 02.34.15 # ah, flashing issue - forget my previous comment 02.36.35 # I have a Windows utility called "create.exe" that downloads the latest build and creates the ucl. I'm not sure who wrote it. Are you familiar with this? 02.36.55 # I think it may be out of date. 02.36.56 *** Saving seen data "./dancer.seen" 02.37.18 # it doesn't work for me. that means it's probably a problem 02.37.37 # ok. 02.37.41 # there a doc on cvs on my site which may help 02.37.51 # bc, it's a rockbox_flash problem/ 02.38.12 DBUG Enqueued KICK BlueChip 02.38.12 # 01 I have a Windows utility called "create.exe" that downloads the latest build and creates 01the ucl. 02.38.24 # cvs is likely a good solution 02.38.40 # i did get cvs 02.38.40 # just a half hour ago 02.38.40 # I have the same problem with the jpg viewer. Everything's up to date as far as I know. 02.43.31 Join zobo [0] (~erik@foxtail.org) 02.56.35 Join fifer- [0] (~Pickle@80.229.144.229) 02.57.27 # does anyone here know the debian package that contains sh-elf-gcc? 02.58.18 # the linux guys are all out at the moment, might be quicker to compile it yourself? 02.58.55 # follow the cross-compiler docs/ 02.58.57 # thats the thing, i have been on google for about 30mins looking for info on it 02.58.59 # :/ 02.59.26 # thx midk 02.59.35 # np 02.59.41 # remember the export PATH command 02.59.52 # will do :) 02.59.53 # thx 03.00.03 # np 03.00.14 # you're cooking tonight mk 03.01.28 # did i really just beat you to an answer there? ;) 03.33.05 Quit AciD ("Hiroshima 45, Tchernobyl 86, Windows 95") 03.45.42 Join AciD [0] (~gni@longchamp44-1-82-67-133-87.fbx.proxad.net) 03.50.45 # bbl 03.50.49 Quit midk ("Leaving") 03.50.55 Quit fifer- (Read error: 60 (Operation timed out)) 03.58.51 Part tpelliott 04.00.59 Part BlueChip 04.29.39 Quit scott666 (Read error: 104 (Connection reset by peer)) 04.29.39 Quit NibbIer (Read error: 104 (Connection reset by peer)) 04.29.47 Join scott666 [0] (~scott666@c-24-245-58-48.mn.client2.attbi.com) 04.36.59 *** Saving seen data "./dancer.seen" 04.45.31 Nick AciD is now known as AciD` (~gni@longchamp44-1-82-67-133-87.fbx.proxad.net) 05.05.14 Quit AciD` (".L") 05.46.55 Join dstar5 [0] (Lee@ACC49DAA.ipt.aol.com) 05.47.41 # hey scott666 05.50.37 Join midk [0] (~midk@c66-235-14-120.sea2.cablespeed.com) 05.51.15 # hey midk and dstar5 05.51.24 # yo scott 05.51.39 # futurama is fun to watch on rockbox 05.51.55 # i noticed the vu meters look bad in .8 ratio 05.51.59 # i need to fix them 05.52.16 # i would have never let it go if iknew they looked so bad 05.52.26 # thye look god in square on simulator 05.52.31 # s/god/good 05.52.38 # s/thye/they 05.52.49 # s/in/and 05.52.53 Nick scott666 is now known as scott|brb (~scott666@c-24-245-58-48.mn.client2.attbi.com) 05.53.47 Quit midk (Client Quit) 05.53.51 Join midk [0] (~midk@c66-235-14-120.sea2.cablespeed.com) 05.55.16 # dstar5, perhaps we should collaborate on another update.. 05.55.21 Join Treyqae [0] (~Treyqae@adsl-8-45-253.mia.bellsouth.net) 05.55.46 # remove the annoying and wastefull mini meters! 05.56.09 # ..or if you feel that putting down work is needed, we shall not 05.57.18 # they're purely cosmetic - i also included an on/off option, if you noticed 05.57.29 # they are useless 05.57.38 # i was thinking of a decay screen redesign, and perhaps an addition of a new mode or two 05.57.44 # seriously. shut up. 05.58.13 # scott|brb: dont you think mini meters are annoying and useless? 05.59.29 # they're purely cosmetic if you think that gap ther is bad, fine, i will resize the needles and all 05.59.43 # but minimeters are no good solution 05.59.54 Nick scott|brb is now known as scott666 (~scott666@c-24-245-58-48.mn.client2.attbi.com) 05.59.58 # dstar5, i was trying to be friendly and initiate another update.. probably with a lack of minimeters. 06.00.10 # but if you really feel you need to complain about a small feature that is easily shut off, fuck it. 06.00.14 # remove the annoying and wastefull mini meters! 06.00.14 # ..or if you feel that putting down work is needed, we shall not 06.00.20 # so let's not. 06.00.22 Part Treyqae 06.00.34 # yes, it's my work, if you do feel like putting it down that's fine, we don't have to do an update./ 06.01.00 # sorry for being rude... but still 06.01.17 # i'm quite tired of your complaints 06.01.22 # i said i did not like mini meters, but you did not discuss, and left them anyway 06.01.30 # what's your point? 06.01.34 # whoever merged em liked em 06.01.36 # that's what matters 06.02.38 # no i dont think he even loked at the code (it was [IDC]Dragin i believe btw 06.02.50 Nick scott666 is now known as scott|war3 (~scott666@c-24-245-58-48.mn.client2.attbi.com) 06.03.01 # doesn't matter, your update that removed the functionality wasn't merged... 06.03.03 # what does that say? 06.03.04 # also see me mail in the list: charging while on usb 06.04.37 # doesn't matter, your update that removed the functionality wasn't merged... 06.04.37 # what does that say? maybe no one has looked at them? 06.04.53 # that's fine, then why remove them if nobody cares about them? 06.04.56 # they must go unnoticed. 06.05.17 # whatever, i'm done with this conversation. 06.05.29 # ok shut up you only want mini meters in because you made them 06.05.45 # i think that's the reason YOU don't want them in - because you didn't code them 06.05.47 # dont fuck with whats there 06.05.50 # no 06.06.00 # i had no problems with anythig else you did 06.06.13 # because i didn't do much else 06.06.16 # i just asked you not to do the minis adn you would not discuss and did anyway 06.06.18 # you had a problem with my decay screen 06.06.39 # excuse me I WROTE THE DECAY SCRENN 06.06.44 # why should i care if you don't like my code? it got in, and your removal of them didn't.. so.. 06.06.48 # s/SCRENN/SCREEN 06.06.51 # i wrote the decay screen, you updated it 06.07.02 # no 06.07.07 # i wrote it 06.07.10 # code stealer. 06.15.01 Join NibbIer [0] (~nibbler@port-212-202-78-112.dynamic.qsc.de) 06.15.02 Quit dstar5 (Read error: 104 (Connection reset by peer)) 06.37.01 *** Saving seen data "./dancer.seen" 07.09.17 Join LinusN [200] (~linus@labb.contactor.se) 07.09.18 Quit NibbIer (Read error: 104 (Connection reset by peer)) 07.10.17 # hey LinusN 07.10.28 # i think tonight i'll get breakout fixed up 07.15.03 # wow 07.45.50 Join elinenbe [0] (trilluser@207-237-224-177.c3-0.nyr-ubr1.nyr.ny.cable.rcn.com) 08.03.23 Quit scott|war3 (Read error: 110 (Connection timed out)) 08.19.05 Join NibbIer [0] (~nibbler@port-212-202-78-112.dynamic.qsc.de) 08.33.28 Join CourtesyFlush [0] (~lsktst@24-116-138-164.cpe.cableone.net) 08.34.36 # Hello? 08.34.39 # hi 08.34.40 # hi hi hi 08.34.45 # I have a problem 08.34.51 # shoot 08.34.53 # i see LinusN is on the ball tonight 08.35.07 # "this morning" you mean :-) 08.35.08 # :) 08.35.29 # "afternoon" then 08.35.30 # my last day before my well-deserved vacation 08.35.32 # When I turn on my Recorder v2 It starts to load the OS then it fades out doesnt turn on 08.35.34 # deal 08.35.39 # aw, we'll miss you 08.35.47 # And when its pluged into the usb it turns off after a whle 08.35.51 # CourtesyFlush: battery status? 08.35.52 # Im sure its charged 08.36.24 # the batteri may be dead 08.36.25 # But I am charging it right now hoping it will work after a while 08.36.40 # or the battery connections may be bad 08.36.40 # But I have a flight tomorrow and I dont want to be with out it 08.36.52 # It could be that 08.37.02 *** Saving seen data "./dancer.seen" 08.37.10 # Im not sure if im using the original power cord thing 08.37.17 # oh 08.37.20 # voltage? 08.37.23 # Im not sure 08.37.25 Join edx [0] (edx@pD9EABC48.dip.t-dialin.net) 08.37.27 # Ill check 08.37.38 # general rule, if you don't know the voltage, don't plug it in 08.37.47 # you may kill it 08.37.48 # 4.5 08.37.52 # too low 08.37.57 # Is that bad though? 08.38.06 # Did it kill my battery? 08.38.12 # probably not 08.38.18 # you need 6V 08.38.18 # hmm 08.38.21 # Alright 08.38.26 # That will help a lot 08.38.27 # Thanks 08.38.31 # you're welcome 08.38.38 # I guess I better try to find the original power cord 08.38.43 # indeed 08.39.13 # Or 08.39.24 # Is there a way to configure it so it will like the 4.5 volt? 08.39.34 # midk: i will probably drop in here from time to time, can't stay away, you know 08.39.39 # CourtesyFlush: no 08.40.00 # LinusN, good... how long'll you be gone? 08.40.04 # week? few weeks? 08.40.06 # 4.5V should be enough to charge the battery, but it will take AGES 08.40.11 # 4 weeks 08.40.15 # i've used a 4.5 adapter- didn't do much 08.40.19 # woo, yay... 08.40.26 # by then breakout could be done 08.40.29 # ..... nah. :) 08.40.35 # midk: i believe it when i see it 08.41.03 # CourtesyFlush: you may be better off charging it via the USB cable 08.41.07 # eh, still have to implement .. hm... 08.41.10 # it's 5V 08.41.51 # Ok 08.41.51 # it still takes a lot longer than with the original charger 08.41.56 # Ok 08.42.03 # no longer than 5 hours? 08.42.09 # i dunno 08.42.18 Join Christi-S [0] (~Sarah@client-427-p-2-lns.winn.dial.virgin.net) 08.42.24 # Christi-S: welcome 08.42.34 # Morning, Linus. 08.42.39 # sorry about your dad 08.42.52 # 'S OK. Against all odds he's still alive. 08.43.11 # Not quite sure how he pulled off restarting his kidneys but I'm pleased. 08.43.22 # i'm glad 08.43.39 # Me too. :) 08.43.41 # how is he then? 08.44.21 Join amiconn [0] (~jens@pD9E7F44B.dip.t-dialin.net) 08.44.26 # Very ill. But slowly getting better. If he could stop feeling sick and eat something it would be quicker. 08.44.41 # Still, we'll see how things go. 08.45.03 # i hope it turns out well 08.45.13 # CourtesyFlush: plane leaves in 5 hours? 08.45.17 # Trouble is he'll doubtless still have the cancer, so that's unlikely, but I live in hope. 08.45.47 # Well I leave for airport in 5 hours about 08.45.58 # more like 6 08.46.14 # Anyway, Rockbox. I'm thinking about implememnting "file move" as a plugin, with added functionality for .m3u files so that it changes the paths in them when it moves them. 08.46.17 # CourtesyFlush: then go look for the charger, and charge in with USB in the meantime 08.46.29 # Does that sound like a sensible way to do it. 08.46.38 # Christi-S: you're nuts :-) 08.47.03 # alright 08.47.13 # actually, we should start with implementing file move in the FAT driver first 08.47.14 # Well, yes, but it didn't strike me as that difficult to do. Maybe I'm underestimating the difficulty. 08.47.29 # it's not hard, just kidding 08.47.37 # *laugh* 08.47.38 # hm, someone asked about plugins howto on the list... 08.47.43 Ctcp Ignored 1 channel CTCP requests in 0 seconds at the last flood 08.47.43 # * midk has fingers twitching to write one 08.47.50 # but how will it find the playlists? 08.47.59 # i could document the whole process of rewriting clock from scratch 08.48.01 # * Christi-S points midk in the direction of the wiki. 08.48.26 # midk: played with the split editor yet? 08.48.27 # Well, it'd only allow moving one file at a time. 08.48.31 # * midk points Christi-S in the way of ... the... store. 08.48.37 # LinusN, i tried, it was a bit confusing 08.48.51 # i couldn't get it to split right 08.48.53 # Christi-S: i mean, searching the hard drive for playlists is likely to take some time 08.48.59 # there needs to be a provided doc or something 08.49.08 # hi all 08.49.20 # hey amiconn 08.49.24 # Oh, right. My idea would be to have it as a viewer. 08.49.29 # midk: http://rockbox.haxx.se/twiki/bin/view/Main/PluginSplitEdit 08.49.34 # So you'd find the playlist you want to move. 08.49.41 # manually. 08.49.57 # aha, you mean moving *playlists*, not mp3 files 08.50.23 # * Christi-S nods. 08.50.27 # * LinusN cleans his glasses 08.50.44 # hi amiconn 08.50.46 # I create playlists with Rockbox, but I don't really want them all hanging about in the root. 08.51.22 # LinusN: Any news concerning the problematic boxes (optimized ata & Hitachi DK23DA)? 08.51.25 # Christi-S, they save in the "current dir" when you choose save them.. 08.51.37 # amiconn: no news... 08.51.39 # midk: Not on my box. 08.51.40 # anyone considered a dual browser setup like the av3x0 for copying/moving files? 08.51.55 # Christi-S, well you can specify a dir with the keyboard 08.52.07 # ie, enter /music/playlist.m3u and it will save it in /music 08.52.10 # True, but you have to specify it every time. 08.52.12 # (yes, i'm clever) 08.52.21 # Ah, but are you big? 08.52.28 # what about including the current dir in the name? 08.52.33 # Christi-S, sure 08.52.40 # midk: "Create playlist" doesn't let you choose where to put it 08.52.51 # no, saving a dynamic one 08.52.51 # Big *and* clever - nice. :) 08.53.02 # you get to name it.. when you name it you can specify a path manually. 08.53.11 # including the path automatically sounds like a good idea. 08.53.36 # * Christi-S wonders if adding browse support to the file naming dialogue might be another way to go. 08.53.44 # midk: dual browser, like side-by-side? 08.53.47 # So many options, so little clue. :) 08.54.02 # LinusN, yes, half of the screen is devoted to one and other half to the other 08.54.20 # you can highlite a file on the left, go to the destination on the right and maybe on+play-> move (or copy) 08.54.22 # would be really wonderful on a Player... :-) 08.54.27 # er..... :) 08.54.30 # recorders only. 08.54.54 # midk: so you devote a whopping 56 pixels for each browser 08.55.03 # lots of scrolling... 08.55.07 # LinusN, if i had 320 to shell out i would 08.55.09 # :) 08.55.17 # well.. what about just.. 08.55.27 # You could always do a vertical split. 08.55.33 # on+play, move(or copy), then you get a browser to pick where you want to move it to 08.55.35 # sounds better 08.56.23 # * Christi-S also wonders if alternative playlist formats are worth considering. 08.56.32 # why? 08.56.51 # The way m3u handles directories is annoying, to say the least. 08.57.01 # Don't know if there's a better solution. 08.57.24 # what's wrong about the dir "handling"? 08.58.29 # Well the fact that you can't easily move a playlist (the problem I'm actually trying to solve.) 08.59.13 # if you create the list with an absolute path, it will work anywhere 08.59.57 # * Christi-S nods. Maybe the answer is to patch Rockbox's creation code so it uses absolute paths. 09.00.13 # (Or make it a configuration option. Some people like relative paths.) 09.00.34 # absolute paths are good when you move around the playlist file 09.00.45 Quit CourtesyFlush ("Read error: Connection reset by peanuts") 09.00.53 # er 09.00.56 # relative paths are good when you move around the directory 09.00.59 # i thought linus just said.. 09.01.16 # "absolute paths are good when you (Connection reset by peanuts)" 09.01.19 # hmm, never mind.. 09.01.25 # Swings and roundabouts. Hmmm. 09.02.29 # I think what I'd propose doing is making Rockbox write absolute paths by default with relative paths as a playlist option. Does that sound like a sensible thing to implement? 09.03.03 # (If we're going to implement move/copy, it should really be in the core code rather than a plugin, I think.) 09.04.39 # I agree that an option to choose between relative and absolute paths in playlist creation would be nice. I do also use both types of playlists 09.04.50 # the "Create playlist" option creates absolute paths today 09.05.17 # so moving around the playlist is easy today 09.05.22 # Hmmm. What's the difference between that and "Save current playlist"? 09.06.18 # Christi-S: Especially "move" should pe implemented in the fat driver (way faster than using copy, then delete source from a plugin) 09.06.45 # * Christi-S nods to amiconn. 09.07.13 # that's why i wrote "actually, we should start with implementing file move in the FAT driver first" :-) 09.07.47 # Christi-S: "save current playlist" saves the entire dynamic playlist contents to a new playlist file 09.07.57 # with inserted files etc 09.08.28 Join Christi-S- [0] (~Sarah@client-425-p-2-lns.winn.dial.virgin.net) 09.08.29 # i guess i have a good vacation project then, implementing file/dir move in the fat driver 09.08.56 Mode "#rockbox +o LinusN " by ChanServ (ChanServ@services.) 09.09.02 Kick (#rockbox Christi-S :LinusN) by LinusN!~linus@labb.contactor.se 09.09.32 # I think I need to have a look at "Create new playlist" then document it better. 09.09.46 # Christi-S-: good 09.10.14 # Always nice to discover there's no need to do something. ;) 09.10.25 # i made quite a few changes while you were gone, so you have lots of nice catching up to do 09.10.54 # I don't think I'll do that till we have a feature freeze. 09.11.00 # good idea 09.11.18 # Best not to run after a moving target. 09.11.36 # * Christi-S- thinks ROMbox looks quite exciting. 09.12.30 # Oh, Linus, can you sub christi@chiark.greenend.org.uk to the cvs list for me? The online form doesn't seem to be working for me. 09.13.37 # it doesn't work? 09.13.58 # It's probably a side effect of the enormous spam-trap on that address. 09.15.24 # * LinusN just tried the form 09.16.01 # I did it a while back and got a "Your request has been received" screen but no further response. 09.16.20 # * Christi-S- tries again. 09.17.15 # Right. I just resubmitted the request. 09.18.24 # you need to respond from that exact email address 09.18.59 # I have email from the server this time. That's an improvement. 09.19.46 # Right - now on it. Irritating how it always works as soon as I mention the problem. ;) 09.19.58 # :-) 09.20.07 # i see you in the database now 09.20.14 # Cool. 09.20.34 # prepare to be swamped in cvs commits :-) 09.20.44 # * Christi-S- nods. 09.21.11 # hey all, is the "Shut down" menu option really necessary on the recorder? 09.21.43 # * Christi-S- wonders what pet project to work on next - better LiOn battery level indicator or improvements to the FM radio. 09.21.59 # anything particular in mind? 09.22.17 # is the lion indicator that bad? 09.22.41 # Timed recording is what I'd particularly like, since I always forget to tune into radio shows. 09.23.59 # Of course that involves messing around with the rtc. 09.24.32 # yup 09.25.00 # Another thing I'm vaguely considering is seeing if I can pick up the station information transmission. Not sure if that's doable though. 09.25.29 # RDS? 09.25.38 # * Christi-S- nods. 09.25.47 # not possible 09.25.52 # Shame. 09.26.06 # archos removed the RDS received from the PCB 09.26.09 # receiver 09.26.18 # I had a feeling it might be wishful thinking. 09.26.36 # there are pads for mounting a RDS receiver chip 09.26.45 # Surely the RDS info is encoded in the FM output somewhere though? 09.26.56 # yes it is 09.27.03 # but you need a decoder to extract it 09.27.27 # * Christi-S- was wondering if it'd be possible to decode in software. 09.27.31 # nope 09.27.51 # Too processor intensive? 09.28.32 # absolutely, and there is no analog FM rx data available to the cpu 09.28.45 # only the demodulated sound 09.29.09 # Oh, right. And the appropriate waveforms aren't in the demodulated sound? 09.29.19 # nope 09.29.31 # Bugger. 09.29.39 # and even if archos had mounted the RDS chip, the cpu would have too much to do to keep up 09.30.01 # Ah well, it was a nice idea. 09.30.10 # yup 09.30.42 # In which case I'll probably look at LiOn charge indication first, since that's a smaller project than the timed recording. 09.31.03 # Of course I'm open to other suggestions. 09.31.06 # Christi-S-: is the discharge curve wrong in the power management code? 09.31.54 # It doesn't seem to work well for me. Plus I'd like more detailed display (time remaining before full charge - pretty v2 'charging' screen). 09.32.37 # ooooh 09.32.51 # that's a tough one 09.33.05 # how much playtime do you get? 09.33.19 # about 10 hours, I think. 09.33.28 # With a 2800mAh battery. 09.33.43 # (All my MP3s are encoded at 256Kb) 09.34.00 # * amiconn wonders why "rockbox info" only says "charging" while the v1's charging screen does display battery percentage 09.34.45 # the battery percentage display in the charging screen should be removed 09.35.00 # it's only fooling the user into thinking that the battery is full 09.35.06 # while it isn't 09.35.17 # * Christi-S- nods. 09.35.36 # Christi-S-: do you have an idea how to calculate the remaining charge time? 09.35.44 # I tend to get a steep initial charge which then drops to a shallower one somewhere between 3 and 4 volds. 09.35.57 # * amiconn thinks the percentage display in the charging screen is a good thing 09.36.15 # Well I was going to look up the chemistry of LiOn batteries and see if that gave me any ideas. 09.36.36 # (I tend to find stuff I don't know much about to be more interesting to tackle.) 09.37.02 # On the v1, there is a similar problem with the percentage display when discharging, since the discharge curve does depend on the type of cells 09.38.10 # While the percentage seems to be pretty correct for the original Archos supplied 1500 mAh cells, that isn't the case with my 2200 mAh Ansmann cells 09.38.27 # calculating remaining cell energy is a whole science in itself 09.39.31 # for example, look at this: http://www.maxim-ic.com/appnotes.cfm?appnote_number=526 09.39.32 # For these, the battery percentage is usually displayed too low 09.39.42 # I think improvement on the current results ought to be possible. I think redoing the model based on theoretical battery chemistry would be worth a try. 09.40.14 # Christi-S-: that is possible on the FM/V2, but really hard on V1 09.40.46 # since it varies a lot between brands and capacities 09.41.16 # we need to find out the chemistry of the FM/V2 battery to begin with 09.41.41 # * Christi-S- nods. Most of the work on battery time was done on the v1 - looking at revising it for the V2 seems like a nice idea. 09.42.00 # The battery display could (try to) auto-calibrate itself, since rockbox does have the info when the backlight, hd etc are switched on/ off, so the power consumption is roughly known 09.42.27 # Linus: Possibly we can do this empirically by writing charge/discharge info to a file. 09.42.47 # i assume that the fm cells have a graphite electrode 09.42.54 # The exception is of course usb mode - rockbox doesn't know whether the hd is on or off then 09.43.18 # we do, but we discard the battery measurements when the HD is on 09.43.27 # ah, surry, we don't 09.43.38 # (know when it's on) 09.44.21 # linus - that's probably a place where I can start then - buffering those values. 09.44.27 # btw, we should probably always activate the charger when entering usb mode 09.45.11 # Do we not? 09.45.31 # the charging code needs revising, and he first step would be to increase the sample rate, from 1 sample/min to perhaps 1 sample/s 09.46.20 # * Christi-S- nods. I'll have a look later today. 09.48.24 # * Christi-S- is beginning to think timed recording would actually be the simpler project. 09.48.46 # also read docs/CHARGING_ALGORITHM 09.49.29 # Thanks. Will do. 09.50.57 # amiconn: the power management code tries to compensate for hard drive activity, but not for other stuff, like backlight 09.53.10 # Right - see people later. 09.53.12 Quit Christi-S- ("If I were actually witty, this quitline would be funny.") 10.11.50 # amiconn: what do you think about redefining the scroll speed setting from Hz to ms/step? 10.11.50 Quit NibbIer (Read error: 104 (Connection reset by peer)) 10.12.25 # /me chimes in with, "that was my idea!" 10.12.38 # midk: yes 10.12.46 # see,, he agrees with me 10.13.00 # how were you planning to do it, assuming you were to do it? 10.13.40 # i think Hz is a better unit, but the HZ granularity make the Hz->ms calculation very coarse 10.14.06 # wasting precious config block bits, and annoying the user 10.14.20 # what about a different sleep, newsleep(int ms) 10.14.43 # midk: the kernel has only 10ms accuracy 10.14.57 # dah 10.15.08 # increasing the accuracy will affect performance 10.15.22 # so how were you planning to do it? 10.15.40 # the setting will be in 10ms steps, of course 10.15.53 # http://psyco.yi.org:8042/alien_bug/alien_bug1.jpg 10.15.54 # that'd suck... 10.16.01 # anybody know what that is? 10.16.18 # absolutely no idea 10.16.32 # looks like a grasshopper to me 10.16.35 # heh 10.16.48 # PRAYING MANTIS 10.16.56 # midk: what will suck? 10.17.04 # 10ms steps 10.17.13 # well its about 2" long 10.17.13 # why? 10.17.19 # i may be able to live with 10ms.. not 20, or 30 - if that's what you mean 10.17.20 # and i dunno 1/2" fat 10.17.33 # 10ms until the next step takes place? 10.17.46 # yes, that's 100Hz 10.18.01 # then what's 20? 10.18.08 # or actually closer to 4.5cm x 1cm 10.18.08 # 50Hz 10.18.09 # heh 10.18.13 # and what's 3 then? 10.18.18 # ze: what is it? 10.18.20 # do the math 10.18.28 # 100/30 10.18.42 # what's the point then? that's just as bad as "XX Hz" 10.19.04 # midk: i dunno, i just found it on the floor in our garage 10.19.14 # midk: the point is that it's annoying that 25Hz an 26Hz gives the same speed 10.19.54 # hmm 10.20.27 # the Hz calculation gives the same sleep() value for a lot of the Hz values 10.20.35 # why don't you just write something of a linear scale for the speed function? 10.20.57 # do you speak english? 10.20.58 # whatever it is, i think it's injured.. and it was tangled in cathair and fuzz when i found it (which you can see in the pic) 10.21.19 # we can only speel in 10ms intervals 10.21.21 # it slowly managed to mostly untangle itself, in short bursts of activity with long rests in between 10.21.21 # sleep 10.21.23 # heh 10.21.31 # 1 = 1, 2 = 2 ... 5 = 6, 6 = 7, 8 = 9, 9 = 10, 10 = 12, 11 = 13, 12 = 15, 13 = 17, 14 = 19.... 10.21.56 # what unit would that be? 10.22.24 # the end result would be put into "scroll_speed" 10.22.39 # so you could still use that into HZ/scroll_speed 10.22.43 # use that with* 10.24.00 # midk: i don't follow you 10.24.09 # well... 10.24.26 # write a linear scale is the simplest way to describe my idea 10.24.45 # take out the "hz" suffix and just have a speed number 10.24.56 # if the speed were 20 have the real scroll_speed 30... 10.24.56 # the main goal is that each step in the setting should give a different speed 10.25.05 # that's what the scale would accomplish 10.26.12 # sleep(HZ/scroll_times[scroll_speed]); 10.27.46 # char scroll_times[] = { 1, 2, 3, 5, 6, 8, 9, 11, 13, 15, 18, 20, 23, 26, 30, 34, 37, 42, 47, 53, 57, 64, 70, 76, 83 }; 10.27.52 # that's a crummy scale, but... :) 10.27.55 # just as an idea. 10.28.12 # how is that better than the ms scale? 10.28.46 # the ms scale loses speed increase as you make it faster, just like the Hz setting currently 10.29.00 # ah, good point 10.29.49 # still, i'd just invert the setting value 10.29.53 # my scale (or something like it) would ensure that the speed increments stay the same as your speed increases 10.30.41 # they won't 10.30.46 # i still think my approach would be simplest... hard to say, i'm not postive about what you're planning 10.31.06 # my scale sucks. but if you had a more accurate table it'd work well 10.31.49 # i'm afraid that we can't make the speed increments the same without significantly lowering the max speed 10.32.25 # why don't we just increase the limit to 50 then, and let the user take care of it? :) 10.33.00 # because i don't want any bug reports saying "scroll speed doesn't change" 10.33.51 # joke... hmm, well... you seem to understand it better than I, so i'll leave it to you 10.34.13 # so maybe it may better to use an anonymous scale, like you said, with 1 being the slowest and X being the fastest 10.34.38 # that sort of tied in with the linear scale idea 10.34.46 # yeah 10.34.51 # as you said it'd have to be lowered (the max speed) 10.35.03 # but i think that it'd still be quite fast? 10.35.07 # i didn't really do the math.. 10.35.16 # i'll give it a try 10.35.30 # the max shown speed would be lower - but the actual speed would be a lot higher - isn't this true? 10.35.39 # it wouldn't be as variable 10.35.54 # but the fastest will be 50Hz and the second fastest will be 33Hz 10.36.18 # then 25Hz etc 10.36.25 # the point would be that the steps would remain the same 10.36.40 # to the end user, "19" would be 33 and "20" would be 50 10.36.40 # they won't in the higher range 10.36.51 # well, a lot closer than the Hz scale 10.37.05 *** Saving seen data "./dancer.seen" 10.42.02 # ok so it's a jerusalem cricket 10.42.22 # which i guess are also referred to a "potato bugs" and "children of the earth" 10.42.22 # woooo 10.42.26 # potato bugs 10.42.27 # :) 10.42.37 # heh 10.42.42 # ah, so it is 10.42.50 # how'd you find out? 10.42.57 # googling 10.43.03 # ... 10.43.04 # eventually i came upon a pic/id 10.43.07 # "bug" 10.43.39 # yeah '"~insect" OR "~bug" california' 10.43.55 # http://math.uc.edu/~chalklr/My%20Photos/Wild%20Flowers%20and%20their%20Associates/006%20%20Potato%20Beetle.jpg 10.44.02 # potato beetle 10.44.03 # YAY. 10.44.31 # the 3rd image looked remotely similar, though i was fairly sure it wasn't it 10.44.42 # LinusN: (sorry, was away.) I think the scroll speed settings should stay to be defined in Hz. And imho increasing the upper limit to 25 Hz was unnecessary either. 10.44.50 # but it took me to a page full of bug pics people sent in to get identified 10.45.00 # and it was on there 10.45.01 # heh 10.45.30 # hmm no not a potato beetle heh 10.45.49 # :) 10.45.56 # amiconn, 10hz is a bit slow.. 10.45.59 # Everything above 8 Hz looks extremely blurry. You could have it increased to 15 Hz as this wouldn't have required additional settings bits 10.46.28 # amiconn: what step size do you have then? 10.47.09 # extremely blurry? 10.47.23 # i see virtually no blur even at about 20 10.47.35 # definitely not "extremely blurry" 10.47.59 # LinusN: Up to 15 Hz, only 12 Hz and 13 Hz give identical speeds 10.50.06 # ah, did anyone notice: the latest rockbox_flash returns "incompatible version" when used 10.50.09 # even with the correct daily 10.50.17 # unless it's been fixed quite recently 10.52.25 # works for me 10.53.51 # ok 10.55.36 # LinusN: Okay, if I use 1 pixel steps then it doesn't look that blurry even with 25 Hz 10.56.08 # Usually I use 3 pixel steps with my small font 10.59.06 # the point in the idea is a smaller step and faster speed, so it's smoother but just as fast 10.59.11 # (my idea at least) 11.07.15 # Both scales have problems: If you use Hz, step size is large with low settings (1 Hz <-> 2Hz) and gets finer with higher setting. With a time scale it's the other way round 11.09.45 # yes, but then we don't lie about the resolution 11.12.18 # With a simple time scale (10 ms step), if you want the speed to be settable as low as it is now, you need even more config bits 11.13.00 # yeah, we would need a table, like midk says 11.13.18 # my bra1n r t3h huge!!? 11.13.20 # i mean.. yeah.. 11.15.01 # Imho the table should roughly resemble an exponential scale, possibly doubling the delay time every 3 steps 11.15.08 # yup 11.15.27 # And the maximum speed should be limited to 50 Hz (2 ticks) 11.15.44 # i've got to reboot into linux - back in 5-7 minutes 11.15.48 # have to reinstall lilo too 11.16.01 Quit midk ("just STOP it arspy") 11.16.34 # i think 100 would be ok too 11.19.21 Join midk [0] (~midk@c66-235-14-120.sea2.cablespeed.com) 11.20.19 # LinusN: Exponential table with 3 steps for doubling (except in the beginning), resembling 10 ms steps: 11.20.46 # 2, 3, 4, 5, 6, 8, 10, 12, 16, 20, 25, 32, 40, 50, 64, 80, 100 11.23.43 # 100 Hz may require too much cpu power if there are a lot of scrolling lines 11.23.50 # yeah 11.27.46 # amiconn: looks good 11.28.46 # so we change it to 0=slowest .. 16=fastest 11.29.12 # mmm, would have been nice to fit in 4 bits... 11.29.41 # so maybe 1Hz is a bit slow... 11.37.25 Join [IDC]Dragon [0] (~d90a3255@reladm.kharkov.net) 11.37.37 # <[IDC]Dragon> hi guys! 11.37.47 # hey [IDC]Dragon 11.38.02 # <[IDC]Dragon> amiconn: congrats to your white backlight, saw that 11.38.31 # <[IDC]Dragon> looks blue-ish like mine 11.40.03 # <[IDC]Dragon> I used some (insulating) silver foil to form a "light guard", focuses more light into the LCD and reduces "light leakage" at the side of the case 11.41.44 # i ordered a bunch of leds, but i won't get them before i leave for vacation :-( 11.42.08 # [IDC]Dragon: Yeah, white backlight looks really nice. Unfortunately I broke the pads for one of the leds, so I had to glue it into place. 11.42.30 # I did already think about light shielding as well. What insulating foil did you use? 11.42.56 # <[IDC]Dragon> I scraped that from an ESD bag 11.43.50 # I think ESD bag foil isn't completely insulating, otherwise it wouldn't be of use against ESD 11.43.51 # <[IDC]Dragon> were your LEDs supposed to be warm-white? 11.44.35 # <[IDC]Dragon> amiconn: I coudn't measure any conductivity at the surface 11.44.50 # I used 0805 leds as I wanted, and I think 1206 would not fit into the cutouts of the plastic lcd frame 11.45.35 # The biggest problem is to solder them in vertically, especially as mine do have the metal contacts at the underside only 11.46.07 # <[IDC]Dragon> uh, yes. better use a kind which has the contact all around 11.48.33 # <[IDC]Dragon> something else: would you have enough space to distribute your ROMbox build together with the matching plugins? I think this is what some people are struggling with. 11.52.52 # The leds are supposed to be neutral white. I used these: http://www.schuricht.de/pdf/D05075.pdf 11.53.21 # For the plugins: That's why I suggest using the stated daily build 11.54.16 # <[IDC]Dragon> LinusN: do you know more about the RDS chip you've mentioned? 11.55.20 Join NibbIer [0] (~nibbler@port-212-202-78-112.dynamic.qsc.de) 11.56.58 # <[IDC]Dragon> LinusN: like, what chip is it, how do you know, is it really not feasible for the CPU? 11.57.35 # http://rockbox.haxx.se/docs/S1A0905X01.pdf 11.57.50 # pure guesswork 11.58.05 # it was likely to use the same manufacturer 11.58.21 # it fits in the socket 11.58.49 # the serial port input from the cpu goes to the tx pin of the chip 11.59.37 # (or was it the serial port...?) 11.59.42 # can't remember 11.59.56 # <[IDC]Dragon> I think the serial 12.00.21 # from what i saw back then, it would be a lot of work for the cpu 12.00.47 # <[IDC]Dragon> but perhaps not all the time 12.01.01 # <[IDC]Dragon> just until the station name is gathered 12.01.12 # RDS info changes all the time 12.01.35 # <[IDC]Dragon> but you don't have to follow that 12.02.24 # <[IDC]Dragon> 1187 bps doesn't sound too much data 12.03.36 # the synch detection would be a pain 12.04.57 # since the synchronization is done by examining the results from the error-checking 12.05.42 # <[IDC]Dragon> I'm not at all in the details of this serial stream 12.05.54 # <[IDC]Dragon> looks like you have 12.06.39 # i studied it, yes 12.06.58 # <[IDC]Dragon> and ordered a sample? ;-) 12.07.09 # i had a dream of getting me a chip and get it to work 12.07.35 # <[IDC]Dragon> lunch time 12.14.14 Join lImbus [0] (~manuel@kernel.cycos.net) 12.16.57 # i once had a dream that people complained about my clock on the mailing list. 12.17.05 # it was really more of a nightmare :_ 12.17.07 # :)* 12.37.08 *** Saving seen data "./dancer.seen" 12.46.34 Part LinusN 13.16.49 Quit NibbIer (Read error: 104 (Connection reset by peer)) 13.20.20 Nick midk is now known as midk|slepe (~midk@c66-235-14-120.sea2.cablespeed.com) 13.20.23 Nick midk|slepe is now known as midk|sleep (~midk@c66-235-14-120.sea2.cablespeed.com) 13.20.30 # nite evb 13.20.54 Join Fifer- [0] (~FIfer@80.229.144.229) 13.51.45 # * midk|sleep is away: sleeping 14.37.09 *** Saving seen data "./dancer.seen" 14.39.13 Join AciD [0] (~gni@longchamp44-1-82-67-133-87.fbx.proxad.net) 15.01.21 Join NibbIer [0] (~nibbler@port-212-202-78-112.dynamic.qsc.de) 15.08.51 Join Smooth [0] (909510b8@ACBD9015.ipt.aol.com) 15.08.54 Quit Smooth (Client Quit) 15.22.45 Quit AciD (".L") 15.23.30 Join AciD [0] (~gni@longchamp44-1-82-67-133-87.fbx.proxad.net) 15.24.25 Quit [IDC]Dragon ("no fate but what we make (EOF)") 15.25.28 Quit AciD (Client Quit) 15.28.22 Join AciD [0] (~gni@longchamp44-1-82-67-133-87.fbx.proxad.net) 15.57.11 Quit Fifer- (Read error: 104 (Connection reset by peer)) 16.37.12 *** Saving seen data "./dancer.seen" 17.14.25 Quit lImbus (Remote closed the connection) 17.27.44 Join scott666 [0] (~scott666@c-24-245-58-48.mn.client2.attbi.com) 17.39.17 Join Smooth [0] (~909510b8@ACBD658E.ipt.aol.com) 18.04.41 Quit AciD (Read error: 104 (Connection reset by peer)) 18.22.29 Join AciD [0] (~gni@longchamp44-1-82-67-133-87.fbx.proxad.net) 18.24.07 Join dbob [0] (jus@ACD2F847.ipt.aol.com) 18.37.14 *** Saving seen data "./dancer.seen" 18.48.03 Join zeekoe [0] (~zeekoe@ip51cc69f6.adsl-surfen.hetnet.nl) 18.48.58 Join scott666_ [0] (~scott666@c-24-245-58-48.mn.client2.attbi.com) 19.06.23 Quit scott666 (Read error: 110 (Connection timed out)) 19.35.32 Join Fifer- [0] (~FIfer@80.229.144.229) 19.36.00 # hi, i am using the 2.6.7 kernel and i am running debian. i have compiled usb-storage etc but cannot mount /dev/sda1 19.36.02 # any ideas? 19.43.58 Quit Fifer- ("Leaving") 20.14.32 Quit NibbIer (Read error: 104 (Connection reset by peer)) 20.20.50 Quit Smooth (Read error: 104 (Connection reset by peer)) 20.23.05 Quit zeekoe (Read error: 60 (Operation timed out)) 20.37.17 *** Saving seen data "./dancer.seen" 21.56.22 Nick midk|sleep is now known as midk (~midk@c66-235-14-120.sea2.cablespeed.com) 21.58.30 Join NibbIer [0] (~nibbler@port-212-202-78-112.dynamic.qsc.de) 22.08.15 Join deathsc0ut|Gratz [0] (none@pD9EE5CF2.dip.t-dialin.net) 22.08.25 DBUG Enqueued KICK deathsc0ut|Gratz 22.08.25 # 15H14ello everybody 15:14) 22.08.35 # hi there 22.08.54 # Mh... I came here to ask a question aaand well 22.09.26 # I built a new hard disk into my AJBR formated it to Fat 32 and now I plugged it into my USB Port 22.09.34 # But my damn win xp doesnt want to recognize the drive 22.09.36 # in the explorer 22.09.53 # That´s crazy because the jukebox seems to be ok with the new hard disk 22.10.12 # how did you format it? 22.11.46 # With some partitioning program 22.11.51 # similar as partition magic 22.11.55 # and whatsoever there is 22.12.03 # on your computer, then 22.12.07 # jep 22.13.15 # I already tried to delete all USB drivers, because before I did that 22.13.27 # windows said something in my task bar like Drive not found 22.13.29 # well that's why it wouldn't work 22.13.36 # if you took out your usb drivers for it. 22.13.51 # mh I installed them again 22.13.54 # 15:14) 22.14.07 # Now it doesn´t say Drive not found anymore 22.14.12 # but it still wont work 22.14.21 # you know how to get into device manager, right? 22.14.27 *** Alert Mode level 1 22.14.27 # right 15:14) 22.15.00 # is there anything listed under "unknown devices"? 22.15.57 *** Alert Mode level 2 22.15.57 # 15N14ope I dont think so... I already checked there and also checked with automatic search 22.16.09 # for hardware which hasnt been installed 22.16.24 Join [IDC]Dragon [0] (~idc-drago@pD951281B.dip.t-dialin.net) 22.16.32 # maybe idc would know 22.16.40 # what sort of hardware was it? 22.17.02 # <[IDC]Dragon> know what? 22.17.12 # it´s a hitachi Travelstar 40 gigs 22.17.25 # having trouble getting xp to recognize his archos recorder with a new hard drive 22.17.31 # actually it´s called Hitachi DK23FB-40F 22.18.03 # <[IDC]Dragon> I recommend Paragon to format it 22.18.14 # <[IDC]Dragon> the free demo version is fine 22.18.27 *** Alert Mode level 3 22.18.27 # 15O14h 15H14e 15H14e 15H14e 22.18.38 # I looked damn long for some program which worked for me 22.18.50 # and then I found that program which was made by Paragon 22.18.56 # but I couldn´t use anything in the demo 22.19.05 # but afterall I found some version which worked 22.19.13 # so I used paragon 22.19.21 # Right now I mounted the drive with that program 22.19.26 # probably that helps somehow 22.19.38 # <[IDC]Dragon> I used the Paragon demo, maybe they meanwhile crippled it some more? 22.19.51 *** Alert Mode level 4 22.19.51 # 15Y14eah 15y14ou couldn´t use anything 22.20.47 # hmmmm 22.20.56 # HAAAA 22.21.02 # I have a solution 22.21.03 *** Alert Mode level 5 22.21.03 # 15:14) 22.21.14 # I can copy files on my JB by mounting it 22.21.16 *** Alert Mode level 6 22.21.16 # 15:14) 22.21.43 # just copied a folder and it works.... but it would still be good if it would be recognized normally 22.23.11 # Hm... does anybody else has an idea how the AJB can be shown in the explorer? 22.24.54 # Well ok i will go... it works quite well that way... 22.24.58 # thanks for everybody helping me 22.24.59 *** Alert Mode level 7 22.24.59 # 15S14ee 15Y14a! 22.25.04 # *waves* 22.25.11 Quit deathsc0ut|Gratz ("« Ë×Çü®§îöñ » Info-[v9.4.22]- Released-[August 19, 2002]- Channel-[#Excurs") 22.35.00 *** Alert Mode OFF 22.36.11 # <[IDC]Dragon> amiconn: do you read? 22.37.18 *** Saving seen data "./dancer.seen" 22.53.01 Join Guest [0] (jirc@64.116.183.131) 22.54.49 Join zeekoe [0] (~zeekoe@ip51cc69f6.adsl-surfen.hetnet.nl) 23.05.26 Quit [IDC]Dragon () 23.15.36 Quit Guest ("Leaving") 23.26.10 # hi 23.26.29 # anyone knowing where the usb screenshotting is done? (which source file?) 23.26.47 Join LinusN [200] (~linus@labb.contactor.se) 23.26.53 # apps/misc.c 23.27.05 # hm... already looked at it 23.27.08 # let's look again 23.27.56 # the boundary checking is done (in etchasketch) :) 23.28.05 # :-) 23.28.05 # whew, what a lot of work that was :P 23.34.42 Part LinusN 23.35.50 # zeekoe, wish me to help you implement a "move around" mode? 23.36.16 # move around? 23.36.24 # without drawing. 23.36.40 # ok 23.36.45 # that's cool 23.36.49 # but i think i can do that 23.36.55 # heh, good luck 23.36.57 # once did it in Ti-Basic 23.37.02 # i tried it a few times, didn't work 23.37.02 # but... if you want to do it 23.37.04 # ok 23.37.06 # i'm sure i know how to do it now 23.37.12 # well, you may do it 23.37.26 # i get some error: 23.37.28 # ../../apps/plugins/etchasketch.c:66: warning: implicit declaration of function ` 23.37.28 # memset' 23.37.38 # i'd have to see the code.... 23.37.41 # but memset is declared in plugin.h 23.37.50 # it's the screen_dump code 23.37.57 # copypasted 23.38.00 # :) 23.38.37 # ahhh 23.38.43 # you were planning to save to disk, no? 23.38.47 # save sketches to disk* 23.38.50 # yep 23.39.06 # ok here's what you do 23.39.07 # linus said i had to do it :) 23.39.11 # err 23.39.34 # well i need what you have so far to see what's wring 23.39.35 # wrong* 23.39.49 # yeah, was already uploading it 23.40.01 # http://home.student.utwente.nl/r.teune/etchasketch.c 23.40.40 # ah, i see what's wrong 23.40.47 # cool 23.41.02 # what is it? 23.41.22 # you're not using the api correctly 23.41.35 # you need to add rb-> before you can snprintf or close 23.41.52 # hm... ok 23.42.06 # of course 23.42.10 # try adding a "rb->" before every function that it gives an error for 23.42.24 # after that we can try moving without etching 23.42.24 # so if i write code for rockbox itself i dont have to do rb, and now i do 23.42.28 # ok 23.42.32 # plugins use an api 23.42.38 # you have to have rb-> before those functions 23.43.21 # which means you're telling [rockbox](rb)[to](->)[do this](lcd_clear_display();] 23.43.40 # heh... :P 23.43.54 # i did rb->screen_dump :P 23.44.05 # asdfadsf. :) 23.44.13 # that will not work. 23.44.31 # that's called object oriented programming, isnt it? 23.44.52 # i don't think so, but i'm not sure. 23.44.57 # at least at all OO examples (C++, php OO) they use -> 23.46.48 # let me see how you took care of the boundary checking 23.47.13 # nice nice.. 23.47.40 # is it? 23.48.02 # just standard boundary checking 23.48.32 # yeah. i was going to suggest drawing the pixel constantly but your way is a bit better 23.48.55 # excellent, you also added a clear-screen function 23.49.07 # rb->lcd_clearrect(0,0,112,64); 23.49.07 # rb->lcd_update_rect(0,0,112,64); 23.49.14 # this could be improved and a bit simpler 23.49.22 # rb->lcd_clear_display(); 23.49.27 # linus told me to add a clearscreen function :) 23.49.29 # rb->lcd_update(); 23.49.38 # hm.. ok :) 23.49.53 # how about this? 23.49.54 # extern unsigned char lcd_framebuffer[LCD_HEIGHT/8][LCD_WIDTH]; 23.50.03 # should it be changed to extern unsigned char rb->lcd_framebuffer[LCD_HEIGHT/8][LCD_WIDTH]; 23.50.23 # nope 23.50.33 # the compiler complains 23.51.10 # weird 23.51.40 # /home/guest/simbuild/etchasketch.po(.text+0xe3): In function `screen_dump': 23.51.40 # /home/guest/uisimulator/win32/../../apps/plugins/etchasketch.c:62: undefined ref 23.51.40 # erence to `_lcd_framebuffer' 23.52.09 # and you called me zeekoe!!! :P 23.52.31 # what are you editing with? 23.52.34 # i did? 23.52.59 # zeekoe, wish me to help you implement a "move around" mode? 23.53.04 # TextPad 23.53.19 # view the line numbers 23.53.30 # its' erroring on line 62, and line 62 is... 23.53.31 # buf[i++] = lcd_framebuffer[y][x]; 23.54.12 # yep 23.54.19 # drop everything and upload what you've got, so we can fix this. 23.54.40 # it says undefined reference to lcd_framebuffer 23.54.52 # but a few lines above, lcd_framebuffer is defined 23.55.03 # uploaded 23.55.06 # can you upload it? i want to see something 23.55.25 # http://home.student.utwente.nl/r.teune/etchasketch.c 23.55.59 # first error.. 23.56.09 # line 28, function declaration isnt a prototype 23.56.18 # ?? 23.56.37 # add "void" in between the parenthases of show_pix when you declare it 23.56.40 # my gcc doesnt tell it 23.56.43 # ok 23.56.44 # void showpix(void) { 23.56.44 # rb->lcd_drawpixel(y,x); /* draw the pixel */ 23.56.44 # rb->lcd_update_rect(y,x,1,1); /* make rockbox show it */ 23.56.44 DBUG Enqueued KICK midk 23.56.44 # } 23.56.51 # sounds reasonable 23.57.12 # remove the rb-> before screen_dump, as it's not in the API 23.57.13 Ctcp Ignored 2 channel CTCP requests in 1 hour and 48 minutes at the last flood 23.57.13 # * zeekoe used VB too much, it's lame at strict use of language 23.57.18 # nder BUTTON_F2 23.57.25 # uh 23.57.26 # i did? 23.57.31 # you need to remove it 23.57.36 # case BUTTON_F2: 23.57.36 # screen_dump(); 23.57.36 # break; 23.57.42 # i already did 23.57.47 # ok 23.57.50 # weird 23.57.54 # i'll upload again 23.58.02 # ok 23.58.06 # can you download again 23.58.20 # still the same 23.58.22 # it should've been gone before 23.58.23 # weird