--- Log for 27.03.114 Server: dickson.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 3 days and 11 hours ago 00.04.56 Join nomada [0] (~nomada@static.197.9.251.148.clients.your-server.de) 00.09.54 # kugel: one issue there is that some codecs/libs expect pointers to not move (such as libmad, mod and others) between frames 00.10.43 # jhMikeS: the codecs are halted using the existing API. i.e. when the decode loop asks for more data 00.11.28 Quit Marex (Ping timeout: 268 seconds) 00.11.33 # they don't all work that way. libmad stores the pointer of the previous frame. things like mod grab a pointer to the buffer but are atomic and don't check it again 00.12.19 Join Marex [0] (~Marex@195.140.253.167) 00.12.28 # I'm looking at libmad 00.12.52 # really, I don't know all that might expect a pointer to be valid around the loop since it wasn't really a concern 00.13.05 # after it calls ci->get_command() it calls ci->request_buffer() 00.13.31 # atomic formats are locked in place, streaming ones are only shrinkable, not movable 00.13.53 # whether or not the buffer from request_buffer() is different or not is not known because the guard buffer migiht be used, no? 00.14.06 # it's a bit deeper in libamd 00.14.08 # *mad 00.14.48 # it might be, but that only limits request size 00.14.51 # the stream buffers are reset afterwards 00.15.53 # it worked for my (limited) testing too 00.15.55 Quit kuldeepdhaka (Quit: gone to fetch temporary death ;)) 00.16.27 # the concern is in the stream struct 00.16.51 # are there portalplayer experts around still ? 00.17.34 # jhMikeS: I don't see it, the old pointer is lost 00.19.08 Quit ZincAlloy (Quit: Leaving.) 00.20.12 # jhMikeS: I'm thinking this situation should be handled by all codecs, the pointer changes also when the buffer wraps around 00.20.39 # doesnt it? (I'm no expert in this area) 00.20.58 # possible I misinterpreted libmad/frame.c or just forgot after so long 00.22.18 # derp stream.c resets it all 00.25.25 # and mod.c? (maybe others) 00.26.43 # one case in mpa.c is unsound 00.27.06 # things are only reset if mad_stream_buffer is called but not if it skips it 00.27.45 Join us`0gb [0] (~0gb.us@c-50-137-60-25.hsd1.or.comcast.net) 00.29.22 # iirc it does that to byte-seek for a frame sync code 00.32.28 # jhMikeS: have you looked at the patch. does it look sensible ignoring the potential codec problems? 00.32.38 # maybe that just needs some minor tweaks 00.32.46 # so far, yes 00.33.34 # much as I can say right off the top of my head :) 00.33.37 # the idea was to halt the codec, safe the file offset, reset the buffer (and rebuffer), then restore the file offset and resume the codec 00.34.12 # I was surprised to find that everything needed was already there so the patch is rather simple in the end 00.35.30 # if the codec is about to request new data anyway, and buffering restores the stream properly (because of the stored file offset), then no audio samples should be lost 00.36.16 Quit GeekShad1w (Ping timeout: 240 seconds) 00.36.20 # oh yea, during that time the PCM buffer should just be drained, and it shouldnt take long enough to go empty 00.37.07 # If all else fails, we can just make it bigger 00.37.08 # sure, most times 00.37.35 # a hard drive spinup is pretty close to the limit as long as it's full 00.39.22 # "all else" always fails :) 00.39.25 *** Saving seen data "./dancer.seen" 00.40.05 # so, then, atomic format (this breaks "pin handle" expectations still) 00.40.19 # since it's just normal rebufferin from the pcm-side it's the same problem when the audio buffer goes low 00.41.09 # kugel: what if the buffer is low when you do the work? 00.41.23 # You'd basically combine both bad cases then 00.41.35 Quit tertu (Ping timeout: 240 seconds) 00.42.41 # gevaerts: buffering_reset() closes all handles (as soon as the buffering thread goes into the event loop), so if it occurs during rebuffering or just before that would be cancelled 00.44.37 # kugel: I mean, you're basically adding the buflib stuff time to the "regular" rebuffer time (including its spin up) 00.45.06 # would be nice to spin the hard drive before doing the realloc 00.45.14 # *for such targets 00.45.27 # So I suspect you'd need a larger pcm buffer, which IIRC means things like DSP change latency gets longer? 00.45.42 # indeed it would 00.46.10 # that shit really needs to not be like that but it's also sort of hard with crossfading 00.46.31 # gevaerts: normally the DSP setting items change the pcm buffer into low-latency when in the menu 00.46.58 # but you still initially wait for the buffer latency for the first change in a setting to be audible 00.47.31 # once it's drained it's maintains low-latency 00.47.51 # gevaerts: uhm, the worst case would be that it happens just after rebuffering has finished in which case the disk is still spinning 00.48.23 # if the disk is already spinning audio decoding can be resumed quickly, it doesnt need the whole file to be buffered 00.48.55 # unless atomic format 00.50.29 # fuck these :) 00.51.05 # haha...then I'll have to stick with an older revision myself :) 00.51.31 # * [Saint] doesn't think he could handle it taking any longer for DSP to catch up with the current state on some targets 00.51.34 Join Strife89 [0] (~Strife89@adsl-98-80-237-172.mcn.bellsouth.net) 00.51.44 # <[Saint]> For the Classic, it can be ~12s+ 00.52.16 # [Saint]: really DSP should be late, with raw codec output being stored, not processed audio 00.52.47 # you only get 12s if you're doing crossfade, it would otherwise be 3s 00.53.11 Quit pamaury (Ping timeout: 265 seconds) 00.53.13 # low mem gets 1s 00.53.18 # <[Saint]> Don't you make me give up my crossfade, ya'hear! 00.53.26 # * [Saint] shakes an old man fist 00.53.29 Quit Marex (Ping timeout: 245 seconds) 00.53.33 # crossfade gets death by snu-snu 00.54.38 Join Marex [0] (~Marex@195.140.253.167) 00.55.05 # <[Saint]> crossfade on automatic track skip only is one of my favorite settings. 00.55.07 Quit kugel (Ping timeout: 265 seconds) 00.55.52 # <[Saint]> Its either that, or go through 1.5TB+ and cut out all the annoying silent leads into tracks which the mastering artist thought should be there. 00.56.00 # I never use it except when fixing it or changing code, so I could say I've used it alot, but not because I use it 00.56.37 # <[Saint]> I have a 10s fade in/out on auto-changed tracks. 00.57.01 # <[Saint]> manual change doesn;t get squat. I want it NOW! 00.57.10 # * gevaerts looks at [Saint] in a despairing way 00.57.14 # Don't you like music? 00.57.55 # <[Saint]> Sure I do, that's why the silence at the begginning of needs to piss off. 00.58.02 # <[Saint]> :) 00.58.30 # <[Saint]> I don;t subscribe to this mastering artist knows best business. 00.58.42 # * jhMikeS puts gaps at the end of the rips to avoid this problem 00.59.05 # <[Saint]> ...wouldn;t that compound the issue? 00.59.23 # <[Saint]> Oh. Errr. I see. Right. 00.59.39 # [Saint]: you've just basically destroyed e.g. Beethoven's fifth with those settings 00.59.41 # no, the existing gaps on the media can go after the current track or at the beginning of the next 01.00.12 # becomes beethoven's 4.95th? 01.00.42 # <[Saint]> gevaerts: Ohhhh...what a shame. 01.00.55 # beethoven can't hear it anyway 01.01.11 # <[Saint]> You asked if I liked *music*! 01.01.47 # mewsic/muse-ick 01.02.09 # * gevaerts hunts [Saint] down 01.02.57 # Anyway, there's a *lot* of music that starts in a rather spectacular way. If you mute that, it's just not the same any more 01.03.06 # per-album audio settings maybe? :) 01.03.28 # jhMikeS: this is when the album changes :) 01.04.43 # <[Saint]> I don't _mute_ it, I just blend the futzing around in with the ass end of the last track so that the lead in isn't noticeable. 01.05.03 # <[Saint]> Though, you have to keep on your toes doing that as some masters like to do this to their albums themselves. 01.05.32 # * gevaerts doesn't get the entire concept 01.05.45 # <[Saint]> Albums you're supposed to listen to in full, start to finish. Nuts to that. 01.05.53 # Well yes 01.05.57 # Albums are a stupid idea 01.06.01 # And so are sonfs 01.06.02 # *songs 01.06.12 # *music* is what it's about, none of your muck :) 01.06.16 # and notes 01.06.23 # <[Saint]> I *HATE* those pesky sonfs...always messing up 'ma shit. 01.06.24 # who's got old man fist now? 01.06.51 # kids these days... 01.07.14 # [Saint]: as far as I understand it, you're still lowering the volume of the starting track 01.07.41 # indeed, fade-in 01.08.08 # All I'm pointing out is that with some music, that's just a crime 01.08.12 # though you can fade out with overlapping but just start without a fade 01.08.38 # <[Saint]> gevaerts: fortunately, its only you that listens to that music. ;) 01.09.07 # * gevaerts very strongly doubts that 01.09.40 # * jhMikeS does too, but also metal and such, sometimes back to back 01.14.02 Quit Scromple (Read error: Connection reset by peer) 01.15.42 Join GeekShadow [0] (~antoine@reactos/tester/GeekShadow) 01.17.02 Join Scromple [0] (~Simon@161.43.73.67) 01.18.29 Quit Marex (Ping timeout: 245 seconds) 01.19.54 Join Marex [0] (~Marex@195.140.253.167) 01.23.12 # * [Saint] wonders if RaaA could use DSP Manager 01.23.45 # <[Saint]> The fact that DSP Manager doesn't have a blacklist/whitelist makes things mightily annoying if you use DSP Manager and RaaA. 01.23.57 # <[Saint]> (RaaA gets a double dose of DSP magics) 02.07.35 # <[Saint]> Bah. 02.07.51 # <[Saint]> Damn this unstoppable force/immovable object bullshit. 02.08.18 # <[Saint]> I have hit the unavoidable wall where all the code for my theme is done, and it needs a "face". 02.08.27 # <[Saint]> I, however, am *not* an artist. 02.08.42 # <[Saint]> (despite what my forum profile may or may not say) 02.12.52 Quit Scromple (*.net *.split) 02.12.52 Quit TheSeven (*.net *.split) 02.12.52 Quit bthomson___ (*.net *.split) 02.12.52 Quit scorche` (*.net *.split) 02.12.52 Quit Beta2K (*.net *.split) 02.12.53 Quit soap (*.net *.split) 02.12.53 Quit onder` (*.net *.split) 02.12.53 Quit Cultist (*.net *.split) 02.13.35 Join onder` [0] (~onder@dyn-dsl-to-76-75-107-236.nexicom.net) 02.22.12 Quit |akaWolf| (Ping timeout: 268 seconds) 02.22.40 # [Saint] why not use squares of different colors as a placeholder 02.23.57 # <[Saint]> I don't need a placeholder. Its essentially finished Barring aesthetics. 02.26.36 # <[Saint]> I do have finny little text bits like "this is a button"; "also a button"; "will do something later" already. :) 02.27.24 # screenie! 02.31.04 Join ygrek [0] (~user@108.59.6.97) 02.39.28 *** Saving seen data "./dancer.seen" 02.42.39 Quit onder` (Ping timeout: 245 seconds) 02.47.14 Quit ygrek (Ping timeout: 245 seconds) 02.49.26 Join Scromple [0] (~Simon@161.43.73.67) 02.49.26 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven) 02.49.26 Join bthomson___ [0] (sid21436@gateway/web/irccloud.com/x-zkfmagmmqaoqvqwn) 02.49.26 Join scorche` [0] (~scorche@rockbox/administrator/scorche) 02.49.26 Join Beta2K [0] (~Beta2K@d24-36-136-246.home1.cgocable.net) 02.49.26 Join soap [0] (~soap@rockbox/staff/soap) 02.49.26 Join Cultist [0] (~CultOfThe@67.186.111.33) 02.49.55 Join onder` [0] (~onder@dyn-dsl-to-76-75-107-236.nexicom.net) 02.53.52 Quit Marex (Ping timeout: 252 seconds) 02.54.44 Join Marex [0] (~Marex@195.140.253.167) 02.57.59 Join ParkerR [0] (ParkerR@unaffiliated/parkerr) 02.58.06 # WOOOOOOOOOOHHHHHHOOOOO 02.58.13 # Bought a Sansa Clip Zip 02.58.20 # $32 after tax 02.59.59 Quit AlexP (Remote host closed the connection) 03.00.38 # <[Saint]> ParkerR: bit steep for a Happy Meal toy. ;) 03.01.49 Quit onder` (Ping timeout: 245 seconds) 03.01.49 # :P 03.02.03 # Full Rockbox and Rockdoom. I'm happy :) 03.02.20 # <[Saint]> Hmmmm. 03.02.44 # <[Saint]> Philosophical - in part: I don't think _any_ target now can have "full" Rockbox. 03.03.18 # Well looking at the themes for the original Clip it looked better than that heh 03.03.48 # <[Saint]> I was just postulating on ROMbox and other target-specific things. 03.04.08 # <[Saint]> I don't think there's a single target that makes use of the entire feature set. 03.04.18 # Do all these literally look all the same or is that some image error? http://themes.rockbox.org/index.php?target=sansaclip 03.04.35 # they're different images for me 03.04.54 # Well different images but the same general look 03.04.59 # <[Saint]> All look different to me. 03.05.11 # <[Saint]> I guess I need a screen grab from you to see what you're seeing. 03.05.21 # One step ahead :P 03.05.26 # http://i.imgur.com/hnMNGIn.png 03.05.27 # <[Saint]> Some look very _similar_, but, all different. 03.05.28 # you mean they're all the same color? the clip has a fixed color screen you realize? 03.05.37 # Oh 03.05.41 # I didnt realize haha 03.05.57 # 1 bit per pixel, colors are fixed 03.06.07 # <[Saint]> monochromatic screen. 03.06.13 # Ahh good to know. 03.06.30 # That explains why they were touting a 1.1" full color screen on the Zip lol 03.06.53 # <[Saint]> You'll soon get pissed off with the form factor of said screen. 03.07.02 # <[Saint]> Its about the worst shape possible. 03.07.17 # <[Saint]> Its like they tried to make a screen that would make cabbiev2 look as bad as possible. 03.07.30 # Heh I like Rockboxed 03.07.33 # So it looks ok 03.07.35 # <[Saint]> (and just about every other theme that isn't "fullscreen album art". 03.07.40 # <[Saint]> ) 03.07.41 Quit jhMikeS (Ping timeout: 264 seconds) 03.07.50 Join ygrek [0] (~user@108.59.6.97) 03.08.43 # <[Saint]> It makes DOOM so bad that you can't see enemy sprites until they're well within "kill you easily" range. :) 03.08.56 # I did notice that... 03.09.04 # you should be listening to music 03.09.05 # not playing doom 03.09.08 # <[Saint]> "Oh, that pixel in the distance is shooting at me...huh" 03.09.56 # <[Saint]> Its a cruel twist. 03.10.03 # <[Saint]> Enough RAM to load all the maps. 03.10.08 # <[Saint]> Not enough screen to see anything. 03.10.28 # :3 03.10.47 # I still kinda like it. My iPod Touch died a little bit ago so I wanted a cheap replacement 03.11.08 # And the Clip does what it does fairly great 03.11.19 # * [Saint] sees the themesite could make better use of available screen real estate 03.11.28 # <[Saint]> (rather like the forums) 03.11.31 # [Saint], ikr 03.12.31 # The individual theme pages stretch 03.13.14 # <[Saint]> Eeeeewwww...I get blue in your client? Ick. 03.13.33 # Huh? 03.13.50 # Oh haha I dont do multicolored nicks :P 03.13.52 # <[Saint]> Oh. Everyone that isn't you does. I see. 03.13.57 # Heh 03.14.22 # wrong, i don't use multicolored nicks either 03.14.33 # [Saint], you mentioned the Zip having enough RAM for the Doom maps. How do it compare hardware wise to the rest of the line? 03.14.45 # *does it 03.14.55 # Ignoring the screen :P 03.16.31 # I see Rocbox matches up with the linux kernel stable version lol (3.13) 03.16.34 Quit RiD (Read error: Connection reset by peer) 03.35.55 # [Saint], Oh also does the Zip have issues with USB storage? It doesn't seem to want to show up PC side and half the time disconnecting USB makes it panic and reboot. I've only been able to transfer files in Sandisk's firmware 03.36.42 # <[Saint]> I would love to know what we do to fuck Windows off so badly here. 03.36.45 Join onder` [0] (~onder@dyn-dsl-to-76-75-118-164.nexicom.net) 03.36.54 # <[Saint]> (this is Windows, yes?) 03.36.59 # Yeah 03.37.01 # Windows 7 03.37.16 # <[Saint]> Color me totally unsurprised. 03.37.32 # <[Saint]> Yeah, you'll need to get used to (if you hadn't already) using the OF for USB exclusively. 03.37.42 # <[Saint]> (or, get a better host OS ;)) 03.37.57 # Ahh ok. My only other experience has been an iPod Nano 1g and the USB worked fine in rockbox 03.38.34 # <[Saint]> All the Clip variants are affected AFAIK. 03.38.45 # [Saint], Arch on my small laptop, Windows on my laptop turned desktop :) 03.39.29 # <[Saint]> That's...quite a contrast. How do you not shoot yourself in the fact every time you transition from sanity to...Windows? 03.39.48 # <[Saint]> *s/fact/face/ 03.40.05 # :P well I do have my Windows themed a lot like I do linux and have cygwin 03.40.09 # Eases the pain slightly 03.44.31 # http://i.imgur.com/0U15Nnm.png 03.54.03 # [Saint], where is the OF music? I don't see it when mounted as mass storage 03.56.04 # <[Saint]> MSC/MTP weirdness. 03.56.17 # Aha it has to be in MTP 03.56.18 # Weird 03.57.12 # MTP on the Nexus 7 left a bad taste in my mouth 03.57.20 # Never liked it 04.08.22 Quit pixelma (Disconnected by services) 04.08.22 Quit amiconn (Disconnected by services) 04.08.22 Join amiconn_ [0] (amiconn@rockbox/developer/amiconn) 04.08.22 Join pixelma_ [0] (pixelma@rockbox/staff/pixelma) 04.08.24 Nick amiconn_ is now known as amiconn (amiconn@rockbox/developer/amiconn) 04.08.24 Nick pixelma_ is now known as pixelma (pixelma@rockbox/staff/pixelma) 04.08.26 # <[Saint]> JdGordon_: (just thinking about stuff) - how hard/easy would it be to decouple the image offset from the preload call? 04.08.50 # <[Saint]> (probably a bit vague) 04.08.59 # ParkerR: $30 for a ClipZ? I jelly. 04.09.18 # <[Saint]> I was thinking in some cases it maght make more sense to set the offset at the time the image is called. 04.09.30 # <[Saint]> Rather than when it is preloaded. 04.09.42 # Strife89, Bestbuy had if for what I thought was $34. Rang it up and it ended up being $29 04.09.46 # *it 04.10.08 # <[Saint]> The benefit here is that it would be possible to have all theme elements in a single bitmap separated only by their offset. 04.10.09 # A local sale? 04.10.32 # Strife89, well judging by it's $30 on Amazon its decent 04.10.45 # It was on their "Clearance" rack 04.10.52 # [Saint]: yeah, I think thats a bad idea 04.10.56 # Ahh. 04.11.04 # it would make very messy code to read for the displaying 04.11.41 # <[Saint]> I hate that if you want to display the same image at different offsets it needs to be proloaded twice. 04.11.57 # <[Saint]> (and we don't seem to be able to actually tell that its the same image, and *do* preload twice...) 04.12.36 # <[Saint]> It would be marginally better if there was de-dup in bufflib. 04.14.08 # <[Saint]> With my way of thinking a theme could consist of two images. A backdrop (if required) and a single bitmap comprising all other elements. 04.14.18 # Strife89, And considering I don't have Prime, it was nice gettings it for slightly cheaper and instant gratification 04.14.24 # *getting 04.14.27 # [Saint]: wait, what does offsets mean here? 04.14.34 # is it the offset into the bmp? 04.14.49 # <[Saint]> yes. 04.15.10 # yeah, apart from image strips I don't tihnk supporting anything like tha is a good idea for readability 04.15.52 # <[Saint]> I guess, then, I should be poking kugel for deduplication. 04.16.27 # <[Saint]> So that preloading 10 of the exact same images just to get unique offsets doesn't *actually* preload the same image 10 times. 04.16.41 # well, something like that could be done 04.16.50 # I'd be interested in an actual use case though 04.19.51 # If all you care about is not loading the same image file twice it could (potentially) be dead simple 04.20.08 # <[Saint]> Well. Lets ignore my use case, and offsets entirely. And focus on the (probable) situation where a user might want to preload the same image twice with different idents to handle a conditional state. 04.20.14 # <[Saint]> Yeah. Right. 04.20.18 # you'd still have multiple %xl(id, filename) lines with the same filename but that doesnt mean more space 04.20.25 # * [Saint] nods 04.20.37 # Why would you do that though? 04.21.31 # ignoring offsets, if you're preloading the same image more than once you're being a dill 04.22.21 # it would actually be *really* simple to do what you want 04.22.32 # <[Saint]> right. Ugh. I fucked that up. No. *not* ignoring offsets, that's kinda critical to my argument. :) 04.23.44 # <[Saint]> I understand about readability, but really, having the image offset coupled to the preload cal is balls. 04.24.22 # <[Saint]> I should be able to preload the image and then display it at any given offset with the draw call. 04.24.42 # <[Saint]> Not stack up as many preloads as I need offsets. 04.24.43 # in load_skin_bitmaps(), in the else{} case: 1) first check if img->loaded != true; 2) copy the filename before load_skin_bmp() overwrites it, 3) load_skin_bmp(), 4) loop through the remiander of the list and copy the buflib_handle to all the img's with the same filename 04.25.24 # [Saint]: I understand what youre saying, but imagine how horrible the display lines would look if you added 2 more params to each %xd() 04.25.33 # much cleaner to put that in the load 04.25.40 # <[Saint]> Ideally, all the proload call should care about is how many subimages the image has. 04.25.47 # <[Saint]> ...actually. Not even then. 04.26.03 # I disagree 04.26.29 # <[Saint]> %xd(foo, x,y) doesn't seem to bad to me. 04.26.37 # <[Saint]> (viewport relative, of course) 04.26.47 # the %xl() is literally "use this ID to draw [from x, y offsets] when I ask for it 04.26.51 # " 04.26.55 # <[Saint]> go to 0,0 if its left out. 04.27.19 # it would also be ambiguous 04.27.36 # She's a beaut' :) https://cdn.mediacru.sh/Uf1YPDla1739.jpg 04.27.38 # %xd(a, 3, 2) == image a, offset (into the strip) 3 item 2 04.28.22 # <[Saint]> I'll say again. WRT readability, I *do* understand...but, c'mon, its not like its human readable as-is. And with the fact that users can freely mix old and new syntax readability pretty much went out the window. 04.29.08 # <[Saint]> The code is human readable...by the author. 04.29.16 # <[Saint]> (sometimes not even then) 04.29.18 # that's a whole other problem :) 04.29.25 # but why should we try to make it worse? 04.29.41 # but my understanding is you want to make sure the same *image file* isnt loaded twice? 04.29.44 # <[Saint]> Personally, I don't think it is. But...yadda yadda, subjective. 04.30.55 # what about this argument then: with my suggestion changing the size (or position, or file) of an image would be a 1 line change, with yours it needs to be changed for every identifer use 04.30.58 # <[Saint]> Basically. Yes. If I can't manipulate the offset from the display call, I want to make sure that I'm not crippled if I preload the same image umpteen dozen times at different offsets. 04.31.40 # <[Saint]> The latter is acceptable. Though I personally believe the former is ideal, albeit disruptive. 04.31.57 Join ygrek_ [0] (~user@108.59.6.97) 04.32.10 # IIRC the whole .bmp is loaded, so try adding a few %xl() lines with the same filename and different id 04.32.17 # s/id/offset/ 04.32.27 # ignore ram usage, it will jus work 04.32.44 # with a few lines of code change that won't use any more RAM (well negligable amount) 04.34.57 Quit ygrek (Ping timeout: 240 seconds) 04.38.34 # [Saint]: consider this wps http://pastebin.com/50xdw68X 04.38.50 # which would you rather add or remove an image from? 04.39.03 # or change the image dimensions 04.39.29 *** Saving seen data "./dancer.seen" 04.40.15 Join Zarggg [0] (~zarggg@24.229.140.62.res-cmts.sm.ptd.net) 04.47.18 Quit us`0gb (Ping timeout: 264 seconds) 04.47.25 Join us^0gb [0] (~0gb.us@c-50-137-60-25.hsd1.or.comcast.net) 04.59.32 # [Saint]: ^ ? 05.01.46 # Rockboxed is bext WPS :P 05.02.32 Join amithkk [0] (uid4289@2buntu/writers/amithkk) 05.02.36 # <[Saint]> JdGordon_: the latter wouldn't bother me. 05.03.15 # thats what I'm proposing 05.03.51 # <[Saint]> Crap. Former. *former*. 05.03.59 # no backsies! 05.08.57 # Haha 05.16.45 # [Saint], I'm not sure how easy this would be to doo but: Instead of expanding the theme listing to fit width you could let the user choose their device and then when they hover on a skin have it pop up the device and skin image sorta like a little preview 05.16.51 # *do 05.22.20 Quit TheSeven (Disconnected by services) 05.22.36 Join [7] [0] (~quassel@rockbox/developer/TheSeven) 05.24.37 Quit Marex (Ping timeout: 240 seconds) 05.26.52 # [Saint], shitty mspaint mockup https://cdn.mediacru.sh/gXtHtq0q0RHp.png 05.32.39 Join Marex [0] (~Marex@195.140.253.167) 05.33.13 # we have the graphics for the various players, so probably not too hard to do, but we as a project don't do much web stuff 05.34.15 # <[Saint]> The general look and feel of the forum and theme site should say as much to the trained observer. 05.42.32 # [Saint], I have about red blob left of ammo https://cdn.mediacru.sh/-PGVlVJEsIsN.jpg 05.44.40 # lol 06.03.20 # It's weird having an FM radio and even weirder that I can actually record it. Heh kinda nice. 06.13.36 Join ygrek [0] (~user@108.59.6.97) 06.13.57 Quit ygrek_ (Ping timeout: 240 seconds) 06.16.11 # Is there any microphone decibel meter for rockbox? 06.16.59 Join tertu [0] (~quassel@174-20-41-3.mpls.qwest.net) 06.23.49 # <[Saint]> ParkerR: I believe the recording screen has a rec level IFF the screen is large enoguh. 06.23.55 Join goom [0] (~goomba@cpe-72-177-176-215.satx.res.rr.com) 06.24.04 # <[Saint]> (its hardcoded, so it may push it offscreen) 06.24.29 Part goom 06.24.43 # <[Saint]> proper rec screen skinning support has been a want of mine for a while now. 06.33.13 # <[Saint]> I probably should check that for you...but, I'm in a lazy mood so speculation is all you get for now. :) 06.35.08 # Heh I'd go check but its in the kitchen charging and I dont feel like getting up 06.35.16 # [Saint], high five for lazy :D 06.38.50 Join DTSyX [0] (~DTSyX@e179054195.adsl.alicedsl.de) 06.39.32 *** Saving seen data "./dancer.seen" 06.43.01 Quit DTSyX (Client Quit) 06.47.44 Quit x56 (Ping timeout: 252 seconds) 06.53.18 Quit tertu (Ping timeout: 265 seconds) 06.56.12 Quit ygrek (Ping timeout: 265 seconds) 07.08.14 Join |akaWolf| [0] (~akaWolf@188.134.9.161) 07.14.11 # [Saint] et whoever: Enjoy a beer on me ;) Donated $5 07.24.01 Quit amithkk (Quit: Connection closed for inactivity) 07.27.03 Join x56 [0] (~0x56@sillytitties.com) 07.33.58 Quit x56 (Quit: Peace) 07.44.07 Quit Zarggg (Ping timeout: 268 seconds) 07.44.41 # [Saint], I just now realized this has an OLED screen after reading the rockbox wiki lol 07.45.07 Quit amiconn (Remote host closed the connection) 07.45.07 Quit pixelma (Remote host closed the connection) 07.45.12 # <[Saint]> Wait....what? 07.45.19 # <[Saint]> You...you read the manual?!? 07.45.37 # <[Saint]> Oh. Wiki. Whoops. I misread. 07.45.54 # <[Saint]> Still, you just put yourself far ahead of the pack of most users. :) 07.46.00 Join pixelma [0] (pixelma@rockbox/staff/pixelma) 07.46.01 Join amiconn [0] (amiconn@rockbox/developer/amiconn) 07.47.03 # [Saint], heh I tend to read up when bored 07.47.13 Join x56 [0] (~0x56@sillytitties.com) 07.47.45 # <[Saint]> Polite. Courteous. Reads the documentation. Donated to the project. 07.47.50 # [Saint], now to find a nice dark theme :D 07.47.52 # <[Saint]> Am I being trolled? 07.47.57 # Nope :D 07.48.17 Quit JdGordon_ (Ping timeout: 240 seconds) 07.48.34 # <[Saint]> Find a qualified member of the opposite sex and breed. 07.48.36 # I've been around rockbox since my old blue iPod Mini 07.48.39 # <[Saint]> We need more of you. 07.49.05 # Doom in greyscale was fun 07.49.29 # <[Saint]> The mini is a fantastic target. 07.49.40 # <[Saint]> If the iPod Classic had a greyscale LCD I would be in heaven. 07.49.46 # Oh god, all the ipodlinux stuff for it too 07.50.26 # Those were great days 07.50.31 # 06:47:46 UTC <[Saint]> Polite. Courteous. Reads the documentation. Donated to the project. 07.50.33 Join fragilematter [0] (~fragilema@unaffiliated/fragilematter) 07.50.34 # IT'S A TRAP! 07.50.54 # <[Saint]> My thoughts exactly. 07.51.21 # he's trying to seduce you in order to get you to do things! 07.51.55 # Never... muhahaha 07.52.13 # [Saint]: also, http://themes.rockbox.org/themes/320x240/podone-r8-themesite/1-wps.png 07.52.34 # I loved that theme 07.52.38 # So freaking simple 07.52.44 # :D 07.53.00 # it's available for 320x240 targets (iPod Classic / Video) 07.53.10 # Then we got color and had to make them look pretty 07.53.13 # <[Saint]> ParkerR: regarding "dark themes", its an OLED, just turn the contrast (I think we call it brightness for some reason, I don't think we differentiate) down. 07.53.14 # <[Saint]> ;) 07.53.55 # Heh yeah what lead me to reading up was when I turned "Brightness" down it looked an awful lot like contrast adjustment 07.54.15 # <[Saint]> copper: while that is very cute, unfortunately it can't replicate the only actual good thing about greyscale LCDs. 07.54.21 # yeah :- 07.54.24 # <[Saint]> visible in full sunlight without a backlight. 07.54.25 # | 07.54.40 # Darker areas casting the shadow on the screen (not quite the right workd for that) 07.55.05 # s/workd/word/ 07.55.09 # <[Saint]> copper: nice work color matching, though. 07.55.20 # <[Saint]> Very, very close. 07.56.01 # cool 07.56.18 # I can't tell because I don't have an actual grayscale iPod to compare 07.56.36 # I think I still have the entire factory manual for my iPod Mini that I primted off forever ago 07.56.55 # I've wanted an iPod since it was first introduced in 2001, but I held off for 11 years! 07.57.10 # <[Saint]> Good thing too. 07.57.40 # <[Saint]> Barring the Mini, Color/Photo/4G and Video, they were all pretty shit. 07.59.05 # you just cited half the lineup :D 08.00.02 # <[Saint]> Oh. And the Nano1G, of course, but that's just a tiny flash Video. 08.00.36 Join ygrek [0] (~user@108.59.6.97) 08.00.37 # <[Saint]> n2G is rather powerful but sounds like ass. 08.01.19 Join DTSyX [0] (~Dominik_M@e179054195.adsl.alicedsl.de) 08.01.49 Join JdGordon [0] (~jonno@rockbox/developer/JdGordon) 08.02.02 # The green trapper-keeper just makes this all that much more legit https://cdn.mediacru.sh/z2abptj0jpsF.jpg 08.02.50 Part DTSyX 08.03.34 # Also the iPod superdock I never built https://cdn.mediacru.sh/peyCTOVudyRG.jpg 08.03.41 # Back when Engadget was good... 08.03.53 # That entire guide was on Engadget 08.04.56 # April 18th 2006 http://www.engadget.com/2006/04/18/how-to-design-your-own-ipod-super-dock-part-1/ 08.04.58 # ogod 08.05.20 # Too many memories! 08.06.07 # Paper shows that I printed it on March 14, 2008 08.09.26 Quit [Saint] (Remote host closed the connection) 08.10.49 # Bye bye... 08.11.09 Join [Saint] [0] (~saint@rockbox/staff/saint) 08.16.11 # [Saint]: wanna give g#776 a try? 08.16.13 # 3Gerrit review #776 at http://gerrit.rockbox.org/r/776 : 3don't load the same bmp image more than once in a skin by Jonathan Gordon 08.17.16 # [Saint], this is actually my first device with an OLED screen. :D 08.21.21 # Ok I lied... Pulse smartpen 08.21.28 # But that's the only two 08.21.49 # It is my first full color OLED though heh 08.24.08 Join ender` [0] (krneki@foo.eternallybored.org) 08.25.39 Join kugel [0] (~kugel@rockbox/developer/kugel) 08.26.00 # Woever takes the time to make these PDF manuals: thank you. I'm amazed at the detail 08.26.05 # *Whoever 08.30.59 # <[Saint]> It all derived from a single source with clever conditional trickery. 08.31.47 # Base example then modify slightly to match player? :P 08.32.05 # <[Saint]> ...not to diminish the effort that went into it, I mean, its just not quite as large an undertaking as it seems. 08.32.17 # Yeah I get that 08.32.32 # Still very helpful 08.32.33 # <[Saint]> We don't separately maintain 30 pdfs. Nuts to that. :) 08.32.45 # Heh 08.33.16 # [Saint], Done anything with your RaspPi as of late? 08.33.52 # <[Saint]> Nothing relevant to Rockbox. 08.34.20 # Well I get that. :P I remembered also talking to you a little bit in #raspberrypi 08.34.37 # why doesn't rockbox on clipzip have single key keylock? 08.34.49 # Although thanks for the idea... portable screen plus the SDL build on the Pi heh 08.35.18 # is it possible to easily hack the power button to be a keylock in keymap? 08.35.30 # e.g. in player mode? 08.35.50 # Well short press of power already is a back up/exit 08.35.51 # <[Saint]> ygrek: not easily, no. 08.36.03 # And long press is power off 08.36.16 # <[Saint]> hence the reason why it requires 2 keys to begin with. 08.36.18 # ParkerR, it is not very needed in player mode - agree? 08.36.34 # <[Saint]> the key maps are VERY crowded. 08.36.34 # I couldn't even get the two key to work. Pressing power and select didn;t seem to do anything 08.36.38 # yes, I understand that there are not enough keys :) 08.37.18 # <[Saint]> Which is one if the reasons why softlock takes two keys to begin with. 08.37.28 # <[Saint]> *one of 08.38.12 # <[Saint]> This edit would be possible, but extremely non-trivial to implement consistently. 08.38.46 Join DTSyX [0] (~dtsyx@e179054195.adsl.alicedsl.de) 08.39.02 # Oh I was thinking "home" was short power press haha 08.39.23 # <[Saint]> And we wont have different key(s) doing different things in different screens unless its absolutely unavoidable. 08.39.35 *** Saving seen data "./dancer.seen" 08.39.44 # I see.. 08.39.46 # Woo double negatives! 08.39.50 # :P 08.39.50 # is there support for double click? 08.39.56 # <[Saint]> No. 08.40.21 # <[Saint]> Just long/short press. 08.41.03 # all other buttons long presses also occupied? 08.41.11 # there should be a way out! 08.41.23 # :'-\ 08.41.27 # <[Saint]> yes. they are. 08.41.33 Quit DTSyX (Client Quit) 08.42.41 # <[Saint]> The current implementation makes it very unlikely that softlock will be accidentally engaged or disengaged. 08.43.02 # <[Saint]> Which is a huge disadvantage of having it as a single key. 08.43.02 # and makes it very unlikely to press with one hand.. 08.43.17 # <[Saint]> That's part of the point. 08.43.50 # <[Saint]> If it can be disabled easily, it is useless as a soft lock. 08.43.54 # I believe using the power button for navigation was a bad choice from the beginning 08.44.22 # <[Saint]> We don't care about what the original firmware does. 08.44.33 # <[Saint]> or how keys are labeled. 08.44.49 # just that the power button is not easily pressed 08.44.55 # accidently 08.44.56 # [Saint]: I use the same image at different spots without preloading more than once since... aaages in my theme. Just set up different viewports, %xd is viewport relative 08.45.00 # <[Saint]> We try to use a consistent key map across all our devices. 08.45.57 # <[Saint]> So what the key is _supposed_ to do isn't necessarily what it will do in Rockbox. 08.46.16 # yeah, not a nice UI if you ask me, but nevermind :) 08.46.25 Join newbie|2 [0] (~DTSyX@e179054195.adsl.alicedsl.de) 08.46.28 # can you please point me how is long press handled 08.46.35 # I mean can't seem to find it in keymap 08.47.15 # <[Saint]> button repeat. 08.48.37 # home+repeat is used for quickscreen 08.48.47 # I wonder if I can change that to be a keylock.. 08.49.13 # for a personal hack 08.49.21 # <[Saint]> You could, yes. 08.49.31 # btw, what about having a keylock as a menu item in that quickscreen? 08.49.44 # like a general solution? 08.50.02 # or is it not really the problem here? 08.50.07 # Kinda remonds me of those old VFDs https://cdn.mediacru.sh/GzgLoEdggHvM.jpg 08.50.11 # <[Saint]> We would need to change the quickscreen in that case. 08.50.24 Quit newbie|2 (Client Quit) 08.50.30 # <[Saint]> Or, add a (pretty much pointless) soft lock menu item. 08.50.43 # <[Saint]> Quickscreen only displays static menu items and settings. 08.50.44 # *reminds 08.50.54 # why pointless? 08.51.10 # <[Saint]> Because no one wants to dig through a menu to find a soft lock. 08.51.12 # if the blind predefined seq on actions leads to keylock - it is ok 08.51.21 # if it is only two presses - it is fine 08.51.38 # <[Saint]> We are *very* reluctant to add new menu items. 08.51.40 # quickscreen is callable from anywhere with one long home press? 08.51.43 # argh! 08.51.59 # <[Saint]> To add a new menu item it needs a justifiable use case. 08.52.03 # that's understandable, considering how crowded is it 08.52.05 Join bertrik [0] (~quassel@rockbox/developer/bertrik) 08.52.06 # <[Saint]> And this (sorry) doesn't. (IMO) 08.52.33 # so that's the question - do people find the current keylock "good enough"? 08.52.41 # What exactly is being discussed? The Home + Select locks seems fine here 08.52.43 Join Zagor [242] (~bjst@rockbox/developer/Zagor) 08.52.49 # *lock 08.52.49 # ok, will try a personal hack for now 08.53.01 # <[Saint]> The only we we have to measure "good enough" is people not complaining. 08.53.04 # ParkerR, the home + select is not doable with one hand -> baaaad 08.53.07 # <[Saint]> And, they don't. SO...I guess? 08.53.12 # I complain! :) 08.53.12 # Ahh 08.53.29 # <[Saint]> Yes. But you are one in a rather large number. :) 08.53.59 # how one gathers a majority here? bribing, lobbying, any other approved methods? 08.54.14 # <[Saint]> With edge cases like this unless we really do have a gaping hole in the functionality we'll usually point to the sources and the licensing. 08.55.47 # * ygrek agrees and saddens 08.56.25 # <[Saint]> Allowing users to map out custom keys is a rather sensitive issue here. 08.56.44 # <[Saint]> There really is no way to do it nicely that won't potentially end in a support nightmare for us. 08.57.26 # ygrek, I don't know about you... https://d1wst0behutosd.cloudfront.net/videos/13780.mp4 08.57.27 # considering the specifics of the device (7 keys) - looks like 08.57.51 # ParkerR, what theme is that (old VFD) 08.57.53 # ? 08.58.26 # http://themes.rockbox.org/index.php?themeid=1650&target=sansaclipzip 08.58.34 # ParkerR, looks rather convoluted! 08.58.43 # True! :D 08.59.12 # ygrek, I agree with you that a one handed would be nice but more with [Saint] on the issues with implementing it 08.59.38 # <[Saint]> Being able to operate it so easily defeats the purpose. 09.00.07 # <[Saint]> Its _supposed_ to be slightly difficult to (dis)engage. :) 09.00.09 # that's why all phones out there come with a keylock that requires three hands to unlock it (sarcasm) 09.00.37 # btw old nokia dumbphones have a keylock with two keypresses 09.00.42 # from the quickscreen 09.00.49 # or at least I configured it so iirc 09.01.37 # actually 3 keypresses - get to the main screen, invoke context menu, click on the first menu item 09.01.45 # unlock was two keypresses 09.01.53 # <[Saint]> This debate (or the root of it, rather: end-user customizable keymaps) comes up maybe once or twice a year. 09.02.11 # I didn't mean user-customizable 09.02.14 # <[Saint]> And the usual consensus ends up being that there just plain isn't a nice way to safely implement it. 09.02.46 # still, what about an option in a quickscreen? 09.03.14 # * ParkerR points to the sources :P 09.03.17 # keylock -> one key press to get to QS, one click (if it is a first item) to lock the keys 09.03.26 # i.e. you will accept such patch? 09.03.26 # <[Saint]> That would mean we would have to change the way the quickscreen behaves. But that may not be a bad thing. 09.04.06 Quit Marex (Ping timeout: 264 seconds) 09.04.15 # <[Saint]> Currently the quickscreen will only accept settings, which this isn't. 09.04.53 # ok, will see how much hacking energy I will have on this one, maybe with some luck it materializes in something 09.04.55 Join Marex [0] (~Marex@195.140.253.167) 09.06.18 # <[Saint]> The problem would be disabling it again. 09.06.37 # <[Saint]> Enabling it with the quickscreen...yeah, I can maybe see that. 09.06.41 # <[Saint]> What about disabling it? 09.06.58 # hm... 09.07.14 # I don't how the keylock is handled inside 09.08.13 # that depends whether it is possible to hook at the point when keylock actually prevents key presses 09.08.20 # I dunno 09.08.42 # Keys lock, can't unlock haha. That would be quite the issue 09.10.42 Join kuldeepdhaka [0] (~kuldeepdh@unaffiliated/kuldeepdhaka) 09.11.22 Join maruk1 [0] (~papier@titanium.v6.sdv.fr) 09.16.38 Join petur [0] (5bb7304d@rockbox/developer/petur) 09.17.45 Quit [Saint] (Remote host closed the connection) 09.18.54 Join [Saint] [0] (~saint@rockbox/staff/saint) 09.19.50 # The wiki mentions a diagnostic mode on the OF of the Clip Zip. Is this user accesable? Kinda want to see it for shits. (Kinda like digging into the iPod diagnotic tests) 09.25.16 Quit onder` (Ping timeout: 240 seconds) 09.25.20 Join onder`_ [0] (~onder@dyn-dsl-to-76-75-118-164.nexicom.net) 09.25.38 Nick onder`_ is now known as onder` (~onder@dyn-dsl-to-76-75-118-164.nexicom.net) 09.30.56 Quit bertrik (Ping timeout: 240 seconds) 09.35.42 Quit ygrek (Ping timeout: 265 seconds) 10.06.50 Quit mc2739 (Ping timeout: 245 seconds) 10.07.07 Quit kuldeepdhaka (Ping timeout: 265 seconds) 10.09.00 Join mc2739 [0] (~mc2739@rockbox/developer/mc2739) 10.09.18 Join kuldeepdhaka [0] (~kuldeepdh@unaffiliated/kuldeepdhaka) 10.09.23 Join ygrek [0] (~user@108.59.6.97) 10.26.26 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 10.39.38 *** Saving seen data "./dancer.seen" 10.51.22 Quit pamaury (Quit: No Ping reply in 180 seconds.) 10.51.31 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 10.56.31 Join ikeboy [0] (~ikeboy@ool-435622d3.dyn.optonline.net) 11.47.36 Quit bluebrother (Disconnected by services) 11.47.41 Join bluebrother [0] (~dom@rockbox/developer/bluebrother) 11.48.55 Quit fs-bluebot (Ping timeout: 245 seconds) 11.50.22 Join fs-bluebot [0] (~fs-bluebo@g226071223.adsl.alicedsl.de) 11.52.36 Quit ikeboy (Quit: Leaving) 12.20.27 Join jhMikeS [0] (~jethead71@rockbox/developer/jhMikeS) 12.39.29 Join cmhobbs [0] (~cmhobbs@ip98-186-66-92.fv.ks.cox.net) 12.39.40 Quit cmhobbs (Changing host) 12.39.41 Join cmhobbs [0] (~cmhobbs@fsf/member/cmhobbs) 12.39.42 *** Saving seen data "./dancer.seen" 13.07.36 Quit kugel (Quit: Lost terminal) 13.16.16 Quit Marex (Ping timeout: 240 seconds) 13.16.57 Join Marex [0] (~Marex@195.140.253.167) 13.41.44 Quit cmhobbs (Ping timeout: 255 seconds) 13.44.14 Quit ygrek (Ping timeout: 268 seconds) 13.50.17 Join amayer [0] (~amayer@mail.weberadvertising.com) 13.50.40 Quit amayer (Read error: Connection reset by peer) 13.58.39 Quit Marex (Ping timeout: 252 seconds) 13.58.50 Join einhirn [0] (~Miranda@2001:638:605:4:4c9f:7078:3d7a:b56d) 14.00.01 Join Marex [0] (~Marex@195.140.253.167) 14.08.38 Join amayer [0] (~amayer@mail.weberadvertising.com) 14.09.01 Quit amayer (Read error: Connection reset by peer) 14.25.28 Join amayer [0] (~amayer@mail.weberadvertising.com) 14.28.18 Quit alucryd (Quit: Alucryd out.) 14.28.49 Join ygrek [0] (~user@108.59.6.97) 14.36.24 Join alucryd [0] (~alucryd@dou59-1-82-238-54-125.fbx.proxad.net) 14.36.24 Quit alucryd (Changing host) 14.36.24 Join alucryd [0] (~alucryd@archlinux/trusteduser/alucryd) 14.38.44 Quit Marex (Remote host closed the connection) 14.39.03 Join Marex [0] (~Marex@195.140.253.167) 14.39.43 *** Saving seen data "./dancer.seen" 15.04.13 Quit amayer (Quit: Leaving) 15.05.10 Join amayer [0] (~amayer@mail.weberadvertising.com) 15.08.20 Join amayer_ [0] (~amayer@mail.weberadvertising.com) 15.10.15 Quit amayer_ (Client Quit) 15.10.28 Join amayer_ [0] (~amayer@mail.weberadvertising.com) 15.11.11 Join amayer__ [0] (~amayer@mail.weberadvertising.com) 15.12.09 Quit amayer__ (Client Quit) 15.12.09 Quit amayer_ (Client Quit) 15.12.22 Join amayer_ [0] (~amayer@mail.weberadvertising.com) 15.13.25 Quit amayer_ (Client Quit) 15.13.34 Join amayer_ [0] (~amayer@mail.weberadvertising.com) 15.18.37 Quit Strife89 (Ping timeout: 240 seconds) 15.23.06 Quit amayer_ (Remote host closed the connection) 15.31.26 Quit kuldeepdhaka (Ping timeout: 265 seconds) 15.34.07 Join kuldeepdhaka [0] (~kuldeepdh@unaffiliated/kuldeepdhaka) 16.05.07 Quit mc2739 (Read error: Connection reset by peer) 16.06.01 Join mc2739 [0] (~mc2739@rockbox/developer/mc2739) 16.19.39 Quit the-kyle (Remote host closed the connection) 16.28.03 Join the-kyle [0] (~kyle@kyle.tk) 16.29.30 Join krnlyng [0] (~liar@83.175.90.24) 16.39.44 *** Saving seen data "./dancer.seen" 16.40.34 Join ikeboy [0] (~ikeboy@ool-435622d3.dyn.optonline.net) 16.42.56 Quit us^0gb (Quit: http://0gb.us/) 16.45.36 Quit krnlyng (Remote host closed the connection) 16.47.26 Join krnlyng [0] (~liar@83.175.90.24) 16.50.36 Quit amayer (Quit: Leaving) 16.51.57 Quit kuldeepdhaka (Ping timeout: 265 seconds) 16.52.12 Join Strife89 [0] (~Strife89@2602:306:bce1:8c20:395b:9c9b:c5fa:86af) 16.56.43 Quit ikeboy (Quit: Leaving) 16.58.51 Join kuldeepdhaka [0] (~kuldeepdh@unaffiliated/kuldeepdhaka) 17.04.40 Quit Wardo (Quit: Blarglarg) 17.05.54 Join rela [0] (~x@pdpc/supporter/active/rela) 17.09.12 Join RiD [0] (RiD@2.83.28.205) 17.25.04 Quit rela (Read error: Connection reset by peer) 17.33.04 # gevaerts: are there still pp developers in the project ? I mean people who know the not-written-anywhere details of the soc 17.33.26 # pamaury: Try waking up amiconn 17.33.39 # He's not very active these days, but he is in the channel :) 17.36.20 # amiconn: ping 17.37.26 # damn, the portplayer platform is a mess ^^ 17.39.02 Quit Strife89 (Ping timeout: 265 seconds) 17.41.02 Quit petur (Ping timeout: 245 seconds) 17.46.29 Join AlexP [0] (~alex@rockbox/staff/AlexP) 17.47.55 Quit Zagor (Quit: Clint excited) 17.55.29 Quit the-kyle (Remote host closed the connection) 17.56.57 Join Strife89 [0] (~Strife89@2602:306:bce1:8c20:442c:50cc:c691:9d4f) 18.16.42 Quit einhirn (Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org) 18.25.35 Quit krnlyng (Remote host closed the connection) 18.26.28 Join bertrik [0] (~quassel@ip117-49-211-87.adsl2.static.versatel.nl) 18.26.28 Quit bertrik (Changing host) 18.26.28 Join bertrik [0] (~quassel@rockbox/developer/bertrik) 18.39.48 *** Saving seen data "./dancer.seen" 18.41.10 # pamaury: I could possibly answer something, depending on the target and which area 18.42.12 Quit maruk1 (Quit: Leaving.) 18.47.03 # jhMikeS: I would like background knowledge on the portalplayers, like where does the information we have comes from and then some more technical points like are the cpu and cop running at the same frequency and things like that 18.47.34 # I'm working on the sansa view which uses "pp6110" (it's called GoForce but it's very similare to pp5522) 18.47.52 # Alot from iPod Linux initially and more reverse engineering after that 18.47.57 # Maybe other sources 18.48.01 # I don't know 18.48.11 # But the cores run at the same frequency, yes 18.48.44 # you're dusting off the View port after all these years? 18.49.03 # someone offered me one so yeah I'm having a look 18.49.16 Quit kuldeepdhaka (Ping timeout: 240 seconds) 18.49.30 # why didn't the View port work out ? 18.50.13 # There was stuff from Mr. H 18.50.16 # everything PP is undocumented, and was reverse engineered at great difficulty 18.50.41 # the 6000 series eventually became tegra, and was only ever used in one or two devices, so no one was enthusiastic about it 18.51.10 # IIRC e200tool was half working on it (code execution but no ability to talk to NAND so you couldn't really do anything) 18.51.30 # then sandisk dropped PP in favor of AMS 18.52.32 Quit ygrek (Remote host closed the connection) 18.52.51 Join ygrek [0] (~user@108.59.6.97) 18.53.45 Join the-kyle [0] (~kyle@kyle.tk) 18.55.46 # I see 18.58.08 # I'll see where it goes :) 18.58.09 # not saying you shouldn't go for it, just saying it may not be good for your sanity :) 18.58.31 # I think I've lost all sanity at RE a long time ago ^^ 18.58.49 # you should finish that sansa connect port 18.59.01 # i think its almost all working except a way to install without modding the hardware 19.00.57 # isn't it hard to find ? 19.01.55 # ah no idea 19.02.37 # and what are the chances I find some installl method ? 19.02.48 # yeah i'm just kidding 19.03.21 # are you low on devices these days/ 19.03.26 Join kuldeepdhaka [0] (~kuldeepdh@unaffiliated/kuldeepdhaka) 19.03.52 # he's baby sitting my Fuze+ :P 19.04.15 # no, I just need something else because always working on imx233 is kind of boring and frustrating 19.04.19 # was going to say i can probably dig up some hardware that i won't have time for 19.04.27 # so you want PP????? 19.04.52 # imx was too documented and not buggy enough 19.05.36 # i want something where the cache coherency doesn't work and different memory addresses have different access speeds because memory controllers are hard 19.05.41 # it's buggy enough ^^ I have zillions of tcc based players but they all use NAND which is a pain to handle 19.06.16 # i think funman has my old Nano 2G if you want to play around with that 19.06.33 # not so sure, I'll stick with my players for the moment 19.06.43 # could probably also find you a classic 6G (no nand at all!) 19.06.55 # I still have much work to finish: finish rbutil install for some imx233 devices, and finish FTL RE too 19.07.15 # what about just replacing the FTL with the Nano 2g one? 19.07.55 # lack of interoperability 19.08.02 # with the OF? 19.08.20 # and basically if you break the FTL on those devices, there are high chances the OF won't even boot so then it's a pain to flash a new bootloader 19.09.04 # don't they have a nice failsafe USB mode? 19.12.14 # yeah but that doesn't help because 1) you need special tool to upload code 2) you need a special build to upload to be able to read/write the firmware. So it's not exactly user friendly to update the bootloader this way. 19.12.27 # The OF provides vendor SCSI commands to do that which is much nicer 19.12.41 # of course we could implement them but then that's more work 19.14.37 # ah ok, i assumed they would still work with a broken NAND 19.14.57 # unfortunately not 19.26.07 Join krnlyng [0] (~liar@83.175.90.24) 19.33.17 Join lebellium [0] (~chatzilla@89-93-178-161.hfc.dyn.abo.bbox.fr) 19.37.55 Join b0hoon [0] (~quassel@078088056108.bielskobiala.vectranet.pl) 19.41.19 Quit Strife89 (Ping timeout: 265 seconds) 19.45.03 # pamaury: i had a working slice of code for the lcd of View but i've lost it, i could try to recreate it maybe slowly... :) 19.45.26 # everithing else is a black magic and it must be reversed 19.45.58 # i stuck on the ATA controller and gave up and then i've lost the code fot the LCD :S 19.52.52 Join amayer [0] (~amayer@mail.weberadvertising.com) 19.52.54 Quit amayer (Read error: Connection reset by peer) 19.53.09 # b0hoon: that's a shame :-/ 19.54.26 # I've currently reversing the bootloader 19.58.14 # yeah i was too fast in reinstalling linux distro 19.59.09 # it is a bit of a pain that the BL is written in C++ but at least it's compiled with type information so it's makes the job much easier 20.00.02 # but first of all, original bootloader needs NVIDIA,0,0 magic in some place i don't exactly remember in order to boot our crafted mi4 image 20.02.07 Join Rower [0] (~husvagn@h176n2-aeg-a11.ias.bredband.telia.com) 20.04.15 # actually it's a check before writing it to flash through the recovery mode 20.04.42 # but i don't remember details now 20.04.46 # something is unclear to me: are the registers shared by the cop and cpu or are some duplicated ? 20.05.04 # for example the MMAP_* 20.06.53 # don't know really... there is no any documentation about SoC 20.07.36 # i know for sure that the 8-bit ports are to the T letter :D 20.08.17 # on the first bit of port T is the state of the power button IIRC 20.08.27 # or maybe HOLD 20.09.24 Join amayer [0] (~amayer@mail.weberadvertising.com) 20.09.33 Quit amayer (Read error: Connection reset by peer) 20.15.27 Join b0hoon_ [0] (~quassel@public-gprs591612.centertel.pl) 20.17.49 Quit b0hoon (Ping timeout: 255 seconds) 20.25.58 Join amayer [0] (~amayer@mail.weberadvertising.com) 20.28.19 Quit amayer (Read error: Connection reset by peer) 20.29.51 Join amayer [0] (~amayer@mail.weberadvertising.com) 20.36.14 Quit amayer (Read error: Connection reset by peer) 20.37.39 Join amayer [0] (~amayer@mail.weberadvertising.com) 20.37.44 Quit krnlyng (Remote host closed the connection) 20.39.29 Quit mc2739 (Ping timeout: 264 seconds) 20.39.49 *** Saving seen data "./dancer.seen" 20.41.02 Join mc2739 [0] (~mc2739@rockbox/developer/mc2739) 20.42.36 Quit amayer (Ping timeout: 240 seconds) 20.55.37 Join amayer [0] (~amayer@mail.weberadvertising.com) 20.56.52 Quit Rower (Read error: Connection reset by peer) 20.57.50 # Build Server message: 3New build round started. Revision f8d367b, 253 builds, 32 clients. 21.02.35 # Build Server message: 3Build round completed after 285 seconds. 21.03.17 Quit ygrek (Ping timeout: 265 seconds) 21.03.55 # :O wtf 21.07.15 # Fun! 21.07.23 # [Saint]: ping 21.07.53 # [Saint]: your build client is broken 21.09.54 # on storebror-daniel it looks worse 21.10.12 # Yes, but bagder's not in here. I pinged him in #rockbox-community 21.10.48 # * gevaerts blocks both of them for now 21.26.38 # Build Server message: 3New build round started. Revision ee1a1ce, 253 builds, 31 clients. 21.29.48 Join newbie|3 [0] (~DTSyX@f051012185.adsl.alicedsl.de) 21.33.28 # Build Server message: 3Build round completed after 410 seconds. 21.33.47 Quit RiD (Ping timeout: 255 seconds) 21.33.56 Quit |akaWolf| (Ping timeout: 265 seconds) 21.34.13 # now it's better 21.38.02 Join habys [0] (~luke@arikui.org) 21.38.07 # Apparently I tried to often to "recall" my account password and now my account is said to be banned because my nickname sounds like spam...?! Very strange. Anyways, I'd like to get my account unbanned, please. Thanks! 21.38.54 # Uuups, KVirc did change my nickname, it's supposed to be DTSyX 21.39.04 Join |akaWolf| [0] (~akaWolf@188.134.9.161) 21.39.25 # Which account? 21.40.27 # same name: DTSyX 21.40.32 # forum? 21.41.04 # Ah, found it... 21.41.05 # http://forums.rockbox.org/index.php?action=profile;u=25883 21.41.24 Join tertu [0] (~quassel@174-20-41-3.mpls.qwest.net) 21.41.28 # Someone banned forums*@* 21.41.34 # rockbox. isn't this the #rockbox irc chat? That would explain why my nick isn't correct either... 21.41.36 # * gevaerts removes that 21.41.49 # newbie|3: it is, but we have accounts in more places :) 21.41.59 # Anyway, working on it 21.42.20 # Ah, I see. I never used irc before... never had to :-) 21.42.28 # Ok, thanks a lot! 21.42.59 # Unfortunately handling bans on the forums is *slow*, so I'll need a few minutes... 21.44.28 # No worries, I'm not in a hurry. I was just changing my email address and apparently after the change I was mistyping the right password so I tried a lot of wrong ones and got banned... 21.45.17 # It's not that. We've had a spam wave a few weeks ago, and some of the resulting bans were overly broad 21.46.22 # Ok. That's a unpleasant coincidence. :-( 21.46.53 # * gevaerts nods 21.48.26 # * gevaerts taps his foot impatiently waiting for the forums to respons properly 21.50.28 Join RiD [0] (Ghost@2.83.28.205) 21.50.29 # Well, I see the problem now: I changed my email address to one that contains "forum". That would explain it. With all the data leaks in the last few month I wanted to have different email addresses for different purposes to be maybe able to see were (future) leaks are coming from. 21.51.07 # Ah, yes. That explains the entire thing :) 21.51.24 # scorche|sh: we really need to fix the forums in some way... 21.51.35 # Ah! 21.51.36 # i think i banned spammers from doing [randomuser]@forums.rockbox.org.spammershost.com 21.51.44 # newbie|3: can you try again? 21.51.53 # saratoga: this one was on forums*@* 21.51.53 # there was some bot net that liked doing that 21.52.04 # oh 21.52.07 # 14 hits, I imagine most of those being from newbie|3 21.52.24 # And the spam wave is over now anyway 21.52.40 # pamaury: pong 21.53.08 # * amiconn also just updated the android toolchain for his build client 21.54.14 # It works now, I got in. Thank you very much! 14x, that seems about right... If the first try is a typo you try every other one exept the right one again... classic... 21.55.04 # So, I can keep the "forum*@*" mail address for my account? 21.55.31 # Yes 21.56.47 # Great. Thanks! 21.57.10 # You're welcome, and sorry about the trouble 21.58.30 # That's ok. That way I finally had to use and get to know irc... :-) 22.00.22 Quit Zambezi (Quit: Suspended: Expired) 22.02.06 Quit newbie|3 () 22.02.16 Join DTSyX [0] (~DTSyX@f051012185.adsl.alicedsl.de) 22.02.33 Quit RiD (Read error: Connection reset by peer) 22.04.25 Quit DTSyX (Client Quit) 22.05.08 Join DTSyX [0] (~DTSyX@f051012185.adsl.alicedsl.de) 22.06.56 Join RiD [0] (Ghost@2.83.28.205) 22.07.12 Join rela [0] (~x@pdpc/supporter/active/rela) 22.12.25 # Thanks again and good bye. 22.12.42 Quit DTSyX () 22.14.15 Quit the-kyle (Ping timeout: 240 seconds) 22.23.39 Join ZincAlloy [0] (~Adium@pD9EE92E7.dip0.t-ipconnect.de) 22.23.46 # gevaerts: ah - i thought we werent having much spam lately 22.24.00 # scorche|sh: no, that part is fine 22.24.14 # But doing anything with the ban list is still horrendous 22.24.57 # gevaerts: either way, there shouldnt be much banning necessary - for user bans, move them to the banned membergroup...for IP and email bans, you do need to ban, but those should be pretty few and far between 22.25.20 # Well... 22.25.32 # This one was about removing a ban :) 22.25.35 # rasher, thanks for the Android builds. Kinda fun to use on my Nexus 7 :D 22.25.42 # gevaerts: ah - there is that... 22.26.06 # whaouh! cabbiev2 for YH-820! Never late than never :) 22.26.09 # Better* 22.26.25 # Never late than never haha 22.26.32 # :( 22.29.19 # ParkerR: My contribution is minimal - but thanks still 22.32.08 # rasher, Well considering I'm too lazy to set a toolchain up, it helps :) 22.39.52 *** Saving seen data "./dancer.seen" 22.45.40 Quit ender` (Quit: The likelihood of Perl being involved in a system is directly proportional to the length of time the system has been in maintenance.) 22.57.26 Quit rela (Read error: Connection reset by peer) 22.59.26 # Is it possible to save a recording to a folder other than root? I've tried a few keypresses while hoverded on recording name but can't seem to get a kyeboard up to type anything 23.00.19 # Oh theres a set as recording directory option for hovering on a directory 23.00.20 # Neat 23.01.28 # Ctrl + F'ing the manual sure is nice 23.01.33 # :3 23.19.08 Join the-kyle [0] (~kyle@kyle.tk) 23.24.59 Quit amayer (Quit: Leaving) 23.39.19 Quit kuldeepdhaka (Quit: alha aphis) 23.40.36 Quit lebellium (Quit: ChatZilla 0.9.90.1 [Firefox 29.0/20140324101726]) 23.45.28 # Build Server message: 3New build round started. Revision 0eae33c, 253 builds, 30 clients. 23.47.53 Quit pamaury (Ping timeout: 264 seconds) 23.52.36 # Build Server message: 3Build round completed after 428 seconds. 23.53.48 Part b0hoon_ ("GTG... Bye.")