--- Log for 17.07.105 Server: kornbluth.freenode.net Channel: #rockbox --- Nick: logbot_ Version: Dancer V4.16 Started: 5 days and 15 hours ago 00.06.26 Quit Harpy (Read error: 110 (Connection timed out)) 00.09.57 Join webguest87 [0] (~51429ed6@labb.contactor.se) 00.10.09 # Hello all 00.10.17 # hi 00.11.08 # a quick question for the Bagder administrator :) 00.12.04 # why in the CVS buil table, the 2 colums of the Gmini port still apear ? 00.12.19 # because the columns are based on more data than what is shown 00.12.21 # i know it's not important 00.12.52 # are will always here? 00.12.56 # no 00.13.19 # i know this port is in "stand by" 00.14.25 # I would call it abandoned 00.14.48 # :) anyone worked on it since long time? 00.14.55 # nope 00.15.00 # been months since 00.15.10 # ok 00.15.31 # there was just one dev worked on it? 00.15.38 # yes 00.16.08 # difficult to port Rockbox alone, no? 00.16.20 # his computer broke down 00.16.28 # :( 00.16.31 # and he couldn't afford a new one 00.16.48 # not good for him 00.17.09 # personaly i'm iriver user 00.17.21 # one very happy user :) 00.17.25 # :-) 00.18.18 # i read in the logs of today maybe Slasheri'll go to imlement paek meter things 00.18.27 # it's very good 00.18.44 # *peak 00.19.31 # i love your Rockbox fw :) 00.19.40 # thanks 00.20.25 # and i love his "association" with the GPL concept 00.20.45 # not money way 00.20.54 # and free to code 00.22.39 # Bagder: think you in the futur (soon i hope), it'll be possible to have got a beep option like the original fw or most of music players? 00.22.52 # it's not a request just question :) 00.23.00 # what would that do? 00.23.17 # I mean, when would it beep? 00.23.28 # but yes, surely we can make it beep 00.23.39 # when pushed a key 00.23.57 # oh 00.24.08 # I always disable such stuff 00.24.13 # like mostly player music 00.24.14 # on every device I own 00.24.44 # you don't like it? 00.25.03 # I hate it 00.25.22 # :), scuse for this evocation in your brain :) 00.25.26 # hehe 00.25.35 # well, that's what options are for 00.25.52 # but it be very usual for lot of people i assume 00.26.01 # true 00.26.24 # think you it'll be dificult to add to options? 00.27.08 # I would guess that the most difficult part is to find someone who'll write the code for the feature 00.27.58 # yes i assume, just if one dev work on it, needed lot of codes? 00.28.08 # lot of time? 00.28.16 # for him 00.28.31 # that would depend on the coder of course 00.28.40 # :) of course 00.29.24 # for example, you, you are an experimented hackers 00.29.37 # no, it would not take very long 00.30.45 # sleep time 00.30.58 # have a good night 00.31.40 # thanks for your answers 00.32.44 # good night to all too :) 00.32.48 Quit webguest87 ("CGI:IRC") 00.34.35 Quit matsl (Remote closed the connection) 00.37.55 Join matsl [0] (~matsl@1-1-4-2a.mal.sth.bostream.se) 01.01.45 Join CBM-away [0] (~youshould@tc2-225-085.altelco.net) 01.09.12 *** Saving seen data "./dancer.seen" 01.37.48 # when a static variable is declared on a a1.c file does it get recognised if called by a a2.c file (included the a1.h)? 01.39.04 # also if someone could tell me where the tree initialization occurs when running rockbox I would be obligued 02.26.01 Quit matsl (Remote closed the connection) 02.32.02 Quit Moos (" Like VS.net's GUI? Then try HydraIRC -> http://www.hydrairc.com <-") 02.41.10 # good night all! I have to sleep! 02.41.13 Quit XavierGr () 03.07.53 Quit Sucka ("a bird in the bush is worth two in your house") 03.09.16 *** Saving seen data "./dancer.seen" 03.10.21 Join textchimp [0] (~chimp@ip67.net66.ipnetworks.net.au) 03.15.20 Join ashridah [0] (ashridah@220-253-123-31.VIC.netspace.net.au) 03.28.29 Quit Coldtoast (Read error: 110 (Connection timed out)) 03.54.14 Quit hicks (Remote closed the connection) 03.54.40 Quit cYmen_ ("zZz") 03.57.39 Nick CBM-away is now known as CheeseBurgerMan (~youshould@tc2-225-085.altelco.net) 04.05.34 Join QT_ [0] (as@area51.users.madwifi) 04.16.03 Quit QT (Read error: 110 (Connection timed out)) 04.16.03 Quit textchimp (Read error: 104 (Connection reset by peer)) 04.24.02 Quit CheeseBurgerMan () 04.24.35 Join CheeseBurgerMan [0] (~youshould@tc2-225-085.altelco.net) 04.43.05 Nick CheeseBurgerMan is now known as CBM (~youshould@tc2-225-085.altelco.net) 05.09.18 *** Saving seen data "./dancer.seen" 05.24.56 Nick CBM is now known as CheeseBurgerMan (~youshould@tc2-225-085.altelco.net) 05.33.37 Nick CheeseBurgerMan is now known as CBM-AFK (~youshould@tc2-225-085.altelco.net) 05.36.28 Nick CBM-AFK is now known as CheeseBurgerMan (~youshould@tc2-225-085.altelco.net) 07.09.20 *** No seen item changed, no save performed. 08.19.41 Quit pike (Read error: 110 (Connection timed out)) 08.27.59 Join pilled [0] (dearth@ip-130.net-82-216-140.issy4.rev.numericable.fr) 08.37.53 Quit pill (Read error: 110 (Connection timed out)) 08.37.53 Nick pilled is now known as pill (dearth@ip-130.net-82-216-140.issy4.rev.numericable.fr) 08.52.39 Join Coldtoast [0] (~edan@ppp111-3.lns1.hba1.internode.on.net) 08.53.59 Nick CheeseBurgerMan is now known as CBM-away (~youshould@tc2-225-085.altelco.net) 09.09.24 *** Saving seen data "./dancer.seen" 09.35.25 Join pike [0] (pike@c83-249-120-126.bredband.comhem.se) 09.42.30 Join Harpy [0] (LiZ63v73tt@dsl-hkigw7wbb.dial.inet.fi) 11.05.32 Join Lear [0] (~chatzilla@h143n1c1o285.bredband.skanova.com) 11.09.28 *** No seen item changed, no save performed. 11.09.40 Quit edx () 11.13.28 Join cYmen [0] (~cymen@nat-ph3-wh.rz.uni-karlsruhe.de) 11.24.23 Join matsl [0] (~matsl@1-1-4-2a.mal.sth.bostream.se) 11.30.47 Join edx [0] (edx@p54A8F533.dip.t-dialin.net) 11.31.10 Quit cYmen (Read error: 104 (Connection reset by peer)) 11.31.13 Join cYmen [0] (~cymen@nat-ph3-wh.rz.uni-karlsruhe.de) 11.37.34 # Hmm, my current implementation of the peak meter looks more like a spectrum meter.. 11.38.28 # Too fast? 11.39.38 # nope, it meters one fixed frequency.. Maybe something like 4 kHz 11.39.50 # i will try to fix that 11.40.01 # for example it igrones bass totally 11.40.34 # Aren't you just looking at peak sample values? 11.41.10 # hmm, we dont have peak values but we have to calculate tehm? 11.41.54 Quit cYmen (Read error: 104 (Connection reset by peer)) 11.41.54 # How else would you do it? 11.43.19 # Hmm.. currently i try to find min and max sample values between a specified period and then calculate average peak value for a longer period 11.45.39 # Doesn't the peak meter do some averaging as well? 11.45.51 # maybe i should first find the bias value and then base the peak readings on that 11.46.00 # then it might work better 11.46.39 # maybe, but it takes samples only ~20 times per second 11.46.53 # so we have to calculate some average also 11.49.42 # current implementation works well for higher frequencies but its more an eq analyzer than a peak meter 11.50.06 Join cYmen [0] (~cymen@nat-ph3-wh.rz.uni-karlsruhe.de) 11.50.15 # i will try that different bias thing when i get to home 12.07.23 Quit Seed (Nick collision from services.) 12.07.30 Join Seed [0] (ben@l192-117-115-168.broadband.actcom.net.il) 12.25.03 Join LinusN [0] (~linus@labb.contactor.se) 12.29.35 Join austriancoder [0] (~5078751e@labb.contactor.se) 12.29.41 # hi 12.29.47 # hi 12.48.05 Join Moos [0] (DrMoos@m29.net81-66-158.noos.fr) 12.48.18 # Good Day all 12.48.46 # hi 12.50.39 # LinusN: we should maybe rename i2c-h100 to i2c-coldfire? 12.53.14 # one of those days, yes 12.54.38 # Hmm, anyone of you 2, planed to improve the i2c patch? :) 12.54.50 # one of those days, yes :-) 12.54.55 # g 12.55.00 # :) 12.55.17 # if i have the bdm in my hands and got it wokring 12.55.51 # really? cool! 12.56.09 # was it hard to find out where to connect it? 12.56.34 # oh... "if i"... :-) 12.56.44 # :) 12.56.53 # * LinusN cleans his glasses 12.57.08 # jep.. i am looking where to connect the bdm today 13.01.22 # should be pretty straightforward, as the cpu pins are visible 13.02.29 # i hope that the palces to connect are marked 13.03.58 # you still haven't scanned the pcb's? 13.05.04 # reboot, brb 13.05.07 Part LinusN 13.06.41 # Interesting... At least since September, the ID3 screen hasn't shown all information. Doesn't anyone use it? :) 13.07.08 Join LinusN [0] (~linus@labb.contactor.se) 13.07.58 # i have scanned it, but as the pcb is not laying straight on the scanner it gets blurred 13.08.03 # Lear: all informations? 13.08.18 # austriancoder: aha 13.08.31 # Yeah, some info, like bitrate, frequency and path aren't possible to display. 13.08.48 # i see it 13.09.05 # LinusN: i must look if i could get better results 13.09.21 # would be good, as we all could see the pcb's 13.09.30 *** Saving seen data "./dancer.seen" 13.10.16 Part LinusN 13.11.28 Join LinusN [0] (~linus@labb.contactor.se) 13.11.33 # and everybody could help to find the bdm connectors ;) 13.11.45 # yup 13.12.52 # its time to setup my whole laptop as linux-only-zone 13.13.34 # time to go 13.13.36 # see you 13.13.40 Quit austriancoder ("CGI:IRC 0.5.4 (2004/01/29)") 13.14.09 Part LinusN 13.14.18 Quit edx (Read error: 110 (Connection timed out)) 13.15.37 Join LinusN [0] (~linus@labb.contactor.se) 13.19.59 Part LinusN 13.21.17 Join LinusN [0] (~linus@labb.contactor.se) 13.22.02 Join hicks [0] (~hicks@zeus.mups.co.uk) 13.28.47 Nick Febs is now known as Febs_away (~chatzilla@207-172-122-81.c3-0.rdl-ubr4.trpr-rdl.pa.cable.rcn.com) 13.32.56 Join Tangleding [0] (~Tangledin@ARennes-351-1-25-19.w82-126.abo.wanadoo.fr) 13.34.03 # Hi crazy Tang 13.34.53 # Hi Moos 13.34.55 # :) 13.35.04 # Back to Brest finaly 13.35.12 # déjà? 13.35.20 # pv 13.36.00 # okay 13.38.23 Join ghostiger [0] (~ghostiger@13e7c2047dcb9e70.session.tor) 13.51.11 # hello Rbx :) 13.51.26 # A x 13.51.37 # I wasn't on IRC chan for a while 14.00.06 # Congrate for latest progresses... 14.00.08 # :) 14.00.13 # Very good work 14.00.16 # :) 14.00.50 # just waiting for remote displaying patch to be comitted in CVS 14.01.03 # then i'll leave original iRiver fw :) 14.01.05 # bye 14.05.04 Quit ghostiger ("Leaving") 14.18.59 Part LinusN 14.26.25 Join LinusN [0] (~linus@labb.contactor.se) 14.28.01 # hi linus 14.28.07 # how are you? 14.28.09 # :) 14.30.48 # fine i guess 14.37.06 # :) 14.37.11 # nice 14.37.28 # want to gongrate you 14.37.38 # for the H110 bootloader 14.37.40 # :) 14.37.52 # very nice work 14.39.20 # thx 14.56.05 Join edx [0] (edx@p54A8EB53.dip.t-dialin.net) 15.00.07 # :) 15.00.16 # Okay i've to go 15.00.41 # i will make a donation at spetember/october 15.00.52 # wee! thx 15.00.54 # since i've suceeded in my exam 15.01.11 # and i'll work now and get payd 15.01.12 # :) 15.02.43 # Cheers :) 15.03.52 Quit Tangleding ("Chatzilla 0.9.68a [Firefox 1.0.4/20050511]") 15.09.31 *** Saving seen data "./dancer.seen" 15.40.09 Quit cYmen (Read error: 104 (Connection reset by peer)) 15.40.40 Join firefox_i686 [0] (~firefox_i@AToulouse-152-1-51-230.w82-125.abo.wanadoo.fr) 15.44.38 Part firefox_i686 ("faites vous plaisir -----> www.linuxiso.org") 15.56.23 Quit matsl (Remote closed the connection) 15.56.24 Quit Coldtoast (Read error: 104 (Connection reset by peer)) 15.59.51 Join matsl [0] (~matsl@1-1-4-2a.mal.sth.bostream.se) 16.00.48 Join Coldtoast [0] (~edan@ppp111-3.lns1.hba1.internode.on.net) 16.05.50 Quit matsl (Remote closed the connection) 16.08.28 Join cYmen_ [0] (~cymen@nat-ph3-wh.rz.uni-karlsruhe.de) 16.13.10 Join asdsd____ [0] (~asdsd@h-67-100-24-142.miatflad.dynamic.covad.net) 16.14.44 Part asdsd____ 16.35.20 Quit ashridah ("Leaving") 17.01.24 Join BBub_ [0] (belzebub16@dsl-082-082-243-103.arcor-ip.net) 17.02.40 # Hmm, if you find any bugs with playback, please tell me as soon as possible. I am only few days here and then month away 17.06.46 # Slasheri: the end of each track seem to be trimmed by a few seconds... 17.06.46 # only three weeks away ;) 17.07.24 # crwl :) 17.07.33 # Lear: Hmm, with any codec or mp3 only? 17.08.29 # i think this is mp3 problem.. 17.09.34 *** Saving seen data "./dancer.seen" 17.10.41 # I mainly play MP3, but I've notived it for oggs as well, when testing the resampler. It started happening within the last couple of days or so... 17.11.50 # LinusN: btw, the optical out is working with current builds. Beam is only lower intensity while not playing anything 17.12.20 # Lear: oh, i will check that 17.12.20 # i assumed he meant while playing 17.12.29 # weird 17.12.44 # afaik, it's been working for quite some time 17.14.30 # Lear: thanks, there is something wrong, ogg playback was not gapless when i just tried with a sine wave 17.15.45 # Good, easy to reproduce. :) Crossfade was off when I noticed it, btw. 17.18.08 Quit BBub (Read error: 110 (Connection timed out)) 17.18.08 Nick BBub_ is now known as BBub (belzebub16@dsl-082-082-243-103.arcor-ip.net) 17.23.44 # Lear: that was easy to fix, i will commit soon :) 17.26.52 # about 3 days ago I was listenign to tracks and instead of tracks crossfading, I got the start of the next song, a burst of the last song then the rest of the next song. Ithink it was after buffering then changing to a different dir, listening for a few secs then skipping to the next track 17.27.29 # so kind of a "worst case scenario" for playback 17.27.50 # i experimented this too few days ago :( 17.28.02 # i've got stuff like that too, and i don't use crossfading 17.28.03 # once it buffered again tho, it was fine 17.28.33 # not buffering enough initially or something (this only happens sometimes when changing tracks to something that isn't buffered yet) 17.33.32 # Slasheri: i found a problem on flac, latest build, it makes a short noise on the beginning of a track 17.33.37 Join XavierGr [0] (~XavierGr@ppp49-adsl-96.ath.forthnet.gr) 17.33.45 # maybe its the tag as rockbox doesnt read it 17.34.00 # BBub: Hmm, i will try that too 17.34.05 # heh. I've queued every single MP3 I have in Winamp then enabled Shuffle and now listening to tracks I've never even heard before 17.34.42 # thx Slasheri ;) 17.49.21 # * LinusN cut the lcd updating time from 1.8ms to 1ms 17.49.42 # in 120mhz 17.53.18 # and from 3ms to 2.5ms in 48mhz 17.54.55 Join Tangleding [0] (~Tangledin@ARennes-351-1-29-158.w82-126.abo.wanadoo.fr) 17.55.15 # Is there slashery? 17.55.26 # slasheri sorry 17.55.52 # ? 17.56.24 # Tangleding: hi, yes i am :) 17.56.31 # Hello 17.56.33 # :) 17.56.36 # How are you? 17.56.38 # :) 17.57.22 # fine thx ;) just trying to catch the last bugs before i leave for few weeks :) 17.57.28 # :) 17.57.29 # nice 17.57.37 # about the gapless fix 17.57.40 # precisely 17.57.48 # it's conceerning ogg i guess? 17.57.56 # no lame? 17.59.24 # all codecs had the problem, but it doesn't mean lame would be totally gapless now 17.59.50 # at least other codecs should be true gapless 18.00.01 # ah okay 18.00.26 # lame is really diffrent from others concerning gapless issue? 18.00.55 # yes it's because mp3s are not designe to be gapless.. 18.01.58 # in fact i've discussed with Gabriel Bouvigne 18.02.09 # (a Lame developer) 18.02.19 # and according to him 18.02.33 # the mainly différence was a "standadisation" one 18.02.36 # LAME-encoded stuff can be gapless, but it is something tacked on later. 18.02.48 # since there are many encoders 18.02.58 # unlike Vorbis for exemple 18.03.38 # he told me that thje vorbis gapless feature was using same method thanrecent lame (with fixed delay) 18.03.43 # so its pretty much impossible to see gapless to non-lame mp3s right? 18.03.56 # i guess so 18.04.01 # would be necessary 18.04.23 # to set the delay according to each encoder 18.04.27 # XavierGr: we may have the dsp to detect and cut silence in future 18.04.36 # :) 18.04.39 # Yes, because the decoder doesn't know how much the source was padded. Encoder delay isn't fixed either. 18.05.01 # oit's fixed for lame anyway 18.05.20 # have you got contact with some of the lame developers? 18.06.02 # Problem is, how to not detect/cut silence not at the very end... 18.08.00 # LinusN: Do you happen to from where the tree.c code is executed? I found the tree_init function called by main.c but this isnt most likely 18.08.13 # ^happen to know 18.08.17 # A cool feature about silence remover 18.08.38 # should allow to detect long silence not only at the file end 18.08.49 # (for kinda bonus track ;) ) 18.09.00 # XavierGr: app_main() calls init() and then browse_root() 18.09.30 # thanks 18.11.28 # so if I make a remote-tree.c identical to tree.c (cahnged lcd_ functions to remote_lcd) and call remote_tree_init() and remote_browse_root() (changed respectively) I can get the remote working right? (then toss up the clutter code) 18.12.56 # Except having two browsers active at the same time sounds like a bad idea... The remote should mirror a clipped version of the main display, IMO. 18.13.37 # Lear: agreed 18.14.24 Quit CBM-away (Read error: 54 (Connection reset by peer)) 18.14.27 # Well amiconn suggested that we use a saperate thread for each. Like creating remote-tree.c remote-wps-display.c e.t.c 18.14.39 # how do the iRiver fw proceeds? 18.15.28 # That might work, but it could also be confusing (for the user), and wouldn't there be synchronization issues? 18.18.11 # well I started a quick hack by replicating every lcd_ function to lcd_remote in the tree.c but encountered a dead end. Where a a function returns the height of the screen. I cant find a way to return 2 values, 1 for the main unit and for the remote. So I thought a different .c file would be better. 18.18.59 # what do you suggest? 18.19.38 # what functions do you refer to? 18.19.58 # you mean the lcd_ ones? 18.20.15 # or the replicate_height()? 18.20.42 # the ones you had problems with 18.23.13 # in tree.c line 239 recalc_screen_height. int height, is returned with the height value of the screen (LCD_HEIGHT) but then the remote screen isnt displayed correctly (text is hidden in the bottom part) 18.23.14 # hm... separating tree into a model and a view sounds like one way of doing it. I.e., tree (and also the wps) maintains a model over what to display, then call on functions to draw that model, once for the main display, and once for the remote, if present. 18.24.28 # so if I change height = REMOTE_LCD_SCREEN the remote is displayed correctly but the main is not 18.24.32 # yes, you need to maintain two values (using arguments to return the value or indicate what you want, different functions,etc) 18.26.03 # so what to do. 1.replicate and adjust 2.make another file for the remote 18.26.40 # 3. split out the rendering code into two cases, main and remote 18.27.15 # in the same tree.c? 18.27.40 # could be, but that isn't a requirement... 18.28.03 # the point is to logically separate the rendering from the rest. 18.28.54 # a complete rewrite as I see it... I will have to understand each and every line of the code... and I am newb. nevertheless i will try. 18.30.01 # no, not a complete rewrite. Lots of restructuring, yes... 18.30.57 # to rewrite tree.c for the screen height is tricky though. I tried many times but the rendering functions must be run twice for every display. 18.32.11 # no, once per display should be enough. :) 18.32.38 # yeah my bad I meant twice, once for each display 18.33.21 # but there is no other way, because the screens need to be rendered differently. 18.34.06 # and the easy way to handle that is to put the rendering in separate functions. 18.34.52 # though amiconn said clearly to me to make a different thread, not just a quick replicate hack, but then I will have to make a huge restructural work in order not to duplicate unnecessary code... 18.35.53 # so I could make a remote-tree.c which has the rendering functions for the remote and then call them from the tree.c if there is a remote? 18.35.59 # personally, I don't see the need for a separate thread... I guess the restructuring needed is why nobody has cared enough just yet. :) 18.36.38 # LinusN: What do you think? 18.36.55 # yes, something like that. Only I'd always call them, and let them return immediately if there is no remote. 18.37.43 # XavierGr: i agree with Lear 18.38.32 # but what if the code in tree.c is not saperated with rendering/setup functions. It is most likely that they are mixed up. 18.39.08 # I will have to dig up a little to be sure 18.39.18 # the code sure isn't separated today, but it needs to be... 18.40.43 # Pitty because I quite sure that I will have troubles to saperate them or even likely to understand them... 18.41.06 # to a large degree, I think what is needed is a "render list" function, that based on the loaded directory, cursor position and an internal state (the top line) draws that list. 18.42.51 # god the remote thing is the only thing that keeps me away from using rockbox. I am dying to make something for it. 18.44.03 # A few additional things are needed though,e.g., the "create playlist" splash. Some could problably be made with splash() (which perhaps also should know how to handle an additional display). 18.44.57 # another question: a static is seen without change in a single .c file, right? What if I want to use a static variable from another file? 18.45.28 # I'd start by going through all rendering (lcd calls) and try to group them logically. As in, render tree, create playlist... 18.46.56 # truth is that not all functions in tree.c has and lcd rendering function. 18.46.59 # A static is only visible within that module, yes. If you want access from another file, use accessor functions. dsp_stereo_mode() is a good example. It returns the current stereo mode, which is maintained within dsp.c. 18.47.28 # well, then perhaps they don't need to be changed at all? 18.47.44 # but it has some huge ones that do many things. 18.47.50 # i.e., there's no rendering to break out. 18.48.10 # also they counter react with other files for various tasks. 18.48.43 # but those things can be grouped into a limited number of "functions"... 18.49.57 # 7 functions have at least one lcd rendering function 18.50.33 # and dirbrowse is HUGE also there are alot of ifdes which need to be removed for the remote. 18.52.42 # But most of that is non-render logic, afaict. The "model" part I mentioned before. 18.54.28 # how can I return 2 values from a function? Maybe as a void functions which alters 2 static values? 18.55.48 # on a tangent, shouldn't the lcd_puts_scroll code be common to all targets? And wasn't it, once upon a time... :) 18.56.14 # pass in a pointer, and set the value through that pointer, 18.57.40 # see e.g. get_tag, it sets flags that way 18.57.51 # (in wps-display.c, that is) 18.59.15 # ok thanks. I will think of this a little bit and I will see what I can do... 19.03.12 # so Slasheri are you going on vacation? 19.08.11 Join Sucka [0] (~NNSCRIPT@host81-156-157-175.range81-156.btcentralplus.com) 19.09.37 *** Saving seen data "./dancer.seen" 19.12.44 # XavierGr: no.. i have to go to the mandatory (civil) military service.. :D 19.15.03 # for how long? 19.16.30 # 13 months and one month (3 weeks in fact) without net access 19.17.02 # but i can do other things during that 12 month period too :) 19.17.30 # so we will see you again after 13 months!!!!! 19.17.43 # hehe :D 19.17.52 # we will surely miss you.... :( 19.18.00 # after one month could be more realistic i hope ;) 19.18.28 # but you said 12 months? 19.18.41 # yes, the service lasts 13 months 19.19.01 # you will have some breaks? 19.19.06 # but during that last 12 month period i have the net access and can do other things too if i have time :) 19.19.09 # ^brakes 19.19.22 # do as I did 19.19.24 # get lucky 19.19.29 # and get out after 7 months 19.19.33 # hmm :D 19.19.40 # because of bad economy 19.19.47 # they just had to dump some of us 19.19.47 # hehe, nice ;D 19.19.50 # how old are Slasheri? 19.19.51 # indeed:) 19.19.55 # XavierGr: 20 :) 19.20.24 # and going to military so soon? I am 21 and I will go in 2011! 19.20.48 # oh :) i just wanted to go there as soon as possible.. then i don't need to worry about it later :) 19.20.49 # Slasheri: inspired by your latest commit I browsed the playback.c a bit. Is the line 1349 correct or should there be some if statement before that? 19.21.04 # Ismo: Hmm, i will check that 19.21.59 # I haven't looked how the pcm stuff works, but that line looks like a bit too alone :) 19.22.01 # Ismo: yes, that's correct. If we were filling the buffer, AUDIO_PLAY event will start the crossfade 19.22.08 # and if not, then it's started there 19.22.16 # :D 19.22.19 # ok 19.22.21 # :) 19.23.03 # in fact codec_track_changed() could be on that statement too but it's outside it because in every case we want to update the wps immediately 19.23.33 # and what country are you from Slasheri? 19.23.41 # XavierGr: from Finland :) 19.24.00 # I thought that is was voluntarily there. 19.24.19 # this is the about only EU country that still has mandatory mil service.. :/ 19.24.36 # hey! 19.24.37 # well count Greece in that too 19.24.39 # dont forget norway 19.24.42 # or sweden 19.24.45 # haha 19.24.45 # oh 19.24.46 # eu 19.24.47 # oh well 19.24.48 # :D 19.24.50 # sweden then 19.25.26 # its 12 months (i think) mandatory here too. 19.25.55 # I remember the elders calling 36 months in the military! :x 19.27.10 # huh, that's sick :D 19.28.16 # indeed! 19.30.50 Join Stryke` [0] (~Chairman8@cpe-24-168-110-99.si.res.rr.com) 19.33.42 # small bug report: the patch that was added to stop scrolling at the bottom of a list when holding it down does not work in the Debug menu 19.34.41 # Stryke`: iirc, that patch was only for the browser, not for menus 19.35.19 # oh, any reason it would not be applied there? 19.35.53 # no particular reason 19.36.19 Join stripwax [0] (~stripwax@213-228-241-36.dsl.prodigynet.co.uk) 19.42.35 # ello 19.43.17 # hi stripwax! 19.43.39 # feh 19.43.45 # anyone in london fancy a beer ? 19.44.15 # crashd - i'd love one, but I've just got back from a four hour drive from the midlands .. way too hot to do anything right now 19.44.26 # XavierGr - hey dude 19.44.26 # :\ 19.44.30 # hehe 19.44.41 # im sunburnt from sitting up on hampstead heath yesterday 19.44.59 # crashd hehe. i'm sunburnt from driving round back from the midlands! ;-D 19.45.04 # : ) 19.45.25 Join webguest72 [0] (~51429e1d@labb.contactor.se) 19.45.33 # hello folks 19.45.45 # a litle question please 19.46.08 # sure 19.46.54 # * stripwax slaps himself for running old plugins in rockbox sim and wondering why it kept crashing.. 19.46.55 # there is a patch for i2c in the tracker, and apear anyone want to work on it, it's normal? :) 19.47.10 # the FM it's very usual :) 19.47.16 # "usual" ? 19.47.46 # "important" for much people 19.48.13 # Linus? 19.48.21 # it's not in your plan? 19.48.51 # Linus: i'm sure you can do it easyly,no? 19.49.16 # no? 19.50.35 # Linus:i noticed in the log that you have adapted the code a bit for i2c for irivers, have you planed something please? :) 19.51.44 # webguest72 - which patch are you referring to? 19.52.16 Quit webguest72 ("CGI:IRC (EOF)") 19.52.26 Join webguest72 [0] (~51429e1d@labb.contactor.se) 19.52.37 # this: http://sourceforge.net/tracker/index.php?func=detail&aid=1232476&group_id=44306&atid=439120 19.53.18 Quit west-acre ("—I-n-v-i-s-i-o-n— 2.0 Build 3515") 19.53.24 # webguest72 - you'll have to ask ac about that one... 19.53.32 Join solex_ [0] (~jrschulz@d127233.adsl.hansenet.de) 19.53.56 # but he deserted this because he working in iaudio now 19.54.08 # and alone Linus can help us 19.54.41 Join bagawk [0] (~lee@bagawk.user) 19.54.45 # Linus: nope? 19.54.58 # huh? 19.55.23 # i optimized the i2c bit rate 19.55.45 # have you planed to aplly the ac patch? 19.55.57 # yes 19.56.06 # wonderfull :) 19.56.21 # it's easy for you, no? 19.56.34 # what do you mean? 19.57.16 # it's more easy for you to do this work than one other dev, because Rockbox is your baby, no? 19.57.29 # :) 19.57.38 # hehe, rockbox is our baby, not mine 19.57.43 # :D 19.57.44 # it's open source so many ppl have written code for it 19.57.44 # webguest72 - any of the devs could apply ac's patch, i expect 19.57.57 # it's not like LinusN could know ALL the code intimately 19.58.30 # i just want to know he was the must experimented with it 19.58.32 # ;) 19.58.53 # was that english? :-) 19.59.00 # haha 19.59.19 # scuse me for my english :) 19.59.32 Join spiralout [0] (~keep_goin@p54B38C70.dip0.t-ipconnect.de) 19.59.34 # since i have hooked up my logic analyzer, it feels natural to add the i2c reading, since i can easily verify it 19.59.55 # ok 19.59.56 # right now i'm investigating the s/pdif output 20.00.11 # LinusN- neat - what's to investigate there? 20.00.33 # some people have problems with it, their dac refuses to play it 20.01.28 # Linus: scuse me for this stupid questions and thanks, we hope you'll can add i2c things for FM soon if you can :) 20.01.37 # webguest72: don't worry 20.01.58 # have a long life to Rockbox :) 20.02.11 # bye all 20.02.15 Quit webguest72 ("CGI:IRC") 20.03.11 # i have a theory why spdif doesnt work, but i don't have a toslink cable to test with :-) 20.03.51 # dinner time 20.03.57 # cu in a while 20.04.10 Part LinusN 20.04.11 Quit solex (Read error: 110 (Connection timed out)) 20.09.05 # Anyone want a patch for sokoban so it caches leveldata? 20.11.20 # a small bug: on the h110 rockbox always shows 276mb of free space no matter how much space is really free 20.11.51 # hehe, neat! 20.15.29 # My sokoban cache patch is here - http://sourceforge.net/tracker/index.php?func=detail&aid=1239851&group_id=44306&atid=439120 20.25.29 Join hicks_ [0] (~hicks@zeus.mups.co.uk) 20.40.25 Quit hicks (Read error: 110 (Connection timed out)) 20.42.23 Quit Tangleding ("Chatzilla 0.9.68a [Firefox 1.0.4/20050511]") 20.43.04 Join webguest80 [0] (~3e4f4094@labb.contactor.se) 20.43.41 # hmm 20.43.51 # BBub: What if you press the joystick while on the "Disk info: Free" screen? (this will rescan free space) 20.43.52 # where's preglow when you need him 20.44.02 Quit Maxime () 20.44.35 Quit bagawk ("Leaving") 20.46.52 Join muesli- [0] (muesli_tv@c-180-216-90.cvx-h.dial.de.ignite.net) 20.48.24 # re 20.49.55 # re? 20.50.32 # have to go see you all later! 20.50.35 Quit XavierGr () 20.51.37 # dont you understand "re" !? 20.52.39 Join Psy-Dead [0] (~nobby@cpc1-bele3-3-1-cust167.belf.cable.ntl.com) 20.53.20 # a lot of ppl don't understand anything less than a TLA 20.57.13 # tla? 20.57.23 Quit Seed (Read error: 104 (Connection reset by peer)) 20.57.27 # Three Letter Abbreviation 20.57.40 # and ppl? 20.57.44 # people? 20.57.50 # yeah 20.57.54 # cheers 20.57.57 # heh 20.57.58 # mate 20.58.17 # you in the UK? or Australia? 20.58.30 # neither nor..germany ;) 20.58.39 # but have been in oz last year 20.58.48 # did you like it there? 20.59.55 # it was in october and exprected to be warm but it was lousy cold ;-) but oz is nice..wished to had more time 20.59.56 Join Seed [0] (ben@l192-117-115-168.broadband.actcom.net.il) 21.00.48 # are you from down under? 21.01.57 # I am 21.02.04 # where the heck WERE you in Australia? heh 21.02.31 # just in sydney to see the coat hanger (spelling!?) 21.02.57 # whats yr location? 21.04.39 Join dj-death [0] (~user@djdeath.dyndns.org) 21.04.42 # Hi all 21.04.54 # I'm new to rockbox 21.05.06 # I'm actually in Tasmania 21.05.07 # I just got it on my iriver ihp120 21.05.19 # it works great ;) 21.05.44 # and has some really cool feature 21.06.12 # tasmania sounded great by brochure. and where do you live most of the time? 21.06.21 Join LinusN [0] (~linus@labb.contactor.se) 21.09.02 # high LinusN 21.09.31 # yo 21.09.38 *** Saving seen data "./dancer.seen" 21.10.43 # has someone problem at the end of file when playing on iriver ? 21.11.04 # dj-death: try the latest bleeding edge 21.11.34 # I mean when listening a file (mp3/ogg) rockbox jump to the next track 2/3 seconds before the end of the current file 21.11.50 # yes, try the latest bleeding edge 21.12.00 # bleeding edge ? 21.12.07 # you mean daily build ? 21.12.12 # the very bottom of the daily build page 21.12.28 # ok 21.12.29 # thx 21.13.03 # http://www.rockbox.org/dl.cgi?bin=h120 21.13.09 # isnt it this one? 21.13.20 # those are daily builds 21.13.39 # where do i find the bleedings? 21.13.41 # http://www.rockbox.org/auto/build-h120/rockbox.zip 21.13.41 # thats bleeding edge 21.13.50 # the very bottom of the daily build page 21.14.10 # ok upgrade done 21.14.14 # let's try 21.14.38 # http://www.rockbox.org/auto/build-h120/?C=S;O=D 21.14.43 # now its the upper one 21.16.21 # LinusN: works fine thx a lot 21.16.31 Part dj-death ("bye") 21.19.18 # LinusN: Hmm, would you like to look at the peak meter code if i commit it soon? at some degree it works but it has quite a strange behaviour 21.19.52 # Slasheri: strange? 21.20.53 # i think the scaling might not be right and for some reason i have to "invert" the calculated average to get the right reading. You will find more from the code :) 21.29.10 # LinusN: committed, please take a look if you have time 21.29.16 # ok 21.29.41 # i really don't know how that peak average should be calculated so i just tried _something_ =) 21.32.37 Quit crashd ("leaving") 21.32.48 Join memmem [0] (~user@p54A23260.dip0.t-ipconnect.de) 21.33.39 Join crashd [0] (nobody@badger.ing.me.uk) 21.36.01 # sorry dude. got distracted 21.36.16 # city called Launceston muesli- 21.36.53 # mmh..never heard of it..which state? 21.37.21 # Tasmania 21.38.52 # mmh..didnt made it far in the south.. 21.38.55 # next time ;) 21.39.27 # http://images.google.com.au/imgres?imgurl=http://www.kyne.com.au/~mark/photos/tasmania/launceston.jpg&imgrefurl=http://www.kyne.com.au/~mark/photos/tasmania/page2.php&h=600&w=800&sz=52&tbnid=zrZcGfiAE1oJ:&tbnh=106&tbnw=142&hl=en&start=3&prev=/images%3Fq%3Dlaunceston%2Btasmania%26svnum%3D10%26hl%3Den%26hs%3D9uY%26lr%3D%26safe%3Doff%26client%3Dfirefox-a%26rls%3Dorg.mozilla:en-US:official%26sa%3DN 21.39.35 # what a horrid url 21.39.42 # http://www.kyne.com.au/~mark/photos/tasmania/launceston.jpg 21.39.49 # yeah. google link. sorry 21.39.55 # anyway. that's where I live 21.40.14 # looks cloudy ;x 21.40.18 # :D 21.40.29 # heh. it is. especially in Winter 21.40.38 # blue skies in Summer tho 21.43.49 # yeah, gorgious nature..thats what i heard about tasmania 21.43.58 # g'Day HCl btw 21.44.07 # evening 21.44.22 # gorgeous 21.44.24 # .. 22.01.41 # l8er mates 22.05.57 Join Yasmine_ [0] (~GS3@AMarseille-252-1-48-136.w86-193.abo.wanadoo.fr) 22.06.01 Part Yasmine_ 22.17.34 Join ep0ch_ [0] (~ep0ch@81-6-218-35.gotadsl.co.uk) 22.18.45 # hey, anyone else noticed that all of sudden 128 kbps mp3 is now realtime with no CPU boost? 22.19.11 # i could swear it needed boost before... 22.19.14 # I have no 128kbit MP3s on mine, so no. But great to hear 22.22.08 # Slasheri - is that pcm peakmeter basically the same approach as I had or does it precalculate volume levels? 22.22.53 # oh wierd *some* 128 kbps are realtime, and some arent. 22.23.15 Join webguest04 [0] (~44e5eab9@labb.contactor.se) 22.23.21 Quit webguest04 (Client Quit) 22.23.57 # stripwax: hmm, it tries to calculate some average volume from one chunk of 512 bytes. But i don't even exactly know what it does ;) what kind of approach you have? 22.24.41 # the peakmeter is wierd... even quiet parts of the music show full peak 22.25.02 # yes, it's kind weird.. try using linear scale instead of logarithmic 22.25.09 Quit muesli- (Read error: 110 (Connection timed out)) 22.25.42 # Slasheri: oh thanks for all the recent playback fixes :) 22.26.08 # np, one more fix is coming (i found just a bug in the playback code) 22.26.36 # hmm i just changed to "linear" peakmeter and the music just hung :s 22.26.44 # :/ 22.26.58 # did it crash or just hung? 22.27.09 # just got silence 22.27.12 # no sound 22.27.15 # ah.. 22.27.39 # i'll try it again, see if it was the peakmeter 22.28.37 # hmm, is the peak meter disabled if wps don't show it? i hope it is.. 22.28.56 # nah i dont think it was changing the peakmeter that broke the sound.. did it again and it worked... 22.29.46 # if you have logf enabled, take a dump and try to see what happened 22.29.55 # haha 22.30.08 # not enabled 22.30.13 # :/ 22.30.21 # i'll try and reproduce 22.30.49 # sorry. telling him to "take a dump" is childishly amusing 22.30.54 # heh 22.30.59 # :D 22.35.33 # Slasheri - yes, that was my approach too but I remember Linus saying it was quite strange so I guess I thought an approved approach would have to be different ;-) 22.36.01 # ah, interesting :) 22.36.55 # Slasheri - how do you work around something like SAR0 changing while you're reading the buffers? or the remaining buffer size being less than your averaging window? 22.37.31 # Slasheri - i think my patch was here http://www.beermex.com/@spc/vu.patch 22.38.26 # so basically you average a block of samples, divide by the bit depth and mutiply by the number of pixels wide the peak meter is, or something? 22.39.20 # ep0ch_ - sort of, the recorder/peakmeter.c code just expects a number between 0 and 0x7fff 22.39.41 # ok 22.40.02 # so yeah, we average a bunch of sample data, and obtain a left and right 'volume' value between 0 and 32767 22.40.32 # sample data is signed? 22.41.20 # ep0ch_ - would that make any difference? volume would still be between and 0 and 32767 22.41.54 # if you have sample values, -255 and 255 average is 0 22.42.01 # when it should really be 255 for the peakmeter 22.42.11 # i.e. the average of 255 and 255 22.43.01 # so you should ignore the sign if sample data uses it? 22.43.16 # bah i'll look at some C code and see if i understand it :) 22.43.21 # ep0ch_ - ah, understood. yes, to derive the sample data obviously we need to know what 'zero value' means. 22.43.45 # I think I assumed sample data was 16 bit signed in my code, dunno what Slasheri does 22.44.45 # Hmm - interesting, he's assuming sample data is unsigned, but only deriving a volume value from samples with value > 32768. weird? 22.45.51 # well half the values wont be calculated then 22.46.15 # well, they'll be calculated but wrong ;-) 22.46.43 # should average the whole lot and add 32768 to the total maybe 22.46.47 Join matsl [0] (~matsl@1-1-4-2a.mal.sth.bostream.se) 22.46.58 # bah i dunno 22.47.19 # ep0ch_ no, don't add 32768 - just take absolute value of each sample, and average that. 22.47.49 # oh yeah of course 22.50.45 # bah playback just stopped again for no reason about 2/3 of the way through an MP3. i'll put logging on from now on 22.51.07 # was quite enjoying the tune too ;) 22.51.19 # ooh, logging ? where/what's that? 22.52.16 # logf 22.52.29 # enable it with the configure script 22.53.01 # * stripwax never even knew. neat 22.53.19 # logs on the remote lcd 22.53.33 # and offers a "dump logf buffer" function 22.53.45 # * stripwax has no idea where his remote is .. :-( 22.53.53 # i need the remote??? 22.53.57 # you can browse the log on the main unit too 22.54.01 # mines still in pieces :s 22.54.04 # ep0ch_: only if you want to see the log live 22.54.45 # if i want it on the main screen can i change the wps to display it? 22.54.51 # Bagder - ah, cool 22.54.57 # ep0ch_: no 22.54.58 # theres plenty of space... 22.55.00 # ah 22.55.02 Join webguest69 [0] (~18d79b85@labb.contactor.se) 22.55.15 # ep0ch_: unless you add the code for it ;-) 22.55.33 # give me a couple of years to get up to speed with rockbox code 22.56.04 # I'll expect your patch by noon tomorrow B-] 22.56.19 # heh heh 22.56.28 # :) 22.59.54 # stripwax: back to peakmeter, if the data is unsigned taking the average of absolute values is pointless 23.01.11 # ep0ch_ - audio data is 16 bit.... if data is unsigned then 'zero' is 32768. so subtract 32768. and then it becomes signed. so you need to take absolute values... 23.01.12 # epoch_: pcm data is signed. 23.01.31 # at least in the iRiver... :) 23.01.32 # (or, equivalently, invert data if sample is > 32768) 23.02.23 # No, the result of inverting will be off by one. 23.03.23 # memmem - by invert I meant 65536-x 23.03.24 Quit webguest69 ("CGI:IRC (EOF)") 23.04.25 # OK, PCM data uses two's complement representation for negative numbers. 23.04.45 # i.e. signed shorts 23.05.08 # and not unsigned shorts, which is what Slasheri's pcm vu meter code seems to use.. 23.05.25 # Signed shorts on architectures that use two's complement arithmetic ;-) 23.05.36 # [20:43:54] BBub: What if you press the joystick while on the "Disk info: Free" screen? (this will rescan free space) <- that works 23.05.52 # i thought it would do it by itself 23.06.08 # do what by itself? 23.06.17 # refresh the free space 23.06.22 # why would it? 23.06.31 # it is time and battery consuming 23.06.51 # i only assumed it because the original firmware does it 23.07.05 # I didn't even know it could do that ;-) 23.07.14 # BBub the original firmware loads the entire directory structure on startup, which is time and battery consuming ;-) 23.08.12 # This is unrelated, I believe 23.08.22 # Bagder - how does rockbox fw know if/when file system changes have been made in usb mode 23.08.24 # i dont really need it anyways ;) 23.08.31 # The problem lies in either iriver firmware, rockbox or your OS not updating the fsinfo block 23.08.37 # stripwax: it doesn't really 23.08.51 Join amiconn [0] (~jens@p54BD4008.dip.t-dialin.net) 23.09.23 # webguest80: rockbox updates it 23.09.31 # windows usually does not 23.09.42 *** Saving seen data "./dancer.seen" 23.09.54 # webguest80 - the problem lies in the fact that the OS has no way of knowing what exactly happens when the harddrive is in usb passthrough mode 23.09.55 # after all, they only made up FAT and wrote the spec 23.09.58 # Indeed, I have a beef with Windows for lying to me about free space on more than one occasion 23.10.28 # stripwax: not at all, the OS should update the FAT record 23.10.33 # stripwax: but the fsinfo stuff should be updated by the OS 23.10.52 Quit Psy-Dead () 23.11.41 # hi 23.12.21 # Bagder/webguest80 - oh right - I misunderstood. yeah, you're right 23.14.21 # Any chance that rockbox will be able to record MP3 at 256 kbit/s or 320 kbit/s on the iAUDIO X5 (as does the original firmware which makes heavy use of EMAC instructions)? 23.14.46 # memmem: we have no good mp3 encoder that runs fast 23.15.22 # so currently we don't see that coming any time soon 23.15.34 # Ditto for OGG? 23.15.43 # yes afaik 23.15.44 # better chances for recording in flac/wavpack ? 23.15.53 # FLAC? shorten? 23.15.54 # BBub: yes indeed 23.16.01 # oh, that sounds nice 23.16.28 # The NoDo page says that WAV recording won't be done but that probably applies to the Archos devices only. 23.16.37 # yes 23.16.47 # wav recording will most likely be done first 23.16.57 # and it even already is somewhat implmented 23.17.04 # Fine. 23.17.14 # Wavpack isn't too far away either, it seems 23.18.16 Quit webguest80 ("CGI:IRC") 23.22.24 # is the waveform-switch in the recording-menu used to switch between raw pcm and pcm in a wave-container? 23.24.41 # Bagder: The gmini builds completely fell out the table, yet the 2 columns are still there... 23.25.11 Quit Stryke` (Read error: 104 (Connection reset by peer)) 23.25.44 # yes, since they're still around 23.25.52 # the columns are based on more data than what is shown 23.30.25 Part LinusN 23.32.22 Join CheeseBurgerMan [0] (~youshould@tc2-225-085.altelco.net) 23.34.58 # I'll go away for a about a week starting now 23.37.24 # No localisation v2 commit before that? ;) 23.37.33 # no ;-/ 23.37.58 # I have an experimental plugin showing 13 shades of grey on iriver :) 23.38.07 # wow 23.38.12 # does it look good? 23.38.24 # Yes, way less flicker than on archos 23.38.32 # cool indeed 23.38.44 # ...because it flicks between 2 adjacent native grey levels, not black & white 23.39.03 # amiconn - that doesn't require constant CPU boost or anything silly does it? 23.39.25 # The experimental thing is without random pixel pattern shift, so more levels would flicker 23.39.41 # I hope to support 97 levels of grey in the actual lib 23.40.13 # stripwax: Yes it requires constant boost, unfortunately. That's why it will be plugin only, like on the archos 23.40.20 # fairy nuff 23.40.26 # 97?! 23.40.28 # hmm :o 23.40.36 # It's not a performance problem, but a problem of constant timer period 23.40.39 # has rockboy been updated to support grayscale yet? 23.40.52 # see ya in a week 23.40.53 # Yes, 97 shades. 23.40.55 Quit Bagder ("Off to search for that connect-resetting peer guy!") 23.41.02 Join muesli- [0] (muesli_tv@Bc1f6.b.pppool.de) 23.41.51 # The method quickly switches between several bitplanes. The maximum number is limited to 32 to allow storing the pattern in a longword for quick access 23.42.20 # On archos, this allows 33 shades of grey, with the lcd being b&w only 23.42.37 # ((2-1) * 32 + 1) 23.42.53 # The iriver lcd already provides 4 shades natively, so 23.43.01 # yummy yummy :) 23.43.04 # (4-1) * 32 + 1 = 97 23.43.55 # The X5 display supports 2^18 colors (and I confirmed that the firmware transfers 2^18 bits per pixel to the LCD controller). 23.44.07 # Nice :) 23.44.24 # X5 display? 23.44.34 # Btw, this allows less shades of (pure) grey than my grayscale lib will support on H1x0 :-P 23.44.53 # amiconn: The pixel data is not shifted left and is sent as two 9 bit words. 23.44.57 # what is X5 display? H3x0? 23.45.03 # iAUDIO. 23.45.04 # iAudio X5 23.45.07 # Oh 23.45.11 # Never heard of it :P 23.45.25 # memmem: Any news concerning the display controller? 23.45.44 # I still think it is quite similar to the H3x0 lcd... 23.45.58 # amiconn: I found enough to be able to initialize it (though I don't know what those commands actually do) and to write pixel data. 23.46.57 # We should still try to find the type, complete with a datasheet 23.47.12 # the x5 looks slick 23.47.17 # Of course. There are probably also some I/O pins involved. 23.47.20 # That will allow us to use some tricks the original firmware doesn't 23.47.35 # such as? 23.47.38 # ...like (simple example) the display flip 23.47.47 # What's that? 23.47.54 # flipping the display 23.47.57 # so its upside down 23.48.13 # All pixel based units have a mode to use the unit upside down 23.48.26 # That could also be done in software. It's used rotated 90 degrees anyway. 23.48.35 Quit Coldtoast ("Peace and Protection 4.22") 23.48.41 # wouldn't hardware be faster though? 23.48.48 # That's useful from time to time, and since it uses a hardware feature of the controller, it's simple... 23.49.43 # memmem: Doing it in software would be quite a bit more complex 23.49.51 Join yngwi [0] (~chatzilla@85-124-85-76.dynamic.xdsl-line.inode.at) 23.50.00 # If all drawing operations go through a display buffer there's no difference. Just subtract 160 instead of adding 160. 23.50.28 # memmem - does that mean an extra test for EVERY pixel operation? or does it mean two functions where one would suffice? :-p 23.50.29 # They go through a display buffer with the same layout as the internal buffer of the lcd 23.50.44 # ...and it's not as simple 23.50.57 # right...because then you would have to rearrange data 23.51.11 # (1) Flipping the line blocks is simple, as ou said just invert the line sequence 23.51.12 # ok, just submitted another useless patch - this one for Cube plugin lets you rotate the cube manually when it's paused 23.51.15 # The iAUDIO firmware's buffer has a different format than expected by the LCED controller. 23.51.38 # (2) Flipping the lines itself is also simple, just read from the end decrementing the pointer 23.52.00 # (3) BUT the hard thing is flipping the pixels within a line block 23.52.06 # I think we don't want to use 2 9-bit words per pixel with one color channel split between two words... 23.52.28 # Just use a 256-byte table. 23.52.46 # ...for b/w graphics. 23.53.08 # However, we need 18 bits per pixel unless we find out how to select a different mode. 23.53.16 # I wouldn't use a palette mode for high/truecolour displays 23.53.33 # I would just use 18 bit mode and use 3 bytes per pixel 23.53.44 # I was talking about a table for flipping the bits inside a byte for b/w displays. 23.53.57 # amiconn - but think of the Plasma-style/color cycling effects you could do in a palettised mode! :-p 23.54.11 # stripwax: that would be fun :) 23.54.15 # memmem right or just do it in hardware.. 23.54.30 # The iAUDIO firmware uses 3 bytes per pixel in RAM and converts to the format expected by the LCD controller while copying the data to the LCD controller. 23.54.32 Quit Harpy (Read error: 110 (Connection timed out)) 23.54.39 # memmem wow, that sounds hideous 23.55.09 # Maybe the controller does only allow that format, but I doubt it 23.55.24 # have you identified what lcd it uses? 23.55.53 # A bit of conversion is probably necessary anyway for colour lcds 23.56.57 # memmem: There are more efficient ways to swap bits than using a table... 23.57.29 # All the bits (7<->0, 6<->1, ...)? Pray tell me... 23.58.05 # You can use a 3-staged shift approach, and that can work on 4 bytes at once, i.e. longwords 23.58.13 # I tried it, it work nicely 23.58.29 # For 8-bit bytes, a table is better.