Bug in automatic file container pattern matching?

[prr]

Hello,

I’m trying to use the automatic file container, so I can automatically schedule radioshows in their proper slot each week. However, for some reason I cannot set it up properly.

I have the following automatic file container in the database:

With the following playback options:

I have also the proper file on disk:

When using the Mini Scheduler, I get the following output:

You can clearly see that the item is not found.

I investigated the issue a bit and I noticed that everything is working fine when I change the filename pattern to:

radioshow-05%M%Y.mp3

Somehow %D doesn’t seem to be recognized. I’m wondering is this a bug or am I doing something wrong?

If I’m doing something wrong, can you please help me to correct my actions? Thanks in advance.

Kind regards,
Marco

[Stefan_Hillen]

@prr

I’m wondering is this a bug or am I doing something wrong?

Could you be so kind to test if it works when you chose the “External Element” like I described here:

Programming the time announcement on mairlist 6.3

It’s all explained by Torben in the Thread I linked to: But here’s my english Step-by-Step tutorial for you (and all in need): Open your hour template and choose “External Items” [Bildschirmfoto 2022-08-20 um 14.12.58] Drag & Drop one example item from your windows explorer (!) into the Listing window: [Bildschirmfoto 2022-08-20 um 14.13.28] Double-click the item to open the preferences, go to the tab “Audio File” [Bildschirmfoto 2022-08-20 um 14.20.53] Change parts of the filenam…

Then I can forward it, if it’s a bug within the AFC.

Thank you for the effort!

BTW: I suggest to turn off the "Automatically redo Auto Cue every time the file is opened) option when loading pre-produced shows. The AutoCue may set the fade out too early and cut off the show.

[prr]

Hi Stefan,

This works properly, but the other approach still does not work. If you create an automatic file container in the database and specify the file pattern, then %D is not recognized. Thus it is probably not a general bug in AFC, but rather a specific bug in the file pattern implementation of an AFC container which is explicitly stored in the database. That or… I am still doing something wrong.

Torben states in one of his posts that it should work either way (i.e. external item or specific item referencing id of AFC).

Kind regards,
Marco