ProppFrexx ONAIR User-Forum

Oh no this was on me for this instance, since I moved a folder in my library to another library - it actually couldnt find the tracks. Will report back when I have a better case for a bug report.

I've had a new occurence, I have the debug log. Due to the big logs, I've filtered out to the time where the issues begin. I've emailed you the log.

I think this happens maybe 2-3 times a week? I have every hour a new script in the scheduler.

I don't think it's due to to the scripting being wrong, since starting a new program with the PROGRAM_STARTSCRIPT works directly. Odd, isn't it?

I've enabled the debug logging - once this happens again I ...

>So you would need to monitor it when you discover the error. I assume it is a history issue.

I understand. What can I do in that situation? Would the script scheduler output some debug log somewhere, perhaps something that I can toggle?

I've send you the log via Email

1. No, nothing in the error log. Last exception dates from january.

2. No errors pop up from there, and work properly.

Hi there,

Sometimes I experience some issue with playlist script generation.
I hope you can help me.

What I am seeing is two things:

1. Sometimes playlist does not generate at all
I assume that the "engine" then cannot generate the first entry and just stops then.
If I then use a PROGRAM ...

It marks the date range between 01-01-0001 and 01-01-0001. I understand that this seems to be a nullable field: can I also pass nothing for those sections to let the backing value become null?

Neat, thanks!

However, it is now like this. Would this break functionality in proppfrexx?

I'm a bit confused, how would it work?
Does pfrestrictions needs to be the last in line?