--- Log for 18.09.105 Server: herbert.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 17 days and 17 hours ago 00.00.16 # Update 13 Sep 2005: Please upgrade to TWikiRelease03Sep2004 or apply patch for SecurityAlertExecuteCommandsWithRev. -- PeterThoeny - 13 Sep 2005 00.00.17 # http://twiki.org/cgi-bin/view/Codev/SecurityAlertExecuteCommandsWithRev , http://twiki.org/cgi-bin/view/Codev/SecurityAlertExecuteCommandsWithSearch 00.00.27 Quit sneakums ("taster, you're the automatic saint") 00.01.19 # Man, every release were affected 00.01.38 # ah, no 00.02.37 # the rev thing was used against us 00.02.51 # um, where's the publication date of these alerts? 00.03.28 # they are wiki pages, you can check their history 00.03.43 # the rev page is from sep 9 2005 00.03.57 # Yeah 00.04.09 # Researcher discloses issue 2005-09-09 00.04.25 # thx, found it, too 00.04.35 # That's ... odd 00.04.55 # and they seemed to have announced it widely on sep 13 00.05.15 # Was Rockbox included in " 5. Compile e-mail list of administrators of public TWiki sites" ? 00.05.25 # nope 00.05.28 # and heise.de published it on sep 16 00.05.38 # not exactly 0-day, but close 00.06.27 # the actual delete was made 23:17 CET on the 16th 00.06.38 # Why do they publish an article about such a serious security hole one year after fixing it??? 00.07.04 # amiconn: there have been two vulnerabilities 00.07.07 # this was not fixed 00.07.10 # until just then 00.07.28 # Bagder: My first thought was that you or Linus took it offline because of someone mentioning this flaw here in the channel... 00.07.29 # according to that page at least 00.07.48 # the first one (from 2004) was used to attack a wiki from the german chaos computer club 00.07.50 # amiconn: I noticed that mention and I mailed both Linus and Zagor 00.07.57 # but it wasn't good enough 00.07.59 # (europe's largest hacker org) 00.08.25 # Bagder: I know that there were two vulnerabilities, the Rev thing being the second 00.08.28 # in retrospect, of course I should've shutdown the twiki parts 00.08.47 # Bagder: well, you learn from these things 00.08.52 # yeah 00.09.17 # we've been hit before :-/ 00.09.23 # after reading #rockbox today, i immediately switched off clamav on my machine since there's a vulnerability, too- 00.09.30 # D'ouh! 00.09.31 # However http://twiki.org/cgi-bin/view/Codev/SecurityAlertExecuteCommandsWithRev says that releases up to TWikiRelease02Sep2004 are vulnerable, and TWikiRelease03Sep2004 fixes it 00.09.34 # 2004 (!) 00.10.21 # NOTE: If you are running an unmodified TWikiRelease02Sep2004, simply copy the patched lib/TWiki/Store.pm, 00.10.27 # Eh. 00.10.30 # Nevermind. 00.10.32 # Ah, an additional patch is needed, but that's from Feb 2005... 00.11.02 # I think it is just their naming that is confusing 00.11.06 *** Saving seen data "./dancer.seen" 00.11.09 # they seem to have made the fix on sep 11 2005 00.11.38 # not that it matters now 00.12.21 # Hmm, indeed a confusing scheme.... 00.12.46 Quit gromit` (Remote closed the connection) 00.18.51 Join gromit` [0] (i=gromit@ras75-5-82-234-244-69.fbx.proxad.net) 00.29.58 # Another archos firmware test recording hung after 10 h 47 min 00.31.23 Quit t0mas (Read error: 104 (Connection reset by peer)) 00.31.37 # 36 different IP addresses have used the twiki flaw 00.33.31 # http://www.groupiys.net/xpl/dc.txt 00.33.41 # seems to be a popular backdoor attempt 00.34.13 # ooh, they've been trying to backdoor you? 00.34.28 # lots of those guys tried hard 00.34.57 # * amiconn 's machine is lagging like hell atm 00.35.18 # Loading a 700 MB file into the hex editor... 00.35.47 # Why is your hex editor caching the entire file? 00.35.56 # Fast searching... 00.36.05 # Sounds silly for such a large file 00.36.15 # Now it's running fine. 00.36.22 # My machine has 1 GB of RAM 00.37.09 # That leaves 300mb.. I guess XP is breathing heavily now :( 00.37.25 # No, everything running smooth again 00.37.43 # (with like a dozen programs opened in parallel) 00.40.09 Join webguest67 [0] (n=46b7ed92@labb.contactor.se) 00.41.33 # hi everybody 00.41.47 # Evening. 00.42.04 # hi rasher 00.43.27 # i just started getting into rockbox and when i load a wps with a bitmap it doesn't show up, any ideas of how to fix this? 00.43.50 # Use the correct syntax :) 00.43.55 # I'd point you at the wiki, but.. 00.43.56 # hang on 00.44.28 # http://rasher.dk/rockbox/WikiRescue/CustomWPS-r1.29%20-%2009-07.html 00.44.31 Quit webguest67 (Client Quit) 00.57.29 # someone did run processes on the server 00.58.04 # Uh-oh 00.58.25 # as the http user 00.58.46 # would need an apache exploit for that to be really useful 00.58.58 # or any other local exploit 00.59.10 # oh, true that 00.59.40 # well at least there's a pretty well-documented point-of-entry 01.00.31 # it's a lot more worrying when you can't tell where they got in 01.00.32 # yes 01.00.52 # but still, seing a 'bash' running that ain't us... 01.01.34 # but I really don't want to shut it down completely 01.04.31 Join webguest67 [0] (n=46b7ed92@labb.contactor.se) 01.07.48 # I've kept the scripts for later analysis, now I need sleep 01.07.53 # night 01.08.08 # night 01.09.19 # that worked! 01.09.36 # thanks rasher 01.10.00 # You're welcome. 01.13.48 Quit Moos ("Parti") 01.21.05 Join davidd [0] (i=davidd@67.50.83.113) 01.21.30 Quit matsl (Remote closed the connection) 01.26.05 Join Paul_The_Nerd [0] (n=paulthen@cpe-66-68-93-2.austin.res.rr.com) 01.31.11 Join ashridah [0] (i=ashridah@220-253-122-113.VIC.netspace.net.au) 01.31.30 Join t0mas [0] (n=Tomas@unaffiliated/t0mas) 01.35.29 Quit davidd () 02.04.06 Part Shapeshifter 02.04.09 Quit Domonoky (Read error: 104 (Connection reset by peer)) 02.06.12 Join CheeseBurgerMan [0] (n=burgerbo@tc2-225-101.altelco.net) 02.07.59 Quit dpassen1 () 02.11.10 *** Saving seen data "./dancer.seen" 02.19.14 Quit Paul_The_Nerd ("Chatzilla 0.9.68a [Firefox 1.0.6/20050716]") 02.29.50 Quit noC|andY`fRa (Read error: 104 (Connection reset by peer)) 02.41.08 Join DJ_Dooms_Day [0] (n=scottr@220-245-186-182.static.tpgi.com.au) 02.53.43 Join DarkShadow [0] (n=8d9ea6a3@labb.contactor.se) 02.57.29 Join noiz [0] (n=noiz@ip68-227-206-41.dc.dc.cox.net) 02.57.55 Join bitshift [0] (i=lock@CPE000c6e94cf09-CM001225d870de.cpe.net.cable.rogers.com) 02.58.18 # hey 02.59.10 # Hey! 02.59.37 # I'm having a problem with creating a song database for my H120. 02.59.38 # whats happening 02.59.48 # any info for rockbox on iaudio x5? 03.00.00 # When I run the .bat to make the database, a dos prompt just flashes onto my screen, then closes, and it doesn't do anything. 03.00.41 # bitshift: not really.. haven't heard from the guy working on it for a while 03.01.21 # what involves developing such software for the device? 03.02.12 # First making a way to run your own code on the device, then writing drivers for Rockbox, I guess 03.02.37 # DarkShadow: what error message do you get? 03.03.09 # I don't get an error message. 03.03.21 # what does it say in the dos prompt? 03.03.33 # The dos prompt just pops up too fast for me to read, then closes. 03.03.55 # run the .bat from within a dos prompt 03.04.17 # How do I get to F/.rockbox though? 03.04.29 # When I tried it, the dos prompt didn't like the period before the folder. 03.04.53 # haha, silly windows 03.04.56 # no idea 03.05.06 # :-P 03.05.36 # cd ".rockbox" works here 03.05.42 # I think there's a code thing you can put on the end /(something) when running it to make it stop...not sure what it is though. 03.05.58 # With the parenthesis? 03.06.24 # no, with the double-quotes. 03.07.00 # unless i'm mistaken about the meaning, dictionary isn't very helpful 03.07.21 # It says Invalid Directory. 03.07.34 # and this is win2000/XP? 03.07.35 # It even shows it when I do 'dir'... it has it with the period before too. 03.07.43 # Yeah, XP. 03.08.00 # that's strange 03.08.07 # And I guess you're on the right drive if you see it 03.08.11 # if you use properties on the batch file, can you not configure it so it doesn't close the window? 03.08.28 # I'll check. 03.09.02 # Umm. 03.09.15 # It doesn't really have anything. 03.10.48 # Hmm. 03.11.52 # Ooh.. 03.11.59 # I renamed rockbox without the period, and ran it in command, and now it's working. 03.12.06 # It had an error, I was missing a file. 03.12.40 Join DJ_Dooms_Day|AF [0] (n=scottr@220-245-186-182.static.tpgi.com.au) 03.12.41 # Do both of you use the DB? 03.12.49 # Hey! 03.14.06 Quit DJ_Dooms_Day (Read error: 104 (Connection reset by peer)) 03.14.26 Join Script [0] (n=Script@p548C95E6.dip0.t-ipconnect.de) 03.20.05 # Umm. 03.20.17 # My H120 says 'Codec Failure' now...and I can't turn it off. 03.20.44 # Did you move .rockbox back? 03.21.11 # Yeah. 03.21.25 # reinstall rockbox, and make sure you overwrite all files 03.21.35 # Well... I couldn't rename it .rockbox...so I copied it back over. 03.21.50 # That's what I was planning on doing, but I can't get this to do anything. 03.21.57 # It's like frozen. 03.22.09 # Plugging it into USB doesn't do anything either. 03.22.18 # Reset it then 03.22.45 # Ah...there's the button. ;) 03.26.10 # How do I restart everything? 03.26.33 # It says "error accessing playlist control (file?)' 03.27.19 # plug in usb and reinstall 03.27.34 # How? 03.27.46 # What do you mean how? 03.27.52 # You've done this before, surely 03.28.07 # Uhh, is it called flashing it? 03.28.27 # no... just unzip rockbox.zip unto the drive 03.28.49 # I did...and it still has that error. 03.29.22 # when? 03.29.26 # can't you just ignore it 03.30.15 # The boot thing comes up, then the Rockbox logo, then it pops up infront of the Rockbox picture... "Error accessing playlist control file" 03.31.05 # can't you just make it go away? 03.31.11 # press stop or select or something 03.32.16 # ah... I got it now. 03.32.25 # How do I get that playlist thing working though? 03.32.27 Quit Riddy (Read error: 110 (Connection timed out)) 03.32.55 # should be fixed next time you create a playlist I think 03.34.28 # Ah...brilliant, thanks. 03.36.41 # Another thing... I was reading through the forums the other day how Rockbox had the problem of letting the mp3 player run out of battery, and that polymer batteries get damaged when they run out of batteries. 03.36.53 # So...just the other day, I didn't know it was on, and it totally ran out of battery. 03.37.44 # I don't think Rockbox can run them far enough down as to damage them 03.37.52 # not sure though 03.39.13 # Okay...then what would the worry be? 03.39.33 # that Rockbox failed to actually shut down 03.39.45 # Ah. 03.39.49 # because it tried to spin up the harddisk, which it couldn't 03.39.50 # So only that it wouldn't save the playlist or something? 03.40.19 # well that, and it'd sit there trying to spin up the harddisk 03.40.41 # Ah. 03.40.43 # Well that's a relief. 03.40.46 # Thanks much! :) 03.41.07 # Do you use the database? 03.41.31 # not really 03.41.49 # Just file tree? 03.42.12 # yes 03.43.24 # Ah. 03.48.30 Quit CheeseBurgerMan (Read error: 104 (Connection reset by peer)) 03.50.39 # Is there a limit to the speed that scrolling increases two when going down a big list? 03.50.52 # It takes me like a minute and a half to scroll through the list of all my songs. 03.51.24 # yes 03.51.31 # eh 03.51.31 # no idea 03.51.32 Quit rasher ("Ex-Chat") 03.52.01 # Whee. 03.52.48 Quit ender` (Read error: 110 (Connection timed out)) 03.55.36 # Anyone here now? 03.56.44 Join CheeseBurgerMan [0] (n=burgerbo@tc2-225-101.altelco.net) 03.56.53 # kinda 03.57.19 # How do you record with rockbox? 03.57.30 # Messing around with it for a while now, I haven't found it. :-P 03.58.12 Join hd [0] (i=hd@gate-hannes-tdsl.imos.net) 03.58.48 # i dont think you can yet 03.59.03 # their still adding a lot of thins 03.59.19 # I guess that would explain it. :-P 03.59.20 # Ah. 04.03.19 # How do you install .patch files? (I'm trying to have a different keyboard--keyboard.patch) 04.03.56 # i think there's a record option in the debug menu? 04.04.00 # but .. it breaks stuff 04.05.38 # Oh..haha. 04.05.42 # Alright, I'll avoid it then. 04.05.45 Join QT [0] (i=as@madwifi/users/area51) 04.05.55 # Hey. 04.11.14 *** Saving seen data "./dancer.seen" 04.14.15 Quit goa (Connection timed out) 04.14.16 Nick hd is now known as goa (i=hd@gate-hannes-tdsl.imos.net) 04.15.13 # Well I think I'll head off for now. 04.15.19 # Thanks so much for all your help, Fuzzie. 04.16.57 Quit DarkShadow ("CGI:IRC (EOF)") 04.17.26 Quit QT_ (Connection timed out) 04.40.32 Quit CheeseBurgerMan (Read error: 104 (Connection reset by peer)) 04.47.33 Quit cYmen ("zZz") 04.59.39 Join pengo [0] (n=xtofu@60.240.136.82) 04.59.49 Quit DJ_Dooms_Day|AF () 05.15.32 Part noiz ("Leaving") 06.11.18 *** Saving seen data "./dancer.seen" 06.21.08 Quit webguest67 ("CGI:IRC") 06.22.34 Quit bitshift ("fractal2 mirc script (ver 1.0betar2) · http://fractal2.net") 07.50.04 Quit ashridah (Read error: 110 (Connection timed out)) 07.50.41 Join ashridah [0] (i=ashridah@220-253-120-24.VIC.netspace.net.au) 08.11.20 *** Saving seen data "./dancer.seen" 08.42.47 Quit Febs (Read error: 110 (Connection timed out)) 09.13.06 # * HCl yawns 09.20.24 Join ender` [0] (i=ychat@84.52.165.220) 09.23.57 # What was the maximum file size rockbox supports? Just thinking if i could record 4h continuously with iriver.. 09.25.02 # if it's around 2GB (2^31), that is not possible then because there is no currently file splitting 09.50.24 # 2GB 09.50.46 # You shouldn't try more, as the recording code doesn't check for that iirc 09.51.31 # (on iriver) 09.52.11 # ok, then i will try manually stopping and restarting the recording after two hours :) 09.52.44 # btw, does original firmware support longer recordings to wav files? 09.54.33 # I have no idea 09.54.42 # Never recorded with the original firmware 09.54.55 # ah, almost same here 09.55.21 # Hmm, or maybe i have enough time to code the splitting feature before recording.. =) 09.59.24 Quit ender` (Read error: 104 (Connection reset by peer)) 10.02.11 # Slasheri, ihp120 has recording limits under 60 mins.. definately wouldn't record longer than 74min.. there were different limits for wav and mp3 recording.. can't remember exactly 10.03.48 Join ender` [0] (i=ychat@84.52.165.220) 10.04.20 # huh.. that's not good 10.04.33 # (with original firmware) 10.04.41 # at least over 3h to wav shouldn't be a problem 10.04.42 # yes 10.04.57 # but there must be something weirdness in the code then 10.05.01 # that's what's stated in the manual at least 10.05.12 # i'm not sure i've ever tried recording that long 10.11.22 *** Saving seen data "./dancer.seen" 10.38.08 Join amiconn_ [0] (n=jens@p54BD48EB.dip.t-dialin.net) 10.39.33 Quit amiconn (Nick collision from services.) 10.39.33 Nick amiconn_ is now known as amiconn (n=jens@p54BD48EB.dip.t-dialin.net) 10.45.11 Join webguest41 [0] (n=d5ee42e0@labb.contactor.se) 11.06.27 # Hmm, the wav splitting seems to work well :) Now listening the recorded files (splitted to 1 MB per file) with iriver and playback is continuous 11.06.42 # cool 11.06.57 # i hope you make the default larger tho :) 11.07.04 # hehe, sure :D 11.07.04 # and make it auto generate a playlist file 11.12.29 # now it will name the files following: rec_0001_00.wav, rec_0001_01.wav, ... Maybe two digits is enough if we have something like 650MB - 2 GB file size (should be configurable) 11.13.16 # hmm 11.13.24 # shouldn't have an extra ending if there's only one file 11.13.29 # Why double numbering? 11.14.07 # pengo: Hmm, so the numbering should go: rec_0001.wav, rec_0001_02.wav, rec_0001_03.wav or something like that? 11.14.15 # Slasheri, yeah i reckon 11.14.24 # ok, that sounds better :) 11.14.31 # tho it's still confusing looking.. 11.14.40 # true.. but files will sort right 11.14.45 # yup 11.15.14 # The numbering should go rec_0001.wav, rec_0002.wav etc 11.15.27 # amiconn: no, if we are splitting the current file? 11.15.32 # Yes 11.15.36 # Hmm.. 11.15.40 # amiconn might be right. 11.15.56 # maybe that's better.. 11.16.00 # This is how the already existing recording screen handles it. 11.16.33 # Slasheri, you could have a rec_0001.wav, rec_0002.wav, and rec_0001.m3u (or whatever playlist format) 11.16.39 # On archos, you can set automatic time split, can do a manual split by a button press, and finally it auto-splits when approaching the 2GB barrier 11.17.04 # interestink 11.17.20 # amiconn: btw, will the recording screen in debug menu be the future recording menu on iriver or will it change? If not, i could implement menu system there etc. to set the recording parameters 11.17.51 # Why diversify code??? 11.18.11 # hmm? 11.18.13 # There already is a recording screen. Imho we should use as much common code as possible 11.18.39 # ah, so then we should port that screen to work 11.19.16 # Yes 11.21.37 # Away now 11.23.05 # is there any widget code in rockbox? 11.23.17 # like buttons and menus and stuff 11.26.03 # unfortunately not really 11.32.37 Join linuxstb_ [0] (n=5343d4aa@labb.contactor.se) 11.34.13 # There is a menu "widget". And maybe one or two more - e.g. the progress bar used in the WPS screen. 11.44.06 Join Shapeshifter [0] (i=user@80-218-25-181.dclient.hispeed.ch) 11.47.15 Join Lear [0] (n=chatzill@h36n10c1o285.bredband.skanova.com) 11.50.11 Join Yokalosh [0] (n=andrew@cpc3-cbly2-4-0-cust144.glfd.cable.ntl.com) 11.50.18 Part Yokalosh 12.01.56 # may I ask a question about a wps? 12.03.28 # Go ahead. 12.03.35 # yes, but now you have used your single question daily allotment. 12.03.46 # lol ok... 12.05.44 # Since I upgraded to the last rockbox version, none of the images used in the wps are beeing shown. e.g. in snapwise: 12.05.44 # #Snapwise v1.0, made by Aru (aru@jhu.edu) 12.05.44 # %x0|snapwisebg.bmp|0|0| 12.05.44 DBUG Enqueued KICK Shapeshifter 12.05.44 # %ac%s%?ia<%ia|%d2> 12.05.45 # %ac%s%?id<%id|%d1> 12.05.47 # %ac%s%?it<%?in<%in - |>%it|%fn> 12.05.51 # %ac%pc/%pt 12.05.53 # %pb 12.05.57 # %ac%s%?Ia<%Ia|%D2> 12.05.59 # %ac%s%?Id<%Id|%D1> 12.06.01 # %ac%s%?It<%?In<%In - |>%It|%Fn> 12.06.05 # %pv %bl (%bt) 12.06.09 # I have to change the first line to: 12.06.11 # %x|a|snapwisebg.bmp|0|0| 12.06.13 # and make a empty line after it, so evereything is aligned correctly. Before of the last version everything was fine without these manual changes 12.06.24 # why is that 12.06.48 # this is how it has to look like http://aru.acm.jhu.edu/snapwise.png 12.07.30 # and if I dont make the changes manually it just shows x0|snapwisebg.bmp|0|0| in the first line insteaqd of the image 12.08.57 # the format has changed, take a look at the newer wps files found at misticriver 12.09.30 # It's documented here: http://64.233.187.104/search?q=cache:iV-vaRt8HvgJ:www.rockbox.org/twiki/bin/view/Main/CustomWPS site:rockbox.org custom wps&hl=en&client=firefox-a 12.09.51 # allright thank you 12.10.10 # yeah I know that page I didnt notice the change 12.11.25 *** Saving seen data "./dancer.seen" 12.13.15 # How does Rockbox deal with a partitioned hard disk? Does it just use the first partition? 12.13.58 Join Moos [0] (i=DrMoos@m113.net81-66-159.noos.fr) 12.23.10 Part Shapeshifter 12.29.41 Quit Lear (Remote closed the connection) 12.39.36 Join cYmen [0] (n=cymen@nat-ph3-wh.rz.uni-karlsruhe.de) 13.07.58 Quit Sucka ("a bird in the bush is worth two in your house") 13.08.01 Join linuxstb__ [0] (n=linuxstb@i-83-67-212-170.freedom2surf.net) 13.09.36 Join ze__ [0] (i=ze@ca-dstreet-cuda2-c9a-73.snbrca.adelphia.net) 13.10.04 Quit ze (Nick collision from services.) 13.10.09 Nick ze__ is now known as ze (i=ze@ca-dstreet-cuda2-c9a-73.snbrca.adelphia.net) 13.13.15 Quit linuxstb_ ("CGI:IRC (Ping timeout)") 13.23.08 Join Febs [0] (n=Febs@207-172-122-81.c3-0.rdl-ubr4.trpr-rdl.pa.cable.rcn.com) 13.24.44 Quit linuxstb (Read error: 110 (Connection timed out)) 13.25.41 Join Sucka [0] (n=NNSCRIPT@host81-156-157-185.range81-156.btcentralplus.com) 13.39.25 Quit Maxime () 13.41.14 Join Maxime [0] (n=flemmard@fbx.flemmard.net) 13.51.04 Quit pengo ("qubero - open binary") 13.52.25 Join Lear [0] (n=chatzill@h36n10c1o285.bredband.skanova.com) 13.54.36 Join paugh [0] (n=kickback@2001:5c0:8fff:ffff:8000:0:3e03:6822) 13.56.11 Ctcp Ignored 1 channel CTCP requests in 0 seconds at the last flood 13.56.11 DBUG Enqueued KICK Script 13.56.11 # * Script 14Winamp 5.08 - The Police - The bedīs too big without you (playing) - 44kHz 128kbps stereo - 4m 24s long 15|4>>>>>>>>5>15>> 14(85%)15|14 13.57.37 # Strange... __builtin_alloca isn't available when I build the simulator... 14.10.24 Quit edx () 14.11.26 *** Saving seen data "./dancer.seen" 14.22.03 # Slasheri: lately Rockbox has been "forgetting" to buffer file data (i.e., I start playback, and when it is time for the first "full buffering", nothing happens, it seems, so playback stops)... 14.22.43 # Have you heard of that problem before? Could be related to me listening to oggs mainly now, or possibly some changes I've made in metadata.c... :) 14.23.15 # Lear: interesting, at least i haven't had that problem yet 14.23.35 # can you reproduce it? 14.23.38 # I have a strange problem 14.23.52 # One time I boot the player, no sound.. 14.23.56 # Stop it, restart it 14.24.00 # the sound come back 14.24.13 # I've seen similar things before; when first "full buffer" is about, it just buffers some data (rest of the track?), but the next buffering after that works as expected. 14.24.19 # Maxime: that must be bacause of some hardware differences between the units :/ 14.24.37 # and that issue will be hard to fix without having such a unit 14.24.39 # But no, I can't easily reproduce it. It just happens sometimes... 14.25.11 # At first I suspected too low anti-skip buffer, but it can even happen with a 30s buffer. 14.25.24 # And most times I've noticed it, the player has been on a desk... 14.25.27 # Lear: hmm, that might be when we skip to the next folder 14.25.34 # on that situation, the buffer always runs empty 14.26.22 # Nope, folder skipping isn't involved (it's off anyway). Always in the middle of a playlist. 14.26.34 # Hmm, weird.. 14.26.45 # And it runs out of buffer in the middle of a track. 14.27.11 # have you tried a fresh daily build without any own patches to code? 14.27.38 # No, not yet. I guess I should at least remove the metadata changes... :) 14.28.33 # :) 14.29.08 # Btw, regarding metadata.c, when should get_metadata return false? 14.30.07 # Hmm, when the file is badly corrupted / unrecognized 14.30.19 # returning false will prevent starting of the playback 14.32.00 # What about IO error reading e.g. vorbis comments? 14.33.13 # i think it's safe to skip the file then 14.33.31 # I.e., return false... 14.33.35 # yes 14.36.18 # btw, i have just enabled the "real" recording screen on iriver. But it's not quite usable yet, there is lot to do to support all of the functions 14.39.05 Quit paugh (Excess Flood) 14.40.22 Join paugh [0] (n=kickback@2001:5c0:8fff:ffff:8000:0:3e03:6822) 14.41.11 Quit paugh (Client Quit) 14.41.40 Join AliasCoffee [0] (n=kickback@dsl-62-3-104-34.zen.co.uk) 14.43.34 # Slasheri: I don't think playback.c always reacts correctly when get_metadata() returns false. 14.43.56 # e.g. the crashes reported when playing FLAC files with id3v2 tags - get_metadata() returns false for such files. 14.44.13 # There's a couple of places where the return value is ignored. 14.45.30 # linuxstb__: Hmm, that's true 14.46.20 # If it doesn't affect playback, is it possible to always call get_metadata() before you initialise the codec? This would allow get_metadata() to change the codec type after analysing the file. 14.46.25 # But if get_metadata sets taginfo_ready to false if the reading failed, that should be not an issue (and we could do that also) 14.46.59 # No, that would spin up the disk 14.47.25 # Don't you need to spin up the disk to load the codec? 14.47.35 # no, if it's buffered 14.47.39 # get_metadata() also spins up the disk. 14.47.59 # yes, it always spins it up 14.48.40 # Is get_metadata() called when you start buffering a new file, or elsewhere? 14.48.57 # cdcd /cygdric 14.49.21 # it's called always before buffering that file. At the same moment the metadata (including codec type) is save to the trackinfo structure 14.49.40 # wtf 14.49.45 # crwl :D 14.49.54 # thank you cygwin or someone 14.49.57 # :) 14.49.58 # Sorry, I have to run now. back later. 14.50.02 # cu 14.50.46 # i managed to do a great windows xp trick - the window that was on top didn't have the keyboard focus 14.50.50 # interesting 14.51.00 # hehe 14.53.02 Join edx [0] (i=edx@p54A85481.dip.t-dialin.net) 14.53.29 Join webguest72 [0] (n=53afb0c2@labb.contactor.se) 15.12.44 Quit Lear ("Chatzilla 0.9.68.5.1 [Firefox 1.4/undefined]") 15.23.11 Quit linuxstb__ (Read error: 104 (Connection reset by peer)) 15.23.13 Join linuxstb_ [0] (n=linuxstb@i-83-67-212-170.freedom2surf.net) 15.35.44 # hehe, now recording peak meters work :) 15.40.15 Quit t0mas (Read error: 104 (Connection reset by peer)) 15.45.35 Join muesli- [0] (i=muesli_t@Bc15d.b.pppool.de) 15.46.45 # re 15.52.15 Join t0mas [0] (n=Tomas@unaffiliated/t0mas) 16.00.14 # Hmm, in recording.c why is peak meter always set to playback mode? 16.00.27 Join muesli__ [0] (i=muesli_t@Bc153.b.pppool.de) 16.02.56 # Slasheri: That's because the MAS has two registers for reading the quasi-peak value, 16.03.12 # one connected to the ADC and one connected to the DAC 16.03.24 # amiconn: yes, but i tought it would be logical to have it in "recording mode" while recording :) 16.03.35 # The DAC reading is always valid because recording monitor is always enabled 16.03.43 # anyway that doesn't matter, i will still implement that for software codecs also 16.03.55 # hmm, ok :) 16.04.05 # ...but the ADC register only works when recording from line in or mic, not from s/pdif 16.05.14 # I think that shoould be changed for swcodec platforms, or perhaps there is no specific mode setting necessary 16.05.41 # Peak calculation is always done across a bunch of PCM samples with swcodec 16.05.55 # i changed it so on swcodec platforms it will be on "recording mode" while recording, so the peak_meter_peek calls the right function to fetch the peak data from 16.06.17 # Why not have just one function? 16.06.57 # Hmm, that is also possible.. Then we have to put the function to a different file 16.07.12 # Hmm, probably 16.07.17 # currently it's on pcm_playback.c for playback (and firmware layer should not access to the apps/).. 16.07.27 # ...or we need to unify pcm_playback and pcm_record 16.07.35 # yes.. 16.07.56 # I'm not sure whether this would be a good idea 16.08.24 # me either :) we still might have units that would not be capable for recording 16.08.26 # I thought a bit about the general architecture, concerning recording, playback, and buffering 16.09.04 # I think that the current separation between buffer/ track handling and pcm playback is the right way 16.09.36 # ...and the firmware layer should allow pcm playback and recording at the same time. 16.09.41 # ...if possible 16.09.51 # hmm, interesting 16.10.21 # In the high-level code, allowing both playback and recording at the same time doesn't make sense 16.10.34 # ...because then we would need to split the buffer 16.10.53 # yes. But for example playing voice samples during recording might be a good idea 16.11.01 # The low-level full-duplex operation opens the door for interesting sound effect plugins 16.11.14 # ah, true also :) 16.11.28 *** Saving seen data "./dancer.seen" 16.11.55 # In short: PCM playback & recording should be allowed full duplex on the units that support it 16.12.24 # File playback and recording should be exclusive (but voice UI still possible since low level supports full duplex) 16.12.36 # yep. I don't think that would be a big problem with the current architecture 16.13.01 # The voice file buffer is set aside anyway, shouldn't make a big difference between recording & playback 16.15.31 # linuxstb_: Rockbox uses the first primary FAT32 partition it can find. 16.16.01 # Logical drives are not (yet) supported, but I intend to change that 16.16.39 # amiconn: Thanks. Just gathering info for the iPod. 16.17.12 # It uses a very simple but effective approach - it simply tries to mount every non-empty partition entry as FAT32. If that fails, it tries the next etc. 16.17.25 # So the partition type field doesn't matter at all 16.18.23 # Rockbox for Ondio is almost the same, only two differences: (1) It handles 2 drives (internal flash + MMC). (2) It handles FAT16 in addition to FAT32 16.18.24 # btw, does iriver have serial or parallel flash chip? 16.18.33 # ? 16.18.45 # Do you mean the firmware flash rom? 16.18.49 # yes 16.18.54 # i think it's parallel.. 16.19.11 # It's a standard flash eeprom. They're always parallel 16.20.10 # yes, unfortunately. If it has been serial then it could be easy to build a mod to recover the flash contents (possible useful for developers) 16.21.01 # You would have to unsolder it anyway, regardless of interface 16.21.25 Quit ashridah ("Leaving") 16.22.32 Quit Script ("Bambalam .gx.") 16.24.37 Quit muesli- (Read error: 110 (Connection timed out)) 16.30.51 Join tucoz [0] (n=martin@12.80-202-99.nextgentel.com) 16.31.56 # Good thing that most of the wiki were taken care of by google & co 16.33.23 # I read that some person at ubuntu had a recent attack from a .ru. Just that he didn't refer to the attackers as gentlemen, but scriptkiddies :) 16.35.08 # amiconn: Hmm, why? Isn't the cpu tri-stated while it's powered off? 16.37.16 # mhm. 16.37.41 Join zenx [0] (n=d9417045@labb.contactor.se) 16.37.58 # hello 16.38.06 # what's up with the website? 16.38.14 # Slasheri: How would you power the flash rom without also powering the CPU when it's soldered in? 16.38.29 # zenx: Read the news item at the top of the front page. 16.39.09 # amiconn: true, that would be hard.. :) but never mind, there is probably no easy and cheap way for everyone to do that 16.39.40 # oh, that's fucked... are there backups? 16.40.31 # zenx: Yes. 16.41.53 # I simply can't comprehend what the point of doing that is. 16.42.04 # any optical gurus here? 16.45.14 # umm, don't know if this has been discussed before, but: has anybody considered connecting an ADAT lightpipe signal to the h120? the adat lightpipe uses the same toslink plastic cable as the s/p-dif, but it's a different protocol. it transfers 8 channels at once (in a serial order) 16.46.18 # Hmm, i don't think that would work.. Checking the cpu datasheet 16.47.36 # here's a brief description: http://www.nt-instruments.com/X0-ASP-pLngCateId_219-pIntLevel_4-pLngPageId_656-X1-default.htm 16.48.59 # "Optical interface components and optical fibres are identical to the cost effective components as applied with the optical S/PDIF (TOSLINK) interface." 16.49.02 # so it may work 16.49.45 # and this is information about the data transfer: http://www.dmalham.freeserve.co.uk/adat.html 16.50.00 # but i really doubt that, the protocol is different 16.50.18 # but if the pulse speed and other features (what there are) differ enough, the S/PDIF chip wouldn't understand anything about the signal anyway, right? 16.51.01 # some kind of weird data transfer mechanism via the optical connectors would be funny, though 16.51.18 # yeah, well this is what I don't have info about 16.51.31 # wether the pulse speed differs and suc 16.51.32 # h 16.52.25 # i have no idea if there's such thing as pulse speed, nor do i really know anything about toslink. but anyway :) 16.53.40 # since the rockbox site is down, can anybody send me some datasheets or specs of the s/pdif chip and the optical receivers of the h120 ? 16.53.51 # the cpu is compliant with IEC958-3 Ed2 and Tech 3250-E Standards only 16.55.47 # is it currently possible to monitor the toslink input signal with headphones? 16.56.02 # that's s/pdif and aes/ebu 16.56.23 # crwl: with few lines of code it should be :P 16.56.38 # the headphone out in h100 series should be of quite good quality, but my soundcard's one might not be 16.56.46 # so it could be used as a kind of sound card.. :P 16.56.53 # and i have optical out on the sound card 16.56.57 # without any resampling it should be easy to reroute the digital input to the dac 16.57.07 # IEC958-3 Ed2 : this is the cpu, and IEC958-3 Ed2 is aes/ebu ? 16.57.09 # i could actually use this if it was possible :) 16.57.46 # Hmm :) maybe i will try that :P 16.58.08 # i'd just need a toslink -> 3,5 mm (optical miniplug, what's its name?) adapter 16.59.43 # yes, i really would need one too. Currently i have used normal toslink cable and put it to the connector (some stuff over the cable to keep it on place) 17.00.05 # yes, that's not really handy :) 17.00.12 # i have no idea where i could find those cables 17.00.19 # yep :D 17.01.13 # http://www.biltema.fi/osteri/osteri.cgi?sivu=skriptisivut/index_kauppa.htm&linkki=24153.htm&tuote=24153&ryhmaid=118 17.01.13 # the cpu is compliant with IEC958-3 Ed2 and Tech 3250-E Standards only 17.01.17 # where is this? 17.01.28 # zenx: on the cpu datasheet 17.01.50 # http://www.freescale.com/files/dsp/doc/ref_manual/MCF5249UM.pdf this? 17.01.57 # yes 17.02.03 # ok thx 17.02.07 # it just feels stupid to order some component worth 1 EUR from the net 17.02.12 # the cpu has builtin drivers for the optical interface 17.03.28 Quit tucoz ("Leaving") 17.16.45 Join matsl [0] (n=matsl@1-1-4-2a.mal.sth.bostream.se) 17.23.45 Quit webguest41 ("CGI:IRC (EOF)") 17.32.17 Quit Febs (Read error: 110 (Connection timed out)) 17.32.59 Join bagawk [0] (i=1000@unaffiliated/bagawk) 17.34.53 # found the Adat chip: http://www.wavefrontsemi.com/index.php?id=11,10,0,0,1,0 17.37.26 Quit muesli__ (Read error: 104 (Connection reset by peer)) 17.44.49 Join Lear [0] (n=chatzill@h36n10c1o285.bredband.skanova.com) 17.48.04 # well, spdif has a data rate of 2.8224 Mbit/s and Adat has a data rate of 12.288 Mbps, so it's unlikely that it could be used :-) 17.48.50 # heh 17.52.38 Join markun [0] (n=markun@bastards.student.ipv6.utwente.nl) 17.55.05 Join Dma-Sc [0] (i=Dma-Sc@ALagny-151-1-58-75.w82-121.abo.wanadoo.fr) 17.55.13 # hi 17.55.52 # hello 17.55.52 Quit zenx ("CGI:IRC (EOF)") 17.56.52 # i was wondering if i could get a complete listing of available wps tags somewhere? though i suppose it was on the bombed wiki :/ 17.57.28 # http://rasher.dk/rockbox/WikiRescue/CustomWPS-r1.29%20-%2009-07.html 17.57.29 # ? 17.57.59 # not entirely up to date.. 17.58.29 # Wow 17.58.36 # I had no idea rockbox was hacked 17.58.46 # No wonder my inbox seemed smaller... 17.58.50 # ah yes didn't tried google cache ;) 17.59.19 # thought this page is a handmade cache of google cache of rockbox wiki ;D 17.59.26 # thought > though 17.59.46 # yes, if you look at the directory it's in, you can see how much work rasher put into it 18.00.02 # so as soon as the wiki backup is restored it'll be no problem to put most of the changes back :) 18.00.26 # yes indeed a cool move :) 18.07.15 # wps formating options are quite complete, and with images support it gives a blast compared to ajb-player wps i used before ;) 18.11.16 Join wacky [0] (n=wacky@modemcable006.177-201-24.mc.videotron.ca) 18.11.30 *** Saving seen data "./dancer.seen" 18.14.28 Join noC|andY`fRa [0] (i=andy@dsl-084-058-119-156.arcor-ip.net) 18.22.18 # hey guys, something totally offtopic here.. 18.23.01 # I'm about to release a software instrument tuner, and I'd like to know what are the steps towards a free software release .. and I know you guys know about it 18.26.00 Join linuxstb [0] (n=5343d4aa@labb.contactor.se) 18.27.25 # wacky: Step 1 - Choose a license based on how you want others to be able to use your code. 18.29.07 # hey :) GPL is my friend 18.29.34 # linuxstb: btw, i got the iriver recorder screen basic functions working :) peak meter etc. 18.30.11 # Slasheri: Nice. Does that mean it's no longer in the debug menu? 18.30.34 # it's still in debug menu but there is now the "real menu" also :) 18.30.41 # i think i will commit after the feature freeze 18.31.00 # Are you using the existing (Archos) recording code? 18.31.05 # yes 18.31.14 # it's very usable 18.32.09 # Apart from a recording codec system, what's left to do? 18.33.19 # hmm, i think there is not so much left to do to support the full pcm recording functions the recording screen offers 18.34.01 # of course the codec support will be the hardest one (but still not very hard) 18.34.31 Join dropandho [0] (n=dropandh@cpe-24-193-36-91.nyc.res.rr.com) 18.34.38 # hey all 18.34.44 # hi 18.34.58 # you happen to notice that the wiki link on site is broken? 18.35.26 # amiconn, linuxstb, do you think would it be better to use the full buffer space while recording and spinning the disk up every 2-3 minutes or keeping the disk continously running? 18.35.51 # dropandho: the wiki is deleted by crackers 18.35.54 # Why would you want to keep it running continuously? 18.36.03 Join dpassen1 [0] (n=dpassen1@resnet-233-61.resnet.UMBC.EDU) 18.36.09 # spinning the disk makes noise in the recording 18.36.13 # linuxstb: i was just thinking what would be a better option 18.36.29 # wacky: hmm, yes.. when using the internal mic 18.36.35 # I though we could even try to eliminate these high frequencies with some algorithmes.. 18.36.40 # slasheri- man...did we loose anything? 18.36.42 # if you spinup/down the disk, does that mean that you'll end up dropping samples as per the iriver firmware? 18.36.47 # Why is recording any different to playback? 18.37.06 # dropandho: there is a backups about a month old and much of the contents have been recovered using the google cache.. 18.37.12 # yes, and even if your microphone is too close 18.37.15 # but there is still much work to do to put the wiki back online 18.37.42 # slasheri- great...this is pretty sad 18.37.45 # AliasCoffee: no 18.37.52 # we wont have that glitch bug 18.38.06 # :) 18.38.13 # was there anyone working on remote support ?! 18.38.28 # slasheri- dont u think someone should put a headline on the homepage calling for anyhelp with this....maybe they have it cached or saved 18.38.29 # i don't think anyone is working with it currently 18.38.31 # I got my LCD broken, and bought an iAudio (since H3xx is discontinued!) 18.38.39 # but I just *want* to run the Rockbox somewhere, anywhere! 18.38.57 # wacky- there was one guy working on a patch...xavier or something...it never got committed tho 18.39.06 # dropandho: hmm, i don't maybe. But i think any help is greatly appreciated when the wiki is up again (restoring the pages etc.) 18.39.14 # maybe=know 18.39.26 # yeah I know.. that's the version I'm running.. but it's nothing complete and up to date with the latest features 18.40.19 Join Febs [0] (n=Febs@207-172-122-81.c3-0.rdl-ubr4.trpr-rdl.pa.cable.rcn.com) 18.40.45 # Slasheri: Spinning all the time is bad. It literally eats battery power 18.41.07 # 2-3 minutes is definitely worth it 18.41.10 # amiconn: good, i thought that also. So it's then good to spin it down 18.41.31 # I did some measurements with video playback on archos, which needs to rebuffer every ~25 seconds 18.41.47 # Even then it's still better to spin down in between 18.42.03 # hehe, nice 18.42.09 Join wacky_ [0] (n=wacky@modemcable006.177-201-24.mc.videotron.ca) 18.42.14 Quit wacky ("ahuh") 18.42.29 # slasheri- i think it is important to let folks know this happened on the front page...and solicite help...how else are people suppose to know? 18.42.40 # It'll probably not worth to spin down on archos with upcoming wav playback, at least at full 44.1/16/stereo 18.42.58 # This will need to rebuffer every ~10 seconds... 18.43.12 # Same for wav recording of course 18.43.51 # hmm, that's quite often 18.43.59 # yup 18.45.09 # wacky_: I'll probably look into making a remote-only build for iriver, i.e. using the remote lcd *instead* the main lcd 18.45.22 # ...hoping that this will help H3x0 development 18.45.36 # amiconn- nice..thanks for the remote work....ive been waitin for that! 18.45.49 # amiconn- it is hard to make the 2 work at the same time? 18.46.32 # dropandho: This won't be the "real thing", but a hack to ease H3x0 development. It allows to make a bootloader for H3x0 without having an LCD driver for the colour lcd 18.46.45 # oh yeah ?! 18.46.50 # It'll probably be easier to work from there... 18.46.57 # is that something possible right now ? 18.47.13 Nick wacky_ is now known as wacky (n=wacky@modemcable006.177-201-24.mc.videotron.ca) 18.47.32 # got it- thanks 18.51.49 Quit bagawk ("Leaving") 18.53.42 Join Dan [0] (i=Bollocks@tredwell.plus.com) 18.56.46 # amiconn - is it something really involving ? or is the code disposed to that quickly ? 18.58.43 # question tho...i know you guys are all about being efficient...so why would folks jump to develop h3x0 if h1x0 isnt complete 19.01.41 # hehe, rockbox will be never complete :) 19.01.58 # there is always something to develop 19.02.29 # hehe- i understand that 19.02.48 # but there hasnt even been an iriver release...so why jump to the next model? 19.03.03 # yes, that's true 19.03.35 # you guys are in a feature freeze...to make sure the other models are cool 19.03.42 Join DangerousDan [0] (n=Miranda@newtpulsifer.campus.luth.se) 19.03.59 # :) 19.04.17 # dropandho: It's not "jumping to the next model", but extending the user and developer base by another model 19.04.55 # The H3x0 is similar to the H1x0 hardware-wise, so it should actually push forward iriver development 19.05.53 # ok- sold! 19.05.53 # hehe 19.06.07 # i guess im greedy...and i wanna see my guy running nice 19.06.09 # thanks all! 19.15.36 Join muesli- [0] (i=muesli_t@Bc1fb.b.pppool.de) 19.19.05 Quit dropandho () 19.35.37 # amiconn - I was just wondering if "compiling a version with native remote support" was something I could put some time into 19.35.44 # or if it was something very involving 19.40.31 # can someone help me with a perl problem? 19.41.07 Quit Seed (Read error: 104 (Connection reset by peer)) 19.41.11 Join Seed [0] (i=ben@l192-117-115-168.broadband.actcom.net.il) 19.41.22 # I want to install a module locally. How can I use this in a perl script? 19.42.01 Join webguest79 [0] (n=81b17b04@labb.contactor.se) 19.42.42 Quit Dma-Sc (Read error: 110 (Connection timed out)) 19.42.42 # bluebrother: does export PERLLIB=/home/user/lib:$PERLLIB work for you? 19.43.34 # and use the module like you normally would. Like use module in perl. 19.43.46 # i.e in the script 19.44.21 Ctcp Ignored 1 channel CTCP requests in 0 seconds at the last flood 19.44.21 # * bluebrother^ tries 19.45.26 # interesting comments about the speed of Ogg: http://www.gizmodo.com/archives/ogg-vorbis-on-ipod-a-rebuttal-015738.php 19.45.42 # Has anyone considered putting codec code in IRAM? 19.46.02 # isn't that what is done at the moment? at least parts of it 19.46.32 # linuxstb: It's way better to use IRAM for data than for code on coldfire 5249 19.46.32 # Only data is in IRAM (AFAIK) 19.46.42 # oh, sorry 19.46.52 # Some code is in iram, but no codec code 19.47.06 # amiconn: Why is is it better to use IRAM for data? 19.47.16 # amiconn: actually, a few Tremor functions are in iram... 19.47.35 # There are two reasons. (1) The 5249 has an instruction cache, but no data cache 19.48.48 # (2) Uncached instructions are loaded from dram using burst mode. 19.49.04 # So basically, the speed-up of putting code in IRAM is minimal? 19.49.31 # Using burst mode for data is only possible with movem, and only if the data is line aligned 19.50.25 Quit webguest79 ("CGI:IRC (EOF)") 19.51.20 # I'm wondering about a comment about a benchmark for Coldfire FFT code: "Without invalidation of all cache locations program requires even more cycles, than in the case when cache is disabled." 19.52.30 Quit Febs (Read error: 104 (Connection reset by peer)) 19.55.27 # Lear: Some core code is in iram too (at least memset, memcpy and lcd_update irrc) 19.56.11 # And the Tremor functions put there are the ones that are called _very_ often... 19.57.08 # Yes, it should pay off to put functions in iram that are called often, and from various places 19.57.48 Join cybernetseraph [0] (n=cybernet@tor/session/x-2a1dc73876c1b5c3) 19.58.14 # The coldfire icache is direct mapped, so depending on the alignment code will sometimes get flushed from the cache due to cache aliasing 19.58.14 # Hey, just thought i'd mention that the wiki on rockbox.org appears to be down. 19.58.51 # if you look at the front page, it clearly states that the wiki was deleted 19.58.55 # it is being worked on :) 19.59.15 # fuzzie: oh, sorry. Must have missed that. 19.59.29 # must be one of those days. 19.59.50 # I'd say that information is a bit easy to over-read. 20.00.02 # oh, that's it. i hadn't reloaded the site since i loaded it, and that wasn't there when i first surfed over. 20.00.04 # if you need info from it, rasher has put the google cached versions at http://rasher.dk/rockbox/WikiRescue/ for now, until the backup is restored 20.00.18 Join Dma-Sc [0] (i=Dma-Sc@ALagny-151-1-47-210.w83-114.abo.wanadoo.fr) 20.00.24 # or, the google cached versions of anything recently modified. 20.00.30 # thanks. I was just checking up on how the iriver support was coming along 20.01.22 # for wps, it would be cool to be able to display several values one after the other (with timer stuff) in a condition case 20.03.43 # Well thanks for the info. I'm no good at audio/embedded development, so good luck guys, i'll keep checking back. Then again, do you have some donation interface? I get my student loan and i'd happily chuck some change your way. 20.05.23 # cybernetseraph: There's a link on the front page... 20.06.11 # god, i really am dim witted today. Thanks for the lack of flaming stupid questions. i think i need more coffee. Goodbye all. 20.07.03 Part cybernetseraph (""shutdown -h now"") 20.07.10 Quit edx (Read error: 110 (Connection timed out)) 20.09.40 # did noone backup the wik? 20.09.43 # *wiki 20.10.02 # the last backup is a month old, hopefully it'll be restored today sometime 20.10.17 # damn 20.10.35 # but that page of rasher's has almost all the changes up to the point of deletion 20.10.39 # any ip logs? 20.10.41 # so it'll just be a little work to get it back up to date 20.10.47 # and, yes, it was an russian ip 20.11.00 # well 20.11.15 # just executed 'rm -rf /' through the exploit, no local exploits or anything, so logs/system/etc are intact. 20.11.31 *** Saving seen data "./dancer.seen" 20.11.32 # have you checked for a proxy on it? 20.12.58 # It was a dialup ip iirc 20.13.42 # hmm 20.14.00 # 85.140.9.74, which resolves to something with 'pppoe' in it, which seems more likely to be broadband 20.14.21 # That sucks 20.14.34 # pppoe = adsl 20.14.43 # usually 20.14.48 # yeah 20.14.58 # ill scan it 20.15.41 # did we lose all of the irc logs too? 20.15.43 # that'd suck 20.16.07 # they're fine 20.16.12 # only stuff owned by the apache user was lost, afaik 20.16.16 # ah 20.18.05 # port 21 is open on eit 20.18.13 # but its not an ftpd i dont think 20.18.20 # *it 20.18.36 # i'd expect it's a dynamic ip anyway 20.18.52 # yes, pppoe is usually dynamic too 20.18.58 # mine isnt 20.19.39 # hmmm 20.19.40 # has anyone emailed abuse@ ? 20.20.40 # there have been a number of *.pppoe.mtu-net.ru visitors to #rockbox 20.21.02 # hmm 20.21.11 # how many? 20.21.42 # recent logs? three different people 20.22.09 # hmm 20.22.23 # shrug 20.22.29 # * Rick goes back to idling like he usually is. 20.22.38 # lol 20.22.58 # well 20.23.03 # heres what id to 20.23.22 # scan the ips for vulns 20.23.39 # what good would that do? 20.23.45 # if they can be rooted easily then he was running proxies off a botnet 20.24.44 # then you could root them and sniff his net out if that was the case 20.24.52 # then take it from there 20.25.23 # email abuse@ first though 20.26.18 Quit muesli- (Read error: 104 (Connection reset by peer)) 20.27.06 Join Musicmad [0] (n=Musicmad@port547.ds1-oebr.adsl.cybercity.dk) 20.28.01 # hi guys - does somebody have an idea what is going on here? http://forums.rockbox.org/index.php?topic=1383.0 20.31.52 Join muesli- [0] (i=muesli_t@hmln-d9b8ef4e.pool.mediaWays.net) 20.31.52 Join webguest64 [0] (n=81b17b04@labb.contactor.se) 20.32.31 # Musicmad, sounds almost like the oppisite of what I was experiencing a while ago. I got a high souding noise on boot sometimes. 20.32.47 # webguest72: ok - never had that. 20.32.51 # Which was fixed in the v5 bootloader 20.33.14 # where the uda is reset early in the boot process 20.33.29 # ok - I have tried with a recent build - still no sound in the morning :) 20.34.30 # annoying, so do you think it has to do with a build, or bootloader? 20.34.42 # Like, was this introduced lately? 20.35.11 # no idea actually - I _think_ it has been like this for 3-4 weeks. 20.35.22 # But I believe there are minor hw differencies in the different h120/h140's 20.35.30 # mine is a 120 20.35.32 Join solex [0] (n=jrschulz@d083052.adsl.hansenet.de) 20.35.50 # As I and a couple of others had this noise on boot (sometimes), where others didn't 20.35.59 # anyway - a reboot is pretty fast, but in the long run it would be nice to avoid it. 20.36.05 # true 20.36.08 # Musicmad, :) 20.37.11 # And it's hard to find out what causes it, as it is occasionally. But, we were able to fix the issue I was having. It just takes some time 20.37.32 # I mean, find and fix 20.37.56 # yeah - I don't know if any info gathered from the debug menu will help? 20.39.04 # If you are able to found out as much as possible when this happens, and maybe suggest something to the devs later on. 20.39.16 # you will be more likely to see a fix. 20.39.47 # I know - trying to establish a pattern. 20.39.54 # Like, what do you think causes it. (good) 20.40.17 # If there is something that can trigger this. 20.40.30 # yeah I know about good bug reports thanks :) 20.41.03 # I had my issue maybe twice a week. It was the usb-bootloader that narrowed it down, as the noise were present at that stage. 20.41.28 # Which meant that it couldn't be the firmware, as this wasn't loaded at that time. 20.42.16 # Musicmad, hope you'll find this out. gtg. 20.42.21 Part webguest64 20.47.01 Quit solex_ (Read error: 110 (Connection timed out)) 20.50.40 Quit muesli- (Read error: 113 (No route to host)) 20.55.16 Quit matsl (Read error: 104 (Connection reset by peer)) 20.55.30 Join stripwax_ [0] (n=stripwax@i-83-67-214-206.freedom2surf.net) 20.56.42 Join matsl [0] (n=matsl@1-1-4-2a.mal.sth.bostream.se) 21.06.15 Quit matsl (Read error: 104 (Connection reset by peer)) 21.07.42 Join matsl [0] (n=matsl@1-1-4-2a.mal.sth.bostream.se) 21.09.04 Quit wacky ("Leaving") 21.09.22 Join Shapeshifter [0] (i=user@80-218-25-181.dclient.hispeed.ch) 21.09.30 Join edx [0] (i=edx@p54A8579A.dip.t-dialin.net) 21.09.56 Join Jefe [0] (n=quickand@65-100-5-62.eugn.qwest.net) 21.12.42 # does anyone know where I can get a rfvMux filter? 21.14.26 Quit Jefe () 21.16.51 Quit Musicmad ("Trillian (http://www.ceruleanstudios.com") 21.17.10 # doesn't rockbox handle dir based playing like playlists, i mean with tracknumber and total tracks info for the current dir? i thought it did on my abj. 21.19.10 Part Shapeshifter 21.24.11 Join Zagor [0] (i=foobar@h63n1fls31o265.telia.com) 21.26.28 # Dma-Sc? 21.28.44 # ehh, yes it does... i was just using the wrong info (id3tag tracknumber instead of playlist tracknumber) X_X 21.32.03 # anyone know any technical reasons why 'id3 info' (or really 'tag info') is not an option on the context-sensitive file menu in the browser? 21.32.10 # would be v. useful! 21.32.19 Join muesli- [0] (i=muesli_t@Bc12c.b.pppool.de) 21.35.20 Quit muesli- (Client Quit) 21.52.32 Join billy1ear [0] (n=billy084@adsl-70-240-180-117.dsl.hstntx.swbell.net) 21.52.55 # is something wrong with web page 21.53.14 # yes, see front page 21.54.33 # guess i should learn to read. anyone have the latest manual, or know somewhere else to download it? 21.56.03 Join preglow [0] (n=thomjoha@hekta.edt.aft.hist.no) 21.57.19 # wiki still dead? :/ 21.58.13 # yes, we'll get the backup restored tomorrow 21.58.43 # ahh, you've got backups 21.58.44 # that's great 21.59.06 # apache logs intact? 21.59.08 # unfortunately not completely up-to-date (since Murphy is always watching) 21.59.16 # yes, we know who did it 21.59.21 # uhh 21.59.29 # dont be so sure 21.59.35 # just let me know if he's situated in oslo 21.59.50 # i'll blow up his mailbox or something 21.59.58 # well that's hard to say. naturally we only know the IP, which was a russian dialup. 22.00.00 # that ip DID have a proxy on it 22.00.01 # hi preglow 22.00.05 # amiconn: hi 22.00.09 # adsl 22.00.19 # Zagor: you can pretty much forget anything happening at all, then 22.00.41 Join rasher [0] (n=jonas@62.79.64.148.adsl.hs.tiscali.dk) 22.00.47 # i can see 2 options 22.01.03 # Dan: correct. same same. 22.01.07 # request logs from the proxy owner, which i doubt will work 22.01.19 # preglow: How costly would it be to derive the peak level from an mp2/mp3 frame? 22.01.19 # or root the proxy 22.01.31 # thatl get you an ip 22.01.39 # No full decode, just enough to obtain an approximately correct level 22.01.40 # if not then email abuse@ 22.01.42 # ? 22.02.31 # amiconn: hmm, lemme think 22.03.06 # you'd haveto do a full huffman decode, which will cost some cpu and quite a lot of memory 22.03.26 # you're thinking archos here? 22.03.30 # yup 22.04.09 # Meanwhile I suspect the peakmeter i2c to cause the recording glitches, but reading less often is going to be imprecise 22.04.59 # ...and since I'm thinking about scanning the frame structure anyway, I had the idea that it might be possible to obtain the peak level as well 22.05.02 # you've actually tried recording without the peak meter, or... ? 22.05.22 # I'm currently trying with a much lower peak rate 22.05.37 # *peek rate 22.05.51 # to be quite honest, i don't think you've got a chance 22.05.56 # especially not with mp3 22.06.27 # layer 3, i mean 22.06.39 # Peeking once per refresh (20 Hz) instead of a busy-yield cycle (roughly 600 Hz) 22.06.45 Quit DangerousDan (Read error: 110 (Connection timed out)) 22.07.11 # Hmm. 22.08.02 # as far as i know, there isn't much you can do apart from actually decoding the waveform to see where the peaks are 22.08.13 # allowing display timers in conditions cases for wps would allow nice play, pause, ff, etc... graphic animations ;) 22.08.24 # haha 22.08.34 # i can control my enthusiasm... 22.10.14 Quit Lear ("Chatzilla 0.9.68.5.1 [Firefox 1.4/undefined]") 22.10.31 # i mean sublines 22.10.55 # amiconn: but this will most certainly add bloat, just the huffman decoding alone requires quite a few lookup tables 22.10.56 # for use with timers ;) 22.11.34 *** Saving seen data "./dancer.seen" 22.15.42 # amiconn: the mas only records in layer 3, yes? 22.16.28 # yes 22.16.51 # Version 1 and version 2 layer 3. No version 2.5 22.17.12 # Max. frame bitrate is 192kbps 22.17.39 # well, you MIGHT be able to get some approximate peak info from the scale factors 22.19.05 # but even if it would work, it would probably be too inaccurate to be usable as a recording peak meter 22.19.24 # I wonder which part of decoding mp3 is the most computationally intensive 22.19.32 # Huffman decode? imdct? 22.19.52 # a split between imdct and filter bank resynthesis, i would think 22.20.48 # god, i wish i could fix that ugly imdct hack of mine soon 22.21.26 # Hmm. How much precision could one expect from using the scalefactors? 22.21.59 # It might still be better than these "quasi peak" readings from the mas 22.22.53 # Perhaps I should perform some experiments to determine how this "quasi peak" behaves for various input signals 22.22.54 # to be quite honest, i have no idea 22.22.58 # i'm not even certain it would work 22.23.28 # i don't know how well the scale factors correlate with the signal 22.23.50 # they're used before quantising to make sure all signals have a pretty uniform level 22.23.53 # to make the most of the quantiser 22.24.26 # and you have to combine those over all the frequency bands 22.24.40 # and you don't really know if some of them might cancel out to make a lower peak than you would expect 22.26.01 # if you're serious about finding out, hacking libmad should be easy 22.26.43 # i might even do it myself tonight 22.26.55 # since i got vaguely interested, heh 22.36.08 Join Arishon [0] (n=44df4f68@labb.contactor.se) 22.36.36 Part Arishon 22.47.37 Quit matsl (Remote closed the connection) 22.50.38 Join DangerousDan [0] (n=Miranda@newtpulsifer.campus.luth.se) 22.53.24 # implementing something like "?%id!=%Id" in wps would also be great :) 22.57.41 Quit dpassen1 (Read error: 110 (Connection timed out)) 22.59.40 Join linuxstb__ [0] (n=linuxstb@i-83-67-212-170.freedom2surf.net) 23.02.45 Quit Dan () 23.03.47 Quit billy1ear () 23.09.18 Quit linuxstb ("CGI:IRC (Ping timeout)") 23.12.41 Join BoD[] [0] (n=BoD@JRAF.org) 23.12.46 # Hello worldz0rz 23.12.47 Quit rasher ("Ex-Chat") 23.14.09 Quit linuxstb_ (Read error: 110 (Connection timed out)) 23.14.36 # so... what's up ? :) 23.16.26 # I was wondering if I should buy a comodore e-vic 20 23.16.45 # maybe it may be "rockboxable" :) 23.27.13 Join webguest13 [0] (n=d5ee45ef@labb.contactor.se) 23.31.44 # bye! 23.32.14 Quit Dma-Sc ("http://dma-sc.atari.org/") 23.35.41 Join coob [0] (i=pen0r@host-84-9-63-253.bulldogdsl.com) 23.42.12 Join ]RowaN[ [0] (i=a2b0y@82-43-212-52.cable.ubr10.newm.blueyonder.co.uk) 23.42.27 # <]RowaN[> quick question.. rockbox for h10 .. is that something that might happen? 23.42.59 # <]RowaN[> iriver h10 i mean 23.43.06 Join linuxstb [0] (n=5343d4aa@labb.contactor.se) 23.43.08 # h10 is closer to the ipod :) 23.43.24 # maybe, someday, but it's completely different from the existing iriver ports 23.43.34 # so if linuxstb gets his ipod port going, h10 would be possible 23.43.40 # coob: Do you know if the guy trying to port uclinux to the H10 got anywhere? 23.43.49 # nope 23.43.56 # stuck in bootloader alley i think 23.43.58 # linuxstb: you've got some ipod porting experiment going on? 23.44.20 # preglow: I'm going to start when my ipod arrives - which will hopefully be tomorrow. 23.44.39 # Unfortunately, I seem to have ordered an ipod with an unsupported LCD. 23.44.58 # yeah no luck on that yet 23.45.09 # linuxstb: excellent! 23.45.15 # maybe you'll be lucky and get an older 60gb... 23.45.32 # it's just a matter of disassembling anyway, no? :P 23.46.15 # linuxstb: well, if you get anywhere, chances are good i'll join in on the fun when i get some cashflow again 23.46.25 # once you manage to decrypt the fw :0 23.46.43 # coob: well, haven't you guys cracked that already? 23.47.03 # the dmca doesn't allow me to reveal that information 23.47.18 # well, it probably does, but i'm not getting shot for it. 23.47.29 # or th eu equivalent of the dmca 23.48.01 # preglow: we have been known to read the flash by beeping it out... 23.48.06 # i don't believe the dmca can give you any trouble on these grounds 23.48.22 # yes, but you're not a lawyer :) 23.48.51 # i can pretend i'm one 23.48.56 # Do we know the make/model of the LCDs in the ipod? 23.49.05 # linuxstb: there are many. 23.49.07 # coob?? 23.49.08 # you here? 23.49.10 # :) 23.49.30 # Is there a list anywhere? I'm having trouble finding detailed technical docs on the ipod. 23.49.48 # haha of course you are, there aren't any! welcome to apple :) 23.50.04 # http://ipodlinux.org/Generations 23.50.13 # I thought the ipodlinux project would have documented things though. 23.50.15 # no real lcd info there 23.50.38 # Even the source code doesn't really refer to the names of many components. 23.50.43 # coding is more fun than documenting. 23.50.59 # But it makes it hard for new devs to join in the project. 23.51.10 # brb 23.51.26 # true 23.52.03 # http://ipodlinux.sourceforge.net/download/ehd66753.pdf <- think thats the datasheet for the mono lcd 23.52.32 # bear in mind nearly all RE work is done without opening iPods 23.52.44 # i think bern's gf told him he couldn't open it :) 23.52.51 # (his original 2g) 23.53.56 # and no hardware other than what came in the box 23.56.08 # Is all the other important hardware on the 4G units understood now? 23.56.16 # i.e. enough to get Rockbox working? 23.56.38 # as far as i understood they haven't even been able to get both cpu cores working 23.56.40 # i would buy an ipod if rb would run on it 23.56.45 # HCl: yes we have 23.56.50 # oh, nice. 23.56.53 # just don't really utilise them 23.56.54 # since when? 23.56.57 # ages. 23.57.01 # <]RowaN[> i told my m8 to buy a h1xx, and he bought a h10 hehe, stupid twat 23.57.04 # i thought only one cpu core worked.. 23.57.08 # nope. 23.57.13 # and only since recently you could set the clock 23.57.18 # just had a lot of cache issues 23.57.28 # anways 23.57.29 # been able to set the clock for months 23.57.31 # anyways* 23.57.33 # goodnight 23.57.36 # yea, recently 23.57.37 # :p 23.57.48 # * The LCD uses the HD66753 controller from Hitachi (now owned by Renesas). 23.58.02 # thats the mono one, i think the photo stuff was all re'd from the bootloader.