Bug if Vortex runs too long ?

[audiosteve]

Hello,




I recentlry ripped my entire CD collection. Quite a few disks, over 1100.


When done I enabled and started MP3 mirroring. This seemed to go slow. I also tried to turn on PW protection for the basic web GUI and as part of that I had to reset the system.


After rebooting and restarting the Vortexbox it appeared that the transcoding was now running much faster. After a few days I woke up and checked the box and found that the transcoding had basically stopped. After rebooting again (BTW, always a soft boot from the WEB GUI),


I restarted the transcoding and it seemed to start running well again. So that is question 1) Why does the transcoding seeem to stop or run slowly and then be fixed by a rebbot. That's question 1. Question 2 is that each tiemn I rebooted and restartd the transcoding, it rechecked ALL files in the MP3 area vs. what's in the FLAC folder. When it did this each time it decided to rewrite some of the tags.These tags should have been already written and OK. Anyone have any answers or thoughts on the cause and cure of these two observed anomalies ?? Thanks, Steve

[audiosteve]

Anybody ?


Another question. Could there be a memory leak? The system has been idle for hours and it shows 93% memory usage in the system status web page. This seems high.

[steveh]

If a large percentage is cached this is normal Linux behaviour. If an application demands more memory the cache is released.

[audiosteve]

Thanks for the reply steveh. A large percnetage of that memory usage was caceh memory. So I guess that answers that. But can anyone tell me why the transcoding (FLAC -> MP3) slows dramatically or stops but works OK after a reboot ?