Search results

6.0.5.5 seems to have solved the NAS dropout issue although I have yet to do a more thorough test. The database log however has the following error message: “Out of range value for column “level” at row 1 (1264).” The tracks2 table in MariaDB has no length value set for the level parameter...

I am using MySQL with MariaDB server. Are you saying I therefore can not re-create the database unless I convert it back to SQL Lite or APE? Can you be clearer please...

I did as you suggested but I still have tracksold.db in that directory. I reinstalled the latest version again with the same result. I also noticed the folder appears to be read only. How do I re-create the database?

These are only 2K and 315K respectively. I did find a number of errors in the database log however, some of which are current, some have gone away: e.g: "Table music.cache2 doesn't exist" and "Unknown column 'reply gain_t' in "field list" (1054) and "Out of range value for column 'level' at...

Update: the problem still exists. There are no obvious Windows errors or functions that coincide with the audio pauses. Hard disc is clean so something is periodically interrupting the data being pulled from the NAS. Thanks for the suggestion - I'll look at the settings tomorrow...

Could the network file read process be affected by the auto save process that occurs every 10 minutes? This is roughly the frequency of the computer freezes. It’s not like skipping, but an actual program freeze We have a large schedule to save.

Thank you for your helpful suggestions. I have tested RB on another computer connected over the gigabit network to the NAS with my usual sql database and it works fine. So the problem does appear to be related to the computer itself and may not be RB after all. I’ll let you know what I discover.

The problem only occurs with tracks sourced on the NAS which worked fine until recent versions. Local hard drive playback is fine. Does this mean the sound card (WASAPI) playback buffer needs to be increased beyond 200ms? I have also tried turning on get tag info as separate process but this...

Please advise the link for a reliable version 5. I'm having ongoing issues with audio dropouts despite altering the buffer settings.

The problem continues. Intermittent freezing of the playback for 1 sec or so. I need to downgrade to v 5 immediately.

After downgrading then upgrading again to 6.0.5.2 I discovered that all my tracklisted files running in sequence had reverted to the first episode in the sequence!!! This should not happen. Is there an easy way to set the order in the scheduler? Some of the files have *0, *8,*18: Do they...

6.0.5.2 also had the audio playback freezing problem referred to above but I think I was able to fix this by increasing the audio buffer setting on the playback soundcard.

Now running 6.0.5.2 as some of the earlier versions still had the audio dropout problem. When this occurred, the playout froze for a couple of seconds on a seemingly random basis. The broadcast stream seems to be running OK in this version. I'll let you know if I discover anything else...

I downgraded to 6.0.4.0 and this solved the streaming issue, but it suffers from intermittent dropouts in he audio. Can you please suggest an alternative version that I can downgrade to that is more reliable?

We don't use the integrated server, but stream to another server which claims to be connected OK. Its whatever the version that RB let me update to from the program. I assume that is the new 64 bit version.

No problem with ad scheduler here...

Exactly when we updated to 6.0.5.4 today, our broadcasting streams no longer encode any data. They are connected to the server but data has stopped and user statistics have dropped to zero. They were working fine with earlier versions until now. Can you help please!!!!!

How often does it happen? This seems to happen to some tracks (wav and mp3) . Also normalise levels set in library don't always appear in the file in a folder - until tracktool again sets the normalisatoon level. It seems to be random.

I found this occurs in 6.0.4.0 but does not in 6.0.4.3!

The programs either side of the sweeper had no mixpoint. The sweeper selected was 16 sec long; the second program began at about 6 seconds past the hour. While on this point, I note that when I add start, end and mix points and normalise tracks in the music library and look in track tool...