01:00 |
01:08:06 | *** | Saving seen data "./dancer.seen" |
01:29:32 | | Join ufdm_ [0] (~ufdm@c-73-164-63-214.hsd1.mn.comcast.net) |
01:32:36 | | Quit ufdm (Ping timeout: 272 seconds) |
01:47:26 | | Quit pixelma (Quit: .) |
01:47:26 | | Quit amiconn (Quit: http://quassel-irc.org - Chat comfortably. Anywhere.) |
01:49:56 | | Join pixelma [0] (marianne@p2e55b6bb.dip0.t-ipconnect.de) |
01:49:56 | | Join amiconn [0] (jens@p2e55b6bb.dip0.t-ipconnect.de) |
02:00 |
02:14:18 | | Join desowin [0] (~linux@078088109026.wroclaw.vectranet.pl) |
03:00 |
03:08:07 | *** | Saving seen data "./dancer.seen" |
04:00 |
04:24:31 | | Quit j-r (Ping timeout: 246 seconds) |
04:36:41 | | Quit akaWolf (Ping timeout: 252 seconds) |
05:00 |
05:08:09 | *** | Saving seen data "./dancer.seen" |
05:15:54 | | Quit yosafbridge (Quit: Leaving) |
05:16:38 | | Join akaWolf [0] (~akaWolf@akawolf.org) |
05:16:39 | | Join yosafbridge [0] (~yosafbrid@static.38.6.217.95.clients.your-server.de) |
05:24:19 | | Join j-r [0] (~j-r@p2003000621560733404207fffefd0a65.dip0.t-ipconnect.de) |
05:24:40 | rb-bluebot | Build Server message: New build round started. Revision 60e2cd6de9, 297 builds, 8 clients. |
05:37:21 | rb-bluebot | Build Server message: Build round completed after 760 seconds. |
05:37:23 | rb-bluebot | Build Server message: Revision 60e2cd6de9 result: All green |
07:00 |
07:04:05 | | Quit akaWolf (Ping timeout: 255 seconds) |
07:08:12 | *** | Saving seen data "./dancer.seen" |
07:34:01 | | Join akaWolf [0] (~akaWolf@akawolf.org) |
07:49:54 | | Join massiveH [0] (~massiveH@ool-18e4e82f.dyn.optonline.net) |
08:00 |
08:00:19 | speachy | well, LTO on the X3 did introduce at least one regression −− rolo broke. |
08:03:09 | braewoods | speachy: which would imply it also broke the BL, no? |
08:03:48 | braewoods | in any case it sounds like LTO has a lot to work before we could turn it on |
08:05:11 | speachy | Theres' going to be a long tail of regressions. |
08:05:30 | braewoods | so why do all this then? |
08:06:04 | braewoods | some of the LTO issues may be resolved or changed by newer toolchain |
08:06:05 | speachy | smaller binaries and generally better performance/optimization |
08:06:38 | braewoods | should we aim for a new toolchain after the next release? |
08:06:48 | speachy | even modern GCC 11 with sim builds doesn't LTO properly yet. |
08:07:08 | braewoods | huh. i'd expect hosted builds to work the the easiest |
08:07:32 | braewoods | i never touched LTO since it seemed to cause way more issues than it solved |
08:07:56 | speachy | I've been involved in several embedded projects that simply wouldn't have fit without LTO. |
08:08:23 | braewoods | ah. well i've mainly developed for Linux so that's why i think differently. |
08:09:08 | braewoods | i have more resources so i want to side with maturity a lot more; i don't have patience to workout random issues due to LTO issues. |
08:09:44 | speachy | most of the LTO "issues" are ultimately due to bugs (or at least a reliance upon undefined behavior) in the code. |
08:09:52 | braewoods | speachy: btw i found an mpio hd300 and i bought it |
08:10:01 | braewoods | i'll be able to test it |
08:10:20 | braewoods | once it arrives |
08:10:21 | speachy | eg definitions that don't match, namespace collisions |
08:10:31 | braewoods | we don't have namespaces so |
08:10:47 | braewoods | but we can still have prototype mismatches |
08:10:50 | braewoods | or so |
08:10:53 | speachy | and being able to trace code execution across "modules" allows for a lot of other issues to be uncovered. |
08:11:01 | speachy | namespace meaing "compilation unit" |
08:11:05 | braewoods | oh. |
08:11:07 | braewoods | TUs. |
08:11:25 | braewoods | C standard calls those translation units |
08:11:54 | braewoods | so you're saying we've got a lot of code to fix before we can use LTO. |
08:13:19 | braewoods | i may be engaging in some UB just to get my code to work... :| |
08:13:26 | braewoods | mostly with casts |
08:13:57 | braewoods | sometimes i discard const because i know the original data is truly not const and i just want it to stop warning |
08:14:06 | MarcAndersen | I'm sorry to say that my connect has still not powered on. I think this thing is totaly dead. |
08:14:10 | braewoods | when dealing with function parameters that want a "const char**" |
08:14:29 | braewoods | or rather, fake it being const. the originaly is char**. |
08:14:56 | braewoods | MarcAndersen: sorry to hear that. |
08:15:14 | braewoods | if you lived in the US i'd send you one of my extra rockbox units. :| |
08:16:05 | MarcAndersen | I got this one on ebay from us. |
08:17:08 | braewoods | ah |
08:17:28 | braewoods | i mostly own non-ipod hardware |
08:17:52 | MarcAndersen | I will just let it be connected and see if it magicly turns on some day, but I wish there was a way for it to ignore the battery and turn on by the help of usb power and then charge. All of my laptops can do that when I connect them to the mains. |
08:17:55 | braewoods | i have 4 gigabeat S units i've acquired by watching for deals on ebay; i've repaired and upgraded the 3 i could open |
08:18:31 | braewoods | if that's what you'd like, i suggest the gigabeat ports. both can be powered from either direct DC power or battery |
08:18:49 | braewoods | Gigabeat S and Gigabeat F (or X if you're lucky enough to find one) |
08:18:59 | speachy | MarcAndersen: alas, ultimately it depends on how the power supply was designed. :/ |
08:19:21 | braewoods | the gigabeats have a battery switch too even |
08:19:24 | MarcAndersen | Maybe that's what i should look after, thanks. |
08:19:54 | braewoods | i'll be doing an upgrade of a gigabeat F later this week |
08:20:14 | braewoods | You can get some good deals on these F series from time to time. |
08:20:33 | braewoods | $30-50, compared to the $100+ some idiots want. |
08:20:52 | braewoods | the S series is pretty rare to find but I have found 2 for $50 or less in the last few months. |
08:21:01 | MarcAndersen | Oh, I also have a small problem with my nano 1g. It takes a very long time to start transfering files and to delete them, like it needs to do it 2 times. Is that something you can confirm? |
08:21:21 | speachy | using the latest builds? |
08:21:32 | speachy | I'm not aware aof any specific problems with the nanos |
08:21:46 | MarcAndersen | Oh, sorry, maybe it's on 3.15. |
08:22:01 | MarcAndersen | I will try updating if it is. |
08:22:19 | speachy | there have been a ton of general improvements but the nanos were unaffected by the iflash woes of their spinning rust bretherens |
08:23:28 | braewoods | seems the entire EU ebay lacks any gigabeats |
08:23:29 | | Quit ufdm_ (Quit: Leaving) |
08:23:32 | braewoods | all US it seems |
08:23:40 | | Join ufdm [0] (~ufdm@c-73-164-63-214.hsd1.mn.comcast.net) |
08:23:52 | speachy | but since the nano doesn't have replaceable internal storage their days are all numbered. |
08:23:57 | desowin | Sansa Connect OF bootloader won't let you through unless the HDQ reports that battery is fine |
08:25:05 | braewoods | MarcAndersen: unfortunately most of the options i've mentioned are mainly a good idea if you can get them repaired and upgraded. you'd probably need a sighted person to do that first. |
08:26:50 | braewoods | in any case i'd be willing to do that at some point if i know what you require |
08:28:57 | desowin | MarcAndersen: if you don't mind shipping to Poland I can check if the battery can be recovered |
08:30:04 | MarcAndersen | That would be fine. Should we make a private chat or something? |
08:30:21 | braewoods | yes |
08:30:25 | speachy | MarcAndersen: one question −− was there a reason you chose the Connect specifically? |
08:30:45 | braewoods | we don't need to know the details and best it doesn't show up in the logs |
08:30:46 | MarcAndersen | Yes, to test the new port mostly. |
08:31:46 | speachy | ah, okay, so you weren't after it due to some physical consideration. (Some hardware is definitely better than others for visually-impaired folks) |
08:31:57 | braewoods | of which i'm no expert on |
08:32:10 | speachy | we definitely appreciate your willingness to suffer... |
08:32:16 | MarcAndersen | /msgnickserv identify marc7002 |
08:32:20 | braewoods | but anything touch based is probably a challenge |
08:32:23 | MarcAndersen | sorry sorry sorry |
08:32:33 | braewoods | MarcAndersen: may want to change your password now |
08:32:36 | MarcAndersen | can you delete that from the log? |
08:32:39 | braewoods | nope |
08:32:45 | braewoods | it's automated to the web site |
08:32:51 | MarcAndersen | I will change my pass |
08:32:52 | speachy | MarcAndersen: yes but not until it rotates. |
08:33:05 | braewoods | well speachy can |
08:33:09 | braewoods | i don't have access to logs :P |
08:33:15 | speachy | (and of course who knows how many eyeballs and/or other bots have seen it) |
08:37:49 | | Quit massiveH (Quit: Leaving) |
09:00 |
09:02:35 | _bilgus | MarcAndersen, when a lithium ion battery goes too low it can actually flip polarity and when you go to charge it it is now backwards and has a melt down |
09:03:04 | _bilgus | therefore they put protection circuits to disconnect when its too low |
09:03:17 | MarcAndersen | Oh |
09:04:13 | _bilgus | by taking 2 standard AA batteries in series to make 3v you can get some power in it safely-ish |
09:06:39 | _bilgus | I usually have a 3.3v supply with a resistor and let it charge for a bit on a metal plate (don't make it encased in a pressure vessel) |
09:07:37 | _bilgus | I've yet to have one blow but you do need to make sure its not getting hot or expanding |
09:08:00 | _bilgus | as for results IDK more good than bad |
09:08:14 | *** | Saving seen data "./dancer.seen" |
09:09:42 | _bilgus | oddly the worst are cordless tool batteries - one pack every cell was .001 v I didn't even try it |
09:19:48 | _bilgus | MarcAndersen, I kinda searched around here is a guide that fits pretty well with my method https://www.instructables.com/Recovering-Lithium-Ion-Batteries/ |
09:20:17 | _bilgus | they use a dedicated charger which is probably a good idea |
09:21:03 | MarcAndersen | _bilgus: I will check it out |
09:21:55 | _bilgus | I've charged a cell battery on a dedicated liion charger for 18650s its not rocket surgery |
09:22:34 | _bilgus | you just need to be aware of the potential for damage to your surroundings and do it in an appropriate area |
09:23:08 | | Quit aquijoule__ (Remote host closed the connection) |
09:23:33 | | Join aquijoule__ [0] (~richbridg@213-225-7-126.nat.highway.a1.net) |
09:24:36 | _bilgus | its usually just a bit too low, 2.6v or something just shy of allowing it to work you get some current in there and they usually start working |
09:25:04 | braewoods | _bilgus: wouldn't a CC/CV power supply work just as well? |
09:25:11 | braewoods | assuming you set it correctly |
09:25:20 | _bilgus | sure a little benchtop supply |
09:25:21 | MarcAndersen | I'm going to send my connect to desowin |
09:26:33 | | Quit j-r (Ping timeout: 252 seconds) |
09:26:33 | braewoods | MarcAndersen: if you end up needing a repaired rockbox unit, let me know. |
09:26:50 | braewoods | i usually repair the ones i buy to use for development as i need stable hardware to work with |
09:28:59 | _bilgus | like I said I use a beefy 3v3 supply and a large-ish resistor 10k? to great effect |
09:29:18 | | Quit pablocastellanos (Ping timeout: 252 seconds) |
09:29:20 | braewoods | _bilgus: resistor to control current flow? |
09:29:30 | _bilgus | yep |
09:29:44 | _bilgus | just a little trickle |
09:29:44 | | Join j-r [0] (~j-r@p2003000621560733404207fffefd0a65.dip0.t-ipconnect.de) |
09:29:45 | braewoods | afaik batteries generally have nothing to stop it |
09:29:51 | braewoods | so they need external help |
09:30:10 | braewoods | that's usually an issue mainly in charging |
09:30:50 | _bilgus | the other thing is that it keeps the temp low |
09:31:14 | braewoods | true. most simple lithium packs lack temperature sensing |
09:32:04 | _bilgus | you'd be bypassing it anyways I'm talking of keeping the heat low to keep from melt down |
09:32:19 | braewoods | thermal runaway |
09:32:46 | braewoods | under normal operation you'd not let it get that low |
09:33:17 | _bilgus | yeah Ive yet to actually do that on purpose to a liion battery the videos were enough of a warning |
09:34:09 | braewoods | i've had devices use a very low current to charge a dead battery for awhile |
09:34:17 | braewoods | and then it spikes |
09:34:20 | braewoods | after awhile |
09:34:29 | _bilgus | yeah thats a safety circuit |
09:34:37 | braewoods | like 0.1 or 0.2 A from a 5V input |
09:35:03 | braewoods | i usually use a dc watt meter to monitor the charging current |
09:35:19 | braewoods | that tells me a lot about how it is progressing |
09:35:29 | _bilgus | those battery chargers are a lot smarter than the lead acid 'smart' chargers ever were |
09:35:55 | braewoods | SLA chargers are never disconnected automatically iirc |
09:36:08 | _bilgus | but they have to be liion is a lot of unstable energy in a small package |
09:36:35 | braewoods | what about lifepo4? |
09:36:36 | | Quit advcomp2019 (Ping timeout: 252 seconds) |
09:36:43 | braewoods | isn't it safer? |
09:36:51 | _bilgus | IDK I haven't ran across any cells yet |
09:37:07 | braewoods | ah. i'm planning to build a lifepo4 pack |
09:37:10 | braewoods | i have the cells already |
09:37:12 | braewoods | they're 26650 |
09:37:58 | _bilgus | oh? are they the same voltage range or just don't get full capacity if used in non life devices? |
09:38:00 | braewoods | their voltage range is different so you need a different type of BMS and charger for them |
09:38:06 | _bilgus | ah |
09:38:11 | braewoods | their max voltag is around 3.6 or 3.7V |
09:38:31 | braewoods | some people use 4S setup to replace SLA packs |
09:38:38 | _bilgus | hmm then maybe using the same dimensions as existing liion is BAD juju |
09:38:56 | braewoods | they're 26650 for a reason |
09:39:11 | braewoods | those are larger and primarily used by lifepo4 cells |
09:39:26 | braewoods | there are 18650 lifepo4 cells but |
09:39:27 | _bilgus | have 3 flashlights that say otherwise |
09:39:30 | braewoods | they're pretty rare |
09:39:36 | braewoods | oh? |
09:39:40 | braewoods | strange |
09:39:43 | _bilgus | no 21700s are rare |
09:40:31 | braewoods | i'm planning a build using those 21 cell boxes they sell from china or so |
09:40:45 | _bilgus | ah 21650 not 26650 I think |
09:40:47 | braewoods | they can fit 21 18650s in a cell holder or 10 26650s |
09:40:56 | _bilgus | let me look |
09:41:11 | _bilgus | no 26650 |
09:41:23 | | Quit j-r (Ping timeout: 252 seconds) |
09:41:30 | braewoods | if you're interested, i think the daly bms is the best overall option that i could find |
09:41:55 | braewoods | you can order them with thermistors too |
09:41:55 | | Join j-r [0] (~j-r@p5df2ecee.dip0.t-ipconnect.de) |
09:42:17 | braewoods | it was the closest i could find for a "brand name" bms from china |
09:42:49 | braewoods | _bilgus: you can also buy those headway lifepo4 cells |
09:42:50 | _bilgus | Ive been toying with making a liion pack for my UPS esp after speachys 'experiments' with LA |
09:42:58 | braewoods | no soldering |
09:43:11 | braewoods | or welding |
09:43:19 | braewoods | the cells use screw on caps |
09:43:21 | _bilgus | soldering is fine I need to make a spot welder anyway |
09:43:33 | _bilgus | ah like those caps of old |
09:43:51 | braewoods | which seems fine but those cells are expensive |
09:43:56 | braewoods | $8+ a pop |
09:44:11 | speachy | my wet-cell failures were more due to a lack of maintainene than anything else. I didn't keep the cells sufficiently, um, wet. |
09:44:34 | _bilgus | our equipment at work does the same |
09:45:07 | braewoods | lifepo4 is the only real option for a drop in replacement |
09:45:14 | braewoods | since it has a compatible voltage range |
09:45:20 | braewoods | in 4S |
09:45:21 | speachy | but LiFePO4 is $$$$ and requires active regulation at the battery or completely different charging circuits. I wouldn't trust one with a charger designed for SLAs |
09:45:39 | braewoods | i've read people do that though speachy. |
09:45:50 | braewoods | as long as the UPS only does regular CC/CV |
09:45:53 | _bilgus | no if anything I figure I can use a circuit to fake the onboard |
09:45:53 | braewoods | it should be ok |
09:46:15 | speachy | when you're talking 100s of amp-hours that's a lot of boom should something go wrong. |
09:46:17 | braewoods | but i wouldn't attempt it without understanding how the UPS charger works |
09:47:08 | _bilgus | a battery explosion is not a fun experience |
09:47:40 | speachy | I think the solar charge controller I have in my camper can hendle LiFePO4; it has different charge modes for wet cell, SLA, and Li |
09:47:40 | braewoods | _bilgus: in any case, i'd check out the daly BMS store on aliexpress if you need a BMS for a custom lifepo4 or lithium pack. |
09:47:41 | _bilgus | I was deaf for a day or two when one exploded in a bulldozer I was attempting to start |
09:48:16 | braewoods | i use primarily the single port options |
09:48:24 | braewoods | so i can use them in a regular battery case |
09:48:38 | braewoods | where the same port is used for charge and discharge |
09:49:11 | braewoods | just need to ask the seller to enable their thermistor part for sale if you want to order one with an optional thermistor |
09:49:44 | braewoods | it's soldered to the BMS so it has to requested prior to shipment |
09:49:50 | speachy | before I was using wet cells I was using very oversized SLAs, but got sick of paying through the nose every couple of years to replace 'em. Gotta love Florida's power quality. |
09:50:14 | speachy | if I were do it again I'd move to golf cart batteries instead. they're designed for abuse. |
09:50:46 | braewoods | must be a large scale UPS |
09:50:54 | _bilgus | jesus guess florida has a lot of em |
09:50:57 | braewoods | most UPS i've used can't handle random SLAs |
09:50:59 | speachy | I'd sized it to handle a five hour outage. |
09:51:13 | braewoods | they have to fit a small profile |
09:51:23 | | Join pablocastellanos [0] (~pidgin@user/pablocastellanos) |
09:51:28 | speachy | this one couldn't; I rigged up custom cables. sat on the floor under my server "table" :D |
09:51:51 | braewoods | most UPS can't be used with external batteries that i can tell |
09:51:54 | braewoods | :D |
09:52:08 | braewoods | what voltages do these higher end UPS use? |
09:52:11 | braewoods | 12V still? |
09:52:29 | braewoods | i would expect for the kind of loads you have that they'd use higher voltage to reduce the wiring costs |
09:52:34 | speachy | one of my printers here has visible acid damage from the more recent BOOM |
09:53:27 | speachy | 1300VA or so tends to be 24V. higher-end stuff (>2KVA) is often 48V. |
09:53:34 | _bilgus | I guess the other option is a vented cabinet |
09:53:40 | _bilgus | vented to outdoors |
09:53:45 | braewoods | _bilgus: one thing to note if you try to build a lithium pack replacement. it may have to be external since many UPS expect 12V range. |
09:53:57 | braewoods | and |
09:54:07 | braewoods | lifepo4 doesn't handle high discharge current well |
09:54:16 | braewoods | my cells are only rated for about 10A each |
09:54:33 | braewoods | 500W ups easily needs like |
09:54:38 | braewoods | 40A or so |
09:54:55 | braewoods | SLAs can handle that |
09:55:19 | braewoods | you'd need a larger lifepo4 to replace it due to discharge current |
09:55:21 | braewoods | ironically |
09:55:26 | _bilgus | I have surplus shipboard UPSs from the 90s they are more like 15-20A @ 120 so 2000W |
09:55:33 | MarcAndersen | Maybe this is a stupid question, but does the gigabeats have touchscreens? |
09:55:43 | braewoods | MarcAndersen: no. neither do. |
09:56:07 | MarcAndersen | Ok. Maybe that's what I should look after next... |
09:56:19 | braewoods | MarcAndersen: Gigabeat S has a directional button pad below the screen. Same with the F. |
09:56:30 | braewoods | the rest are side buttons or switches |
09:56:37 | MarcAndersen | Which is most accessible? |
09:56:46 | braewoods | define accessible |
09:56:56 | MarcAndersen | I mean for the blind. |
09:57:11 | rb-bluebot | Build Server message: New build round started. Revision 8de163b8ae, 297 builds, 9 clients. |
09:57:12 | speachy | braewoods: "usable without being able to see where your fingers are" |
09:57:13 | braewoods | well, most of our targets don't use touch screens. |
09:57:16 | _bilgus | are the rockers alrady too hard to get? |
09:57:20 | braewoods | _bilgus: yep. |
09:57:47 | MarcAndersen | Is the best processor in the gigabeat s? |
09:58:02 | braewoods | MarcAndersen: probably the S. the F has a sunken in pad that can be hard to trigger consistently. |
09:58:09 | braewoods | bad news if you can't see well |
09:58:25 | _bilgus | see I think we should be looking at ease of replacemnt as well |
09:58:29 | braewoods | how much storage you need? |
09:58:38 | _bilgus | how easy is replacimg the battery or storage |
09:58:45 | speachy | MarcAndersen: IMO the best option for blind users is the original xDuoo X3. funky buttons that are very easy to tell apart by touch. |
09:58:47 | braewoods | the gigabeat S is pretty easy actually |
09:58:53 | speachy | and the crappy screen doesn't matter. :) |
09:59:12 | braewoods | for a sighted person to repair anyway |
09:59:27 | braewoods | i've finished repairing 3 gigabeat S to functional state |
09:59:40 | braewoods | upgraded their storage too |
09:59:48 | MarcAndersen | Do any of the gigabeats or xduoo have external storage? |
10:00 |
10:00:00 | braewoods | the gigabeat S has no external storage |
10:00:06 | braewoods | only the internal |
10:00:13 | braewoods | but it is replaceable |
10:00:13 | speachy | X3 has dual SD slots. no internal storage. |
10:00:24 | _bilgus | just saying already got burnt once with an older device one that is repairable would make that less terrible |
10:00:47 | _bilgus | IF you can get a new X# or new-ish |
10:00:53 | _bilgus | X3 |
10:00:58 | braewoods | the gigabeat S is a pretty beefy device for its age |
10:00:59 | speachy | the newer X3ii has a single SD slot, but not as accessible due to its hosted nature (bootloader is not accessible) |
10:01:16 | braewoods | i installed a 128GB SSD in all 3 of the ones i repaired |
10:01:19 | braewoods | and new batterie |
10:01:22 | braewoods | batteries |
10:01:23 | MarcAndersen | Does any of them have a built in speaker which works in rockbox? |
10:01:29 | braewoods | Sadly no. |
10:01:30 | _bilgus | doubtful |
10:01:35 | braewoods | most players need headphones |
10:01:58 | MarcAndersen | The connect has one, right? |
10:02:04 | braewoods | are there any rockbox players with built in speakers? |
10:02:08 | braewoods | no idea i'll look |
10:02:12 | MarcAndersen | the zen x-fi |
10:03:00 | MarcAndersen | I got that in 2009 and tested it during development in 2013. |
10:03:56 | braewoods | sansa connect has some holes on theback; it might support a speaker |
10:03:59 | braewoods | i'd ask desowin |
10:04:26 | MarcAndersen | But first I need to get it to start up... |
10:04:31 | braewoods | indeed |
10:04:55 | MarcAndersen | Stupid peace of crap |
10:05:15 | braewoods | the connect is not easy to repair from what i saw |
10:05:23 | braewoods | the battery has no aftermarket replacements |
10:05:40 | MarcAndersen | Maybe I should just drop sending it to desowin then? |
10:05:42 | speachy | there's always aliexpress |
10:06:05 | braewoods | speachy: really... i didn't see any. |
10:06:15 | braewoods | i had to import my gigabeat S batteries |
10:06:20 | speachy | well, yeah. |
10:06:47 | MarcAndersen | Maybe I should just throw it in the trash and get another model? |
10:06:50 | braewoods | MarcAndersen: up to you. |
10:07:04 | braewoods | MarcAndersen: that's just my take on it a a sighted person |
10:07:20 | MarcAndersen | Sure |
10:08:01 | rb-bluebot | Build Server message: Build round completed after 649 seconds. |
10:08:03 | rb-bluebot | Build Server message: Revision 8de163b8ae result: All green |
10:08:32 | desowin | Sansa Connect has built-in speaker |
10:08:40 | braewoods | huh. interesting. |
10:08:48 | braewoods | that's pretty rare to find. |
10:09:08 | desowin | it is mono, and OF (and Rockbox) switches to it when there are no headphones connected |
10:09:26 | | Join advcomp2019 [0] (~advcomp20@user/advcomp2019) |
10:09:28 | braewoods | are there any other ports with it? |
10:09:46 | desowin | MarcAndersen: it is up to you |
10:10:01 | speachy | oh! that reminds me. |
10:10:30 | speachy | desowin: https://www.rockbox.org/dl.cgi?bin=sansaconnect can you grab an appropraite voice file and make sure it's sane? |
10:11:50 | desowin | I would say the speaker is pretty bad. and I don't think you can use it to output something else than on the headphones |
10:12:13 | braewoods | MarcAndersen: the gigabeat S is still under development but i can send you one of the repaired units. it's basically done but still lacks rbutil integration, main reason it's not "stable". |
10:14:05 | MarcAndersen | braewoods, I think that would be better then. |
10:14:36 | braewoods | i can preinstall rockbox for you if you want. currently they run the OF. |
10:14:56 | MarcAndersen | braewoods, Yes please do that |
10:15:06 | | Quit MarcAndersen (Remote host closed the connection) |
10:15:07 | braewoods | i'll pm you then for the rest. |
10:15:10 | braewoods | ... |
10:15:12 | braewoods | lol |
10:15:15 | braewoods | quit |
10:15:20 | braewoods | :| |
10:15:29 | braewoods | well they'll be back at some point if they want it |
10:15:30 | | Join MarcAndersen [0] (~no_znepna@193.169.154.231) |
10:15:38 | MarcAndersen | My client crashed |
10:15:53 | braewoods | we saw the quit message |
10:16:00 | braewoods | i'll pm the rest |
10:16:02 | MarcAndersen | what did it say? |
10:16:46 | braewoods | "MarcAndersen (~no_znepna@193.169.154.231) has quit (Remote host closed the connection)" |
10:17:09 | MarcAndersen | Oh that's my ip |
10:19:38 | desowin | speachy: I just used the voice menu for the first time |
10:20:22 | desowin | I seems to work (with Polish voice pack), just clearly audible it is synthesized |
10:22:10 | speachy | desowin: it's generated using espeak-ng's defaults, if there are better-sounding settings to use that's easily changed. |
10:25:48 | braewoods | speachy: do you know what processor the ipod 6G uses? |
10:25:51 | braewoods | i can't find it on rockbox.org |
10:26:48 | speachy | it's on the wiki. some samsung arm9xx part |
10:27:51 | MarcAndersen | No matter what it's better than these 2 portalplayer devices I have left which actually works |
10:28:25 | braewoods | the gigabeat S has 64MB of RAM. |
10:28:31 | braewoods | an armv6 SoC |
10:28:41 | braewoods | and some other features most ports lack |
10:28:46 | braewoods | like FM Radio RDS |
10:28:54 | braewoods | but i think that's moot for Europe; didn't they do away with FM there? |
10:34:41 | MarcAndersen | Ok. It doesn't matter which one you send, just the one you use the least. |
10:36:06 | speachy | one thing that concerns me is that we can only spell out ascii words. |
10:36:26 | braewoods | can we do better with our limited resources? |
10:36:45 | speachy | but I don't really see a good way to improve that. |
10:36:49 | braewoods | i'm no expert on TTS. |
10:37:21 | speachy | the idea is you'd generate appropriate voice snippets for your specific files. |
10:37:34 | speachy | falling back to spelling out words |
10:37:44 | speachy | but that fails for non-english. |
10:37:56 | speachy | (or rather, non-ascii) |
10:38:14 | braewoods | the main problem is what TTS solutions could you use with rockbox's limited resources? |
10:38:54 | braewoods | i'd assume we'd use a third party one if we were trying to improve it |
10:44:12 | braewoods | speachy: how do i build voice files? |
10:44:22 | braewoods | i don't normally use them. |
10:44:24 | MarcAndersen | just press v in advanced build |
10:44:36 | speachy | configure script, advanced, lets you generate voices. |
10:44:38 | braewoods | does it have to be part of the normal build process? hm. |
10:44:42 | MarcAndersen | and make voice |
10:44:43 | speachy | it's not. |
10:45:23 | speachy | building voice files from the cmdline is vastly improved from what it used to be but it's still relatively crappy |
10:45:33 | MarcAndersen | I'm soon going out for a while, but I'll read the logs when I come back. |
10:45:37 | braewoods | ok |
10:46:16 | speachy | the build infra piggybacks on top of the configure script with options taken from builds.pm |
10:47:00 | speachy | but generally speaking the expectation is that users will generate voices (and file talk clips) using rbutil, which has its own quidks. |
11:00 |
11:00:45 | MarcAndersen | I'm going out now just so you know |
11:03:25 | braewoods | speachy: syntax error from configure while doing that |
11:03:35 | braewoods | ../tools/configure: 1156: [: =: argument expected |
11:04:18 | braewoods | ../tools/configure: line 1156: [: : unary operator expected |
11:04:23 | braewoods | when i use bash |
11:06:03 | speachy | at what step? |
11:07:06 | speachy | pretty sure that's because you dn't have any of the supported tts engines instealled |
11:07:07 | braewoods | after choosing the english voice or so |
11:07:16 | speachy | shouldn't be a syntax error though. |
11:07:20 | braewoods | even so it should still give a proper response |
11:07:31 | braewoods | not leave me wondering what's wrong |
11:07:34 | speachy | ah found it, a missing space |
11:08:02 | speachy | edit the script, line 1156, find the "] and change it to " ] |
11:08:15 | *** | Saving seen data "./dancer.seen" |
11:08:21 | speachy | "$MIMIC"] -> "$MIMIC" ] |
11:08:42 | braewoods | ok. |
11:09:28 | braewoods | that should be patched in a commit though |
11:09:34 | speachy | yep. |
11:09:56 | braewoods | what software is recommended? |
11:09:58 | braewoods | rbspeak? |
11:10:16 | speachy | espeak-ng is what the nightly voice builds utilize |
11:10:28 | speachy | festival might be the best for English |
11:10:59 | rb-bluebot | Build Server message: New build round started. Revision 663539619c, 297 builds, 9 clients. |
11:14:42 | braewoods | sheesh. no wonder this isn't done much. building the voices takes a long time. |
11:15:22 | braewoods | how do i make a zip archive for the voice stuff... |
11:21:44 | rb-bluebot | Build Server message: Build round completed after 644 seconds. |
11:21:46 | rb-bluebot | Build Server message: Revision 663539619c result: All green |
11:23:31 | braewoods | ok found it |
11:25:41 | | Quit JanC (Ping timeout: 265 seconds) |
11:28:31 | | Join JanC [0] (~janc@user/janc) |
11:39:28 | braewoods | interesting, i'm going to have to investigate this |
11:39:41 | braewoods | speachy: i've produced panics when using the remote with gigabeat S. |
11:39:50 | braewoods | i'll see if i can find out the issue later. |
11:52:38 | | Quit advcomp2019 (Read error: Connection reset by peer) |
11:53:22 | | Join advcomp2019 [0] (~advcomp20@user/advcomp2019) |
12:00 |
12:02:47 | | Join ZincAlloy [0] (~Adium@ip5f5abcae.dynamic.kabel-deutschland.de) |
13:00 |
13:08:18 | *** | Saving seen data "./dancer.seen" |
13:58:29 | braewoods | i've got a head scratcher... |
13:58:51 | braewoods | my code hangs in the callback or something... |
14:00 |
14:04:33 | braewoods | speachy: i've got a mystery. maybe you know something i don't. so, i pass a context pointer to my zip callback... i've confirmed via printf logging that the pointers are exactly the same before i call it and during.. |
14:04:55 | braewoods | but when i try to print the string buffer i wrote to, the contents are totally different once i'm in my callback. |
14:05:18 | braewoods | it should say "/extract/" like it was earlier but it just says "zip" once in the callback |
14:05:36 | braewoods | is it a coincidence that "zip" is the name i gave to core_alloc_ex? |
14:05:43 | braewoods | yet wth is goingon |
14:05:56 | braewoods | it's like my allocation got moved or something |
14:06:41 | braewoods | it just don't make no sense. |
14:07:47 | braewoods | braewoods/rockbox/blob/extract/firmware/common/zip.c">https://github.com/braewoods/rockbox/blob/extract/firmware/common/zip.c |
14:07:57 | braewoods | is my code right now, the extract prototype i haven't finished yet |
14:09:19 | braewoods | https://dpaste.com/3D8W6X45G |
14:09:22 | braewoods | is my log output |
14:10:02 | braewoods | wth am i doing wrong? or is rockbox doing? |
14:10:23 | braewoods | this behavior just doesn't compute to me |
14:10:28 | braewoods | but it does explain my issue |
14:10:34 | braewoods | just not the why |
14:10:40 | braewoods | something is happening to my allocation. |
14:11:01 | braewoods | hm |
14:17:50 | braewoods | i'll see if refetching the pointer changes anything |
14:21:30 | braewoods | ok it's not moving afaik... |
14:21:55 | braewoods | only one other possibility... the data was written to somehow between the two states. |
14:28:14 | desowin | cryptomemory read commands do not comply with I2C (Atmel calls it TWI) |
14:28:32 | desowin | it is connected to the same lines as proper I2C devices in Sansa Connect |
14:29:19 | desowin | I2C is bitbanged so I would pretty much have to add new function in generic_i2c |
14:30:06 | desowin | question is, how should I name it? i2c_cryptomemory_read()? |
14:56:16 | bluebrother | braewoods: well, my idea was to factor out bootloader installation into separate binaries. That also has the advantage that we can run Rockbox Utility non-root, and then use pkcon / elevation for the bootloader installation. So Rockbox Utility wouldn't need to do any mtp stuff. |
14:56:56 | braewoods | bluebrother: yea that's what i'm working towards. |
14:56:58 | bluebrother | instead we'd install the bootloader, then wait for the bootloader to come up in usb mode, and automatically figure the correct drive to use. |
14:57:18 | braewoods | i actually had a different idea |
14:57:24 | braewoods | slightly different |
14:57:55 | braewoods | we can send the rockbox files as an archive payload before the bootloader and the bootloader can extract them on first boot |
14:58:21 | bluebrother | I've started to look into how to split out the bootloader installation into separate binaries, but got stuck on the communication issue. Right now f.e. ipodpatcher functions are used to detect the correct disk. But those require sudo / elevation, so won't work anymore like it does now. |
14:58:55 | bluebrother | of course we could start the separate ipodpatcher during detection, but then would need some communication. |
14:59:22 | bluebrother | and similar issues for others. Had quite a lot of other stuff on my plate lately, so no real progress on this |
14:59:24 | braewoods | bluebrother: ok, fair enough. i'm just looking at a solution for MTP only ports (initially) |
14:59:43 | bluebrother | well, beastpatcher could do that. First send the bootloader, then rockbox.zip |
14:59:46 | braewoods | i'm working on coding zip support for rockbox so it can extract the ZIP archive |
14:59:49 | bluebrother | so nothing lost :) |
15:00 |
15:00:01 | braewoods | so we can keep the first install simple |
15:00:09 | bluebrother | indeed. |
15:00:37 | braewoods | i found that it has support for TAR already but it's easier if i just code ZIP support for RB i think |
15:00:43 | braewoods | so we don't need to repack anything |
15:00:52 | bluebrother | though I didn't deem it necessary to automatically install Rockbox in the first run. More user friendly though :) |
15:01:11 | braewoods | well i decided to go this route since it has a lot of other use cases too |
15:01:20 | braewoods | ZIP support would open up new potential if i can get this working |
15:01:28 | braewoods | right now tracing some weird issue |
15:01:33 | bluebrother | right. Simple zip support shouldn't be too much of an issue. Though I remember issues from years back when an updated zip created slightly different archives. |
15:02:47 | braewoods | i also plan to add decompression support but right now just trying to get the basic skeleton to work |
15:02:54 | braewoods | i suspect i got a memory stomping bug |
15:03:11 | braewoods | my core_alloc allocations change contents somehow and the data hasn't been moved |
15:03:13 | bluebrother | fun! |
15:03:59 | braewoods | ok, changing the context pointer to a global changees nothing. |
15:04:05 | braewoods | sounds like an overflow |
15:04:07 | braewoods | or something |
15:04:29 | braewoods | guess i get to pick apart it and see when it changes |
15:04:56 | braewoods | changes sometime after calling my read function |
15:08:21 | *** | No seen item changed, no save performed. |
15:08:30 | braewoods | unrolled my read function, time to test it out |
15:28:21 | braewoods | ... |
15:28:27 | braewoods | SERIOUSLY? THAT'S THE ISSUE? |
15:28:33 | braewoods | ugh. |
15:29:05 | braewoods | i didn't request enough memory. sizeof(zip_extract) |
15:29:19 | braewoods | it's taking the size of my function address |
15:29:24 | braewoods | i forgot to add struct to it |
15:41:11 | braewoods | g#3543 for whoever has time to review a trivial change |
15:41:13 | rb-bluebot | Gerrit review #3543 at https://gerrit.rockbox.org/r/c/rockbox/+/3543 : zip: rename modts field to mtime by James Buren |
15:47:48 | speachy | bluebrother: how does /rockbox/bot/utility sound for rb-bluebot? |
15:48:08 | speachy | for a cloak, I mean |
15:49:11 | blbro[m] | Sounds good to me :) |
15:50:54 | speachy | ok, request put in for that and the logbot |
15:51:53 | blbro[m] | Nice, thanks |
15:59:15 | desowin | speachy: can you get me a cloak? |
15:59:53 | * | braewoods gives desowin the emperor's new clothes. |
15:59:56 | braewoods | :P |
16:00 |
16:07:38 | speachy | desowin: sure, /rockbox/developer/desowin ? |
16:17:41 | | Quit rb-bluebot (Changing host) |
16:17:41 | | Join rb-bluebot [0] (~rb-bluebo@rockbox/bot/utility) |
16:17:53 | | Quit desowin (Changing host) |
16:17:54 | | Join desowin [0] (~linux@rockbox/developer/desowin) |
16:24:50 | speachy | apparently I neglected to register rb-logbot with nickserv.. |
17:00 |
17:08:25 | *** | Saving seen data "./dancer.seen" |
17:56:24 | | Quit ZincAlloy (Quit: Leaving.) |
18:00 |
18:37:25 | | Join cockroach [0] (~blattodea@user/cockroach) |
19:00 |
19:08:27 | *** | Saving seen data "./dancer.seen" |
19:23:56 | | Quit wolfshappen (Quit: later) |
19:25:09 | | Join wolfshappen [0] (~waff@irc.furworks.de) |
19:54:23 | braewoods | speachy: were inline functions not a thing in early rockbox? i see a lot of macros that could be inline functions. they don't need the typeless nature of macros. |
19:54:54 | braewoods | instead they're using a GNU extension to simulate a function expression |
19:55:03 | braewoods | ({ }) |
19:55:30 | speachy | cam |
19:55:54 | braewoods | cam? |
19:55:56 | speachy | can't comment on the thinking of all of the baggage but for a while there one really couldn't trust gcc to inline things with any sense of coherency |
19:56:29 | braewoods | would you be opposed if i replaced function macros with inline functions where they're a drop in replacement? |
19:56:44 | speachy | and if the stuff wasn't inlined the performace would be worse |
19:56:57 | braewoods | static inline should still be honored |
19:57:14 | braewoods | even at -Os |
19:57:23 | braewoods | but not quite sure |
19:57:32 | speachy | at -Os it'll most likely _not_ inline them actually |
19:57:40 | braewoods | i see |
19:57:43 | braewoods | hm. |
19:57:53 | braewoods | i've seen GCC inline my static functions at times |
19:58:03 | speachy | some archs have relatively high overhead for function calls |
19:58:16 | speachy | (remember this whole thing started on sh) |
19:58:24 | braewoods | which we dropped |
19:58:49 | braewoods | oddly pathfuncs.h already uses some inline functions |
19:58:50 | speachy | yep, but there's still a ton of code/structure that was optimized for the sh targets. |
19:59:16 | speachy | generally I'd like to see some sort of tangible improvement to change stuff that's already working. |
19:59:19 | braewoods | i think we should consider replacing some of this code with inline functions since those may be better optimized than a function macro |
19:59:29 | braewoods | even so |
19:59:38 | braewoods | i'll come back to this later |
20:00 |
20:01:16 | braewoods | weird |
20:01:27 | braewoods | i see this macro defined in rockbox headers but nothing uses it |
20:01:30 | braewoods | __need_size_t |
20:01:52 | braewoods | i wonder what it was added for |
20:03:36 | speachy | git blame? |
20:04:12 | braewoods | speachy: do you have any recommendations for how i should split paths for relative file paths? i need to split them so i can use mkdir on the components... except for the last part which may be a file |
20:04:39 | braewoods | the rockbox pathfuncs seem a bit confusing to use for this |
20:05:17 | speachy | I can't comment on the rb path functions, but typically one walks forward, finding the path separators, and using that to walk/create the directory tree |
20:05:41 | braewoods | yea, i have constructed the full path and i just need to step through all but the last part. |
20:05:55 | braewoods | i can null terminate them to allow mkdir to work before reverting to the original char |
20:14:21 | | Quit wolfshappen (Quit: later) |
20:46:19 | braewoods | speachy: huh, i just realized. GOBBLE_PATH_SEPCH and GOBBLE_PATH_SEPCH are specialized versions of strspn and strcspn |
21:00 |
21:08:30 | *** | Saving seen data "./dancer.seen" |
21:25:07 | | Quit akaWolf (Ping timeout: 246 seconds) |
21:27:03 | | Join akaWolf [0] (~akaWolf@akawolf.org) |
21:59:57 | | Quit cockroach (Quit: leaving) |
22:00 |
22:49:14 | | Quit MarcAndersen (Quit: I was using NightOwl 0.2.) |
23:00 |
23:08:32 | *** | Saving seen data "./dancer.seen" |