media-scannning removes added songs instantly about streeme

[GoogleCodeExporter]

Hmm.. that's kind of tricky, but it looks like the song itself isn't being 
added, but the app is reporting that it is. When Streeme tries to finalize the 
scan, it removes all missing relationships with song, so your artists and album 
entries get flushed. Try running the integration tests by typing ./symfony 
test:all and see if anything fails. that'll give me a really clear idea what 
code might be goofed. (They're passing on my W7 x64 test system using the 
latest XAMPP)

If you don't see any test errors, I'd say go through the config and 
troubleshooting steps to just double check your configuration is right. If 
you've got this far, then you're really close. 

Can you scan using iTunes? does it work? 

Original comment by [email protected] on 29 Aug 2011 at 3:15

[GoogleCodeExporter]

sorry nor Itunes here ;)

But i did the test:all. Here are the results: What's wrong with the song table 
test?

functional/client/listAlbumsServiceActionsTest.......................ok
functional/client/listArtistsServiceActionsTest......................ok
functional/client/listGenresServiceActionsTest.......................ok
functional/client/playerActionsTest..................................ok
functional/client/player_desktopActionsTest..........................ok
functional/client/player_mobileActionsTest...........................ok
functional/client/playlistServiceActionsTest.........................ok
unit/AlbumTableTest..................................................ok
unit/ArtProxyTest....................................................ok
unit/ArtistTableTest.................................................ok
unit/ArtworkScanAmazonTest...........................................ok
unit/ArtworkScanFoldersTest..........................................not ok
    Failed tests: 1, 2, 3, 4, 6, 8, 10, 13
unit/ArtworkScanMetaTest.............................................not ok
    Failed tests: 1, 2, 3, 4, 6, 7, 8, 13
unit/ArtworkScanTest.................................................ok
unit/GenreTableTest..................................................ok
unit/MediaScanTest...................................................ok
unit/PlaylistFilesTableTest..........................................ok
unit/PlaylistScanTest................................................ok
unit/PlaylistTableTest...............................................ok
unit/ScanTableTest...................................................ok
unit/SongGenresTableTest.............................................ok
unit/SongTableTest...................................................not ok
    Failed tests: 18, 19
unit/StreemeItunesPlaylistParserTest.................................ok
unit/StreemeItunesTrackParserTest....................................ok
unit/StreemeUtilTest.................................................ok
unit/combineFilesTest................................................ok
Failed Test                     Stat  Total   Fail  Errors  List of Failed
--------------------------------------------------------------------------
unit/ArtworkScanFoldersTest        0     13      8      0  1 2 3 4 6 8 10 1
unit/ArtworkScanMetaTest           0     13      8      0  1 2 3 4 6 7 8 13
unit/SongTableTest                 0     25      2      0  18 19
Failed 3/26 test scripts, 88.46% okay. 18/328 subtests failed, 94.51% okay.

thx again.

Original comment by [email protected] on 1 Sep 2011 at 9:28

[GoogleCodeExporter]

I have same issue

Total Songs Scanned: 3260
Songs Skipped: 0
Songs Added: 3200
Albums Added: 230
Artists Added: 420
Songs Removed: 3200
Albums Removed: 230
Artists Removed: 

Perl, Apache x64, PHP x64 Windows 7 Czech ver. x64

Original comment by [email protected] on 4 Sep 2011 at 10:10

[GoogleCodeExporter]

did you guys install streeme to C:\xampp or did you use your own directory? 
Still haven't gotten to the bottom of the problem, but it looks like the tests 
that are failing are integration tests that move things around on the 
filesystem - they are being blocked for some reason. Marek, do you have the 
same unit test problems discovered by Daniel?

Original comment by [email protected] on 9 Sep 2011 at 1:50

[GoogleCodeExporter]

hmm, looks kind of tricky ;)
No, I installed streeme on c:\http\www\streeme and my music library is on 
d:\mp3.
I changed the paths in the apache vhost config to match the install dir.
Did I missed a path setting in a streeme config?

Original comment by [email protected] on 9 Sep 2011 at 7:45

[GoogleCodeExporter]

daniel: I set up a VM with your exact setup and set the watched folders dir to 
D:\mp3 - The only way I could get it to remove all the songs immediately like 
that was when the database wasn't properly initialized. Can you vefiry your 
config/databases.yml file has the right details for all and test then type the 
following let me know if the problem still persists?

symfony doctrine:build --all --and-load
symfony guard:create-user my_username my_Pa$$word
symfony cc 
symfony scan-media --type=filesystem

Original comment by [email protected] on 10 Sep 2011 at 11:01

[GoogleCodeExporter]

sorry, the DB settings in config/databases.yml are correct: both DBs (streeme, 
streemetest) were created.

symfony doctrine:build --all --and-load
[...]
>> tokens    C:/HTTP/www/streeme/lib/filter/.../SongGenresFormFilter.class.php
>> autoload  Resetting application autoloaders
>> file-     C:/HTTP/www/streeme/cache/clien.../config/config_autoload.yml.php
>> doctrine  generating sql for models
>> doctrine  Generated SQL successfully for models
>> doctrine  creating tables
>> doctrine  created tables successfully
>> doctrine  Loading data fixtures from "C:\HTTP\www\streeme\data/fixtures"
>> doctrine  Loading data fixtures from "C:/...trineGuardPlugin/data/fixtures"
>> doctrine  Data was successfully loaded

symfony guard:create-user testUser testPass
>> guard     Create user "testUser"

symfony cc
[...]
>> file-     C:/HTTP/www/streeme/cache/client/test/config/config_app.yml.php
>> file-     C:\HTTP\www\streeme\data/client_test-cli.lck
>> file-     C:/HTTP/www/streeme/cache/project_autoload.cache
>> file-     C:/HTTP/www/streeme/cache/combine/js/testnamespace.js
>> file-     C:/HTTP/www/streeme/cache/combine/css/testnamespace.css
>> file-     C:/HTTP/www/streeme/cache/.test_all_status

symfony scan-media --type=filesystem
[...]
Total Songs Scanned: 5
Songs Skipped: 0
Songs Added: 5
Albums Added: 3
Artists Added: 1
Songs Removed: 0
Albums Removed: 3
Artists Removed: 1

With phpMyAdmin I can see that most of tables are empty. But e.g. in 
sf_guard_user I can see my created user and in genre are the mp3 genres of my 
mudic library which were NOT deleted after the songs were removed.
Any idea? ;-)

Original comment by [email protected] on 12 Sep 2011 at 8:36

[GoogleCodeExporter]

AHA! it's a documentation bug :P I'm sorry for wasting your time. In your 
apps/client/app.yml file, ignore my directive to change the filesystem to 
CP-1252 for windows. Leave it on ISO-8859-1. I will fix the docs immediately. I 
guess I should check this parameter in more depth as it's a recent addition. 

Original comment by [email protected] on 14 Sep 2011 at 5:23

[GoogleCodeExporter]

Whooohooo - that's it!  Now all my songs are added!
But I found a new problem/bug with the encoding (?) and the search function in 
streeme(and now I'm sorry to waste YOUR time again ;-) ):

When I try to search for an artist or a song name with special characters (e.g. 
german band "Die Ärzte") in the web frontend I get "no matches found". But on 
the left side in the artist drop-down I can see the artist and even click on 
the name to list all the songs. I get the same behavior when I search for a 
song with special characters (no matches found). But the song is listed when I 
type in the album name or the artist which has no special characters in it's 
name.

I found out that all my mp3 tags are saved as ID3v2.4 (UTF-8). Do I have to 
change all the tags to ID3v2.3 (ISO 8859-1) to match the filesystem settings or 
is it possible to keep the tag encoding and solve the problem with some config 
changes? ;-)

Original comment by [email protected] on 15 Sep 2011 at 8:53

[GoogleCodeExporter]

Nope. If your tags look okay in the sidebar, I think this is just the same 
Mysql bug I'm working on where the LIKE op isn't flexible enough for search.  
Should be fixed soon.. In the meantime - if you desire to have search 
capability that is both case insensitive and correctly parses UTF-8 chars, use 
sqlite. It's built into XAMPP, so you should be able to use it by doing the 
following:

config/databases.yml
dsn: 'sqlite:C:\path\to\streeme\streeme.db'

you won't need a username or password for sqlite as it's totally filesystem 
based. SO you can comment them out:
#username: foo
#password: bar

type 
symfony cc 
symfony doctrine:build --all --and-load
symfony guard:create-user my_username my_Pa$$word
symfony cc 
symfony scan-media --type=filesystem

The reason I don't use sqlite by default is it's a bit slower to write, but 
that may change in the near future since it's easier to configure.

once you finish scanning and get back into the app, you should be able to 
search for things by name no problem. 

Original comment by [email protected] on 15 Sep 2011 at 3:10

[GoogleCodeExporter]

Ahh, that's interesting! With sqlite the search function works great; even with 
special characters.
But it seems that searching in a bigger music library is slowlier with sqlite 
than with mysql.. 

Original comment by [email protected] on 22 Sep 2011 at 9:48

[GoogleCodeExporter]

Original comment by [email protected] on 23 Sep 2011 at 4:43

• Changed state: Fixed