ProppFrexx ONAIR User-Forum

Both examples do work fine here.

I tried again.
No. It does not work here !

When you say "The other pc has it's own config folder"...this is good, but it seems, like on that other PC you had configured an Advert-Library-Path which was inaccessible at the time PF started.
Hence the error you have seen...
Again, it is of course not only the config folder itself, but the content you configured. E.g. if in the config you are pointing to a certain Advert-Folder, that folder must be available at the time you start PF.
Could it be, that the Advert-Lib folder and/or even your other library folders (at the time you start PF) are not available, but are available later on.
This should even be logged into the Overlay log file (in case the debug log was disabled at that time)! Also check for any entries in the Error.log file...
So please take a look there...


The -debug command-line option wouldn't break any registration.
A new registration is only needed, if the Ident-Number changes! And this only happens, if you e.g. install a new OS, change your network settings, machine name or change the hardware.
Did you change anything in that respect? Did the Ident-Number change?

Yes v3.0.13.17 fixes -debug and registration problem.

But unfortunately -debug does not show more info why pf does not start, staying at "loading..." in status bar.
The debug log at program start (with -debug) shows only : I 've tried everything with no luck. I am thinking to give up for the moment.

And when you close it and then restart all Starts fine again?

I guess I found a race condition regarding the -debug vs. -usbReg command-line option, a v3.0.13.17 is available.

Bernd
8 in 10 times it does not start.
The only way to continue is to manually reload libraries, overlays and scripts.
I can not find why. That's why I thought that -debug would give me some info on where it stucks but no.
I don't say that the problem is related to PF. It might be my OS settings or something else.
So I don't blame PF for this problem.

But after purchasing and testing for almost 2 months I am still not ready to let PF work on Air.
I am not anymore confident that updating to newer version won't let me off air.
(Now it became a psychological matter !).

Unfortunately excitement and all those tests didn't let me spend time for my actual on air programming and that had an impact on my radio's station audience.
So I decided to let pf for a while and "experiment" when I have free time.

Dimitris

Dimitris,

We already did 3 TeamViewer session. We (restarted) PF like 20 times? And it always started just fine.
Now you changed various settings I guess, like you global config folder S: or something similar. And since then you got issues.... so I guess this is pretty obvious that it must be related to that.

The -debug option does not log every command or issue of course, so it must be something at the very beginning which is going wrong.

We might do a 4th TeamViewer session tomorrow afternoon if you want...

Bernd I narrowed the problem to MLS.
For some reason it does not load a folder library and does not start the server.
I am pm sending you my tv info to check.

As already explained in a PM.
The _synced_.pfp playlist file got somehow corrupted, so that the MLS got stuck in an initial endless loop.
Preventing it to start correctly.
I now optimized that in a new v3.0.13.18 and also optimized the timeout setting for remote library access, so that it doesn't take so long if a MLS is unavailable.