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.

SofRaZorbacK: you can edit it yourself (IIRC you already have write access) - click on attach - then a list of the already attached files comes up and then you can choose "manage" and it lets you upload a new file then

01:02:04

Quit cynicalliberal(Read error: 148 (No route to host))

01:02:15

Nick cynicalliberal__is now known as cynicalliberal (i=chatzill@moobilenet6-55.ucdavis.edu)

_Amblin: that's cool. I look forward to more improvements in it. I gotta replace my ipod mini but need something that does audio books ok and rockbox appears to. Other than that, It looks like more ipods for me...

Hm, I don't see an error (at least it doesn't stop) and I don't push play, but it still appears as before/normal. I tried resetting the player settings more than one and deleted the whole .rockbox before updating (config, tag-cache and bookmarks where saved and restored)

well, I think I'll wait till "someone" uploads a new one. My rockbox updating script checks out the date of the bootloader on download.rockbox.org so I will notice when there's a newer version. The change isn't a feature I cannot live without ;)

JdGordon: I thought awhile back about adding a small header to the images that would give needed info about it so that a single bitmap function can be used for all types and no need to pass the sizes. Would simplify a lot of stuff really and is probably a fairly simple change.

"rsync −−delete -vrtm −−modify-window=2 ~/oggchive/ /oggpod/music/", which handles fat's bogus timestamps and also doesn't whine when it can't set the some unix-type permissions that fat doesn't support

The only thing that restricts use of ipod_control is that it's hidden. It's hardly a large stumbling block. You could just say "You can put files anywhere, but ipod_control is hidden so music in it won't be visible"

I honestly think the world would be better off if everyone had the false impression that ipod_control was off limits than if everybody had the false impression that ipod_control was a normal folder to rockbox, which it ain't

I still disagree. Any user stupid enough to deliberately put music in ipod_control and then lodge a feature request asking for that use case to work is really too much trouble than they're worth. They will cause support problems in many other ways other than just this way.

I'm sorry I'm making a big deal about this, but I read dozens of support requests a day about Rockbox, and I have very real firsthand experience about how "Someone told me that..." comes back to haunt, quite literally, me.

I think the danger of a new user putting their music in ipod_control, not seeing their music, and getting disgusted with the whole project, is a much more common and much more important case than the corner case that you're presenting of your hypothetical user who satisfies a ton of unlikely conditions and gets misled in the other direction.

You assume that the only trade was hundreds for dozens, but that's assuming you tell them nothing vs telling them they can't do it, and leaves out the case of actually explaining things to them, again.

sorry to return to this, but ... I don't think the central issue is truth vs. falsity. There are at least three potential responses to the question "where do I put my music": 1) anywhere, 2) anywhere except ipod_control, 3) anywhere except ipod_control and <insert explanation about hidden directories>. 1 & 3 are true statements, 2) is false. Yet response #1 causes many more support requests than response #2, which in turn causes a few more support requests t

I'm not sure if this has been covered before, forgive me if it has, but does the e200 charge when its plugged via usb while running rockbox? Or does it only just notice that its plugged in and that's it?

You can't really compare it to lossy formats on 'audio quality', because by definition, lossy formats cut bits of the audio. The whole thing is never there, the question boils down to whether or not your ears can hear the missing bits.

jbwan: 4G iPods, and certain other targets, have a problem that fits the symptoms he's describing. Which is why I mentioned that, and referenced him to a forum thread that should _actually_ solve his problems for the time being.

The build I referenced you to just leaves the processor at a faster (still safe, just doesn't save as much battery by slowing down) speed so that you don't have to change speeds, and don't trigger the freeze.

but, if we had a buffer for the text which got drawn after the rest of the image (for a rect) we could do that, and if the entire string is drawn into the text buffer scrolling would be simple, just grab a rect from the text buffer and paste it into the frame buffer

its hard to explain..... to update a rect first you copy the background for that rect, then youd copy the rect from the image buffer, then lastly you copy the rect for the text you want into the framebuffer

amiconn: for ticking reduction, what sort of high cpu frequency framerate loss on the remote do you think would be acceptable _without_ adding the remote ticking option? It seems the hot spot is around 75-80 fps down from 93.5.

The iPod button driver seems to call backligh_on without any filtering...before checking the queue status even. Caption Backlight floods the queue with backlight on messages when it's within the on time it's using.

I've had an iFP since about forever, since I found a very cheap waterproof case for it, but the WMA bootloader required I used a very specific firmware version with limited Original Firmware functionality.

Llorean: Do you have any idea what the "cutit.c" program is expecting as input? It's referred to in the wiki version of the Sansa install instructions as a way to extract the .mi4 of the original firmware from a Sansa.

LinusN: I thought the decision a bit over a year ago was that Bass/Treble shouldn't affect volume at all, allowing the user to clip if they wanted, but ensuring they had full control of their player. (Though I assume volume _raising_ with it is a bug)

markun: It's been suggested that the bootsplash functionality in the Gigabeat bootloader is removed and replaced by "silent booting" (i.e. the bootloader doesn't touch the LCD unless it needs to display an error message, or the user has pressed a magic button). This has been implemented on the ipod, sansa and H10 bootloaders so far...

OK, so my first idea is that a tool could be written to decrypt the .mi4 file in the hidden partition, write the RB bootloader back in its place, and then write the unencrypted version of the OF to an unused (but in a fixed location) part of the hidden partition. This just requires raw disk access to the device, which is already in ipodpatcher. This means no OF.bin on the FAT32 partition for the user to break.

B4gder: On your page, you mention that the hidden partition was slightly different after updating the BL without a new MI4, I was curious if you remembered about that difference before I went and investigated the dumps or something

markun: ok. What about the title in the system menu problem? I also could reproduce it but it seem that me and the reporter are the only persons that managed it. This is the first time I confirm the bug, that's why I ask

B4gder: Yes, your dump of sda2 seems to contain: A 512 byte header, the bootloader, some blank space (zeros) until 0x80000, another 512-byte header, then the mi4 file, then zeros to the end of the partition.

Llorean: If you can get e200tool working, an interesting first test would be to do "dd if=rockboxbootloader.mi4 of=/dev/sda2 seek=1025" to write the bootloader directly to the firmware partition. (I think you'll need Linux for that as well). You could then test putting back the OF's mi4 file.

Llorean: I just assume that most people use their daps with not the best speakers so that the dap isn't the weakest point in the chain. That wasn't a punch to you, just my abstract thoughts. I think (based on your phrase) that you don't take part on that discussions

cro: I'm very casual about my sound quality. I refuse to do double blind tests, because I *like* the fact that my brain thinks certain file types sound better, even though rationally I know I probably can't hear the difference.

linuxstb: The only differences between the /dev/sda2 with the official upgrade, and with PP5024.MI4 dd'ed in are at: 0x80005, 0x80006, 0x7810E1, 0x782D64, 0x782D65, 0x782D68, 0x782D8C, 0x782D90, 0x782D94, 0x782D95, 0x782D98, 0x782DBC, 0x782DC0

barrywardell: What do you think about storing the decrypted version of the OF in that hidden partition, instead of in a file on the FAT32 partition? That would mean changing the bootloader slightly to read it from there instead.

The first sector starts with "PPBL", followed by the length of the bootloader, which follows in subsequent sectors. Then it's empty until 512KB into the partition, where there is a "PPMI" string, followed by the length of the mi4 image, which is then in the subsequent sectors. The mi4 image itself also has a 512-byte header.

Hey guys, I have an idea, lemme hear what you think. Say your playing a game or watching a plugin, and you want to control the music (stop, play, next song etc), one presses the record button, then the stop, play, next button, and in the backround, the player responds without having to go to Now playing

Because when your in a plugin, or game, the play stop fas forward, rewind, are all being used. The record button will act like a shift key on a computer, for running operations outside of the present window

Bagder: i was playing around with the code, and i think the problem i'm running into with the lines on the top of the screen are due to the display init.... if i comment that out so it doesn't init the display, and then boot to OF.bin, no lines... if i put it back in and boot to OF.bin, lines on top