Search results

You can send to my gmail address...codertimt.

Cool, glad to hear that works. After research and finding that the id3 v2.4 calls for UTF-8 tags I was hopeful. You are correct about the file browser, even if you did save the file with UTF-8 encoding, the memory stick would have to mounted on the Wiz with a special flag for the fat...

I've attached a new test build which I think really fixes the db crash...of course I've said that before. I went ahead and updated the full builds also, but thought I'd go ahead and post this here also. It appears my mpd connection in the song db update thread was timing out and closing. And...

Okay, I believe I finally found it. I was fixing the wrong problem before, it needed to be fixed or the two databases could be out of sync, but it apparently wasn't causing our crash. I restructured the code(again) and was able to catch the condition of the segfault, it's a NULL pointer...

Okay, I'm 99% sure I have the db update crash fixed. The update takes place in two parts, first the mpd db is updated and then the song db that enables id3 tag browsing is updated. So as to not block the UI, the song db update happens in it's own thread which is supposed to wait on the mpd db...

Should be possible... UTF-8 supports the language. I included a font with the latest build that supports Korean... Probably going to have to restructure some stuff going forward though, the Korean font is pretty sizeable...will most likely offer as an add-on or something... Update the OP...

I will have to research some to find out what I need to do to make this happen. I'm pretty new to this whole character encoding thing. Do you happen to know what character encoding your ID3 tags are stored as? UTF-8? Unicode? Sure, why not. :) I put a link on the project home page.

Completely unintentional. I will get the corrected version in next full build as well and the other(s) mentioned and the corrected English version. Okay, from that I might be on the right track...I'll create another test build with some verbose output around the song db update. Hold button...

Unless something isn't working correctly it should be just like the f100/f200. 'A' in the library to append a folder, hold A to add folder as new playlist. In the playlist it should be hold A to delete item from playlist. Press select+start together to get key help on any screen... And thanks...

Original Post updated with link to version 0.4.3 and listing of changes.

I don't store that flag anywhere, so Im guessing mpd is restarting the db update when it gets killed before finishing. I'll have to research that a little to be 100% certain. 2000 songs is going to take a bit... I ran some benchmarks on the gp2x at one point but don't remember the exact...

AWESOME! New full build forthcoming soon. Probably be later tonight though. I've been informed yardwork comes first... :)

Sorry, I missed you're full post on this. Sorry you're having troubles. I haven't seen anything like this before and none of what you're describing here sounds "normal" at all... I would try a fresh copy to the SD card maybe and try again from the beginning? Pressing and holding the Menu...

Yes, you have to run the update command. One thing to be aware of is that there is delayed initialization for each section, so the first time you enter a section there will be a small(maybe 1/2 second) initialization delay before it's loaded...then when you visit is subsequently it should be...

Good to hear. Muchas Gracias :) I'll get it added to the next build. New build attached. SWSURFACE and no double buffering as recommended by Pickle. Pretty sure I never hit this combo in the other builds I've made..

Okay, I will give that a try. I know I tried both HWSURFACE && SWSURFACE with DOUBLEBUF, but might have only tried HWSURFACE without DOUBLEBUF, I will get another build in the beta section using just SDL_SWSURFACE... EDIT: I have positive results from the testing crew(aka sbock). Thanks Pickle.

I have a "flickering" issue I can't seem track down in Ommpc. It's not a bad problem most of the time, simply because I don't update that much of the screen that often, but there a couple scenarios where it presents itself pretty badly...and while I can also minimize those places, I'd like to...

Yes, the db update takes place in it's own thread...

I don't really have any guide, but I'll give a quick overview that will hopefully help... The "Playlists" screen From this screen you can load and save playlist and create a random or blank one. New Playlist creates a blank playlist, Random creates a playlist of 50 random songs. Save will...

There is in the Music Library section. There should be an text overlay stating "Updating Database". I'm not sure my reasoning for it only showing up there is valid, so I won't expound on it. I'll add that to me todo list...