--- Log for 05.12.116 Server: card.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 4 days and 12 hours ago 00.06.18 Quit Harbec (Ping timeout: 265 seconds) 00.08.04 Quit ender` (Quit: sweater, n a garment worn by children when their mother is cold) 00.31.41 Quit ZincAlloy (Quit: Leaving.) 00.48.48 Ctcp Ignored 1 channel CTCP requests in 0 seconds at the last flood 00.48.48 # * __builtin needs a way to get sub-HZ timing 00.54.41 Quit girafe2 (Read error: Connection reset by peer) 01.00.17 # <__builtin> would it be a good idea to just calibrate a busy loop for 10 milliseconds and then do intervals of that? 01.06.24 # __builtin: what do you need sub-HZ timing for ? 01.09.02 # many targets have udelay for precise delays 01.09.14 # udelay(int microseconds); 01.14.56 Quit pamaury (Ping timeout: 265 seconds) 01.21.44 *** Saving seen data "./dancer.seen" 01.23.25 Quit xorly (Ping timeout: 250 seconds) 01.28.59 # * __builtin is trying to make it easier to press buttons simultaneously 01.30.17 # <__builtin> so essentially button_get(true); usleep(5000); button = button_status(); 01.32.03 # <__builtin> sleep(0) mostly works but it's unreliable 01.32.11 # <__builtin> and sleep(1) is too slow 01.34.53 Join mc2739 [0] (~mc2739@rockbox/developer/mc2739) 01.54.09 Join Bilgus [0] (ae6611d9@gateway/web/freenode/ip.174.102.17.217) 01.56.08 # __builtin: what context are you wanting to do this in? 01.56.14 # <__builtin> plugin 01.56.17 # <__builtin> so no udelay() 01.57.08 # I've been all over the get action code the last few weeks do you know what buttons you want to use? 02.04.09 # problem with button get is that you are going to be fighting with button_try_post, it waits till the queue is empty before posting another key even unless it is a release event 02.04.55 # so you would need to already have popped the last key from the queue before you would get the next 02.06.30 # using action.c get_custom_action() you could define your own custom keymap that would allow you to do what you want 02.19.29 Nick Bray90820 is now known as bray90820 (~bray90820@50-83-212-56.client.mchsi.com) 02.25.01 Quit krnlyng (Ping timeout: 265 seconds) 02.38.03 Join krnlyng [0] (~liar@77.117.11.111.wireless.dyn.drei.com) 02.49.09 Quit nlogex (Quit: WeeChat 1.6) 03.02.43 Quit Moarc (Ping timeout: 248 seconds) 03.03.05 Join cosmiclatte [0] (~Android@172.98.87.84) 03.03.34 Join Moarc [0] (~chujko@a105.net128.okay.pl) 03.05.37 Quit PurlingNayuki (Ping timeout: 258 seconds) 03.14.48 # anyone here use a portable amp? 03.15.22 # and I'm wondering how to compare the components of an iriver h300 to newer players 03.15.25 Join PurlingNayuki [0] (~Thunderbi@2001:da8:215:6905:6452:a23b:ac84:22e4) 03.15.29 # like what are the main ones to look at 03.16.29 # can I upgrade some output caps or something like that to tide me over until I can actually afford something relatively first or second tier in terms of players 03.21.48 *** Saving seen data "./dancer.seen" 03.41.18 Join Harbec [0] (~Harbec@dsl-205-233-124-148.b2b2c.ca) 03.45.55 Quit Harbec (Ping timeout: 248 seconds) 03.46.53 # that seems like a fools errand you've more of a chance of destroying your player than anything, what exactly are you trying to achieve? 03.47.30 # <[Saint]> The numbers, Mason! 03.48.22 Join Harbec [0] (~Harbec@dsl-205-233-124-148.b2b2c.ca) 03.49.22 # <[Saint]> In all fairness, I say go for it...I need some spares for my h3**. 03.49.57 # <[Saint]> I don't need a mainboard, but I would love a spare LCD and case. 03.51.13 # lol, I'm not sure what the options are in terms of upgraded SMD components or how exactly you would go about quantifying that 03.52.02 # <[Saint]> fishbulb: TL;DR: there's absolutely nothing you can replace that will make any meaningful difference that won't; 03.52.02 # <[Saint]> A - Require major re-routing of the mainboard, and/or 03.52.02 # <[Saint]> B - Require a major software re-write. 03.52.13 # as for a portable amp I think that is just one more thing to carry around I'd throw my money into a better set of headphones 03.52.50 # Lower impedance the better 03.53.21 # <[Saint]> Bilgus: a lot of people tend to forget about impedance matching their monitors, and making sure there's enough output to actually drive them. 03.53.42 # <[Saint]> just "get better monitors" almost always also means getting a portable active or discrete amp. 03.53.43 # figure an amp is just going to amplify whatever you don't like in the original signal GIGO 03.54.14 # or you have cans that the thing can't really drive properly 03.54.41 # like literally anything with a "form factor" 03.55.04 # <[Saint]> I use the FiiO Mont Blanc personally. 03.55.25 # <[Saint]> Nothing quite like the feeling of carrying around a small explosive device close to your genitals to make you feel alive. 03.56.07 # hmm you and I we have different definitions of feeling alive :p 03.56.33 # <[Saint]> I have a bit of a wank everyday setup. 03.56.44 # <[Saint]> SSD converted iPod Classic 6G w/ extended battery, FiiO Mont Blanc, and UE 18 Pro full custom monitors. 03.56.46 # that one is pretty expensive 03.56.54 # <[Saint]> It is. Yes. 03.57.00 # the fiio 03.57.25 # <[Saint]> I wouldn't look at the cost of my monitors then... 03.57.33 # I just use reference headphones 03.57.39 # sennheisers are good 03.57.54 # anything used in studios are good 03.58.14 # <[Saint]> sennheisers /can/ be good. 03.58.21 # <[Saint]> very far from "are" good though. 03.58.27 # <[Saint]> they really make some absolute shit. 03.58.37 # <[Saint]> there's a few rare gems in there though. 03.58.44 # ok their studio headphones and some others are good 03.59.00 # anything upwards of those aren't shitty 03.59.16 # not anything, but anything people rate 03.59.30 # <[Saint]> spending the ludicrous monies for lifetime guaranteed full replacement warranty custom molded monitors was the best audio descision I ever made I think. 03.59.33 # "things that other people say are good are usually good" 04.00.11 # I just got some memory foam/pleather cushions 04.00.26 # those work better than the stock ones 04.01.06 Quit idonob (Ping timeout: 256 seconds) 04.01.26 # cool thing about in ear is how much less power you need to destroy your hearing 04.01.28 # that fiio e12 analogue is too expensive compared to other ones, there's a couple of chinese things that are ok 04.01.42 # I got tired of in ear because so much wax built up 04.02.08 # and in australian summer it's sweaty as hell, they fall out a bit 04.02.17 Join idonob [0] (~Owner@S010610c37b922980.vs.shawcable.net) 04.02.17 # <[Saint]> I dunno man...I mean, reviewers /loved/ the IE80s. 04.02.26 # <[Saint]> WHich are, IMO, the worst purchase I ever made. 04.02.53 # <[Saint]> Stupid bass-heavy pieces of shit, even when you tune them to their minimal bass output. 04.02.55 # sites like head-fi trashed the objective amp and have some really biased reviews so they'll get given more shit 04.03.11 # <[Saint]> God I really wanted to like the IE80s for what I paid for them. 04.03.17 # <[Saint]> They really are trash though. 04.03.45 # <[Saint]> If you google 'em you'll probably immediately go "ooooohhhhh, those ones - yeah" 04.04.17 # I've only seen them 04.04.23 # <[Saint]> Ah. 04.04.28 # I had cx500 as my last in ear 04.05.34 # <[Saint]> I got the EU16 Pros and then at some point was upgraded for cost+shipping to the EU18 Pros when I needed to send them in for a slight readjustment against new molds. 04.05.36 # they were pretty good but that sweat issue 04.06.02 # anything that makes my ears more gross is sort of bad 04.06.31 # <[Saint]> One thing I find mildly annoying about the EU18s in the custom fitting is that they are almost, dare I say it, /too/ isolating. 04.06.34 # <[Saint]> Pretty easy to wander out into traffic, etc. 04.06.48 # oh yeah I was almost hit by a couple of busses 04.06.58 # those guys do not stop, trams are easier to see coming 04.07.15 # also cyclists can come out of nowhere 04.07.37 # I've caused a couple of accidents and near accidents with nothing in or on my ears 04.08.10 # <[Saint]> probably the best thing you can do for your h300 is sell it and rebuild an iPod 5.5G or 6G as solid state+large battery. 04.08.16 # with arrogant spandex dudes assuming I'd hear or see them coming up at 50km/h on a dead silent bike 04.08.32 # no they don't sound that much better 04.08.48 # why would you say ditch the h300 for an ipod? 04.08.53 # <[Saint]> I guess you like your output a bit more colourful than I do. 04.08.58 # <[Saint]> I like mine to be flat. 04.09.02 # colourful how 04.09.15 # as in not the intended reproduction 04.09.21 # <[Saint]> ^ that 04.09.26 # I'm probably just used to it, I always had a large battery and I did an ssd 04.09.32 # yeah but where are you getting your information? 04.09.43 # <[Saint]> RMAA 04.09.50 # can I see? 04.10.19 # <[Saint]> errrrr, sec. I might have a comparison set local. 04.10.36 # these "studio headphones" are reasonably flat, not linear 04.10.42 # even my studio monitors are flattish 04.10.51 # and those cost a lot 04.11.36 # pretty flat actually, surprising what can come out of things the size of a shoebox 04.11.52 # krk used to make some good speakers 04.12.34 # at some point they turned chinese and grey/silver 04.12.48 # before that they were chinese for like one or two models 04.13.33 # <[Saint]> Hmmmmm, fuck. I can't find my RMAA sets offhand. I do have them somewhere around. 04.13.33 # <[Saint]> What I recall was the h300 had a really bad 'hiss' that the iPod 6g doesn't, and the iPods and h300 both had a pretty sharp roll off in the high frequencies but in the h300 it actually started in the audible spectrum. 04.14.00 # <[Saint]> But I understand this is subjective. If I can't find loaded and unloded results I'll attempt to reproduce them and see if they stack up. 04.14.33 # I notice a hiss compared to some other sources 04.14.54 # I thought it was components getting crappier because it's twelve years old now 04.15.12 # <[Saint]> AFAIR it's just an inherent quality of the H300. 04.15.35 # I was thinking of the xduoo x3 04.15.40 # and an amp 04.15.46 # bah imo that 12 years old probably means better components in the first place 04.15.59 # it does, these things are bricks 04.16.14 # <[Saint]> The YP-R* are weird little devices. 04.16.24 # the what? 04.16.35 # <[Saint]> Well made, I think I'm the only person in history who's bricked one. 04.17.04 # I mean anything slim like phones clip at low volumes 04.17.22 # <[Saint]> One of our hosted platforms. re: YP-RO/YP-R1 04.17.24 # I've never heard a good phone or anything that isn't a dedicated player 04.17.33 # how much are they? 04.18.02 # <[Saint]> Not sure. I got mine at cost+shipping, which ended up at just over $150 NZD. 04.18.26 # <[Saint]> Which isn't a useful value to anyone who can't get the same deal. 04.18.38 # I was looking at the xduoo x3 because for about 150aud it's 256gb of storage and 24bit with decent stuff 04.19.07 # <[Saint]> You're thinking Rockbox, yes? I mean, the original FW is trash. 04.19.28 # <[Saint]> You should know that anything higher than 16bit is just useless fluff that'll be internally downsampled. 04.19.36 Quit atsampson (Ping timeout: 240 seconds) 04.19.42 # I wouldn't get a player that couldn't do rockbox 04.19.42 # <[Saint]> So, don't target those magic numbers deliberately. 04.19.58 # <[Saint]> I mean, honestly, there's really no fucking point in anything higher than 16bit anyway. 04.20.02 # yes but the dac does... stuff 04.20.04 Join atsampson [0] (~ats@cartman.offog.org) 04.20.18 # like burns power and cash? yes :p 04.20.27 # <[Saint]> the DAC does what it is told. 04.20.55 Join a_person [0] (326f9425@gateway/web/freenode/ip.50.111.148.37) 04.20.55 # 100usd for 256gb of storage and 10 hours of playback that is neutral and supposedly good is a good price 04.21.02 # for a metal thing 04.21.32 # <[Saint]> Anyway, my point is, if you go in targeting things like 96KHz+, or 24bit+, you're playing a fools game. 04.21.35 Join Strife1989 [0] (~quassel@adsl-98-80-184-227.mcn.bellsouth.net) 04.21.41 # <[Saint]> because we do 16/48 max. 04.21.46 # most reviews are good 04.22.14 # <[Saint]> there's no good reason to have greater than 16/48 in consumer reproduction audio anyway. 04.22.24 # couldn't hurt 04.22.28 # <[Saint]> you're not dynamically live mixing the soundstage out and about. 04.22.35 # <[Saint]> and, yes, actually it can hurt. 04.22.54 # plugging things into good speakers is pretty common 04.23.13 # <[Saint]> and 24/96+ is meaningless in that context. 04.23.19 # <[Saint]> like, absolutely so. 04.23.48 # The themes and forums subdomains are unreachable (by me). I'm guessing that the folks who ought to know already know but it has been a while so I figured I'd just wave the flag just in case it was unnoticed. 04.24.10 # well it can't record and I'm positive my ears are more damaged from gigs than would be necessary to notice it, so this is a theoretical argument 04.24.14 # <[Saint]> none of the hardware in the world is going to change /your/ hardware, and your ears aren't ever going to be capable of perceiving anything that can't be duplicated in 16bits. 04.24.24 Quit Strife89 (Ping timeout: 265 seconds) 04.24.38 # I know this 04.24.45 # but if the hardware can do it, good 04.24.52 # it's got good dacs and amps 04.25.36 # I'm short on cash and it looks like an alright price, I can't change anything about my iriver 04.26.26 # a_persion afaik it it known and will be fixed when they get a chance, works about 10hrs out of each day 04.26.33 # a_person 04.26.47 # <[Saint]> it'll work intermittently, or it won't. 04.26.50 # <[Saint]> the issue is known. 04.27.03 # <[Saint]> it's suffering a non-targeted DDOS on and off. 04.27.13 # what? 04.27.48 # <[Saint]> Bah. Force of habit. Added another D. 04.27.48 # <[Saint]> (heh...the D) 04.27.49 # why would someone bother 04.27.52 # cool. 04.28.02 # <[Saint]> see "non-targeted", fishbulb. 04.28.14 # <[Saint]> no one is bothering. 04.28.30 # do you do SDR stuff too, I've seen you somewhere else 04.29.02 # multirotors? rtlsdr? 04.29.21 # a vaping channel? 04.29.28 # <[Saint]> I have been known to, but I mostly do JEOS Kodi stuffs, and a bunch of Android stuffs. 04.29.48 # I'm looking at a cat s60 04.30.01 # I can't find any better phone, milspec and with a thermal camera 04.30.13 # if you know of phones that have cooler shit than that I'm all ears 04.30.18 # my phone is from last decade 04.31.30 # <[Saint]> S7 in an otterbox extreme. 04.31.31 # <[Saint]> you'll use the thermal cam like...once. 04.31.32 # I ran out of corpses to rebuild this phone, it's on it's last regeneration 04.31.43 # no I'll use it a bit, I have a touring muscle car 04.32.00 # <[Saint]> then you should get a real, dedicated thermal cam. 04.32.02 # I built it, I already have sensors everywhere 04.32.33 # no I'd use this phone, I wouldn't afford or use a dedicated thermal camera for how useful it is 04.32.50 Quit Harbec (Ping timeout: 260 seconds) 04.32.57 # more than the sensors that are in place and common sense when it comes to driving high output cars hard 04.33.06 Part a_person 04.33.13 # <[Saint]> the problem with those cat phones is they just can't resist shitting over the software for no good reason, there's no third party development paths for them, and the hardware they shipped with was already ~18 months outdated at launch. 04.33.19 # <[Saint]> and they're fucking expensive. 04.33.40 # <[Saint]> may as well get a flagship device and an extreme reggedized case. 04.33.44 # how do you know those are problems, the android has barely been messed with 04.33.58 # it's already milspec and has a thermal camera, and decent enough specs 04.34.09 # does the s7 still explode? 04.34.20 # <[Saint]> It never did. Way to bias. 04.34.35 # I went on some flights recently and they banned them from the aircraft 04.34.41 # <[Saint]> No they didn't. 04.34.53 # yes, they did 04.35.08 # <[Saint]> No. You're very clearly mistaking and conflating S and Note series devices. 04.35.13 # <[Saint]> *mistaken 04.35.15 # they banned them outright from the aircraft and you had to mail them back 04.35.22 # oh the note 7 04.35.35 # galaxy note 7 then 04.35.41 # I really don't care about phones 04.35.44 # <[Saint]> And also more iPhones have "exploded" than Note 7s, period. 04.35.52 # <[Saint]> Samsung just handled it better. 04.36.11 # Lithium ions are awesome :D 04.36.12 # obviously samsung telling the aircraft made them as illegal as drugs 04.38.11 # <[Saint]> Eh. Not really. That was more a vitriolic reaction from the concern trolls of the public sector and a really well executed smear campaign. 04.38.36 # <[Saint]> Samsung did the right fucking thing and got slammed for it, because fair competition in the mobile sector isn't a thing. 04.38.57 # <[Saint]> ANd now it's "the phone that explodes", and there's so much bias around people can't even get the damn model right. 04.39.11 # I had a gps unit go all melt down on my dash a few years ago, Luckily it just suffered a mangled case as I took it apart and ripped the battery from it 04.39.12 # no they got banned from aircraft 04.39.26 # <[Saint]> I realize you didn;t do that intentionally but it really helps validate my point, so I'll own it. 04.39.36 # I'm sure if I went into a store they wouldn't say "oh do you want the pre recall model or the one that never has caught on fire" 04.39.48 # "do you want a burnt one or a normal one" 04.40.15 # if the price was right I'd gladly take the 'burnt' ones 04.40.32 # why? 04.40.48 # <[Saint]> I dunno man. You might be surprised how far this even innocent biases travel. 04.40.48 # <[Saint]> For a while, perhaps even still, Google autosuggestion for "I want a phone that..." 04.40.54 # <[Saint]> was "doesn't explode". 04.40.59 # bc I don't subject my devices to such extremes 04.41.24 # ever read the warnings in your phones manual? 04.41.28 # <[Saint]> Bilgus: me too. Honestly, I've got better odds of being hit by lightning, or eaten by a shark. 04.41.31 # if I see "if you have any narcotics or a samsung s7 you'll probably be put in prison" AT AN AIRPORT 04.41.33 # <[Saint]> And I live 4km inland. 04.41.54 # then yeah I'm going to think "oh that must have been a bad thing" 04.42.01 # <[Saint]> Samsung just did the right thing for consumer safety by just going "nope, fuck it, we're taken' 'em all back". 04.42.09 # <[Saint]> which hilariously, caused even more concern. 04.42.28 # <[Saint]> The Apple or other OEM way of handling it is to quietly just pay the fuckers out to avoid a civil suit. 04.42.34 # you have to carry all lipos on carryon 04.43.07 # <[Saint]> fishbulb: which is the problem. They did the /right/ thing. 04.43.11 # <[Saint]> Not a bad thing. 04.43.17 # all lithium batteries that have insane capacities, which I take on planes, have to be carried on board 04.43.34 # if you have any rechargeable li-ion or lipo in your checked baggage they'll take it out 04.43.39 # on any plane 04.43.47 # or, a phone that has been known to explode 04.43.51 # publically known to explode 04.44.13 # like I said I don't give a fuck about any phones, other than the cat s60 and you didn't explain why that's a bad phone 04.44.24 # the android it comes with hasn't been fucked with 04.44.29 # how do you regulate an explosive device in most consumers pockets no less a device that people would have a melt down without 04.44.33 # from what I can see they've done everything right 04.45.12 # bilgus an 18650 shorted will go off like a decent bomb 04.45.17 # a decent 18650 04.45.22 # it'll cause havoc 04.45.33 # all except they have a protection device built in 04.45.42 # no they don't, none of the ones I do have 04.45.47 # I said decent 04.45.56 # oh yes they do its called venting 04.46.02 # these discharge rates can never have protection 04.46.10 # he meant protection as in circuits that pop 04.46.14 # and they don't vent 04.46.24 # they spray lava out 04.47.07 # <[Saint]> I did. You just didn't accept it. Which is usually the case when someone doesn't want an opinion, but is rather seeking validation of the descision they're already made: 04.47.07 # <[Saint]> - no clear commitment to update cycle 04.47.07 # <[Saint]> - shipped with ~18mo outdated hardware 04.47.07 DBUG Enqueued KICK [Saint] 04.47.07 # <[Saint]> - zero path for third party development when you're eventually left out in the cold 04.47.08 # or they explode and then spray burning stuff out 04.47.23 # the cat phones? where dd you get that info? 04.47.40 # caterpillar aren't going to go broke any time soon 04.47.49 # <[Saint]> what do you think that means? 04.48.05 # <[Saint]> they're also not going to keep supporting it indefinitely. 04.48.15 # military spec anything is lucky to have 18mo old hardware at all 04.48.38 # that is the thing about most any consumer products they are outdated when you get them 04.48.54 # <[Saint]> which for a new mobile is a huge fucking problem, especially when that ingress protection can be added to almost any flagship with an external case. 04.49.09 # what's some flagship devices then 04.49.29 # what do any of them do that are at all useful like a thermal camera 04.49.34 # the FLIR external things are crap 04.49.52 # <[Saint]> My God, seriously? S7, Pixel/XL, N6P, V20... 04.50.02 # I'd want audio, awesome gps and outdoors stuff, or... a dedicated qwerty keyboard 04.50.06 # <[Saint]> and the thing that is useful like a therman camera is a dedicated therman camera. 04.50.07 # I don't give a fuck about photography 04.50.10 # <[Saint]> *thermal 04.50.45 # <[Saint]> So, I refer back to my point of "you don't want opinions, you want validation". 04.50.55 # <[Saint]> And you won't get that from me. 04.52.04 # <[Saint]> I mean...who cares about a current OS and guaranteed security advisory patches, right? ....nah. No one. You're right. 04.52.09 # good luck getting an actual keyboard on phones :/ 04.52.55 # <[Saint]> Bilgus: you're not aware of the blackberry clusterfuck then I take it. 04.53.15 # that is why there are touch screen devices in my kids pockets 3 around the house doing various things but a dumb phone in my pocket 04.53.29 # <[Saint]> Blackberry Priv. 04.53.39 # I can text and not have to look at the damn thing 04.53.41 # <[Saint]> I shit you not that's a thing that exists and was launched this sector. 04.54.24 # that is... AWESOME :) 04.54.28 # <[Saint]> SOme marketing team decided "yes, this is a thing that will work", and managed to get it all the way through production into sales before they remembered it was a shit idea all the other times anyone tried it. 04.55.05 # <[Saint]> including almost bankrupting themselves years ago be refusing to modernize. 04.55.21 # <[Saint]> they though they would claw their way back and have another go throwing money into the money pit. 04.55.25 # <[Saint]> 'cos...reasons. 04.55.26 Join JensB [0] (~jensb@multitrading.dk) 04.56.45 # I'm just fine with my dumb phone tbh $35 every 3 years I can beat someone unconscious with it and then call 911 for them 04.58.03 # when I need a computer I use my tablet or my lappy 04.58.20 # but I'm weird 04.58.37 # <[Saint]> Modern handsets reflect the fact that tablets are deceased technology. 04.58.47 Quit JensB (Remote host closed the connection) 04.58.56 # why because they are so freaking large? 04.58.58 # <[Saint]> phones and tablets raised and lowered in size and stabilized on ~6" 04.59.20 # I knew there was a reason for those big pockets on jnco jeans 04.59.41 # <[Saint]> I would need some really compelling reasons to go back to a smaller device. 04.59.44 # they just happened to be 10 years early 05.00.10 # <[Saint]> me from ~2 years ago thought the Nexus 6 was a whale (the internal name is 'shamu' - lol). 05.00.17 # <[Saint]> Now...it's just "a phone". 05.02.25 Join JensB [0] (~JensB@multitrading.dk) 05.02.32 Quit PurlingNayuki (Ping timeout: 245 seconds) 05.03.41 # so on how many devices is the current dev build too big? 05.05.49 # I want something milspec 05.06.18 # tablets are still good 05.06.39 # I have an android tablet which is why I don't give a fuck about phones unless they do something a tablet can't 05.06.45 # which isn't much, tablets are large and powerful 05.07.21 # the size and power of a tablet is the good thing about them 05.07.26 # and battery life 05.07.42 Nick Strife1989 is now known as Strife89 (~quassel@adsl-98-80-184-227.mcn.bellsouth.net) 05.08.03 # my laptop is a tablet too but linux isn't a good platform for battery life graphics or maps or... anything 05.08.35 # and if I'm going to give my phone number to android it's for a milspec phone or one that does something phenomenal 05.08.48 # android and the dozen other companies that'll get all my info immediately 05.08.57 # and sync all that bullshit 05.09.19 # take all my information when I click "ok" 05.11.50 # [Saint], where can I talk about phones? 05.12.26 # <[Saint]> In general, or somewhere where people aren't going to mock the shit out of you for that Cat monstrosity? 05.12.43 # :) 05.12.55 # phones that are good 05.13.06 # somewhere people know phones 05.13.25 # <[Saint]> #android is the obvious choice - I'd keep the Cat thing to yourself though. 05.13.34 # no, that's the only phone I like 05.13.45 # <[Saint]> Then, nowhere. 05.13.53 # <[Saint]> And, I would also wonder why. 05.13.59 # why what 05.14.04 # <[Saint]> You just want a fucking echo chamber or self validation. 05.14.13 # I'd prefer a milspec phone 05.14.43 # a slightly smaller screen, a bigger battery and military grade durability 05.15.18 # a flagship device is a thin fashionable piece of crap that will shatter like a faberge egg and cost just as much 05.16.05 # if I want to break an android device that I actually want to use, I'd just throw my tablet at a wall 05.16.35 # <[Saint]> It is obvious you have some extreme biases, I have no want or desire to contribute to the fishbulb echo chamber of self validation and butthurt. 05.17.11 # which channels have other people who keep up with phones? 05.17.52 # I don't know anything about phones or tablets or android, so I can't help you finding a channel - except for: try google. 05.19.27 # <[Saint]> Last thing I'll say on the topic would be, again, #android. But this is not the place for you if you actually want objective reasoning. 05.19.49 # <[Saint]> It's not the CAT fanclub and the hardware will rightly be railed for obscurity. 05.20.39 # <[Saint]> sorry, s/if you/unless you/ 05.21.27 # A few hours ago, I succeeded in building a rbclient and tested builds with 3 architectures. 05.21.48 # <[Saint]> Nice. 05.21.51 *** Saving seen data "./dancer.seen" 05.22.01 # I executed runclient.sh, but I haven't seen any build reports. 05.22.09 # Is there a way I can make sure it's working ? 05.22.17 # <[Saint]> There haven't been any commits. 05.22.27 # <[Saint]> So, this would be entirely normal. 05.23.06 # I feel better already. :) 05.23.46 # Is there a list of build-clients somewhere (rockbox is great at making statistics web-sites, btw). 05.26.07 # So on how many devices is the current dev build too big? 05.30.15 # <[Saint]> None. But that's because we've had to get somewhat aggressive with ifdef'ing shit out. 05.30.53 # <[Saint]> If you were to blanket enable all optional features that /could/ build for every given target I think there's going to be at least 3 casualties. 05.31.08 # archosplayer, 05.32.05 # archosrecorder, 05.40.54 # on the recorder error: firmware image is 327634 bytes while max size is 204800! 05.41.14 # I can't imagine my patch adds that much 05.41.33 # am I doing something wrong? 05.43.25 # maybe i need to set the ram size instead of using default? 05.45.39 Join PurlingNayuki [0] (~Thunderbi@2001:da8:215:4ff:7cbe:2c03:50ca:cbbd) 05.49.39 Quit smoke_fumus (Quit: KVIrc 4.2.0 Equilibrium http://www.kvirc.net/) 05.51.15 # <[Saint]> I really don't see any way possible you'll be able to cram it in there. 05.51.40 # <[Saint]> like, for those targets, it is virtually impossible to add any new features at all. 05.52.10 # <[Saint]> but overflowing it by such a huge amount does indeed suggest something went very weird. 05.52.48 # so how can I conditionally define out my patch on unsupported builds? 05.53.50 # <[Saint]> for those it is pretty easy, just wrap it all in #ifdef PLAYER_PAD 05.54.15 # well then I sure hope there aren't many 05.55.08 # any hands on experience with topping nx2 ? 05.55.24 # <[Saint]> It really would be nice if Mr. Someone finished up with the Gerrit hooks for pushing builds to the build client on-demand. 05.56.27 Ctcp Ignored 1 channel CTCP requests in 0 seconds at the last flood 05.56.27 # * [Saint] is pretty much religiously a bottom. 05.56.30 # <[Saint]> topping ain't my bag. 05.59.03 # why not 05.59.11 # oh right 05.59.33 # gay sex 06.00.06 Mode "#rockbox +o scorche" by ChanServ (ChanServ@services.) 06.00.10 Kick (#rockbox fishbulb :bye) by scorche!~scorche@rockbox/administrator/scorche 06.00.14 Mode "#rockbox -o scorche" by ChanServ (ChanServ@services.) 06.00.56 Join fishbulb [0] (~fishbulb@unaffiliated/fishbulb) 06.00.58 Mode "#rockbox +o [Saint]" by ChanServ (ChanServ@services.) 06.01.13 # [Saint]: So if for instance the archosplayer is there an actual def or do I need to check MODELNAME? 06.01.31 # <[Saint]> wait...hmmm, I can't kick myself? 06.01.44 Mode "#rockbox +o scorche" by ChanServ (ChanServ@services.) 06.01.46 Kick (#rockbox [Saint] :nope - i have to) by scorche!~scorche@rockbox/administrator/scorche 06.01.48 Mode "#rockbox -o scorche" by ChanServ (ChanServ@services.) 06.02.10 Join [Saint] [0] (~sinner@rockbox/staff/saint) 06.02.49 # <[Saint]> For reference I tried to be diplomatic and kick myself with the message 'fair is fair' - but Chanserv seems to (rightly) assume no one is that retarded. 06.03.42 # i'm pretty sure you didnt descend into homophobic crap 06.03.53 # <[Saint]> Bilgus: I referenced it. PLAYER_PAD is an easy way of referencing all the Archos Player variants. 06.04.29 # well it seems to be okay with a few? wouldn't want to nuke them all 06.04.29 # it was pro homo 06.04.40 # he started it 06.04.46 # <[Saint]> I did. 06.04.48 # does anyone have experience with the topping nx2 06.05.34 # it's a dac amp, has android support 06.06.24 # archosfmrecorder,archosrecorderv2,archosondiosp, archosondiofm 06.06.35 # all compiled fine 06.07.24 # <[Saint]> Oh, right - then, you will need to be more specific. 06.07.57 # So MODELNAME? 06.08.19 # <[Saint]> #ifndef MODEL_FOO || MODEL_BAR || MODEL_BAZ 06.08.19 # <[Saint]> funsies() 06.08.19 # <[Saint]> #elif 06.08.19 DBUG Enqueued KICK [Saint] 06.08.19 # <[Saint]> nofunsies() 06.08.41 # lol 06.09.03 # <[Saint]> Sadly, there's no "big 'ol list of target defines". 06.09.48 # <[Saint]> not in a single place I mean. 06.14.52 # hmm so maybe a better idea is to define something if I want to enable.. then I only have to have one place like this #if (defined(HAVE_BACKLIGHT) || !defined(HAS_BUTTON_HOLD)) && !(defined(ARCHOS_PLAYER) || defined(ARCHOS_RECORDER)) #define SELBL 06.15.10 Join Strife1989 [0] (~quassel@adsl-98-67-59-148.mcn.bellsouth.net) 06.15.20 # any clue where I could do that like SOURCES or something 06.18.39 # alsoi I get a bunch of errors about the keymap being unsupported for iriverifp7xx 06.18.48 Quit Strife89 (Ping timeout: 250 seconds) 06.20.45 # I guess the better question is Where I should do it 06.23.27 Quit puckipedia (Ping timeout: 260 seconds) 06.24.29 Join puckipedia [0] (puck@puckipedia.com) 06.43.56 Quit [7] (Ping timeout: 240 seconds) 06.44.51 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven) 06.48.47 Quit PurlingNayuki (Ping timeout: 245 seconds) 06.52.19 Join PurlingNayuki [0] (~Thunderbi@2001:da8:215:4ff:7cbe:2c03:50ca:cbbd) 07.14.05 # Ok I guess the archos player is fine since the image gets compressed but the archosrecorder is still way over even after compression and this is with the current DEV build ie. Straight from the server 07.14.59 # error: firmware image is 324306 bytes while max size is 204800! >>Compression >> error: firmware image is 217202 bytes while max size is 204800! 07.15.56 Quit PurlingNayuki (Ping timeout: 258 seconds) 07.18.49 Join PurlingNayuki [0] (~Thunderbi@2001:da8:215:6905:2ce2:f3f6:d7c:ce6a) 07.21.53 *** Saving seen data "./dancer.seen" 07.28.19 Join edhelas [0] (~edhelas@145.133.43.230) 07.28.33 Join Harbec [0] (~Harbec@dsl-10-131-122.b2b2c.ca) 07.32.58 Quit Harbec (Ping timeout: 260 seconds) 07.39.15 Join wodz [0] (~wodz@iwl138.internetdsl.tpnet.pl) 07.39.35 Quit wodz (Client Quit) 07.39.58 Join wodz [0] (~wodz@iwl138.internetdsl.tpnet.pl) 07.53.49 Quit athidhep (Read error: Connection reset by peer) 07.53.49 Join athidhep [0] (~afoakf@unaffiliated/athidhep) 07.53.50 Quit edhelas (Ping timeout: 265 seconds) 07.53.50 Quit PurlingNayuki (Ping timeout: 245 seconds) 07.55.32 Quit athidhep (Quit: athidhep) 08.03.53 Quit cosmiclatte (Quit: AndroidIrc Disconnecting) 08.07.48 Quit amiconn (Quit: http://quassel-irc.org - Chat comfortably. Anywhere.) 08.07.48 Quit pixelma (Quit: .) 08.08.03 Join pixelma [0] (~pixelma@rockbox/staff/pixelma) 08.08.04 Join amiconn [0] (~amiconn@rockbox/developer/amiconn) 08.12.47 Join ender` [0] (krneki@foo.eternallybored.org) 08.13.16 Join girafe [0] (~girafe@LFbn-1-8015-136.w90-112.abo.wanadoo.fr) 08.30.05 Join PurlingNayuki [0] (~Thunderbi@114.255.40.10) 08.32.09 Quit fishbulb (Ping timeout: 268 seconds) 08.34.46 Quit PurlingNayuki (Ping timeout: 265 seconds) 08.43.56 Join edhelas [0] (~edhelas@145.133.43.230) 08.51.11 Quit edhelas (Ping timeout: 246 seconds) 08.53.17 Quit GodEater (Quit: Coyote finally caught me) 08.57.04 Join GodEater [0] (~whoknows@90.218.131.42) 08.57.04 Quit GodEater (Changing host) 08.57.04 Join GodEater [0] (~whoknows@rockbox/staff/GodEater) 09.01.17 Join petur [0] (~petur@91.183.48.77) 09.01.17 Quit petur (Changing host) 09.01.17 Join petur [0] (~petur@rockbox/developer/petur) 09.05.56 Quit Strife1989 (Ping timeout: 248 seconds) 09.06.16 Join Strife89 [0] (~quassel@adsl-98-80-190-200.mcn.bellsouth.net) 09.08.13 Join edhelas [0] (~edhelas@145.133.43.230) 09.16.36 Quit edhelas (Remote host closed the connection) 09.21.55 *** Saving seen data "./dancer.seen" 09.29.05 Join PurlingNayuki [0] (~Thunderbi@114.255.40.10) 09.29.36 Nick shiftymike is now known as shifttymike (~megal0man@unaffiliated/megal0maniac) 09.48.37 Quit girafe (Read error: Connection reset by peer) 10.09.05 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 10.15.35 # pamaury: I successfully compiled nwz toolchain with rockboxdev.sh from gerrit. Good work. 10.15.47 # great :) 10.17.00 # __builtin: button status is updatded once per tick (ie HZ rate) 10.18.44 # so there is no point in trying to read the button state faster than this 10.24.46 # [Saint]: there only is one Archos Player, no variants 10.25.54 # that's the one with the charcell display 10.34.15 Join ZincAlloy [0] (~Adium@2a02:8108:8b80:1700:ecc7:527b:eee:b98c) 10.35.05 Join rela [0] (~x@pdpc/supporter/active/rela) 10.38.50 # Bilgus: the fact that this is broken is probably not your fault and the fact that these warnings don't show up on the site is that they were surpressed at the time when it was clear that without a real big change rombox which is the thing broken IIRC would not be possible anymore. The firmware itself gets build still and works but only in the "load from disk" form not the "load from ROM". If the "ajbrec.ajz" file gets built and put in the zip you 10.38.50 # should be fine, I believe 10.41.56 Quit pamaury (Ping timeout: 240 seconds) 10.44.24 # one thing that comes to my mind without having checked your patch though - the backlight related part should be wrapped in an ifdef HAVE_BACKLIGHT or HAS... whatever is the correct term there as e.g. the stock Ondio does not have a backlight but softhold. There is the possibility for a backlight mod which then needs a custom firmware but I'd exclude it (in the correct way) 10.46.41 # I mean excluding for the majority but depending on the feature so that whenever someone builds an advance build with backlight it is automagically included 10.48.27 # advanced too 11.21.56 *** Saving seen data "./dancer.seen" 11.23.32 Join robertd1 [0] (~root@201.208.231.245) 11.23.34 Part robertd1 11.23.39 Join robertd1 [0] (~root@201.208.231.245) 11.25.52 Join xorly [0] (~xorly@193.85.203.185) 11.35.55 Quit robertd1 (Ping timeout: 268 seconds) 11.37.05 Join robertd1 [0] (~root@201.208.231.245) 11.38.52 # I think you guys might benefit from using lz4 compression - especially for graphics. 11.38.52 # https://community.arm.com/docs/DOC-10570 11.39.14 # https://cyan4973.github.io/lz4/ 11.39.14 Quit ZincAlloy (Quit: Leaving.) 11.41.40 Quit robertd1 (Ping timeout: 248 seconds) 11.42.17 # ... sorry correction to the github link ... http://github.com/Cyan4973 11.42.51 Join robertd1 [0] (~root@201.208.231.245) 11.44.25 # ... eh and of course ... lz4.org 11.45.27 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 11.49.30 # JensB: Not really. Al in all you need to have *decompressed* version in memory anyway. Storage space is cheap while RAM is precious on this devices. 11.50.58 # Well, you can of course compress the entire thing and load it into RAM and then decompress it into RAM - that is not worth anything. 11.51.20 # But if you compress each image used and store in Flash-memory, then you can decompress them when they need to be drawn. 11.51.37 # Thus you can sometimes have 400K on a 200K device. 11.51.52 # little gain for MUCH complexity really 11.52.16 # That means your program must be reduced in size. 11.52.40 # Otherwise it won't fit - because you can't expand the memory as the memory in the device is fixed. :) 11.53.33 # JensB: I'll happily evaluate patch if you propose one but trust me the gain will be little and added complexity huge. 11.54.31 # OK 11.54.55 Quit robertd1 (Ping timeout: 240 seconds) 12.13.55 Quit rela (Ping timeout: 240 seconds) 12.18.01 Join rela [0] (~x@pdpc/supporter/active/rela) 12.25.13 # pamaury: Do you know any free tool which can statically evaluate stack usage? gcc has -fstack-usage but this is per function. In theory you could combine this with callgraph (-fdump-rtl-dfinish might be useful) BUT I can't find any working tool to do that 12.35.03 Quit wodz (Ping timeout: 256 seconds) 12.36.14 # wodz: no, I have never tried to evaluate stackusage 12.36.45 Join fIorz [0] (nobody@rain.florz.de) 12.37.35 # hi 12.39.00 # I just installed rockbox on a Sansa Clip that the original firmware kept rebooting on on track changes and fun stuff like that, no such problems with rockbox! :-) Binary file /sites/rockbox.org/logbot/logfile matches