Search results

Bummer. Thanks guys. Apparently I've misused the vsync code or possibly it can only be used with the minimal lib and not sdl. I guess I'll just make the changes to minimize the impact, but it still bugs me. Yep, turns out the keyboard is not supported yet. I saw the entries in the language...

Okay, two new test build executables trying to track down the flickering. The first is compiled without double buffering and the second is with Exophase's vsync code... http://ommpc.googlecode.com/files/ommpc2x-nodb.zip http://ommpc.googlecode.com/files/ommpc2x-vsync.zip Also, attached are...

Cool. Thanks. For now, I will probably change the keyboard not to display the keypress in the top corner which should get rid of most of the keyboard flicker. Then we'll have to see what other solution presents itself in the future...

Currently only looks for jpg. EDIT: Just changed the Album Art code to look for the following... {"cover.jpg", "cover.png", "folder.jpg", "folder.png", "Cover.jpg", "Cover.png", "Folder.jpg", "Folder.png", filename.jpg, filename.png, "AlbumArt.jpg", "albumart.jpg", "AlbumArt.png"...

Good to know, thanks. Did you update the paths in the config file, either via the settings menu or manually edit ommpc.conf? If so, then maybe try a couple of more time, there is currently an intermittent crash updating the db...

It doesn't do embedded, so it needs to be a file in the directory...Looks for AlbumArt.jpg, AlbumArtSmall.jpg, Folder.jpg, then just tries to grab the first jpg it comes to in the folder... Probably need to reexamine that list, but that is the current behavior.

I'm going to attach another file that outputs the target fps because there should have been a definite noticable difference in the fps. 1fps should have been unusable with massive delay between button presses. You probably wouldn't notice much at the higher fps, but some things like the...

Could you attach the file to a post...or email to me at my gmail address...codertimt. Thanks.

Another test build, defaults to 10fps. Accepts a new config file item "fps=??" to be manually added to the ommpc.conf file. So sometime you're feeling bored, you can try different values to see if it helps/hurts the flicker any...

Any difference in flicker on the settings page with the SWSURFACE build? I believe you see the flicker on the keyboard and the settings page because the screen is actually redrawn often at those times. Most of the time, we don't actually re-draw anything unless something has changed and needs...

Hey Stephan, if you get the chance, could you try the attached build and see if compiling with the SWSURFACE flag makes any difference with the UI repsonse. Thanks. Also, is the flickering only on the setting screen with the keyboard(you can also get the keyboard saving a playlist/bookmark)...

There has been some builds in the Beta section for the last few days, but I feel pretty good about it now, so thought I'd call it a release. First, the obligatory screenshots and then a quick description of what is in the 0.4 series. * Icon based menu system replaces popup menu, easily...

New build which should address two of these items. Still haven't attempted to track down the occasional db crash.... Link in OP. And another new build in the OP, that speeds up start time considerably and has some touch screen improvements...

Awesome, a translation! The file Is being read as utf-8 so I believe special characters such as umlauts should work if saved as utf-8? I live in the land where simple ASCII still rules so I don't have much experience with doing so... But I think I remember testing that and it working... Binding...

Thanks for the great feedback Stephan. I've been working on this for so long I forget about some of the "issues" that need to be fixed. Software vol turns on mpd's internal mixer to control volume as opposed to using the hardware mixer. It was introduced on the f200 to deal with the issue...

So, segfault in SDL_SetVideoMode? If so, I had the same and narrowed it down to using 32bpp. Changed to 16bpp and got my program to run... Can't really help beyond that as I don't actually have a Wiz. :) Hope you get everything going. Tim

The last beta I uploaded should have had the clock speed option modified to go up to 580 for the wiz...did you grab the latest?I was wrong about that...will be fixed. Also, if you did manage a save of the options, the player might be getting defaulted back down to 280 now when restarting...

Cool. Good to know. For other first timers...the first thing you're going to need to do is goto Settings->Update DB to get your music into the database... Well the first thing will be to setup paths in Settings->Options if they aren't correct... Anyway, latest build in the OP and here...

As long as MPD supports it(and I would think it would) I should be able to. I have to check and see what I might be doing wrong around that code... I will definitely take a look... Thanks and Thanks.

Great news! Could you try the attached build the re-enables hardware surfaces and see if that works with the 16bpp? Thanks...