--- Log for 27.01.112 Server: kornbluth.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 1 day and 7 hours ago 00.06.30 Quit domonoky (Read error: Connection reset by peer) 00.09.45 Quit wodz (Quit: Leaving) 00.15.20 Join Farthen [0] (~Farthen@2a01:4f8:101:2a4:0:bc28:b2e1:9) 00.19.49 Join kadoban [0] (~kadoban@ip98-165-177-158.ph.ph.cox.net) 00.20.00 Quit ender| (Ping timeout: 276 seconds) 00.21.07 Quit lebellium (Quit: ChatZilla 0.9.88 [Firefox 10.0/20120118081945]) 00.23.22 Join ender| [0] (~ender1@2a01:260:4094:1:42:42:42:42) 00.25.59 Nick mc2739_ is now known as mc2739 (~mc2739@rockbox/developer/mc2739) 00.28.48 Quit Strife89 (Ping timeout: 260 seconds) 00.35.32 Quit liar (Ping timeout: 245 seconds) 00.36.09 Join anewuser [0] (~anewuser@186.88.33.132) 00.36.09 Quit anewuser (Changing host) 00.36.09 Join anewuser [0] (~anewuser@unaffiliated/anewuser) 00.38.14 Quit bertrik (Ping timeout: 240 seconds) 00.45.35 Join curtism [0] (~curtis@bas11-montreal02-1128531121.dsl.bell.ca) 00.50.17 Quit AlexP (Read error: Connection reset by peer) 00.50.30 Quit pamaury (Remote host closed the connection) 00.55.06 *** Saving seen data "./dancer.seen" 01.05.15 Quit kadoban (Read error: Operation timed out) 01.24.44 Quit Thra11 (Ping timeout: 255 seconds) 01.47.18 Nick perrikwp_ is now known as perrikwp (~quassel@cpe-024-163-024-033.triad.res.rr.com) 01.53.12 Join perrikwp_ [0] (~quassel@cpe-024-163-024-033.triad.res.rr.com) 01.55.06 # <[Saint_]> JdGordon: Pongy-McPongington... 01.55.19 # way too slow :) 01.55.28 # i was pining for your ping yesterday 01.55.56 Quit perrikwp (Ping timeout: 245 seconds) 01.55.59 Nick perrikwp_ is now known as perrikwp (~quassel@cpe-024-163-024-033.triad.res.rr.com) 01.56.46 # <[Saint_]> Yeah, but, I still replied! :) 02.10.49 Join perrikwp_ [0] (~quassel@cpe-024-163-024-033.triad.res.rr.com) 02.13.07 Quit MethoS- (Read error: No route to host) 02.13.48 Quit perrikwp (Ping timeout: 260 seconds) 02.14.32 Join MethoS- [0] (~clemens@134.102.106.250) 02.15.33 Join dreamlayers [0] (~bgjenero@rockbox/developer/dreamlayers) 02.35.20 # Commit f4954c4 in rockbox by 03Boris Gjenero: Fix FS#12559: sigaltstack threads fortify failure 02.37.28 # f4954c4 build result: All green 02.51.20 Join anewuser_ [0] (~anewuser@186.88.33.132) 02.54.42 Quit anewuser (Ping timeout: 245 seconds) 02.55.08 *** Saving seen data "./dancer.seen" 03.02.14 Quit MethoS- (Quit: Konversation terminated!) 03.42.14 Nick perrikwp_ is now known as perrikwp (~quassel@cpe-024-163-024-033.triad.res.rr.com) 04.01.26 Join IndexPhinger [0] (~IndexPhin@S01060014a53245ef.ed.shawcable.net) 04.01.36 # Hello 04.04.12 Quit dreamlayers (Quit: Leaving.) 04.06.06 # I need some help with making a theme for my iPod 30Gb, I like the Terminal theme but I'd like to move around some of the now playing menu settings 04.07.13 # Hmm...i'll read some more and wait for my iPod replacement battery :( 04.08.32 Part IndexPhinger 04.20.27 Quit anewuser_ (Read error: Connection reset by peer) 04.23.39 Quit TheSeven (Read error: Operation timed out) 04.24.39 Join TheSeven [0] (~TheSeven@rockbox/developer/TheSeven) 04.36.48 Join [Saint] [0] (~Saint]@unaffiliated/saint/x-8516940) 04.37.28 Join T44 [0] (~Topy44@f049225154.adsl.alicedsl.de) 04.40.55 Quit Topy (Ping timeout: 240 seconds) 04.44.16 Quit nosa-j (Excess Flood) 04.46.51 Join nosa-j [0] (~m00k@adsl-74-235-42-94.clt.bellsouth.net) 04.48.34 Quit pixelma (Disconnected by services) 04.48.35 Quit amiconn (Disconnected by services) 04.48.35 Join amiconn_ [0] (quassel@rockbox/developer/amiconn) 04.48.36 Join pixelma_ [0] (quassel@rockbox/staff/pixelma) 04.48.39 Nick pixelma_ is now known as pixelma (quassel@rockbox/staff/pixelma) 04.48.58 Nick amiconn_ is now known as amiconn (quassel@rockbox/developer/amiconn) 04.55.10 *** Saving seen data "./dancer.seen" 04.58.54 Join [Saint__] [0] (~Saint]@unaffiliated/saint/x-8516940) 05.01.14 Quit [Saint] (Ping timeout: 260 seconds) 05.28.12 Quit perrikwp (Read error: Connection reset by peer) 05.29.14 Join perrikwp [0] (~quassel@cpe-024-163-024-033.triad.res.rr.com) 05.54.38 Join factor [0] (~factor@74.197.205.204) 05.55.00 Join dreamlayers [0] (~bgjenero@rockbox/developer/dreamlayers) 05.56.12 Join Rob2222 [0] (~Miranda@p5B02473A.dip.t-dialin.net) 06.00.09 Quit Rob2223 (Ping timeout: 260 seconds) 06.04.02 Join kadoban [0] (~kadoban@ip98-165-177-158.ph.ph.cox.net) 06.20.04 Quit factor (Ping timeout: 252 seconds) 06.54.48 Join factor [0] (~factor@74.197.205.204) 06.55.11 *** Saving seen data "./dancer.seen" 06.55.38 # I washed my sana and i died :( 06.55.46 # Sansa fuze^ 06.56.00 # did not even last one time. 06.56.06 # not very NEMA compliant 07.24.35 # Did you let it dry out long enough before testing? 07.26.08 # factor: There's a lot of info online on saving wet electronics 07.27.47 Quit dreamlayers (Quit: Leaving.) 07.33.15 # I thought I did 07.33.31 # I left it for a few days . but nothing no lights on the wheel 07.33.37 # I took it apart. 07.33.49 # was wondering if I could get the pinout for the display 07.34.03 # I program pic chips and would be nice to use it for experiments 07.34.09 # its dead . 07.34.31 # 60 bucks down the drian 07.34.39 # literally 07.39.41 # sucks oh well 07.40.13 # may think about getting another , but will be later. Will have to use my tablet as a music device 07.43.07 Quit [Saint__] (Remote host closed the connection) 08.28.10 # dreamlayers: we should probably report the longjmp bug upstream 08.32.18 Join Zagor [242] (~bjst@rockbox/developer/Zagor) 08.48.48 Join am_devcorp [0] (~am_devcor@94.158.169.5) 08.50.14 Join nosa [0] (~m00k@adsl-74-235-42-94.clt.bellsouth.net) 08.50.33 Nick am_devcorp is now known as amdc (~am_devcor@94.158.169.5) 08.51.07 # REGISTER amdevcorp kchan41@gmail.com 08.51.54 Quit nosa-j (Ping timeout: 252 seconds) 08.51.55 Nick nosa is now known as nosa-j (~m00k@adsl-74-235-42-94.clt.bellsouth.net) 08.53.10 Quit amdc (Client Quit) 08.53.34 Join wodz [0] (~wodz@89-76-160-35.dynamic.chello.pl) 08.55.13 *** Saving seen data "./dancer.seen" 08.55.51 # yay - battery_bench on my HD300 ended after 39:24:21 ! This is with new 1700mAh replacement battery 08.56.52 Join bertrik [0] (~bertrik@ip117-49-211-87.adsl2.static.versatel.nl) 08.56.52 Quit bertrik (Changing host) 08.56.52 Join bertrik [0] (~bertrik@rockbox/developer/bertrik) 09.04.08 Join einhirn [0] (~Miranda@bsod.rz.tu-clausthal.de) 09.08.29 Quit kadoban (Ping timeout: 245 seconds) 09.12.45 # wodz, Awesome. 09.17.24 Quit bertrik (Quit: And That, My Liege, Is How We Know the Earth to Be Banana Shaped) 09.27.59 # Commit fab7264 in rockbox by 03Thomas Martitz: Force settings touchscreen mode in menus. 09.28.00 # Commit b8439f2 in rockbox by 03Thomas Martitz: Add touchscreen_get_mode() to plugin and lua. 09.28.01 # Commit c406f94 in rockbox by 03Thomas Martitz: Lua: Add pluginlib_actions wrapper for lua scripts. 09.28.03 # Commit aba5c47 in rockbox by 03Thomas Martitz: pluginlib_touchscreen: Rework API to offer wait-for-button APIs. 09.28.04 # Commit 93a4b32 in rockbox by 03Thomas Martitz: test_codec/test_fps: Use pluginlib_touchscreen API to make them fit for touchscreen including point mode. 09.28.05 # Commit 7013d0c in rockbox by 03Thomas Martitz: application: Enable chipper and fft plugins. 09.28.06 DBUG Enqueued KICK CIA-81 09.28.06 # Commit 7c623d5 in rockbox by 03Thomas Martitz: Use PLA in boomshine.lua instead of the awkward kbd_input context. This enables it on RaaA. 09.28.08 # Commit 049f3c7 in rockbox by 03Thomas Martitz: test_touchscreen.rock: Add keymap for sdl and android. 09.28.09 # Commit 6eeca70 in rockbox by 03Thomas Martitz: PLA: Add map for android. Directional keys not available in point mode due to 09.30.46 # 93a4b32 build result: All green 09.32.41 # Commit c6d69ae in rockbox by 03Thomas Martitz: Bump plugin api and abi version needed for b8439f2. Sort too. 09.35.03 # c6d69ae build result: All green 09.38.56 # <[Saint_]> chipper? 09.39.17 # <[Saint_]> Oh! Chopper...nevermind. 09.40.36 # yep, typo 09.42.52 # <[Saint_]> I wasn't taking the piss, for the record...I was seriously curious what the "chipper.rock" plugin was :) 09.43.33 # I realized :) 09.47.15 # good lord. A commit frenzy. 09.47.20 # we need some sort of badge system for that 09.50.16 # each commit is relatively small though 09.50.27 # like that more as a single commit? 09.52.34 # I wasn't complaining, I am impressed ;) 09.52.51 # your dedication to improving rockbox is inspiring 09.52.55 # took me an hour to split the single commit I had locally up :) 09.53.34 # I think it's better as lot of little commits, since they're all separate features. 09.55.00 # <[Saint_]> Wasn't there a conversation in the very recent past about how it might be better to not to commit sprees like that? 09.55.22 # <[Saint_]> Since not every commit is built (or somesuch?) 09.55.52 # <[Saint_]> s/to not to/to not do/ 09.57.32 # [Saint_]: whats the problem with that? I prefer to have well separated commits and what is really interesting is the total outcome of the bunch 09.57.58 Join mortalis [0] (~mortalis@77.108.98.177) 10.00.09 # <[Saint_]> wodz: I'm not sure, entirely...I just recall a conversation on the topic. 10.02.57 Join liar [0] (~liar@clnet-p09-185.ikbnet.co.at) 10.03.33 # wodz: I think what [Saint_] is saying is they're *not* well seperated (at least, not by time), so in theory one of the commits might break the build, but we wouldn't be sure which one, since so many all got commited at once. 10.04.02 # the build system could make incremental builds 10.04.18 # it could, but it doesn't currently 10.04.24 # not really a problem though 10.04.26 # more work for Zagor ;) 10.04.32 # usually committers check and fix problems later 10.04.35 # incremental builds? 10.04.48 # build each revision 10.04.52 # Zagor: as in, definitely build each new commit 10.04.57 # not just the latest one 10.05.08 # s/later/immediately 10.05.22 # ah, I thought you meant some magic wizardry to only build modified code etc. 10.05.23 Nick [Saint_] is now known as [Saint] (~Saint]@unaffiliated/saint/x-8516940) 10.05.36 # no -that would be magic indeed 10.06.22 # I don't think we should change anything until it we identify an actual problem. 10.06.48 # no indeed 10.07.52 # as long as the last commit is always built, we don't risk having undetected errors. pinpointing the exact commit that introduced it is likely not very important. 10.08.49 # probably true 10.10.22 # GodEater_: that magic is called "make" :) 10.10.43 # kugel: yes, but doesn't our build system do a make clean first deliberately? 10.10.49 # yes 10.11.14 # building each commit would be interesting for the binsize, not so much for warnings/errors 10.11.48 # but not important, one can always bisect if interested 10.11.55 # locally 10.14.59 # especially since bisecting with git is dead easy 10.20.04 # relying on make to do the right thing would indeed be nice 10.20.15 # s/make/our Makefiles/ 10.24.45 # the uncertainty is not so fun though 10.25.01 # but it would make blazing fast build runs 10.27.32 # even for developers =) 10.28.13 Join oiaohm [0] (~oiaohm@unaffiliated/oiaohm) 10.29.30 # I know this might be a bit of a warped question. After seeing this http://seeedstudio.com/wiki/DSO_Quad . I started wondering if rockbox has ever dreamed about doing perfectly matched hardware for it. 10.30.07 # <[Saint]> come again? 10.35.21 Quit oiaohm (Ping timeout: 252 seconds) 10.35.29 Join oiaohm [0] (~oiaohm@unaffiliated/oiaohm) 10.35.57 # <[Saint]> 72MHz is a bit light in the CPU department... 10.36.18 # [Saint]: the DSO Quad is fully open spec hardware. I was wondering if anyone has dreamed of doing a design matched to rockbox requirements. 10.36.35 # I know the dso quad is too low. 10.36.46 # <[Saint]> I take it, oiaohm, that you're wondering if Rockbox a: runs on, or b: might possibly run on, this device? 10.37.10 # <[Saint]> Oh...right. I get you now. 10.37.49 # <[Saint]> There's been various attempts at building a dedicated Rockbox device. 10.38.27 # Is there a list of them? 10.38.56 # <[Saint]> There's probably something on the wiki about them. 10.39.25 # Its like the allwinner A10 and other quite powerful arm chips are getting out there quite cheap. 10.39.39 # Ie allwinner is 1.5 ghz 10.39.47 # and under 5 dollars. 10.39.52 # <[Saint]> It ends up being terribly expensive...its fun as an educational project I'd guess, but nbot terribly practical. 10.40.14 # <[Saint]> s/nbot/not/ 10.41.23 # <[Saint]> Lyre...that's what it was called, I remember now... 10.41.47 # <[Saint]> oiaohm: http://www.rockbox.org/wiki/LyreProject 10.42.11 # [Saint]: we are getting a lot of base tech. Like the raspberry pi and http://rhombus-tech.net/ 10.42.31 # So there has to become a point soon were it will be afforable. 10.43.02 # If you build hundreds of thousands of the things, yes 10.43.15 Quit tchan (Read error: Connection reset by peer) 10.43.53 # Thing is knowing what rockbox required to perform decently. 10.43.58 # So you can spot the techs worth following. 10.43.58 # <[Saint]> Forr those that run either full linux distros, or a linux-esque OS, we have an SDL port. 10.44.04 Join tchan [0] (~tchan@lunar-linux/developer/tchan) 10.44.58 # If you want traditional rockbox (as opposed to RaaA) 1.5gHz is *vastly* overpowered 10.45.00 # So rasbery pi ram A version ram limit of 128 megs is going to do rockbox self in. 10.45.17 # huh? 10.45.19 # there is stacks of different techs at the moment. 10.45.28 Join LinusN [0] (~linus@giant.haxx.se) 10.45.47 # rasbbery pi 700 mhz arm 128-256 meg depending on version. 10.46.05 # <[Saint]> which is foolishly overpowered for Rockbox 10.46.22 # Well, not foolishly I'd say, if you like APE 10.46.47 # <[Saint]> that's foolish, though :) 10.47.22 # What's the raspberry pi's audio quality like though? That's not unimportant 10.47.39 Join pamaury [0] (~quassel@vit94-1-82-67-248-70.fbx.proxad.net) 10.47.40 Quit pamaury (Changing host) 10.47.40 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 10.47.46 # gevaerts: cd level or better. 10.48.06 # That's specs, not quality 10.48.17 # The most expensive parts of the idea are the peripherials and housing. SoC is relatively tiny friction of total cost 10.48.22 # It's easy to do 44.1kHz 16 bit audio with lots of noise 10.48.24 # <[Saint]> oiaohm: It might be worth investigating the hardware Rockbox does already run on. 10.48.52 # <[Saint]> It doesn't need to be a Machine-of-Death 10.49.23 # Ah, and proper routing of the PCB is quite tough topic 10.49.35 # The chip at the core of the rasberry pi is arm chip design by broadcom targeting multimedia. 10.50.29 # oiaohm: that chip cannot play audio. you need a dac and an amplifier. 10.50.51 # BCM2835 10.50.52 # oiaohm: have you read about technical aspects of rasberry Pi? From porting point of view this is no-go. It boots though custom RISC graphic core with no public specs 10.51.09 # the only doable option is RaaA on PI 10.52.25 # and HDMI video interface is not what you want for portable device 10.53.48 # the pi does have an analog jack, but I haven't seen what hardware it is connected to 10.53.49 # What *would* be interesting is to port rockbox to some Cortex-M3 based SoC. It should be sufficient and is power efficient and cheap. 10.54.52 # Zagor: the SOC after a basic amp. 10.55.16 # Zagor: PI is almost a 1 chip design. 10.55.18 *** Saving seen data "./dancer.seen" 10.56.22 # That the thing there are a lot of one chip design arm chips out there at the moment. 10.56.37 # preaching to the choir a little there. 10.56.44 # are you saying the bcm2835 contains an internal dac? I can't see that on google. 10.57.04 # Zagor: Yep. 10.57.15 # bom for PI is available so this should be easy to check 10.57.17 # citation needed! 10.59.28 # the pi appears as closed as any other proprietary box. no data sheets, binary drivers etc. 11.01.04 # Zagor: ...and weird boot scheme 11.05.38 # Zagor: https://github.com/raspberrypi/linux/commits/rpi-patches You do have the kernel source to the PI. 11.06.52 # and the graphics acceleration? 11.07.25 # Zagor: Not sure if the mesa side is released yet. 11.09.09 # Of course there is most likely a few firmware blobs 11.09.09 # But its in the range of decent. Zagor 11.09.53 # So IP should be thinking a lot of people behind it are broadcom 11.11.06 # How much is the min you would dare run rockbox on. 11.11.41 # <[Saint]> look at the early Archos targets... 11.12.08 # <[Saint]> Those that started it all. They're not exactly power-houses. 11.13.07 # but they have hw decoding, so are not comparable 11.13.24 # oiaohm: My view on PI is like this - this is interesting how low you can go with price. This VERY well advertised project but it is not so interesting from the hackers point of view. 11.14.52 # we run 256kbit mp3 decoding on 27 MHz coldfire 11.15.22 # or 20MHz ARM7 11.15.55 # so basically *any* current 32-bit processor can run rockbox 11.16.45 # lots of measurements here: http://www.rockbox.org/wiki/CodecPerformanceComparison 11.17.15 # Zagor: so the cordex M3 duel core running at 266 mhz as a side processors in the OMAP 4430 to the Cordex A9 duel core at 1ghz would be more than enough power. 11.17.19 # doesn't the Pi also feature hardware decoding? 11.17.24 # (of video at the very least) 11.17.34 # oiaohm: oh yes, by a huge margin 11.18.17 # So basically it would be wrong to use a OMAP4430 like that only running the Cordex A9 to fire up the Codex M3 duel core. 11.18.47 # single core Cortex-M3 should be enough 11.18.51 # "wrong" is subjective. I believe the objective term is "overkill". :-) 11.19.32 # <[Saint]> hahaha 11.23.04 # GodEater_: yes it does 11.23.42 # I don't know if the same hardware can also be used to decode audio though 11.24.15 # even if it could, it is far from certain it would draw less power 11.25.46 # the problem I see with the PI is that the hardware is not documented, and that they will probably only implement what they need, but the price is definitely nice 11.26.03 # pamaury: Its new hardware. 11.26.25 # pamaury: or at least newish 11.26.46 # pamaury: basically the are doing the PI and the documentation and driver and everything else for the core chip at the same time. 11.28.00 # I hope so, but even then the hardware will not be documented which is a shame 11.30.16 # pamaury: the circuit board design will be released after launch http://www.raspberrypi.org/forum/general-discussion/links-to-pcb-cad-design-files 11.30.19 # oiaohm: don't expect too much - Eben explicitly stated that they didn't get the permission from Broadcom to publish SoC documentation. 11.30.48 # and many parts are as binary blobs 11.30.53 # oiaohm: the SoC is the interesting part, we will never get the datasheet and I'm not even talking about the graphic subsystem 11.31.19 # We will at least have enough to drive it. 11.31.29 # pamaury: you have to talk about graphic subsystem as it is used to bootstrap on this platform :-) 11.31.54 # oiaohm: we don't - we can run linux kernel THEY provide nothing more 11.32.55 # this is pretty damn closed hardware with a bit of good marketing 11.33.01 # really that's stupid, broadcom seems to make interesting SoC but they are so closed... 11.33.25 # opengl ES drivers will come with it. 11.33.52 # Its not a paper weight completely. 11.35.18 # oiaohm: If you port rb to PI (not as RaaA) within a 5 years I owe you a beer. 11.35.52 # if you include the binary blobs that might be possible no ? That's quite unsatisfactory but hey... 11.36.39 # pamaury: like the major blob the gpu one is in the first stage boot loader. So as long as what I run is after that I don't need to get that one. 11.36.47 # pamaury: Gonna pickup the contest :-; 11.36.51 # ? 11.37.17 # wodz: as long as I don't have to nuke the first stage boot loader I should stand a fair chance. 11.37.39 # I am really sick of hearing PI is open platform. 11.37.40 # Ie if you were mean and said I had to beat the first stage boot loader I would be in trouble. 11.38.05 # wodz: I was more looking at affordable parts that could possible be recycled as is. 11.38.14 # Or close as possible. 11.38.23 # Ie volume makes stuff well cheaper. 11.39.00 # oiaohm: I think even the part after 1st stage bl will not be trivial 11.39.03 # <[Saint]> Is someone able to do me a favour and build me a RaaA .apk at 240x320 please? It would be much appreciated, my build environment has fallen over and I'd like to do some testing on device. 11.39.07 # <[Saint]> Thanks in advance. 11.40.12 # wodz: I did not say it would be trivial. 11.40.41 # wodz: just I would stand a chance as long as I don't have to beat up the first stage bootloader. 11.41.16 # Because I know that boot loader will basically kick my ass. 11.41.56 Join [Saint_] [0] (~Saint]@unaffiliated/saint/x-8516940) 11.42.38 # oiaohm: I really like your enthusiasm but believe me this will be tedious task with this level of documentation they provide 11.43.49 # Yep the horid use source and bend. 11.44.58 Ctcp Ignored 1 channel CTCP requests in 0 seconds at the last flood 11.44.58 # * gevaerts recommends waiting until the devices are available, and then doing some tests on the audio to assess quality. If it's noisy, don't even bother 11.45.47 Join dfkt [0] (dfkt@unaffiliated/dfkt) 11.47.07 # gevaerts: exactly it going to come down to quality of the final device if it worth the effort. 11.47.15 # gevaerts: there are quite a few at the moment. 11.47.23 # That are worth watching. 11.47.43 # But most of the items I have been looking at have be over kill to rockbox requirement. 11.53.08 Quit Zambezi (Read error: Connection reset by peer) 11.53.27 Join Zambezi [0] (Zulu@bnc.fran.dotbnc.se) 12.01.36 # wodz: I'm not sure I want to pick up the contest, I have enough to do with documented platform already :) 12.03.35 # chicken :P 12.04.11 # don't tempt me...:P 12.04.34 # I might have ported it before iyou receive it ;) 12.06.59 # pamaury: You work for Broadcom? I didn't know :P 12.08.18 # omg, that would probably be so frustrating to work for such a closed company 12.09.56 # I plan to buy one but if someone else can do the dirty work, I'm ok with it 12.15.39 Join anewuser [0] (~anewuser@186.88.33.132) 12.15.39 Quit anewuser (Changing host) 12.15.39 Join anewuser [0] (~anewuser@unaffiliated/anewuser) 12.15.41 # wodz: will you buy one ? 12.15.58 # or are you trying to convince people not to ? :) 12.17.03 Quit [Saint_] (Quit: Quit) 12.24.20 # pamaury: Its not my business to convince people not to buy - I just only want to calm down the hurray-enthusiasm which arose around this platform. Maybe I'll buy one - dunno 12.24.39 Join benedikt93 [0] (~benedikt9@unaffiliated/benedikt93) 12.25.00 # I guess lots of people will be happy with it because they don't plan to replace the OS 12.25.16 # and don't want to know how it works 12.30.26 # pamaury: And it runs Linux so is cool (TM) 12.32.17 # well yeah, we saw what happened with android 12.41.02 Join Thra11 [0] (~thrall@31.185.164.69) 12.53.42 Quit factor (Read error: Connection reset by peer) 12.55.21 *** Saving seen data "./dancer.seen" 13.04.35 Join Rower85 [0] (husvagn@78-69-196-71-no178.tbcn.telia.com) 13.10.34 Part oiaohm 13.11.16 Join factor [0] (~factor@74.197.205.204) 13.12.08 Quit benedikt93 (Quit: Bye ;)) 13.12.21 Quit anewuser (Read error: Connection reset by peer) 13.22.45 Nick funman is now known as namnuf (~fun@rockbox/developer/funman) 13.24.31 Join funman [0] (~fun@rockbox/developer/funman) 13.25.02 Quit namnuf (Remote host closed the connection) 13.33.13 Part LinusN 13.33.54 # pictureflow manual tex file is a nightmare 13.35.31 # not speaking about pictureflow.c by itself 13.37.44 Quit perrikwp (Read error: Connection reset by peer) 13.38.54 Join perrikwp [0] (~quassel@cpe-024-163-024-033.triad.res.rr.com) 13.49.59 # wodz: Sorry :( 13.56.40 Quit perrikwp (Read error: Connection reset by peer) 13.59.06 Join perrikwp [0] (~quassel@cpe-024-163-024-033.triad.res.rr.com) 14.05.58 # wodz: why ? 14.08.40 Join perrikwp_ [0] (~quassel@cpe-024-163-024-033.triad.res.rr.com) 14.11.24 Quit perrikwp (Ping timeout: 245 seconds) 14.34.50 Join funman_ [0] (~fun@rockbox/developer/funman) 14.49.27 Quit funman (Quit: leaving) 14.49.28 # GodEater, I'm not /against/ IP bans. I played around with them quite a bit and never got many trigger hits. But if the tool is needed I'm not opposed to it. 14.50.53 Quit wodz (Quit: Leaving) 14.55.23 *** Saving seen data "./dancer.seen" 14.58.19 Nick funman_ is now known as funman (~fun@rockbox/developer/funman) 14.59.49 Quit factor (Quit: Leaving) 15.14.40 Quit Thra11 (Quit: kthxbai) 15.15.55 Join benedikt93 [0] (~benedikt9@unaffiliated/benedikt93) 15.21.59 # So, switching from openjdk-7-jdk to openjdk-6-jdk enabled me to build android rockbox 15.24.21 # that's interesting news 15.24.30 # I didn't think you could build much of anything with openjdk! 15.24.37 # I've only ever tried with the sun one 15.25.56 # <[Saint]> Thats also pretty interesting considering I've always used openjdk-7-jdk 15.26.18 # <[Saint]> And was yesterday until my build env fell over. 15.26.27 # fell over? 15.26.35 # <[Saint]> "broke" :) 15.26.40 # how? 15.26.54 # <[Saint]> The disk it was on shat itself. 15.32.23 Join perrikwp [0] (~quassel@cpe-024-163-024-033.triad.res.rr.com) 15.35.07 Quit perrikwp_ (Ping timeout: 240 seconds) 15.36.54 Quit einhirn (Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org) 15.45.55 Join perrikwp_ [0] (~quassel@cpe-024-163-024-033.triad.res.rr.com) 15.48.04 Quit perrikwp (Ping timeout: 245 seconds) 16.06.41 Quit Misanthropos (Quit: Leaving) 16.37.05 Join y4n [0] (y4n@unaffiliated/y4ndexx) 16.44.08 Join pyther [0] (~pyther@unaffiliated/pyther) 16.48.02 # Hi. I got an ogg album that seems to crash rockbox 3.10, all my other albums work just fine. "Data abort at 00000015 FSR 0x8 (domain 0, fault 8) address 0x98B81000)" 16.48.57 # which model ? 16.49.19 # SanDisk Sansa Fuze v2 16.49.43 # I ripped the cd using rubyripper, and vorbis tools to create the ogg, the oggs also have tags and an embedded .jpg 16.49.58 Quit scorche (Read error: Connection reset by peer) 16.50.15 Join scorche [0] (~scorche@rockbox/administrator/scorche) 16.51.37 Join Dingo- [0] (~dsadas@81-234-209-229-no108.tbcn.telia.com) 16.51.45 Quit Ariioch (Ping timeout: 255 seconds) 16.53.20 # ah that might be the reason, there are problems with the album art in ogg which take too much memory 16.53.30 # don't remember the associated bug on our tracker 16.54.49 # well I'll strip the art and see what happens 16.55.18 # * [Saint] dislikes embedded AA in general, as a rule. 16.55.26 *** Saving seen data "./dancer.seen" 16.55.46 # <[Saint]> there's seldom much call for "per-track" album art. 16.56.17 # will rockbox use the cover.jpg or some similar file for cover art? 16.56.23 # <[Saint]> even if there is a call for it, it can still be done with an external image as opposed to an embedded one. 16.56.24 # I don't really need cover art embedded in the track 16.57.18 Part Zagor 16.57.30 # <[Saint]> perhaps reading the manual might be a good idea ;) 16.57.47 # <[Saint]> Rockbox uses quite a few naming schemes for album art. 16.57.58 # [Saint]: that is always a viable solution, thought asking in IRC is so much quicker 16.58.19 # I that embedding the art into the file was a common standard, but it kinda does seem stupid 16.59.13 # <[Saint]> embedded art is usually HUGE as well...when there's no good reason to have art that's any larger than the smallest dimension of the screen, also. 16.59.41 # I've been shrinking everything to 300x300 17.02.00 Quit liar (Read error: Connection timed out) 17.02.40 # <[Saint]> pyther: http://download.rockbox.org/daily/manual/rockbox-ipodvideo/rockbox-buildap3.html#x19-399000C.21 17.02.43 # funman: removing the album art, didn't help I'm still getting that crash 17.02.56 # <[Saint]> this is the manual section you'll want re: album art 17.03.06 # thanks 17.03.11 # <[Saint]> nevermind the player type, its not relevant. 17.04.12 # <[Saint]> you'll want to look at "C.21.2 Where to put album art" specifically 17.06.37 # * [Saint] has /Music/Artist/Album structure, so just uses a single Folder.jpg in each album's folder. 17.06.56 # <[Saint]> Its also conveniently the naming scheme from many media players. 17.23.56 # * [Saint] wonders why rasher 's "unmodified" daily builds carry the M flag 17.29.15 Quit adnap (Ping timeout: 240 seconds) 17.31.26 Quit Naked (Ping timeout: 252 seconds) 17.32.08 Join Naked [0] (~naked@naked.iki.fi) 17.37.20 Join adnap [0] (~adnap@rrcs-71-42-140-57.sw.biz.rr.com) 17.37.58 Join dreamlayers [0] (~bgjenero@rockbox/developer/dreamlayers) 17.37.59 Part dreamlayers 17.38.10 Join dreamlayers [0] (~bgjenero@rockbox/developer/dreamlayers) 17.47.49 Join kadoban [0] (~kadoban@ip98-165-177-158.ph.ph.cox.net) 17.47.59 Join Brijesh3__ [0] (~Brijesh@121.245.17.210) 17.49.20 # hi..............is there anybody who worked for AAC decoder on rockbox?? 17.53.25 # Commit 74736fc in rockbox by 03Michael Sevakis: find_first_set_bit tweaks 17.56.42 # 74736fc build result: 0 errors, 2 warnings (Michael Sevakis committed) 17.56.55 # Brijesh3__, AAC works just fine on rockbox 17.58.02 # oh sorry, misunderstood you 18.02.03 # I would like to improve rockbox_flash messages, to clarify when the bootloader needs to be upgraded: http://gerrit.rockbox.org/r/#change,71 I know it says don't mess with this code, but I'm making a trivial change which doesn't affect the flashing itself. 18.10.22 Quit Zambezi (Ping timeout: 252 seconds) 18.14.48 Join Zambezi [0] (Zulu@bnc.fran.dotbnc.se) 18.30.21 Join bertrik [0] (~bertrik@ip117-49-211-87.adsl2.static.versatel.nl) 18.30.22 Quit bertrik (Changing host) 18.30.22 Join bertrik [0] (~bertrik@rockbox/developer/bertrik) 18.39.23 # Should core_alloc_ex() panic if it fails? Most callers don't check for errors, and a panic would be better than other random consequences. 18.42.59 Quit Brijesh3__ (Quit: Leaving) 18.43.13 Join anewuser [0] (~anewuser@190.207.131.94) 18.43.13 Quit anewuser (Changing host) 18.43.13 Join anewuser [0] (~anewuser@unaffiliated/anewuser) 18.55.28 *** Saving seen data "./dancer.seen" 18.56.51 Quit anewuser (Ping timeout: 248 seconds) 18.59.13 Join lebellium [0] (~chatzilla@e179071140.adsl.alicedsl.de) 19.03.01 Join liar [0] (~liar@clnet-p09-185.ikbnet.co.at) 19.11.11 Join mudd1 [0] (~cmertes@ip-78-94-202-227.unitymediagroup.de) 19.24.54 Quit Keripo (Quit: Leaving.) 19.27.53 Quit lebellium (*.net *.split) 19.27.54 Quit scorche (*.net *.split) 19.27.54 Quit funman (*.net *.split) 19.27.55 Quit pamaury (*.net *.split) 19.27.55 Quit tchan (*.net *.split) 19.27.55 Quit T44 (*.net *.split) 19.27.55 Quit fs-bluebot (*.net *.split) 19.27.56 Quit jhMikeS (*.net *.split) 19.27.56 Quit froggyman (*.net *.split) 19.27.56 Quit simabeis (*.net *.split) 19.27.56 Quit dv_ (*.net *.split) 19.27.57 Quit Guinness` (*.net *.split) 19.27.57 Quit jm (*.net *.split) 19.27.58 Quit Sleepy_Coder (*.net *.split) 19.27.58 Quit GodEater_ (*.net *.split) 19.27.59 Join simabeis [0] (~simabeis@lobmenschen.de) 19.28.02 Join froggyman [0] (~froggyman@unaffiliated/froggyman) 19.28.06 Join jm [0] (jm@epicsol.org) 19.28.06 Join funman [0] (~fun@rockbox/developer/funman) 19.28.08 Join T44 [0] (~Topy44@f049225154.adsl.alicedsl.de) 19.28.09 Join jhMikeS [0] (~jethead71@c-68-61-166-99.hsd1.mi.comcast.net) 19.28.09 Quit jhMikeS (Changing host) 19.28.09 Join jhMikeS [0] (~jethead71@rockbox/developer/jhMikeS) 19.28.22 Join lebellium [0] (~chatzilla@e179071140.adsl.alicedsl.de) 19.28.22 Join scorche [0] (~scorche@rockbox/administrator/scorche) 19.28.38 Join tchan [0] (~tchan@lunar-linux/developer/tchan) 19.28.58 Join Guinness [0] (Slayer@c-68-55-111-159.hsd1.va.comcast.net) 19.29.00 Join pamaury [0] (~quassel@vit94-1-82-67-248-70.fbx.proxad.net) 19.29.01 Quit pamaury (Changing host) 19.29.01 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 19.29.09 Join dv_ [0] (~quassel@chello080108009040.14.11.vie.surfer.at) 19.32.10 Join fs-bluebot [0] (~fs-bluebo@f053154112.adsl.alicedsl.de) 19.32.28 Quit dreamlayers (Quit: Leaving.) 19.33.00 Join Sleepy_Coder [0] (majic@just.dontfeedthebots.co.uk) 19.33.00 Quit Sleepy_Coder (Changing host) 19.33.00 Join Sleepy_Coder [0] (majic@unaffiliated/sleepycoder/x-938672) 19.38.32 Quit bug2000 (Ping timeout: 252 seconds) 19.39.04 Join anewuser [0] (~anewuser@186.93.202.222) 19.39.04 Quit anewuser (Changing host) 19.39.04 Join anewuser [0] (~anewuser@unaffiliated/anewuser) 19.40.45 Quit mortalis (Quit: KVIrc 4.1.1 Equilibrium http://www.kvirc.net/) 19.46.06 Quit curtism (Ping timeout: 276 seconds) 19.58.12 Join curtism [0] (~curtis@bas11-montreal02-1128531121.dsl.bell.ca) 20.02.59 Quit thims (Quit: leaving) 20.07.58 Quit liar (Read error: Operation timed out) 20.08.49 # Commit 900b494 in rockbox by 03Amaury Pouly: imx233: fix PHYISCAL_ADDR to handle the buffered region (hard to debug if misused) 20.08.50 # Commit bf47e57 in rockbox by 03Amaury Pouly: imx233: implement dcp blitting, simplify code and make it work even in context interrupt by busy waiting 20.08.51 # Commit 05ba5c1 in rockbox by 03Amaury Pouly: imx233: update arbiter to get more debug information, update debug screen accordingly 20.08.51 # Commit d32891f in rockbox by 03Amaury Pouly: fuze+: change rendering scheme, do not rely on generic framebuffer and implement rect updating and yuv blitting correctly. 20.08.52 # Commit 28a10ec in rockbox by 03Amaury Pouly: sbloader: always send packets of size xfer_size (even the first). Also maintain a table of known transfer sizes. In particular stmp3770 uses 48 ... 20.11.00 # I'd to move the fuze+ to unstable. I know I must update builds.pm but the icon field is unclear to me: to which icons does it refer ? 20.11.22 # 28a10ec build result: All green 20.12.05 # gevaerts: any idea ? 20.15.35 # I guess Zagor is the one who knows since he made most of the modifications to this file 20.19.42 # Commit d684858 in rockbox by 03Amaury Pouly: fuze+: mark as unstable 20.21.05 Join Strife89 [0] (~Strife89@207.144.201.128) 20.22.08 # d684858 build result: All green 20.37.05 # [Saint]: hm, might be because of my build scripts :-\ 20.39.48 # pamaury: I assume it's talking about the images eg. http://www.rockbox.org/playerpics/archosondiosp-small.png 20.40.33 # hm, so we actually have fuze+ icons 20.45.32 # that's frustrating, the fuze+ OF changes the DC-DC frequency when tuner is enabled but when I does that, it simply shutdowns ! 20.47.58 Quit ze (Ping timeout: 252 seconds) 20.48.48 Quit Xerion (Ping timeout: 240 seconds) 20.51.30 Join ze [0] (ze@ze.yi.org) 20.55.29 *** Saving seen data "./dancer.seen" 21.11.52 Join Misanthropos [0] (~Misanthro@adsl-84-227-69-83.adslplus.ch) 21.18.42 Quit bluebrother (Disconnected by services) 21.18.44 Join bluebrother^ [0] (~dom@rockbox/developer/bluebrother) 21.20.47 Quit y4n (Quit: PANTS OFF!) 21.20.56 Quit fs-bluebot (Ping timeout: 272 seconds) 21.22.16 Join fs-bluebot [0] (~fs-bluebo@g231122069.adsl.alicedsl.de) 21.47.04 Join saratoga [0] (~980329c2@www.haxx.se) 21.47.18 # kugel: is the volume set correctly in this commit: http://git.rockbox.org/?p=rockbox.git;a=commitdiff;h=1dcc834e5954cfd662e501565d265c3d0c8d9cae 21.48.01 # IIRC it reduced the volume by 4dB 21.48.41 # IIRC the R0 has an as3543, so it probably needs the AMSv2 value 22.06.05 Quit dfkt (Quit: -= SysReset 2.55=- Sic gorgiamus allos subjectatos nunc.) 22.16.35 Join Guest35250 [0] (~Ben_and_A@pool-96-238-198-249.bing.east.verizon.net) 22.16.49 # I have a question regarding thmees 22.17.02 Nick Guest35250 is now known as Baltowolf (~Ben_and_A@pool-96-238-198-249.bing.east.verizon.net) 22.18.06 # Anyone? 22.18.56 # not if you don't ask your question 22.19.06 # * bluebrother^ is unlikely to answer an unasked question 22.19.23 # Well, I was seeing if someone would response first... 22.19.53 Join liar [0] (~liar@clnet-p09-185.ikbnet.co.at) 22.20.26 # So, I'm trying to "port"/redesign a theme, the iLike theme, I just changed the backdrop, and the only other thing I want to do is change the pause/play buttons, I took the blue pause/play buttons I wanted from the other iLike theme and scaled them but there's a magenta transparency color in Rockbox. Hwo do I remove it? 22.20.54 # why do you want to remove transparency? 22.21.31 # Well, I want to remove the color showing through. 22.21.50 # which color showing through what? 22.22.21 # The magenta color is showing through the backdrop. 22.22.29 # that magenta is the key for transparency. Use it for areas that should be transparent. If you want an area not to be transparent use a different color 22.22.44 # then you likely have changed the color. 22.23.02 # What do you mean? 22.23.05 # or scaling did some dithering, ending up with some pixels in a color in between 22.23.19 # How come I can see it through the backdrop though? 22.23.48 # err ... a backdrop is in the back. How do you want to see through the backdrop? 22.23.54 # don't we support transparency without magenta by now? 22.24.20 # Well, why is the magenta color visible? 22.24.25 # hmm, there has been a change, right. 22.24.27 # I guess that'sm y real question. 22.24.33 # because is a non-transparent magenta color 22.24.38 # Oh. 22.24.46 # So I need to change it then, right? 22.24.50 # Then it will work? 22.25.05 # I don't think magenta as transparency has been removed, since that would have broken all existing themes that use transparency 22.25.11 # if you use the right magenta. 22.25.12 Join perrikwp [0] (~quassel@cpe-024-163-024-033.triad.res.rr.com) 22.25.31 # So, which magenta color do I need to use? 22.25.49 # ff00ff 22.26.27 # <[Saint]> "the standard horrid magenta in MS Paint" :P 22.27.14 # :) 22.27.40 Quit perrikwp_ (Ping timeout: 245 seconds) 22.28.33 # <[Saint]> If you rescale an image (Hi, I'm the iLike author by the way), the colors will blend...this is a fact. This will *completely* fuck transparency...and you'll need to re-do it by hand. 22.29.31 # [Saint]: well, you _could_ disable dithering in your image program :) 22.29.32 # you'll only need to turn of any anti aliasing 22.30.03 # Ok, trying it now. Thanks. :P 22.30.10 # Nice them by the way Saint. 22.30.18 # *theme 22.30.55 # <[Saint]> I find even then they try to be "smart" and you'll still get a "ring" of blended color around the really obvious blocks of different color. 22.31.08 # <[Saint]> Maybe I use "the wrong editor(TM)". 22.31.42 # do you use nearest-neighbour scaling? 22.32.00 # if not the scaling algorithm will most likely interpolate the colours 22.32.10 # <[Saint]> Thanks, Baltowolf. You can thank Apple...I only painstakingly recreated it ;) 22.33.00 # :P 22.34.59 # now to see if it works... 22.36.53 # I think it shrunk XD 22.37.08 # I put it in Photoshop and used a giant brush and I took away some pixels I guess. ROFL 22.37.27 # IT looks fine otherwise though. I'll fix it when I get home, I've got to go. Thanks for your help guys. 22.37.40 # I'll report back if it works. :P 22.37.44 # bye 22.37.45 Part Baltowolf 22.38.00 Quit benedikt93 (Quit: Bye ;)) 22.47.22 Quit liar (Read error: Connection timed out) 22.55.32 *** Saving seen data "./dancer.seen" 23.01.09 Quit curtism (Quit: Live Long and Prosper) 23.01.22 Join curtism [0] (~curtis@bas11-montreal02-1128531121.dsl.bell.ca) 23.10.53 Join perrikwp_ [0] (~quassel@cpe-024-163-024-033.triad.res.rr.com) 23.11.20 Join Xerion [0] (~xerion@5419EF19.cm-5-2d.dynamic.ziggo.nl) 23.13.25 Quit perrikwp (Ping timeout: 255 seconds) 23.13.58 Join perrikwp [0] (~quassel@cpe-024-163-024-033.triad.res.rr.com) 23.15.58 Quit perrikwp_ (Ping timeout: 245 seconds) 23.27.43 Quit perrikwp (Read error: Connection reset by peer) 23.28.54 Join perrikwp [0] (~quassel@cpe-024-163-024-033.triad.res.rr.com) 23.49.50 Join factor [0] (~factor@74.197.205.204)