--- Log for 23.01.117 Server: nylund.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 18 days and 3 hours ago 00.03.45 # Thanks! 00.06.09 # jhMikeS: why is the cbdata affectation in ascodec_async_init conditional ? 00.06.46 # to short out setting it if there's no callback since it does nothing then 00.07.05 # the inlining should optimize it out 00.10.35 Quit furrywolf (Read error: Connection reset by peer) 00.12.57 # ok 00.13.56 # dongs you were trying to verify the pinout of the NAND https://imgur.com/a/1Z9Fd -> the datasheet furrywolf posted has it on pg 72 http://www.keil.com/dd/docs/datashts/ams/as3525_ds.pdf 00.13.57 # 3Gerrit review #72 at http://gerrit.rockbox.org/r/72 : 3correct a typo by Wieland Hoffmann 00.14.19 # :/\ 00.14.21 # Ok, if after a few days, the clip+ still doesn't do anything when plugged into usb -- does that mean the NAND is dead, and the hardware is no good anymore? 00.14.38 Join furrywolf [0] (~randyg@72-57-75-247.pools.spcsdns.net) 00.14.45 # probably not 00.15.04 # what does it mean then? 00.15.07 # when I connected my fuze to my shop stereo today, it made a number of annoyingly loud pops before it started playing. Can the headphones amp be kept powered off until the unit is fully ready to play? 00.15.33 # furrywolf that is a ground loop 00.15.58 # or do you mena when you were plugging it? 00.17.01 # I mean from the time I pressed the power button until the time it loaded the playlist and played the track it resumed on 00.17.04 # semitones how long has the device been unplugged? 00.17.09 # Actually I get a windows message that the USB drive malfunctioned and windows cannot recognize it... 00.17.18 # Bilgus_, for 3+ days 00.17.23 # there's no ground loop on a device with no ground, as it was running off battery 00.17.37 # and ground loops tend to cause 60hz hum, not loud pops. 00.18.30 # furrywolf: I get similar from my zip. It buzzes during boot, and makes a couple clicks. Maybe that has to do in part with the volume set. 00.18.37 # * jhMikeS adds a comment about that conditional then 00.18.48 # *on the speaker, that is 00.19.26 # Idk mine does pop when plugged in but you are correct on battery no ground loop 00.20.09 # semitones try a different port on the pc and hold down the volume + button when you plug it 00.20.17 # the normal solution is to keep the audio output disconnected until everything is powered up and the buffer is full... keeping the amp powered off is probably the fuze equivalent. 00.20.57 # ? 00.21.45 Quit TheLemonMan (Quit: "It's now safe to turn off your computer.") 00.22.11 # my player the fuze+ pops when plugged in to stereo 00.22.30 # well when on charger and plugged to stereo 00.22.54 # this wasn't on charger. running off battery, powered up with the 3.5mm cable connected. 00.23.23 # Idk mine does pop when plugged in but you are correct on battery no ground loop /quote 00.23.31 # agreed 00.24.04 # Bilgus_, something happened that time - windows asked to format the drive, and it appears to be 0 bytes...? 00.24.29 # * pamaury spots fuze+ and slowly disappears so no one can blame him for anything 00.25.03 # hey the fuze+ is pretty awesome now, esp with that selective keylock 00.25.39 # compared to the OF it is perfect 00.26.27 # semitones It usually shows up as a raw partition but not 0bytes 00.28.12 # what does the vol up button do? Bilgus_ 00.28.24 # makes it load into OF 00.28.50 # ah kk. Maybe I should give up on this then, it does not seem to cooperate 00.29.29 # Idk the fact that holding the button up made it boot gives me some hope that the Bootloader is there 00.30.24 # ok! although I unplugged it and tried again, and now it isn't working. Maybe the battery has to run out a little again 00.30.36 # un-plug and hold the power button and try re-plugging without holding anything and see if it fails to enumerate again 00.30.52 # ok, holidng power for 30 s 00.31.07 # the RB bootloader will not work if the battery is real low 00.31.47 # Bilgus_, that did the trick 00.31.54 # (or non existent) 00.31.59 # it is asking me to format again, lets see what properties say 00.32.11 Join _mt_ [0] (~MT@50-241-203-110-static.hfc.comcastbusiness.net) 00.32.38 # blah, fat doesn't allow "?" in filenames, does it? 00.32.51 # properties still says 0 bytes. At this point, what should I do? Should I see if rockbox utility sees it? 00.33.02 # furrywolf: probably not 00.33.06 # NO the rb utility won't 00.33.09 # om 00.33.11 # ok 00.33.53 # should I change the filename of some of my tracks to not match the actual album name, or try to figure out how to force the kernel to write non-valid filenames? :) 00.33.57 # ok so this time you didn't hold any buttons and when plugged it shows 0 bytes? 00.34.03 # Yes 00.34.36 # It also only shows one drive, even though there is a microSD plugged into the clip+ as well 00.34.48 # but that's probably expected 00.35.14 Quit ender` (Quit: Knowledge is power. Power corrupts.) 00.35.17 # oh first remove that sd card after you un-plug and hold the power button again 00.35.39 # thanks 00.36.07 # I doubt it will make a difference TBH 00.36.20 # no stone unturned. What are we hoping for? 00.37.05 # It shows 0 bytes still 00.37.42 # was hoping that it'd atleast show the RAW partition 00.38.14 # but I'd say something is dead and maybe your NAND is just completely dead whereas others were not 00.38.44 Quit alexweissman (Remote host closed the connection) 00.39.41 # well hold on to it for now there may eventually be hope or someone to send it to to get it fixed 00.40.22 # Ok for sure. Could I give my email address to someone who may eventually want to do something with it? The screen is still good for sure 00.41.25 Quit robertd1 (Ping timeout: 252 seconds) 00.43.14 # Idk I'd just toss it in a drawer and check the forums or here next time you think about it 00.43.53 # I'll eventually have one to futz with 00.44.38 Join robertd1 [0] (~root@186-90-12-124.genericrev.cantv.net) 00.44.55 # or put it on ebay as not working for parts i think you might get something out of it 00.45.02 *** Saving seen data "./dancer.seen" 00.47.47 # no, that's not how you use ebay. you put it on ebay as "Untested, as-is". Or at least that's how most sellers seem to list things they know are broken... 00.48.05 # I'm all for being honest 00.49.13 # I am too, but I've gotten way too many "untested" things that were obviously know to be broken... now I just assume "untested" means "broken" and bid accordingly. 00.49.43 # s/know/known 00.50.07 # agreed or stolen since they don't have a power cord 00.52.18 Join Barbadus [0] (62e117a1@gateway/web/freenode/ip.98.225.23.161) 00.54.35 Quit Barbadus (Client Quit) 00.56.22 Quit Mihail (Quit: http://www.kiwiirc.com/ - A hand crafted IRC client) 00.59.22 Quit xorly (Ping timeout: 276 seconds) 01.00.42 Join alexweissman [0] (~alexweiss@149-160-186-148.dhcp-bl.indiana.edu) 01.01.11 Quit robertd1 (Ping timeout: 248 seconds) 01.06.31 Quit pamaury (Ping timeout: 276 seconds) 01.23.55 Quit MrZeus1 (Ping timeout: 255 seconds) 01.27.53 Quit semitones (Read error: Connection reset by peer) 01.35.07 Quit _mt_ (Read error: Connection reset by peer) 01.37.00 Quit skapazzo (Quit: leaving) 01.38.35 Join Senji_ [0] (~Senji@85.187.103.250) 01.39.35 Join StaticAmbience [0] (~Quassel@host86-157-17-68.range86-157.btcentralplus.com) 01.41.39 Quit Senji (Ping timeout: 240 seconds) 01.50.56 Join Senji [0] (~Senji@85.187.103.250) 01.52.51 Join idonob_ [0] (~Owner@50.67.32.65) 01.52.51 Quit Senji_ (Ping timeout: 255 seconds) 02.09.08 Quit idonob_ (Ping timeout: 240 seconds) 02.10.41 Join robertd1 [0] (~root@186-90-12-124.genericrev.cantv.net) 02.15.31 Join idonob_ [0] (~Owner@50.67.32.65) 02.22.51 Quit Senji (Ping timeout: 255 seconds) 02.26.24 Quit ZincAlloy (Quit: Leaving.) 02.27.09 Quit alexweissman (Remote host closed the connection) 02.28.16 Join ZincAlloy [0] (~Adium@2a02:8108:8b80:1700:6863:9077:2d20:f243) 02.30.54 Join alexweissman [0] (~alexweiss@2001:18e8:2:28b6:3c1b:3b70:e552:8189) 02.32.27 Quit ZincAlloy (Ping timeout: 255 seconds) 02.34.23 Quit idonob_ (Ping timeout: 245 seconds) 02.34.26 Quit alexweissman (Remote host closed the connection) 02.43.18 Join CustosL1men [0] (~CustosLim@unaffiliated/cust0slim3n) 02.45.05 *** Saving seen data "./dancer.seen" 03.04.28 Quit Moarc (Ping timeout: 240 seconds) 03.05.00 Join Moarc [0] (~chujko@a105.net128.okay.pl) 03.17.48 Join alexweissman [0] (~alexweiss@c-68-51-123-75.hsd1.in.comcast.net) 03.20.47 Quit gluytium (Ping timeout: 260 seconds) 03.26.19 # Bilgus_: yes, i got the chips few days ago. been busy. its in the queue of things to do! 03.29.46 Join gluytium [0] (U2FsdGVkX1@ma.sdf.org) 03.42.53 # has anyone disassembled the clip+ OF? 03.43.18 # pamaury had some ida files. 03.43.36 # i briefly looked at disassembly while stepping through the romboot but not enough to care about what it was doing 03.54.47 # I was just wondering if there was anything we were missing when it came to handling the memory on these devices 03.55.51 # for instance ecc 04.03.38 Join idonob_ [0] (~Owner@50.67.32.65) 04.17.26 Quit furrywolf (Quit: Reconnecting) 04.18.09 Quit idonob_ (Ping timeout: 256 seconds) 04.18.22 Join furrywolf [0] (~randyg@72-57-75-247.pools.spcsdns.net) 04.24.49 Quit fishbulb (Ping timeout: 255 seconds) 04.35.06 Quit rogeliodh (Ping timeout: 240 seconds) 04.36.45 Quit yosafbridge` (Quit: Leaving) 04.36.45 Join yosafbridge [0] (~yosafbrid@68.ip-149-56-14.net) 04.37.44 # INTERNAL_AS3525 0 /* embedded SD card */ why does this map to the base of the NAND_BASE_ADDRESS? 04.41.19 Join rogeliodh [0] (~rogeliodh@ec2-52-90-241-120.compute-1.amazonaws.com) 04.43.32 Quit gluytium (Ping timeout: 258 seconds) 04.44.21 # nm Advanced Peripheral Bus 04.45.09 *** Saving seen data "./dancer.seen" 04.54.16 # So we are using the pl180 to access the NAND on the AS3525? what implications does this have on the actual NAND are we just using defaults then? 05.00.26 Join gluytium [0] (U2FsdGVkX1@ma.sdf.org) 05.00.48 # funman I see from the forums you have some insight into this 05.05.26 Quit gluytium (Ping timeout: 252 seconds) 05.07.05 Quit robertd1 (Ping timeout: 252 seconds) 05.09.08 Join robertd1 [0] (~root@186-90-12-124.genericrev.cantv.net) 05.25.52 Quit derf (Ping timeout: 276 seconds) 05.27.29 Join derf [0] (~derf@static-108-18-126-14.washdc.fios.verizon.net) 05.34.28 Join gluytium [0] (U2FsdGVkX1@ma.sdf.org) 05.39.45 Quit gluytium (Ping timeout: 256 seconds) 05.42.50 # for anyone who wants a laugh... http://fw.bushytails.net/posusbadapterplugs01.jpg the plugs on my usb3.0 adapter card. yes, they're completely symmetrical, with the contact plate perfectly centered. yes, plugs go in just as easily in either direction. no, it doesn't work very well with the shield shorts all four contacts on the card together... 06.00.53 # bbl, wolfy bedtime 06.10.19 Quit robertd1 (Ping timeout: 240 seconds) 06.10.33 Join Rower [0] (husvagn@d83-183-134-99.cust.tele2.se) 06.11.08 # I guess they took their own approach to USB-C 06.12.03 # lol 06.15.39 Quit [7] (Ping timeout: 240 seconds) 06.16.11 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven) 06.25.10 Quit furrywolf (Ping timeout: 252 seconds) 06.30.07 Join Senji [0] (~Senji@85.187.103.250) 06.30.57 Join Strife1989 [0] (~quassel@adsl-98-80-191-24.mcn.bellsouth.net) 06.34.31 Quit Strife89 (Ping timeout: 248 seconds) 06.39.52 Join robertd1 [0] (~root@186-90-12-124.genericrev.cantv.net) 06.45.13 *** Saving seen data "./dancer.seen" 06.46.39 Quit robertd1 (Ping timeout: 240 seconds) 07.01.46 Join robertd1 [0] (~root@186-90-12-124.genericrev.cantv.net) 07.16.43 Quit robertd1 (Ping timeout: 255 seconds) 07.21.36 Join johnb3 [0] (~johnb2@p5B296E33.dip0.t-ipconnect.de) 07.22.12 # semitones: http://www.mediafire.com/file/8v1x35qtovpuu92/clppa_new.bin 07.22.51 # BTW i have 2 fuze v2, one variant 0, one variant 1 07.24.08 # semitones: you have to rename it to clppa.bin when you put it on the internal drive. 07.27.34 Quit Rower (Ping timeout: 240 seconds) 07.28.14 Join Rower [0] (husvagn@d83-183-134-99.cust.tele2.se) 07.29.09 Quit johnb3 (Ping timeout: 264 seconds) 07.31.58 Join robertd1 [0] (~root@186-90-12-124.genericrev.cantv.net) 07.42.20 # i think he might be able to short the 'recovery' pins and do what he needs but idk 07.49.14 Join JanC_ [0] (~janc@lugwv/member/JanC) 07.50.10 Quit JanC (Ping timeout: 240 seconds) 07.50.29 Nick JanC_ is now known as JanC (~janc@lugwv/member/JanC) 07.56.28 Quit robertd1 (Ping timeout: 252 seconds) 08.01.35 Quit naleo_ (Read error: Connection reset by peer) 08.03.16 Join robertd1 [0] (~root@186-90-12-124.genericrev.cantv.net) 08.07.51 Quit robertd1 (Ping timeout: 248 seconds) 08.29.46 Quit Rower (Ping timeout: 255 seconds) 08.30.12 Join Rower [0] (husvagn@d83-183-134-99.cust.tele2.se) 08.38.05 Join parchd [0] (~parchd@unaffiliated/parchd) 08.40.59 Join ender` [0] (krneki@foo.eternallybored.org) 08.45.17 *** Saving seen data "./dancer.seen" 08.50.19 Join xorly [0] (~xorly@ip-89-176-102-19.net.upcbroadband.cz) 09.08.15 Join petur [0] (~petur@91.183.48.77) 09.08.15 Quit petur (Changing host) 09.08.15 Join petur [0] (~petur@rockbox/developer/petur) 09.21.41 Join Hagen_ [0] (5db53e90@gateway/web/freenode/ip.93.181.62.144) 09.22.48 # Hallo, how can i get rockbox on my iPod Classic 6th Generation with my MacBook Pro? 09.29.39 Quit Hagen_ (Ping timeout: 260 seconds) 09.33.14 Join robertd1 [0] (~root@186-90-12-124.genericrev.cantv.net) 09.45.27 Quit Rower (Ping timeout: 248 seconds) 09.46.12 Join Rower [0] (husvagn@d83-183-134-99.cust.tele2.se) 09.46.59 Quit dys (Ping timeout: 240 seconds) 09.57.11 # Bilgus_: this is an empirical discovery 09.57.38 # afaiu sandisk replaced the nand controller with an sd controller since they didn't have to pay any royalties on it 10.00.57 Quit xorly (Ping timeout: 264 seconds) 10.01.24 Join elensil [0] (~edhelas@2001:1c02:1903:d800:fc05:338f:da98:b60e) 10.09.44 Join wodz [0] (~wodz@iwl138.internetdsl.tpnet.pl) 10.16.47 Quit petur (Read error: Connection reset by peer) 10.19.34 Join petur [0] (~petur@rockbox/developer/petur) 10.25.22 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 10.38.03 Join dys [0] (~dys@2003:5b:203b:100:6af7:28ff:fe06:801) 10.45.18 *** Saving seen data "./dancer.seen" 10.54.19 Quit robertd1 (Ping timeout: 240 seconds) 10.54.57 Quit fs-bluebot_ (Ping timeout: 264 seconds) 10.55.47 Join robertd1 [0] (~root@186-90-12-124.genericrev.cantv.net) 10.56.34 Quit bluebrother (Ping timeout: 240 seconds) 10.58.19 Join bluebrother [0] (~dom@rockbox/developer/bluebrother) 10.58.25 Quit Rower (Read error: Connection reset by peer) 10.59.21 Join Rower [0] (husvagn@d83-183-134-99.cust.tele2.se) 11.08.42 Join fs-bluebot [0] (~fs-bluebo@xd9baf795.dyn.telefonica.de) 11.20.44 Quit Guest44936 (Quit: Page closed) 11.20.49 Quit pamaury (Remote host closed the connection) 11.24.27 Quit robertd1 (Read error: No route to host) 12.17.27 Quit Rower (Ping timeout: 248 seconds) 12.17.36 Join Rower [0] (husvagn@d83-183-134-99.cust.tele2.se) 12.18.23 # funman: thats ok i have working clips as well. tapping some of the nand signals and seeing if they look like, well, nand accesses is also on todo list. 12.18.25 Join robertd1 [0] (~root@186-90-12-124.genericrev.cantv.net) 12.18.34 Join ZincAlloy [0] (~Adium@2a02:8108:8b80:1700:90f9:202e:30e5:cb2a) 12.41.29 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 12.45.20 *** Saving seen data "./dancer.seen" 13.02.29 Join mutnai [0] (6db90a3e@gateway/web/freenode/ip.109.185.10.62) 13.07.56 Join pamaury_ [0] (~quassel@wks-50-63.mpi-sws.org) 13.18.19 Quit pamaury (Ping timeout: 240 seconds) 13.22.22 Quit Moarc (Quit: i znowu NADMUCHAŁ BALONA) 13.23.14 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 13.26.57 Join Moarc [0] (~chujko@a105.net128.okay.pl) 13.30.32 # pamaury: How far are you with X1 port? 13.31.09 Quit Moarc (Ping timeout: 240 seconds) 13.33.12 Quit paulk-collins (Quit: Leaving) 13.33.57 Join Moarc [0] (~chujko@a105.net128.okay.pl) 13.41.26 # I haven't touched it in a month, not enough time. I have the bootloader running last time I checked but no drivers so it's kind of useless right now 13.41.48 # wodz: ^ 13.42.22 # pamaury_: Can I help with RE somehow? 13.42.40 # pamaury_: or sony is the priority now? 13.43.10 # at the moment not really, I just need to sit down and write the drivers. If you have timne to investigate the audio issue on Sony's that would helpful. Mostly try aplay 13.43.48 # Ideally, I would like to fix the audio issue on Sony's very very soon, then commit the port, and then people/me can incrementally improve it 13.44.10 # so I can work on the X1 ;) 13.45.30 # strategically, it makes more sense right now to make the Sony port working to have some feedback/users, rather then two ports that are not finished :) 13.45.59 Quit pamaury (Ping timeout: 248 seconds) 13.46.02 # pamaury_: I'd need to know how can I safely play with OF on sony 13.46.21 # wodz: don't touch the bootloader and you'll be fine 13.46.50 # if you wan to touch the bootloader, just don't touch mknwzboot and you'll be fine 13.47.38 # I think with mknwzboot now, you can't brick it unless you change the install script in mknwzboot. 13.47.45 # pamaury_: Suppose I have 'virgin' device - how do I run something on it (*safely*). Some script or something to explore it? 13.48.25 # ah good question. I have some uncommited code to add this option to the debug menu of the bootloader: you get a choice between running the service menu or an arbitrary script at the root of the device 13.48.37 # this should make it super easy to run arbitrary script 13.48.42 # I'll push it tonight 13.49.12 # (in any case you need to install the bootloader) 13.50.24 # pamaury_: Ok, then I'll install bootloader once I find some free time. 13.51.26 # wodz: wait until tonight, so I push this "run a script" option. And then yes, you install it once and you can play with it. 13.51.26 # Otherwise there is another obvious option: just replace /.rockbox/rockbox.sony by your favorite script 13.51.42 # but it has some non-obvious drawbacks so I don't recommend it 13.52.09 # I won't have time tonight so no problem 13.52.18 # ok :) 13.54.16 # * Bilgus_ wonders if we can enable ECC, if it would even make a difference, and HTH do we verify if it is?? 13.55.09 # HTH? 13.55.25 Join JanC_ [0] (~janc@lugwv/member/JanC) 13.56.04 Quit JanC (Ping timeout: 240 seconds) 13.56.40 Nick JanC_ is now known as JanC (~janc@lugwv/member/JanC) 14.02.09 # hown the hell 14.02.16 # how* 14.03.53 # enable ECC on what ? 14.04.10 # I assume the clip+ is still using that NAND controller even if we are accessing it by alternate means I'd like set up the controller 14.05.02 # Bilgus_: If you refer to raw nand and sandisk - we have no control over *any* low level feature of sd<->nand bridge. Anyway there is no f*** way to run nand flash without some sort of error correction on - be it BCH or Hamming. ECC is far to weak 14.06.06 # Ill have to get into it later bbl 14.12.13 # I think this is kind of hopeless. Even if the SD controller somehow exposes vendor specific commands, we'll never find them. I think the best hope is you try the SCSI format command and hope that it completely recreates the FTL structure on the flash 14.19.43 # s/scsi/sd 14.45.24 *** Saving seen data "./dancer.seen" 14.50.44 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 14.51.30 Join JanC_ [0] (~janc@lugwv/member/JanC) 14.51.40 # pamaury_: I am looking a bit on v4l2 radio interface. How rockbox scan actually? v4l2_radio_set() with RADIO_SCAN_FREQUENCY should return true if setting to such freq gives some signal or what? v4l2 uses VIDIOC_S_HW_FREQ_SEEK for that but it is higher level. You ask driver to star seeking up/down next station basically 14.52.39 Quit JanC (Ping timeout: 240 seconds) 14.52.45 Nick JanC_ is now known as JanC (~janc@lugwv/member/JanC) 14.53.22 # wodz: rockbox has two seeking more iirc: tuning ("set this frequency") and scanning ("start scanning all frequencies until you find a station") 14.53.26 # *mode 14.54.20 # actually maybe not 14.54.22 # pamaury: reading rockbox si4700.c I doubt that 14.55.06 # pamaury: The difference seems to be that RADIO_SCAN_FREQUENCY returns bool if it succeeded to find station at requested frequency 14.55.09 # there was some discussion about doing that because scanning is hardware dependent but actually scanning is now done by trying each frequency and asking the driver if it is tuned 14.56.14 # well this can be done as well with v4l2 - simply set freq and check RSSI 14.56.15 # I expect v4l2 supports tuning to a particular frequency and getting rssi ? 14.56.23 # heh 14.56.27 # great mind think the same at the same time ;) 14.56.51 # It should the question how we set the threshold. v4l2 rssi is 0-65535 14.57.24 # ah, does that correctly to something physical ? Like 65535 encodes to high dB values and it's a linear scale ? 14.59.33 # higher = better 15.00.39 # Documentation doesn't impose any scale actually. 15.00.50 # Do we pass frequency in HZ? 15.01.04 # or kHz or something? 15.01.10 # pamaury: ^ 15.01.22 # I think Hz 15.05.13 Quit Moarc (Quit: i znowu NADMUCHAŁ BALONA) 15.05.39 # wodz: for RSSI, I see three possible hacks: 1) read driver code and see how RSSI is encoded 2) see if drivers exposes RSSI via /sysfs, 3) access tuner registers directly to get raw rssi 15.06.13 Quit mutnai (Quit: Page closed) 15.06.56 Join Moarc [0] (~chujko@a105.net128.okay.pl) 15.07.59 # pamaury: 2) and 3) are actually the same. 1) is hard as it seems __video_do_ictrl() called by sony's driver to take care of standard ioctls is compiled into kernel. 15.08.19 Join skapazzo [0] (~skapazzo@151.9.205.1) 15.09.43 # well 2 can be more generic if Sony exposes a RSSI for all its tuners whereas 3 is tuner specific. But I don't even know how many different tuners Sony uses 15.10.22 # I think the only way to find out is to experiment on device 15.17.00 Quit wodz (Ping timeout: 255 seconds) 15.18.54 # wodz (logs): looking at the /etc/rc.d/icx_driver file on A20 (so quite recent and I expect supports all possible configuration), the si470x is the only driver 15.19.36 # so I think we can safely assume for now that this is the only tuner used by Sony 15.31.49 # @wodz: so what you are telling me is everything dealing with the NAND is handled behind the scenes and we just have to write/read and forget? 15.32.51 Quit Rower (Ping timeout: 260 seconds) 15.33.55 Join Rower [0] (husvagn@d83-183-134-99.cust.tele2.se) 15.38.27 Join amayer [0] (~amayer@mail.weberadvertising.com) 15.42.21 # Bilgus_: on the amsv2 soc, there is only a SD interface for use by software (at least that's what rockbox uses). So if the soc is talking directly to a flashm there is some hidden sd<->flash bridge and rockbox has no control over it 15.46.02 # crazy 15.46.41 # I mean it's pretty much like the ZEN X-Fi3, which has a Phison bridge. Except in this case they seem to have embedded the bridge in the SOC 15.47.00 # those bridge usually don't come with any documentation 15.48.49 # Bilgus_: are you trying to change the flash of a clip+ ? 15.53.26 # well dongs is doing that AFAIK I was just trying to get up to speed on the mechinisms behind the scenes and wondering if there is anything we are doing that might be making these chips even less robust than they already are but that is an eventual goal yes. 15.54.05 # I'm sure this tree has already been barked up so to speak judging by the forums 15.56.32 # I think there were plenty of bad flash reported with the OF ? That's what I've heard 16.10.44 Join johnb3 [0] (~johnb2@p5B296E33.dip0.t-ipconnect.de) 16.11.41 Join rasferret [0] (~yaaic@tmo-119-1.customers.d1-online.com) 16.12.10 Quit rasferret (Client Quit) 16.15.42 Join furrywolf [0] (~randyg@184-194-117-112.pools.spcsdns.net) 16.19.32 Quit Rower (Ping timeout: 256 seconds) 16.19.46 Join Rower [0] (husvagn@d83-183-134-99.cust.tele2.se) 16.45.25 *** Saving seen data "./dancer.seen" 16.47.03 Join Senji_ [0] (~Senji@85.187.103.250) 16.49.29 Join mutnai [0] (6db91733@gateway/web/freenode/ip.109.185.23.51) 16.50.26 Quit Senji (Ping timeout: 260 seconds) 16.57.47 Join Senji [0] (~Senji@85.187.103.250) 16.58.02 Quit Senji (Read error: Connection reset by peer) 16.58.29 Join Senji [0] (~Senji@85.187.103.250) 17.00.09 Quit Senji_ (Ping timeout: 240 seconds) 17.02.06 Quit gevaerts (Ping timeout: 260 seconds) 17.02.41 Quit evilnick (Ping timeout: 260 seconds) 17.04.36 Join xorly [0] (~xorly@193.85.203.185) 17.12.19 Quit Moarc (Ping timeout: 240 seconds) 17.13.07 Join Moarc [0] (~chujko@a105.net128.okay.pl) 17.23.44 Join evilnick [0] (~evilnick@rockbox/staff/evilnick) 17.24.30 Join gevaerts [0] (~fg@rockbox/developer/gevaerts) 17.27.55 Quit johnb3 (Ping timeout: 252 seconds) 17.47.55 Quit petur (Quit: Connection reset by beer) 18.00.10 Join naleo [0] (~naleo@unaffiliated/naleo) 18.08.51 Quit elensil (Quit: Leaving.) 18.19.15 Quit pamaury (Remote host closed the connection) 18.20.09 Quit Rower (Ping timeout: 255 seconds) 18.20.17 Join Rower [0] (husvagn@d83-183-134-99.cust.tele2.se) 18.22.11 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 18.29.59 Quit pamaury_ (Remote host closed the connection) 18.34.28 Quit pamaury (Ping timeout: 240 seconds) 18.35.16 Join thomasjfox [0] (~thomasjfo@rockbox/developer/thomasjfox) 18.45.28 *** Saving seen data "./dancer.seen" 18.49.31 Join MrZeus1 [0] (~MrZeus@2a02:c7f:7025:ed00:199:db4f:dcd5:e640) 18.53.39 Join paulk-collins [0] (~paulk@gagarine.paulk.fr) 19.09.22 Join johnb3 [0] (~johnb2@p5B296E33.dip0.t-ipconnect.de) 19.11.21 Quit mutnai (Quit: Page closed) 19.14.01 Join lebellium [0] (~chatzilla@89-93-177-91.hfc.dyn.abo.bbox.fr) 19.17.30 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 19.23.51 Quit prof_wolfff (Ping timeout: 260 seconds) 19.35.47 Join prof_wolfff [0] (~prof_wolf@82.159.0.123.dyn.user.ono.com) 19.49.04 Quit parchd (Ping timeout: 276 seconds) 19.52.19 Quit dys (Ping timeout: 240 seconds) 19.59.52 Quit johnb3 (Quit: Nettalk6 - www.ntalk.de) 20.09.21 Quit xorly (Ping timeout: 260 seconds) 20.11.24 Join dys [0] (~dys@ip-109-44-1-74.web.vodafone.de) 20.16.46 Join edhelas [0] (~edhelas@145.133.43.230) 20.16.54 # hello :) 20.29.20 Join TheLemonMan [0] (~root@irssi/staff/TheLemonMan) 20.30.20 Join rela_ [0] (~x@p200300764D619E008161BCEB3243FC92.dip0.t-ipconnect.de) 20.31.28 Quit rela (Ping timeout: 245 seconds) 20.44.46 # jhMikeS: here ? 20.45.31 *** Saving seen data "./dancer.seen" 20.55.00 # pamaury: what is hwstub, I see that you're doing some work recently on it, does it also affect the iPod builts ? 20.57.47 # no 20.58.10 # it's a piece of code that we usually load in hardware recovery mode to experiment, we script it using lua 21.01.02 # ok thanks :) 21.25.34 Join rasferret [0] (~yaaic@x55b507a9.dyn.telefonica.de) 21.35.07 # any arm expert around ? 21.35.26 # * pamaury is confused by inconsistent arm documentation 21.41.07 Join mutnai [0] (6db91733@gateway/web/freenode/ip.109.185.23.51) 21.41.24 # pamaury: aye 21.41.31 # jhMikeS: ah the savior \o/ 21.41.41 # * jhMikeS is confused 21.41.57 # jhMikeS: I have this instruction: 21.41.57 # stm r1, {...., pc} 21.42.29 # some doc says it's ok, some says it's unpredictable, some it's implementation defined and pc can get instr pc + 8 or +12 21.43.04 # I've tried it on the fuze+ (arm926) and it seems to be PC+12 21.43.28 # I can handler +8 or +12 just fine, but I'd like to be sure this is not unpredictable 21.43.32 # *handler 21.44.00 # what's it for? 21.45.00 # in hwstub, to catch data aborts in read/writes 21.45.18 # I have a mecanism that looks like setjmp/longjmp 21.47.43 # it looks like you probably don't want stm with pc in the list 21.49.12 # I would really prefer to have it though ;) 21.49.46 # and also by curiousity, I'd like to know what is the correct answer 21.52.01 Quit cc___ (Quit: WeeChat 1.6) 21.52.15 # deprecated 21.53.11 Quit girafe (Ping timeout: 260 seconds) 21.55.45 Join petur [0] (~petur@78-23-23-252.access.telenet.be) 21.55.45 Quit petur (Changing host) 21.55.45 Join petur [0] (~petur@rockbox/developer/petur) 21.58.48 # ok 22.01.10 Quit michaelni (Read error: Connection reset by peer) 22.01.38 Join michaelni [0] (~michael@213-47-41-20.cable.dynamic.surfer.at) 22.03.00 # * pamaury rewrites the code differently 22.03.21 # that's always better than rewriting it the same 22.07.42 # jhMikeS: so basically the only reliable way of getting PC is something like "mov r0, pc" or an add/sub ? 22.30.19 Quit petur (Quit: Leaving) 22.31.13 Quit amayer (Quit: Leaving) 22.31.34 # jhMikeS: are you going to push g#1522 or is there still some discussion on this ? 22.31.35 # 3Gerrit review #1522 at http://gerrit.rockbox.org/r/1522 : 3AMS: Return ascodec to interrupt-based I2C2 driver by Michael Sevakis 22.33.10 # Updating my clip zip to the latest git build yields a rather interesting "incorrect cpu mode in mutex_lock (0x13 != 0x1F)" 22.33.31 # TheLemonMan: latest git does that on my fuze too 22.33.39 # on my clip+ too 22.33.41 # yes we know 22.33.45 # that's it, everyone could complain 22.33.47 # :D 22.33.47 # I mentioned it yesterday... I was told it was mihail's bug 22.34.08 Join amayer [0] (~amayer@mail.weberadvertising.com) 22.34.24 # it is 22.34.46 # pitchforks hear no reasons 22.35.33 # TheLemonMan: I downloaded the 1/20 build instead, for the testing I was doing. 22.37.13 Join girafe [0] (~girafe@LFbn-1-11729-221.w2-7.abo.wanadoo.fr) 22.37.44 # I wonder why it is in SWI mode though 22.38.48 # amsv2 runs IRQ in svc mode 22.39.12 # * pamaury realize that's a weird sentence 22.40.16 # immediately after entering IRQ, it switches to SVC and re-enables interrupts (so that interrupts can be nested) 22.40.53 # neat 22.45.33 *** Saving seen data "./dancer.seen" 22.46.56 # <__builtin> aha, I figured out an annoying bug 22.47.15 # <__builtin> SDL_image doesn't actually decode the images... it just calls a library function to do it 22.50.21 # any thoughts on the playlist navigation speed bug? 22.52.38 # what is this bug ? 22.53.25 # I have around 3900 tracks on my playlist. the further down you are in the playlist, the slower it scrolls, until the last 10% or so is essentially inaccessible, as acceleration has stopped working, and it takes several seconds to scroll down each line. 22.54.34 Join Mihail [0] (25d4b85c@gateway/web/cgi-irc/kiwiirc.com/ip.37.212.184.92) 22.54.54 # jhMikeS: I don't have problems with g#1522. If you also don't have problems - commit it. 22.54.55 # 3Gerrit review #1522 at http://gerrit.rockbox.org/r/1522 : 3AMS: Return ascodec to interrupt-based I2C2 driver by Michael Sevakis 22.55.31 # furrywolf: sounds like some quadratic loop reading the playlist from the beginning every time 22.55.40 # pamaury: quite possibly. 22.56.07 # * pamaury knows nothing about playlist 22.56.16 # * furrywolf knows even less 22.58.59 Quit jhMikeS (Ping timeout: 240 seconds) 22.59.26 # a quick look at playlist_viewer.c suggests that: playlist_viewer_ex() calls gui_synclist_draw() that calls playlist_callback_name() to get the name of each item to display, that calls playlist_buffer_get_track() with the track numbe 22.59.37 # I suspect playlist_buffer_get_track() does a linear scan of the playlist file 23.00.50 Quit thomasjfox (Quit: Konversation terminated!) 23.01.31 # there is this interesting comment: 23.01.31 # the name_buffer is probably too small to store enough 23.01.31 # titles to fill the screen, and preload data in the short 23.01.31 DBUG Enqueued KICK pamaury 23.01.31 # direction. 23.01.49 # arg, irc ate the first line: 23.01.49 # This really shouldn't happen. If this happens, then 23.02.11 # If this happens then scrolling performance will probably 23.02.11 # be quite low, but it's better then having Data Abort errors 23.02.30 Join jhMikeS [0] (~jethead71@d192-24-173-177.try.wideopenwest.com) 23.03.43 # Mihail: I tweaked it some more. 1) Locking cpu_boost correctly 2) alter the system init so it doesn't use threading stuff too early 23.03.58 Quit TheLemonMan (Quit: "It's now safe to turn off your computer.") 23.05.18 Ctcp Ignored 1 channel CTCP requests in 0 seconds at the last flood 23.05.18 # * jhMikeS wants to know if he should ditch core voltage readout or put it somewhere better than CPU Frequency 23.05.34 # also needs a patch not to pull more than 100ma until it either negotiates for 500ma or gives up and decides it's on a wall charger 23.06.30 # since I think that's why my player was annoying Mihail's code 23.06.43 # notably, it doesn't do it when connected to a 500ma port. 23.07.11 # furrywolf have you tried tweaking your scroll settings yet? 23.07.28 # furrywolf: does your host report over current ? 23.07.32 # no. it does not seem like the type of thing that would be a setting, but rather a bug or design issue. 23.07.49 # if it does not, it is unlikely to be the problem, in practice most USB hosts are very tolerant about the 100mA limit 23.08.36 # pamaury: no, but watching the adc screen shows vbus dropping to 4.2 and chg_in dropping to 4.1, which is below the charger setpoint of 4.2, and probably why charge current is dropping low enough to generate endofch interrupts. 23.09.30 # the two places on this laptop that I connected it to were a usb 2 pcmcia card, which only officially has 100ma ports, and a bus-powered hub... 23.09.37 # sounds more like a poor charge pump on the host side 23.09.54 # jhMikeS: probably better move get_cpu_voltage() to debug-as3525.c? 23.10.00 # probably the usb port cannot sustain 100mA at 5V and thus the voltage drops 23.10.06 # Well if you would please change the settings in Settings >General Settings> Display> Scrolling and see if the behavior changes so I have at least a chance to narrow it down 23.10.21 # Mihail: which screen in particular? 23.10.52 # pamaury, re your "I don't know" https://www.rockbox.org/irc/log-20170121#17:45:23, then I'm puzzled by you saying you 'don't understand how all of a sudden the problem now appears'. 23.11.06 # on boost as now 23.11.09 # which thing that has HAVE_ADJUSTABLE_CPU_VOLTAGE is also a AMS v1? 23.11.38 # Mihail: you're saying keep it there? 23.12.14 # pamaury: yes and no... it might be able to sustain 100ma just fine, but the charger is fixed at 200ma, plus load of the system itself. 23.12.26 # per usb spec, it shouldn't pull >100ma until negotiating for more 23.12.37 # it's probably pulling 250ma or more 23.12.55 # furrywolf: true, but you usually can't negotiate with a charger 23.12.58 # chrisjj: I don't see the problem 23.13.07 # no, so if it doesn't enumerate, crank it up full. :) 23.13.08 # chrisjj: (I mean your problem) 23.13.13 # pamaury: ISTM some change between the two versions has cause the problem. And the problem's appearance looks sudden only because none of the intermediate builds were tested on ZEN. 23.13.36 # furrywolf: in practice, it means you have to wait until you are enumerated, and that happens very quickly 23.13.55 # jhMikeS: keep on boost screen but move get_cpu_voltage() form system-as3525.c to debug-as3525.c 23.14.09 # Mihail: ah, okay 23.14.13 # My problem is your recent builds suffer from BSoPO on ZEN. 23.14.17 # also as soon at it will be enumerated, it will start to draw 250mA (or as much as it can) 23.14.47 # Bilgus_: which setting in there exactly? the first couple I poked at seem to be for scrolling long titles on the screen, not the user scrolling up and down on the playlist. 23.14.47 # pamary: Is this ZEN BSoPO the problem you say you don't see? 23.16.43 # chrisjj: I'm puzzled because 1) I don't know what's causing the power down, and 2) you tested lcd_fix, claims it work, tested the parent of lcd_fix, claims it doesn't work, but lcd fix cannot be related to the problem, also I sent you a new build of lcd_fix and you claim it doesn't work 23.16.48 # thus that's puzzling 23.17.20 # pamary: Is this ZEN BSoPO the problem you say you don't see? 23.17.36 # but, with the finding that jhMikeS discovered about frequency scaling, that could change everything 23.18.20 # No I don't see why you don't understand I find it puzzling :) 23.18.28 # Ah, got you. 23.18.45 # hrmm, it did something different now. scrolling failed and became really slow around track 3700 (of 3903), but after letting it sit a bit, then it scrolled faster. 23.19.10 # jhMikeS: are you sure that we really need mutex_lock in set_cpu_frequency()? AFAIK we shouldn't call set_cpu_frequency() directly, only though cpu_boost. 23.20.18 # Paged scrolling 23.20.34 # also, I have some mp3s that won't play. is it worth trying to figure out why? 23.20.49 # pamaury: Does this 'new build of lcd_fix' contain any other changes from the original? 23.20.59 # they get (ERR) prepended to the track name 23.21.08 # chrisjj: could you test the latest dev build ? 23.21.35 # Yes, but I'd first like to understand where we are. 23.21.36 # Mihail: it does need serialization, yes. I moved it up a level in a new patch 23.22.09 Quit rasferret (Quit: Yaaic - Yet another Android IRC client - http://www.yaaic.org) 23.22.22 # chrisjj: not that I am aware but evidence shows different apparently. Or the problem is more or less random 23.22.28 # Mihail: so, cpu_boost needs the serialization. I reconciled that between portal player and AMS. I just haven't pushed the patch yet 23.22.34 # gui_sync_list holds around >10000 items in my testing and somewhere less than 60000 but I suspect it is either paged scrolling accelerated scrolling causing a problem 23.23.00 # chrisjj: we discovered a very problematic bug related to frequency scaling this week-end, I'd like to know if this explains the problem or not 23.23.05 # So the new lcd_fix was built from the exact same sources as the old? 23.23.27 # the scrolling issue is... odd. now it only does it the first time I scroll past a certain spot in the playlist, after a reboot. 23.23.34 # chrisjj: as far I know yes 23.23.50 # if I wait 10 seconds after it starts doing it before I scroll down further, then it scrolls at normal speed. 23.24.30 # if I keep trying to force it to scroll, then it keeps being slow. 23.24.30 # lol 23.24.36 # furrywolf: are you playing music while doing this? 23.24.38 # yes 23.25.02 # pamaury: the original lcd_fix was 45697a0bf-161212 . What was the new lcd_fix? You didn't ID any as such upon issue. 23.25.03 # oh well, now that I figured out how to make it work, it's much less annoying. 23.25.06 # hmmm...maybe PCM is getting low and prioritizing the codec thread? 23.25.13 # does it do better with paged scrolling enabled? 23.25.19 # chrisjj: so I think that we need to 1) try latest dev build, see if it fixes the problem, and if it does not, 2) go back to a much ealier commit, make 200% sure it's good and bisect 23.25.44 # I'm not sure. paged scrolling was so bloody annoying than I turned it off. the worst part was the selection would be at a random spot on the screen after it scrolled. 23.25.55 # * furrywolf reboots and turns it on 23.26.03 # Sounds good. Still I'd like to know which two lcd_fix builds we're talking about. If only so I don't miss a flaw in the test setup. 23.26.48 # feat req: parameters for scrolling long titles automatically, and parameters for scrolling long screens based on user input, should be separate submenus. 23.27.46 # no, paged scrolling doesn't affect it. it still bogs down around track 3700. it's much faster overall, however. 23.27.50 # chrisjj: rockbox_zen_8e82839f_lcdfix == lcdfix if I've got my memory straight 23.28.18 # jhMikeS: in this case - why not add muxet_lock directly to cpu_boost()? 23.28.56 # I was working on a sync list that allows piecemeal loading of lists but its a pain in the ass to make the scrollbar touch scrolling work properly so it is on a back burner 23.28.58 # pamaury: OK, thanks - that fits. And which is 'the parent of lcd_fix'? 23.29.13 # chrisjj: 8e82839f as I recall 23.29.30 # Mihail: that's what I did but in a way that different target choose their own method. PP uses a spinlock. 23.29.54 # is there an option to eliminate the three spaces to the left of the index, to show more of the track title at once? 23.30.05 # ah, ok 23.30.12 Join [Saint] [0] (~sinner@rockbox/staff/saint) 23.30.30 Quit mutnai (Quit: Page closed) 23.30.47 # pamaury: 8e82839f is the same number you gave me for the new lcdfix. Surely the same build cannot be lcd_fix AND the parent of lcd_fix? 23.30.51 # furrywolf I suspect it is the algo for accelerated scrolling, did you say it still did it when not playing music as well? 23.31.16 # chrisjj: rockbox_zen_8e82839f_lcdfix is 8e82839f+lcdfix 23.31.28 # I take it you have icons turned off? 23.31.39 # it's acting like it's bogging down thinking about something, causing the accelerating scrolling to miss input. but that's just my guess based on how it feels. 23.31.53 # 8e82839f is parent of original lcdfix 23.32.05 # once I wait, then it scrolls normally until next time I reboot. is there some caching going on? 23.33.05 # hmm not in the sync list that I know of but it could be as far as the SD-Card is concerned 23.33.36 # oh, I see. the space to the left of the index is reserved for showing the little green musical note. is there a way to make the little green musical note a one-pixel vertical bar? :) 23.33.40 # and in that case I doubt it can be fixed 23.34.36 # and can you set the playlist font to a different font than the menus? 23.34.59 # also, I'm guessing font hinting isn't implemented? lol 23.35.06 # <[Saint]> Yes. But not trivially. 23.35.27 # <[Saint]> And no. 23.36.18 # <[Saint]> You can define fonts on a per-viewport and per-screen basis. 23.36.37 # <[Saint]> but this is goverened by the theme engine and has no front-end in userspace. 23.37.09 # <[Saint]> and, regarding icons...same thing. 23.37.38 # <[Saint]> that is also governed by the theme engine and can be adjusted, but again this has no front-end in userspace. 23.37.49 # I just have really long filenames, and want to minimize horizontal scrolling. 23.38.26 # "Cult of Luna & Julie Christmas - Mariner (2016) - 03 - The Wreck Of S.S. Needle.mp3" etc 23.38.40 # <[Saint]> you can disable automatic scrolling period, if you wish. 23.38.46 # pamary: OK, got you. FTR, the version in rockbox_zen_8e82839f_lcdfix.zip is 8e82839feM-170110. 23.39.00 # <[Saint]> also - wow, that file naming schema is nuts. 23.39.23 # pamaury: OK, got you. FTR, the version in rockbox_zen_8e82839f_lcdfix.zip is 8e82839feM-170110. 23.39.47 # no, manual scrolling, where I scroll right so I can see which track it is. heh. 23.39.47 # <__builtin> you can TAB-complete in most clients, ya' know? 23.40.07 # wb saint 23.40.10 # <[Saint]> why are your filenames so verbose? 23.40.23 # [Saint]: nuts? that was standard on a ftp server I was on waaaay back when, and I've kept it. 23.40.44 # because from looking at just the filename, you can tell the artist, album, etc. 23.41.12 # <[Saint]> it only really makes any sense if you have your files in the "shit everything into a single directory" organization scheme IMO. 23.41.21 # when you have tens of thousands of tracks in a playlist, looking at just the track name tells you about nothing. 23.41.39 # <[Saint]> If you have your media organized in a sane fashion that information is derived from the directory structure. 23.41.53 # chrisjj: yes I know 23.42.05 # I have nice directory structure too. that track is in "Cult of Luna/Cult of Luna & Julie Christmas - Mariner (2016)/" 23.42.10 # <[Saint]> "/music/artist/album/disk */**-track.ext" 23.42.42 # yeah, you do that, then when you can only see filenames, you have no idea what you're looking at, you can't sort the playlist in any sane fashion, etc. 23.42.47 # * __builtin has about 1 track, so no need for names :P 23.42.49 # <[Saint]> IMO there's absolutely no reason for a filename to be that information-dense. 23.43.28 # pamaury: OK... but I though you might not, since you didn't mention 8e82839feM-170110. 23.43.37 # I even have a script to magically fix tracks like you name them. :P 23.43.47 # <[Saint]> Or, at the very least, put the relevant information first. 23.43.52 # mv -v "03. The Wreck Of S.S. Needle.mp3" "Cult of Luna & Julie Christmas - Mariner (2016) - 03 - The Wreck Of S.S. Needle.mp3" 23.44.06 # <[Saint]> the first half of your filenames are functionally useless for most use cases. 23.44.10 # and __builtin's one track is a soundtrack from a video game 23.44.10 # (it fixes a lot of other things too... I like my script) 23.44.22 # chrisjj: 8e82839fe + lcdfix = 8e82839feM, I cherry picked the lcd code without commit 23.44.22 # <__builtin> Bilgus_: how did you know? 23.44.37 # lucky guess 23.45.36 # pamaury: I just now guessed that :) but thanks for the confirmation. 23.45.39 # <[Saint]> regarding viewing of playlists, I have a playlistviewer in my themes that scrapes that information from metadata personally. 23.46.23 # <[Saint]> I guess it's subjective but I see very little reason to ever have much more than the track number and track title in the filename. 23.46.26 # Testing ZEN latest fev build (28bf763-170121) now. 23.46.28 # chrisjj: I also had a look at the code for frequency scaling on stmp3700 and datasheet and there is a potential issue there. On the ZEN and ZEN Mozaic, memory frequency scaling is disabled. Thus it can happen than CPU runs at 64 MHz, VDD at 1.05V but EMI at 130MHz. That's find on STMP3780 because the EMI power ram is a separate VDDMEM, but on STMP3700 it is VDD. And the datasheet recommends a VDD of at least 1.2V at 130MHz. The current code is 23.46.28 # clearly breaking this 23.46.30 Quit edhelas (Ping timeout: 248 seconds) 23.46.38 # *ZEN and ZEN X-Fi 23.46.46 # *fine 23.46.52 # "09-sreaming_females-it's_not_fair.mp3" becomes "Screaming Females - Rose Mountain (2015) - 09 - It's Not Fair.mp3", etc. it not only re-structures the name, it fixes non-space space characters, lack of capitalization, bad punctuation (its will become It's, etc), and idiotic crap like filename#[[DoofusRippers9000]]#.mp3 23.46.54 # *power rail 23.47.16 # furrywolf you can set the scroll time real low I guess but that would get super annoying or you can hold the right key and make the whole damn list scroll 23.47.26 # yes, I've just been scrolling right. 23.47.51 # I guess I should finish my automatic name shortening code... I started adding a mode to my script to generate short names for sticking on portable devices. 23.47.52 # Pamaury: Funny that. Only a week after I was bugging you about DFS :) 23.48.32 # well it's a subtle different between STMP3700 and STMP3780 23.49.23 # <[Saint]> furrywolf: ...yeah, I dunno man, I just use MusicBrainz Picard for this as it does a much better job and does all of what you've stated and more automagically. 23.49.28 # I don't know if that explains it, but it's worth trying to change the VDD voltage at 64MHz on STMP3700 to not go below 1.2V and see if it makes a different 23.49.31 # *difference 23.49.33 # pamaury: And I wonder if this VDD issue fits with the fact I found most BSoPDs when trying to charge from empty battery. 23.49.45 # <[Saint]> I've used MusicBrainz Picard for the better part of a decade and never saw any reason to reinvent the wheel. 23.50.10 # chrisjj: possibly, I don't know 23.50.14 # heh, actually, I got my name-shortening mostly working... I forgot! lol 23.50.16 # cp -v "Cult of Luna & Julie Christmas - Mariner (2016) - 03 - The Wreck Of S.S. Needle.mp3" "/tmp/mp3/TheWreckOfS.S.Needle (Cult of Luna & Julie Christmas - Mariner (2016) - 03 - The Wreck Of S.S. Needle).mp3" 23.50.21 Quit Bilgus_ (Remote host closed the connection) 23.50.43 # it might be that the RAM is perfectly happy running at 130MHz @ 1.05V, or it might be that's crapping out randomly ^^ 23.51.05 # <[Saint]> furrywolf: Perhaps you should look into it. Seems like your solution revolves around the metadata or filename being correct to begin with. MusicBrainz Picard doesn't need any hinting from either filename or metadata to tag correctly. 23.51.24 # <[Saint]> It's perfectly capable of deriving that information from contect and audio signature. 23.51.30 # I ignore metadata entirely, because it's correct about 1% of the time. 23.51.53 Join Bilgus_ [0] (~Bilgus@gateway/tor-sasl/bilgus) 23.51.55 # the vast majority of people ripping cds do not bother setting it correctly, if at all. 23.51.55 # <[Saint]> ...because you don't use a sane distributed tagger. 23.51.58 # <[Saint]> that's why. ;) 23.52.35 # <[Saint]> Give it a look before you knock it my man. My entire point is that what it's tagged with initially isn't relevant. 23.53.01 # <[Saint]> It pulls from record industry DBs and a metric shitload of other verifiable sources. 23.53.12 # <[Saint]> Relying on humans is a mugs game, indeed. So I don't. 23.53.35 # also, my script is smart enough to take track lists from various sources (just about any website that will list the tracks in the correct order) and match it to the filenames, using fuzzy matching, for when you get an album where the idiot ripping it didn't even bother with track numbers... 23.54.09 # <[Saint]> Seems like you've just reinvented the wheel and made about 1/8th of a MusicBrainz Picard. 23.54.36 # it will also rename tracks to an ultra-short format, which I wrote for the display on my work van's head unit... "ThWrckOfS.S.Ndl" 23.54.55 # I never finished selection of output format though... I should finish it. 23.55.28 # <[Saint]> MBP can also do that, based on user defined rules with regex parsing. 23.55.35 # <[Saint]> You really should give it a look... 23.55.59 # it looks annoyingly gui 23.56.23 # <[Saint]> Ah. You're one of those. I see. 23.56.55 # <[Saint]> Personally I don't ming a GUI driven solution as long as it Just Works (TM). 23.58.27 # also, mine has humorous messages, like "Please kill the person who put the numbers at the end of the filename." (yes, it automatically recognizes and fixes that, too)