Crashes
From Ssl-wiki
Contents |
Introduction
There are several reasons why SSL can crash, of which some of them we will discuss and explain here.
Overheating
If your system suddenly freezes or crashes without any prior warning or Operating System Message, most likely this is due to your laptop overheating. Especially Apple laptops are know to be prone to overheating. Remedy would be to use an external additional fan to make sure it does not overheat. Another way to solve this problem is to simply reduce the CPU load, for example by lowering the GUI refresh rate or raising the USB buffer size.
Corrupt files
If SSL suddenly disappears but the Operating System is still running this can be a problem of corrupt files. Also a error message that the application had to be closed bla bla is a sign of corrupt files. The tricky thing is that usually building overview should tag those files which are corrupt, but its the same problem as virus scanners do have: Only known viruses or those containing know virus patterns will be detected as such. Applied to SSL it means that oOnly known corrupt files or known corruption patterns will be detected. So
- if a file has been detected as corrupt, SSL knows it is corrupt and should not crash on it.
- If its *not* detected as currupt, it does *not* mean the file is okay, it just means that it has not been detected 100% as corrupt.
In other words:
- Every file which is tagged as corrupt is faulty
- Not every file which is not tagged as corrupt is okay!
Filtering out corrupt files is not an easy thing (else SSL would do it for you...). Some files may play fine at one gig, and on other gigs it will crash SSL (that is due to the reason that corrupt files may cause memory corruption which severity depends on what files you have played before, in which order etc.). This also means that audio files which used to work with one version of SSL (and were corrupt but *not* detected as corrupt!) might not work with another version of SSL That explains why some users do not have any problems with 1.4 and suddenly have problems with 1.5 for example. This is really a bad thing, and we can only hope that in the future SSL will be made more robust concerning these issues.
You should be pretty safe if you encode your files by yourself using for example the sophisticated LAME encoder. Also stay away from files downloaded from P2P services, they are often corrupt.
You should also keep in mind that even if you can play those files fine with any other media player that does not necessarily mean they are not corrupt! It just shows that the other players can handle those files much better than SSL does right now.
If you have found a corrupt file , the safest way is to *not* play this file anymore, because there is absolutely no guarantee that these files play fine. As said before, they might run fine in the current version of SSL but may cause problems in previous or even in next versions. Please upload any corrupt file which is not tagged as corrupt (meaning SSL does not know it is corrupt) to Serato (try this link) so that the SSL developers can make sure such files will be detected for future versions of SSL. You can try to reencode those files, which will make them playable again with (hopefully only) a little loss of quality.
Processor too slow
Links
Acknowledgement
Credits for this article go out to:
Todo
Processor too slow
