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.

unlike the rockbox windows encoder, which will not touch the aspect ratio. it will letterbox the video on my tiny screen, which is not terrible, but i was actually hoping to scale it when the video was wider than my screen, and crop the sides

MU{lappy}: you know, i think i figured out the problem (im obviously no expert). my video is one resolution, my display is another. i can tell any encoder to make this file into a 220x176 version of itself, and it will, but of course it will be skewed.. iow, it's not gonna crop off the video...

i *still* hit trouble w/ mencoder, and i've been using it for a good number of years now. framerates tend to be a common source of trouble, especially in MPEG sources where the source framerate may vary

also, is your input interlaced, telecined, or progressive? it's fairly unlikely to be progressive, and if it's interlaced it *might* look better deinterlaced, and telecined will almost definitely look better detelecined.

well, it /is/ tangentially relevant. perhaps if we get to the right answer, someone will see it, update the wiki, and everyone converting video for their sansas running rockbox wont be hosing their aspect ratio

Llorean: because it doesn't involve messing w/ the file itself, i would think. i'm just trying to think of a way that might be considered more acceptable than slapping APEv2 or ID3 tags onto files that aren't really expected to support them.

and it looks like adding APEv2 reading is simple enough that i wouldn't mind maintaining it in a custom build if it weren't wanted upstream. my only real concern is that the codec might try to "play" the tags.

in theory yes, but you have to give the timestamp as an integer to use the time-based selection (not sure if there is even a tag defined for it). By default, the commit count (times the db has been updated) is used

Bagder: I think an open feature request tracker is still a good idea, but I do agree it doesn't really "work." How would you feel about having a 100% separate tracker, just for feature requests, that's not reviewed? Then, if anything from it gets implemented, they can submit a patch, and if we see anything we like, we can move it to the official feature request one (alongside bugs/patches currently)?

Meanwhile we'd have a clear place for people to voice. Some devs would read it now and then. And it would give us someplace to say "go read through this for ideas" if somebody says "What can I work on?"

I didn't say "but it will be ignored." I mean we make it clear that "it is merely wishes, and there is no guarantee that any ideas on this tracker will be seen or responded to by a developer in a timely manner, it is just a place to gather them so that if a developer goes looking, they know where ideas can be found"

Having an open tracker, and a closed feature tracker (where we can move features once they become officially "planned" like viewports was) accomplishes this, I think, without just telling people "Instead of posting to the tracker, post to the mailing list, and remind us every 3 months of your idea until we reject it, then remind us every six months hoping our opinions change"

A feature that one person wants, is trivial to implement, and will literally have zero performance impact is more likely than a feature thousands want but isn't wanted by the core devs, or perhaps is wanted by them but requires a rewrite of the playback code.

i wanted to switch to this a while ago.. and gave up for lack of help.. but now.. i tried to delete some songs on my ipod.. and tho it says in settings that the stuff is there...the directories are empty

and "You can distinguish the iPod classic from the iPod (5th generation) by the last three digits of the serial number. The iPod classic serial number's last three digits will be one of the following: Y5N, YMU, YMV, and YMX."

alright, but can somebody help me, http://pastebin.ca/1052645 take a look at that and can somebody tell me whats wrong, i changed the key maps and changed the gigabeat to the gigabeat s, and under rockbox i get nothin

fml: I've never experienced something like a hang at the end of the playlist, but if you can reproduce it and there's no flyspray entry for it already, I think you should open one and add a clear description of the problem (and a reproduction recipe if possible)