--- Log for 18.06.105 Server: brown.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 7 days and 22 hours ago 00.00.33 Join muesli- [0] (muesli_tv@c-180-36-125.h.dial.de.ignite.net) 00.00.40 Join ehntoo [0] (~noclue2@24-177-147-34.dhcp.mrqt.mi.charter.com) 00.04.52 # still, i like it 00.05.00 # it's fancy and looks nice 00.05.14 # the glitching has got to go, however 00.05.59 Quit Philip_0729 () 00.08.20 Join webguest31 [0] (~449a2258@labb.contactor.se) 00.08.25 Quit muesli- (Read error: 104 (Connection reset by peer)) 00.10.51 Quit ghode|afk (Read error: 110 (Connection timed out)) 00.11.10 # oops 00.11.20 # i managed to seek further into an mp3 than rockbox had cached 00.11.23 # this it did not like 00.12.53 # Hi, about the latest sleep timer poweroff commit, was that maeant for sleep only or is idle poweroff included? 00.12.59 # amiconn: 00.13.13 # oops 00.13.34 # sorry bout the nick tabbing thing 00.13.59 # it seems idle poweroff still does not work with charger in 00.14.32 # That's on purpose 00.14.47 # oh 00.15.50 # instead of having no option b/c sometimes I do plug the iriver in to listen at night, however I want it to turn off when it's done 00.15.53 # can't we just turn it off or on whenever we want to? 00.16.06 # YOu can turn it off by hand 00.16.29 # I agreed that leaving it running at sleep timer timeout makes no sense, so I changed that 00.17.20 # However, both linuxstb and I agreed that it is better to not idle poweroff while the charger is connected 00.17.31 # i second that 00.17.35 # third 00.17.36 # ;) 00.17.41 # shush you! 00.17.41 Join Nuxator [0] (~chatzilla@abo-124-251-68.guy.modulonet.fr) 00.17.42 # smartass :P 00.17.45 # heh, ok 00.17.46 Nick thegeek_ is now known as thegeek (na@ti521110a080-1004.bb.online.no) 00.17.49 # hi 00.18.03 # What appened to cvs page on the website 00.18.10 Join thegeek_ [0] (na@ti521110a080-1004.bb.online.no) 00.18.12 # i dunno, is it broken? 00.18.16 # it's showind ihp100 and 300 twice 00.18.23 # showing 00.18.24 # oh that. 00.18.30 # yea, i was wondering about that too 00.18.32 Part thegeek_ 00.18.34 # Nuxator, I think that'll go away soon 00.18.36 # Bagder is the one to prod about that. 00.18.48 # aha. 00.18.55 Quit west-acre ("—I-n-v-i-s-i-o-n— 2.0 Build 3515") 00.18.58 # so we just gotta make about 12 more commits. 00.18.59 # ^^ 00.19.08 # HCl, that's about right 00.19.09 Join markun [0] (~markun@bastards.student.ipv6.utwente.nl) 00.19.11 # 12!! 00.19.29 # 16, actually 00.19.33 # alright, thx for the explaination guys :) 00.19.41 # Nuxator: Bagder changed the case of some build names (iRiver -> iriver) 00.19.43 # yea, 16 00.19.53 # * Nuxator have to read irc logs 00.19.58 Part webguest31 00.20.02 Join ghode|afk [0] (~dude@host-84-9-107-254.bulldogdsl.com) 00.20.11 Join webguest31 [0] (~449a2258@labb.contactor.se) 00.20.12 Quit webguest31 (Client Quit) 00.21.49 # preglow: Is there a reason why pcm_set_volume exists? 00.22.21 # I'd like to get rid of that, it would make implementing a cleaner way for volume & balance much easier 00.22.59 # ...featuring dB-linear mapping of volume 00.24.04 # amiconn: You will start working on the graphics api next week? 00.24.09 # yup 00.24.14 # great 00.24.18 # 1 week of vacation, time to code... 00.25.16 # A friend will bring his md player and optical cable next week. I want to take a look at auto track marking. 00.26.13 # I don't think many people will have use for it, but still.. 00.26.44 # that would rule for ripping vinyl 00.27.27 # bill20r3: I was talking about iriver H1xx -> minidisc 00.27.32 # ahh. 00.27.43 # well that would be ok too, I suppose. 00.27.43 # heh 00.27.57 # recording md's is a pita 00.28.08 # Don't know why people use a md player when they have an iriver.. 00.28.30 # The other direction could be interesting as well 00.28.37 # And for 80 minutes of music you have to wait.. 80 minutes 00.28.53 # amiconn: you'd have to ask linus 00.29.01 # I mean, when a cd or md player sends a track change signal, the iriver could auto-split the recording 00.29.08 # doesn't auto track marking work by introducing gaps? 00.29.25 # what do you mean db-linear mapping? 00.29.33 # HCl: No, you can send a track number in the subchannel of the spdif signal. 00.29.35 # _That_ would be great for ripping copy-protected cds 00.29.48 # HCl: When the tracknumber changes you split. 00.29.55 # ah 00.30.05 # nice 00.30.13 # also, as you can see, i do have internet at parents after all 00.30.21 # and i need to go to sleep.. 00.30.22 # gnight. 00.30.27 # rockboy asm core!! 00.30.28 # :-) 00.30.29 # Ah, I was wondering why you were still here :) 00.30.35 # good night 00.30.37 # preglow: The current volume mapping isn't linear, because 0..-52 dB uses 0.25 dB steps and -52.. -78 dB uses 2 dB steps 00.31.03 # ahh, i thought the scale was constant 00.31.30 # preglow: The point is wether there is a reason for having pcd_set_volume() 00.31.35 # *whether 00.31.47 # *pcm_set_volume() , bah :/ 00.32.41 # If not, I'll remove it and change uda1380_setvol to take 2 parameters, l & r 00.33.02 # amiconn: yeah, i was thinking of doing that 00.33.05 # would be cleaner 00.33.06 # Then the volume & balance handling is easily centralised in sound.c 00.33.16 # are you sure, btw? looks like the scale is 0.25 db steps all the way to me 00.33.28 # ...and would be very similar to the dac3550 version 00.33.33 Quit Nuxator ("Chatzilla 0.9.68.5 [Firefox 1.0.4/20050511]") 00.34.15 # Hmm, lemme check again 00.34.49 # the table is a bit misleading 00.37.37 Quit ghode|afk (Read error: 104 (Connection reset by peer)) 00.38.16 # preglow: It's definitely nonlinear 00.41.48 # 0..-52 dB uses 0.25 dB steps, -52..-66 dB uses 0.5 dB steps and -66..-78 dB uses 0.75 dB steps 00.42.10 # Fun, that 00.42.20 # it certainly is great it doesn't mention it 00.43.25 # Yes, strange. Table 33 says it's 0.25 dB steps full range, but decrypting table 34 tells you otherwise 00.43.40 # yeah, i see 00.43.46 # i wonder which is true... 00.44.06 # would be strange if someone devised that table in that manner for no reason 00.44.12 # In fact it can't be 0.25 dB for the whole range, because 255*.025 is 63.75, not >78 00.44.30 # *0.25 I mean 00.44.54 # ...and it would explain the rockbox volume behaviour in comparison to iriver 00.45.25 Quit _aLF ("Leaving") 00.45.26 # I remember someone telling here that rockbox 50% doesn't equal iriver volume == 20 00.45.28 # don't think i can detect changes as subtle as this 00.45.55 # No, but the effect cumulates as the curve is nonlinear 00.46.14 # a curve is always nonlinear.. 00.46.15 # i'm very seldom lower than -12db anyway 00.46.20 # HCl: no? 00.46.25 # no? 00.46.36 # i was of the impression that a linear curve is a straight line and not a curve 00.46.41 # Really? I'm often < 50 "rockbox-%" with earphones 00.46.47 # you can call all figures curves 00.46.51 # they don't have to curve 00.46.59 # at least that's my impression 00.47.10 # * HCl is more down to the ground than theoretical :) 00.47.17 # really 00.47.26 # depends on the earphones/headphones, i guess 00.47.40 # HCl: i'm a nice mix 00.47.43 # sleep now 00.47.45 # night 00.47.45 # preglow: Still, no obvious reason for pcm_set_volume()? 00.47.49 # night HCl 00.47.51 # none that i can think of 00.47.54 Quit t0mas (No route to host) 00.47.55 # HCl: nitey 00.47.59 # Then I'll ditch that 00.55.40 Quit pbvas ("Leaving") 01.05.46 Quit markun () 01.07.14 # preglow: There's another stage in the volume curve. 01.07.42 # -72..-78 dB uses 1.5 dB steps 01.10.29 # haha 01.11.16 # I'll extrapolate that to be -inf our virtual -84 dB 01.24.44 Quit mrlala (Read error: 110 (Connection timed out)) 01.36.07 Join Spack [0] (~50097d1f@labb.contactor.se) 01.37.18 Quit Spack (Client Quit) 01.39.14 Part leftright 01.40.11 *** Saving seen data "./dancer.seen" 01.40.16 # preglow: What do you think, can we ditch the playback test from the debug menu? 01.46.28 # oh yes 01.46.35 # i can see no further need for it 01.48.56 # Hmm, the audio circuit exhibits noticeable crosstalk 01.49.23 # oh? 01.49.31 # how did you notice it? 01.49.52 # You could test with the old code as well: 01.50.29 # Play some music and set balance to all left, then only listen to the right earphone 01.50.39 # It should be silent if there were no crosstalk 01.50.55 # more probably, this is a roundoff error bug in my code 01.51.09 # No, it's there with my new code as well 01.51.14 # strange 01.51.26 # ..and there is no roundoff error because it's working differently 01.51.41 # ...like the mas3507 (dac3550) code 01.52.02 # Only the values are different, and no prescaler to take into account 01.52.04 # almost all audiocircuits exhibit crostalk.. 01.53.10 # yeah, but i can't ever recall actually having heard it 01.53.24 Quit hicks (Remote closed the connection) 01.53.26 # if you can hear it, it's very significant 01.53.52 # Yeah, I noticed it only because I am testing my balance code, and set extreme values 01.54.00 # * HCl hears it most of the time when his brainwave generator tests for it... 01.55.37 Quit Kat ("Computer goes to sleep!") 01.56.36 # Hmm, strange. The archos player has way less crosstalk. I'll check the iriver fw 02.02.33 # It's the same with iriver firmware and with old rockbox code 02.02.50 # i think it's really rare to have noticable crosstalk 02.03.29 # On archos player it's barely noticeable at full volume, when the other earpiece already distorts 02.04.53 # Btw, I even tested without the remote control. 02.05.04 # I don't use the remote often 02.06.20 # i never use it 02.06.51 # but yeah, balance should digitally mute the other channel at extreme values 02.06.55 # so it is crosstalk you're hearing 02.12.39 # Hmm, I need to break plugin api backwards compatibility, now I'm obliged to sort functions :-/ 02.12.53 # could you stuff in a logf while you're at it? 02.13.04 # that's sorely needed 02.13.27 # granted it's quickly done 02.13.41 # i can't even remember how to handle variable arument functions 02.14.09 # That's not trivial. It shouldn't be there when building without logf support, and we need a macro in plugin.h 02.14.36 # why shouldn't it be there? it'll just be an empty call without logf support 02.14.52 # Variable argument functions are handled the same way as elsewhere 02.15.07 # The plugin api is just a struct containing mostly function pointers 02.15.20 # yes, i know 02.15.37 # i've never used a variable argument function anywhere 02.15.39 # not just rockbox 02.15.43 # never had the use for them 02.15.48 Part Moos 02.15.51 # You never used printf() ? 02.16.00 # sure, but never made on of my own 02.16.05 # ;) 02.16.08 # and to have logf support in plugins, you need to make a wrapper 02.16.30 # plugin_logf that wraps logf, since logf is just a macro if logf support isn't enabled 02.16.57 # YOu don't need a wrapper 02.17.10 # You need a macro though 02.17.21 # ROCKBOX_HAVE_LOGF should do 02.17.26 # ...and the macros has to make an assumption 02.17.37 # but then the plugin struct will be different for builds with logf support 02.17.50 # We do a similar thing for DEBUGF() 02.18.23 # DEBUGF() in plugins is empty for usual builds, and for debug builds it's rb->debugf() 02.18.42 # ..so it assumes your api pointer is called rb 02.18.42 # ahh, yes, of course 02.18.54 # you can just pass along the api pointer 02.18.58 # LOGF(rb, "%s", lol) 02.19.15 # Hmm 02.19.28 Join telliott [0] (~telliott@208-251-255-120.res.evv.cable.sigecom.net) 02.19.38 # cleaner than assuming it's called rb, if you ask me 02.20.02 # Are the current id3 database tools working? 02.20.12 # Cleaner, yes, but also a source of possible mistakes 02.20.41 # You can't check the correct number of arguments in variadic macros... 02.21.21 # indeed, no, but if you mean mistakenly passing your string as the rb pointer, then you'd have serious compiler error on your hands 02.21.23 # ...and it's easy to get this wrong: logf("%s", blah) in the core, but LOGF(rb, "%s", blah) in plugins 02.21.25 # telliott: should be 02.22.15 # preglow: ah, yes, pointer type mismatch 02.22.25 Join nsasch [0] (~nsasch@ool-44c16c10.dyn.optonline.net) 02.22.25 # "%s"->logf wont work 02.22.25 # heh 02.22.35 # the first argument to logf has to be string 02.22.38 # Not? ;-) 02.22.39 # so it will be caught 02.22.46 # hahah 02.22.50 # perhaps it will 02.22.55 # calling the address of a string is pretty 02.23.07 # calling the address of a string plus an offset 02.23.07 # haha 02.23.15 Quit telliott (Client Quit) 02.23.45 # Yeah, almost what seems to happen with the h1x0 sims on windows... calling the audiobuffer() array :-/ 02.24.11 # a queer business, that 02.24.49 # but yeah, assuming 'rb' wouldn't be the greatest sin in the universe anyway 02.24.55 # especially if DEBUGF already does it 02.25.07 # but not having logf support in plugins would be a great shame 02.25.14 # since it's really, really helpful 02.30.28 # but i gotta sleep 02.30.40 # later 02.30.48 Quit preglow ("leaving") 02.41.18 Quit RotAtoR () 02.42.40 Quit Sucka (Read error: 110 (Connection timed out)) 02.50.19 Quit nsasch ("Chatzilla 0.9.68.5 [Firefox 1.0.4/20050511]") 02.50.23 Join xen` [0] (~xen@pla25-1-82-227-196-9.fbx.proxad.net) 02.52.09 Join Febs [0] (~chatzilla@207-172-122-81.c3-0.rdl-ubr4.trpr-rdl.pa.cable.rcn.com) 02.55.59 Quit cYmen ("zZz") 03.05.55 Join mrlala [0] (~mistame@cpe-66-75-129-164.san.res.rr.com) 03.07.34 Quit gromit` (Read error: 110 (Connection timed out)) 03.09.22 Join lostlogic [0] (~lostlogic@node-4024215a.mdw.onnet.us.uu.net) 03.16.02 Join ashridah [0] (ashridah@220-253-120-77.VIC.netspace.net.au) 03.28.43 Quit Febs ("Chatzilla 0.9.68.5 [Firefox 1.0.4/20050511]") 03.32.53 Join kenshin [0] (~dave@c-24-17-8-193.hsd1.wa.comcast.net) 03.33.43 # anyone here running Debian? 03.34.07 # the cross-compiler i built the other day is crashing (internal error) when i do a "normal" build. 03.34.19 # simulator builds work just fine. 03.35.56 Join amiconn_ [0] (~jens@p54BD6F51.dip.t-dialin.net) 03.40.13 *** Saving seen data "./dancer.seen" 03.51.58 # mine's working okay. built gcc 3.4.4 for m68k the other day 03.52.15 Quit amiconn (Read error: 110 (Connection timed out)) 03.52.15 Nick amiconn_ is now known as amiconn (~jens@p54BD6F51.dip.t-dialin.net) 03.53.15 # hmm. maybe i should try 3.4.4. mine is 3.3.4. 03.54.05 # yeah, you'll need 3.4.4 for m68k. sh1 should be okay with 3.3.x 03.54.44 # is the WPS screen supposed to work in the simulator? 03.55.36 # i manage to kill the simulator when selecting an audio file. 04.06.15 Join QT_ [0] (as@area51.users.madwifi) 04.17.21 Quit QT (Read error: 110 (Connection timed out)) 04.48.29 Join webguest92 [0] (~5087fe04@labb.contactor.se) 04.49.46 Join asdsd____ [0] (~asdsd@h-67-100-24-230.miatflad.dynamic.covad.net) 04.49.59 # ugh, this playlist insert next, last qeue next last etc, and then trying to view whats been selected is driving me crazy 04.50.55 Part asdsd____ 04.51.51 # why not have the playlist menus the first electable in all the submenus 04.52.14 # electable=selectable 04.53.01 # and view menu the first selectable in that submenu 04.57.01 Quit kenshin (Read error: 60 (Operation timed out)) 04.57.38 # managing/viewing the playlist from the wps screen is a lengthy procedure 04.57.47 Part webguest92 05.05.26 Join kenshin [0] (~dave@c-24-17-8-193.hsd1.wa.comcast.net) 05.09.24 Join lostlogic_ [0] (~lostlogic@node-4024215a.mdw.onnet.us.uu.net) 05.27.39 Quit lostlogic (Read error: 110 (Connection timed out)) 05.40.17 *** Saving seen data "./dancer.seen" 05.43.47 Quit kenshin (Read error: 110 (Connection timed out)) 06.33.06 Join tvelocity [0] (~tony@ipa0.2.tellas.gr) 06.38.06 Join wacky_ [0] (~wacky@modemcable011.4-37-24.mc.videotron.ca) 06.38.12 # does Rockbox play midi files yet ? 06.46.17 # oh.. sorry, just read the wiki :) 06.50.59 Join Aramil [0] (~tony@ipa39.7.tellas.gr) 06.54.51 Quit Aramil (Client Quit) 06.57.04 Quit tvelocity (Read error: 145 (Connection timed out)) 07.05.52 Quit wacky_ ("ahlakj :)") 07.20.40 Join kenshin [0] (~dave@c-24-17-8-193.hsd1.wa.comcast.net) 07.24.47 # omfg headache sucks >.< 07.27.28 Join tvelocity [0] (~tony@ipa39.7.tellas.gr) 07.29.12 Join jdrews [0] (~jon@adsl-19-106-191.asm.bellsouth.net) 07.30.29 # awesome firmware you guys made 07.31.19 # i was wondering --- on the ihp120-- whenever you go to browse after playing a song-- you cant get back to the play screen. am i missing something? 07.31.31 # hm. no idea. 07.31.32 # try stop? 07.31.40 # at least, thats what would make sense to me. 07.31.40 # yeah that was my first reaction 07.31.51 # no dice 07.32.01 # i haven't looked at the interface yet myself, but i do plan to modify it at least in some ways 07.32.15 # but first i gotta finish the database stuff 07.32.19 # heh cool 07.32.34 # well its just a tiny little annoying thing anyhow 07.32.44 # *nods* 07.32.45 # so its not really crucial 07.34.05 Quit jdrews () 07.35.15 Join jdrews [0] (~jon@adsl-19-106-191.asm.bellsouth.net) 07.35.20 # wb 07.35.37 # thanks 07.36.06 # bah. i should've taken my iriver with me when i left to go to my parents :/ 07.36.31 # what in the name of god would convince you to leave it 07.36.38 # mine is grafted into my leg 07.36.40 # lol. 07.36.43 # well 07.36.50 # i'm pretty sick at the moment.. flue 07.36.57 # didn't think i would use it 07.37.00 # music does the body good 07.37.03 # and to be honest 07.37.07 # i just tried to put some music up 07.37.13 # and its just making my headache worse :/ 07.37.32 # ah-- must have been the specific music 07.37.43 # nah.. 07.37.46 # its a pretty soft song 07.37.50 # k's choice - almost happy 07.38.03 # i think ive run into that before 07.38.09 # k's choice rules 07.38.17 # disbanded right? 07.38.20 # i just happen to have the album on my laptop in ogg 07.38.33 # cause i needed to test oggs with the database creator.. 07.38.37 # no idea. 07.38.42 # i just listen to music 07.38.50 # i don't care about bands or "celebrities" that much. 07.38.56 # they're just people, don't see the big deal with them. 07.39.28 # nope i was wrong-- they're still together 07.39.33 # good 07.39.41 # that means i might get more good music :p 07.40.01 # still waiting for one of their albums to surpass their album cocoon crash 07.40.03 # yeah tehy should be due for new music-- last album was 2002 07.40.21 *** Saving seen data "./dancer.seen" 07.40.48 # alright im gonna go idle-- looking for shiny things in the house to macro 07.41.06 # macro? 07.41.23 # photography-- specifically big pictures of little things 07.41.28 # jondrews.com <-- thats me 07.42.11 # ah. 07.42.19 # flies are scary up close o.o 07.42.57 # pretty flower 07.43.10 # *looks at gallery* 07.43.28 # no idea what this is though. o.o 07.43.33 # blue... icey.. thingy.. 07.43.44 # yup thats what it is 07.44.05 # its inverted and color changed-- whats dark is light et vice versa 07.44.09 # they would make nice backgrounds 07.44.32 # but i'm not gonna replace the picture of my gf, obviously :P 07.44.40 # heh 07.45.38 # real nice pictures though 07.45.43 # thanks 07.46.07 # :) 07.46.35 # awright-- gotta run 07.46.36 # peace 07.46.41 Part jdrews 07.59.32 Nick ehntoo is now known as ehntoo|sleep (~noclue2@24-177-147-34.dhcp.mrqt.mi.charter.com) 08.07.04 Join Puro [0] (Cham_@gb.jb.74.247.revip.asianet.co.th) 08.07.50 # .th.. 08.07.50 # does anyone know of an open source firmware that would work with the Archos AV400? 08.08.14 # i *think* there was something for it, but i'm not 100% sure 08.08.21 # h 08.08.22 # hmm 08.11.40 # anyone tried building a cross-compiler for m68k-elf in debian amd64? 08.12.02 # hrm. 08.12.09 # preglow would probably be the guy to ask 08.12.16 # he has an amd64 i think 08.12.35 # i tried gcc-3.3.4 and compiling the compiler barfed 08.12.52 # i'm trying 3.4.4 hoping it will compile 08.25.01 # * HCl stares at another chat channel 08.25.14 # i swear. some males seriously need to see a doctor about their testosterone levels. 08.25.30 # dumb people are funny sometimes o.o. 08.26.49 # it's not polite to stare 08.27.48 # meh, online, they don't notice :) 08.35.27 # why can't compiling go faster!? ;) 08.38.35 # it can. 08.38.37 # o.o 08.39.16 # compiling gcc 08.42.25 # kenshin: afaik, you have to have gcc 3.4.4 anyway 08.42.30 # 3.3.4 doesn't support coldfire 08.47.48 # yeah. i've tried 3.4.4. 08.48.28 # can't get the cross-compiler built. gcc craps out building it. 08.49.45 # tried running it in a 32-bit chroot and that one won't build rockbox "normal". 08.54.30 # you might want to ask preglow about it.. 08.56.45 # who's preglow? 08.57.49 # mp3 codec person 08.57.52 # he has an amd64 08.57.58 # and he manages to build rockbox, obviously 08.59.08 # don't see him here. in the meantime i'll see what gcc-4.0 does! ;) 08.59.15 # mmm. 08.59.18 # good luck with that... 08.59.31 # unfortunately, i can tell you gcc 4, at least the version i tested 08.59.44 # does not produce a usable rockbox binary 09.00.06 # someone has to dig out why not and update the rockbox code... there's a potential speed boost to be gained from gcc 4 09.00.34 # i don't mind looking into why code doesn't compile 09.00.41 # it'll compile. 09.00.44 # but it won't work 09.00.44 # :/ 09.01.01 # i do this at work every day 09.01.15 # if you think you have a chance at fixing it, please :) 09.01.34 # i'm new to gcc-4.0 but my job is writing C code 09.01.56 Quit tvelocity ("Leaving") 09.01.58 # sooner or later i think i'll find it (if no one beats me to it) 09.03.54 # if my busted-arse gcc would build the cross-compiler without crapping all over it!! 09.06.10 Nick QT_ is now known as QT (as@area51.users.madwifi) 09.06.30 Quit ashridah ("Leaving") 09.19.27 Part kenshin 09.26.33 Join webguest37 [0] (~3ee7f502@labb.contactor.se) 09.38.37 # now backlight dimming uses only 2 interrupts / cycle and works pretty well :) 09.39.10 # nice 09.40.23 *** Saving seen data "./dancer.seen" 09.42.05 Quit webguest37 ("CGI:IRC (Ping timeout)") 09.49.32 Join Harpy [0] (gTOiFAi3rO@dsl-hkigw7wbb.dial.inet.fi) 09.50.13 Join ashridah [0] (ashridah@220-253-122-135.VIC.netspace.net.au) 09.56.08 Quit mrlala (Read error: 110 (Connection timed out)) 09.56.33 Join t0mas [0] (~Tomas@ip503c08d1.speed.planet.nl) 09.57.43 # hm 09.57.48 # pretty intresting bug 09.58.01 # when I select a new song from the file browser (iriver) 09.58.06 # while another is playing 09.58.21 # it does something to the uda chip... wich makes my amp. go mad 09.58.29 # loud buzzing sound.... untill the song starts 10.01.02 # (it does the same on shutdown) 10.03.23 # hmm, that is a problem with the line out 10.03.26 # try headphone jack 10.04.26 # I did 10.04.28 # does the same 10.04.34 # :/ 10.04.43 # do you disable the uda when no audio is playing? 10.05.18 # (it sounds like the 50 hz from the mains plug) 10.05.20 # wps calls audio_pause/stop when switching tracks (you can check it from logf) 10.05.27 # that's weird 10.05.36 # i have never had that buzzing 10.05.44 # plugin mains 10.05.49 # and connect it to an amp 10.06.13 # morning 10.06.20 # Hmm, maybe it's a grounding problem 10.06.29 # hi amiconn :) 10.06.30 # sounds like it 10.06.39 # but the iriver firmware doesn't have that problem 10.08.07 # No buzzing here 10.11.47 Join Deejay [0] (~Deejay@220-253-104-157.TAS.netspace.net.au) 10.16.07 Quit Deejay (Client Quit) 10.17.12 # Hmm, someone said we should allow leaving the menu again with the menu button (A-B)? I have to agree, and this is also done that way on ther other targets. 10.17.18 # Any objections? 10.18.39 # sounds good 10.19.13 # Same goes for settings 10.19.37 # (cancelling settings with both off and menu) 10.24.04 # Hmm, button lock with button combo in wps is unnecesary on iriver, I'd think? We have that lock switch... 10.24.36 # jup 10.24.48 # * t0mas is going to some family today... 10.25.02 # lucky me... they live next to snow world 10.25.14 # snowboarding in summer :D 10.25.20 Quit t0mas ("see you tomorrow") 10.26.45 Join webguest82 [0] (~5087e5a7@labb.contactor.se) 10.28.16 # the 'view current play list' menu is used frequently, is there any way of making it more accessable 10.28.38 # or with less key strokes 10.29.21 Join Nuxator [0] (~chatzilla@abo-124-251-68.guy.modulonet.fr) 10.30.04 # yes it should be in the playlist menu when whe push and let push the joystick 10.31.08 # It's like that in the user guide but it's missing in iriver build i wonder why 10.31.39 # The menu layout could be improved a bit, but there are surely many different opinions 10.32.12 # E.g. I almost never use the playlist viewer 10.34.17 # yes but in user guide there is a shortcut for playlist viewing just on top of insert , queue..... 10.34.49 # now that would be perfect for parties :) 10.35.04 # or a dj 10.35.14 # Another question why hd spin up when i pause my music? 10.35.15 # Hmm, this is harder to integrate main & remote lcd dimming to same timer.. But should be possible :) 10.35.37 # I think insert is a way more comfortable first menu item 10.35.49 # make it last then 10.36.27 # Slasheri: Hmm, might be difficult to dim both differently with the 2 ints/cycle approach 10.36.40 # amiconn: yep, that requires 3 interrupts 10.36.45 # yup 10.36.51 # yes last is fast too 10.37.22 # much more user friendly 10.37.47 # Slasheri: Different thing - I just noticed a bug with skip forward. It should do nothing when at the last track of a playlist, but it restarts that track 10.38.03 # amiconn: ah, that will be fixed :) 10.38.23 # Skip backward is totally broken, but I think you already know that 10.38.30 # yes it is..- 10.40.33 # And you can fast forward further than the fisrt 2mo buffering, guess you'll have to find a way to buffer the first track 10.42.00 # But even with those bugs rockbix is still a lot more fun than iriver's firmware 10.42.00 # It should always be possible to ffwd/rew outside of the buffered data, of course it has to reload then 10.42.32 # it's another solution (may even avoid this pb during buffering) 10.48.36 # pressing play (side button) when in 'view current playback' should return the wps, 10.49.37 # 'view current playlist' 10.52.34 # right joystick in 'view current playlist' is also unutilised 10.56.15 # hello. 10.56.40 # 'ello 11.02.01 Join ep0ch [0] (~ep0ch@82-133-67-85.dyn.gotadsl.co.uk) 11.02.08 # hello 11.02.57 # has anyone noticed that when a playlist has finished playing the cpu freq is still high? shouldn't it go to low when nothing is playing? 11.04.06 # also, is it possible to have the cpu freq displayed in a wps? 11.07.30 Join Febs [0] (~chatzilla@207-172-122-81.c3-0.rdl-ubr4.trpr-rdl.pa.cable.rcn.com) 11.22.51 Quit Nuxator ("Chatzilla 0.9.68.5 [Firefox 1.0.4/20050511]") 11.25.17 Join Philip_0729 [0] (~Philip_j_@user-3892.l6.c1.dsl.pol.co.uk) 11.26.30 # hello 11.40.26 *** Saving seen data "./dancer.seen" 11.41.47 Join LinusN [0] (~linus@labb.contactor.se) 11.44.15 # hi Linus 11.44.23 # hi 11.46.01 # i see you're taking on the h100 hacking with full speed :-) 11.49.22 # Did you check whether my changed MFDR(2) values in system.c are correct? 11.49.33 # I still have that laying around here uncommitted 11.52.25 # was that the page mode? 11.52.57 Quit xen` () 11.53.28 # ah, the i2c 11.53.36 # yes 11.53.42 # no, i haven't tested 11.58.21 Part Puro 12.00.03 # Does anyone else like ep0ch's idea of displaying CPU frequency in the WPS? I do, and have just implemented it. 12.00.30 Part LinusN 12.00.46 # Linus didn't :p 12.01.09 # I am sure it was just a coincidence... 12.01.21 # I see no point in having cpu frequency displayed in wps 12.01.41 # Then don't include it in your WPS. But would you object to me adding the option? 12.02.16 # I find it interesting for debugging purposes - to see which codecs need CPU boosts. AC3 doesn't seem to all of the time. 12.02.55 # Hmm, i think that even better would be to calculate and display average cpu speed in wps 12.03.13 Join muesli- [0] (muesli_tv@hmln-d9b8ef53.pool.mediaWays.net) 12.03.31 # Average over what time? 12.03.40 # beginning of the track 12.03.56 # For debugging purposes there's the debug menu 12.04.06 # g'mornin mate 12.04.07 # s 12.04.10 Join preglow [0] (thomj@s183a.studby.ntnu.no) 12.04.22 # amiconn: Yes, but that's not convenient when I'm listening to songs. I want the WPS, not a debug screen. 12.05.22 # You talked about debugging. 12.05.45 # I don't think an end user is interested in the cpu frequency 12.06.07 # Maybe debugging is the wrong word. I should have said "during development". 12.06.09 # so they wont have it in their wps... 12.06.28 # i think this is a nice idea, actually 12.06.51 # could give a nice indication of how much more we need to optimise a codec 12.06.56 # What if you wanted to try and test encoding settings to minimise CPU boosting. A normal user could experient without needing to play with the debug screen. 12.07.26 # I can understand some people not being interested, but what is the downside of implementing it? 12.08.21 # linuxstb, what does your implementation display? 1/0? or the full freq.? 12.08.33 # an average would be more helpful 12.08.45 # It displays "FREQ/(1024*1024)" - which I think is the frequency in MHz. 12.08.50 # cool 12.09.10 # why not just divide by 1000000 ? 12.09.12 # linuxstb: it should display FREQ/1000/1000 (not 1024) 12.09.14 # divide by a million no? 12.09.14 # linuxstb: If an average user doesn't use it it would be wasted code 12.09.15 # The FREQ define seems to be the way to do it - it's defined for all platforms. 12.09.51 # amiconn: yes, but it'll be useful during development 12.09.54 # we can always remove it 12.10.10 # amiconn: Based on that argument, the whole debug menu is a waste of code. 12.10.19 # Anyway, if you're still going to implement it, using output_dyn_value should be the easiest way of formatting 12.10.26 # its like a rpm idicator in a car, useful for racing 12.12.13 # but not required for everyday driving 12.13.08 # Slasheri, you get the bit about cpu freq being high after a playlist has finished? 12.16.01 Join LinusN [0] (~linus@labb.contactor.se) 12.16.35 # ep0ch: yes, that will be fixed :) 12.16.43 # ty :) 12.17.22 # please make the 'view current playlist' more accessable 12.17.43 # amiconn: output_dyn_value is a nice function, but seems overkill for this. I think the output will always be in MHz. 12.18.19 Part webguest82 12.18.48 # If you always want an integer value, then yes 12.19.00 # Might be sufficient after all 12.19.32 # maybe boost ratio is interesting as well 12.19.57 # time boosted vs time normal 12.20.11 # only that would be more than adequate, as a matter of fact 12.20.12 # maybe just a boost % value 12.20.15 # for developers 12.20.22 # or in average MHz :) 12.20.57 # average mhz might be interseting as well 12.21.57 # but boost % and average mhz could very well be in a debug screen 12.22.05 # LinusN: btw, what do you think about adding main lcd & remote lcd brightness configuration (0-100%, in 10% steps for example) to settings menu? 12.22.47 # LinusN: Do you remember why the last 2 conditionals in is_mp3frameheader() (lines 114..119 in mp3data.c) are there? 12.23.26 # and maybe some fade settings also.. 12.23.28 # Slasheri: as opposed to contrast? 12.23.49 # LinusN: yep, i have managed to dim the backlight continuously :) 12.23.52 # It seems the intention is to treat layer 1 data as invalid since the mas can't handle it, but it's looking (1) cumbersome and (2) even incomplete 12.23.56 # works nice 12.24.22 # Slasheri: fixed the glitches? 12.24.30 # Slasheri: you didn't say "backlight"... 12.24.36 # preglow: almost fully fixed 12.24.44 # ah.. but i meant backlight :) 12.25.22 # amiconn: i don't remember, , check the cvs log 12.25.24 # preglow: i am now working to implement maximum of 3 interrupts per pwm cycle to drive both backlights 12.25.42 # Slasheri: how did you implement it? 12.26.02 # LinusN: committed by linusnielsen as v 1.1 ... 12.26.13 # amiconn: hehe 12.26.33 # that code was borrowed, and i'm not sure i did that part 12.26.34 # LinusN: i initialized timer1 to create the pwm pulses 12.26.54 # LinusN: Ah ok 12.27.31 # LinusN: currently i tested it with main screen backlight: 2 interrupts / pwm cycle 12.27.37 # Will check the other conditionals again, should be possible to simplify these last 2 considerably 12.27.44 # backlight fades very smoothly 12.28.39 # Slasheri: interrupt frequency? 12.29.10 # Hmm, currently pwm cycle frequency is about 5ms 12.29.30 # Interrupt frequency varies a bit but there should be never more than 3 interrupts in 5 ms period 12.29.57 # Slasheri: how do you handle cpu boost? 12.30.23 # Hmm, just a thing. Interrupt driven pwm will probably cost more cpu than you'd think on first sight. Any interrupt breaks cpu sleep and causes at least one thread schedule cycle until all threads are sleeping again 12.30.29 # LinusN: it's still unhandled. There is very slight blink when cpu frequency changes.. 12.30.52 # amiconn: correct 12.30.53 # amiconn: Hmm.. 12.31.18 # at least it worked without problems for 500 kbit/s vorbis files ;) 12.31.41 # Slasheri: we're talking about battery consumption 12.31.58 # LinusN: of course.. that should be measured 12.32.24 # LinusN: (mp3data) Removing the last 2 conditionals fixes layer 1 for iriver, so it'll be #ifdefed out there 12.32.26 # and some menu option added to turn on/off the backlight dimming 12.32.34 # i can go with fading, but a constant pwm for "brightness" is a waste of battery 12.32.50 # We can do the same on archos player btw 12.32.51 # amiconn: good 12.33.00 # hmm, ok 12.33.19 Join MisticJeff [0] (~41ad57d4@labb.contactor.se) 12.33.23 Join leftright [0] (~5087e5a7@labb.contactor.se) 12.33.49 # Greetings... 12.33.59 # helo 12.34.22 # LinusN: but i try to take some measurements to see how much constant dimming would eat cpu/battery 12.34.58 # Slasheri: do so 12.34.59 # I hate to interupt but need to throw this out there for a Rockbox/iriver fan: display HDD usage in WPS, total/remain 12.35.36 # Slasheri: I agree that softly fading backlight might be a cool effect (unfortunately impossible on archos recorder), but constant dimming is unnecessary imho 12.35.42 # MisticJeff: what a funny request 12.35.49 # The backlight isn't exactly very bright anyway 12.36.36 # by no means 12.36.47 # amiconn: yep. i just though if it could be possible to keep for example remote lcd continuously on with a low brightness without much battery decrease :) 12.36.52 # but measuring power drainage might be interesting anyway 12.36.53 # hehe, i have been wondering... why do people want to stuff *everything* to the wps 12.37.35 # becuase they stare at it all the time while musics playing :) 12.37.37 # Slasheri: It might end up using more battery power for the cpu than it would cost to just leave the backlight at 100% 12.38.31 # amiconn: yep.. that has to be measured :) 12.38.51 # amiconn: i don't think its a question of battery power for the ones wanting to use it 12.39.00 # more a comfort/whatever thing 12.39.12 # leetness thing, you mean 12.39.28 # whatever floats your boat 12.39.32 # :) 12.40.14 # Slasheri: Btw, where did you put your interrupt routines? backlight.c? 12.40.28 # MisticJeff: is it something *you* want, or are you just the messenger? 12.40.33 # amiconn: yes.. everything is in backlight.c 12.41.06 # * LinusN has updated the iriver schematics btw 12.42.21 # yeah, saw 12.47.03 Join hicks [0] (~hicks@3484ea817d4da2b6.session.tor) 12.53.54 # Slasheri: so is the glitches fixable? 12.54.17 # preglow: yes they are (at least if cpu frequency is not changed during fading) 12.54.27 # Slasheri: well, that's a fairly common occurance 12.54.53 # the frequency could be boosted/locked so there will be no glitches 12.55.05 # Slasheri: Do you change the timer interval for different cpu frequencies? 12.55.09 Join Audiophil [0] (~c1d85c22@labb.contactor.se) 12.55.22 # Slasheri: or you could just lock the brightness at a specific setting before a cpu_boost 12.55.26 # amiconn: yep, at every interrupt the correct frequency is calculated 12.56.04 # frequency=intervall 12.56.34 # I think that it might help to avoid glitching if the total interval (Ton + Toff) is a constant number of cycles, regardless of frequency 12.58.39 # Hmm, maybe. Or TRR1 could be updated on every cpu frequency change. That should also fix it 12.58.52 # now some food :) -> 12.59.42 # slasheri: anything new on the dim lights? 13.07.19 # LinusN: Indeed the 2 checks in mp3data.c just filter out layer 1 files in a cumbersome way 13.08.13 # filtering out layer1 files should just be a compare 13.09.38 # Audiophil: yes, now testing dimming remote and main screen at same time 13.10.35 # available in bleeding edge release? 13.10.46 # not yet 13.11.02 # pity 13.11.45 # i will commit it as soon as the code is stable and clean enough 13.11.56 # yep, good! 13.12.35 Quit edx (Read error: 110 (Connection timed out)) 13.12.40 # someone should make a wps-simulator/editor 13.13.05 # too bad i don't know any programming languages :/ 13.14.26 Quit muesli- (Read error: 113 (No route to host)) 13.18.24 # is the peakmeter not functioning on the iriver port? 13.18.37 # no 13.18.52 # oki 13.18.55 # :) 13.19.06 # that will be implemented later 13.19.20 # how does the peak meter behave for archos? 13.19.25 # long decay? no decay? 13.19.33 # who needs a peakmeter? :> 13.20.53 # preglow: See General settings -> Display -> Peak meter 13.21.25 # but i encountered one error, the recursive folder adding to playlists only works 1 level 13.21.52 # if i add album\*.mp3 it'll work, but artist\album\*.mp3 won't work 13.31.17 # my, musepack seeking will be a hack 13.34.11 Part LinusN 13.34.20 # I'm an old hack too, but I still manage to get through life fine :) 13.34.35 Part MisticJeff 13.40.29 *** Saving seen data "./dancer.seen" 13.41.07 Join gromit` [0] (~gromit`@ras75-5-82-234-244-69.fbx.proxad.net) 13.46.13 Join belgarath [0] (~acd4fbae@labb.contactor.se) 13.46.26 Quit Philip_0729 () 13.52.47 # Hmm, does the remote lcd have a EL-backlight? 13.53.01 # It seems to be not dimmable (flickers and color changes) 13.53.44 # color changes? :) 13.54.18 # yep, from green to blue while it's being dimmed ;) 13.54.21 # several older panasonic mobile phones had changeable backlight colors, that was quite l337 13.54.32 # up to seven colors in one model 13.54.44 Join bipak [0] (~bip@p50885F4E.dip.t-dialin.net) 13.54.51 # :D 13.55.08 # ooh are there any other remote backlight colours? 13.55.41 # no, i just think that remote lcd has an el backlight and it does not like being dimmed 13.55.52 # ok 13.55.57 # el backlight? 13.56.13 # electro-luminense or something like that (not led backlight) 13.56.16 # but i am not sure about that 13.56.42 # at least the dimming is not possible because it flickers too much 13.57.08 # I will just comment out the remote lcd dimming code 13.57.41 # Yes el == electro luminescence 13.57.51 # not familiar with that 13.58.05 # You can't dim el backlights with pwm 13.58.30 Join cYmen [0] (~cymen@nat-ph3-wh.rz.uni-karlsruhe.de) 14.01.34 Quit bipak_ (Read error: 60 (Operation timed out)) 14.08.14 Join Chamois [0] (HydraIRC@champigny-5-82-226-182-23.fbx.proxad.net) 14.22.49 # i noticed that using the remote with rockbox firmware means it does not tick - will it still not tick when it has a WPS and scrolling? 14.25.27 # it will tick 14.25.34 # it sure does when i log to it while using it, at least 14.25.44 # but we might slow the speed of the transfer to make it less noticable 14.26.35 # ok 14.26.39 # just wondering 14.32.58 Join DMJC [0] (~DMJC@60-240-163-90.tpgi.com.au) 14.33.15 Nick ehntoo|sleep is now known as ehntoo (~noclue2@24-177-147-34.dhcp.mrqt.mi.charter.com) 14.45.20 # Hmm, i will now commit the initial backlight fader 14.45.33 # do so 14.45.35 # i thought it didn't work? 14.45.50 # i will just check the code that it should not break anything 14.46.10 # HCl: it works on main unit, not on remote lcd 14.46.16 # ahh. 14.46.17 # okay 14.46.18 # :) 14.46.38 # preglow: the cpu frequency change is still unhandled. please hack it if you have some time ;) 14.46.45 # no time :/ 14.46.57 # ok, i can look at it later 14.48.49 Quit cYmen ("zZz") 14.50.05 Join Moos [0] (moos012@m214.net81-66-158.noos.fr) 14.52.08 Join Teslacute [0] (Teslacuted@159-134-55-234.as1.cty.limerick.eircom.net) 14.54.06 Join edx [0] (edx@p54A8DF55.dip.t-dialin.net) 14.54.06 # preglow: committed, please test :) 14.54.35 # will in a moment 14.54.37 # just finish something 14.54.40 # good :) 14.56.06 # I've been reading the battery FAQ, specifically the bit about leaving the player connected to the mains for a while. Do you know whether that's the same on the H100's or just the Archos? 14.56.56 Nick Febs is now known as Febs_away (~chatzilla@207-172-122-81.c3-0.rdl-ubr4.trpr-rdl.pa.cable.rcn.com) 14.56.59 # dAMN, that's some interrupt handler :PP 14.57.31 # Teslacute: Hmm, i think you shouldn't worry about that. Irivers has litium polymer battery and hardware charging control so you can charge the battery anytime you wish 14.57.56 # And new replacement batteries are pretty cheap also :) 14.58.28 # Slasheri : the backlight is beautiful now 14.58.28 # preglow: Yep, a bit monster for an interrupt handler ;D 14.58.30 # congrats 14.58.36 # :) 14.59.59 # @Slasheri: I leave it plugged in for days on end and use it as the core of a hi-fi system, the charging indicator turns off and I presumed it left the batteries alone from then on and just ran itself off the mains but after the FAQ I'm not sure... 15.00.33 # Hmm, i think it should not charge the batteries when the led is off.. 15.00.44 # So it should be safe to leave it connected 15.00.47 # no i think it always runs off the battery even when connected 15.01.22 # fade looks very nice 15.01.25 # but seeing as its li polymer and not nimh it shouldn't really matter 15.01.27 # still a bit long for my taste 15.01.41 # maybe an option to choose the time 15.02.05 # preglow: that can be configured. Maybe some menu option should be added 15.02.29 # don't know if i'd say an option is needed 15.02.31 # would you be able to change the brightness of the led so that it is constantly dimmer than normal? 15.02.37 # but that's just my opinion 15.02.48 # preglow: i like a longer fade :) 15.03.23 # thanks guys, it only has to last a few years anyway. 15.03.30 # we've gotta make feel seeking play sound some time 15.03.36 # i hate not hearing where i am while seeking 15.03.44 Part Teslacute 15.03.59 # belgarath: it is possible but it might eat more battery than it saves 15.04.13 # it's worth testing, though, backlight does eat quite a bit 15.04.26 # ok 15.04.48 Join kenshin [0] (~dave@c-24-17-8-193.hsd1.wa.comcast.net) 15.05.30 # preglow: did you ever get a cross-compiler built in amd64? 15.05.35 # no 15.05.42 # i use my server box, which is 32 bit, for this 15.05.53 # damn 15.05.54 # trying to build the cross compiler on my amd64 box didn't work 15.05.57 # it bugged out 15.06.12 # yeah, i have the same problem you had 15.06.16 # the fade works really well i think 15.06.29 Join webguest83 [0] (~515649cd@labb.contactor.se) 15.06.37 # hi 15.07.02 # running in a 32-bit chroot seems to work but that's a pain 15.07.07 # oh yes 15.07.20 # not all things are 64 bit ready yet, i'm afraid 15.07.59 # i was reading misticriver forums before in h300 section and 1 poster said at moment playback is only a hack because it is a plugin and other plugins can interfere with it. Is this true? 15.08.15 # webguest83: it's not exactly a hack 15.08.18 # i meant for h100 of course 15.08.24 # webguest83: but we need to fix that, yes 15.08.48 # other plugins WILL interfere with it 15.08.57 # you can't use plugins while playing music currently 15.09.00 # but like i said, that'll be fixed 15.09.31 # i guess it would be silly to ask for a timescale since you guys work at your own pace on your own time 15.09.36 # indeed 15.09.38 # why does it matter? 15.10.06 # fixing this shouldn't be _that_ much of a job, so i hope it'll be done soon 15.10.08 # couple of weeks, perhaps 15.10.08 # why does what matter? 15.10.13 # but no guarantees 15.10.13 # k 15.12.24 # its just i thought this multi codec architecture and playback stuff that everyone was sort of avoiding until slasheri came along was the proper thing not a plugin. but what does it matter to me. ill just keep waiting (not in a bad way), rockbox is free 15.13.49 # i don't understand what you mean 15.13.55 # codecs will always be plugins 15.14.07 # if not, we'd have to keep all of them in memory at once, that'd be a waste of ram 15.14.13 # we just need to make a new kind of plugin for codecs 15.14.30 # so we'll have to types of plugins: ordinary plugins and codec plugins 15.14.39 # the second part is missing right now 15.14.53 # do those ipodlinux guys ever come in here? someone posted the other day about them getting video to work at 15 fps though with no sound currently and video is uncompressed. will rockbox be around 15 fps with sound or different? 15.15.00 Join markun [0] (~markun@bastards.student.ipv6.utwente.nl) 15.15.05 # no idea 15.15.06 # are OTF playlists on the db feasible? 15.15.24 # some of them come in here occasionally, yes 15.15.38 # uncompressed video isn't really feasible for the newer platforms 15.15.40 # Slasheri: The backlight dimming looks very nice! 15.15.50 # markun: thx :) 15.16.06 # yes its difficult to notice when the backlight comes in its so gradu 15.16.12 # *gradual and subtle 15.16.26 # its great 15.18.10 # hmm I've had the bootloader ready to flash for a while now, but I've held back to see if any scary bugs pop up. whats the longet you guys have used rockbox on h1x0 without a crash or needing reset button? 15.18.23 # dont know if fade in is a good idea, would prefer it to be instant, 15.18.24 # longest* 15.18.26 # if you're afraid of using the reset button, keep away 15.18.33 # ok fair enough 15.18.36 # it shouldn't happen much, but it'll happen 15.18.45 # no players have been destroyed using rockbox so far 15.18.49 # i've reset my player hundreds of times 15.19.09 # but that's because i'm a developer 15.19.10 # the other i saw someone say there were lots of 'crosslinked' sectors on their disk when they used some diskchecking utility 15.19.20 # what are these 'crosslinked' sectors? 15.19.26 # no idea, never heard of them 15.19.34 # other day* arg cant blody type 15.19.38 # bloody* :P 15.19.44 # yeah, i saw it, i still have no idea 15.19.48 # that might not be rockbox' fault 15.19.58 # when in usb mode, rockbox has no control over what's being done to the disk 15.20.13 # and that's when most of the disk writing is being done 15.20.24 # windows have corrupted my disks for me tons of times 15.21.00 # i need to send my h120 to germany/usa as my reset button is almost unusable 15.21.09 # never use sharp pins! 15.21.11 # ! 15.21.18 # i don't know how you guys manage it ;) 15.21.24 # i've used my reset button god knows how many times 15.21.27 # A 15.21.29 # it works perfectly still 15.21.32 # a paperclip works fine 15.21.40 # i use a tiny torx screwdriver 15.21.50 # it fits very perfectly 15.21.53 # so i guess that helps 15.22.34 # do any of you guys have the h3x0 or h300 remote yet? 15.22.34 Quit belgarath ("CGI:IRC (EOF)") 15.22.35 Join belgarath [0] (~acd4fbae@labb.contactor.se) 15.23.07 # webguest83: a crosslinked sector is when two files's FAT cluster sequences point to the same cluster 15.23.36 # and how bad is that? 15.23.53 # well, it means one of the files is broken, or both 15.24.01 # ow 15.24.28 # that can't be due to rockbox though? 15.26.09 # hehe, i have used 5mm led to reset the iriver hundred of times ;D 15.26.33 # hahaha 15.26.52 # yes, one of those big paperclips fits perfectly in reset 15.27.08 # thick paperclip could be better but i have leds and other components everywhere :P 15.27.19 # have one in my car, in the leater case's belt loop, and plenty at home and work. ;) 15.27.35 # now I have to spend ages wiggling around the reset hole with a paperclip... 15.27.39 # leather* 15.27.49 # and iRiver aren't responding at all to my emails 15.30.10 # well 15.30.12 # go figure 15.30.25 # i don't think they're eager to repair the damages you've done to a device not using their os ;) 15.31.18 # well I didn't really say that I was using rockbox 15.34.12 # but the normal firmware barely requires you to reset it though. 15.34.33 Part amiconn 15.34.37 # i've never had the ordinary firmware lock up 15.35.32 # no resets with R-box yet, 15.39.15 Quit webguest83 ("CGI:IRC (Ping timeout)") 15.40.31 *** Saving seen data "./dancer.seen" 15.55.42 Join ]RowaN[ [0] (a2b0y@82-43-211-171.cable.ubr10.newm.blueyonder.co.uk) 15.56.03 # <]RowaN[> love the backlight dimming guys =] 15.58.54 Join Lost-ash [0] (ashridah@220-253-120-95.VIC.netspace.net.au) 16.03.30 Quit DMJC-L ("Leaving") 16.09.19 # is the WPS supposed to work in the simulator? 16.11.02 Quit ep0ch (" Want to be different? HydraIRC -> http://www.hydrairc.com <-") 16.13.01 Join elinenbe [0] (elinenbe_@207-237-225-9.c3-0.nyr-ubr1.nyr.ny.cable.rcn.com) 16.17.19 Quit ashridah (Read error: 110 (Connection timed out)) 16.25.13 Quit leftright ("CGI:IRC") 17.17.07 Part preglow 17.33.23 Quit kenshin (Read error: 110 (Connection timed out)) 17.40.32 *** Saving seen data "./dancer.seen" 17.52.40 Quit Audiophil ("CGI:IRC (Ping timeout)") 17.55.12 Join Sucka [0] (~NNSCRIPT@host217-42-252-124.range217-42.btcentralplus.com) 17.59.36 Nick StrathAFK is now known as Strath (~mike@dgvlwinas01pool0-a247.wi.tds.net) 18.03.20 Join ashridah__ [0] (ashridah@220-253-123-16.VIC.netspace.net.au) 18.04.05 Nick ashridah__ is now known as ashridah (ashridah@220-253-123-16.VIC.netspace.net.au) 18.18.18 Join Audiophil [0] (~c1d85c22@labb.contactor.se) 18.22.19 Join kenshin [0] (~dave@c-24-17-8-193.hsd1.wa.comcast.net) 18.23.37 Quit Lost-ash (Read error: 110 (Connection timed out)) 18.24.55 Quit Audiophil ("CGI:IRC (EOF)") 18.32.07 Quit ashridah ("Leaving") 18.32.36 # mrf. 18.32.44 # its unusually quiet here. 18.33.14 # no 18.33.20 # it was just unusually loud the last days 18.33.24 Join hubbel [0] (hubbel@h7n2fls304o1033.telia.com) 18.35.32 Join Shagnar [0] (~tester@p54A0D53C.dip.t-dialin.net) 18.36.46 Join Audiophil [0] (~c1d85c22@labb.contactor.se) 18.38.03 # mm. 18.38.05 # i dunno. 18.38.33 # slasheri, how do i enable backlight dimming? 18.38.50 Join Tangleding [0] (~Tangledin@ARennes-351-1-17-146.w82-126.abo.wanadoo.fr) 18.38.57 # :) 18.40.10 # anyone else knows? 18.41.16 # what's the question? 18.41.24 # (not sure i can help) 18.41.28 Join as [0] (na@ti521110a080-1004.bb.online.no) 18.41.30 Quit thegeek (Read error: 131 (Connection reset by peer)) 18.41.41 # i just loaded a build of the latest CVS source and dimming was on by default 18.41.49 # indeed 18.42.10 # seems it isn't de/activable from menu for now 18.42.22 # "initial support" says the CVS log ;) 18.42.54 # i'm sure there will be a menu option within a week or so 18.43.01 # Slasheri: just wondering why you used TIMTER1 and not "tick_add_task" functionality? 18.43.08 # with no doubt 18.45.38 # anyway the dimming is nice to be true 18.45.40 # :) 18.47.02 Quit Audiophil ("CGI:IRC (EOF)") 18.47.23 # Something that would be nice as a fix for later 18.47.28 # : 18.47.53 # allow the remote EL-light to be always ON only with AC power 18.47.54 # ;) 18.49.25 # about future ticking issue 18.49.35 # i was wondering if something couldn't be done: 18.49.53 # what about freezing remote scrolling during HD access? 18.50.01 # it will fix the proble, no? 18.50.22 # (excluding during navigation of course) 18.51.33 # hubbel: Hmm, that's a good question. Nobody told me about that function ;) Maybe it would worked too 18.56.02 Join GovCon [0] (~I_am_not@159-134-96-248.b-ras1.lmk.limerick.eircom.net) 19.00.55 # Does anyone know why the settings need to be saved when you pause? (only when resume is enabled) 19.01.55 # Hi Markun 19.01.57 # :) 19.02.01 # hey 19.02.07 # really don't know 19.02.09 # :/ 19.02.32 # Me neither. I would guess it's only needed when you press stop.. 19.02.45 # in fact i'm not sure i understood 19.03.17 # you talk about the config saved in inacessible HD part? 19.03.22 # or *.cfg one? 19.03.43 # If you have resume enabled and you press pause during playback the settings are being written to the inacessible HD part. 19.04.01 # okay$ 19.04.07 # and not in STOP mode? 19.04.53 # let me check.. 19.06.52 # Hm, no, don't think so. 19.07.15 # Slasheri: think it would be cleaner to use that instead of using the other timer (which might be needed for some more critical function) 19.07.49 # Tangleding: I was mistaken, there is also HD activity if you press stop. 19.08.06 # okay no problem 19.08.10 # anyway 19.08.18 # i was just making hypothesis 19.08.25 # (i m not a developer) 19.08.31 # hubbel: that's true.. maybe it should moved to use kernel tick timer if it works that way 19.08.53 # Slasheri: think timer0 is at 100 hz 19.09.15 # ah! 19.09.19 # it's not possible 19.09.23 # (i imagine the safe HDD part couldn't be acceeded in play mode?) 19.10.10 # current implementation needs to change timer period and kernel timer resolution is not high enough for that 19.13.10 # 100 Hz could be enough for some kind of dimming, but it would require to toggle backlight on every tick (or to do some calculations) and pwm cycles couldn't be long.. So that would be pretty inefficient and could lead to visible steps during dimming 19.15.16 # have good time all 19.15.18 # :) 19.15.22 # i leave 19.15.34 # bye :) 19.15.38 # i go to sauna -> 19.15.39 # :) 19.15.44 # eh eh 19.16.04 # have a nice time then 19.33.39 # Slasheri: aha.. ok =) 19.37.29 Join yngwi [0] (~chatzilla@chello080109107064.1.15.vie.surfer.at) 19.40.35 *** Saving seen data "./dancer.seen" 19.42.03 Quit kenshin (Read error: 145 (Connection timed out)) 19.42.43 # Hi 19.42.44 # ive a question 19.44.59 # Ask away... 19.46.48 Join Spack [0] (~c1f90f5b@labb.contactor.se) 19.50.00 # hi 19.53.31 Quit Spack ("CGI:IRC") 19.54.19 Join mr_qno [0] (~c324ae72@labb.contactor.se) 19.59.36 # god i hate tv commercials 20.00.57 Quit mr_qno ("CGI:IRC (EOF)") 20.01.48 # HCl: great words of wisdom :-) 20.01.55 # :P 20.02.19 # i swear. some of these commercials make me want to torture the guy who thought of them. 20.02.41 # renault = bad commercials 20.02.47 # and theres this local digital tv company 20.02.50 # who has even worse commercials 20.04.05 # local commercials are always the worst 20.05.01 Quit markun (Read error: 113 (No route to host)) 20.09.02 # sorry i had to make some shopping 20.09.29 # it's about Lame and gapless 20.09.47 # is the issue solved or not? 20.09.55 # i tested with latest build 20.10.19 # and it was absolutely gapless when i used ff fw to get near track skipping 20.10.32 # but a firend told me he experimented same using ff fw 20.10.53 # but when he let the track ending "naturally" there was a little gap 20.10.59 # isn't this strange? 20.11.36 Join preglow [0] (~81f18ab7@labb.contactor.se) 20.11.53 # hello Preglow 20.11.54 # :) 20.11.58 # Tangleding: if you used ff/rw as well, then it's pure luck you got gapless 20.12.05 # seeking is very inaccurate 20.12.18 # that is, it's not pure luck, actually 20.12.29 # Hmm, forward seeking should be quite stable with mp3 :) 20.12.29 # but like i said on ha, gapless playback does not work currently 20.12.32 # indeed it's imprecise 20.12.42 # but not to much 20.12.48 # Slasheri: stable, yes, but not precise 20.12.58 # okay gapless still doesnt work 20.13.10 # preglow: yes, but at least it shouldn't now mess with the buffer position 20.13.12 # no it doesn't, and i don't know why 20.13.16 # i wonder why it was gapless using ff fwrd 20.13.36 # Slasheri: i managed to lock playback up when i seeked to a position that hadn't been buffered yet. this was yesterday 20.13.43 # Slasheri: i couldn't reproduce it, though 20.13.55 # ah.. interesting 20.13.57 # Tangleding: luck 20.14.02 # Tangleding: some files just wont work yet 20.14.32 # Slasheri: i tried the same thing afterwards, then it worked fine, but the time before that, the playback just stopped, with the hdd led blinking fast 20.14.40 # Slasheri: and it never stopped buffering, it seemed 20.14.46 # okay thats very curious 20.14.51 # indeed 20.14.54 # hmm, ok 20.15.29 # i will do some small redesing to buffer filling system so that it would never block. That should solve some problems 20.15.56 # Tangleding: don't hold your breath for gapless to work, unless amiconn or anyone else fixes it. i'm very busy right now 20.16.09 # Slasheri: that sounds nice 20.16.17 # but anywho, gotta go again 20.16.20 # later 20.16.20 # hm.. I'm using the remote-lcd to display recording waveform in realtime 20.16.30 # hubbel: 1!! 20.16.35 # cool :) 20.16.52 # hubbel: gotten anywhere with the recording test, btw? 20.17.06 # i've also hacked together with a buffers and threads 20.17.22 # so the dma1 notifies the main thread when data has arrived 20.17.28 # ok Preglow 20.17.31 # no problem 20.17.55 # hubbel: any commits coming up? :) 20.18.25 # maybe tomorrow 20.18.35 # :) 20.19.19 # must try to write wav to disk and see how stable the code is =) 20.19.59 # hmm, i suddenly find myself wanting to write an aiff codec plugin 20.20.04 # time to go before i actually do it 20.20.05 # later 20.20.14 Part preglow 20.20.52 # aiff? 20.21.00 # isn't a MacIntosh format? 20.21.20 # think speex is going to be very handy to record longs sessions of speach.. 8 kbit/s and 16 kbit/s sounds pretty nice actually, so we only have to spin up the harddisk once in an hour or so =) 20.21.49 # speech =) 20.22.52 # speex yes i Dled it yesteray 20.22.55 # in prevision 20.22.56 # :D 20.53.19 Join LinusN [0] (~linus@labb.contactor.se) 21.01.25 Join RotAtoR [0] (~e@c-67-162-206-66.hsd1.mi.comcast.net) 21.02.32 # Hi Linus 21.02.37 # yo 21.02.45 # ca va? 21.03.25 # ca va bien merci, et toi? 21.03.46 # trés bien merci :) 21.04.24 # still in vacations? ;) 21.04.37 # yup 21.04.51 # :) 21.06.15 # i hope you've got still a bit of your time for Rockbox ;) 21.06.46 # certainly 21.07.11 # :P 21.07.26 # Slasheri: i like the backlight fading, but i think it should only fade out, not in 21.08.10 # LinusN: Hmm, maybe that should be configurable.. I like fade in too :) 21.08.30 # maybe an option? 21.08.33 # definitely configurable 21.08.59 # i use to push a key to light the backlight, to see what's playing 21.09.15 # and then i don't want to wait for the backlight to go on 21.09.24 # ah, ok :) 21.09.39 # especially not when driving a car 21.11.51 # a question... i have a directory with 676 files in it 21.11.57 Quit Shagnar (Read error: 110 (Connection timed out)) 21.12.07 # when i try to open it, rockbox displays dir buffer full and displays only some of the files 21.12.14 # how can i increase the dir buffer? 21.12.29 # there's an option in the settings under "limits", however, changing it doesn't help 21.13.18 # CoCoLUS: there is a faq you know 21.13.41 # and a manual 21.13.50 # anyway, you need to reboot 21.14.10 # set the option, exit the menu back to the browser, then shut off 21.14.11 # ah... well *blush* 21.14.20 # hi linus 21.14.22 # :) 21.14.42 # well... with every other setting -not- needing a reboot... *cough* 21.15.12 # CoCoLUS: yes, the limits settings are special 21.15.31 # who would have reckoned such a windows-like behavour here? ;) 21.15.39 # anyway, thanks. 21.15.40 Join kenshin [0] (~dave@c-24-17-8-193.hsd1.wa.comcast.net) 21.16.21 # Tang: re 21.16.31 # CoCoLUS: it's because the buffers are allocated at boot 21.17.03 # I really like to be able to logf to the remote lcd =) 21.17.20 # hubbel: then do it 21.17.27 # is there a negative sideeffect when i increase them to much? 21.17.42 # CoCoLUS: smaller audio buffer 21.18.06 # is that noticeable when i increase it from 400 to lets say 1000 ? 21.18.07 # CoCoLUS: it's not that much of a problem on iriver, but it is on archos 21.18.11 # LinusN: i do it all the time =) 21.18.24 # hubbel: ah, i misunderstood 21.18.43 # CoCoLUS: no, you won't notice 21.18.59 # nice, thanks. 21.19.24 # btw, 676 files in one dir? you're nuts! 21.19.47 # sorry i went away 21.19.50 # back now 21.19.52 # :) 21.19.54 # I've just added logf to the plugin interface - can someone have a quick look to make sure it's OK? I've just duplicated the logic of the DEBUGF macro. 21.20.15 Join mrlala [0] (~mistame@cpe-66-75-129-164.san.res.rr.com) 21.20.28 # try it, if it works it's probably ok :-) 21.20.37 # any opinion on this: 21.20.38 # yeah it's somewhat of a remnant 21.20.48 # from the time where i didn't organize my music properly :) 21.20.54 # when 21.21.06 # about future ticking issue 21.21.21 # i was wondering if something couldn't be done: 21.21.23 # what about freezing remote scrolling during HD access? 21.21.32 # what about freezing remote scrolling during HD access? 21.21.40 # (excluding during navigation of course) 21.22.13 # Tangleding: why? 21.22.43 # the ticking isn't due to interference with HD access? 21.23.14 # LinusN: In which case, it's probably OK.... 21.23.29 # Tangleding: i don't know, but i doubt it 21.23.43 # okay 21.23.44 # does rockbox tick? 21.23.51 # indeed 21.24.01 Quit GovCon ("Client comited hari kari") 21.24.05 # it tick with audio playback and LCD scrolling 21.24.10 # i do'nt 21.24.15 # for me this like a beep but for remote 21.24.18 # remember who assured this 21.24.45 # i have to go now 21.24.47 # it's propably wanted by iriver fw 21.24.51 # cu around 21.24.59 # ciao 21.25.01 Part LinusN 21.25.09 # ciao 21.28.39 # Btw, recording is going pretty good.. I've just recorded > 1 minute to a wave file.. also I did a test to show the waveform in realtime on the remote lcd, very nice 21.29.42 # nice hubbel 21.29.43 # :) 21.29.51 Join GovCon [0] (~I_am_not@159-134-96-248.b-ras1.lmk.limerick.eircom.net) 21.32.49 Quit Sucka ("a bird in the bush is worth two in your house") 21.40.05 Join Yokalosh [0] (~Yokalosh@cpc1-cbly2-4-0-cust103.glfd.cable.ntl.com) 21.40.38 *** Saving seen data "./dancer.seen" 21.48.58 # when is the next version of rockbox coming out if ever? 21.52.22 # cool hubbel 21.59.22 Join MisticJeff [0] (~41ad57d4@labb.contactor.se) 21.59.46 # Greetings... 22.00.30 Join preglow [0] (thomj@s183a.studby.ntnu.no) 22.00.31 # Question for preglow or Slasheri: 22.02.14 # I don't like complaining but i have a request, anyway to have the ability to press any key when the backlight is off and have it just activate the backlight without actually activating the button function? 22.02.41 # hmm 22.02.48 # <]RowaN[> that'd suck during the daytime, when you couldnt tell if it was on or off 22.03.05 # <]RowaN[> you'd see the screen, press a button, and nothing would happen in effect 22.03.15 # well, you usually know if its on or off 22.03.20 # if you haven't touched it, it's off 22.03.52 # hmm, just a small thing 22.03.56 # i usually flip the hold switch on then off again to turn the backlight on really quick 22.03.56 Nick as is now known as thegeek (na@ti521110a080-1004.bb.online.no) 22.03.58 # <]RowaN[> what im saying is that in the daytime, you dont need to press once before you can "see" coz you can see anyway even with the backlight off 22.04.01 # on resume, it asks for PLAY button 22.04.08 # this is joystick press on irirver rockbox 22.04.11 # <]RowaN[> just press vol up/down 22.04.17 # but there is a dedicated play button too 22.04.21 # this is confusing. 22.04.53 # Hmm, i think that backlight should active when player is on hold and user presses any key 22.05.04 # <]RowaN[> who would i need to nag around here to get fade out on track skip option implemented? 22.05.10 # *activate 22.06.11 Quit Yokalosh (Read error: 131 (Connection reset by peer)) 22.06.15 # ]RowaN[: at least crossfade on track skip will be implemented later 22.06.39 # <]RowaN[> ok cool 22.06.52 # but maybe fade out only is a good idea if crossfade is not available at the moment you skip the track 22.07.18 # you can switch of fade out 22.07.24 # it's been in settings for a long time 22.07.44 # what do you think guys?? 22.08.09 # personally i don't think i'll ever need it, but i see how it can be useful, yes 22.08.12 # preglow, about the bass/treble settings, they are equal to the iriver settings, are they? 22.08.22 # CoCoLUS: should be 22.08.42 # nothing more agrivating that hitting the joystick to the right or left while a song is playing but the backlight is off and then skipping to the next song when all you wanted to do was turn on the backlight to see what was up 22.08.47 # because i got distortions using the same settings as with the orig. fw on some tracks 22.08.52 # noticable on the new jack johnson ;) 22.12.38 # didn't amiconn report something similar? 22.14.55 Join webguest08 [0] (~50b16d10@labb.contactor.se) 22.14.56 # ahhhh... MisticJeff solved own problem by realizing the record button currently does nothing while a song is playing, activates the backlight nicely. Back into lurkdom 22.15.08 # MisticJeff: well, let's hope that lasts... 22.15.20 # CoCoLUS: iriver firmware might be compensating by reducing the main volume 22.15.47 # and that could be tested/confirmed by doing... what? :) 22.16.29 # by doing the same in rockbox? 22.16.43 # and comparing the output 22.18.49 Quit webguest08 (Client Quit) 22.22.18 # <]RowaN[> but maybe fade out only is a good idea if crossfade is not available at the moment you skip the track 22.22.19 # <]RowaN[> What seems to happen when you skip tracks in winamp (when using DirectSound output plugin) is that the current song fades out quickly (in 500ms) but the next track seems to start almost immediately. It might sound strange, but I think its just perfect because its happy medium between crossfading and not crossfading - the next track starts immediatly (so you're not waiting around to hear it), yet the song you leave doesnt end 22.25.24 # <]RowaN[> basically the 2 songs are playing at the same time for a very small moment (1st track is fading, next track starts over the top at full volume) 22.25.39 # <]RowaN[> its very pleasing on the ears =] 22.26.19 # <]RowaN[> one of those features that is a pain to live without once you've got used to it 22.27.32 Quit mrlala (Read error: 145 (Connection timed out)) 22.35.51 Join asdsd____ [0] (~asdsd@h-67-100-24-230.miatflad.dynamic.covad.net) 22.37.34 Quit belgarath ("CGI:IRC") 22.38.10 Part asdsd____ 22.55.50 Quit GovCon (Read error: 110 (Connection timed out)) 22.57.24 Join StrathAFK [0] (~mike@dgvlwinas01pool0-a247.wi.tds.net) 23.04.14 Quit Tangleding (Read error: 54 (Connection reset by peer)) 23.07.22 Quit Strath (Read error: 110 (Connection timed out)) 23.11.56 Quit kenshin (Read error: 110 (Connection timed out)) 23.20.50 # cleaning 23.22.55 # need a roomba? 23.23.54 # I need clues 23.23.56 # :-) 23.24.13 # I wonder if the h300 has the same adc support has the h100 23.24.24 # as the... 23.24.37 Join Musicmad [0] (~Musicmad@port547.ds1-oebr.adsl.cybercity.dk) 23.27.05 # hubbel: just read the irc log. You did som recording on the iriver? 23.28.37 # yes, he did 23.28.42 # i also have done so ;) 23.28.55 Quit RotAtoR () 23.29.12 # ok :) - he just mentioned realtime display of the waveform being recorded. That would be a kick ass feature I think. 23.29.18 # yes, i agree 23.29.20 # it's very cool 23.29.43 # nice when checking for "overs". 23.29.52 # current firmware ready lacks in this aspect. 23.30.55 Quit soom () 23.32.38 Join ghode|afk [0] (~dude@host-212-158-195-215.bulldogdsl.com) 23.37.43 # Musicmad: yes, support for recording is on it's way 23.38.02 # great news. 23.38.38 # the keypad difference between the h100 and h300 is annoying to fix in the code 23.40.04 # It's a tradeoff when selecting size of each sampling-buffer, small is nice when you want a responsive waveform and large is nice because larger write's to the file is more battery efficient I guess 23.40.41 *** Saving seen data "./dancer.seen" 23.41.12 # Or one could use small dma transfers to get the waveform and delaying the write to file until a large-enough size has been sampled.. hm 23.41.34 # sounds good 23.49.28 # Bagder: i wouldn't say the crt0.S code is MCF5249 specific 23.49.38 # it's highly dependent on where peripherals are connected, no? 23.49.53 # true 23.50.17 # it really is h1x0-specific... 23.50.52 # I'll revert 23.54.42 Quit Nibbler (Read error: 113 (No route to host)) 23.55.30 # thanks 23.55.34 # no problem 23.55.34 # heh 23.55.50 # i thought about fixing that myself the other day, and thought about it