ProppFrexx ONAIR User-Forum

It only adds then, if you run a script. Montez, if you manually add them! That is what the setting is for - the option what to do for manual added tracks.

I assume you might pre-create a playlist using a script? Running a script is not like adding tracks manually ;-)
I assume, that when you ...

No. The history size is only defined by the number of entries.
The size/min. values are only for the extended check and might ‚limit‘ the check further - to high numbers would be ignored. Specifying not to add entries to the history during voice tracking in advance is a good idea.

However those ...

There is no extended history.
There are extended history checks - but no extra history.

Yes, the default is only at scripting.

There is no best setting, as everyone has other needs.
Do you experience any issues?

I’ll take a look why the new Force settings doesn’t persist…

Because this is by design, it is always realtime - the individual history entries do not have a date associated with it.
However, see the Back-To-Future… options in the history settings. Precreated playlists are still considered during realtime scripting at the time they are due.

Not all script-line options do apply for all script modes.
Eg. the RecalcACDP option does not applies to the LoadPlaylist mode (as otherwise, a manually pre-made wouldn’t play as it was designed by the creator of such playlist).

This is actually by good reason and design.
So what goes wrong ...

I assume it might be an ACPD issue?
But without further details I can not really tell. A quick here just shows me, that the media type is correctly set and as such the defined mixing settings apply correctly for that media type.

May be you can try to suppress ACDP for such media types, to see if ...

Yes, as said - it should fix it.

You say, that the issue only appears, when someone manually creates a playlist (when voice tracking is performed).
See the other option the the ‚More…‘ dialog. - eg. you can also set the option to ‚Never‘ add manually added tracks to the global history.

A new v4.5.2.12 is available which add a new "Force Exclude Filter with Adding" option to the More... option dialog.
If option forces the exclude filter also when adding tracks to the global history.

Are you talking about manually added tracks?
The Exclude Option is today basically only used when checking the history.

Note, that in each script-line you have a separate option to check and/or add tracks to the history - see the script-line Options:
- SuppressHistoryCheck
- SuppressAddHistory
So ...