--- Log for 23.12.104 Server: niven.freenode.net Channel: #rockbox --- Nick: @logbot Version: Dancer V4.16 Started: 1 month and 13 days ago 00.00.03 # sure. anything in particular you're thinking about? 00.00.16 # not for the moment 00.00.29 # we have the choice between a linux and a port of rockbox 00.00.45 # but our last discussion was about rockbox 00.03.44 # in my opinion, linux brings too much baggage unless you need complex stuff like networking or a usb host 00.04.08 Join Dulcise [0] (~Will@cpc2-darl1-5-0-cust195.midd.cable.ntl.com) 00.04.20 # but I guess my opinion is rather predictable in this topic :-) 00.04.38 # ha 00.04.41 # ya 00.05.07 # but there are 99% chances that we'll port rockbox 00.05.24 # :) 00.05.26 # it would be really cool 00.05.44 # would be a solid basis for us :) 00.05.47 # also 00.06.09 # does the gmini use a MAS for mpeg playback? 00.06.22 # mp3 I mean 00.06.25 Quit Dulcise (Client Quit) 00.06.33 # hmm dunno exactly... w8 00.06.55 # Zagor: I got an answer from the guy with the reboot-instead-of-shutdown problem with flashed rockbox. 00.07.14 Join jyp [0] (~jp@243.135-200-80.adsl.skynet.be) 00.07.26 # amiconn: ok, was it a player or a recorder? 00.07.35 # Player 00.07.54 # hi jyp 00.08.04 # jyp: 00.08.05 # [00:04] does the gmini use a MAS for mpeg playback? 00.08.05 # [00:05] mp3 I mean 00.08.08 # hey all 00.08.19 # What's MAS ? 00.08.26 # same question... 00.08.26 # mp3 decoder chip 00.08.35 # Bagder: (gmini & mas) Iirc it doesn't 00.08.45 # It is decoded in software 00.08.45 Join Dulcise [0] (~Will@cpc2-darl1-5-0-cust195.midd.cable.ntl.com) 00.08.52 # ok 00.09.20 # so we'll have the same situation for gmini and iRiver then 00.09.25 # yup 00.09.37 # too bad no one is interested int he 400 :( 00.09.43 # probly too much work i guess 00.09.54 Quit Stryke` ("Friends don't let friends listen to Anti-Flag") 00.09.57 # JJ-Demon: too little docs. those texas chips are top secret stuff. 00.10.01 # JJ-Demon: maybe few gmini400 00.10.03 # for the mment 00.10.19 # time to sleep 00.10.26 # We get quite a lot of gmini 400 requests on #gmemu and on the forum 00.10.46 # ill have to learn to code;) 00.10.46 # i can imagine. but it's an entirely different device. much more in common with the multimedias. 00.10.58 # nite badger 00.11.22 # Zagor: It's a really strange problem. Sometimes the player reboots instead of shutdown, and it takes up to 7 tries to shut down. Another time it shuts down with the first try 00.11.23 # i suppose photos of the chips and stuff wouldnt help? and all the numbers 00.11.31 # neither arm nor calmrisc ? 00.11.53 # JJ-Demon: it's always a start 00.12.03 # Taking photos is probably the 1st thing to do ;) 00.12.07 # ya 00.12.10 # hmm ok, i think ill take soem pics then 00.12.15 # Then try to gather docs for them 00.12.19 # i gota remove some dust under my screen 00.12.20 # then gather firmwares 00.12.29 # ill do it when im doing that 00.13.00 # JJ-Demon: if you have access to a flat-bed scanner, that's the ideal way to make board images 00.13.07 # Zagor: The version number he told (5.02, not sure yet whether this is ROM or archos fw, but these are closely related) suggests that it is a newplayer. I requested some further details, let's see 00.13.43 # amiconn: ok 00.15.15 # I have a vague idea what might cause this, though if this idea is the real cause, I wonder why we didn't observe it on any other archos unit yet: 00.18.57 # Let's say we port rockbox to gmini... 00.19.12 # Somehow the shutdown sequence might cause an NMI, or a reset (due to an uninitialized port??) 00.19.16 # What version shall we take as a starting point ? 00.20.20 # grab the daily tarball. later is practically always better. 00.20.36 # ok 00.21.21 # amiconn: what does it look like when it won't turn off? is backlight and screen on? text still showing? 00.22.18 # He didn't tell this (yet). He said that it starts the shutdown sequence, and he uses the safe shutdown from the menu 00.23.03 *** Saving seen data "./dancer.seen" 00.23.13 # aha, he uses safe shutdown? is it only that which fails or won't it turn off even when holding the button? 00.23.59 Join Digital007 [0] (~acbebec9@labb.contactor.se) 00.24.05 # Hi 00.24.52 # Zagor: Neverending questions... He didn't tell this detail as well. I also ahd some more questions, which are already on the way... e.g. whether this problem existed before flashing 00.24.59 # s/ahd/had/ 00.26.16 # ok. well it's good that we have contact at least. i have a faint recollection of there being something fishy with the poweroff circuit on the players. can't remember what it was though. 00.27.16 # damn those ipod users 00.27.43 # Digital007: ? 00.27.47 # Zagor: Well, we're pulling the circuit with the button input pin switched to output. Maybe the pull is not strong enough, or long enough. (I guess the cpu will no longer pull when the voltage gets too low) 00.28.06 # found a workaround for the iriver shufflebug 00.28.28 Quit gromit` (Remote closed the connection) 00.30.52 # got a sneer from an ipod user on the train as i was using my iriver 00.31.47 # so then you asked to see his remote? 00.31.58 # ipod = gaayyyy 00.31.59 # ;) 00.32.17 # no i didn't 00.32.20 Join gromit` [0] (~gromit`@ras75-5-82-234-244-69.fbx.proxad.net) 00.32.22 # why would i wanna see his remote for? 00.32.32 # because it's lousy :) 00.32.41 # yea the iriver remote is pretty good 00.33.04 # lol i got a case for my gmini 400 at an ipod store, the guys there couldnt belive it played video 00.33.08 # Zagor would iriver-rockbox have proper shuffle when its finally implemented? 00.33.08 # re 00.33.45 # Digital007: yes, we've had good shuffle for years 00.33.49 # yea 00.34.06 # its just that the iriver does not have a clock, so i wondered if shuffle for it was possible 00.34.29 # and we're rather proud of the fact that we even can resume shuffled playlists in the same order 00.34.35 # ye 00.34.47 # iriver firmware plays the same songs in the same order when shuffle is on 00.34.51 # clock has nothing to do with it. only some archos models have clock as well. 00.34.53 # just hope rockbox doesn't do that 00.36.06 # there's plenty of entropy elsewhere besides the clock. such as when you press the play button. humans are pretty random :) 00.36.06 # Digital007: I still wonder why the iriver owners relate a working shuffle to the existence of a clock. In fact, 3 of the 6 archos models that currently run rockbox don't have a clock, and they all have the same, excellent shuffle 00.36.21 # well its what i read on the misticriver site 00.37.03 # A crossfader should be possible as the decoding is software on the iriver 00.37.38 # yes 00.37.46 # amiconn: it could be because the random function is sometimes based on the computers clock 00.38.56 # Yes, *sometimes* the random seed is taken from the clock... but as Zagor said, there are plenty of other entropy sources 00.39.51 # just out of interest, what like? 00.40.03 # random number generator? 00.40.35 DBUG Sent KICK JJ-Demon to server 00.40.35 # * JJ-Demon 12is AFK, 11on another planet 05—14I05-15n05-15v05-00i05-00s05-15i05-15o05-14n05— 00.40.36 Kick (#rockbox JJ-Demon :Colourcodes are *not* appreciated here!) by logbot!~bjst@labb.contactor.se 00.40.37 Join JJ-Demon [0] (~JJ@203-206-17-167.dyn.iinet.net.au) 00.40.59 # can you use a random number genenerator without a random seed? 00.41.15 # of course 00.41.32 # Dulcise: we use the clock tick when you start the playlist. it varies every time. 00.42.16 # so Zagor on the iriver how you vary the playlist every time play is pressed if there is no clock? 00.42.29 # there is a clock, just no realtime clock 00.42.41 # all computers have internal clocks that start from 0 on powerup 00.42.42 # so it is still possible? 00.42.45 # Other possibilities would be the time between 2 keypresses, the duration of a keypress... 00.42.57 # or battery level, disk spinup time etc etc 00.43.10 # Digital007: Yes, definitely 00.43.15 # cool 00.43.19 # can't wait for iriverbox 00.43.20 # :) 00.43.34 # interesting 00.43.39 # riverrock! 00.43.40 # same :P:) 00.43.40 # oh :p 00.43.59 # Even my very first computer (a Sinclair ZX Spectrum) had this runtime counter, and guess what - it could be used for the random seed 00.44.35 # the ZX Spectrum was ok as an upgrade from a calculator..... 00.45.04 # isn't it also used in the fsb, for when to send the command or something 00.45.09 # yea 00.45.14 # to the cpu 00.45.24 # the MAS is obselete these days 00.46.47 # MAS? 00.46.55 # as in the archos 00.46.57 # hardware decoder 00.47.03 # and hardware bass/treble/loudeness 00.47.49 # aaah, is thats why flac etc. can't be added to the archos 00.47.55 # yea 00.48.01 # iriver is software driven 00.48.12 # :) 00.48.24 # so you could add any codec u want to it if u wished 00.48.51 # yeah 00.49.04 # ...and you bet people will ask for any codec you can think of :) 00.49.36 # MP3Pro would be a good start 00.49.57 # no one uses mp3pro anymore... 00.50.47 # i'm happy with just the ones that are already supported by the h1xx 00.51.06 # well we won't support wma of course 00.51.23 # :( 00.51.36 Nick JJ-Demon is now known as JJ-Away (~JJ@203-206-17-167.dyn.iinet.net.au) 00.51.43 # perhaps a long time in the future others, flac etc. 00.51.43 # Zagor: why not? 00.52.13 # i know you its not possible to do protected ones 00.52.27 # *they shouldn't be a you in there... 00.54.45 # because ot 00.55.04 # it's a locked-down proprietary format that we aren't even allowed to implement without paying Microsoft 00.56.30 # that sucks, i don't know why companys make proprietary formats, they must lock themselfs out of quite a bit of the market 00.56.59 # the idea, especially if you have a monopoly, is to lock customers into the market 00.57.30 # i guess 00.57.44 # hehe 00.57.57 Join pvh [0] (~Miranda@S01060050bac5c39e.gv.shawcable.net) 00.58.08 # have you seen how microsoft told its customers about bbypassing itunes drm ? 00.58.22 # burning a cd 00.58.29 # no..? 00.58.32 # then they removed the tip from their website :) 00.58.37 # funny... 00.58.51 # After my latest solder-job to reattach the end board, my rockbox powers on then powers off right after. 00.59.03 # If I hold the on button on, it stays on. 00.59.37 # Anyone have any ideas? 00.59.38 # pvh: which model is it? 00.59.43 # lol 00.59.43 # i wonder if you can bypass wma protections in a similar maner... 01.00.03 # ya :) 01.00.07 # Dulcise: of course you can 01.00.09 # Recorder V1 01.00.18 # that's why they removed the tip :) 01.00.23 # dumbass 01.00.29 # dumbass <- microsoft 01.00.31 # :) 01.00.32 # lol 01.00.51 # In theory we can do any format; just don't infringe on patents 01.00.53 # :P 01.01.15 # then release the patented format with bittorent 01.01.18 # hrm no... 01.01.20 # not anymore 01.01.23 # :) 01.02.22 # That would be interesting to implement WMA... I'm not sure they'd have anything against us. 01.02.46 # wma is crap :) 01.03.00 # I don't know ;) 01.03.09 # why not .mov 01.03.30 # well.. if you did your own implimentation is it infiringing at all? 01.04.00 # wait a min, ignore last thing i said 01.05.45 # Zagor: I just found a very interesting routine in the archos player disassembly when checking how they do the player poweroff 01.06.41 # There is the (very slight) chance that the charger gets plugged while the powerdown loop is running, but the box did not yet powerdown completely 01.07.04 # We do not handle this case in rockbox, so this will cause a deadlock 01.07.34 # Archos activates the watchdog timer in this case, causing a reset after ~100 ms 01.07.39 # ok 01.08.03 # Is there any way to force rombox to boot from the AC Charging screen?? 01.08.15 # Just press on 01.08.27 # Doesn't work. 01.08.51 # Must be my build, which is a couple months old now. 01.09.21 # Works for me, both on the recorder V1 and the player. It only boots after releasing the button again 01.10.07 # Will 'box boot without the .rockbox folder? 01.10.17 # Yup. 01.10.34 # It will complain about the missing .rockbox folder of course 01.10.39 # That's not it then 01.24.28 # Zagor: In fact it's very easy to deadlock rockbox, I just tried it with the recorder. Start safe shutdown, and while it displays the "Shutting down" message, plug in the charger... 01.24.53 # you just need to know the trick :) 01.28.16 # Same trick does also work for the player 01.30.38 # Btw, is there a reason why the power_off() disables the backlight for the player, but not for the recorder models? 01.33.01 # I guess this has to do with the backlight being connected to the rtc, and the "direct switch" functions being internal to backlight.c ... but this could be changed (?) 01.33.06 # Is it possible that my problem is caused by lousy soldering? I would think that as long as I had soldered at least one point on each side it would work. 01.34.15 # amiconn: there is no (good) reason for that. the recorder should do the same imho. 01.37.57 # The "official" backlight_off() function does only post an event to the backlight queue, which wouldn't help here 01.38.36 Quit mecraw_ ("Trillian (http://www.ceruleanstudios.com)") 01.42.16 Nick JJ-Away is now known as JJ-Demon (~JJ@203-206-17-167.dyn.iinet.net.au) 01.42.33 # time to go 01.42.35 # cu! 01.42.38 # goood night 01.42.49 Quit Quelsaruk ("KVIrc 3.0.1.99 'System Virtue'") 01.43.38 # I think I'll follow that example 01.43.44 # Nite everyone 01.43.56 Part amiconn 01.43.58 # nite 01.44.02 # too ;) 01.44.05 Quit jyp ("Leaving") 01.50.48 Quit pvh (Read error: 60 (Operation timed out)) 01.59.36 # bed time 01.59.41 Quit Zagor ("Client exiting") 02.23.05 *** Saving seen data "./dancer.seen" 02.31.15 Quit Digital007 ("CGI:IRC (EOF)") 02.44.15 Join PnkyChkn [0] (PnkyChkn@AC80EB90.ipt.aol.com) 02.44.34 # hello? 02.44.55 # hey 02.44.58 # hey 02.45.05 # hi 02.45.28 # I'm looking for some knowledgeable folk to give me a hand with a problem I'm having with my Studio 20. 02.45.39 # Can you guys help at all? 02.46.47 # depends, what is the problem? 02.47.05 # ok, here's what happened 02.48.29 # About a month ago I was walking back from class with the player in my pocket. I took it out to turn it off, and it turned off and gave me an HD error. I tried to start it up again, and it got stuck on the "Jukebox Ver 5.xx" screen for a while, then gave me a file sys error. 02.48.42 # So 02.48.54 # I just changed the batteries, and it's still doing the same thing 02.49.08 # and I've taken it apart to check if it was the battery connectors, but they're fine. 02.49.21 # but I'm still having the same problem. 02.49.55 # can you connect to usb? 02.50.01 # (to a pc, via usb) 02.50.17 # The PC won't recognize the hardware. The player goes into USB mode, but the comp doesn't recognize it. 02.51.30 # won't boot, pc won't recognize it? 02.51.33 # hmm. 02.51.43 # yep. 02.53.07 # hold on 02.53.17 # ok, thanks 02.56.05 # you changed the batteries -> were they full (or at least 50% charged)? 02.57.11 # They'd been charging for about 3, 3 and a half hours. 02.57.40 # so I should try again when they're more fully charged? 02.57.56 # they should probably be working now.. 02.58.20 # but it seems that people with this error were able to usb to a pc fine, could you double check that if you didn't? 02.58.54 # I did 02.58.58 # double check it I mean 02.59.22 # weird, sorry, i can't help 02.59.25 # I AM however using a driver that wasn't from the CD...found it on the internet 02.59.28 # could that be it? 02.59.32 # (my computer crashed and I lost the install CD) 02.59.37 # has it connected to usb before? 02.59.41 # yeah 02.59.52 # since you installed the new driver? 02.59.55 # yep. 03.00.03 # probably not then 03.00.06 # ok 03.00.13 # well, thanks anyway 03.00.27 # there was one other thing, now that I think about it. 03.01.18 # When I took it apart to check the battery connectors, one of the battery springs (the part of the connector that the - end of the battery connects to) had a weird wire restricting the spring 03.02.23 # I took it out because my electronics-knowledgeable friend told me that he didn't think it was supposed to be there and wasn't important, but could this be why I'm having trouble? I was still getting the same error before I took it out, but.... 03.02.52 # I tried this before I got new batteries (because I had to wait till I got home from college to be near a store that sold NiMH batteries) 03.03.46 # here's a studio scan.. 03.03.48 # http://www.rockbox.org/internals/6k_cpu.jpg 03.05.14 # thanks 03.05.18 # don't see anything like it though 03.05.48 # i've still got no idea.. maybe if you come back later or tomorrow you'll run into LinusN who could likely help you 03.06.05 # [idc]dragon or amiconn may also be helpful 03.06.50 # ok 03.06.57 # any idea what time they can usually be found? 03.07.25 # amiconn left about 1h45m ago 03.07.36 # you may want to try tomorrow about 3h earlier if you can 03.08.05 # alright 03.08.11 # thanks so much for all the help 03.08.21 # no problem, good luck! 03.08.39 # be back tomorrow then. Later 03.08.44 Part PnkyChkn 03.13.42 Quit midk (Read error: 54 (Connection reset by peer)) 03.16.09 Join midk [0] (~midk@c66-235-14-120.sea2.cablespeed.com) 03.22.48 Quit Dulcise (":/") 03.28.40 Quit midk ("Leaving") 04.23.07 *** Saving seen data "./dancer.seen" 04.56.34 Join midk [0] (~midk@c66-235-14-120.sea2.cablespeed.com) 04.58.34 Quit midk (Client Quit) 04.58.35 Join midk [0] (~midk@c66-235-14-120.sea2.cablespeed.com) 05.15.24 Quit midk ("*poof*") 05.17.47 Join midk [0] (~midk@c66-235-14-120.sea2.cablespeed.com) 06.09.49 Quit Josh_file ("CGI:IRC (EOF)") 06.16.14 Quit midk ("*poof*") 06.23.08 *** Saving seen data "./dancer.seen" 06.42.42 Join midk [0] (~midk@c66-235-14-120.sea2.cablespeed.com) 06.45.52 Join |XO2| [0] (XOXOXO@ool-4355d5ca.dyn.optonline.net) 07.32.15 Join ze__ [0] (psyco@adsl-63-205-41-178.dsl.lsan03.pacbell.net) 07.37.02 Quit ze (Read error: 60 (Operation timed out)) 07.41.14 Nick ze__ is now known as ze (psyco@adsl-63-205-41-178.dsl.lsan03.pacbell.net) 07.48.13 Join ze__ [0] (psyco@adsl-63-205-45-129.dsl.lsan03.pacbell.net) 07.49.44 Quit |XO2| (Connection timed out) 07.53.02 Quit ze (Nick collision from services.) 07.53.04 Nick ze__ is now known as ze (psyco@adsl-63-205-45-129.dsl.lsan03.pacbell.net) 08.23.12 *** Saving seen data "./dancer.seen" 08.45.39 Join amiconn [0] (~jens@pD9E7FFA8.dip.t-dialin.net) 08.54.51 Join einhirn [0] (~Miranda@carlsberg.heim2.tu-clausthal.de) 09.06.19 Join Zagor [242] (~bjst@labb.contactor.se) 09.06.36 # morning 09.08.09 # i've changed my mind about rushing 2.4 out the door. there's only very little changes from 2.3. most of our work has been for the new hardware support. 09.09.57 # morning 09.13.14 # Imho some of the bug fixes would justify a new release. 09.13.31 # There was that file caching bug for writing in 2.3, which wears the flash unnecessarily and makes it slow as hell on Ondio when e.g. saving configs 09.14.08 # yes, that is one of the five changes i found and listed in my preliminary notes 09.14.13 # Then 2.3 does not support all Ondio hardware versions yet. Some users already ran into that problem 09.14.51 # i'm not saying we shouldn't release, just that a pre-christmas rush job is not necessary 09.15.54 Join amiconn_ [0] (~jens@pD9E7F373.dip.t-dialin.net) 09.16.06 # Grmpf! 09.16.17 Quit amiconn (Nick collision from services.) 09.16.18 Nick amiconn_ is now known as amiconn (~jens@pD9E7F373.dip.t-dialin.net) 09.16.20 # on the other hand I have the release done already so release is simply a matter of sending a mail. hmm... 09.16.36 # i feel your pain :( 09.16.43 # Another improvement (way less significant though) is the Ondio keyboard 09.18.17 # http://www.rockbox.org/download/2.4/rockbox-2.4-notes.txt 09.19.00 # On the other hand, it would be good to get some things straight before a new release... the recording beep is one such thing 09.19.20 # The current implementation definitely disturbs prerecording. 09.19.31 # yes. but the code I packaged does not include that 09.20.29 # I experimented a bit yesterday. When I only toggle coded reg. 0 bit 0, it still beeps even without an input signal, and it does not disturb prerecording. But the beep gets even more faint... 09.21.09 # as in hard to hear faint, or just not very strong? 09.23.16 # Well, you can hear it in a quiet environment (and it gets louder if there is an input signal, but it may be hard to hear in a noisy environment 09.24.44 # it's clear we need more experiments and input from the blind users 09.24.53 # All other "beep methods" do only beep when there is an input signal, and then are about the same strength 09.33.34 # Iirc, the 74 and 80 minute time split settings are already present in 2.3. The remote control should also work in 2.3, it was broken afterwards, and then fixed again. 09.34.20 # no the split was added after 2.3. i base the notes on the cvs log 09.34.48 # the remote is probably right though, it was only temporarily broken post-2.3 09.35.30 # remote was broken on Nov 18 (by Linus adding the iRiver code) and then fixed again on Nov 25 09.36.04 Quit einhirn (Read error: 104 (Connection reset by peer)) 09.36.07 # right 09.36.38 # i meant that your remark about the remote was right 09.38.18 # You're right about the time split. That means the 2.3 manual is incorrect about that... 09.38.49 # aha. another reason to release then :) 09.40.09 # Then there is flash for the players (although there still seem to be some quirks) 09.41.02 # yes I don't want to announce that as released until we've had more testing 09.41.19 # ..and still nobody tried it on an oldplayer.. :( 09.50.04 # Zagor: Didn't you offer to send your oldplayer? 09.50.26 # If this was a serious offer, I'd ask [IDC]Dragon if he still has a spare flash rom, and would solder this in. 09.50.51 # sure, we could do that. i hardly ever use it anyway, only for testing once in a blue moon 09.54.36 # Okay. If Jörg is willing to do that, you could send your player to me first. I would do the uart boot mod and do some tests first. Jörg doesn't dare to do the uart boot mod for players, as he seems to have killed a player by doing it... If this works, I'd send the cpu board to Jörg, who would then swap the ROM and send it back to me. I would flash it, and do some more tests 09.54.55 # ok 09.55.31 # "who will win. rockbox or 1.70 firmware. i hope to God its rockbox." -- iriver.com user forum 09.55.44 # :) 09.55.55 # :) 10.23.15 *** Saving seen data "./dancer.seen" 10.32.30 # (away now) 10.46.30 Join [IDC]Dragon [0] (~d90a3255@labb.contactor.se) 11.06.37 Join einhirn [0] (~Miranda@carlsberg.heim2.tu-clausthal.de) 11.22.53 Join Quelsaruk [0] (~kvirc@80.103.138.199) 11.38.51 # <[IDC]Dragon> Zagor: do you read? 11.40.53 # <[IDC]Dragon> owever, saw your chat with Jens 11.41.03 # <[IDC]Dragon> however... 11.41.41 # <[IDC]Dragon> I'm in favour of a "small" relaese, call it 2.31 if you like 11.41.52 Join Digital007 [0] (~acbefcab@labb.contactor.se) 11.41.59 # morning............. 11.42.06 # <[IDC]Dragon> Hi 11.42.12 # hi 11.42.23 # Does anyone have one of those iSkin iriver protectors? 11.43.33 # [IDC]Dragon: i think 2.4 is fine. 2.31 will most likely confuse more than help 11.43.58 # btw, morning :) 11.44.02 # <[IDC]Dragon> whatever 11.44.36 # <[IDC]Dragon> my reasoning is that a "scheduled" release won't hurt, especially before we change it big time 11.44.48 Quit Quelsaruk (Read error: 104 (Connection reset by peer)) 11.45.18 Join |Quelsar| [0] (~kvirc@80.103.138.199) 11.45.25 # <[IDC]Dragon> with ID browsing and/or multivolume 11.45.31 Nick |Quelsar| is now known as Quelsaruk (~kvirc@80.103.138.199) 11.45.43 # re 11.46.01 # <[IDC]Dragon> it may be unstable for a while then 11.46.36 # yes, i agree. i'll release after lunch. 11.46.36 Quit MooMaunder (Read error: 104 (Connection reset by peer)) 11.47.51 # <[IDC]Dragon> recording beep is not in yet, you said 11.48.17 # <[IDC]Dragon> or should we disable it for prerecording but include it? 11.48.49 # <[IDC]Dragon> would be nice for the blind chaps 11.49.03 # i think we should test more first 11.49.07 # <[IDC]Dragon> else they just missed it in this realese 11.49.45 # <[IDC]Dragon> at least it's not "harmful" then 11.50.38 # there's also the issue about releasing things that we might change. i prefer to test it in the dailies for a few weeks first. 11.51.23 # <[IDC]Dragon> like, having a branch before a release? 11.51.37 # <[IDC]Dragon> or a freeze? 11.51.56 # we've usually done it with freezes, but a branch works too if we don't want to freeze 11.52.25 # also functions can be tested without freezing, just by being in the dailies and having people try them 12.19.27 Join Tang [0] (~chatzilla@136.127.119-80.rev.gaoland.net) 12.19.42 # hello guys :) 12.20.04 # 09.55.31 # "who will win. rockbox or 1.70 firmware. i hope to God its rockbox." -- iriver.com user forum 12.20.43 # LOL! I have no real doubt you can win agianst iRiver firmware section.... 12.23.18 *** Saving seen data "./dancer.seen" 12.35.00 # hi tang 12.35.09 # Hi Zagor 12.35.11 # :) 12.36.00 # happy christmas for tomorrow :) 12.44.14 Join |Quelsar| [0] (~kvirc@80.103.138.199) 12.44.14 Quit Quelsaruk (Read error: 104 (Connection reset by peer)) 12.44.31 # <|Quelsar|> f***ing drivers... 12.48.10 Join zeekoe [0] (me@zeekoe.kabel.utwente.nl) 12.51.11 Nick |Quelsar| is now known as quelsaruk (~kvirc@80.103.138.199) 12.56.23 Join MooMaunder [0] (~me@194.152.87.150) 12.58.56 # cu l8r! 12.59.00 Quit quelsaruk ("KVIrc 3.0.1.99 'System Virtue'") 13.01.58 Quit Digital007 ("CGI:IRC (EOF)") 13.03.08 *** SPY: Authentication failed for Zagor 13.03.26 Mode "#rockbox +o Zagor " by ChanServ (ChanServ@services.) 13.03.45 Topic "Rockbox 2.4 released - Merry Christmas!" by Zagor (~bjst@labb.contactor.se) 13.04.03 Mode "#rockbox -o Zagor " by Zagor (~bjst@labb.contactor.se) 13.23.54 # woo, rockbox 2.4! 13.26.34 Join Christi-S [0] (~Christi@client-60-p-1-lns.glfd.dial.virgin.net) 13.26.40 # woo, Hadaka awake :) 13.26.46 # hi christi 13.26.50 # Heya 13.27.09 # Who do I kill for releasing 2.4 just after I get the 2.3 manual done. ;) 13.27.15 # me :) 13.27.27 # Consider yourself killed. 13.27.28 # seriously, very little has changed that affects the manual 13.27.38 # * Christi-S nods. 13.27.38 # this has probably been asked here every now and then, but have you considered doing anything about Neuros? 13.28.01 # Hadaka: not while the compiler costs $6000 13.28.05 # <[IDC]Dragon> Christi-S: do a search-and replace 2.3 -> 2.4 ;-) 13.28.08 # yikes 13.28.15 # understandable :) 13.28.16 # I have to do a manual update anyway. I have to use a Type 1 rather than a Truetype font for the PDF to be searchable. 13.28.57 # IDC - there's a couple of new features though (recording beeps etc.) - might as well try to get them added. 13.29.07 # <[IDC]Dragon> no beep yet 13.29.08 # the beeps are not in 2.4 13.29.21 # Oh, right. So what is that I need to know about? 13.29.34 # <[IDC]Dragon> Ondio keyboard screen 13.29.47 # oh and, I remember hearing something about S/PDIF recording being broken at some point - does that work with 2.4? 13.30.11 # Since that's not documented yet, I don't have to worry about that. 13.30.16 # Hadaka: that has never been cleared out. it works for lots of people, but one or a few have had problems. 13.30.34 # <[IDC]Dragon> and more Ondio in general... 13.30.52 # right, well I'll have to test that myself then 13.30.55 # That it? 13.31.07 # <[IDC]Dragon> afaict, yes 13.31.19 # Christi-S: there are two new timesplit options: 74 and 80 minutes 13.31.29 # i don't remember if you list all options 13.31.42 # for time split recording 13.32.04 # They're actually already documented - wasn't in the early drafts, but amiconn is a wonderfully thorough proofreader. ;) 13.32.21 # ah 13.32.58 # Looks like I don't have to kill you after all, since I was going to release a new manual anyway. ;) 13.33.20 # Too late now though. Ah well, these things happen. 13.33.26 # <[IDC]Dragon> 2.5 will be the killer then 13.33.44 # * Zagor rises from the ashes 13.33.58 Join R3nTiL [0] (~zorroz@83.69.98.99) 13.34.01 # Neat trick! 13.34.28 # <[IDC]Dragon> I have to try vintage versions of Rockbox. 1.4 was one when I started 13.34.29 # I'm hoping to get a few more volunteers helping out on the manual. Realistically it's a bigger job than 1 person can handle. 13.35.02 # <[IDC]Dragon> s/one/on 13.35.15 # yes. I and linus discussed setting up a system on the web site where people can upload their modified sxw files and we'll make diffs from them 13.36.22 # Well, I've said to submit them as patches for the time being, since we already have a mechanism for that. 13.36.52 # yes, but it's heavy work finding out what was changed 13.36.55 # <[IDC]Dragon> is sxw diff-able ASCII? 13.36.56 # As long as an author starts from a previous reach, editing it in should be fairly easy. 13.37.10 # OpenOffice has versioning support. 13.37.11 # [IDC]Dragon: it's xml in a zip 13.37.28 # Christi-S: aha, well ok never mind me then :-) 13.37.31 # <[IDC]Dragon> xml would be diff-able 13.37.34 # Start a new version and then I get to decide whether to accept any changes or not. 13.37.44 # It's moderately nifty. 13.37.49 # (Assuming it works.) 13.39.14 Join R3nTiL1 [0] (~zorroz@83.69.98.158) 13.41.16 # Oooh. I just typed "release" as "reach" 13.41.22 # I need more sleep. 13.41.41 # 2.4 manual willl probably be out tonight then. 13.41.54 # goodie 13.41.58 # I need to check that changing the font hasn't mucked up the formatting. 13.42.24 # But PDFs you can actually search through are a good idea. 13.43.57 # indeed 13.44.55 # noteyou can use .tex and cvs 13.45.08 # with each part in a separate file 13.45.31 # yes, but tex has a rather steep learning curve 13.45.39 # boah 13.45.41 # The effort of moving away from OO wouldn't be worth it. 13.45.46 # So does OO. 13.46.03 # you have editors if you wanna simplify the task 13.46.07 # such as lyx 13.46.14 Join webguest53 [0] (~539930ec@labb.contactor.se) 13.46.19 # and i think it is possible to convert existing files 13.46.28 # (It might have been before I bashed the 2.3 manual into shape,) 13.46.36 Join qlb212 [0] (~539930ec@labb.contactor.se) 13.46.36 Quit webguest53 (Client Quit) 13.46.39 # i actually don't have strong opinions about which tools to use. (s)he who does the work selects the tools. 13.47.05 # If I were starting from scratch, I'd probably use LaTeX. 13.47.08 # But I'm not. 13.47.27 # you can convert 13.47.46 # No thanks. I have enough pain in my life. 13.48.05 # as you want :) 13.48.53 # I've never found a text processing system I like. They all (TeX included) have their own idiocies. 13.49.12 # vi 13.49.15 Quit R3nTiL (Read error: 60 (Operation timed out)) 13.49.19 # Since I understand OOs idiocies better than the rest, I'm sticking with the devil I know. 13.49.24 # the main advantage of tex is that maintaining is easier 13.49.40 # since it is plain text 13.49.54 # and it is cross platform 13.50.06 #