<?xml version="1.0" encoding="UTF-8"?>
<!-- This is a sample Schedule with possible keys and values to be set. MANDATORY keys can not be ommited. RECOMMENDED keys can be ommited but we strongly recommend using them. OPTIONAL keys are only if you want to add more info to your schedule (such as in/out points,etc.) -->
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<!-- NOTE: UniqueIDs listed below can be formatted the way you want, they just need to be unique. -->
<dict>
	<!-- OPTIONAL - This is what the user will see as the name of the schedule, only important if schedule does not yet exist and will be created. IGNORED if schedule UID already exists. -->
	<!-- If not provided in XML, will be set to "Unkown" if a new schedule must be created (no UID found)-->			
	<key>displayName</key>
	<string>MySchedule</string>
	<!-- MANDATORY - This is the start date and time of the region that will be cleared and reimported with the xml info below. Must be within boundaries of existing schedule in our database-->	
	<!-- !!! WARNING !!! All the events and playlists between the startDateTime and the endDateTime will be DELETED from the current schedule - so make sure to change these values according to what you want to update in your schedule-->	
	<key>startDateTime</key>
	<date>2013-09-29T22:00:00Z</date>
	<!-- MANDATORY - This is the end date and time of the region that will be cleared and reimported with the xml info below. Must be within boundaries of existing schedule in our database-->
	<key>endDateTime</key>
	<date>2013-10-08T23:00:00Z</date>
	<!-- MANDATORY - this is the schedule UID. It is important that it stays the same between updates -->	
	<key>uniqueID</key>
	<string>0F87B1AC-8184-4A29-AB0C-350470398E93</string>
	<!-- This is the list of items into the schedule. Each item of the schedule is an "event" (with a start date and time). A schedule contains multiple events.  -->
	<!-- WARNING: There is no consitency check during import. You MUST make sure that there is no overlap between the events for best behaviours  -->
	<key>items</key>
	<array>
		<dict>
			<!-- RECOMMENDED - this is what the user will see as the name of the event (and on top of the playlist editor), so it IS important -->
			<!-- If not provided in XML, will be set to "Unkown" -->			
			<key>displayName</key>
			<string>My First Event Name</string>
			<!-- MANDATORY - This is the START date and time of the event. Only events within the schedule start and end will be imported-->	
			<key>startDateTime</key>
			<date>2013-10-07T15:00:00Z</date>
			<!-- MANDATORY - This is the END date and time of the event. Only events within the schedule start and end will be imported-->	
			<key>endDateTime</key>
			<date>2013-10-07T15:30:00Z</date>
			<!-- An event holds one and only one playlist (the event's playlist). This playlist can then contain other playlists or clips-->
			<key>items</key>
			<array>
				<dict>
					<!-- MANDATORY - As this item is the event's playlist, it can only be the type = Playlist -->					
					<key>type</key>
					<string>Playlist</string>				
					<!-- RECOMMENDED - This is the playback UID of the event, MUST be consistent between each import. MUST be unique.-->			
					<!-- If not provided in XML, A new playbackUniqueID will be created. Must be set if you want to be able to update schedules. Does not need to be set if schedules are imported only once.-->	
					<key>playbackUniqueID</key>
					<string>993AD714-597A-4C04-8DAB-E7566FF88D33</string>
					<!-- OPTIONAL - Sets if the Event is Looping or not -->
					<key>isLooping</key>
					<false/>
					<!-- OPTIONAL - Sets the attributes of the playlist item - will be applied to all items within that playlist, unless an attribute is specified for these items -->
					<!-- Attributes must match the exact name. You can get the name of the possible attributes for a Node by connecting to it in Telnet -->
					<key>attributes</key>
					<dict>
						<!-- BUILT-IN ATTRIBUTES - Invariable -->
						<!-- Sets the audio volume of the clip. From 0.0 to 1.0. There is no gain. -->
						<key>Audio Volume</key>
						<string>0.5</string>
						<!-- Sets what should happen at the end of the clip. Can either be "Normal" (next clip will chain) or "Loop" (Clip will loop => the rest of the event after that point will not be played. -->
						<key>Clip End Behaviour</key>
						<string>Normal</string>
						<!-- For interlaced materials, if the field priority is wrong, allows to invert it without reexporting the clip. -->
						<key>Reverse Field Order</key>
						<string>Reversed</string>
						<!-- BUILT-IN ATTRIBUTES - Variable = need configuration in the Node selected in the schedule window in OnTheAir Manager -->
						<!-- Sets which logo overlay file will be used for that clip. The file must be present in the "Overlay Logos Folder" set in the OnTheAir Node system preference pane. Logo option required.  -->
						<key>Overlay Logo</key>
						<string>LIVE_HD.png</string>								
						<!-- Sets if an AppleScript must be triggered at the start/end of a clip. The key must start by "AppleScript", then a space and the name of the AppleScript file. The AppleScript must be written with "On Action" parametrers and must be placed in the "AppleScript" folder in this folder: /Library/Application Support/Softron/OnTheAir Node/  -->
						<key>AppleScript Start Record</key>
						<string>1</string>
						<!-- PLUG-INS ATTRIBUTES - Must be configured in the Plug-Ins tab of the OnTheAir Node system preference pane for the Node selected in the schedule window of OnTheAir Manager. -->
						<!-- Below are some examples of typical attributes -->
						<key>CG Project /Applications/OnTheAir CG/Projects/Ticker.cg</key>
						<string>On</string>
						<key>GPICommander Output 1</key>
						<string>On</string>
						<key>Videohub Output 1</key>
						<string>0003 Quad Out 1</string>
					</dict>
					<!-- This is the list of items of a Playlist. A playlist can contain multiple and different items (clips, sub-playlists or live events).-->
					<key>items</key>
					<array>
						<dict>
							<!-- MANDATORY - Type of item: "MediaItem" (for clips), "Playlist" (for sub-playlists)  or "External" (for live events) -->						
							<key>type</key>
							<string>MediaItem</string>
							<!-- MANDATORY - The path to the media. -->																	
							<!-- All Media must reside in one of the Media Folders available for OnTheAir Manager. Media Folders are set in OnTheAir Node.-->	
							<!-- Schedule import will be rejected if one clip is out of the Media Folders -->	
							<key>clipInfoAbsolutePathToMediaItem</key>
							<string>/Users/pierre/Movies/Animation_BigBuckBunny.mov</string>
							<!-- RECOMMENDED - This is the playback UID of the item, MUST be consistent between each import. MUST be unique.-->			
							<!-- If not provided in XML, A new playbackUniqueID will be created. Must be set if you want to be able to update schedules. Does not need to be set if schedules are imported only once.-->	
							<key>clipInfoPlaybackUniqueID</key>
							<string>1F13799D-1C36-44F8-9783-B85962E2C9D1</string>
							<!-- OPTIONAL - Sets if the Media is Looping or not -->
							<key>isLooping</key>
							<false/>
							<!-- OPTIONAL - Sets in and out points for a media item. HasIn or HasOut point must be set to "true", the value must be entered within boundaries of the media -->
							<key>clipInfoHasInPoint</key>
							<false/>
							<key>clipInfoInPointInSeconds</key>
							<real>0.0</real>							
							<key>clipInfoHasOutPoint</key>
							<true/>
							<key>clipInfoOutPointInSeconds</key>
							<real>5</real>
							<!-- OPTIONAL - Sets the media item size and position -->
							<key>clipInfoDisplayVideoSizeWidth</key>
							<real>1920</real>							
							<key>clipInfoDisplayVideoSizeHeight</key>
							<real>1080</real>
							<key>clipInfoDisplayVideoOriginX</key>
							<real>0.0</real>
							<key>clipInfoDisplayVideoOriginY</key>
							<real>0.0</real>
							<!-- OPTIONAL - Sets the attributes of the media item -->
							<!-- Attributes must match the exact name. You can get the name of the possible attributes for a Node by connecting to it in Telnet -->
							<key>clipInfoAttributes</key>
							<dict>
								<!-- BUILT-IN ATTRIBUTES - Invariable -->
								<!-- Sets the audio volume of the clip. From 0.0 to 1.0. There is no gain. -->
								<key>Audio Volume</key>
								<string>0.5</string>
								<!-- Sets what should happen at the end of the clip. Can either be "Normal" (next clip will chain) or "Loop" (Clip will loop => the rest of the event after that point will not be played. -->
								<key>Clip End Behaviour</key>
								<string>Normal</string>
								<!-- For interlaced materials, if the field priority is wrong, allows to invert it without reexporting the clip. -->
								<key>Reverse Field Order</key>
								<string>Reversed</string>
								<!-- BUILT-IN ATTRIBUTES - Variable = need configuration in the Node selected in the schedule window in OnTheAir Manager -->
								<!-- Sets which logo overlay file will be used for that clip. The file must be present in the "Overlay Logos Folder" set in the OnTheAir Node system preference pane. Logo option required.  -->
								<key>Overlay Logo</key>
								<string>LIVE_HD.png</string>								
								<!-- Sets if an AppleScript must be triggered at the start/end of a clip. The key must start by "AppleScript", then a space and the name of the AppleScript file. The AppleScript must be written with "On Action" parametrers and must be placed in the "AppleScript" folder in this folder: /Library/Application Support/Softron/OnTheAir Node/  -->
								<key>AppleScript Start Record</key>
								<string>1</string>
								<!-- PLUG-INS ATTRIBUTES - Must be configured in the Plug-Ins tab of the OnTheAir Node system preference pane for the Node selected in the schedule window of OnTheAir Manager. -->
								<!-- Below are some examples of typical attributes from plugins-->
								<key>CG Project /Applications/OnTheAir CG/Projects/Ticker.cg</key>
								<string>On</string>
								<key>GPICommander Output 1</key>
								<string>On</string>
								<key>Videohub Output 1</key>
								<string>0003 Quad Out 1</string>
							</dict>
						</dict>
						<dict>
							<!-- MANDATORY - Type of item: "MediaItem" (for clips), "Playlist" (for sub-playlists)  or "External" (for live events) -->						
							<key>type</key>
							<string>Playlist</string>
							<!-- RECOMMENDED - this is what the user will see as the name of the playlist, so it IS important -->
							<!-- If not provided in XML, will be set to "Unkown" -->			
							<key>displayName</key>
							<string>A Sub Playlist For Daniel</string>
							<!-- RECOMMENDED - This is the playback UID of the item, MUST be consistent between each import. MUST be unique.-->			
							<!-- If not provided in XML, A new playbackUniqueID will be created. Must be set if you want to be able to update schedules. Does not need to be set if schedules are imported only once.-->	
							<key>playbackUniqueID</key>
							<string>CDE542C4-5DEB-4B29-97FB-A12AC00E4C18</string>							
							<!-- RECOMMENDED - This is the Unique ID for the playlist. It is different then the playbackUniqueID in that it does not need to be unique in the schedule. Indeed, you can replay the same playlist multiple times in one schedule. -->
							<!-- If not set, a new playlist will be created upon each import. So users can end up with thousands of playlists in browser. -->
							<key>uniqueID</key>
							<string>654EFR3-15G5-4C35-CFR4-9791457DRFGH</string>
							<!-- OPTIONAL - Sets if the Playlist is Looping or not -->
							<key>isLooping</key>
							<false/>
							<!-- OPTIONAL - Sets if a Preset duration to a sub-Playlist: does not have an impact, is only informational and will display offsets if the playlist does not have that preset duration -->
							<key>presetDurationInSeconds</key>
							<real>60.0</real>
							<!-- This is the list of items of a Playlist. A playlist can contain multiple and different items (clips, sub-playlists or live events).-->
							<key>items</key>
							<array>
								<dict>
									<!-- MANDATORY - Type of item: "MediaItem" (for clips), "Playlist" (for sub-playlists)  or "External" (for live events) -->						
									<key>type</key>
									<string>External</string>						
									<!-- RECOMMENDED - this is what the user will see as the name of the Live, so it IS important -->
									<!-- If not provided in XML, will be set to "Unkown" -->
									<!-- Will be ignored if clipInfoUniqueID already exists in our database -->
									<key>clipInfoDisplayName</key>
									<string>Live Clip</string>
									<!-- MANDATORY - Duration of the Live Event -->		
									<!-- Will be ignored if clipInfoUniqueID already exists in our database -->													
									<key>clipInfoDurationInSeconds</key>
									<real>3600</real>
									<!-- RECOMMENDED - This is the playback UID of the item, MUST be consistent between each import. MUST be unique.-->			
									<!-- If not provided in XML, A new playbackUniqueID will be created. Must be set if you want to be able to update schedules. Does not need to be set if schedules are imported only once.-->	
									<key>clipInfoPlaybackUniqueID</key>
									<string>EC7DADC6-BC16-4B93-BDA9-41F239943237</string>
									<!-- RECOMMENDED - This is the UID of the Live event, MUST be consistent between each import. MUST be unique.-->			
									<!-- If not provided in XML, A new Live clip will be created in Media Browser upon every import.  -->	
									<key>clipInfoUniqueID</key>
									<string>D7A8A9AE-C822-4AE0-8C57-D9BCE81BC19C</string>
									<!-- OPTIONAL - Sets in and out points for a Live Clip (so you can reuse the same Live clip multiple times, with different durations). HasIn or HasOut point must be set to "true", the value must be entered within boundaries of the duration of the Live (first time it was created with that UID) => the first time it is created it should be done with a long duration -->
									<key>clipInfoHasInPoint</key>
									<false/>
									<key>clipInfoInPointInSeconds</key>
									<real>0.0</real>							
									<key>clipInfoHasOutPoint</key>
									<true/>
									<key>clipInfoOutPointInSeconds</key>
									<real>5</real>									
								</dict>
							</array>
						</dict>
					</array>
				</dict>
			</array>
		</dict>
	</array>
</dict>
</plist>
