Hello there,
after using google a lot during the last week, I wasn't able to find an answer to this aggravating problem.
Device: QNAP TS-419P+
Firmware: 3.4.4 Build 0718T
Twonky Version: Built-In 5.1.6
While pumping my entire media collection onto the device I experienced crashes during video playback. Further investigation showed that Twonky Server would loose all db content and start a rescan. After three or so happless attempts, Twonky Server would crash alltogether and become unresponsive, forcing a restart. Then the whole loop started again.
I started to exclude media and directories to find what caused this issue and I singled out one music genre directory:
Size: 17,5 GB
Files: 3768 (mp3 and ogg)
Folders: 210
It is the largest directory of my collection. All others import without problem.
Are there any limitations I should be aware of ? I have read here on the forum that there are bad media files ?
Help would be much appreciated
Thx
Constant crashes while scanning directory
-
Alphaelectric
- Posts:1
- Joined:Sun Jul 31, 2011 1:38 pm
- AV Hardware:QNAP TS-419 P+
XBOX 360
-
parnott
- Posts:326
- Joined:Mon Sep 20, 2010 9:55 pm
- AV Hardware:Twonky, WDTV Live, XBMC (Linux & Windows)
Re: Constant crashes while scanning directory
You must have one or more bad files somewhere.
Firstly, are you sure about those statistics. 17.5GB for 3768 music files looks very high. I can get around 12 full-length movies encoded in mp4 at high quality in that space.
I would suggest you start looking through your directories for files that appear excessivly large compared to comparable files with the same time duration. Alternatively, just start removing directories (remember to rebuild the database) until you narrow it down to a particular directory. Suggest you start with the ogg files first.
Firstly, are you sure about those statistics. 17.5GB for 3768 music files looks very high. I can get around 12 full-length movies encoded in mp4 at high quality in that space.
I would suggest you start looking through your directories for files that appear excessivly large compared to comparable files with the same time duration. Alternatively, just start removing directories (remember to rebuild the database) until you narrow it down to a particular directory. Suggest you start with the ogg files first.