--- Log for 23.08.104  Server: orwell.freenode.net  Channel: #rockbox
--- Nick: logbot  Version: Dancer V4.16p1  Started: 9 days and 14 hours ago

00.03.52 Join    LinusN [200] (~linus@labb.contactor.se)
00.15.09 Quit    _aLF ("Leaving")
01.00.26 Part    LinusN
01.08.37 Join    AciD` [0] (~gni@longchamp44-1-82-67-133-87.fbx.proxad.net)
01.22.05 Quit    AciD (Read error: 110 (Connection timed out))
01.24.13 Quit    Nibbler (Read error: 60 (Operation timed out))
01.26.31 ***     Saving seen data "./dancer.seen"
02.23.00 Join    gromit`` [0] (~gromit@ALagny-151-1-29-26.w83-114.abo.wanadoo.fr)
02.34.12 Join    Madman [0] (~madmangor@adsl-69-224-113-50.dsl.irvnca.pacbell.net)
03.01.23 #       <Madman> anyone here?
03.01.30 #       <gromit``> hello
03.04.21 #       <Madman> hey, do you know anything about pong on the jukebox recorder?
03.08.04 Quit    Madman ()
03.26.35 ***     Saving seen data "./dancer.seen"
03.42.11 Nick    gromit`` is now known as gromit`TiRED (~gromit@ALagny-151-1-29-26.w83-114.abo.wanadoo.fr)
03.48.23 Join    hume22 [0] (~fgjkrj@200.12.45.10)
03.48.47 #       <hume22> hello i have an archos jukebox 10 and i have the error dir buffer full
03.49.08 #       <hume22> i never used rockbox before but i installed 2.2 and got the daily build of today
03.49.18 #       <hume22> any help will be great
04.10.42 Join    Dstar5 [0] (~441cbb6b@labb.contactor.se)
04.35.10 Nick    gromit`TiRED is now known as gromit`aw (~gromit@ALagny-151-1-29-26.w83-114.abo.wanadoo.fr)
04.35.38 Join    Madman [0] (~madmangor@adsl-69-224-113-50.dsl.irvnca.pacbell.net)
04.41.07 Quit    AciD` (Remote closed the connection)
04.45.40 Join    AciD [0] (~acid@longchamp44-1-82-67-133-87.fbx.proxad.net)
04.50.38 #       <Madman> anyone know anything about the dir buffer full! error?
04.52.15 #       <Madman> i just flashed my jukebox, it worked fine, but after i tried to install the latest daily build, it says, "dir buffer is full!"
04.58.39 #       <Madman> anyone know?
05.02.14 Quit    AciD (Read error: 60 (Operation timed out))
05.05.59 #       <Madman> it also wont allow me to install a new firmware, including all of the daily builds and the original archos firmware (1.7)
05.07.41 #       <Madman> it has v. 2.2 of rockbox in right now, because thats what came with the flash
05.13.18 #       <Madman> either nobody is here or nobody knows
05.15.01 #       <Madman> its like v2.2 keeps on re-writing itself after i delete it...
05.23.10 Join    hume23 [0] (~fgjkrj@200.12.45.10)
05.24.04 #       <hume22> madman go into the options general, system then limits
05.24.23 #       <hume22> and change the file limits and power off and on your player
05.24.55 #       <Madman> didnt work...
05.25.58 #       <Madman> i think something else is wrong.  i tried to delete the .ajz file and the .rockbox dir files, but they just rewrite themselves.
05.26.05 #       <Madman> i did that from the computer
05.26.25 #       <Madman> i cant even see any dir's in the jukebox
05.26.37 #       <hume22> i had the same problem today
05.26.38 ***     Saving seen data "./dancer.seen"
05.26.42 #       <hume22> and that how i fixed it
05.27.01 #       <hume22> hey do you know how to fix the laggint between changing tracks
05.27.11 #       <hume22> it takes like 4 secs
05.27.18 #       <hume22> before it was instant
05.27.47 #       <Madman> do you have a daily build?
05.28.02 #       <hume22> yep
05.28.26 #       <hume22> takes like 5 secs
05.28.29 #       <Madman> and its flashed?  it shouldnt do that
05.28.42 #       <hume22> whats flashed
05.28.51 #       <Madman> your jukebox
05.28.52 #       <hume22> first day i start using this firmware
05.29.09 #       <Madman> oh, well it should only take like 2 secs
05.29.31 #       <hume22> the light starts blinking
05.29.41 #       <hume22> like its searching hard
05.30.03 #       <hume22> it didnt do that before i installed this firmware
05.30.35 #       <Madman> that is weird, whenever i change the limit, not only does it reset when i turned it off, but i saw it jump from 0 to 50.  
05.30.49 #       <Madman> that means that the default is 0 when it boots up.
05.31.33 #       <hume22> you have jukebox 10
05.31.55 #       <Madman> 20
05.32.00 #       <Madman> recorder 20
05.32.51 #       <hume22> oh i have jukebox 10
05.33.01 #       <hume22> well didnt you delete some files_
05.33.06 #       <Madman> it should work about the same though
05.33.12 #       <hume22> try reinstalling it again
05.33.16 #       <hume22> and change the limit
05.33.34 #       <Madman> whenever i delete something, it just rewrites itself
05.33.45 #       <Madman> im starting to think that its possesed
05.33.55 #       <Madman> :)
05.33.59 #       <hume22> maybe
05.34.14 #       <hume22> u think this rockbox is better than the original_
05.34.23 #       <Madman> much better
05.35.12 #       <hume22> what does flashing do to your player
05.35.12 #       <Madman> or it was until it stopped working
05.36.22 #       <hume22> u think if i flash it it will work
05.36.55 #       <Madman> it makes your jukebox run from ram so it goes a lot faster and boots faster
05.37.36 #       <Madman> if i were you, i wouldnt flash it right now.
05.37.38 #       <hume22> hmm how long does it take_}
05.37.44 #       <hume22> why
05.38.06 #       <Madman> wait untill i get mine working because i might have found a glitch or something
05.38.20 #       <Madman> its fast.
05.38.33 #       <hume22> ok sounds good
05.38.50 Quit    Ka_ (orwell.freenode.net irc.freenode.net)
05.38.50 NSplit  orwell.freenode.net irc.freenode.net
05.38.50 #       <hume22> could it damage it
05.39.14 NHeal   orwell.freenode.net irc.freenode.net
05.39.14 NJoin   Ka_ [0] (~tkirk@pcp04776551pcs.howard01.md.comcast.net)
05.39.46 #       <Madman> it could, but its highly unlikely
05.40.01 #       <Madman> they just like to put out a disclaimer so that you dont sue them
05.40.10 #       <hume22> ok cool
05.40.21 #       <Madman> http://rockbox.haxx.se/docs/flash/rockbox_flash_boot.avi
05.40.25 #       <hume22> i wonder why they dont put rockbox on the damn thing from the start
05.40.53 #       <Madman> download that video and see what flashing you rockbox will do
05.41.06 Quit    Ka_ (orwell.freenode.net irc.freenode.net)
05.41.06 Quit    dwihno (orwell.freenode.net irc.freenode.net)
05.41.06 Quit    ze (orwell.freenode.net irc.freenode.net)
05.41.06 Quit    mbr (orwell.freenode.net irc.freenode.net)
05.41.21 #       <hume22> thanks
05.41.22 NJoin   Ka_ [0] (~tkirk@pcp04776551pcs.howard01.md.comcast.net)
05.41.22 NJoin   dwihno [0] (~dw@81.8.224.89)
05.41.22 NJoin   ze [20] (psyco@adsl-63-205-46-145.dsl.lsan03.pacbell.net)
05.41.22 NJoin   mbr [0] (~mb@stz-softwaretechnik.com)
05.41.24 #       <Madman> and the recorder in the video is the type that i have
05.42.15 #       <hume22> cool
05.42.22 #       <hume22> it does load a lot faster
05.42.47 #       <Madman> i dont know if your jukebox is compatible with it though
05.42.54 #       <hume22> how long does it take to flash
05.42.57 #       <hume22> hmm
05.43.05 #       <Madman> a few seconds
05.44.24 #       <hume22> it says it is compatible but i have to check with a sort of utility
05.47.00 #       <Madman> oh no...
05.47.37 #       <Madman> since i flashed it, the firmware is installed in the ram, so i cant delete it.
05.47.46 #       <Madman> or i dont know how to
05.49.28 #       <hume22> hmm
05.50.22 #       <Madman> wow, it just started to work for no apparent reason
05.50.55 #       <hume22> The first is a Recorder, FM Recorder or Recorder V2 model. Be sure you're using the correct package, they are different! The technology works for the Player models, too. Players can also be flashed, but Rockbox does not run cold-started on those, yet. 
05.51.00 #       <hume22> what those this mean
05.51.15 #       <hume22> i mean does
05.52.30 #       <Madman> cold started means by just pressing on... i thing
05.52.31 #       <Madman> think
05.53.05 #       <hume22> so it might not work
05.54.30 #       <Madman> it should
05.55.23 #       <Madman> its working for me now, im going to try to install one of the daily builds
05.55.27 #       <hume22> you think i should flash it
05.56.38 #       <Madman> back up all of your stuff first
05.58.03 #       <hume22> to my hard disk
05.58.12 #       <hume22> you mean to my pc
05.58.18 #       <hume22> or to the same player
05.58.40 #       <Madman> to the pc
05.58.50 #       <Madman> im not saying anything is going to happen
05.58.53 #       <Madman> but just incase
05.59.01 #       <hume22> ok lets see
05.59.23 #       <Madman> by the way, i got mine to work.
05.59.40 #       <Madman> i held f1 and on to boot it to the original os
05.59.52 #       <Madman> then i turned it off and booted to rockbox
06.00.15 #       <hume22> cool
06.00.19 #       <hume22> im going for it
06.00.21 #       <Madman> then i had to execute the ucl file to make the dailybuild load up when it boots
06.00.24 #       <hume22> hope it works
06.00.41 #       <Madman> that was for anyone who is going to read the log who had my problem
06.02.20 #       <Madman> my jukebox is going like 10 times faster now
06.02.58 #       <Madman> if you get it to work, tell me
06.06.21 #       <Madman> have you installed it yet?
06.10.18 #       <Madman> ill be back
06.10.21 Quit    Madman ()
07.26.39 ***     Saving seen data "./dancer.seen"
07.37.35 Join    oxygen77 [0] (~Chris@pauguste-7-82-66-87-78.fbx.proxad.net)
07.55.34 Quit    hume23 (Read error: 110 (Connection timed out))
07.55.58 Quit    hume22 (Read error: 110 (Connection timed out))
08.20.25 Join    midk [0] (~midk@c-24-18-39-204.client.comcast.net)
08.21.29 Join    Bagder [241] (~dast@labb.contactor.se)
08.21.44 #       <Bagder> morning
08.21.53 #       <midk> hey bagder
08.25.38 #       * Bagder hates coming to work only to find that someone took your "target" so now I can't test my code
08.25.51 #       <midk> :(
08.26.30 #       <Bagder> btw, I bought a new rec20 from a UK guy last week
08.26.43 #       <midk> oh, great
08.26.44 #       <Bagder> not new then, used of course
08.26.47 #       <midk> when do you get it?
08.26.58 #       <midk> i doubt you could easily find a new one, they're so old
08.27.00 #       <Bagder> I hope I'll get it in a few days
08.27.38 #       <Bagder> I miss my rockbox
08.27.38 #       <midk> great great
08.27.41 #       <midk> :)
08.40.03 Join    Madman [0] (~madmangor@adsl-69-224-113-50.dsl.irvnca.pacbell.net)
08.40.33 Quit    Madman (Client Quit)
08.53.51 Join    amiconn [0] (~jens@pD9E7E7AD.dip.t-dialin.net)
09.13.22 Join    Zagor [242] (~bjst@labb.contactor.se)
09.26.43 ***     Saving seen data "./dancer.seen"
09.29.41 Join    kurzhaarrocker [0] (~knoppix@p508775EB.dip0.t-ipconnect.de)
10.33.21 Part    kurzhaarrocker
11.01.13 Nick    midk is now known as midk|sleep (~midk@c-24-18-39-204.client.comcast.net)
11.01.15 #       <midk|sleep> nite everyone
11.01.25 #       <Bagder> sweet dreams
11.19.53 Join    lImbus [0] (~manuel@kernel.cycos.net)
11.26.47 ***     Saving seen data "./dancer.seen"
11.39.48 Join    mbrisou [0] (~mbrisou@217.109.194.238)
11.44.22 #       <mbrisou> EHLO
11.48.24 #       * oxygen77 is away: chui pas là
11.48.57 Part    mbrisou ("Leaving")
11.51.57 Join    kurzhaarrocker [0] (~knoppix@p508775EB.dip0.t-ipconnect.de)
11.52.22 #       <kurzhaarrocker> Bagder do you at least have a backup of your music collection?
11.54.19 Quit    Hes ("Changing server")
11.54.19 Join    hessu [0] (~hessu@he.fi)
11.58.38 Join    mroizo [0] (~chatzilla@kabel218248.mobiel.utwente.nl)
11.58.45 #       <mroizo> #gmemu
12.00.25 Join    Strath [0] (~mike@dgvlwinas01pool0-a226.wi.tds.net)
12.00.59 #       <Strath> hey kurzhaarrocker
12.01.31 #       <kurzhaarrocker> Hi :D
12.23.52 Quit    kurzhaarrocker (orwell.freenode.net irc.freenode.net)
12.23.52 NSplit  orwell.freenode.net irc.freenode.net
12.23.52 Quit    Dstar5 (orwell.freenode.net irc.freenode.net)
12.23.52 Quit    webmind (orwell.freenode.net irc.freenode.net)
12.24.16 NHeal   orwell.freenode.net irc.freenode.net
12.24.16 NJoin   kurzhaarrocker [0] (~knoppix@p508775EB.dip0.t-ipconnect.de)
12.24.16 NJoin   Dstar5 [0] (~441cbb6b@labb.contactor.se)
12.24.16 NJoin   webmind [0] (~random@217-195-236-172.dsl.esined.net)
12.24.31 #       <Bagder> kurzhaarrocker: I do have my music backed up, so no worries there at least
12.24.47 Quit    kurzhaarrocker (Read error: 104 (Connection reset by peer))
12.24.53 #       <Strath> lol
12.25.01 Join    kurzhaarrocker [0] (~knoppix@p508775EB.dip0.t-ipconnect.de)
12.25.06 #       <Strath> wb
12.35.01 Join    Nibbler [0] (~andrer@port-212-202-73-54.dynamic.qsc.de)
12.59.36 Join    ze__ [20] (psyco@adsl-63-205-46-145.dsl.lsan03.pacbell.net)
12.59.36 Quit    Nibbler (Read error: 54 (Connection reset by peer))
12.59.41 Join    Bagder_ [241] (~dast@labb.contactor.se)
13.00.32 Quit    Bagder (orwell.freenode.net irc.freenode.net)
13.00.32 NSplit  orwell.freenode.net irc.freenode.net
13.00.32 Quit    ze (orwell.freenode.net irc.freenode.net)
13.00.32 Quit    dwihno (orwell.freenode.net irc.freenode.net)
13.00.32 Quit    Zagor (orwell.freenode.net irc.freenode.net)
13.00.32 Quit    mbr (orwell.freenode.net irc.freenode.net)
13.00.32 Nick    ze__ is now known as ze (psyco@adsl-63-205-46-145.dsl.lsan03.pacbell.net)
13.00.41 Nick    Bagder_ is now known as Bagder (~dast@labb.contactor.se)
13.01.01 NHeal   orwell.freenode.net irc.freenode.net
13.01.01 NJoin   Zagor [242] (~bjst@labb.contactor.se)
13.01.01 NJoin   mbr [0] (~mb@stz-softwaretechnik.com)
13.01.54 Nick    kurzhaarrocker is now known as kurzhaarrocker|m (~knoppix@p508775EB.dip0.t-ipconnect.de)
13.02.08 Part    kurzhaarrocker|m
13.05.04 NJoin   dwihno [0] (~dw@81.8.224.89)
13.09.36 Join    AciD [0] (~acid@longchamp44-1-82-67-133-87.fbx.proxad.net)
13.26.48 ***     Saving seen data "./dancer.seen"
13.27.26 #       * oxygen77 is back (gone 01:39:01)
13.34.57 Quit    oxygen77 ("Cho")
13.51.40 Quit    mroizo ("Chatzilla 0.9.64a [Mozilla rv:1.7/20040614]")
14.17.49 Join    kurzhaarrocker [0] (~knoppix@p508775EB.dip0.t-ipconnect.de)
14.18.04 #       <kurzhaarrocker> Is it really desirable to have french text in the wiki?
14.18.27 #       <kurzhaarrocker> http://rockbox.haxx.se/twiki/bin/view/Main/FaqBatteries
14.18.50 #       <webmind> next to english or french only ?
14.18.52 #       <Strath> do you realize how many people who speak french there are working on archos stuff?
14.19.16 #       <kurzhaarrocker> It's a page in french only
14.19.19 #       <webmind> ah
14.19.26 #       <webmind> then it could use translation :)
14.19.26 #       <Strath> (besides archos employees ;) )
14.19.52 #       <kurzhaarrocker> To me it seems as it might be a translation of the english battery faq
14.20.16 #       <webmind> ok
14.21.33 #       <kurzhaarrocker> Strath: But should we mix the languages within one wiki?
14.22.11 #       <Strath> up to you... i don't speak french, so it doesn't matter to me ;)
14.23.08 #       <kurzhaarrocker> The grades I received for my french lessons prove that I don't speak french either.
14.25.10 #       <webmind> kurzhaarrocker, well demanding english only would not be nice to the french.. and the otherway around for the non-french
14.26.13 #       <kurzhaarrocker> Is there a wiki-police? :)
14.30.21 #       <Bagder> you applying for the job? ;-)
14.30.28 Join    oxygen77 [0] (~Chris@pauguste-7-82-66-87-78.fbx.proxad.net)
14.30.39 #       <lImbus> I do speak french, amongst other languages, and it looks to me like JocelynDelalande ist currently translating the BatteryFAQ.
14.30.48 #       * kurzhaarrocker hides from the wiki-police job
14.40.23 Join    Nibbler [0] (~andrer@port-212-202-73-54.dynamic.qsc.de)
14.50.03 #       <amiconn> Hi all
14.50.25 #       <kurzhaarrocker> Hi amiconn. Any news from the recording-bug front?
14.50.54 #       <amiconn> Bad news for all core developers: It seems like there is some function in rockbox which trashes innocent memory.
14.51.14 #       <Bagder> can you repeat the problem?
14.52.19 #       <amiconn> Unfortunately, this bug is not triggered often, but yesterday I observed the following odd behaviour:
14.53.31 #       <amiconn> (1) I was listening to some music (shuffled dynamic playlist, created via on+play on the directory and selecting playlist->add)
14.54.08 #       <amiconn> (2) As I went away for a short time, I only stopped playback, but didn't shut down the box
14.54.48 #       <amiconn> (3) When I came back, I hit ON to resume, but didn't get the resume question. Instead, it told me about a corrupt playlist control file.
14.55.13 #       <Bagder> ugh
14.55.28 #       <amiconn> (unfortunately my brain wasn't fast enough to realize I should save that file for analysis. I didn't have my computer with me)
14.57.01 #       <amiconn> (4) The file browser was still in the dir where my files are located (via follow playlist = yes). When I hit "Left", it should have gone one dir level up (which it did) - but the cursor was not positioned on the dir I just left, but on some other random file!
14.57.38 #       <amiconn> (5) Switching the box off and back on returned everything to normal (of course I had to create a new dynamic playlist)
14.58.23 #       <Bagder> this may explain why others have reported broken playlist control files
14.59.10 #       <amiconn> That all combined is why I believe there is something trashing other thread's memory - in my case it may have corrupted the playlist control as wel as the browser's dir buffer
14.59.35 #       <Bagder> I think you're right
15.00.17 #       <amiconn> The "only" thing is - we have to find out what it is
15.02.38 #       <Bagder> yeps, and it is likely hard to repeat using the sim
15.02.46 #       <amiconn> yup
15.03.47 #       <amiconn> Yesterday I got an idea how to check if there is something wrong with rombox, i.e. trying to write to the rom - using the user break interrupt feature of the sh1
15.07.14 #       <amiconn> I'll look into it this evening - perhaps it may help to get the rombox recording issue sorted
15.16.01 #       <amiconn> kurzhaarrocker: That recording bug issue is really strange. I'll have to do further test recordings. Maybe the MAS firmware itself has a bug...
15.17.02 #       <kurzhaarrocker> I still am confused because I never encountered any audiable recording bug problems. But to be honest I usually record with a patched firmware from January/04.
15.26.51 ***     Saving seen data "./dancer.seen"
15.33.04 Join    [IDC]Dragon [0] (~d90a3255@labb.contactor.se)
15.34.56 #       <amiconn> hi Jörg
15.48.04 Quit    [IDC]Dragon ("CGI:IRC (Ping timeout)")
16.36.25 Quit    Strath ("Client closed")
16.46.00 Join    Lee_ [0] (Lee@ACC483A3.ipt.aol.com)
16.46.13 #       <Lee_> hey Dstar5 is still here     lol
16.46.21 #       <Lee_> i was using it on a cell phone
16.46.55 #       <kurzhaarrocker> ? A jukebox on a phone?
16.47.05 Quit    Dstar5 (Nick collision from services.)
16.47.15 #       <Lee_> no, i was using IRC on a phone
16.47.41 Nick    Lee_ is now known as dstar5 (Lee@ACC483A3.ipt.aol.com)
16.47.45 #       * kurzhaarrocker shakes his head
16.48.01 #       <dstar5> i used cgiirc     lol
16.49.08 #       <dstar5> it didn't work well on the phone
16.49.14 #       <dstar5> it was weird
16.49.27 #       <dstar5> it had names of pages like fmain, fuserlist, and fmsg
16.49.39 #       <kurzhaarrocker> Then use a wired phone! MUAHAHAH! 
16.49.54 #       <dstar5> heh
16.55.35 Join    [IDC]Dragon [0] (~d90a3255@labb.contactor.se)
16.56.13 Quit    [IDC]Dragon (Client Quit)
16.57.01 Join    [IDC]Dragon [0] (~d90a3255@labb.contactor.se)
16.57.21 #       <dstar5> hey [IDC]Dragon 
16.57.36 #       <dstar5> is that board working yet? :)
16.59.21 #       <[IDC]Dragon> hi dstar5 
16.59.33 #       <[IDC]Dragon> I still haven't tried
16.59.41 #       <[IDC]Dragon> lots of other worries:
16.59.55 #       <[IDC]Dragon> a HD in my PC died
17.00.10 #       <dstar5> ouchhh
17.00.11 #       <[IDC]Dragon> a part of a tooth of mine broke off
17.00.20 #       <dstar5> ouchhhh
17.00.35 #       <dstar5> thats really bad
17.00.37 #       <[IDC]Dragon> the HD is replaced now, but not my tooth
17.00.45 #       <dstar5> :(
17.01.02 #       <dstar5> i lost everythig on my drive about 5 times within a week
17.01.14 #       <dstar5> turned out to be a bad IDE cable
17.01.37 #       <[IDC]Dragon> after the first one, it wasn't much to lose, I guess  :-(
17.01.59 #       <dstar5> yes
17.02.18 #       <[IDC]Dragon> I was lucky, recovered most of the data
17.02.26 Part    kurzhaarrocker
17.02.34 Part    oxygen77 ("Cho")
17.02.38 #       <dstar5> thats good :)
17.02.48 #       <dstar5> what went wrong with it?
17.02.49 #       <[IDC]Dragon> and bought 2 new disks, I have a RAID now
17.02.57 #       <dstar5> nice :)
17.03.03 #       <[IDC]Dragon> the one just died of age, I guess
17.03.37 #       <[IDC]Dragon> it still works, but has plenty of errors
17.03.38 #       <dstar5> how much storage on the disks?
17.03.49 #       <[IDC]Dragon> 160 GB each
17.04.01 #       <[IDC]Dragon> (the broken one, and the 2 new)
17.04.12 #       <dstar5> i have 1 160gb drive
17.04.28 #       <dstar5> it was very cheap, got it for $90
17.04.35 #       <[IDC]Dragon> those are the most economical
17.04.49 #       <[IDC]Dragon> got mine for %u20AC84
17.05.00 #       <[IDC]Dragon> EUR 84, that is
17.05.19 #       <[IDC]Dragon> about the same, I guess
17.05.27 #       <dstar5> ahh, that would be about what i got mine for
17.05.38 #       <dstar5> euro/dollar are quite close
17.06.00 #       <[IDC]Dragon> I wanted a larger one, but they are overproportionally expensive
17.06.07 #       <[IDC]Dragon> like 300 GB
17.06.26 #       <[IDC]Dragon> then I remembered the RAID feature of my mainboard
17.06.55 #       <[IDC]Dragon> works pretty well now, with that disk pair, blazingly fast
17.07.03 #       <dstar5>  1 EUR = 1.22005 USD
17.07.07 #       <dstar5> 7200rpm?
17.07.11 #       <[IDC]Dragon> yes
17.07.23 #       <[IDC]Dragon> and times two, for the stripe
17.07.49 #       <[IDC]Dragon> Samsung makes very quiet disks
17.07.51 #       <dstar5> now what about 2 radtors ;)     10,000 rpm each
17.08.18 #       <dstar5> my drive is western digital
17.08.47 #       <dstar5> *raptors
17.10.05 #       <[IDC]Dragon> sounds noisy?
17.10.47 Quit    AciD (Connection timed out)
17.11.03 #       <dstar5> no, very quite, except when the drive is powering on, it has a loud spinup
17.11.22 #       <dstar5> much quiter than my dads 40gb drive in the same machine'
17.11.38 Join    mattzz [0] (~d90a3255@b120199.adsl.hansenet.de)
17.12.19 #       <[IDC]Dragon> hi mattzz!
17.12.31 #       <[IDC]Dragon> home again?
17.13.02 #       <mattzz> hi joerg - yup
17.13.21 #       <mattzz> wasp experience...
17.13.49 #       <[IDC]Dragon> wasp? you got stinged?
17.14.36 #       <mattzz> we were on that company trip last weekend. Thousands of wasps. Unfortunately the only one who got stinged was my daughter. But she is fine again.
17.15.36 #       <dstar5> i am going to go write some c0de
17.15.38 #       <dstar5> see you
17.15.55 #       <mattzz> project camp is finished as well - so we are going back to normal - kind of...
17.16.04 Quit    dstar5 ("umount /dev/brain")
17.16.37 #       <[IDC]Dragon> mattzz: didn't know you've got family...
17.16.58 #       <mattzz> three fine women ;-)
17.17.18 #       <[IDC]Dragon> three! impressive.
17.17.34 #       <mattzz> well, two girls, one woman to be precise
17.17.44 #       <[IDC]Dragon> I suspected that.
17.18.26 #       <mattzz> Is your phase of bad luck over?
17.19.35 #       <[IDC]Dragon> no, I need to get this code to work....   ;-)
17.26.52 ***     Saving seen data "./dancer.seen"
17.27.56 Join    slazZ [0] (slazZi@c146175.adsl.hansenet.de)
17.29.30 Quit    slazZ (Client Quit)
17.29.42 Part    Bagder
17.41.30 Join    edx [0] (edx@p548793BC.dip.t-dialin.net)
17.43.08 Part    Zagor
17.44.39 Quit    mattzz ("CGI:IRC")
17.47.23 Join    mecraw [0] (~lmarlow@69.2.235.2)
17.54.59 Part    lImbus
18.14.30 #       <[IDC]Dragon> amiconn: r u there?
18.14.50 #       <amiconn> [IDC]Dragon: Yep; just came home :)
18.17.46 #       <[IDC]Dragon> saw your idea to use the user break controller to trap bad writes, good idea!
18.18.03 #       <[IDC]Dragon> (poor man's MMU)
18.19.36 #       <amiconn> yup. Unfortunately the user break controller does only provide control over one area, which must be sized 2^n
18.20.59 #       <amiconn> Otherwise it could be used to track down other bugs, e.g. the memory trashing I suspect to be the cause for the odd behaviour I expereinced yesterday
18.22.28 #       <[IDC]Dragon> the ISR can filter that out, but severly degrades performance
18.22.44 #       <amiconn> I'm actually thinking of a way to do this with the user break controller (by capturing writes to the area that contains the dir browsers buffer, and then filtering in the isr
18.22.52 #       <amiconn> :)
18.23.21 #       <amiconn> All that means I have to figure out how to implement such an ISR
18.23.39 #       <[IDC]Dragon> I once looked into the UBC, to allow gdb to step through ROM
18.23.45 Join    _aLF [0] (~alex@mutualite-3-82-67-66-128.fbx.proxad.net)
18.23.48 #       <_aLF> hi
18.23.56 #       <[IDC]Dragon> but it turned out impractical
18.24.17 #       <amiconn> [IDC]Dragon: Iirc the sh1 features a single step mode
18.24.43 #       <[IDC]Dragon> I'm not aware of that
18.28.00 #       <[IDC]Dragon> while you do such anvanced stuff, I'll rotate the font, if you don't mind
18.29.46 #       <amiconn> Ok, I remembered wrong. But it should be possible to mimic a single step mode by utilizing the UBC
18.31.05 #       <[IDC]Dragon> iirc, branches were an unsolvable problem
18.31.23 #       <[IDC]Dragon> rendering it useless for a debugger
18.31.30 #       <[IDC]Dragon> but I don't remember why
18.34.47 #       <amiconn> Probably because if a user break is triggered by a delay slot instruction, the break interrupt is delayed until after the instruction
18.35.06 #       <amiconn> (Just reading the notes)
18.45.47 #       <amiconn> [IDC]Dragon: For simply capturing writes to the ROM, it looks like I only have to initialize the UBC; the exception is already handled in system.c. Do I miss something?
18.45.48 #       <[IDC]Dragon> amiconn: please remind me how we wanted to do font rotation
18.46.09 #       <[IDC]Dragon> (UBC) sounds OK, yes
18.46.30 #       <[IDC]Dragon> (font) the glyphs are 16 bit words
18.46.56 #       <[IDC]Dragon> so using 8 bit (rotated or not) would break compatibility anyway?
18.48.11 #       <amiconn> Yes and no. The font glyph data is defined as being of bitmap_t type, which is 16bit.
18.48.55 #       <amiconn> In order to not break compatibility, the pointer itself has to stay that way, that means, each glyph must be short aligned.
18.49.41 #       <amiconn> This doesn't prevent us to use byte alignment within the glyph, because the actual drawing is handled by lcd_bitmap()
18.50.12 #       <[IDC]Dragon> and all chars are 6 byte wide, which happens to be even
18.50.25 #       <amiconn> Yup.
18.50.46 #       <[IDC]Dragon> got it
18.51.36 #       <amiconn> So basically, convbdf has to "learn" an additional output format ("rockbox raw"), with the glyphs already rotated and byte packed
18.52.20 #       <amiconn> Then the makefile has to use that to build font.[ch], and the rotate_font_bits() call taken out from the font init
18.52.38 #       <[IDC]Dragon> or just change the C output format, we won't use both
18.52.44 #       <amiconn> Of course the function itself has to stay, because it is needed for loaded fonts
18.52.52 Join    AciD [0] (~acid@longchamp44-1-82-67-133-87.fbx.proxad.net)
18.54.13 #       <amiconn> [IDC]Dragon: Further ideas for font handling:
18.54.36 #       <amiconn> (1) change the bitmap offsets into an array of short. This would require 2 different font structs, as discussed a while ago
18.56.06 #       <amiconn> (2) Do the font rotating (and perhaps changing to short offsets) on the fly for loaded fonts too. This would either allow larger fonts with the same font buffer size, or allow us to decrease the fonts buffer size
18.58.17 #       <amiconn> Font buffer size is currently 9000 bytes
18.59.06 Join    dstar5 [0] (Lee@ACC1F283.ipt.aol.com)
18.59.27 #       <dstar5> yay   checkers has a new life in it :)
18.59.33 #       <dstar5> i just figured out how to finsih it
19.03.27 Join    zeekoe_ [0] (~zeekoe@ip51cc69f6.adsl-surfen.hetnet.nl)
19.09.22 Nick    zeekoe_ is now known as zeekoe (~zeekoe@ip51cc69f6.adsl-surfen.hetnet.nl)
19.14.04 #       <amiconn> [IDC]Dragon: Capturing ROM writes via UBC works - I can't flash an .ucl with an UserBreak-enabled ajbrec.ajz. It complains about the plugin wanting to write to the ROM
19.17.31 #       <[IDC]Dragon> whow, that was quick!
19.17.54 #       <amiconn> It's only 3 lines in system.c :)
19.18.00 #       <[IDC]Dragon> what do you do in your ISR?
19.18.26 #       <amiconn> I didn't write a special ISR yet - only capturing the write via the default ISR
19.18.50 #       <amiconn> BAR = 0x02000000;  /* start address of ROM */
19.18.50 #       <amiconn> BAMR = 0x003FFFFF; /* match any ROM address */
19.18.50 #       <amiconn> BBR = 0x00F8;      /* Break on any write access, CPU & DMA, IF & data, any size */
19.19.47 #       <[IDC]Dragon> so we won't know who wrote where
19.20.07 #       <amiconn> If I want to use this for tracking other wrong writes, of course I have to write my own ISR
19.20.10 #       <[IDC]Dragon> but maybe we don't have to, if everybody behaves
19.20.45 #       <[IDC]Dragon> btw, you used an old flash plugin? The current one shoudn't run if ROM-based
19.20.50 #       <amiconn> We will know who writes there, because the default ISR outputs the source address
19.21.04 Join    etelcontar [0] (~cf2e7d12@labb.contactor.se)
19.21.06 #       <[IDC]Dragon> ah, OK
19.21.31 #       <[IDC]Dragon> so, go and record (or whatever)
19.21.35 #       <amiconn> No, I did run the flash plugin from a rolo'ed ajbrec.ajz (which had the rom-write detection enabled)
19.22.01 #       <etelcontar> hey guys, sorry to interrupt, but I wonder if you can help me out...
19.22.15 #       <[IDC]Dragon> a flash protection ;-)
19.22.48 #       <amiconn> [IDC]Dragon: This was just a first test, now I'll flash an .ucl with that, and try as much functions as I can think of
19.23.05 #       <amiconn> etelcontar: ?
19.23.39 Quit    etelcontar (Client Quit)
19.23.52 Join    etelcontar [0] (~cf2e7d12@labb.contactor.se)
19.23.53 #       <[IDC]Dragon> you have to ask, else I'm afraid we can't help
19.24.20 #       <etelcontar> hey.. my archos just locked up .. I upgraded to 2.2 the other day and now it is stuck on "error".. any thoughts?
19.24.43 #       <[IDC]Dragon> what error? when?
19.24.59 #       <zeekoe> etelcontar: you "upgraded" to 2.2? :-P
19.25.06 #       <[IDC]Dragon> flashed or regulear disk loading?
19.25.07 #       <etelcontar> I went to play a tune.. now the LCD diplay just says "Error"
19.25.20 #       <etelcontar> regular disk loading
19.25.53 #       <[IDC]Dragon> does it happen again, after power cycling?
19.26.02 #       <etelcontar> how do you power cycle? 
19.26.14 #       <[IDC]Dragon> shut it off, then on again
19.26.21 #       <etelcontar> HOW?
19.26.36 #       <etelcontar> There does not seem to be an "off" switch on this thing
19.26.51 #       <etelcontar> Studio 20
19.26.56 ***     Saving seen data "./dancer.seen"
19.27.19 #       <zeekoe> lol... how do you normally turn it off?
19.27.41 #       <etelcontar> I set the idle timeout to 1 minute and unplug the power
19.28.39 #       <zeekoe> hey.. you're right... i can also see just on & menu on studio 20
19.28.47 #       <[IDC]Dragon> hold stop for a while
19.29.02 #       <etelcontar> how long? I did that already
19.29.43 #       <etelcontar> ok.. that worked! (took about 30 seconds)
19.30.11 #       <[IDC]Dragon> if it's not crashed, this should be shorter
19.30.25 #       <[IDC]Dragon> (it's the normal power off, afaik)
19.31.05 #       <etelcontar> any song I try to play gives me the "Error"
19.32.21 Quit    AciD (Read error: 104 (Connection reset by peer))
19.33.47 #       <dstar5> could it be there is no .rockbox?
19.33.57 #       <dstar5> i am not sure how that errors look on the player
19.36.19 #       <[IDC]Dragon> etelcontar: you may want to try the Windows installation on the daily build page
19.36.41 #       <zeekoe> etelcontar: what version did you use before
19.36.44 #       <etelcontar> do I need a build environment for that?
19.36.50 #       <[IDC]Dragon> no
19.37.05 #       <etelcontar> I had 1.4 before (I think)
19.37.18 #       <zeekoe> ok :)
19.37.25 #       <zeekoe> you'll be amazed :)
19.37.26 #       <[IDC]Dragon> it's an install exe that doas everything for you, the most foolproof we have to offer
19.37.51 #       <etelcontar> ok, I will have to try that wehn I get home .. I have no USB cable here at the office
19.38.13 Join    AciD [0] (~acid@longchamp44-1-82-67-133-87.fbx.proxad.net)
19.38.20 #       <[IDC]Dragon> actually, where is that installer?
19.38.32 #       <[IDC]Dragon> I thought we have it in the daily build
19.38.54 #       <dstar5> we do
19.39.00 #       <[IDC]Dragon> ah, rightmost column
19.39.48 Join    de [0] (~uski@gandalf.digital-network.org)
19.39.57 #       <dstar5> i think that should just be made bold
19.40.00 #       <[IDC]Dragon> etelcontar: download the upper right link from http://rockbox.haxx.se/daily.shtml
19.40.09 #       <dstar5> make it standout for people that are new
19.40.26 #       <[IDC]Dragon> (most recent Windows installer)
19.41.02 Quit    de (Client Quit)
19.41.05 #       <zeekoe> maybe put it on the download page
19.41.05 #       <dstar5> or just make it seperate from the table, and make it above it
19.44.18 #       <amiconn> [IDC]Dragon: Good news: rockbox doesn't seem to try writing the rom (in all cases I could test so far)
19.44.45 #       <dstar5> bye
19.44.48 Quit    dstar5 ("umount /dev/brain")
19.45.09 #       <zeekoe> amiconn: is that good news?
19.45.23 #       <zeekoe> amiconn: now you still know the answer to the rec problems...
19.46.02 #       <etelcontar> well, thanks for the info.. I will try the Windows installer tonight. In the mean time.. is there any way I can blow away the archos.mod file and return to the Archos until then?
19.46.23 #       <etelcontar> without a USB cable that is
19.47.22 #       <amiconn> zeekoe: No, I still don't know what causes it, but I now know what does not cause it..
19.48.15 #       <amiconn> I think I'll have to rely on Linus doing some logic analyzing in order to understand what's going on there
19.49.02 #       <amiconn> I tried changing the hard mas reset into a soft reset. Unfortunately this didn't help anything
19.50.07 Quit    etelcontar ("CGI:IRC")
19.51.39 #       <amiconn> I just triggered the corrupt playlist control file bug again
19.52.14 Quit    hessu (Read error: 104 (Connection reset by peer))
19.53.16 #       <[IDC]Dragon> oh
19.53.39 Join    uski [0] (~uski@2001:7a8:3bb9:0:defa:ced:dead:beef)
19.55.43 Nick    midk|sleep is now known as midk (~midk@c-24-18-39-204.client.comcast.net)
19.58.21 #       <amiconn> It's actually quite easy to trigger the bug:
19.58.52 #       <amiconn> (1) Set the cursor over a directory containing music. Do not enter it.
19.59.15 #       <amiconn> (2) Press On+Play and select playlist->add. The music will start playing
19.59.38 #       <amiconn> (3) Hit OFF to stop, the hit ON again -> corrupt playlist control file
20.02.57 #       <[IDC]Dragon> hooray
20.03.08 #       <amiconn> So it seems that the playlist control file handling is wrong if the playlist is generated that way. It doesn't have to do with trashed memory
20.03.11 #       <amiconn> [IDC]Dragon: ?
20.04.57 Join    maikeul [0] (~gromit@ALagny-151-1-7-101.w82-121.abo.wanadoo.fr)
20.10.46 Join    pfavr [0] (~Peter_Fav@213.237.46.232.adsl.ron.worldonline.dk)
20.14.01 Join    Strath [0] (~mike@dgvlwinas01pool0-a226.wi.tds.net)
20.14.51 #       <Strath> the new main page design for http://www.donat.org/archos just went live
20.17.18 #       <midk> stop advertising. ;)
20.17.42 #       <Strath> lol
20.17.48 #       <Strath> i'm not
20.18.27 #       <Strath> i'm just letting people know so they can marvel at the pretty new main page
20.18.53 #       <midk> resize those logos in photoshop.
20.18.59 #       <Strath> ?
20.19.14 #       <Strath> whats wrong with em?
20.19.52 #       <midk> pixelated?
20.19.55 #       <midk> at least in mozilla.
20.20.47 #       <Strath> what size would you like em?
20.21.29 #       <midk> the same size...
20.21.36 #       <midk> dah, they're just pixelated
20.22.04 #       <Strath> i supose i could blur em a bit
20.22.17 #       <midk> why are they pixelated?
20.22.32 #       <midk> take the large rockbox logo and downsize it, not the small one and increase its size.
20.22.32 #       <Strath> no idea...
20.22.38 #       <Strath> did
20.22.51 #       <Strath> rockbox400.png, resized to 200
20.23.02 Quit    gromit`aw (Read error: 110 (Connection timed out))
20.23.07 #       <Strath> thats what it was/is
20.23.29 #       <Strath> (redid again, looks the same to me)
20.23.40 #       <midk> looks fine?
20.23.57 #       <Strath> i didn't say that ;)
20.24.15 #       <midk> how are you resizing it?
20.28.27 #       <Strath> bicubic
20.29.24 #       <Strath> i think i know....
20.29.33 #       <Strath> i had left it as indexed colour
20.30.23 Join    lImbus [0] (lImbus@16.114-136-217.adsl.skynet.be)
20.31.08 #       <Strath> better?
20.31.13 #       <[IDC]Dragon> amiconn: sorry for not paying attention
20.31.42 #       <[IDC]Dragon> I think my rotated font works, that distracted me
20.31.47 #       <midk> stath: ho.. :(
20.31.49 #       <midk> no*
20.32.27 #       <midk> http://www.freewebs.com/midky/snapshot1.jpg
20.32.33 #       <midk> see the rockbox/avos logos at the left
20.34.54 #       <Strath> wow that looks bad
20.35.04 #       <Strath> but thats just your libs
20.35.34 #       <Strath> looks fine in Firefox/win32
20.35.47 #       <midk> firefox looks the same
20.36.11 #       <Strath> you want me to upload a screenshot?
20.36.37 #       <midk> yes.
20.36.45 Join    jakesir [0] (solaris@pool-141-157-47-182.balt.east.verizon.net)
20.37.07 #       <[IDC]Dragon> hi Jake
20.38.36 #       <jakesir> hello
20.38.51 #       <jakesir> what's the latest to my problem?
20.40.28 #       <Strath> midk, uploading to temp, i'm going to sleep
20.41.00 Nick    Strath is now known as StrathAFK (~mike@dgvlwinas01pool0-a226.wi.tds.net)
20.41.33 #       <midk> ok
20.41.34 #       <midk> nite
20.42.10 #       <[IDC]Dragon> jakesir: you have read my emails?
20.42.21 #       <jakesir> yeap
20.42.33 #       <[IDC]Dragon> since then, nothing changed, I had to give up
20.42.59 #       <[IDC]Dragon> please tell me what to flash on it before returning it
20.43.00 #       <jakesir> lol
20.43.09 #       <jakesir> ummm.... 2.2
20.43.18 #       <jakesir> and i'm happy to live with that
20.43.20 #       <[IDC]Dragon> PK
20.43.23 #       <[IDC]Dragon> OK
20.43.42 #       <jakesir> does it play alright under 2.2?
20.44.01 #       <[IDC]Dragon> you shoudn't change that, since your box has this disk read/write problem
20.44.22 #       <jakesir> ok
20.44.29 #       <jakesir> i'll stick to 2.2 forever
20.44.36 #       <midk> boooooo
20.44.45 #       <[IDC]Dragon> I think it plays, 1 bad bit every 8KB is probably not very audible
20.44.55 #       <jakesir> hmmmm
20.45.00 #       <[IDC]Dragon> although I wonder
20.45.07 #       <jakesir> well, i mainly use it for audio books
20.45.13 #       <jakesir> so, it won't matter too much
20.45.17 #       <[IDC]Dragon> have to test, I think I never played mp3
20.45.53 #       <jakesir> did you see my HD content of audiobooks?
20.46.06 #       <[IDC]Dragon> and it has this severe starting problem, at least for me
20.46.44 #       <[IDC]Dragon> no, I'm too disceet to look at your disk
20.46.44 #       <jakesir> i have that same starting problem when the box is openned. it goes away when the casing is closed
20.46.50 #       <jakesir> lol
20.46.52 #       <midk> haha
20.47.40 #       <[IDC]Dragon> seriously, I only put Rockbox on and off
20.48.09 #       <midk> i trust idc
20.48.41 #       <jakesir> you can delete the whole HD, i don't care
20.48.52 #       <[IDC]Dragon> no, why should I?
20.49.29 #       <jakesir> i meant that i have back-ups??
20.50.51 #       <jakesir> isn't 2.3 due soon?? it's been 5 month...
20.51.04 #       <[IDC]Dragon> overdue
20.51.19 #       <[IDC]Dragon> I could as well put a daily build on it
20.51.26 #       <jakesir> hmmmm
20.51.29 #       <jakesir> that's fine
20.51.48 Quit    pfavr ("ChatZilla 0.9.61 [Mozilla rv:1.7.2/20040810]")
20.53.33 Join    jakesirs [0] (solaris@pool-70-17-201-201.balt.east.verizon.net)
21.00.06 #       <midk> allchan say brb
21.00.15 Quit    midk (Remote closed the connection)
21.06.26 #       <amiconn> [IDC]Dragon: The playlist control file bug isn't reproducable on the sim :(
21.06.46 #       <[IDC]Dragon> I would have been surprised
21.07.13 #       <[IDC]Dragon> did I say the rotated font is working?
21.07.34 Join    midk [0] (midk@c-24-18-39-204.client.comcast.net)
21.07.35 #       <amiconn> So it looks like there might be a bug in either the file handling code (bad) or the fat driver (even worse) :((
21.07.52 #       <[IDC]Dragon> on the first shot, I was not prepared for that, suspected some old code to be running
21.08.11 #       <amiconn> [IDC]Dragon: (font rotation) nice :)
21.08.50 #       <[IDC]Dragon> I changed the algorithm to something wrong, to find out if it has an effect, but it did
21.08.59 Quit    midk (Read error: 104 (Connection reset by peer))
21.09.05 Join    midk [0] (midk@c-24-18-39-204.client.comcast.net)
21.11.15 Quit    jakesir (Read error: 110 (Connection timed out))
21.11.31 #       <[IDC]Dragon> sorry for uncomfotable playlist control file debugging
21.11.49 #       <[IDC]Dragon> do you really think it's the file system?
21.11.59 #       <[IDC]Dragon> not some astray pointer?
21.13.28 #       <amiconn> What I did understand so far: (1) If a playlist is generated the way I described (via On+Play) on the dir), it is much longer  than otherwise - every single file is listed on a separate line
21.14.15 #       <amiconn> (2) The corrupt files just end prematurely, but not always at the same position (and the position is not sector aligned)
21.17.05 #       <[IDC]Dragon> I have to leave now.
21.17.23 #       <[IDC]Dragon> cu guys
21.17.30 Part    [IDC]Dragon
21.22.38 Join    zeekoe_ [0] (~zeekoe@ip51cc69f6.adsl-surfen.hetnet.nl)
21.27.00 ***     Saving seen data "./dancer.seen"
21.33.54 Join    zeekoe2 [0] (zeekoe@vpn007140.vpn.utwente.nl)
21.38.01 Nick    midk is now known as midk|shower (midk@c-24-18-39-204.client.comcast.net)
21.40.40 Quit    zeekoe (Read error: 110 (Connection timed out))
21.48.04 Join    dstar5 [0] (Lee@ACC47BDC.ipt.aol.com)
21.51.56 Quit    zeekoe_ (Read error: 110 (Connection timed out))
21.56.44 Nick    midk|shower is now known as midk (midk@c-24-18-39-204.client.comcast.net)
22.03.48 Quit    midk (Read error: 104 (Connection reset by peer))
22.03.57 Join    midkay [0] (midk@c-24-18-39-204.client.comcast.net)
22.09.03 Join    Bagder [0] (~daniel@1-1-5-26a.hud.sth.bostream.se)
22.09.25 #       <amiconn> hi Bagder
22.09.32 #       <Bagder> evening
22.09.48 Quit    midkay (Read error: 104 (Connection reset by peer))
22.10.06 #       <amiconn> Bagder: di you read about my findings about the corrupt playlist control file bug?
22.10.40 #       * Bagder checks
22.12.15 #       <zeekoe2> oh... if you're talking about bugs anyway, when you press play, then on, a bit later off, the resume point is set to the point where you pressed on
22.12.23 #       <zeekoe2> is that supposed to happen?
22.12.44 #       <dstar5> i found a bug in flash
22.12.50 #       <Bagder> the resume point is set all the time
22.13.00 #       <zeekoe2> Bagder: it is???
22.13.02 #       <dstar5> if you are charging using archos firmware, and plug in usb, you get ata error -31
22.13.11 Quit    uski ("brb")
22.13.12 #       <dstar5> same if you press on when archos charging
22.13.14 #       <zeekoe2> Bagder: but now when for example browsing files
22.13.17 #       <amiconn> dstar5: Yes, we know
22.13.46 #       <amiconn> dstar5: I found that last week, reported it to [IDC]Dragon, and he said Linus pointed it to him 2 weeks ago...
22.14.19 #       <amiconn> dstar5: It has to do with the cold start detection not being perfect...
22.14.35 #       <dstar5> ok
22.14.58 #       <dstar5> time for a new nick
22.15.02 Nick    dstar5 is now known as bagawk (Lee@ACC47BDC.ipt.aol.com)
22.15.40 #       <zeekoe2> uh
22.15.43 #       <zeekoe2> s/now/not
22.15.44 Join    midk [0] (midk@c-24-18-39-204.client.comcast.net)
22.15.46 #       <Bagder> amiconn: maybe you should talk to hardeep about that playlist control bug, as he's the author of that
22.16.02 #       <amiconn> ah
22.16.46 #       <amiconn> hardeep has been offline for almost 3 weeks now...
22.21.27 Quit    jakesirs ("—I-n-v-i-s-i-o-n— 2.0 Build 3515")
22.26.44 Quit    midk ("just STOP it arspy")
22.27.58 Join    midk [0] (midk@c-24-18-39-204.client.comcast.net)
22.30.28 Quit    midk (Client Quit)
22.30.36 #       <amiconn> Bagder: It found out some more: If I create a playlist that way, DON'T stop the playback but plug in USB and look into the .playlist_control, it looks alright
22.31.14 #       <amiconn> After unplugging USB and re-plugging it, it is chopped the same way as it is when I hit OFF to stop
22.31.21 Join    midk [0] (midk@c-24-18-39-204.client.comcast.net)
22.31.31 #       <Bagder> hm
22.35.14 Join    LinusN [200] (~linus@labb.contactor.se)
22.36.49 #       <amiconn> hi LinusN
22.37.31 #       <LinusN> howdy
22.38.01 Quit    midk ("just STOP it arspy")
22.39.23 Join    midk [0] (~midk@c-24-18-39-204.client.comcast.net)
22.42.44 #       <amiconn> LinusN: Read about the .playlist_control woes?
22.43.51 #       <bagawk> hey LinusN 
22.44.04 #       <bagawk> this is my new nick (i was dstar5)
22.46.09 #       <LinusN> amiconn: yes
22.46.52 #       <LinusN> bagawk: hi
22.47.51 #       <LinusN> i have suspected file system problems for a long time
22.49.34 #       <amiconn> LinusN: It seems rockbox likes to annoy me - while I try to hunt down one bug (or just want to use it), it presents me with another one :(
22.49.59 #       <LinusN> welcome to the club...
22.50.44 #       <LinusN> i have also suspected that the recording bug is a file system problem as well
22.52.07 #       <LinusN> so, how shuld we implement file/dir move in the UI?
22.53.57 #       <Bagder> probably cut and paste style
22.54.01 #       <Bagder> with on+play
22.55.00 #       <LinusN> my thought as well
22.55.29 Join    Zane [0] (~4035995f@labb.contactor.se)
22.55.43 #       <Zane> Yo
22.55.58 #       <Zane> who here knows where to get a good chat server?
22.56.38 #       <amiconn> LinusN: If you decide to do some logic analyzing - could you try to capture the recording init while running from ROM?
22.56.59 #       <amiconn> LinusN: Changing the hard reset into a soft reset didn't help...
22.57.27 #       <amiconn> The reset itself worked, but trying to record still hangs at 30 bytes
22.58.17 Quit    bagawk (Read error: 104 (Connection reset by peer))
22.58.35 Quit    Zane (Client Quit)
22.59.37 #       <LinusN> amiconn: so the recording bug is still worse in ROM?
22.59.58 #       <amiconn> It depends about which bug you are talking...
23.00.02 Quit    midk (Remote closed the connection)
23.00.14 #       <LinusN> ah, so the 30-byte bug is only in rom?
23.00.45 #       <amiconn> The bug which trashes either individual frames or the whole remainder of the file seems to be independent from where rockbox is running
23.01.29 #       <amiconn> However, the bug where recording hangs after 30 bytes is very prominent when running from rom, and occurs only rarely when running from ram
23.01.33 #       <LinusN> is it any different if you have prerecording enabled?
23.03.09 #       <amiconn> (see my description within the Wiki article)
23.03.17 #       <LinusN> you should try to increase the sleep(20) in init_recording
23.03.21 #       <amiconn> Hmm, I didn't try prerecording yet
23.03.29 Join    bagawk [0] (Lee@ACC16FFD.ipt.aol.com)
23.04.21 Join    midk [0] (~midk@c-24-18-39-204.client.comcast.net)
23.04.33 #       <amiconn> Yes, increasing the sleep() time within mas_reset() lowers the probability of triggering the bug, but doesn't get rid of it
23.04.39 #       <LinusN> ic
23.05.05 #       <LinusN> how long have you set it to?
23.06.11 #       <amiconn> 200 ms gave me 60% failure rate, 500 ms gave 20% (this is when running from ROM)
23.06.15 #       <LinusN> amiconn: i'm not talking about the delay in mas_reset()?
23.06.29 #       <amiconn> Huh?
23.06.38 #       <LinusN> i'm talking about the sleep(20) in init_recording()
23.07.12 #       <bagawk> amiconn: leaving the mas_reset() out was a bad thing?
23.07.20 #       <LinusN> where it waits for a frame to be encoded
23.07.25 #       <bagawk> (it has been working for me fine)
23.08.07 #       <LinusN> the mas reset should not be necessary
23.08.13 #       <amiconn> LinusN: That one I didn't touch (yet)
23.08.19 #       <LinusN> amiconn: try it
23.09.16 #       <amiconn> If we leave out the mas_reset() we have to make sure all parameters are reset to default. That's why I tried the soft reset (via the reset bits in the control register)
23.09.47 #       <amiconn> I still wonder why this hang does (almost) only happen when running from ROM...
23.11.29 #       <LinusN> 1) timing
23.11.41 #       <LinusN> 2) write-to-rom
23.12.11 #       <amiconn> LinusN: There is no write-to-rom, I checked it today (with the help of the user break controller)
23.12.21 #       <LinusN> ah
23.12.34 #       <LinusN> so it's probably a timing problem
23.13.24 #       <amiconn> And the check itself worked perfectly - I stumbled upon it myself when trying to flash an .ucl via an ajbrec.ajz containing that "rom protection"
23.13.57 #       <amiconn> -> Exception I0C:UserBrk at 0x091F8082
23.14.06 #       <amiconn> *poof*
23.18.22 #       * amiconn tries a recording init with sleep(50) - compiling...
23.18.27 Nick    zeekoe2 is now known as zeekoe (zeekoe@vpn007140.vpn.utwente.nl)
23.23.01 #       * amiconn flashing...
23.23.49 #       * amiconn testing...
23.24.47 #       * LinusN is holding his breath
23.27.02 ***     Saving seen data "./dancer.seen"
23.28.13 #       <amiconn> Error rate is almost the same - around 65% (20 tries)
23.28.23 Join    [IDC]Dragon [0] (~d9ff8d6f@labb.contactor.se)
23.28.50 #       <[IDC]Dragon> LinusN almost suffocated...
23.29.11 #       <[IDC]Dragon> sorry for log-peeking
23.29.23 #       <LinusN> the 30-byte bug is most likely related to the first-frame "trick"
23.29.40 #       <LinusN> i have seen it lots of times when developing the init code
23.30.01 #       <amiconn> Yeah, this took a bit longer because I stumbled once more about my rom-write catch (my flashed .ucl did still do that, so I had to boot with F1+On)
23.30.29 Quit    bagawk ("umount /dev/brain")
23.31.14 #       <[IDC]Dragon> LinusN: the font file format we use is something "standard"?
23.31.37 #       <Bagder> nope
23.31.55 #       <[IDC]Dragon> Rockbox proprietary?
23.32.00 #       <Bagder> yeps
23.32.01 #       <amiconn> LinusN: I wonder why that first frame trick is necessary in the first place...
23.32.13 #       <LinusN> amiconn: what happens if you set the delay to something really long, like half a second?
23.32.19 #       <LinusN> amiconn: read the comment
23.32.31 #       <amiconn> sleep(50) _is_ half a second...
23.32.43 #       <[IDC]Dragon> because I wonder if we should/could make it more efficient
23.32.43 #       * LinusN is silly
23.32.52 #       <midk> dhahahah what a joker.
23.34.16 #       <LinusN> amiconn: the irq handler is edge triggered, on the falling edge of EOD
23.34.58 #       <[IDC]Dragon> well, I'm off for sleep
23.35.07 #       <amiconn> nite [IDC]Dragon
23.35.08 Quit    [IDC]Dragon ("CGI:IRC (EOF)")
23.35.08 #       <LinusN> the trick records some data, and the drain_dma_buffer() will clear the dma buffer and raise EOD
23.37.03 Nick    midk is now known as midk|gone (~midk@c-24-18-39-204.client.comcast.net)
23.37.05 #       <midk|gone> bbl
23.40.01 #       <amiconn> LinusN: Yes, I read this. But I still don't get 2 things: (1) why the mas doesn't set eod high if it is started in monitoring mode directly, (2) why it shouldn't be sufficient to force it high by reading _without_ recording anything first
23.40.57 #       <LinusN> 1) This is why i call it "the silly MAS"
23.41.13 #       <amiconn> (Otherwise I think I shouldn't hurt to do this, and obviously extending that initial recording period doesn't change anything)
23.41.33 #       <LinusN> 2) clearing an empty dma buffer has no effect
23.42.04 Quit    AciD (Connection timed out)
23.42.32 Quit    Bagder ("Leaving")
23.43.49 #       <amiconn> On a related topic: I tried a 10 hour recording with m/s stereo switched off, and did not get a corrupt file. I'll have to do more tests (with a well-defined source, i.e. CD) to find out if it is really related to the m/s stereo setting
23.44.04 #       <LinusN> interesting
23.44.39 #       <amiconn> Maybe the mas firmware has another bug (why else would archos switch off m/s when it is on by default)
23.45.03 #       <LinusN> could be
23.45.19 Join    AciD [0] (~acid@longchamp44-1-82-67-133-87.fbx.proxad.net)
23.47.16 #       <amiconn> LinusN: Do you have logic analyzer captures of the archos firmware initializing the mas recording mode?
23.47.46 #       <LinusN> yes
23.47.51 #       <LinusN> ah, no
23.48.45 #       <LinusN> btw, are we using B2 versions of the MAS?
23.50.05 #       <amiconn> Yeps. Most likely all recorder have that version, because if I understand the specs correctly, this is the only version capable of recording
23.50.27 #       <LinusN> and the black magic is performed?
23.50.33 #       <amiconn> yup
23.55.38 #       <amiconn> The following things would be interesting to see as logic analyzer diagrams, containing EOD, PR, /RTW and the i2c communication:
23.55.53 #       <amiconn> (1) recording init done by archos firmware
23.56.02 #       <amiconn> (2) recording init done by rockbox
23.56.12 #       <amiconn> (3) recording init done by rockbox running from rom
23.57.33 #       <amiconn> (if such complex analysis would be at all possible; and I forgot the mas reset pin)
23.58.55 #       <amiconn> Btw: the i2c communication would be interesting by itself