[WIP] The Paper Street Soap Company (mockups and development of a new skin concept) - Printable Version
+- XBMC Community Forum (http://forum.xbmc.org)
+-- Forum: Development (/forumdisplay.php?fid=32)
+--- Forum: Skin Development (/forumdisplay.php?fid=12)
+---- Forum: WIP Skins (/forumdisplay.php?fid=160)
+---- Thread: [WIP] The Paper Street Soap Company (mockups and development of a new skin concept) (/showthread.php?tid=86501)
- blacklist - 2011-02-18 22:48
clock2113 Wrote:I don't know anything about scripting, but I could make source sounds...
I'd love to hear what you come up with
It looks like XBMC needs them in .wav format.
- joebrady - 2011-02-19 01:37
clock2113 Wrote:If there is a page turn sound, there needs to be like 10 subtly different ones that round robin; hearing the exact same .wav file EVERY TIME would get old really fast...
10 pretty subtle ones for ya.
- blacklist - 2011-02-19 03:44
Nice find Mr. Brady. Thank you, Sir.
These are actually working out quite nicely.
- joebrady - 2011-02-19 03:53
I surprised myself on that find.
"I really like what you're doing, great job doing it!"
Super stoked about this skin, can't wait to get a crack at it.
- blacklist - 2011-02-19 04:43
joebrady Wrote:I surprised myself on that find.
Just loaded a few in at random and they sound pretty tight. Might have to go in and drop the level on them (they seem a little loud to me) but otherwise I think these are probably what we're going with.
As far as randomizing goes... not 100% sure if we can or not, going to see what can be done with sounds.xml. We have a random number python script we use elsewhere, so I'm thinking we might be able to bring that into play to pick one of the sounds at random.
- blacklist - 2011-02-19 06:43
Just did a bunch of research in optimizing XBMC's database. Seeing HUGE improvements in speed here, so I thought I would gather the info together. Of course, this is for the MySQL database solution (which I highly, HIGHLY recommend).
ALTER TABLE SONG ADD INDEX idArtist(idArtist);
ALTER TABLE SONG ADD INDEX idGenre(idGenre);
CREATE INDEX idAlbum_idx ON song(idAlbum);
CREATE INDEX idArtist_idx ON song(idArtist);
CREATE INDEX idArtist_idx ON album(idArtist);
CREATE INDEX idArtist_idx ON exartistsong(idArtist);
CREATE INDEX idArtist_idx ON exartistalbum(idArtist);
Movies: ALTER TABLE movie ADD INDEX ix_idFile(idFile);
TV: ALTER TABLE episode ADD INDEX ix_idFile(idFile);
(I made up that last one my self, but it stands to reason that it would work as well)
Still looking for more optimizations of the video database.
- garyi - 2011-02-19 09:16
I wish I knew what you were on about.
- blacklist - 2011-02-19 09:23
garyi Wrote:I wish I knew what you were on about.
I'm trying to find a way to reduce the database bottleneck in xbmc to make up for loading this skin so full of python, etc. I already use MySQL as the database instead of sqlite that XBMC ships with. Running those SQL commands will create new index keys that result in a pretty healthy speed increase for database calls, therefore making the whole interface a bit snappier.
Make more sense now?
- ronie - 2011-02-19 16:08
blacklist Wrote:this is for the MySQL database solution (which I highly, HIGHLY recommend).
is MySQL faster than sqlite?
blacklist Wrote:Music Indexes:
so one can speed things up by altering some tables?
- blacklist - 2011-02-19 16:53
ronie Wrote:just wondering....why?
1. I do find it faster.
2. Its a heck of a lot easier to deal with from a development point of view. I use a program called HeidiSQL that lets me explore tables, build querys, etc to dig into what's going on behind the scenes.
3. Its networked, so all three of my TVs use the same database.
And yes, by altering the tables and adding an index for some of the key fields, it speeds up querys. I've seen a very noticeable change in my music and movies after executing those changes.
Plus, its extra nerdy to be running a SQL server rather than a bunch of boring flat files