Day Eleven - Linking In The “Database”
11 06 2008If you're new here, you may want to subscribe to my RSS feed. Thanks for visiting!
Just a quick post tonight.
Day Eleven and basically all mundane coding today. Linking in the “database” which is what is used to manipulate Audio that’s added to a project.
This means scanning meta tags of Audio files and extracting the name of the Audio track, artist, frequency etc and posting it to the “database” which doubles as the “project file” now.
This probably seems trivial but each Audio file format does it differently and some don’t have meta tags at all. So fiddly but it’s all working now.
Because MixAction is non destructive with Audio files any editing needs to be able to be “undone” and thus the database is the easiest way to handle this. The tables go way beyond just the meta data of course with the special effect settings, timings and so on for each track.
Also MixAction is not a “meda player” in the traditional sense. It needs to be able to play tracks without moving to the next track, or if the user chooses, do exactly that. Some tracks may need to cross fade into the next, some start instantly, some detect silence at the start or end of a track and so on. So there’s quite a few parameters to set potentially on any given track or track sequence.
Did some work on the application “icon”. Not set in stone yet and not ready for preview, will continue to play with it and get a few local eyes on it first.
OK. More of the mundande tomorrow with linking the Audio to the database and playlist but things are much more business like now in terms of work needing done.
Later…
Related posts brought to you by Yet Another Related Posts Plugin.
How are you playing the music files? Did you write your own decoding or are you using another library?
Hi Sohail,
Both actually. Originally I started out with a Direct-X wrapper I wrote and called functions from it. This worked nicely but there was a lot of stuff I wanted to do and wouldn’t have the time to extend it. So I purchased a library as well. The library is excellent, truly excellent, but there are some things that my original wrapper did a bit more flexibly (like scanning tags etc) so I use direct calls for that. Playback is now being handled by the purchased library however. I’ll probably provide more details on which one and so on at a date closer to release.