for the local newsflash we use a audio track that is overwritten every week (we have a file for each day of the week). For some reason the software frooze on that file today. Replaced it by a dummy file to keep the station on air but (here comes my question)…
How can we say to the software to skip corrupted tracks??
Is there a way to make that the software doesn’t freeze on a corrupt track?
Is there a warning possible when the software stops? (email)?
Generally, BASS (the audio library used by mAirList) can handle broken audio files very well; plays them until the point where the file gets corrupted, or skips them altogether.
Perhaps you can upload one of those broken files somewhere so we can analyze it.
I don’t get it.
Yesterday our Behringer FCA 1616 died on us. Replaced the soundboard with a Focusrite scarlett18i20. Should be a better board (and in fact an urgent replacement given the fact that we want to take the software onair next saterday).
Can the replacment of soundboard have an impact on why sinds yesterday playback goes bad?
Just created new playlist to see if that fixes something (and no this didn’t solve a thing just logged in an the sooftware was once again frozen on a track).
Had a look into the systemlog. Had a whole bunch of these kind of errors:
10/05/2016 22:42:57 Warning Error prebuffering item “The Passenger”: Cannot open file “Z:\MUZIEK DATABASE MAIRLIST\03 - JAREN 70\Iggy Pop - The Passenger.mp3”. Het systeem kan het opgegeven pad niet vinden (translation to english The system can’t find the specified path).
This is a bit odd. The Z drive is on the pc SSD hard drive. It is not a network drive nor a mapped drive. I’m stuck …
The location of the database file (.mldb) is absolutely independent of the location of the audio files.
“Prebuffering” means that mAirList opens the files beforehand (default: next 5 items) and checks if they are OK. This might involve creating a temporary copy in your TEMP folder, according to the settings on the File Manager page in mAirListConfig.
“file not found” simply means “file not found”. There MUST be something wrong with the file paths somewhere.
If the files are registered in a mAirListDB, the audio folders are registered as “storages” in the DB administration (DB app -> Administration -> Configuration). Have you moved your audio folder lately? Then you just adjust the storage folder accordingly.
It is definitely not related to any changes in the audio hardware.