# Working with the schedule (console)


You can use the AWS Elemental MediaLive console to create or delete any of the [schedule actions](x-actions-in-schedule.md) in a channel. You can work with the schedule when the channel is running or when it is idle. 

The actions are performed in the channel when the channel is running.

The console provides two views for working with actions:
+ A list view that lists actions in tabular format
+ A timeline view that shows a timeline representation of the actions

In either view, you can do the following:
+ Create individual actions.
+ Delete individual actions.
+ Delete several actions in one request (a batch command).
+ View the actions currently in the schedule.

**Topics**
+ [

# Creating actions in the schedule (console)
](schedule-using-console-create.md)
+ [

# Deleting actions from the schedule (console)
](schedule-using-console-delete.md)
+ [

# Modifying actions in the schedule (console)
](schedule-modify.md)
+ [

# Viewing the schedule (console)
](schedule-using-console-view.md)

# Creating actions in the schedule (console)
Creating actions

You can create different actions in the schedule. For a list of supported actions, see [Types of actions in the schedule](x-actions-in-schedule.md).

The general procedure is the same to create any type of action.

**To create an action**

1. Read the information about [planning the actions](sched-how-actions-work.md) you want to add. 

1. Open the MediaLive console at [https://console.aws.amazon.com/medialive/](https://console.aws.amazon.com/medialive/).

1. In the navigation pane, choose **Channel**, and then choose the channel that you want to work with.

1. On the **Details** pane, choose the **Schedule** tab.

1. Choose the **Switch** button to display the view that you want: **List** view or **Timeline** view. For information about the layout and color coding of the timeline view, see [Viewing the schedule (console)](schedule-using-console-view.md).

1. For **List** view, choose the appropriate action:
   + To create a fixed, follow, or immediate action from scratch, choose **Create**. 
   + To create a follow action after an existing action, choose that action, choose **Schedule actions**, and then choose **Create follow actions from**. 

     This method displays the **Create schedule action** page with some fields already completed, so you can quickly create a follow switch for that existing action.

1. For **Timeline** view, choose the appropriate action:
   + To create a fixed, follow, or immediate action from scratch, choose **Create**.
   + To create a follow action, find the input switch that you want to follow, and then choose **Create follow action** in that card.

     This method displays the **Create schedule action** page with some fields already completed, so you can quickly create a follow switch for that existing action.

1. On the **Create schedule action** page, complete the fields. For information about completing the fields, see the following topics.

1. When you have finished, choose **Create**.

   MediaLive adds the action to the list or the timeline at its appropriate time slot. 

When you create a follow input switch, you effectively create an *input follow chain*. The input follow chain starts with the input above the first follow and ends with the last follow input. For more information about input follow chains, see [Fixed, immediate, and follow switches](ips-switch-types.md).

**Topics**
+ [

# Fields for an input switch
](schedule-fields-for-ips.md)
+ [

# Fields for an input prepare
](schedule-fields-for-input-prep.md)
+ [

# Fields for activating a global image overlay
](schedule-fields-for-activate-image.md)
+ [

# Fields for deactivating a global image overlay
](schedule-fields-for-deactivate-image.md)
+ [

# Fields for activating a per-outputs image overlay
](schedule-fields-activate-image-per-output.md)
+ [

# Fields for deactivating a per-outputs image overlay
](schedule-fields-deactivate-image-per-output.md)
+ [

# Fields for activating a motion graphics overlay
](schedule-fields-for-mg.md)
+ [

# Fields for deactivating a motion graphics overlay
](schedule-fields-for-mg-deactivate.md)
+ [

# Fields for a splice\$1insert message
](schedule-fields-for-splice_insert.md)
+ [

# Fields for a time\$1signal message
](schedule-fields-for-time-signal.md)
+ [

# Fields for a return-to-network message
](schedule-fields-for-return-to-network.md)
+ [

# Fields for ID3 metadata
](schedule-fields-for-id3-userdata.md)
+ [

# Fields for ID3 segment tags
](schedule-fields-for-id3-segment-tags.md)
+ [

# Fields for pause
](schedule-fields-for-pause.md)
+ [

# Fields for unpause
](schedule-fields-for-unpause.md)

# Fields for an input switch
Input switch

This section describes how to complete the fields for these three types of input switches:
+ A switch to a static live input 
+ A switch to a static file input 
+ A switch to a dynamic file input

**Topics**
+ [

## Fields for a switch to a static live input
](#schedule-fields-ips-static-live)
+ [

## Fields for a switch to a static file input
](#schedule-fields-ips-static-file)
+ [

## Fields for a switch to a dynamic file input
](#schedule-fields-ips-static-dynamic)

## Fields for a switch to a static live input
Static live input

This table shows the fields that apply for an action to switch to a static live input. 


| Field | Description | 
| --- | --- | 
| Action name |  A name for this input switch.  | 
| Action type |  Input Switch. | 
| Input attachment | The live input to switch to. The input must already be set up as an [input attachment](creating-a-channel-step2.md) in this channel. For example, if you want to switch from input A to input B, specify input B in this field. | 
| Start type  | Fixed, Immediate, or Follow. For information about start types for input prepare, see [Fixed, immediate, and follow switches](ips-switch-types.md). | 
| Date and time | If the Start type is Fixed, specify the date and time (in UTC format) that the channel must switch to this new input. This time must be at least 30 seconds in the future.Note that the time is the wall clock time, not the timecode in the input. | 
| Reference action name |  If the **Start type** is **Follow**, choose the input to switch from, which is the input that precedes this new input. The dropdown list shows all existing input switches that are file inputs. Remember that input B can follow input A only if input A is a file input and the source end behavior for input A is *continue*. For information about these switching rules, see [Fixed, immediate, and follow switches](ips-switch-types.md). For example, if you want to switch from input A to input B, specify input A in this field.  | 
| Follow point | If the Start type is Follow, complete this field. The follow point is always End, to indicate that the switch will occur when the input in Reference action name has finished. | 

## Fields for a switch to a static file input
Static file input

This table shows the fields that apply for an action to switch to a static file input. 


| Field | Description | 
| --- | --- | 
| Action name |  A name for this input switch.  | 
| Action type |  Input Switch. | 
| Input attachment | The file input to switch to. The input must already be set up as an [input attachment](creating-a-channel-step2.md) in this channel. For example, if you want to switch from input A to input B, specify input B in this field. | 
| Input clippings settings – Enable input clipping | This field appears only for a file input that is [eligible for input clipping](input-clipping.md).Enable the field if you want to clip the file at the start and end, or only at the start, or only at the end. | 
| Input clippings settings – Input timecode source |  Choose the source: Zero-based – To set the start and end times relative to the start of the file, which is 00:00:00:00. Embedded – To set the times based on the timecode in the file. The file must have a timecode, otherwise the clipping instruction is ignored.  | 
| Input clippings settings – Start timecode, Stop timecode |  Complete one or both fields. Enter values in the format hh:mm:ss:ff.  | 
| Input clippings settings – Last frame clipping behavior | This field appears only if you specify a stop timecode. Exclude last frame – Clip the file before the frame specified in the end timecode. For example, if the end timecode is 01:00:30:19, don't include frame 19.Include last frame – Don't clip the file. In the preceding example, include frame 19. | 
| Start type  | Fixed, Immediate, or Follow. For information about start types for input prepare, see [Fixed, immediate, and follow switches](ips-switch-types.md). | 
| Date and time | If the Start type is Fixed, specify the date and time (in UTC format) that the channel must switch to this new input. This time must be at least 30 seconds in the future.Note that the time is the wall clock time, not the timecode in the input. | 
| Reference action name |  If the **Start type** is **Follow**, choose the input to switch from, which is the input that precedes this new input. The dropdown list shows all existing input switches that are file inputs. Remember that input B can follow input A only if input A is a file input. For information about these switching rules, see [Fixed, immediate, and follow switches](ips-switch-types.md). For example, if you want to switch from input A to input B, specify input A in this field.  | 
| Follow point | If the Start type is Follow, complete this field. The follow point is always End, to indicate that the switch will occur when the input in Reference action name has finished. | 

## Fields for a switch to a dynamic file input
Dynamic file input

This table shows the fields that apply for an action to switch to a dynamic file input. 


| Field | Description | 
| --- | --- | 
| Action name |  A name for this input switch.  | 
| Action type |  Input Switch. | 
| Input attachment | The file input to switch to. The input must already be set up as an [input attachment](creating-a-channel-step2.md) in this channel.For example, if you want to switch from input A to input B, specify input B in this field. | 
| Dynamic input setting – URL path for input source A | This field appears if the input is set up as a [dynamic input](dynamic-inputs.md). Enter a value to replace the \$1urlPath\$1 portion of the URL for source A in the input. A hint below the fields shows the URL path that you created for this source. | 
| Dynamic input setting – Use the same URL path for input source B | This field appears if the input is attached to a standard channel, meaning that it has two pipelines and therefore has two sources.Enable this field (the default) if you want to use the same value for the `$urlPath$` in source A and source B.Disable this field to use a different value, then enter the value. | 
| Input clippings settings – Enable input clipping | This field appears only for a file input.Enable the field if you want to clip the file at the start and end, or only at the start, or only at the end. | 
| Input clippings settings – Input timecode source |  Choose the source: Zero-based – To set the start and end times relative to the start of the file, which is 00:00:00:00. Embedded – To set the times based on the timecode in the file. The file must have a timecode, otherwise the clipping instruction is ignored.  | 
| Input clippings settings – Start timecode, Stop timecode |  Complete one or both fields. Enter values in the format hh:mm:ss:ff.  | 
| Input clippings settings – Last frame clipping behavior | This field appears only if you specify a stop timecode. Exclude last frame – Clip the file before the frame specified in the end timecode. For example, if the end timecode is 01:00:30:19, don't include frame 19.Include last frame – Don't clip the file. In the preceding example, include frame 19. | 
| Start type  | Fixed, Immediate, or Follow. For information about start types for input prepare, see [Fixed, immediate, and follow switches](ips-switch-types.md). | 
| Date and time | If the Start type is Fixed, specify the date and time (in UTC format) when the channel must switch to this new input. This time must be at least 30 seconds in the future.Note that the time is the wall clock time, not the timecode in the input. | 
| Reference action name |  If the **Start type** is **Follow**, choose the input to switch from, which is the input that precedes this new input. The dropdown list shows all existing input switches that are file inputs. Remember that input B can follow input A only if input A is a file input. For information about these switching rules, see [Fixed, immediate, and follow switches](ips-switch-types.md). For example, if you want to switch from input A to input B, specify input A in this field.  | 
| Follow point | If the Start type is Follow, complete this field. The follow point is always End, to indicate that the switch will occur when the input in Reference action name has finished. | 

# Fields for an input prepare
Input prepare

This section describes how to complete the fields for these three types of input prepares:
+ A prepare of a static live input 
+ A prepare of a static file input 
+ A prepare of a dynamic file input

## Fields for a prepare of a static live input
Static live input

This table shows the fields that apply for an action to prepare a static live input. 


| Field | Description | 
| --- | --- | 
| Action name |  A name for this input prepare.  | 
| Action type |  Input Prepare. | 
| Input attachment | The live input to prepare. The input must already be set up as an [input attachment](creating-a-channel-step2.md) in this channel. | 
| Start type  | Fixed, Immediate, or Follow. For information about start types for input prepare, see [Types of starts for input prepares](plan-prep-start-types.md). | 
| Date and time | If the Start type is Fixed, specify the date and time (in UTC format) that the channel must start to prepare the input. This time should be at least 10 seconds before the upcoming input switch.Note that the time is the wall clock time, not the timecode in the input. | 
| Reference action name |  If the **Start type** is **Follow**, choose the input to follow. This input is the input whose end you want to use as the trigger for the input prepare. It is not the input for the upcoming input switch. The dropdown list shows all existing input switches. If the input switch that you want to use as the reference (trigger) isn't listed, you need to first create that input switch. For information about start types for input prepare, see [Types of starts for input prepares](plan-prep-start-types.md).  | 
| Follow point | If the Start type is Follow, complete this field. The follow point is always End, to indicate that the input prepare will occur when the input in Reference action name has finished. | 

## Fields for a prepare of a static file input
Static file input

This table shows the fields that apply for an action to prepare a static file input. 


| Field | Description | 
| --- | --- | 
| Action name |  A name for this input prepare.  | 
| Action type |  Input Prepare. | 
| Input attachment | The file input to prepare. The input must already be set up as an [input attachment](creating-a-channel-step2.md) in this channel. | 
| Input clippings settings – Enable input clipping | This field appears only for a file input that is [eligible for input clipping](input-clipping.md).Enable the field if the upcoming input switch (which you are preparing) will also be clipped. You must set up the prepare action with identical clipping instructions as the switch action. | 
| Input clippings settings – Input timecode source |  Choose the source: Zero-based – To set the start and end times relative to the start of the file, which is 00:00:00:00. Embedded – To set the times based on the timecode in the file. The file must have a timecode, otherwise the clipping instruction is ignored. Make sure you choose the same source in this prepare action and the upcoming switch action.  | 
| Input clippings settings – Start timecode, Stop timecode |  Complete one or both fields. Enter values in the format hh:mm:ss:ff. Make sure you enter the same values in this prepare action and the upcoming switch action.  | 
| Input clippings settings – Last frame clipping behavior | This field appears only if you specify a stop timecode. Exclude last frame – Clip the file before the frame specified in the end timecode. For example, if the end timecode is 01:00:30:19, don't include frame 19.Include last frame – Don't clip the file. In the preceding example, include frame 19.Make sure you choose the same option in this prepare action and the upcoming switch action. | 
| Start type  | Fixed, Immediate, or Follow. For information about start types for input prepare, see [Types of starts for input prepares](plan-prep-start-types.md). | 
| Date and time | If the Start type is Fixed, specify the date and time (in UTC format) that the channel must start to prepare this input. This time should be at least 10 seconds before the upcoming input switch.Note that the time is the wall clock time, not the timecode in the input. | 
| Reference action name |  If the **Start type** is **Follow**, choose the input to follow. This input is the input whose end you want to use as the trigger for the input prepare. It is not the input for the upcoming input switch. The dropdown list shows all existing input switches. If the input switch that you want to use as the reference (trigger) isn't listed, you need to first create that input switch. For information about start types for input prepare, see [Types of starts for input prepares](plan-prep-start-types.md).  | 
| Follow point | If the Start type is Follow, complete this field. The follow point is always End, to indicate that the input prepare will occur when the input in Reference action name has finished. | 

## Fields for a prepare of a dynamic file input
Dynamic file input

This table shows the fields that apply for an action to prepare a dynamic file input. 


| Field | Description | 
| --- | --- | 
| Action name |  A name for this input prepare.  | 
| Action type |  Input Prepare. | 
| Input attachment | The file input to prepare. The input must already be set up as an [input attachment](creating-a-channel-step2.md) in this channel. | 
| Dynamic input setting – URL path for input source A | This field appears if the input is set up as a [dynamic input](dynamic-inputs.md). Enter a value to replace the `$urlPath$` portion of the URL for source A in the input. A hint below the fields shows the URL path that you created for this source.Make sure you enter the same values in this prepare action and the upcoming switch action. | 
| Dynamic input setting – Use the same URL path for input source B | This field appears if the input is attached to a standard channel, meaning that it has two pipelines and therefore has two sources.Enable this field (the default) if you want to use the same value for the `$urlPath$` in source A and source B.Disable this field to use a different value, then enter the value.Make sure you choose the same option in this prepare action and the upcoming switch action. | 
| Input clippings settings – Enable input clipping | This field appears only for a file input that is [eligible for input clipping](input-clipping.md).Enable the field if the upcoming input switch (which you are preparing) will also be clipped. You must set up the prepare action with identical clipping instructions as the switch action. | 
| Input clippings settings – Input timecode source |  Choose the source: Zero-based – To set the start and end times relative to the start of the file, which is 00:00:00:00. Embedded – To set the times based on the timecode in the file. The file must have a timecode, otherwise the clipping instruction is ignored. Make sure you choose the same source in this prepare action and the upcoming switch action.  | 
| Input clippings settings – Start timecode, Stop timecode |  Complete one or both fields. Enter values in the format hh:mm:ss:ff. Make sure you enter the same values in this prepare action and the upcoming switch action.  | 
| Input clippings settings – Last frame clipping behavior | This field appears only if you specify a stop timecode. Exclude last frame – Clip the file before the frame specified in the end timecode. For example, if the end timecode is 01:00:30:19, don't include frame 19.Include last frame – Don't clip the file. In the preceding example, include frame 19.Make sure you choose the same option in this prepare action and the upcoming switch action. | 
| Start type  | Fixed, Immediate, or Follow. For information about start types for input prepare, see [Types of starts for input prepares](plan-prep-start-types.md). | 
| Date and time | If the Start type is Fixed, specify the date and time (in UTC format) that the channel must start to prepare this input. This time should be at least 10 seconds before the upcoming input switch.Note that the time is the wall clock time, not the timecode in the input. | 
| Reference action name |  If the **Start type** is **Follow**, choose the input to follow. This input is the input whose end you want to use as the trigger for the input prepare. It is not the input for the upcoming input switch. The dropdown list shows all existing input switches. If the input switch that you want to use as the reference (trigger) isn't listed, you need to first create that input switch.  | 
| Follow point | If the Start type is Follow, complete this field. The follow point is always End, to indicate that the input prepare will occur when the input in Reference action name has finished. | 

# Fields for activating a global image overlay
Activate global image overlay

This table shows the fields that apply for an action to activate an image overlay. 


| Field | Description | 
| --- | --- | 
| Action type | Static Image Activate. | 
| Action name | A name for this activation action. For example, the layer and the name of the image to overlay.  | 
| Start type  | Fixed or Immediate. | 
| Date and time |  The date and time (in UTC format) that the channel must activate the image overlay. The time should be at least 60 seconds later than the time that you submit the action.  Note that the time is the wall clock time, not the timecode in the input.  | 
| Input location | Enter the locations (URLs) on the server where the image file is stored.Also complete **Credentials**, if the server requires that you provide user credentials. | 
| Other fields | Complete these fields to control the layer, position, look (such as fade-in), and other behavior of the image.  | 

# Fields for deactivating a global image overlay
Deactivate global image overlay

This table shows the fields that apply for an action to deactivate an image overlay. 


| Field | Description | 
| --- | --- | 
| Action type | Static Image Deactivate.  | 
| Action name | A name for this deactivation action. For example, the name of the image. Or a name that ties back to the activation action plus the term "deactivate." | 
| Start type  | Fixed or Immediate. | 
| Date and time |  If the **Start type** is **Fixed**, specify the date and time (in UTC format) that the channel must deactivate the image overlay. The time should be at least 60 seconds later than the time that you submit the action.  Note that the time is the wall clock time, not the timecode in the input.  | 
| Layer | Enter the layer that contains the image overlay that you want to deactivate. A value 0 to 7. Default is 0. | 
| Fade out |  Enter the time in milliseconds for the image to fade out. Default is 0 (no fade-out).  | 

# Fields for activating a per-outputs image overlay
Activate per-outputs image overlay

This table shows the fields that apply for an action to activate an image overlay. 


| Field | Description | 
| --- | --- | 
| Action type | Static Image Output Activate. | 
| Action name | A name for this activation action. For example, the layer and the name of the image to overlay.  | 
| Start type  | Fixed or Immediate. | 
| Date and time |  The date and time (in UTC format) that the channel must activate the image overlay. The time should be at least 60 seconds later than the time that you submit the action.  Note that the time is the wall clock time, not the timecode in the input.  | 
| Input location | Enter the locations (URLs) on the server where the image file is stored.Also complete **Credentials**, if the server requires that you provide user credentials. | 
| Other fields | Complete these fields to control the layer, position, look (such as fade-in), and other behavior of the image.  | 

# Fields for deactivating a per-outputs image overlay
Deactivate per-outputs image overlay

This table shows the fields that apply for an action to deactivate the image. The deactivate action operates on one per-output layer that you specify and on the outputs that you specify. It doesn't operate on a specific image. 

To understand how this statement is significant, consider this example. You might specify layer 4 and outputs A and C. Layer 4 in output A contains the image overlay X, output B contains image overlay X, and output C contains image X. MediaLive removes X from output A, and removes Y from output C. Image X in output B will remain active.


| Field | Description | 
| --- | --- | 
| Action type | Static Image Output Deactivate.  | 
| Action name | A name for this deactivation action. For example, the name of the image. Or a name that ties back to the activation action plus the term "deactivate." | 
| Start type  | Fixed or Immediate. | 
| Date and time |  If the **Start type** is **Fixed**, specify the date and time (in UTC format) that the channel must deactivate the image overlay. The time should be at least 60 seconds later than the time that you submit the action.  Note that the time is the wall clock time, not the timecode in the input.  | 
| Outputs | Select the output or outputs where you want to deactivate a specific layer. | 
| Layer | Identify the layer that you want to deactivate. Enter a value 0 to 7. Default is 0. | 
| Fade out |  Enter the time in milliseconds for the image to fade out. Default is 0 (no fade-out).  | 

# Fields for activating a motion graphics overlay
Activate motion graphics overlay

This table shows the fields that apply for an action to activate a motion graphics overlay. 


| Field | Description | 
| --- | --- | 
| Action type | Motion Graphics Activate. | 
| Action name | A name for this activation action. For example, the name of the motion graphic asset.  | 
| Start type  | Fixed or Immediate. | 
| Date and time |  The date and time (in UTC format) that the channel must activate the motion graphics overlay. The time should be at least 60 seconds later than the time that you submit the action.  Note that the time is the wall clock time, not the timecode in the input.  | 
| Duration | Optional. The duration in milliseconds for the motion graphic to remain on the video. If you omit this field or set it to 0, the duration is unlimited and the motion graphic will remain until you create a deactivate action. | 
| URL | The URL of the motion graphics asset. This asset is always an HTML file. The URL follows this syntax:`<protocol>://<path>/<file>.html`For example:`https://example.com/ticker_tape.html` | 
| Credentials |  Complete this section only if the server where the motion graphics asset is stored requires user authentication from MediaLive. Enter the user name provided by the owner of the server. For the password, enter the name of the password stored on the AWS Systems Manager Parameter Store. Don't enter the password itself. For more information, see [Requirements for AWS Systems Manager password parameters](requirements-for-EC2.md).  | 

# Fields for deactivating a motion graphics overlay
Deactivate motion graphics overlay

This table shows the fields that apply for an action to deactivate an motion graphics overlay. 


| Field | Description | 
| --- | --- | 
| Action type | Motion Graphics Deactivate.  | 
| Action name | A name for this deactivation action. For example, deactivate\$1motion\$1graphic. | 
| Start type  | Fixed or Immediate. | 
| Date and time |  If the **Start type** is **Fixed**, specify the date and time (in UTC format) that the channel must deactivate the motion graphics overlay. The time should be at least 60 seconds later than the time that you submit the action.  Note that the time is the wall clock time, not the timecode in the input.  | 

# Fields for a splice\$1insert message
Splice\$1insert

This table shows the fields that apply for an action to insert a splice\$1insert SCTE 35 message. 


| Field | Description | 
| --- | --- | 
| Action type | SCTE 35 Splice Insert. | 
| Action name | A name for this splice\$1insert action. For example, splice\$1insert actions could be numbered sequentially, restarting every day or every month.  | 
| Start type  | Fixed or Follow or Immediate.  | 
| Date and time |  If the **Start type** is **Fixed**, specify the UTC start time for the splice\$1insert action. The time should be at least 15 seconds in the future. Note that the time is the wall clock time, not the timecode in the input.  | 
| Reference action name |  If the **Start type** is **Follow**, choose the input to follow. The dropdown list shows all existing input switches that are file inputs. Remember that a SCTE 35 action can follow input A only if input A is a file input and the source end behavior for input A is *continue*. For information about these switching rules, see [Fixed, immediate, and follow switches](ips-switch-types.md).  | 
| Follow point | If the Start type is Follow, complete this field. The follow point is always End, to indicate that the switch will occur when the input in Reference action name has finished. | 
| Splice event id | The ID for the splice event. Enter an ID for the splice event that is unique among all scheduled and active splice\$1insert messages in this channel. A message is active if the schedule action is in process in the channel and has not completed.  | 
| Duration | The duration for the splice event. Complete in one of these ways:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/medialive/latest/ug/schedule-fields-for-splice_insert.html) | 

The splice\$1insert inserted in the transport stream will have the following:

```
      segmentation_event_cancel_indicator = 0 
      out_of_network = 1
      duration_flag = 1
      duration = the specified time
```

Or

```
      segmentation_event_cancel_indicator = 0
      out_of_network = 1
      duration_flag = 0
```

# Fields for a time\$1signal message
Time\$1signal

This table shows the fields that apply for an action to insert a time\$1signal SCTE 35 message.


| Field | Description | 
| --- | --- | 
| Action type | SCTE 35 Time Signal. | 
| Action name | A name for this time\$1signal action. For example, you might name time\$1signal actions with a sequential number, restarting every day or every month. | 
| Start type  | Fixed or Follow or Immediate. | 
| Date and time |  If the **Start type** is **Fixed**, specify the UTC start time for the time\$1signal. The time should be at least 15 seconds in the future. Note that the time is the wall clock time, not the timecode in the input.  | 
| Reference action name |  If the **Start type** is **Follow**, choose the input to follow. The dropdown list shows all existing input switches that are file inputs. Remember that a SCTE 35 action can follow input A only if input A is a file input and the source end behavior for input A is *continue*. For information about these switching rules, see [Fixed, immediate, and follow switches](ips-switch-types.md).  | 
| Follow point | If the Start type is Follow, complete this field. The follow point is always End, to indicate that the switch will occur when the input in Reference action name has finished. | 
| Add Scte35 descriptors | Choose this button and complete the fields that appear. The descriptors are a standard component of a time\$1signal message. | 

# Fields for a return-to-network message
Return-to-network

This table shows the fields that apply for an action to insert a return-to-network SCTE 35 message.


| Field | Description | 
| --- | --- | 
| Action type | SCTE 35 Return to Network. | 
| Action name | A name for this return-to-network action. For example, splice0003\$1 return\$1early. | 
|  Start type  | Fixed or Follow or Immediate. | 
| Date and time |  If the **Start type** is **Fixed**, specify the UTC start time for the return. The time should be at least 15 seconds in the future. Note that the time is the wall clock time, not the timecode in the input.  | 
| Reference action name |  If the **Start type** is **Follow**, choose the input to follow. The dropdown list shows all existing input switches that are file inputs. Remember that a SCTE 35 action can follow input A only if input A is a file input and the source end behavior for input A is *continue*. For information about these switching rules, see [Fixed, immediate, and follow switches](ips-switch-types.md).  | 
| Follow point | If the Start type is Follow, complete this field. The follow point is always End, to indicate that the switch will occur when the input in Reference action name has finished. | 
| Splice event id | The ID of the splice\$1insert that the return-to-network should end. You assigned this ID when you created the splice\$1insert. | 

# Fields for ID3 metadata
ID3 metadata

This table shows the fields that apply for an action to perform a one-time insertion of ID3 metadata. MediaLive inserts the metadata as base64.


| Field | Description | 
| --- | --- | 
| Action type | HLS Timed Metadata. Choose this option to insert in HLS or MediaPackage outputs.**Timed Metadata**. Choose this option to insert in CMAF Ingest outputs. | 
| Action name | A name for the metadata item. You might want to design a convention for naming ID3 metadata items, such as id3\$1metadata-<UTC time>. | 
|  Start type  | Fixed or Immediate. | 
| Date and time |  If the **Start type** is **Fixed**, specify the UTC start time for the ID3 metadata item. The time should be at least 15 seconds in the future. Note that the time is the wall clock time, not the timecode in the input.  | 
| ID3 |  Enter the ID3 metadata encoded as base64. The metadata must be fully formed ID3 metadata (including both a header and a frame, as per the ID3 2.4.0 specification).  The content of the `value` property can include MediaLive [variable data](variable-data-identifiers.md). MediaLive will examine the contents of the base64 and perform substitutions. For example, MediaLive will change **\$1dt\$1** to the date and time.  | 

# Fields for ID3 segment tags
ID3 segment tags

This table shows the fields that apply for an action to insert ID3 metadata in every segment. There are two options for inserting the metadata:
+ The **tag** option, to insert metadata as plain text.
+ The **ID3** option, to insert metadata as base64.

For details about the types of output groups that support each option, see the table in [Different mechanisms for including metadata](id3-enable-result.md).


| Field | Description | 
| --- | --- | 
| Action type | HLS ID3 Segment Tagging. Choose this option to insert in HLS or MediaPackage outputs.**ID3 Segment Tagging**. Choose this option to insert in CMAF Ingest outputs. | 
| Action name | A name for the segment tag.  | 
|  Start type  | Fixed or Immediate. | 
| Date and time |  If the **Start type** is **Fixed**, specify the UTC start time for the ID3 segment tag. The time should be at least 15 seconds in the future. Note that the time is the wall clock time, not the timecode in the input.  | 
| Tag | Complete this field if the content of the tag is free text. Enter the value for a TXXX field inside the ID3 tag. MediaLive creates an ID3 tag with a single TXXX field and inserts the tag in every segmenThe content can include MediaLive [variable data](variable-data-identifiers.md). In the following example, the content consists of the date and time, and the current segment number. The tag contents will be different in each segment.**\$1dt\$1-\$1sn\$1** | 
| ID3 | Complete this field if the content of the tag is ID3 metadata. Enter the content encoded as base64. The metadata must be fully formed ID3 metadata (including both a header and a frame, as per the ID3 specification).  | 

# Fields for pause
Pause

In **Schedule action settings**, complete the following fields.


| Field | Description | 
| --- | --- | 
| Action type | Pause. | 
| Action name | A name for the action.  | 
|  Start type  | Fixed or Immediate. | 
| Date and time |  If the **Start type** is **Fixed**, specify the UTC start time for the action. The time should be at least 15 seconds in the future. Note that the time is the wall clock time, not the timecode in the input.  | 
| Actions | Choose Add actions, then for Pipeline id, choose the pipeline that you want to pause: PIPELINE\$10 or PIPELINE\$11.  | 

When you choose **Create**, MediaLive adds an action to the schedule to pause the specified pipeline and to unpause any pipeline that isn't specified. As a result, only the specified pipeline will be paused after the action is performed.

# Fields for unpause
Unpause

In **Schedule action settings**, complete the following fields.


| Field | Description | 
| --- | --- | 
| Action type | Pause. | 
| Action name | A name for the action.  | 
|  Start type  | Fixed or Immediate. | 
| Date and time |  If the **Start type** is **Fixed**, specify the UTC start time for the action. The time should be at least 15 seconds in the future. Note that the time is the wall clock time, not the timecode in the input.  | 
| Actions | Keep this section empty. Don't add any actions.  | 

When you choose **Create**, the empty **Actions** section instructs MediaLive to add an action to the schedule to unpause all pipelines.

# Deleting actions from the schedule (console)
Deleting actions

These rule apply when you add delete actions to the schedule:
+ In a single-input channel (a channel that doesn't involve input switching), you can delete actions as follows: 
  + You can delete an action with a start time that is more than 15 seconds in the future. The channel won't perform the action.
  + You can delete an action that has already been performed. Deleting this action doesn't reverse the action, it only removes it from the schedule.
+ In a multiple-input channel, you can delete actions as follows:
  + You can delete an action with a start time that is more than 15 seconds in the future. The channel won't perform the action.

    There are some constraints that apply to deleting inputs switches and input prepare, event when they are in the future. For more information, see [Deleting actions from the schedule](ips-manage-schedule.md) and [Deleting and stopping input prepare actions in the MediaLive schedule](input-prep-delete.md).
  + You can delete an action that has already been performed. Deleting this action doesn't reverse the action, it only removes it from the schedule.

    There are some constraints that apply to deleting inputs switches and input prepare, event when they are in the future. For more information, see [Deleting actions from the schedule](ips-manage-schedule.md) and [Deleting and stopping input prepare actions in the MediaLive schedule](input-prep-delete.md).

**Deleting versus reversing**

It is important to understand that deleting a stale action from the schedule doesn't reverse its effect in the channel. For example, if you have paused the channel, and the channel has performed the action, you unpause the channel by entering a new action. You don't unpause it by deleting the action.

**Note**  
If the channel has already received the action, you might be able to modify it to effectively delete it. For more information, see [Modifying actions in the schedule (console)](schedule-modify.md).

You can delete any number of actions in one request, or any combination of types of actions in one request. For example, you can mix the deletion of SCTE 35 message actions and image overlay actions.

The general procedure is the same to delete any type of action.

**To delete actions in list view**

1. Open the MediaLive console at [https://console.aws.amazon.com/medialive/](https://console.aws.amazon.com/medialive/).

1. In the navigation pane, choose **Channel**, and then choose the channel that you want to work with.

1. On the **Details** pane, choose the **Schedule** tab.

1. If necessary, choose the **Switch** button to display the **List** view. For information about the layout and color coding of the timeline view, see [Viewing the schedule (console)](schedule-using-console-view.md).

1. Choose one or more actions to delete.

   If you choose an input switch that is in an input follow chain, a prompt appears. This prompt notifies you that all the follow input switch actions and the follow SCTE 35 actions up to the next fixed input switch will also be deleted. You can cancel or continue. 

   Choose **Actions**, and then choose **Delete**.

**To delete actions in timeline view (console)**

1. Open the MediaLive console at [https://console.aws.amazon.com/medialive/](https://console.aws.amazon.com/medialive/).

1. In the navigation pane, choose **Channel**, and then choose the channel that you want to work with.

1. On the **Details** pane, choose the **Schedule** tab.

1. If necessary, choose the **Switch** button to display the **Timeline** view. For information about the layout and color coding of the timeline view, see [Viewing the schedule (console)](schedule-using-console-view.md).

1. In each action section, choose the **X** to delete the action.

   If you choose an input switch that is in an input follow chain, a prompt appears to notify you that the follow actions below this action (up to the next fixed input switch) will also be deleted. You can cancel or continue. 

# Modifying actions in the schedule (console)
Modifying actions

You can't modify an action in the schedule, even if it hasn't been received by the channel. However, you can sometimes achieve a modify effect using a create action, a delete action, or both.

**Topics**
+ [

## General rule about modifying actions
](#modify-action-not-started)
+ [

## Modifying an input switch action
](#schedule-modify-ips)
+ [

## Modifying an input switch action in a follow chain
](#schedule-modify-ips-follow)
+ [

## Inserting an input switch action into a follow chain
](#schedule-insert-follow)
+ [

## Modifying an input prepare action
](#schedule-modify-prep)
+ [

## Modifying an image overlay that is in progress
](#schedule-modify-image-overlay)
+ [

## Modifying a motion graphics overlay that is in progress
](#schedule-modify-mg)

## General rule about modifying actions


You can't modify an action in the schedule, even if it hasn't been received by the channel. 

To change an action that hasn't yet started, delete the action and create it again. See the following sections for important tips on deleting and recreating.

## Modifying an input switch action


You can't modify input switches in the schedule. But you can achieve the same result by deleting the action and creating it again. 

Keep in mind that you can't delete or create an action that has a start time less than 15 seconds in the future. Give yourself enough time to delete and recreate the action before this deadline.

## Modifying an input switch action in a follow chain


When you delete an action in an *input follow chain* (in order to delete and recreate it), you must also delete and recreate the input switch follow actions and SCTE 35 follow actions below this one. You must do this because each action refers to the previous action. If you delete the previous action, the next action becomes an orphan. Orphan actions aren't permitted. 

**Example 1: Modify an action**  
For example, assume this is the input follow chain:

```
Input A              Fixed    File
           Input B   Follow   File
           Input C   Follow   File
           Input D   Follow   File or Live
Input E              Fixed    File or Live
```

To delete and modify input A, you must also delete inputs B, C, and D. You must delete input B to prevent it becoming an orphan. The same rule applies until the next fixed input (input E), which isn't chained to another input. Therefore, you aren't required to delete input E.

When you delete input A using the console, a prompt appears to notify you that the follow actions below this action (up to input E, which is the next fixed input switch) will also be deleted. You can cancel or continue. You must then recreate inputs A to D. Recreate them in order going down the chain: input A, input B, input C, input D.

**Example 2: Delete an action**  
This example shows how to delete input B: 

```
Input A              Fixed    File
           Input B   Follow   File
           Input C   Follow   File
           Input D   Follow   File or Live
Input E              Fixed    File or Live
```

When you delete input B using the console, a prompt appears to notify you that the follow actions below this action (up to input E, which is the next fixed input switch) will also be deleted. You can cancel or continue. You must then recreate inputs C and D. Recreate them in order going down the chain: input C, input D. Remember to set up input C to follow input A instead of input B. 

## Inserting an input switch action into a follow chain


To insert a follow switch action into an *input follow chain* (between two existing follow switch actions), you must delete and recreate the follow actions below the insertion. You do that to prevent two actions from following one previous action. Branching is not allowed in the chain. 

For example, suppose that you want to insert input X between input B and input C. Input C already refers to input B. You also want input X to refer to input B, but that is not allowed. Therefore, you must delete input C and the inputs that follow. You then recreate the chain in the following order: input X (refers to input B), input C (refers to input X), input D (refers to input C).

## Modifying an input prepare action


You can't modify input switches in the schedule. But you can achieve the same result by deleting the action and creating it again. 

Keep in mind that you can't delete or create an action that has a start time less than 15 seconds in the future. Give yourself enough time to delete and recreate the action before this deadline.

### Modifying a SCTE 35 message that is in progress


You can't modify a SCTE 35 message that is active in the channel. Specifically, you can't shorten the duration of a splice\$1insert. But you can achieve the same result by creating a return-to-network action. 

### Modifying or deleting an ID3 segment tag that is in progress


You can't modify the contents of an ID3 segment tag that is active in the channel. Instead, create a new action to override the active tag. The new action can contain a tag with new content, or it can contain an empty tag:
+ If the new action contains a tag with content, the channel starts inserting the contents of the new action into every segment.
+ If the new action contains an empty tag, the channel stops inserting segment tags, which means you have effectively deleted the tag.

## Modifying an image overlay that is in progress


You can't directly modify an image overlay (either global or per-outputs) that is running in the channel. But you can achieve the same result by creating a new action with the same layer specified. You can do the following:
+ Shorten or extend the duration of an image overlay.
+ Change one or more attributes.
+ Specify an attribute that isn't currently specified in an image overlay. For example, you might want to specify a fadeout where there is no fadeout in the current overlay. 
+ Create a new action (with a new action name) that inserts an image overlay 15 seconds in the future. Make sure to specify the following:
  + The same layer as the image that you want to modify.
  + A duration that is appropriate (the image doesn't inherit the duration of the current image). 
  + All the attributes that you want. 

  The new action replaces the current action because you specified the same layer. 

## Modifying a motion graphics overlay that is in progress


You can't modify a motion graphic overlay that is running in the channel. But you can achieve the same result in other ways. For example, the authoring system (that produces the motion graphic asset) can modify the content that is being published to the URL associated with the action. For information about preparing and publishing the motion graphics asset, see [Step 1: Prepare the motion graphic asset](mgi-prepare-asset.md).

# Viewing the schedule (console)
Viewing the schedule

You can display the list of actions currently in the schedule and view them in list or timeline view.

**To view actions (console)**

1. Open the MediaLive console at [https://console.aws.amazon.com/medialive/](https://console.aws.amazon.com/medialive/).

1. In the navigation pane, choose **Channel**, and then choose the channel that you want to work with.

1. On the **Details** pane, choose the **Schedule** tab.

   The **Schedule actions** pane shows the actions in the schedule's current window of time. 

   You can switch between the two views of the schedule by choosing the **Switch** button. 

**List view**  
The actions are mostly listed in chronological order.

Input switches in an input follow chain are grouped together starting from the top of the chain (which is the action above the first follow action) to the last follow action. Other actions, such as actions for SCTE 35 and image overlay, might occur between two follow actions. MediaLive can't predict whether a SCTE 35 or image overlay action will occur between two follow actions and doesn't attempt to show it in the list view. 

**Timeline view**  
The actions are arranged in cards along a vertical axis. The card titles are color-coded by the action type. For example, SCTE 35 time\$1signal messages are yellow.

One card might contain several input switches. The first input switch is always a fixed-type input switch. The remaining input switches in that card are always follow-type input switches.