I think I found a solution for that. Am going thru it lets see what can be done.
I am planning to use SQLlite (http://www.sqlite.org/index.html). It an embeddable SQL database engine. Its small, the dll is about 220 KB and fast.
Regards
Satish
Printable View
I think I found a solution for that. Am going thru it lets see what can be done.
I am planning to use SQLlite (http://www.sqlite.org/index.html). It an embeddable SQL database engine. Its small, the dll is about 220 KB and fast.
Regards
Satish
@ryguy: now, then try nevertheless once MediaCar ... ;)
I understand the problem not completely.
I provide the playlist before...
In the car one plays anyway only after more existing Playliste .
Per album a playlist. Then i do not search - i only play music ...
Does your that make differently?
While driving? How do you concentrate you on traffic?
Voice activation my friend :)
I dunno guys, all i have to say is i am glad database is being added and who cares if it overkill if it is only 220k. Also i hope there will be some sort of rating system so you can build smart playlists. If this train of though continues lets start a new thread
@ryguy:
On the motorway, with open windows and loud music? I would like to see the speech recognition, which works still error free ;)
Functioned not times the 100% in the quiet room.
But you are right - if it functioned, is it a very good alternative to the mouse, Touchscreen...
@antimatter: YES!
I just wanted to backup ryguy on the sql database issue. You don't have to use Microsoft's bloated SQL server. There are much lighter alternatives like MySQL and SQLLite.
SQL is VERY fast and VERY efficient. For the simple database we will be using to keep track of songs, even an old EPIA 800 would be able to execute queries with will very little use of CPU. In fact, it will probably use less CPU power for searching through 1000+ songs than ANY other solution (assuming the index tables are created properly).
Once a database is built of your mp3s, it will be very easy to do searching and browsing. Also, it will make it easy to add any new features in the future related to finding and organizing your music and videos. It supports storing cover art along with the song info as well, right in the database as a binary field.
I could go on and on, but it looks like Satish is already sold on the idea. :D BTW, SQLlite is definitely the way to go. It is slower than SQL for creating indexes but it is almost twice as fast for executing queries.
Finally I was able to complete the preview alpha version of VOICES (Media App) . It can be downloaded from. http://voices.techworldonline.com/0.0.0.1/ . Now its time for me to switch off the PC for some time before I get a list of Bugs ;)
Regards
Satish
I think the whole application should be built around the database.
All navigational favorites should be stored in the database. Route history; so you can pull up and get directions to places you have already been.
Video files should be in there too, I woudl also suggest that we have a shuffle feature for the video files so you can watch them on a random basis (mobile mtv).
I think the app would run best and would also be the most versatile if everything was stored in the database.
What do you guys think?
I'm no programmer, but from what you are suggesting, the app would require a major rewite. SA has done a great job so far. The original 'voices' changed my view of SATNav being a pain to being enjoyable to use. I don't think you should try to dictate how someone else should write their apps. If you feel that strongly then why not write your own app.Quote:
Originally Posted by ryguy
Sorry to be annoying but thats just my point of view :D
No i'm not suggestion sat rewrites the app. I'm just stating that we should utilize the database for more than just the mp3 collection. Yes sat has done a great job coding this app...and i've been communicating with him from the beginning regarding suggestions. That is all it was bud, so take it easy ;)