Thread: Archive

more info on the box, is it usb? etc...

Originally Posted by Nic

more info on the box, is it usb? etc...

First version is Serial. This can be used with a Serial to USB converter for now. We are working on a USB version as well.

Thanks

You missed the 6PM deadline....

Ill comment on the skinning engine.

There are many methods and depending on how you actually build the skin will determine which method you should go with. If there is going to be a full blown skinning app that can be used and never have to hand edit the text files, this would be the easiest approach (but also more work for you to support the skinning app, bugs etc). I like the method of using Up and Down images as it cuts down significantly on file management and saving out dozens of images for each element. That alone will turn me off from skinning any app (main reason i havent skinned winamp and wont try). I also think using percent instead of pixels is a good idea, who wants to count pixels and percentages are just easier to understand for the average joe.

I think using everything in the app as a seperate object like you stated is a good idea, that way you can skin (build) the app layout the way you want it to be, and add or remove anything you like.

Skinning FP is very easy, but still rough around the edges in that you have to hand edit, and the skinning app that is available could be more robust but still gets the job done and makes things a lot easier. The skinning app for PhoneControl is great. It even packages up the skin for you to make it easier to distribute to your fellow carpc brotheren

One idea i like is the ability to use up and down images, define the area that is the object, and also the ability to layer another image on top of this area, say an icon (image). So if i design a skin and someone likes it , but wants to change the icons but keep everything else the same they can just create new icon images, or sliders. So a hybrid method (no pun) of using up/down images with layered seperate images would rock. Gives the ease of use to first timers and more flexibility and power to those more experienced etc.

Scripting engine.
If you are using a scripting engine PLEASE make it as easy as possible. Something that does the scripting in the background would be nice. For example, if the play command is a 1 line function, it would be nice to just pick from a list of possible commands or elements and the script associated with that command or element would be used. If someone wants to go in and edit the script for that command so it does something else or combine functions into one element that too should be possible. Easiest for newbies and script pros will feel right at home.

I think you are on the right track.
A skin engine that will alow the user to completely change the look and functions of the app will please everybody and offer the maximum flexibility. If people want a mp3 centric driven player someone can create it, if someone else wants a menu centric player that also can be done, both running the same engine.

I posted a new update to the server.... use the following link for direct download:

http://www.hybrid-mobile.com/mp3car/mmc_alpha_508.zip
user: mp3car
pass: betanext

I am working on Beta 1 now. Skinning and other feature requests are being added.

Originally Posted by liquid_smoke

Ill comment on the skinning engine.

There are many methods and depending on how you actually build the skin will determine which method you should go with. If there is going to be a full blown skinning app that can be used and never have to hand edit the text files, this would be the easiest approach (but also more work for you to support the skinning app, bugs etc). I like the method of using Up and Down images as it cuts down significantly on file management and saving out dozens of images for each element. That alone will turn me off from skinning any app (main reason i havent skinned winamp and wont try). I also think using percent instead of pixels is a good idea, who wants to count pixels and percentages are just easier to understand for the average joe.

I think using everything in the app as a seperate object like you stated is a good idea, that way you can skin (build) the app layout the way you want it to be, and add or remove anything you like.

Skinning FP is very easy, but still rough around the edges in that you have to hand edit, and the skinning app that is available could be more robust but still gets the job done and makes things a lot easier. The skinning app for PhoneControl is great. It even packages up the skin for you to make it easier to distribute to your fellow carpc brotheren

One idea i like is the ability to use up and down images, define the area that is the object, and also the ability to layer another image on top of this area, say an icon (image). So if i design a skin and someone likes it , but wants to change the icons but keep everything else the same they can just create new icon images, or sliders. So a hybrid method (no pun) of using up/down images with layered seperate images would rock. Gives the ease of use to first timers and more flexibility and power to those more experienced etc.

Scripting engine.
If you are using a scripting engine PLEASE make it as easy as possible. Something that does the scripting in the background would be nice. For example, if the play command is a 1 line function, it would be nice to just pick from a list of possible commands or elements and the script associated with that command or element would be used. If someone wants to go in and edit the script for that command so it does something else or combine functions into one element that too should be possible. Easiest for newbies and script pros will feel right at home.

I think you are on the right track.
A skin engine that will alow the user to completely change the look and functions of the app will please everybody and offer the maximum flexibility. If people want a mp3 centric driven player someone can create it, if someone else wants a menu centric player that also can be done, both running the same engine.

Thanks! That is all I needed to hear. That is exactly where I am heading with this

Thanks again

Originally Posted by t00h0t

You missed the 6PM deadline....

I know... sorry. I posted the link in the MMC Alpha 5 Rev 7 thread. Let me know if that works for you.

One of my biggest issues with MP3's is that recorded music is not created equal. Some songs are loud, some are quiet. This could be the nature of the artist, but it could also be a result of a bad encoding. It would be really cool if we could somehow program each song to play louder or quieter via MMC. The settings would be retained in a database and reference everytime a track is played.

Example:
Song A: +15% volume
Song B: -5% vol
Song C: +25% vol
Song D: +-0% vol

You could even take that further and allow users to program EQ settings for each song.

Example:
Song A: +15% vol, 50hz +2db, 10khz -3db
Song B: -5% vol, 50hz -1db, 200hz +3db
Etc...

Should have posted this in the requests thread. Already copied and pasted.