Music 1 integration

You have a question or need an advice about how to do something? Ask it here!
TheoOrl45
Posts: 111
Joined: 23 Apr 2012 00:28

Music 1 integration

Post by TheoOrl45 » 20 Feb 2013 00:08

Hi Bernd,

I'm a new music 1 customer.
You put on your website a "fully music 1 integration", but there is no information about it anywhere. If I search "music 1" into the search function of this forum, it tells me that they are too common.

Could you give me more information about it ?
I found how to export my library within a csv files, with the "music 1 v7" export format. But, anything else.

For example, I'm wondering if the GUID should be put into the "cart" field into "music 1" database or if I should put, as I previously imagined, the full filepath.

Then, you tell about importing into proppfrexx music 1 log... what do you mean exactly ? do you refer to the "proppfrexx" export format music 1 provided us with ? or do you refer to the real "music 1" log ?
It's not very clear and user manual is not updated about this functionnality...

Sorry, I can't be clear because it's difficult to explain what it is because I don't know what we can really do.

Best regards,

--
Theo
Theo, from France.

User avatar
radio42
Site Admin
Posts: 6391
Joined: 05 Apr 2012 16:26

Re: Music 1 integration

Post by radio42 » 20 Feb 2013 00:08

I'll take a look at it today...and hopefully I find the issue.
So if yes, a new version can be expected at the beginning of next week I guess!

User avatar
radio42
Site Admin
Posts: 6391
Joined: 05 Apr 2012 16:26

Re: Music 1 integration

Post by radio42 » 20 Feb 2013 00:08

I have found the issue. It was a pure lookup issue when using GUIDs...
I post a new version soon!

TheoOrl45
Posts: 111
Joined: 23 Apr 2012 00:28

Re: Music 1 integration

Post by TheoOrl45 » 20 Feb 2013 13:54

What a complete answer :-) !!!

REALLY GREAT !!!!! Thank you a lot Bernd ! I'm looking forward to test all this functionalities :-)
Theo, from France.

User avatar
radio42
Site Admin
Posts: 6391
Joined: 05 Apr 2012 16:26

Re: Music1 integration

Post by radio42 » 20 Feb 2013 20:49

Working with external schedulers is typically a two way communication:

1. You export your media library(ies) (audio files) to the external scheduler:
This export file is then imported (by e.g. Music1), so that the external scheduler 'knows' which tracks are available.
Typically I suggest to use fully qualified filenames in this export, as this allows the external scheduler to e.g. pre-listen/playback such tracks.
However, Music1 would also using a GUID, but in such case the tracks can not be pre-listen/playback within Music1.
Whenever you add new tracks to your ProppFrexx media libraries - a new (delta) export might be needed, to synchronize these new tracks also with Music1.

2. You import a log-file generated by external scheduler:
Typically this log-file represents a logical playlist to be played for a particular date (and hour).
Some schedulers export a log-file on a per day bases, some on a per hour bases - Music1 allows both.
So the 'Split by' option (see below) can be adjusted to let ProppFrexx understand, what log-file is currently being imported and how ProppFrexx translate its entries to appropriate program scheduler entries.
As such importing of log-files generated by Music1 into ProppFrexx is a regular (e.g. daily) task.

The Program Scheduler supports importing of various external 'log-file formats' from external schedulers (like Music1).
When you open the Program Scheduler from within ProppFrexx you'll find an 'Import' button in the dialog's ribbon. Click on it to import an external scheduler log-file.
Music 1 Note: You need to make sure to install the very latest Music1 version and use the special ProppFrexx log-file format with it!

The Music1 log-file import allows you to import future dated schedules only.
The import automaticlly generates the following:
- related .pfp playlist files
- a related .pfs script (using the generated .pfp files)
- appropriate program scheduler entries (using the .pfs script(s))

So it is a simple click and import (with all default options already set).
Experienced users still have the possibility to highly customize the import process. A PROGRAM_IMPORT control-command even allows you to run the import in an automated batch fashion (e.g. by using the pfremcmd.exe tool even driven from any command-line).

The "ProppFrexx ONAIR.importformats" file (located in your ProppFrexx 3.0 AppUserData directory contains the freely definable Music1 import format specification) - which typically doen't need to be adjusted (especially for Music1).

Import a log-file from Music1:

To import a log-file from Music1, just open the "Program Scheduler" - which is located in the 'Scheduler' ribbon.
In the 'Program Scheduler' dialog you'll find an 'Import' button - click on it.
This opens the 'Program Schedule Log Importer' dialog.

In here you can specify various settings (but the default values should in most case all be fine, but you always need to specify at least the 'Import Log-Filename' and 'Track Base Folder'):

Here are the details for each setting:

Import Format: select 'Music1 ProppFrexx'

Spot Breaks: Defines how to handle spot break groups contained in the log.
- EmbeddedContainer: Spot break groups will be created as a single embedded containers (the items of the spot break group will be contained in the container). The spot break group will be played as one continuous item.
- IndividualItems: The items of spot break groups will be created as individual playlist items and be played individually.
- SeparateOverlay: Spot break groups will result in separate overlay scheduler entries and not be included in the regular program scheduler entries. As such spot break groups will be played via the overlay player instead of the playlist.

Import Log-Filename: Please specify the external scheduler log file to import (click on the '...' button to select one).

Track Base Folder: Please specify the folder containing the audio files referenced in the log file.
You might specify multiple paths separated by a semicolon. The first path given will be the primary one.
If the log-file already contains fully qualified filenames, this is not used.
But any not fully qualified filenames in the log-file will be searched in the given base folder(s).
Missing extensions will be added automatically (supported extensions are .wav, .mp3, .ogg, .mp2, .wma, .m4a, .flac).
ProppFrexx always evaluates both: filename and/or a GUID reference.
If a GUID reference is given as a 'filename' (which is the 'cart' field in case of Music1), ProppFrexx tries to resolve the related track internally and expands it to a fully qualified filename itself.
If a filename is given, ProppFrexx tries to resolve it either directly (e.g. if a fully qualified filename is given in the import log) or by scanning the given 'Track Base Folder(s)'.

File Format: Defines the format of the log filename to import.
The format defines where to find the year, month and day component within the imported log filename. This is important for the importer in order to recognize the correct Date!
So make sure, that the filename format matches exactly the given log filename!
Use the following placeholders to identify the date components:
yyyy or YYYY: 4-digit year
yy or YY: 2-digit year
MM: 2-digit month
dd or DD: 2-digit day
HH: 24-hour digits
mm: minutes
You might use the '_' or '-' character as a placeholder for any other character in the filename.

Import Options: Select the import options to use for processing the log file.
- None: No options.
- GeneratePlaylistOnly: Only playlists are generated, but NO scheduler entries are created!
- SkipInvalidItems: Invalid log items are ignored during processing (e.g. audio files not found are ignored).
- SkipExistingPrograms: Item groups which result in a program scheduler entry which already exists will not be created, instead only the new playlist will be created.
- RenameLogFileWhenDone: After a successful import the original log file will be renamed to .done.
- DeleteLogFileWhenDone: After a successful import the original log file will be deleted.
- SkipOverscheduledItems: Any items which exceed the program scheduler time will be discarded.
- CheckDynamicItems: Dynamic items are validated during the import. Dynamic items are Script- or Overlay-Container entries.

Split by: Defines how the log should be splitted to create individual program entries.
- None: The entire log will result as a single program scheduler entry. No splitting is performed. Note, that overscheduled hours will not be handled and TimeUpdate event are ignored, which might result in a false playlist.
- Hour: The log will be splitted by hour. For each hour an individual program scheduler entry will be created. Note, that TimeUpdate event are ignored in this case.
- TimeUpdate: The log will be splitted only by TimeUpdate events. With each TimeUpdate event a new individual program scheduler entry will be created for the following items. Note, that hours are ignored in this case.
- TimeUpdateAndHour: The log will be splitted by hour as well as by TimeUpdate events. With each TimeUpdate event and with each hour a new individual program scheduler entry will be created for the following items.
- TimeUpdateOrHour: The log will be splitted by hour or by TimeUpdate events. With each TimeUpdate event an individual program scheduler entry will be created for the following items. A new hour will only be concidered, if no TimeUpdate happend in the previous hour.
- Consecutive: The entire log will result in a single program scheduler entry, but any time update splits within the log will be evaluated and translated into appropriate Time Update Sync events. As such, overscheduled hours will be handled correctly.

Also make sure to specify a Playlist Output Folder (the folder to which the resulting/imported playlist files should be created - but typically you can leave this as is.

Finally click on the Read Log File button to read and parse the log-file (this might take some seconds due to the extensive file checking).
The result of the reading/parsing will first be displayed in the table list.
Each root entry represents one scheduler entry to be created within ProppFrexx.
You can expand these entries to see the playlist items associated with it.
This allows you to verify and or edit the import before doing the actual import.

Once all is fine, click on the Import button at the bottom of the dialog.
Now the effective program entries are created, necessary scripts are created as well as .pfp (ProppFrexx) playlist files are generated.
As such your program scheduler is updated and you are done with it.

The next time you open the same dialog you just need to specify a new 'Import Log-Filename' and can click on 'Read Log File' and then click on 'Import'.

After the import is done you might want to test it - so you can close the import dialog and the program scheduler dialog.
Note, that it is only allows to import future dated items!
The default setting for the import filename assumes the format "MMddyy.tab".
You can change this (if needed in the import configuration file called "ProppFrexx ONAIR.importformats") which is located in your AppUserData directory (radio42/ProppFrex ONAIR/3.0).
In this file you will find the 'format' section for the 'Music1 ProppFrexx' format and the following line:
<option name="ImportFilenameFormat" value="MMddyy" />
Here you can change the import filename format if needed.

To start the program scheduler click on the 'Run Scheduler' button in the scheduler control ribbon - this will activate the program scheduler and automatically play the imported programs when they are due.

As explained above the 'PROGRAM_IMPORT' control-command might be used to run the import in an automated batch fashion (e.g. by using the pfremcmd.exe tool even driven from any command-line - or by using a 'Reminder' scheduler entry which triggers the 'PROGRAM_IMPORT' control-command at a certain time (e.g. every day or hour).


Here are some details about the Music1 log-file format and how ProppFrexx 'translate' its entries:

Log Time: the actual start time of a playlist entry
Mainly used to identify the effective program entry (this log entry is related to) and to detect overscheduled items.
Note: the log-file name (see 'File Format' above) identifies the date, where this field containes the time within that date.

Cue: the cue type for the log entry
'@' : Fixed (hard-sync at nominal time)
'+' : Soft
'|' : Manual/Pause
'-' : Fixed EndsAt (nominal time)
'*' : VoiceOver 'Ends with Ramp of Next Track' Transition
':' : 'Starts with Outro of Previous Track' Transition
'~' : VoiceOver 'Start with CueIn or Ends with Ramp of Next Track' Transition


Event Type: classifies the type of log entry.
MUS: music
AUD: non-music audio
PUB: the given filename will be converted to a dynamic OVERLAY container
COM: commercial
BRK: spot-break-marker hint
CMD: direct command (see 'Special CMD' below for details)
BRS: SpotBreak Start-Marker
BRE: SpotBreak End-Marker
UPD: TimeUpdateSync
-----
MUS = Music
ANN = Announcement
NEW = News
LOC = Local
ADD = Advertising
REP = Report
EFF = SoundEffect
PRO = Promo
COM = Commercial
SWP = Sweeper
DRP = DropIn
SID = StationID
SPO = Sports
LOG = Logo
LIN = Liner
INT = Intro
BED = Bed
HOT = Hot
MU2 = Music2
SHW = Show
OTH = Other
TRF = Traffic
MSC = Miscellaneous
US1 = User1
...
US4 = User4
WEA = Weather

Length: the duration of the entry

Nominal Time: the effective start time
This field might contain the effective start time to use for e.g. FixTimeElements, Sport-Breaks or TimeUpdateSyncs.

Cart: the filename to use
See special 'Special Filename (Cart) handling' below.

Title: the default trackname to use
Note: this trackname would only be used in case the effective audio file doesn't contain any meta data.

Notes: any additional comment
Typically uses as additional ModeratorText notes.


Special Filename (Cart) handling:
The cart field might contain either a GUID, a filename or a dynamic entry reference.
If a GUID is given the filename is resolved internally by ProppFrexx.
If a filename is given the 'Track Base Folder'(s) are scanned (if the filename is not already fully qualified) or if it is already fully qualified it is taken directly.
In addition you might specify so called dynamic entry references. These will be resolved to a dynamic Script or Overlay container entry.
A dynamic entry has the following syntax:
OVERLAY:<referencename> (Example: OVERLAY:OVL45)
ADVERT:<slotname> (Example: ADVERT:ADD_Mo1700)
SCRIPT:<scriptname> (Example: SCRIPT:MyNews)
Log entries having such special filename will result to a related dynamic container playlist entry.
Such dynamic container playlist entry will be like any other regular playlist entry, except, that instead of playing a dedicated audio file, the content to be played will be resolved dynamically at playtime. As such the playlist entry will play all tracks (as one continous stream) as a result of resolving the given reference as explained below.

Overlay-Container (OVERLAY:<referencename>):
The given <referencename> is used to resolve the related overlay from the overlay scheduler. This allows you to schedule/play an item as defined within the ProppFrexx overlay scheduler.
ProppFrexx looks-up the given <referencename> within the defined overlays for the given start time (+/- 30 minutes).
If an overlay is found having the given <referencename> being defined - this overlay entry is used to resolve the related tracks (as if the overlay would be played out manually at exatly this playlist position)!
As a result, using 'Embedded Overlay Container' entries allows you to:
- supress automatic Overlays being scheduled by the Overlay-Scheduler
- manually position the overlays exactly within your preparted playlist

Script-Container (SCRIPT:<scriptname>):
The given <scriptname> is used to resolve the related script. The found script is executed in exactly one-loop. This allows you to schedule/play a dedicated script at a given playlist position.

Advert-Container (ADVERT:<slotname>):
The given <slotname> is used to resolve the related advertising entry from the advertising manager/library. This allows you to schedule/play an item as defined within the ProppFrexx Advertising Manager. ProppFrexx looks-up the given <slotname> within the defined list of advert slots. If a slot is found - this advert slot is used to resolve the related tracks (as if the slot would be played out manually at exatly this playlist position)!


Special CMD handling
The Music1 CMD 'Event Type' might be used to trigger special commands. The following are supported (the command itself is directly taken out of the Cart (filename) field):

FTE Type=<type> [Start=<mm:ss>|<hh:mm:ss>] [Dur=<approxDuration>] [<text>]
This entry must preceed the block/entry to which it will apply and defines a FixTime-Element.
Example: FTE Type=Fixed Start=20:00 Dur=63

TUS Type=<type> [Start=<mm:ss>|<hh:mm:ss>] [<trackname>]
Inserts a regular TimeUpdateSync entry to the playlist.
Example: TUS Type=Fixed Start=17:45:00 This is a Sync at 45

Any other CMD will be treated as a 'OnPlaying' event control-command to be associated with the next regular log-entry.

TheoOrl45
Posts: 111
Joined: 23 Apr 2012 00:28

Re: Music 1 integration

Post by TheoOrl45 » 20 Feb 2013 21:55

Bernd,

You focused in import function. But, what about exporting librairies ?

What is the best way to export librairies for music 1 (version 7). I managed to create the CSV file using the format "Music 1v7 export", but when importing into Music1, some fields are missing...

Note : To be more accurate... there are some problems using export for Music 1 v7 but it's hard to define if they are due to proppfrexx export or to music1 import...

Filename and cart
Into your proppfrexx export, there are 2 fields : directory and filename. First gives the folder, and the second gives only the filename (not the full path).
=> When importing CSV into Music1, CART and FILENAME receive the filename. It would be better if CART receive GUID and FILENAME receive DIRECTORY + FILENAME.

TrackEnd
When importing, TrackEnd doesn't go to the ENDING music1 field.

HookIn, HookOut...
I modified proppfrexx.exportformats to replace "Ramp2" by "Intro". When importing into Music1, it's okay. But for the other values (like HookIn Hook Out and so on), no value are imported...

If I use your exportformats (in CSV) and the CSV import music1 functionality (that give me no possibility to customise fields), there are some wrong values... Strange... it seems not to be "seamless integration" as you mentioned previously :-)
PS : I use v7 of music1.
Theo, from France.

TheoOrl45
Posts: 111
Joined: 23 Apr 2012 00:28

Re: Music 1 integration

Post by TheoOrl45 » 21 Feb 2013 11:40

I also contacted Music1 (Steve) yesterday.

I will try to see if something possible using CSV file. If not, I will create a specific import settings by myself to fill Music1 database. Some fields are not required for my need, but even export all detailed fields, as trying to fill thoses values into Music1 :-)

I made test yesterday withini you proppfrexx.exportFormats to give the "filename" field the value ${directoryname}\{$filename} (which I should replace with the ${filenameandpath} macro you mentioned). It works but I thought that export using your Music v7 settings and import using the "fromCSV" provided by Music1 software would be "without thinking" :-)

Thank you again for your quick and complete answer.

Ps : I send you an email a few days ago about the licence...
Theo, from France.

User avatar
radio42
Site Admin
Posts: 6391
Joined: 05 Apr 2012 16:26

Re: Music 1 integration

Post by radio42 » 21 Feb 2013 20:29

Hi Theo,

yes, you should use the ProppFrexx Export feature to export your library tracks to Music1 and yes, the "MUSIC 1 v7 Export" format is the right one.

The main issue is, that Music1 doesn't have a real 'import' standard on their side - as such I am affraid, that a little bit of 'custom' settings/mappings are required on the Music1 side.

On the ProppFrexx side, you might even change the "MUSIC 1 v7 Export" definition - but all changes might also be done on the Music1 side.
Just to give you the full picture...
The export format definition is located in a file called "ProppFrexx.exportformats" - this file is located in the ProppFrexx installation folder (as it is normally considered to be fixed and should normally not be changed). It is a plain xml file containing a <format name="MUSIC 1 v7 Export"... section, which looks like this:

Code: Select all

    <format name="MUSIC 1 v7 Export" type="CSV" extension=".csv" delimiter="TAB" useHeader="True" quote="" quoteEsc="" quoteHeader="False" trim="True" encoding="utf-8">
        <fields>
            <field name="GUID" start="0" length="0" align="left" pad=" ">${guid}</field>
            <field name="Artist" start="0" length="0" align="left" pad=" ">${artist}</field>
            <field name="Title" start="0" length="0" align="left" pad=" ">${title}</field>
            <field name="Duration" start="0" length="0" align="left" pad=" ">${lengthms}</field>
            <field name="Directory" start="0" length="0" align="left" pad=" ">${directoryname}</field>
            <field name="Filename" start="0" length="0" align="left" pad=" ">${filename}</field>
            <field name="Genre" start="0" length="0" align="left" pad=" ">${genre}</field>
            <field name="Year" start="0" length="0" align="left" pad=" ">${year}</field>
            <field name="Album" start="0" length="0" align="left" pad=" ">${album}</field>
            <field name="BPM" start="0" length="0" align="left" pad=" ">${bpm}</field>
            <field name="Grouping" start="0" length="0" align="left" pad=" ">${grouping}</field>
            <field name="Mood" start="0" length="0" align="left" pad=" ">${mood}</field>
            <field name="ISRC" start="0" length="0" align="left" pad=" ">${isrc}</field>
            <field name="Rating" start="0" length="0" align="left" pad=" ">${rating}</field>
            <field name="TrackType" start="0" length="0" align="left" pad=" ">${tracktype}</field>
            <field name="AlbumArtist" start="0" length="0" align="left" pad=" ">${albumartist}</field>
            <field name="Composer" start="0" length="0" align="left" pad=" ">${composer}</field>
            <field name="Copyright" start="0" length="0" align="left" pad=" ">${copyright}</field>
            <field name="EncodedBy" start="0" length="0" align="left" pad=" ">${encodedby}</field>
            <field name="TrackNumber" start="0" length="0" align="left" pad=" ">${tracknumber}</field>
            <field name="DiscNumber" start="0" length="0" align="left" pad=" ">${discnumber}</field>
            <field name="Publisher" start="0" length="0" align="left" pad=" ">${publisher}</field>
            <field name="Conductor" start="0" length="0" align="left" pad=" ">${conductor}</field>
            <field name="Lyricist" start="0" length="0" align="left" pad=" ">${lyricist}</field>
            <field name="Remixer" start="0" length="0" align="left" pad=" ">${remixer}</field>
            <field name="Producer" start="0" length="0" align="left" pad=" ">${producer}</field>
            <field name="Bitrate" start="0" length="0" align="left" pad=" ">${bitrate}</field>
            <field name="Options" start="0" length="0" align="left" pad=" ">${options}</field>
            <field name="TrackEnd" start="0" length="0" align="left" pad=" " mapping="TrackEndIndicator">${trackendindicator}</field>
            <field name="CueIn" start="0" length="0" align="left" pad=" ">${cueinms}</field>
            <field name="FullLevel" start="0" length="0" align="left" pad=" ">${fulllevelms}</field>
            <field name="Ramp" start="0" length="0" align="left" pad=" ">${rampms}</field>
            <field name="Ramp2" start="0" length="0" align="left" pad=" ">${ramp2ms}</field>
            <field name="Outro" start="0" length="0" align="left" pad=" ">${outroms}</field>
            <field name="FadeOut" start="0" length="0" align="left" pad=" ">${fadeoutms}</field>
            <field name="Next" start="0" length="0" align="left" pad=" ">${nextms}</field>
            <field name="CueOut" start="0" length="0" align="left" pad=" ">${cueoutms}</field>
            <field name="HookCueIn" start="0" length="0" align="left" pad=" ">${hookcueinms}</field>
            <field name="HookFullLevel" start="0" length="0" align="left" pad=" ">${hookfulllevelms}</field>
            <field name="HookRamp" start="0" length="0" align="left" pad=" ">${hookrampms}</field>
            <field name="HookRamp2" start="0" length="0" align="left" pad=" ">${hookramp2ms}</field>
            <field name="HookOutro" start="0" length="0" align="left" pad=" ">${hookoutroms}</field>
            <field name="HookFadeOut" start="0" length="0" align="left" pad=" ">${hookfadeoutms}</field>
            <field name="HookNext" start="0" length="0" align="left" pad=" ">${hooknextms}</field>
            <field name="HookCueOut" start="0" length="0" align="left" pad=" ">${hookcueoutms}</field>
            <field name="Comment" start="0" length="0" align="left" pad=" " mapping="ReplaceCRLF">${comment}</field>
            <field name="ModText" start="0" length="0" align="left" pad=" " mapping="ReplaceCRLF">${moderatortext}</field>
        </fields>
        <mappings>
            <mapping name="ReplaceCRLF">
                <map value="${CRLF}">-CRLF-</map>
                <map value="${CR}">-CR-</map>
                <map value="${LF}">-LF-</map>
            </mapping>
            <mapping name="TrackEndIndicator">
	        <map value="|">Cold</map>
	        <map value="\">Fade</map>
            </mapping>
        </mappings>
    </format>
As this export format is a simple TAB separated file format (in the order of the above fields), you might adopt the related Music1 import/mapping accordingly.

To your detailed questions:

Filename and Cart:
Yes, we decided to split this (path and filename) into 2 fields, as Music1 has some internal limitations with repect the total length of a single Music1 field - which is (if I remember it correctly) something like 128 or 160 characters.
A fully qualified filename however might be up to 260 characters long!
So we decided to use 2 fields in the export - so that you might combine them on the Music1 side.
So you might do 2 alternative things:
a) change the ProppFrexx.exportformats definition (e.g. by using the ${filenameandpath} instead of the ${directoryname} macro)
b) change the Music1 import settings/mappings and combine the 2 fields into a single combined one

TrackEnd:
That must be a pure settings/mapping thing on the Music1 side!

HookIn, HookOut:
That must be a pure settings/mapping thing on the Music1 side! But I am not sure, if those fields do exist in the Music1 standard.
Note, that you can create any number of 'custom' fields within Music1 and if so, you must adopt the import settings/mappings of Music1 accordingly.

When talking about 'seamless integration' I was mainly talking about the scheduler log-import and the ProppFrexx side of the world.
Unfortunately I can not force 3rd party companies to do the same...

Exporting meta data to Music1 and setting up of custom attributes within Music1 is always a 'custom' processing step - at least that is the point of view of Music1.
So I am also contacting the Music1 guys again to ask for a more 'streamlined' import on their side!

TheoOrl45
Posts: 111
Joined: 23 Apr 2012 00:28

Re: Music 1 integration

Post by TheoOrl45 » 22 Feb 2013 01:21

Hi Bernd,


Something strange....
I created a music1 log for 2013.02.22... Here is an extract :

Code: Select all

Log Time	Cue	Event Type	Length	Nominal Time	Cart	Title	Notes
						M1PF _LOG Version = 1	
00:00:00	+	AUD	0:00:33.853		98354124-ef0f-4846-b342-02ea9c63b78b	TOTH_001	
00:00:34	+	MUS	0:03:20		This song card can be overwritten or deleted.	Test Song Card	
00:03:59	+	MUS	0:03:37.63		aacd7518-6179-4ca3-ae10-6fdf7e5ff731	The spell	
00:07:37	+	AUD	0:00:11.063		7be90661-c889-48f4-8786-db7564529e3c	BASIC ID_001	
00:07:48	+	MUS	0:03:47.414		f8dd43f7-0c24-4c28-bcf2-2d56756be7be	If I had you	
(The second line is a mistake, but these are tests ^^).

I import this one and here is the .pfp playlist result (within the C:\Users\<user>\AppData\Roaming\radio42\ProppFrexx ONAIR\3.0\Music1 ProppFrexx folder):

Code: Select all

<?xml version="1.0" encoding="utf-8"?>
<playlist version="1" xmlns:pf="http://proppfrexx.radio42.com" xmlns="http://xspf.org/ns/0/">
    <title>P20130222_0000</title>
    <creator>ProppFrexx ONAIR</creator>
    <date>2013-02-22T00:55:16.3046047+01:00</date>
    <trackList>
        <track>
            <location>D:\_RADIO@HOME\PXX_AUDIO_DATA\98354124-ef0f-4846-b342-02ea9c63b78b</location>
            <duration>33853</duration>
            <identifier>bcd7f7ae-bfa6-488d-a285-021bd63bd78b</identifier>
            <title>TOTH_001</title>
            <extension application="http://proppfrexx.radio42.com">
                <pf:settings>
                    <pf:general>
                        <pf:entryType>200</pf:entryType>
                    </pf:general>
                    <pf:cuePoints />
                </pf:settings>
            </extension>
        </track>
        <track>
Not sure the location is correct...
By the way, running scheduler after import had not driven to load the playlist...nothing occured except :
M1 @ 20130222_00 (User defined)
Music 1 ProppFrexx [Import] [NOT FOUND!] Soft
2013.02.22 00:00:00 - 2013.02.22 23:59:59
Bugs ?
Theo, from France.

User avatar
radio42
Site Admin
Posts: 6391
Joined: 05 Apr 2012 16:26

Re: Music 1 integration

Post by radio42 » 22 Feb 2013 08:56

Looks like the import failed and various entries could not be resolved - probably because the GUIDs are incorrect.
Can you please post me the screen shots of the Program Scheduler Import dialog once you clicked the 'Rad Log File' button!
In addition which .pfs script is being created and how dows the created program scheduler entry looks like?

Post Reply

Who is online

Users browsing this forum: No registered users and 22 guests