Click in the nick column to highlight everything a person has said.
The icon identifies that the person is a core developer (has commit access).

Notice: Only Gecko based browsers prior to FF4 support the multipart/mixed "server push" method used by this log reader to auto-update. Since you do not appear to use such a browser, this page will simply show the current log, and not automatically update.

kugel: i don't know much about how sound libraries work, but I think most let you specify the volume you want to the OS mixer, which then adjusts the amplifier output power in conjunction with digital gain adjustments

saratoga: I know that some of my Windows apps will change volume within the app if I use volume keys, but also allow me the option to disable this so that the volume keys adjust the host OS volume instead.

there's also some mixer part, but I had the feeling it's more about the output mixers (not sure if the term is correct, I mean that what you see when running alsamixer). I might have another look thoughj

I need to figure out how to get code running on a Telechips 8200 cpu. I know I need to prepend a header, but how do I get started? There is a LOT of code for the Cowon D2 that I've been sifting though, but it's hard to filter out the basic bootloaderish stuff. I'm simply trying to make a 'hello world' of sorts for now. Blinking the backlight is the goal, and it should just take either GPIOF or GPIOB.

IMO the Cabbie themes should also be fairly heavily commented, to give users a better idea of which part of the code does what. I'd be happy to put a patch together, but it might not be something I can do immediately.

you are allowed to draw (images) in the default viewport. I guess the reason is just that cabbiev2 was designed before viewports or when viewports, especially conditional viewports, were still fairly new. And since they "just work" no-one bothered to clean them up yet.

if you like working on it go ahead. :) And while you are at it, I'd like every port to show volume in dB instead of the icon while adjusting - it was added to the Clip port but not others (an colour targets I imagine that in yellow font too)

S_a_i_n_t: I'm not sure I agree that Cabbie should be a _demo_ theme. It's the _default_ theme. Maybe instead of heavily commenting cabbie, it would be more useful to do a new theme, designed to be a demo, using as many WPS features as you can.

linuxstb: When the other shipped themes are taken out of the release builds (which *will* happen eventually, that's the reason they were all added to the themesite), then Cabbie will have to serve the purpose of being both the default *and* the demo theme. The idea I believe is to update the code of Cabbie as heavily as possible without changing its appearence.

S_a_i_n_t: That logic doesn't follow... The demo theme doesn't have to be shipped with Rockbox. In fact, I would doubt anyone would want to use it, as it would have too many features. But of course, commenting cabbie would also be a good thing.

if someone else works on it, it might give me incentive to finally make the c200 port use a 10-pixels tall font, using the screen estate better - one more line possible which can finally show playing time info

GodEater: My intention is not to change the appearence of Cabbie *at all*, just to update the code, and decrease the total size of the theme by using progressbars for the battery and volume and kicking the bitmap strips out.

I'm starting to think that there is little point waiting for the skin buffer resizing patch so I'm going to make the buffers large enough to fit (IIRC mutlifont doesnt work on some targets because the buffers are too small anyway) and commit the fm patch

there's a few pointers to fix, you need a file per font, you may have to have more than one per font if you load the font into different size buffers at different times (one theme uses it as main font, one as a skin font?)

Torne: I really dont think the skin fonts need to bother with loading from a cache file. I would have no problem with the 60k setting font loading from a disk copy and the others using the first 10k of glyphs and then let the cache sort itself out

hows this for a fun idea... have something read every tag on your DAP and keep a count of how often each glyph would be required. Then have it write the stats out to a txt file, then fix bdf2fnt to be able to write the glyphs on disk in an order by those stats?

sure, but the system still works (in theory anyway) if you have a huge font where each glyph takes 50K. A Page-based system needs to be able to load a full page, so we'd have to check what that means for all fonts

wodz: The convention (rightly or wrongly) is to use the 4-char string that is stored in the file header as the parameter to the -add option. IIUC, you're still only storing 4 chars in the file, but using a 5-char string as the argument?

funman: I wan't to keep the current 2-thread model. I was hoping I would just need to add a new entry point to the thread and simply switch between the two. However, I would have to rewrite a bit more than I imagined if I wanted to add a callback.

What do you people think about the way to select between UMS and MTP ? And on top of that, select HID or not. How do you think it should be handled ? I need to implement somthing before being able to commit something and the discussion never ends up with a solution each time I ask :)

pamaury, gevaerts: speaking of USB - would it be possible to probe the host OS if it can deal with USB composite device correctly? Just an idea I had because switching HID on and off ge ts a bit annoying (using my c200 on XP and MacOS 10.4)

pixelma: not easily not. You can probably determine which OS it is by looking at the sequence of descriptors it ask (for example Windows doesn't ask other speed descriptor iirc). But that's not reliable imo.

pamaury: if I have HID enabled then I can't access the device, and HID controls usually don't work. There's one weird exception though if I let a program run called "USB prober" HID works at least but I still can't access the device

linuxstb: take me, for example. I wrote the fft plugin, do something rbutil related every once in a while but don't have committer access. Hey, I'm not complaining, I prefer using FS# - keeps me disciplined and moves some of the weight off my shoulders. But every once in a while, I have to test something on a multitude of targets and it takes *long* to do it by hand.

S_a_i_n_t: you know, there is a valid scenario where that could happen with linear. If there's a single spike, it might get zeroed out during the averaging but (I think) it would still influence the scaling. Meaning, everything would display as either 0 or 1 pixel at the bottom. That's obviously wrong but was done to save an iteration through the results (reuse a loop).

guess I am just very confused by the steps i need to take. so i should download the bootloader and ipodpatcher from the thread, plus the current build for a iPod 80gig from here: http://build.rockbox.org/

syrius: you shouldn't have to delete this part of the path (if I understand your question correctly), I believe Rockbox still tries to find the subfolders. I am not sure with this part of the linux paths, did you try?

saratoga: as I said the last time we discussed it, the fft is not the bottleneck - the lack of PCM data is. Therefore, unless I find a way to get more data, there's hardly any point in doing the transform faster (won't increase perceivable speed).

gevaerts: getting paid to install something doesn't mean you're distributing the software, as I understand it hes just downloading our binary and putting it on the disk, so I think we're still distributing it

Why is it that after selecting "Advanced - Voice Build" you get rewarded with a confirmation telling you what you already know (that you selected a voice build) instead of it just going "righto, I'll create that makefile for you..."?

kugel: I was actually thinking about that the other day - since we use fixed-point numbers so much, can't we not add a utility function that's like %f but for fixed-point numbers. Might come in handy :)