FireFly Media Server › Firefly Media Server Forums › Firefly Media Server › Nightlies Feedback › svn1586 library too big?
- This topic has 9 replies, 4 voices, and was last updated 17 years, 5 months ago by rpedde.
-
AuthorPosts
-
24/07/2007 at 9:10 AM #1581John_Doe74Participant
Hello to all!
First, sorry for my English, i´m a german native speaker, and reading english goes better…ok, heres my configuration: I use the latest nightly 1586 on an NSLU2 (with Unslung 6.8 ) , Client is the Roku Soundbridge 1001 with the latest FW (2.7)
After scanning my whole Mp3-Library, the Soundbridge cannot connect to the Firefly-Server, I´ve tried all different configuration with the Server (scan-type, case sensitive,…)
And here comes the clue: After scanning only a few songs, all goes fine! Now my question – is the library too big for the performance of the NSLU2, and ran the Server into a Time-Out?Can i try to change the Dbase Type (Sqlite3)?
Thx in Advance!
24/07/2007 at 11:09 AM #11803fizzeParticipantRight, the german part is a lil further down 😉
8-10k of music files shouldnt be a problem. unfortunately you cant change the DB backend (yet *hint**nudge* @ Ron ;))
Whats the output ofcat /proc/cpuinfo
on your slug?
na dann red ma halt deutsch 😉Wieviele mp3s hast du denn?
8-10000 sollten eigentlich kein Problem darstellen.Was sagt der Befehl:
cat /proc/cpuinfo
auf deinem slug?
24/07/2007 at 2:44 PM #11804John_Doe74ParticipantI have the 266 mhz Version of the slug!
Hmm, the Songs.db is about 100mb – i think thats the Problem… And yes, there are a little bit more than 8-10k´s of musik files 😆
As told, i think the Server runs into a Time-out… Is there a workaround to fix this?
So und jetzt auf deutsch – einfacher Bist ja sogar ein Landsmann! 😀Also wie gesagt, meine Vermutung ist, das die Datenbank einfach zu groß ist, mir wäre es auch gleich ein wenig zu warten, spiel dann eh vor allem meine Playlists ab, wollte halt nur meine kompletten Mp3´s zusammen haben und nicht schon wieder splitten müssen…
Konnte mich dunkel an einen Thread erinnern wo es um dieses Time-Out Problem gegangen ist, finde den aber nicht mehr…
24/07/2007 at 2:57 PM #11805fizzeParticipantHm, too bad, the SoundBridge times out after 60sec….
I guess this means waiting until ron has implemented GDBM as backend again….
Ja, die Soundbridge wartet maximal 60sec, dann gibts nen Timeout.
Übertakten wäre noch ne Lösung, aber wenn der schon auf 266Mhz läuft…. hmm….
Mit GDB lief angeblich so einiges besser.Mit Smart Playlists kannst dir aber sicher helfen. So in der Ar id < 5000 oder so 😉 Da kannst dir die Library nett spalten.
Ansonsten kannst nur auf GDBM hoffen, das als backend wohl irgendwann mal wieder zur verfügung stehen wird – zumindest wenn man Rons ToDo-Liste vertrauen schenkt 😉
24/07/2007 at 3:17 PM #11806John_Doe74Participanthmm the “Can´t connect” from the Soundbridge comes about after 15 seconds, i think it´s the Server, that says no!?
Heres the connection log – see that “Checking to see if connection matches keep-alive” – “nope”?
But why?
10:15:49 (00016403): Thread 87: Entering ws_dispatcher (Connection from 192.168.1.xxx)
2007-07-24 10:15:49 (00016403): Thread 87: got request
2007-07-24 10:15:49 (00016403): Request: GET /rsp/info HTTP/1.0
2007-07-24 10:15:49 (00016403): Thread 87: Read: User-Agent: Roku SoundBridge/2.5
2007-07-24 10:15:49 (00016403): Thread 87: Adding header *User-Agent=Roku SoundBridge/2.5*
2007-07-24 10:15:49 (00016403): Added *User-Agent=Roku SoundBridge/2.5*
2007-07-24 10:15:49 (00016403): Thread 87: Read: Host: 192.168.1.xxx:3689
2007-07-24 10:15:49 (00016403): Thread 87: Adding header *Host=192.168.1.xxx:3689*
2007-07-24 10:15:49 (00016403): Added *Host=192.168.1.xxx:3689*
2007-07-24 10:15:49 (00016403): Thread 87: Read: Accept: */*
2007-07-24 10:15:49 (00016403): Thread 87: Adding header *Accept=*/**
2007-07-24 10:15:49 (00016403): Added *Accept=*/**
2007-07-24 10:15:49 (00016403): Thread 87: Read: Pragma: no-cache
2007-07-24 10:15:49 (00016403): Thread 87: Adding header *Pragma=no-cache*
2007-07-24 10:15:49 (00016403): Added *Pragma=no-cache*
2007-07-24 10:15:49 (00016403): Thread 87: Read: accept-encoding: gzip
2007-07-24 10:15:49 (00016403): Thread 87: Adding header *accept-encoding=gzip*
2007-07-24 10:15:49 (00016403): Added *accept-encoding=gzip*
2007-07-24 10:15:49 (00016403): Thread 87: Read: accept-codecs: wma,mpeg,wav,mp4a,alac
2007-07-24 10:15:49 (00016403): Thread 87: Adding header *accept-codecs=wma,mpeg,wav,mp4a,alac*
2007-07-24 10:15:49 (00016403): Added *accept-codecs=wma,mpeg,wav,mp4a,alac*
2007-07-24 10:15:49 (00016403): Thread 87: Read: rsp-version: 0.1
2007-07-24 10:15:49 (00016403): Thread 87: Adding header *rsp-version=0.1*
2007-07-24 10:15:49 (00016403): Added *rsp-version=0.1*
2007-07-24 10:15:49 (00016403): Thread 87: Read: transcode-codecs: wav,mp3
2007-07-24 10:15:49 (00016403): Thread 87: Adding header *transcode-codecs=wav,mp3*
2007-07-24 10:15:49 (00016403): Added *transcode-codecs=wav,mp3*
2007-07-24 10:15:49 (00016403): Thread 87: Read:
2007-07-24 10:15:49 (00016403): Thread 87: Headers parsed!
2007-07-24 10:15:49 (00016403): Checking to see if connection matches keep-alive
2007-07-24 10:15:49 (00016403): Nope!
2007-07-24 10:15:49 (00016403): Thread 87: Connection type HTTP/1.0
: Connection: non-persist
2007-07-24 10:15:49 (00016403): Thread 87: Original URI: /rsp/info
2007-07-24 10:15:49 (00016403): Thread 87: Translated URI: /rsp/info
2007-07-24 10:15:49 (00016403): Thread 87: Preparing to find handler
2007-07-24 10:15:49 (00016403): Checking /rsp/info against handler for /
2007-07-24 10:15:49 (00016403): Thread 87: URI Match!
2007-07-24 10:15:49 (00016403): Thread 87: Time is 1185297349 seconds after epoch
2007-07-24 10:15:49 (00016403): Thread 87: Setting time header
2007-07-24 10:15:49 (00016403): Added *Date=Tue, 24 Jul 2007 17:15:49 GMT*
2007-07-24 10:15:49 (00016403): Added *Connection=close*
2007-07-24 10:15:49 (00016403): Added *Server=mt-daapd/svn-1586*
2007-07-24 10:15:49 (00016403): Added *Content-Type=text/html*
2007-07-24 10:15:49 (00016403): Added *Content-Language=en_us*
2007-07-24 10:15:49 (00016403): Thread 87: Using non-default handler
2007-07-24 10:15:49 (00016403): in main_auth
2007-07-24 10:15:49 (00016403): Checking url /rsp/info
2007-07-24 10:15:49 (00016403): Checking url /rsp/info
2007-07-24 10:15:49 (00016403): Dispatching auth for /rsp/info to plugin
2007-07-24 10:15:49 (00016403): Checking url /rsp/info
2007-07-24 10:15:49 (00016403): Checking url /rsp/info
2007-07-24 10:15:49 (00016403): Dispatching /rsp/info to rsp/svn-1586
2007-07-24 10:15:49 (00016403): Checking if pw required for /rsp/info as user
2007-07-24 10:15:49 (00016403): Nope
2007-07-24 10:15:49 (00016403): in main_handler
2007-07-24 10:15:49 (00016403): Checking url /rsp/info
2007-07-24 10:15:49 (00016403): Checking url /rsp/info
2007-07-24 10:15:49 (00016403): Dispatching /rsp/info to plugin
2007-07-24 10:15:49 (00016403): Checking url /rsp/info
2007-07-24 10:15:49 (00016403): Checking url /rsp/info
2007-07-24 10:15:49 (00016403): Dispatching /rsp/info to rsp/svn-1586
2007-07-24 10:15:49 (00016403): Getting uri...
2007-07-24 10:15:49 (00016403): Mallocing privinfo...
2007-07-24 10:15:49 (00016403): Tokenizing url
2007-07-24 10:15:49 (00016403): Found 5 elements
2007-07-24 10:15:49 (00016403): Checking reponse 0
2007-07-24 10:15:49 (00016403): Found it! Index: 0
2007-07-24 10:15:49 (00016403): Starting rsp_info
2007-07-24 10:15:49 (00016403): Gzipping output
2007-07-24 10:15:49 (00016403): Added *Content-Encoding=gzip*
2007-07-24 10:15:49 (00016403): Added *Vary=Accept-Encoding*
2007-07-24 10:15:49 (00016403): Updating Connection from close to Close
2007-07-24 10:15:49 (00016403): Added *Cache-Control=no-cache*
2007-07-24 10:15:49 (00016403): Added *Expires=-1*
2007-07-24 10:15:49 (00016403): Updating Content-Type from text/html to text/xml; charset=utf-8
2007-07-24 10:15:49 (00016403): Emitting reponse header Expires: -1
2007-07-24 10:15:49 (00016403): Emitting reponse header Cache-Control: no-cache
2007-07-24 10:15:49 (00016403): Emitting reponse header Vary: Accept-Encoding
2007-07-24 10:15:49 (00016403): Emitting reponse header Content-Encoding: gzip
2007-07-24 10:15:49 (00016403): Emitting reponse header Content-Language: en_us
2007-07-24 10:15:49 (00016403): Emitting reponse header Content-Type: text/xml; charset=utf-8
2007-07-24 10:15:49 (00016403): Emitting reponse header Server: mt-daapd/svn-1586
2007-07-24 10:15:49 (00016403): Emitting reponse header Connection: Close
2007-07-24 10:15:49 (00016403): Emitting reponse header Date: Tue, 24 Jul 2007 17:15:49 GMT
2007-07-24 10:15:49 (00016403): Executing: select count(*) FROM songs
2007-07-24 10:16:01 (00016403): Done sending xml stream
2007-07-24 10:16:01 (00016403): Thread 87: Terminating
2007-07-24 10:16:01 (00016403): Thread 87: Freeing request headers
2007-07-24 10:16:01 (00016403): Thread 87: Freeing response headers
2007-07-24 10:16:01 (00016403): Thread 87: Freeing request vars
2007-07-24 10:16:01 (00016403): Thread 87: Closing fd
2007-07-24 10:16:01 (00016403): With thread 87 exiting, 0 are still running
24/07/2007 at 4:11 PM #11807fizzeParticipantwell, the selcet count(*) from songs is fast.
So, maybe the soundbridge hits the fan here and just snatches at the sheer amount of songs 😉In all seriousness: then it indeed seems to be a soundbridge-memory limit.
Can you try to reduce the sice of your library to see if you hit a brickwall at… say 15.000 or 10.000 songs?
*shrug*Also, try to post this over at the RoKu forums.
Wahrscheinlich gibt die SB auf, weil du einfach zu viele Lieder hast. Frag dazu ruhig die Jungs von RoKu.
Ansonsten kann ich dir nur empfehlen, deine Bibliothek schrittweise zu verkleinern, und zu sehen, obs irgendwann funzt…. *schulterzuck*24/07/2007 at 8:54 PM #11808Dave.BParticipantJust throwing this in here for comparison purposes:
My 133MHz slug has a 21MB songs.db file, with 14038 songs. My SB M1001 plays the entire library with no problems.
I’ve been expecting the SB to fall over ever since I passed 10,000 songs, but it just keeps going.
I guess you have many, many more tracks than I do if you’ve hit 100MB on your songs.db, but would you care to put a figure on it?
Just out of curiosity.
Cheers.25/07/2007 at 3:09 AM #11809rpeddeParticipant@Dave.B wrote:
Just throwing this in here for comparison purposes:
My 133MHz slug has a 21MB songs.db file, with 14038 songs. My SB M1001 plays the entire library with no problems.
I’ve been expecting the SB to fall over ever since I passed 10,000 songs, but it just keeps going.
I guess you have many, many more tracks than I do if you’ve hit 100MB on your songs.db, but would you care to put a figure on it?
Just out of curiosity.
Cheers.last I talked to RokuMike, I think he said the soundbridge falls over at about 50K songs. iirc.
Doesn’t look like it’s the server, though, that connection was successful. Is the server name valid utf-8?
Try using firefox to browse to http://server.ip:3689/rsp/info and see if you get a parseable xml file.
— Ron
25/07/2007 at 7:04 AM #11810John_Doe74ParticipantThx for response!
Yes the server name is valid! And yes i get a parseable xml file!
Is that part ok?
0
0
0i mean records and totalrecords? At “counts” there is the right number of files!
I think he said the soundbridge falls over at about 50K songs. iirc.
Thats the hint – it looks like i must decrease the size…
Thx!
26/07/2007 at 3:17 AM #11811rpeddeParticipant@John_Doe74 wrote:
Is that part ok?
0
0
0Ya, it isn’t used as part of the info response, just when paging through resultsets of queries.
— Ron
-
AuthorPosts
- The forum ‘Nightlies Feedback’ is closed to new topics and replies.