[craigd]

There are a number of common issues when first setting up I’ll track as many of them here as I can but first here’s a list of common items which cause issues, thanks to avus m3 for original collation of these.

1. Ensure you have a build that supports MySQL, Camelot 9.11 is only equivalent to r26018 and a minimum build number of r28142 is required. I’d recommend using the newest Dharma build available.
2. Ensure your sources are valid and accessible and will scan to a local db with the advanced settings removed
3. Ensure user has been created in mysql
4. Ensure user has create, and edit access to server
5. Ensure user has create and edit access to schemas
6. Ensure character and collation of schema is set to latin1
7. Ensure all sources are defined with smb links and not local defined
8. Ensure there are no occurrances of “\” in your sources MySQL requires all path seperators to be “/”
9. Mysql server needs to be contactable on port 3306, Try connecting with all firewalls disabled to see if this is being blocked.



In addition to these issues a number of users have noticed lockups and slow downs accessing certain views here’s the solutions found so far, thanks to albaranov for the music fixes.

1. Delay of 3 minutes when you click on an Artist in Library mode.
Fixed by adding index: CREATE INDEX test_idx ON song(idAlbum);

2. Delay of 20 seconds when you click on "Artists"
Fixed byadding index: alter table song add index idArtist(idArtist);

3. Delay of 10 seconds when you click on "Genres"
Fixed by: alter table song add index idGenre(idGenre);


****update 13/04/2011: indexes how to by Krazypoloc****

Alright guys I got it all figured out (famous last words).

Code:

C:\Documents and Settings\Aaron>[b]mysql -u root -p xbmc_music[/b]
Enter password: ********
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 3
Server version: 5.1.41 Source distribution

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> [b]CREATE INDEX test_idx ON song(idAlbum);[/b]
Query OK, 21514 rows affected (1.50 sec)
Records: 21514  Duplicates: 0  Warnings: 0

mysql> [b]alter table song add index idArtist(idArtist);[/b]
Query OK, 21514 rows affected (0.56 sec)
Records: 21514  Duplicates: 0  Warnings: 0

mysql> [b]alter table song add index idGenre(idGenre);[/b]
Query OK, 21514 rows affected (0.63 sec)
Records: 21514  Duplicates: 0  Warnings: 0

Thats for the music bit....I then added...

Code:

C:\Documents and Settings\Aaron>[b]mysql -u root -p xbmc_video[/b]
Enter password: ********
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 19
Server version: 5.1.41 Source distribution

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> [b]ALTER TABLE movie ADD INDEX ix_idFile(idFile);[/b]
Query OK, 680 rows affected (0.30 sec)
Records: 680  Duplicates: 0  Warnings: 0


mysql> [b]ALTER TABLE movie ADD INDEX idMovie(idMovie);[/b]
Query OK, 690 rows affected (0.16 sec)
Records: 690  Duplicates: 0  Warnings: 0

mysql> [b]ALTER TABLE movie ADD INDEX idFile(idFile);[/b]
Query OK, 690 rows affected (0.11 sec)
Records: 690  Duplicates: 0  Warnings: 0

********



As in the pros and cons at present posters are not able to be tracked or stored by the database. This means only the htpc which originally updates the library will shows the correct images for items in the library. At present to get the images you will need to refresh each item or enter and exit the info screen for each item. There are two main ways to automate a workaround to this issue.

1. Use symlinks to share thumbnails folder. Using symlinks all thumbnails are held on one pc (usually the same as the mysql db sits on) and rather than a folder a shortcut is essentially created which points each other pc to the shared folder.
Pros:
Only one copy of each file is created.
All systems always show correct images

Cons:
Network performance will control how quickly images can be loaded so can impact user experience.

2. Synchronise folders so copies of files are held centrally and copies are cascaded to all other htpc's. Using tools such as synctoy, rsynch, dropbox folders can be set to replicate manually or automatically depending on selected tool.

pros:
guaranteed best performance as files are cached locally
simple to set up

cons:
images not available until sync completes
not all tools automate easily and some cost money