--- Log for 02.10.120 Server: wilhelm.freenode.net Channel: #rockbox --- Nick: logbot_ Version: Dancer V4.16 Started: 4 days and 19 hours ago 00.21.19 Quit Xeha (Ping timeout: 246 seconds) 00.32.08 *** Saving seen data "./dancer.seen" 01.15.43 Quit asaba (Quit: Relay server offline) 01.16.27 Join asaba [0] (~asaba@103.113.159.184) 01.27.05 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 01.30.58 Join ZincAlloy [0] (~Adium@ip5f5acf9f.dynamic.kabel-deutschland.de) 01.35.43 Quit ZincAlloy (Ping timeout: 260 seconds) 01.42.43 Quit pamaury (Ping timeout: 260 seconds) 01.43.54 Join ZincAlloy [0] (~Adium@2a02:8108:943f:d824:dd70:9d6b:47e7:1f50) 01.48.47 Quit ZincAlloy (Ping timeout: 272 seconds) 01.48.52 Quit asaba (Quit: Relay server offline) 01.50.08 Join asaba [0] (~asaba@103.113.159.184) 01.53.30 Quit asaba (Client Quit) 01.53.56 Join asaba [0] (~asaba@103.113.159.184) 02.00.02 Quit asaba (Quit: Relay server offline) 02.00.36 Join asaba [0] (~asaba@103.113.159.184) 02.01.25 Quit kugel (Ping timeout: 264 seconds) 02.09.10 Join kugel [0] (~kugel@ip5b40d8e6.dynamic.kabel-deutschland.de) 02.09.10 Quit kugel (Changing host) 02.09.10 Join kugel [0] (~kugel@rockbox/developer/kugel) 02.10.43 Quit asaba (Quit: Relay server offline) 02.11.58 Join asaba [0] (~asaba@103.113.159.184) 02.15.02 Quit lonoxmont (Ping timeout: 256 seconds) 02.15.16 Join lonoxmont [0] (~lonoxmont@024-180-058-254.res.spectrum.com) 02.16.07 Quit kugel (Ping timeout: 246 seconds) 02.17.55 Join johnb5 [0] (~johnb2@p5b3afe15.dip0.t-ipconnect.de) 02.19.15 # speachy : screen update is amazingly better, seeking works again. Thx 02.21.56 Join kugel [0] (~kugel@2a02:8109:9e80:132c:201:2eff:fe4f:ff76) 02.21.56 Quit kugel (Changing host) 02.21.56 Join kugel [0] (~kugel@rockbox/developer/kugel) 02.27.32 Join pamaury [0] (~pamaury@maths.r-prg.net.univ-paris7.fr) 02.27.32 Quit pamaury (Changing host) 02.27.32 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 02.29.27 Quit johnb5 (Ping timeout: 240 seconds) 02.32.12 *** Saving seen data "./dancer.seen" 02.34.28 Quit asaba (Quit: Relay server offline) 02.35.42 Join asaba [0] (~asaba@103.113.159.184) 02.41.56 Quit asaba (Quit: Relay server offline) 02.43.27 Join livvy [0] (~livvy@gateway/tor-sasl/livvy) 02.44.08 Join asaba [0] (~asaba@103.113.159.184) 02.57.32 Quit asaba (Quit: Relay server offline) 02.57.58 Join asaba [0] (~asaba@103.113.159.184) 03.06.19 Quit asaba (Quit: Relay server offline) 03.08.32 Join asaba [0] (~asaba@103.113.159.184) 03.16.35 Quit asaba (Quit: Relay server offline) 03.17.17 Join asaba [0] (~asaba@103.113.159.184) 03.24.40 Quit asaba (Quit: Relay server offline) 03.24.51 Join asaba [0] (~asaba@103.113.159.184) 03.34.55 Quit mendel_munkis (Remote host closed the connection) 03.36.17 Join mendelmunkis [0] (~mendelmun@65-128-170-32.mpls.qwest.net) 04.10.37 Quit kugel (Ping timeout: 260 seconds) 04.32.13 *** Saving seen data "./dancer.seen" 04.49.11 Join kugel [0] (~kugel@ip5b40d8e6.dynamic.kabel-deutschland.de) 04.49.12 Quit kugel (Changing host) 04.49.12 Join kugel [0] (~kugel@rockbox/developer/kugel) 04.50.15 Join johnb5 [0] (~johnb2@p5b3afe15.dip0.t-ipconnect.de) 05.03.50 Quit johnb5 (Ping timeout: 256 seconds) 05.12.02 Join sakax [0] (~r0b0t@unaffiliated/r0b0t) 06.09.34 Join johnb5 [0] (~johnb2@p5b3afe15.dip0.t-ipconnect.de) 06.11.18 Join Xeha [0] (~Xeha@unaffiliated/xeha) 06.32.15 *** Saving seen data "./dancer.seen" 06.33.21 Join tchan1 [0] (~tchan@c-98-220-238-152.hsd1.il.comcast.net) 06.35.27 Quit tchan (Ping timeout: 240 seconds) 06.41.16 # speachy , _bilgus__ : as for hires sample tracks, you can find many here: http://www.2l.no/hires/ 06.42.15 # I didn't notice any difference vs. CD quality ;-) 06.48.58 Quit johnb5 (Ping timeout: 260 seconds) 06.52.43 # okay from what I can tell, we're down to two significant issues on the x3ii. 06.53.14 # a) "pop" on startup and sometimes between tracks. (probably due to sample rate changing) 06.53.29 # b) sometimes playback just ... freezes, and can't be recovered. 06.54.23 # (these _may_ affect the rocker too, that's not clear yet) 07.26.08 # speachy: a) definitely does affect the rocker, too, yes, i have exactly that behaviour. 07.26.17 # speachy: if i find out how to apply the dev build, sure. 07.27.07 # oh, it seems it lets me select that one directly from the "Development Version" thing in rbutil 07.27.12 # ok, hold on. 07.30.35 # ok i selected "Development Version (Revision b5cb99a)" but in the rockbox info in the settings it shows "Version: 466156...". 07.31.28 # the latter is from 2 days ago. 07.31.32 # did you reboot? 07.31.36 # yes 07.31.52 # (the hosted targets can't ROLO yet) 07.32.18 # grab https://build.rockbox.org/data/rockbox-agptekrocker.zip 07.32.23 # and unzip it to the root of the sd card. 07.32.38 # (that link always points at the latest dev build) 07.33.34 # (the latest nightly rocker zip also shows the correct filename inside) 07.34.17 # https://www.rockbox.org/dl.cgi?bin=agptekrocker 07.35.12 # yup NOW i'm on bc5. 07.35.18 # err, b5c... 07.37.21 # speachy: ok the lowest volume level is MUCH too loud 07.38.43 # speachy: i'm at -127db (lowest setting) and it's ears-blowing. 07.41.32 # allright, a settings reset seems to have solved that. 07.42.03 # the volume scaling was changed. 07.50.29 # speachy: looking good so far, i'm unable to spot any kind of p(l)opping sounds when switching tracks. 07.50.48 # but there is a pop at startup? 07.51.03 # didn't notice one either, no. 07.54.51 # only thing that annoys me i can spot is the behaviour of the power button, since it's used for a) locking and b) powering off. since b) requires holding the button long, it shouldn't lock when actuating the button already, but only when releasing after a short time. 07.55.41 # otherwise the behaviour is just confusing. it locks and then half a second later powers off. 07.56.24 # but no plopping sounds on startups, no, just tested multiple times. 07.59.24 # https://unix.porn/rockbox.jpg 08.01.39 # OH, volume control is broken on some songs... 08.01.45 # oh good, so the audio issues seem to be limited to the x3ii (and probably x20) 08.02.17 # i'm unable to control the volume now and it's damn loud 08.02.37 # does the vol level indicator change? 08.02.47 # that does change, yes, but even on 0 it's just loud 08.04.26 # skip to the next song, any difference? 08.04.40 # (wondering if that different track triggered a sample rate change) 08.04.57 # (not that it should matter; volume control is completely independent) 08.08.29 # no, and even rebooting didn't fix it. 08.08.49 # it just stays way too loud 08.16.20 # interesting finding: when using the volume buttons on the right, i hear interrupts in the music with exactly the button repeat rate when keeping it hold down. 08.19.05 # yeah, I see that too. 08.21.57 # also had an audio playback hang, until the voiced menu kicked it into working 08.22.13 # had one too, where a reboot solved it 08.22.44 # and voice prompts on the main manu are garbled a bit. with a couple of random playlist control errors thrown in too. 08.22.54 # the symptoms here are memory corruption. 08.23.02 # O.O 08.23.56 # but I also have a small pile of additional WIP patches going on 08.28.29 Quit tchan1 (Quit: WeeChat 2.8) 08.28.49 Join tchan [0] (~tchan@lunar-linux/developer/tchan) 08.29.45 # do you see random "failure accessing playlist control file" messages? 08.32.10 # no 08.32.16 *** Saving seen data "./dancer.seen" 08.33.35 # huh, I wonder if my SD card is flaky. 08.37.54 # yup, corrupted 08.49.36 # ewwww :-( 08.53.00 # we also dont' need to poll the battery voltage and charging state every tick. geez. 09.34.28 Quit pamaury (Quit: Konversation terminated!) 09.43.54 Quit prof_wolfff (Ping timeout: 272 seconds) 09.58.40 # oh wow, my physical hifi equalizer unit just arrived. 09.59.10 # nice. 10.01.52 # Build Server message: New build round started. Revision b0e1b24, 282 builds, 9 clients. 10.15.04 # this current shouldn't matter on the rocker unless you're using >48KHz. But I wanted it in as a baseline before I started trying to tackle those odd audio issues. 10.15.13 # current build I mean 10.23.48 # Build Server message: Build round completed after 1316 seconds. 10.23.52 # Build Server message: Revision b0e1b24 result: All green 10.31.05 Join tobbez_ [0] (tobbez@sagiri.wrya.net) 10.31.10 Quit tobbez (Ping timeout: 240 seconds) 10.31.16 Nick tobbez_ is now known as tobbez (tobbez@sagiri.wrya.net) 10.32.20 *** Saving seen data "./dancer.seen" 10.40.06 Quit TheSeven (Disconnected by services) 10.40.16 Join [7] [0] (~quassel@rockbox/developer/TheSeven) 10.40.32 Quit bzed (*.net *.split) 10.40.33 Quit pixelma (*.net *.split) 10.40.53 Join bzed [0] (~bzed@shell.bzed.at) 10.40.53 Join pixelma [0] (marianne@rockbox/staff/pixelma) 10.43.28 Quit Rondom (Read error: Connection reset by peer) 10.44.06 Quit marex-cloud_ (Ping timeout: 244 seconds) 10.45.23 Join Rondom [0] (~rondom@modo.nonmodosedetiam.net) 10.47.10 Join marex-cloud_ [0] (sid137234@gateway/web/irccloud.com/x-ukndsoussuzqivtp) 10.55.12 Quit livvy (Remote host closed the connection) 10.55.23 Join livvy [0] (~livvy@gateway/tor-sasl/livvy) 10.57.03 # ok, the x3ii still has the pop/etc and the audio hang. neither seems to have happened with the rocker. 11.14.59 Quit marex-cloud_ () 11.26.51 Join tbaxter [0] (~Adium@pool-100-34-20-58.phlapa.fios.verizon.net) 11.40.44 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 11.44.50 # _bilgus__: with DEBUG turned on, plugins/announce_status.c:561 fails. I don't know what it's intending to do. 12.06.30 Join johnb5 [0] (~johnb2@p5b3afe15.dip0.t-ipconnect.de) 12.09.21 Join MrZeus_ [0] (~MrZeus@2a02:c7f:70d0:6a00:4de9:2d61:e6b2:84bc) 12.11.06 Quit johnb5 (Ping timeout: 256 seconds) 12.18.45 Join ZincAlloy [0] (~Adium@ip5f5acf9f.dynamic.kabel-deutschland.de) 12.23.01 Quit ZincAlloy (Ping timeout: 246 seconds) 12.23.41 Join ZincAlloy [0] (~Adium@2a02:8108:943f:d824:14e1:4f1b:6b0a:d867) 12.23.44 # <_bilgus__> its supposed to allow the usb screen and allow you to stop playback, shut off player 12.24.27 # I think what's happening with the x3ii's wonky audio stuff is that the OS's driver API is triggering the callback before we're ready. 12.24.39 # <_bilgus__> not sure why it would fail there considering the default handler is used in lots of places 12.25.11 # _bilgus__: failing as in failing to compile, because 'button' is not defined. 12.26.10 # <_bilgus__> oh duh I see that :/ Now 12.28.04 Quit massiveH (Quit: Leaving) 12.31.12 Join johnb5 [0] (~johnb2@p5b3afe15.dip0.t-ipconnect.de) 12.32.21 *** Saving seen data "./dancer.seen" 12.32.54 # <_bilgus__> I'll have to revisit that 13.02.46 Quit johnb5 (Ping timeout: 272 seconds) 13.31.22 Join lebellium [0] (~lebellium@89-92-69-66.hfc.dyn.abo.bbox.fr) 13.53.23 Join petur [0] (~petur@rockbox/developer/petur) 14.02.01 Join beencubed [0] (~beencubed@209.131.238.248) 14.06.09 Join johnb5 [0] (~johnb2@p5b3afe15.dip0.t-ipconnect.de) 14.17.52 Quit johnb5 (Ping timeout: 265 seconds) 14.32.24 *** Saving seen data "./dancer.seen" 14.42.54 Join johnb5 [0] (~johnb2@p5b3afe15.dip0.t-ipconnect.de) 14.47.44 Quit johnb5 (Ping timeout: 256 seconds) 15.08.14 # hmm. so our "beep buffer" is sitting in IRAM. 15.31.19 Join johnb2 [0] (~johnb2@p5b3afe15.dip0.t-ipconnect.de) 15.55.16 Join johnb3 [0] (~johnb2@p5b3afe15.dip0.t-ipconnect.de) 15.56.16 Quit t0mato (Read error: Connection reset by peer) 15.56.25 Quit johnb2 (Ping timeout: 240 seconds) 15.56.31 Join t0mato [0] (~t0mato@193.32.127.161) 16.01.58 Quit johnb3 (Ping timeout: 260 seconds) 16.32.26 *** Saving seen data "./dancer.seen" 16.50.13 Join ac_laptop [0] (~ac_laptop@186.2.247.129) 17.54.01 # speachy: IRAM? 17.57.16 # on-chip low-latency RAM 17.59.37 # granted at lower bitrates it's only 384 bytes but if we crank up higher.. it scales linearly (@192K max we'd need 1.5K) 18.06.22 # speachy: so basically cpu cache 18.06.33 # to quote what it's called in x86 land 18.06.54 # but in this case... used for far more 18.07.18 # since for some cases it could be used the only ram 18.07.51 # no, cpu cache is different. 18.08.18 # ok... 18.08.19 # cache sits between the CPU and your memory/data bus, but IRAM is attached to that bus. 18.08.59 # i just thought it was similar because i've read alternative BIOS implementations would use the cache as RAM until the system was further initialized and could switch to main RAM 18.20.52 # (L1) cpu caches are typically clocked at the same speed as the CPU, ultra-fast and low latency. IRAM is typically clocked at the full system bus speed. 18.21.32 # (you may have a third layer of on-chip RAM which is slower. and then you have external DRAM/SRAM, which has higher latency/lower clocks yet. 18.22.06 # so the closer to the CPU you can get things, the faster it'll be. 18.23.16 # a good rule of thumb is that each layer in your memory hierarchy is an order of magnutude slower 18.24.24 # oh wow... 18.24.54 # I just found the USB cable for my original archos player. it's the only thing I've ever owned that had a USB-A -> USB-A cable. 18.25.49 # and the adapter I was using for its power supply 18.26.08 # with its embarrasingly bad solder joints 18.32.30 *** No seen item changed, no save performed. 18.33.13 Quit MrZeus_ (Read error: Connection reset by peer) 18.34.42 Join MrZeus_ [0] (~MrZeus@90.203.212.4) 18.44.14 Join ZincAlloy1 [0] (~Adium@2a02:8108:943f:d824:e87c:1c38:9a2d:a3e5) 18.45.17 Quit ZincAlloy (Ping timeout: 272 seconds) 18.46.56 Quit pamaury (Ping timeout: 258 seconds) 18.51.24 Quit lebellium (Quit: Leaving) 19.03.23 Quit livvy (Ping timeout: 240 seconds) 19.12.58 Quit petur (Quit: Leaving) 19.26.18 Quit ZincAlloy1 (Quit: Leaving.) 19.37.06 Quit bluebrother (Disconnected by services) 19.37.11 Join bluebrother^ [0] (~dom@rockbox/developer/bluebrother) 19.37.17 Join fs-bluebot_ [0] (~fs-bluebo@55d462d0.access.ecotel.net) 19.39.47 Quit fs-bluebot (Ping timeout: 260 seconds) 19.46.56 Quit MrZeus_ (Ping timeout: 256 seconds) 19.47.03 # speachy: just how bad were those? 19.48.54 # at the time, pretty good. :) At least once they moved to the Recorder with the bitmapped screen 19.49.39 # bit map? 19.49.42 # ah, 2 color? 19.49.55 # no, as opposed to 2x16 character cells 19.50.01 # oh. 19.50.15 # bitmaps are normally monochrome so that's why i thought.. 19.50.26 # XBMs, etc. 19.51.14 # make that 2 rows of *11* characters. :D 19.51.34 # vs 112x64 pixels for the newer versions. 19.57.58 Join tomb [0] (tomf@our.lady.of.perpetual.faith) 20.11.56 Join massiveH [0] (~massiveH@ool-18e4e82f.dyn.optonline.net) 20.18.48 # For some reason preferences with rockbox and the original firmware aren't saving. Any idea what the issue is? The permissions look fine to me 20.24.43 Quit t0mato (Quit: Ping timeout (120 seconds)) 20.24.54 Join t0mato [0] (~t0mato@193.32.127.161) 20.32.34 *** Saving seen data "./dancer.seen" 20.56.48 # I think I figured out the audio hang problem. 20.57.49 # root cause is unknown but we can now recover cleanly. 20.57.59 # (likely related to that popping..) 21.05.02 # Build Server message: New build round started. Revision c7eceea, 282 builds, 9 clients. 21.23.09 # Build Server message: Build round completed after 1089 seconds. 21.23.13 # Build Server message: Revision c7eceea result: All green 21.27.18 # and simply toggling the output port switch or adjusting the volume is enough to generate pops on the audio output. 21.27.47 Quit ac_laptop (Ping timeout: 240 seconds) 21.29.12 # I think we might be SOL there. since we don't have kernel sources. 21.29.32 # I think it's the codec powering on and off 22.13.07 Quit Oksana (Ping timeout: 246 seconds) 22.29.06 Join Oksana [0] (~Wikiwide@Maemo/community/ex-council/Wikiwide) 22.30.54 Join ac_laptop [0] (~ac_laptop@186.2.247.129) 22.32.37 *** Saving seen data "./dancer.seen" 22.34.28 # <_bilgus__> maybe we should stream empty audio to it then 22.42.46 Quit t0mato (Quit: Ping timeout (120 seconds)) 22.45.19 Join t0mato [0] (~t0mato@193.32.127.158) 23.03.37 # the rocker does the same thing, just not as pronounced 23.06.40 # the big click is the codec being reset 23.07.14 # "the analog output should be muted externally if click noise adversely affect system performance" 23.31.01 # welp, I fixed the read only error by dumping an mp3 into the original firmware. What a weird issue. I love rockbox so much. 23.31.08 Quit Acou_Bass (Ping timeout: 260 seconds) 23.33.57 Join Acou_Bass [0] (~eddie@cpc96070-bolt17-2-0-cust175.10-3.cable.virginm.net) 23.38.35 Quit [7] (Ping timeout: 244 seconds) 23.39.24 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven) 23.41.39 # funny thing is permissions errors are only a thing on the hosted targets... 23.41.54 # the older ones don't even have a permission model 23.42.24 # for why would they? they're basically a single user application. 23.43.55 Quit Acou_Bass (Ping timeout: 240 seconds) 23.44.20 # its the first time I've ever seen anything that seems remotely related to permissions -- let alone any errors, really. I've been using this since around mid 2007 or whenever the iPod Video one came out. 23.45.54 Join Acou_Bass [0] (~eddie@cpc96070-bolt17-2-0-cust175.10-3.cable.virginm.net)