--- Log for 04.04.105 Server: orwell.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 12 days and 8 hours ago 00.00.24 # Hmm. It seems I am unable to find their current source code on the site... 00.00.42 # yes, I read commit mails 00.01.25 # http://sourceforge.net/mailarchive/forum.php?forum=openneo-cvs 00.01.59 # the do all their development somewhere else and bulk-commit once every few months 00.02.19 # or so it seems at least 00.03.35 # any news on the multi codec arch.? 00.05.11 Join vol [0] (~jugga@cpe-24-194-97-147.nycap.res.rr.com) 00.05.37 Quit Rick (Read error: 131 (Connection reset by peer)) 00.06.56 Join Rick [0] (rick@wbar25.lax1-4.28.143.213.lax1.dsl-verizon.net) 00.13.44 Join GCarrier [0] (~gcarrier@tofu.eu.org) 00.16.13 Join kergoth [0] (~kergoth@covenant.kergoth.com) 00.16.33 # Bagder: Haha, it's indeed similar. Why do they come up with that now... strange... ? ;-) 00.17.22 # well, they move in mysterious ways ;-) 00.18.43 # From looking at it, their main loop should be a bit faster (unrolled once), but their initial and final tests look like they're slower 00.20.02 # I remember that it was really difficult to get the initial test (for short strings) to perform at least with the same speed as the C function. 00.20.17 # I first had a looped version as they do. It was slower 00.21.14 Join LinusN [0] (~linus@labb.contactor.se) 00.21.20 # hi LinusN 00.21.37 # hi LinusN 00.22.56 # shalom 00.23.21 # gheh. 00.24.09 # LinusN: I finally managed to write my graphics api documentation / proposal wiki page. http://www.rockbox.org/twiki/bin/view/Main/GraphicsAPI 00.26.51 # goodie 00.28.35 # Grr, next wiki spammer.... 00.40.50 Join StrathAFK [0] (~mike@dgvlwinas01pool0-a202.wi.tds.net) 00.41.29 # LinusN: hi 00.41.33 # helo 00.42.02 # LinusN: do you know what is maximum real bandwidth of USB 2.0 hi-speed channel? 00.42.12 # LinusN: in megabytes of real data 00.42.14 # 480mbit/s? 00.42.33 # yes... but those stop bits... other collision stuf... 00.42.54 # so i guess it is in the vicinity of 40Mbyte/s 00.43.07 # ok.. that is what i think too. 00.44.32 # some pages claim up to 60Mb, others say 50Mb 00.46.29 # then it is pretty good. :) 00.48.18 # btw, i have a question on SDRAM. it says that the minimum seek time for a address for Samsung ram is 5.5ns, and maximum is 1000ns. what is it depend on? 00.50.13 Quit Rick (Read error: 104 (Connection reset by peer)) 00.50.52 # XShocK: "seek time"????? 00.51.10 # there is no such thing as "seek time" in SDRAM 00.51.33 # maybe you mean "access time"? 00.51.45 # CLK cycle time. 00.52.23 # well, i guess their sdram isn't made to run with a too slow clock 00.52.45 # i just saw in on http://www.rockbox.org/twiki/pub/Main/DataSheets/Samsung_K4S561632D.pdf on page 8 i think... 00.53.00 # i saw 1000ns and was very scared by it 00.53.13 # so what does it mean? 00.53.15 # in fact, with a too slow clock, all available bandwidth will be used for refresh, so there will be no time left for actuall memory access 00.53.37 # scared? 00.54.42 # i was scared since if that memory sometimes require 1000ns just to access a byte of data, it will certainly not do the job i wanted it to do. 00.54.54 # i just wanted to know what that 1000ns actually ment 00.56.18 # clk cycle time is how fast the CLK can be 00.56.37 # mmm. ok. then fine. :)) 00.57.02 Join preglow [0] (thomj@s183a.studby.ntnu.no) 00.57.25 # but all accesses are equally fast with the same CLk rate 00.58.02 # so no matter what address i choose in ram it will be accessed in the same amount of time? 00.58.10 # yes 00.58.23 # anyone know what's inside of the ifp9xx boys? 00.58.41 # the first access in a burst takes 5 clocks, and the following accesses take 1 clock each 00.59.05 # preglow: no, but it could be the philips chip 00.59.28 Quit Strath (Read error: 110 (Connection timed out)) 00.59.35 # probably is 00.59.54 # preglow: i think i saw it somewhere. wait a sec 01.01.36 # hhm.. no sorry 01.01.38 # i want a good excuse to learn arm asm, god damnit! 01.02.16 # http://www.itime.cn/Article_Show.asp?ArticleID=3419&ArticlePage=7 01.02.39 # found something.. i don't know chineese thou.. :) 01.03.44 # i wish the table was even smaller 01.04.51 # http://www.itime.cn/UploadFiles/2004101311493811.gif 01.04.58 # the link was under it 01.05.02 # looks like the SAA7750 chipset 01.05.46 # no, wait, it's a newer one 01.05.55 # i love secretive hardware manufacturers 01.05.55 # arghh 01.07.54 Quit _Lucretia_ ("Leaving") 01.08.02 # what do we know of the dsp part in the saa7750? nothing? 01.08.29 # why do they even have a dsp part? arm should be more then capable of doing most dsp efficiently 01.09.37 # preglow: efficiently, perhaps, but the epic core is probably a lot more efficient than the arm7 01.10.12 # well, yes, dedicated dsp cores will always be more efficient for dsp than other designs, obviously 01.10.16 # we know a little about the epic core, but nothing about how to program it 01.10.22 # what do we know? 01.11.21 # we know a little about how to communicate with it, but not much more 01.11.37 # i still have a dialog with philips about it 01.12.39 # god, i wish they stopped being anal 01.12.43 # what the hell have they got to loose? 01.13.05 # i don't think philips is that secretive about it 01.13.25 # then hooray! 01.13.37 # it just isn't practical for customers to program the dsp core themselves 01.13.49 # so no customer has wanted to do it 01.13.58 Join Rick [0] (rick@wbar25.lax1-4.28.143.213.lax1.dsl-verizon.net) 01.14.12 # that's probably why the epic programmers guide wasn't released 01.14.48 # so there is still a small chance that we can get the information 01.14.53 # that would be great indeed 01.14.59 # as long as it doesn't cost philips anything 01.15.19 # they don't want to be burdened by loads of support questions 01.15.23 Join DJ_Dooms_Day [0] (~scottr@dialup-252.15.220.203.acc10-dryb-mel.comindico.com.au) 01.15.25 # well, it shouldn't provided they have the documentation in a practical form 01.15.44 # and there is a risk that the epic programmers guide doesn't exist at all 01.15.48 # indeed 01.16.14 # we'll see... 01.16.40 # would be fun, for sure 01.16.58 # indeed 01.17.19 # i love learning about new architectures 01.18.49 # can someone recomend a good source of knowledge of digital electronics? 01.18.51 # i also happen to want a flash based portable, heh 01.19.11 # XShocK: you mean an online resource for learning? 01.19.26 # online or paperprinted, any 01.19.30 # yes 01.19.36 # i have no idea... :-) 01.19.47 # heh 01.19.51 Join XavierGr [0] (~3e01ea1a@labb.contactor.se) 01.20.00 # i've got a couple of books 01.20.07 # but have no idea whether they're any good 01.20.28 # say their names anyway 01.20.32 # what do you mean by digital electronics? 01.20.43 # i guess amazon has hundreds of books about digital electronics 01.20.48 # i would have to dig in my book pile 01.21.04 # the sedra & smith one springs to mind, but that's analogue electronics as well 01.21.32 # * LinusN hasn't read a single book about digital electronics 01.21.34 # preglow: don't worry, i though that they right near you. :) 01.22.08 # XShocK: i'm sorry, i can't, i'm using a ton of books as support for my vinyl records, and the books in question are behind that arrangement, heh 01.22.37 # * preglow needs a bigger appartment 01.22.46 # but where to get that info? i had never ever thought that there is such a thing as FPGA 01.22.54 # oh, there is 01.23.11 # i've got a book on vhdl, i think 01.23.25 # i can't remember what i've sold and what i've still got 01.23.31 # :) 01.23.39 Quit XavierGr (Client Quit) 01.23.40 # XShocK, you could do worse than scour the support sites of the major semiconductor manufacturers 01.23.57 # Rushton, VHDL for Logic Synthesis 01.24.10 # they usually have reasonable downloads for manuals, application notes, white papers, demo code etc. 01.24.22 # it seems i did read a book about digital electronics after all... :-) 01.24.30 # then if you come across something you don't get, use google :) 01.24.32 # :) 01.25.11 # i don't get the difference between sram and sdram. :) 01.25.12 # for programmable logic, start with PIC chips... 01.26.09 # XShocK: static ram and dynamic ram are two very different architectures 01.26.22 # the 'd' is the difference... dynamic ram is more complex to use but cheaper because it's simpler 01.26.23 # Camilo: i have done a card emulator on pic 16f84a, it worked, but i couldn't manage it to work as i wanted because it didn't have enough speed. 01.27.02 # basically, dynamic ram can't hold the contents for very long, it has to be rewritten with the same info over and over again, called the "refresh" 01.27.14 # but both are accessed in the same amount of time, right? 01.27.25 # sram is usually faster 01.27.27 # depends on design, but no, usually not 01.27.55 # dram is accessed as a matrix, using rows and columns 01.27.55 # if you're using dynamic ram you have to consider what will refresh it etc. 01.28.19 # so you give it the row address first, then the column 01.28.28 # this slows down the accesses 01.30.10 *** Saving seen data "./dancer.seen" 01.30.27 # I don't get one more thing. this refresh process. Camilo, you said that i should manage refreshing those capacitors by myself? 01.30.31 # XShocK: google is your friend, there are lots of pages describing the basics of electronics 01.30.48 # XShocK: yes, the dram controller has to refresh the dram 01.30.56 # CPUs and microcontrollers tend to have refresh circuitry 01.31.13 # so you have to configure them to refresh according to the parameters ofthe DRAM you're using 01.31.37 # the programmer doesn't have to care about the refresh once the dram controller is set up 01.31.39 # ok. thanks.i though it does in itself. 01.31.54 # but you are constrained - usually to using the same sorts of row/column numbering for all your dram banks 01.33.38 # XShocK: actually, sdram has a self-refresh mode, but that is for powersaving purposes, when the computer sleeps 01.34.13 # LinusN: Speaking about access speeds - the sdram data path in the iriver is 32 bits wide, and 4-byte bursts are possible, correct? 01.34.23 # nope 01.34.29 # the path is 16-bit 01.34.50 # lovely 01.34.59 # yeah, isn't it? :-) 01.35.02 # so a one dword burst takes seven cycles 01.35.08 # as lame as it gets 01.35.35 # one dword = 5+1 bus cycles 01.35.48 # if a dword is 32 bits 01.36.16 # Okay, data path is 16 bits, but 4-*word* bursts are possible.... 01.36.52 # ahh, i thought the 5 cycle first access was without data read 01.37.14 # no, that includes the first word 01.37.16 # That means, if someone implements memcpy() and memset() using movem and an even number of registers, it should get a nice speedup... 01.37.30 # indeed 01.37.37 # yup 01.37.41 # so long as the move/copy is big enough 01.37.42 # Too bad my iriver still didn't arrive... 01.37.57 # amiconn: don't hold your breath 01.38.05 # night folks 01.38.09 # Camilo: nite 01.38.13 Quit Camilo ("Chatzilla 0.9.67 [Mozilla rv:1.8b2/20050309]") 01.38.13 # good night 01.38.15 # * Bagder goes to sleep as well 01.38.24 # * LinusN should sleep too 01.38.30 # * preglow is very tired 01.38.37 # and ignoring it for the third hour 01.38.45 # :-) 01.38.49 Join elinenbe [0] (trilluser@207-237-225-9.c3-0.nyr-ubr1.nyr.ny.cable.rcn.com) 01.38.50 # it's getting harder 01.39.03 # and I need to finish my Psychology outline. :) 01.39.05 # amiconn: but yes, using movem for all memory transfer is a muust, really 01.39.12 # i better go to sleep too 01.39.25 # i need to write report, code a module and apply for jobs 01.39.25 # haha 01.39.26 # XShocK: oooh, psychology...that was a long time ago... 01.39.39 # i would rather sleep 01.40.03 # :) 01.40.19 # thank god i don't have to get up very early tomorrow 01.40.37 # * LinusN will get up in about 3 hours 01.40.44 # sounds absolutely delightful 01.40.54 # i can't wait... 01.40.55 # were i you, i'd get in bed as soon as possible 01.41.06 # aye, aye, captain! 01.41.09 # with only three hours sleep, i am near suicidal when i have to get up 01.41.12 Quit elinenbe (Client Quit) 01.41.14 # * LinusN obeys and goes to sleep 01.41.19 # nite folks! 01.41.22 # night 01.41.24 # night 01.41.27 Part LinusN 01.41.28 # night 01.45.26 # one more question. how long can the data stay without refreshing? 01.46.17 # a very short time 01.46.22 # why worry about that? 01.47.48 # i want it to work on the fastest mode possible. and i know that it will stay in ram no more that 10-20ms. 01.48.18 # well, i have no idea about specific numbers 01.48.26 # but the memory caps discharge pretty fast, i think 01.49.29 # ok then. anyway it will probably will be dischanrged in that time. 01.50.50 # ok. will not bother anyone anymore. :) 01.50.50 # probably 01.50.56 # haha 01.51.11 # i want to be bothered, writing reports are boring 01.51.34 # hehe.. same in here. 02.11.26 # well 02.11.28 # tired, bed next 02.11.34 # night, all 02.11.41 Quit preglow ("leaving") 02.11.42 # night 02.11.59 # night 02.12.42 Quit Aison ("( www.nnscript.de :: NoNameScript 3.72 :: www.XLhost.de )") 02.25.44 Join Aison [0] (~hans@zux166-181.adsl.green.ch) 03.19.08 Quit Sucka ("a bird in the bush is worth two in your house") 03.19.37 Join Byron [0] (byron@63.77.203.136) 03.19.40 # hello 03.20.17 # I need some help, I put rockbox on my ondio and when I record the audio level won't go any lower than 21db 03.28.39 Quit Aison ("( www.nnscript.de :: NoNameScript 3.72 :: www.XLhost.de )") 03.30.11 *** Saving seen data "./dancer.seen" 03.56.53 Quit DMJC ("Leaving") 03.56.54 Quit Byron (Read error: 104 (Connection reset by peer)) 03.57.51 # does ondio already has record function? 03.58.01 # i mean rockbox 04.06.03 Join QT_ [0] (as@area51.users.madwifi) 04.08.54 Join Rocker [0] (~youthink@67.71.34.203) 04.10.07 Part Rocker 04.19.12 Quit QT (Read error: 110 (Connection timed out)) 04.48.56 # night all 04.49.09 Quit XShocK (" Want to be different? HydraIRC -> http://www.hydrairc.com <-") 05.00.20 Quit edx (Read error: 110 (Connection timed out)) 05.26.45 Quit Stryke` ("Friends don't let friends listen to Anti-Flag") 05.30.15 *** Saving seen data "./dancer.seen" 05.33.39 Join Byron [0] (byron@63.77.203.136) 05.33.44 # oops, I fell off 05.34.02 # anyone know why the ondio won't let me record any lower than 21db 05.35.50 # the record audio is really high and I can't turn it down 05.54.24 Quit asdsd (Read error: 104 (Connection reset by peer)) 05.54.25 Quit Byron (Read error: 131 (Connection reset by peer)) 05.58.53 Join pizza_ [0] (~pizza@rrcs-24-73-230-86.se.biz.rr.com) 05.59.29 # got a quick question. 05.59.38 # Are there any known issues with the car adapter mode? 06.00.29 # my JBR isn't pausing when power is disconnected. 06.09.19 Quit jakepdev (Read error: 60 (Operation timed out)) 06.19.20 Join edx [0] (edx@pD9EAAE58.dip.t-dialin.net) 06.24.26 Join cYmen_ [0] (~cymen@nat-ph3-wh.rz.uni-karlsruhe.de) 06.25.48 Quit cYmen (Read error: 104 (Connection reset by peer)) 06.31.38 Join bobdbob [0] (~bobdbob@ics151-142.icsincorporated.com) 06.37.03 Quit pizza_ ("[BX] "I did not have sexual relations with that client, BitchX."") 07.25.08 Join LinusN [0] (~linus@labb.contactor.se) 07.30.16 *** Saving seen data "./dancer.seen" 07.42.26 Quit GCarrier (Read error: 60 (Operation timed out)) 07.51.09 Join matsl [0] (~matsl@1-1-4-2a.mal.sth.bostream.se) 07.52.31 Quit matsl (Remote closed the connection) 07.59.17 Join Byron [0] (byron@63.77.203.136) 08.05.20 # I fell off again 08.05.30 # anyone answered my question while I was gone? 08.05.49 # eh? 08.06.07 # recording level? 08.06.27 # yeah 08.06.30 # we log all irc activity 08.06.37 # when I record the lowest it'll go is 21 db 08.06.43 # excellent 08.07.05 # check the IRC link on the rockbox site 08.07.14 # anyway, nobody answered it 08.07.18 # oops 08.07.19 # so i'll answer now 08.07.21 # can you? 08.07.24 # YaY! 08.07.34 # no, the 21dB limit is in the hardware 08.07.53 # nothing we can do about it 08.07.55 # ohh man, that sucks, all of my recordings are too hot 08.08.14 # well, glad to know that the problem has been acknowledged 08.08.35 # you're not the only one with that problem 08.08.59 # is there a way to tell rockbox not to change that aspect of the archos... if it works fine in the original firmware that is. 08.09.20 # i repeat: the 21dB limit is in the hardware 08.10.03 # bummer, well thanks for the help and I hope someone comes up with some sort of audio compression or something to bypass the hardware limitation, but I doubt that can happen anyway. 08.10.22 # thanks Linus, you've been a big help 08.10.32 # you're welcome 08.10.41 # I can't find anything refering to this problem on google so I am glad I found someone who knows what is up 08.11.11 # hang on 08.12.19 # you record with the builtin mic, right? 08.12.28 # yeah 08.12.41 # http://www.rockbox.org/twiki/bin/view/Main/GeneralFAQ#Q65_What_kind_of_mic_can_I_conne 08.14.03 # thanks 08.15.48 # is there a firmware upgrade for PMA400 08.16.54 # what's that? 08.17.04 # the new archos that is a pda 08.17.14 Join Zagor [0] (foobar@h14n2fls31o265.telia.com) 08.17.29 # no, we have no plans for the pma400...yet 08.17.36 # morning Zagor 08.18.40 # hi. anyone got any ideas how to get rid of the twiki registration spam? manual screening is all I can think of :-( 08.19.08 # me too 08.19.45 # we can of course look for links in the user topic 08.19.55 # and alert the admins 08.20.08 # but not everyone adds links either 08.20.18 # it's a start 08.20.42 # Hmm, that would disallow links to someone's homepage.... 08.20.48 # Morning, btw :) 08.20.53 # not disallow 08.21.14 # just alert the admins when the topic is added or changed 08.21.22 # via email 08.21.40 # we check it and approve or delete, manually 08.22.00 # it's not that we're swamped with wiki spam...yet 08.22.07 # how about a rockbox-related question on the form? 08.22.23 # well we do get several bogus registrations per day. it's becoming a burden. 08.22.28 # good idea 08.23.57 # hehe, how about "which FAQ entry is about...blabla?" :-) 08.25.15 # or just "which color is the Rockbox logo?" 08.25.34 # anyway, are the wiki spam entries purely automated? 08.25.50 # no, they're manual. i tried changing the form and they still come. 08.27.00 # ok, so the questions have to be somewhat hard 08.27.06 # yes 08.28.41 # "name three of the Rockbox project staff members" :-) 08.29.10 # spelling would be a problem 08.29.37 # or a dropdown list of all wiki users 08.29.47 # multi-choice 08.30.50 # which of these 5 platforms is *not* supported by rockbox? 08.31.29 # reminds me of the rockbox-trivia irc channel :-) 08.31.37 # :) 08.41.48 # is there a software mod that you guys could do to the rockbox fm 20 so that the line-in would accept a microphone? 08.42.16 # I've got an amplifier and a mic and the archos in a fanny pack right now, but it'd be nice if I could get rid of the amp 08.42.41 # the internal mic picks up all of that nasty hard drive noise, makes it useless 08.42.47 Join ashridah [0] (ashridah@220-253-123-13.VIC.netspace.net.au) 08.43.14 # Byron: can't be done. you need the amplifier. 08.43.40 # D'oh 08.44.02 # any way to make the hard drive stop spinning up during recordings, maybe use some sort of memory buffer? 08.44.25 # rockbox doesn't spin up until the memory is full 08.44.31 # we already use all the memory we have, but when it's full we need to spin up the disk to store it 08.45.19 # yea, bummer 08.45.33 # it spins up every 3 mins or so, sometimes more frequantly 08.46.01 # yup, that sounds about right 08.46.13 # Byron: if you set the recording settings to record to the current directory, it won't spin up when you start the recording 08.47.25 # or you could buy an Ondio, which is a flash player/recorder, also supported by rockbox 08.48.45 # right, but the audio won't go any lower than 21db 08.48.54 # so I'm gonna get messy audio quality one way or the other 08.49.07 # the best way to record so far, is to have an external mic 08.49.19 # yes 08.49.20 # that will always be the case 08.51.19 # "No need to put lcd_write() in the IRAM since it has to be slow." 08.51.20 # ;-) 08.51.25 # (from OpenNeo) 08.52.24 # i wonder why they removed the TOC support 08.52.52 # they do odd things 08.56.46 # the commen in the new code says "No TOC exists" 08.56.48 # comment 08.56.55 # even weirder 08.57.13 # indeed 08.57.25 # it makes me suspect they don't know what they 08.57.27 # 're doing 08.59.15 # "No need to support HD bigger than 2 TB" 08.59.17 # hehe 09.04.33 # maybe they're trying to save memory? 09.04.52 # yes, possibly 09.05.09 # 400 bytes per id3 entry...oooooh :-) 09.05.11 # their heap is growing so they need to cut off code ;-) 09.05.16 # 100 bytes 09.05.53 # 64KB for heap is a quite a lot when you only have 256 09.06.03 # yup 09.06.15 # why did they add heap anyway? 09.06.16 # they're stuck in heap hell 09.06.21 # Zagor: m m m malloc 09.06.32 # yeah, but what are they using it for? 09.06.43 # nothing useful 09.06.45 # same thing as other heap junkies 09.06.55 # various bits and pieces? 09.06.56 # I saw that theres apparently some primitive mpeg playback code on the CVS, does this mean we're close to getting mp3 playback? :) 09.06.59 Quit ashridah (Read error: 60 (Operation timed out)) 09.07.02 # Zagor: yeps, just random stuff 09.07.22 # DJ_Dooms_Day: the mpeg playback you see is the archos playback code 09.07.27 # how very foolish 09.07.30 # -_- 09.07.34 # lies! 09.07.48 # Zagor: they do a lot of things we wouldn't... 09.07.59 # lies? 09.08.29 # Im in denial, leave me be 09.10.18 # * Bagder pats DJ_Dooms_Day on his head. "Ok my son, now go and play with the other kids" ;*) 09.17.57 Join Lynx_ [0] (HydraIRC@134.95.189.59) 09.21.08 Join Schnueff [0] (~mah@134.96.247.232) 09.30.19 *** Saving seen data "./dancer.seen" 09.30.41 Join bobTHC [0] (~foo@l07v-6-110.d1.club-internet.fr) 09.30.41 Quit Bagder (Read error: 131 (Connection reset by peer)) 09.31.13 # hi all! 09.37.48 Join Bagder [0] (~daniel@1-1-5-26a.hud.sth.bostream.se) 09.39.57 Quit gromit (Nick collision from services.) 09.40.15 Join gromit` [0] (~gromit@ras75-5-82-234-244-69.fbx.proxad.net) 09.41.18 # morning Bagder 09.41.26 # hey 09.44.24 Join kurzhaarrocker [0] (~Phil@p3E9C2EAB.dip0.t-ipconnect.de) 09.45.15 # LinusN you're evil. Instead of commiting the triggered recording patch you made a cvs conflict. :) 09.46.17 # muhahahahaaaaa 09.46.19 # * Bagder verifies that LinusN is evil 09.46.35 # kurzhaarrocker: sorry about that 09.46.51 # no problem. Rockbox lives and thats good. 09.55.42 # It was extremly easy to fix anyway - just an additional include 09.56.31 # * LinusN updates the patch tracker 09.58.25 # �h? What do you mean with update? It certainly won't mean you update the patch of triggered recording? 09.58.42 # i just did 09.58.52 # ups. Thanks! :) 10.04.03 # * LinusN is installing the peak meter patch on his recorder 10.04.20 # Hooray! :D 10.04.26 # * kurzhaarrocker jumps up and down in joy 10.06.48 # i like the new trigger bar 10.08.27 # * kurzhaarrocker searches something to wag with 10.08.48 # is the trigger enabled by default? 10.09.16 # I don't think so. It shouldn't be. Triggered recording is something sepcial 10.09.45 # seems to be 10.09.49 # But in my configs it is stored that I it records triggered -> I don't know the default by heart any more. 10.10.50 # seems like the cursor for the gain isn't drawn in the right place 10.11.47 # it seems to be correctly drawn when the cursor is an inverted bar 10.11.58 # but not when it's an arrow 10.12.40 # Hm. I should have noticed that. My fault. Unfortunately my batteries are in an external charger right now -> can't verify. 10.22.35 # did you ditch the idea with the blinking led while waiting to trigger? 10.23.28 # No. It should blink. 10.24.01 # it doesn't for me 10.28.29 Join ashridah [0] (ashridah@220-253-121-18.VIC.netspace.net.au) 10.29.37 Quit Ka (Read error: 110 (Connection timed out)) 10.32.41 # The code that blinks the led in TRIG_STEADY state is in recording.c, line 388. I'll verify what happened as soon as my batteries are charged. 10.34.01 # Hm. When the thing is prerecording - is (mpeg_stat & MPEG_STATUS_RECORD) == true? 10.35.06 # no 10.35.49 # then MPEG_STATUS_PRERECORD is set 10.36.04 # That's what I thought. 10.38.06 # maybe i misunderstood 10.38.27 # it only blinks during the trig duration period 10.38.38 # That is the intension 10.38.48 # and not just when the trigger is armed, which i thought it would do 10.39.13 # my mistake 10.39.25 Join Patr3ck [0] (~patr3ck@pD9ECF52C.dip.t-dialin.net) 10.39.44 # It was a useful feature to be able to distinguish wether the trigger threshold has been reached from the distance. 10.40.40 # It is only useful for long trigger times though. 10.41.56 # is the wiki manual up to date? 10.42.41 # no 10.42.45 Join bzerk86 [0] (~Brian@66.cust16.sa.dsl.ozemail.com.au) 10.42.47 # <- meeting :( 10.43.33 Nick QT_ is now known as QT (as@area51.users.madwifi) 10.56.54 # kurzhaarrocker: i wish you could have make it compile in the simulator... 11.00.30 Join Quelsaruk [0] (~kvirc@85.48.43.61) 11.00.33 # morning 11.00.37 # moo 11.00.42 # :) 11.05.19 Join DJ_Dooms_Day|AF [0] (~scottr@203.220.52.89) 11.10.02 Part kurzhaarrocker 11.10.51 Quit bzerk86 ("Leaving") 11.13.14 # * LinusN just committed the triggered recording patch 11.24.01 Quit DJ_Dooms_Day (Read error: 110 (Connection timed out)) 11.27.11 Nick kergoth is now known as kergoth`zzz (~kergoth@covenant.kergoth.com) 11.30.20 *** Saving seen data "./dancer.seen" 11.48.55 Join DMJC [0] (~James@220-245-171-89.tpgi.com.au) 11.48.55 Quit Byron (Read error: 104 (Connection reset by peer)) 11.56.04 Part LinusN 11.56.22 Join Lost-ash [0] (ashridah@220-253-123-107.VIC.netspace.net.au) 11.57.49 Quit ashridah (Nick collision from services.) 11.58.58 Nick Lost-ash is now known as ashridah (ashridah@220-253-123-107.VIC.netspace.net.au) 12.01.00 Join Ka [0] (~tkirk@pcp0010733332pcs.howard01.md.comcast.net) 12.01.18 Nick kergoth`zzz is now known as kergoth (~kergoth@covenant.kergoth.com) 12.06.15 # Argh, Linus is gone! :-/ 12.12.44 Join Lost-ash [0] (ashridah@220.253.123.107) 12.12.45 Quit ashridah (Connection reset by peer) 12.13.46 # ping Lost-ash 12.23.43 Nick Lost-ash is now known as ashridah (ashridah@220.253.123.107) 12.26.17 Join LinusN [0] (~linus@labb.contactor.se) 12.26.54 # network maintenance... 12.30.17 Join Aison [0] (~hans@zux166-181.adsl.green.ch) 12.35.50 Join DJ_Dooms_Day [0] (~scottr@dialup-36.79.221.203.acc15-dryb-mel.comindico.com.au) 12.36.26 Quit Quelsaruk ("KVIrc 3.2.0 'Marmalade'") 12.39.44 Join preglow [0] (thomj@s183a.studby.ntnu.no) 12.39.48 Join quelsaruk [0] (~kvirc@80.103.131.254) 12.43.49 # LinusN: The triggered recording patch broke the ondio fm build... 12.44.17 # ... and your fix doesn't work (it obviously can't), but instead breaks the advanced sound settings for ondio sp... 12.44.21 Quit DJ_Dooms_Day|AF (Read error: 60 (Operation timed out)) 12.44.31 # that's really funny, because it works when i build locally 12.44.49 # The problem is not related to the mas types, but to the button handling 12.44.56 # i know 12.45.07 # my "oops" commit wasn't related to the build error 12.45.27 # It wasn't? 12.46.02 # no, it was because i accidentally added advanced peak meter recording settings to the SP 12.46.05 # The build obviously cannot work, because the button assignment is hardcoded, and the Ondio doesn't have PLAY nor F2 12.46.55 # do you have any good ideas what buttons we could use? 12.49.04 # I did not yet try the triggered recording, so I don't know the details. But from looking at the code, I wonder why it defines its own menu function instead of using the existing one 12.49.36 # The USB handling is just plain wrong 12.50.01 # ah, yes 12.51.26 Quit ashridah (Read error: 110 (Connection timed out)) 12.52.25 Join hibou [0] (~a4810127@labb.contactor.se) 12.55.00 # Btw, the 'Oops' commit seems unnecessary to me. The code section in question is protected by #ifdef HAVE_RECORDING anyway, and the MAS3539 cannot record... 12.55.08 # true 12.58.26 # Hmm, I need to have a look at the triggered recording myself. Can only do that in the evening, and it's too bad I don't always have access to an Ondio FM 12.59.04 # hmmm, ondio has no play key... 12.59.33 # i guess the "cancel" function has to be disabled on the ondio then 12.59.44 # If at all possible, I would prefer it to use the standard rockbox menu system. That would ensure consistent operation with the other menus, and also most likely save some code size 12.59.50 # (pressing OFF to cancel the settings) 12.59.58 # amiconn: agreed 13.08.01 Join ceebmoj [0] (~5189b144@labb.contactor.se) 13.08.11 # hi 13.10.04 Quit Ka (Read error: 110 (Connection timed out)) 13.10.34 # I have been reading the Audio API stuff has any progres been made on it? 13.10.42 # not really 13.11.51 # i'm working on restructuring the audio code to prepare for the new code 13.12.15 # who is working on it? 13.12.21 Join Ka [0] (~tkirk@pcp0010733332pcs.howard01.md.comcast.net) 13.12.28 # are thay about to talk to? 13.14.10 # i am working on it 13.14.29 # restructuring the code, that is 13.16.20 #