Log Creation - Revision history

DKlann: Update links to the Rivendell Operations and Administration Guide

2024-04-14T02:08:19Z

Update links to the Rivendell Operations and Administration Guide

DKlann: wordsmithing, typography, add some links.

2022-07-05T15:25:48Z

wordsmithing, typography, add some links.

Show changes

DKlann: promote voice track "aside" to a full, unparenthesized paragraph, add link to O&A Guide, image formatting cleanup

2020-08-03T20:02:28Z

promote voice track "aside" to a full, unparenthesized paragraph, add link to O&A Guide, image formatting cleanup

DKlann: remaining " to ldquo and rdquo

2020-08-03T02:33:52Z

remaining " to ldquo and rdquo

DKlann: /* Tutorial */ minor language and grammar tweaks

2020-08-03T02:31:37Z

‎Tutorial: minor language and grammar tweaks

Show changes

DKlann: minor tweaks to the Overview

2020-08-03T02:11:21Z

minor tweaks to the Overview

DKlann: correct the text and link to the opsguide wildcard discussion.

2020-07-28T17:00:09Z

correct the text and link to the opsguide wildcard discussion.

DKlann: change heading levels under Tutorial.

2020-07-27T15:51:11Z

change heading levels under Tutorial.

DKlann: major update with lots of wordsmithing and links, including Rivendell version 3.4.1 screenshots.

2020-07-27T15:49:47Z

major update with lots of wordsmithing and links, including Rivendell version 3.4.1 screenshots.

Show changes

DKlann: Add info about the mystical Voice Track Event

2018-09-17T19:47:25Z

Add info about the mystical Voice Track Event

@@ Line 17: / Line 17: @@
 == Tutorial ==
-This tutorial guides you through creating your first '''Log'''. It does not cover all the options that you might encounter along the way; see the [http://opsguide.rivendellaudio.org/html/chapter.rdlogmanager.html Rivendell Operations and Administration Guide] for all the details. The tutorial assumes that you have songs, stations IDs, and liners/jingles in your audio library, and are a 24/7 music station. It also includes brief tips and directions for those using external schedulers.
+This tutorial guides you through creating your first '''Log'''. It does not cover all the options that you might encounter along the way; see the [https://opsguide.rivendellaudio.org/html/chapter.rdlogmanager.html Rivendell Operations and Administration Guide] for all the details. The tutorial assumes that you have songs, stations IDs, and liners/jingles in your audio library, and are a 24/7 music station. It also includes brief tips and directions for those using external schedulers.
 If you have not already configured the '''Log''' creation parameters in [[RDAdmin]], please do so now:
@@ Line 29: / Line 29: @@
 :* click &ldquo;OK&rdquo; to save the settings
-See ''[http://opsguide.rivendellaudio.org/html/appendix.filepath_wildcards.html Appendix D. Filepath Wildcards]'' in the [http://opsguide.rivendellaudio.org/html/ Rivendell Operations and Administration Guide] for all the available &ldquo;wildcards&rdquo; you can use in the ''Log Description Template'' and the ''Log Name Template''.
+See ''[https://opsguide.rivendellaudio.org/html/appendix.filepath_wildcards.html Appendix D. Filepath Wildcards]'' in the [https://opsguide.rivendellaudio.org/html/ Rivendell Operations and Administration Guide] for all the available &ldquo;wildcards&rdquo; you can use in the ''Log Description Template'' and the ''Log Name Template''.
 [[Image:Edit-service-3.4.1.png|center|443px|thumb|border|Service settings for Log generation]]
@@ Line 58: / Line 58: @@
 NOTE: If you are using an external Music Scheduler, your &ldquo;Music&rdquo; event will instead be set to '''IMPORT''' ... '''From Music'''.
-This is where you place Voice Track markers in your '''Events''' for later processing with [[RDLogManager]] and then [[RDLogEdit]]. While editing an '''Event''' you need to right-click in either the PRE-IMPORT CARTS or the POST-IMPORT CARTS boxes and choose &ldquo;Insert Voice Track&rdquo;. See figure. It is common practice to have an '''Event''' that contains only a &ldquo;Voice Track Placeholder&rdquo; in the &ldquo;PRE-IMPORT CARTS&rdquo; section; you can then use this '''Event''' in many positions in many different Clocks. See ''[http://opsguide.rivendellaudio.org/html/chapter.voicetracking.html Chapter 9. VoiceTracking]'' in the Rivendell Operations and Administration Guide for more details about voice tracking with Rivendell.
+This is where you place Voice Track markers in your '''Events''' for later processing with [[RDLogManager]] and then [[RDLogEdit]]. While editing an '''Event''' you need to right-click in either the PRE-IMPORT CARTS or the POST-IMPORT CARTS boxes and choose &ldquo;Insert Voice Track&rdquo;. See figure. It is common practice to have an '''Event''' that contains only a &ldquo;Voice Track Placeholder&rdquo; in the &ldquo;PRE-IMPORT CARTS&rdquo; section; you can then use this '''Event''' in many positions in many different Clocks. See ''[https://opsguide.rivendellaudio.org/html/chapter.voicetracking.html Chapter 9. VoiceTracking]'' in the Rivendell Operations and Administration Guide for more details about voice tracking with Rivendell.
 [[File:Editing Event - 00 Voice Track (on ram) 001.png|center|824px|thumb|border|Right-click to add VoiceTrack placeholder]]

@@ Line 7: / Line 7: @@
 '''[[Events]]''' - Events are items (lines) in a [[Log]]. An Event could be a song that is picked using criteria you specify, a specific Cart number, one or more macros, etc. An Event can also be a place holder for, notes, voice-tracks, and for importing a &ldquo;track&rdquo; from an external, third-party music or traffic scheduling application.
-'''[[Clocks]]''' - Clocks represent one hour of '''Events''' in your broadcast. You can have as many or as few Clocks as you need. If you have broadcast hours where the format is exactly the same you can use the same clock for all those hours. You fill clocks with '''Events'''.
+'''[[Clocks]]''' - Clocks represent one hour of '''Events''' in your broadcast. You can have as many or as few Clocks as you need. If you have broadcast hours where the format is exactly the same you can use the same Clock for all those hours. You fill Clocks with '''Events'''.
 After you have Clocks with Events in them, you tell Rivendell which Clock to use in each of the 168 hours in a week. You do this by setting the Clocks in the '''[[Grid]]'''. A Grid represents one week of a '''Service''''s broadcast time. In other words, you  &ldquo;fill the grid with '''Clocks'''&rdquo;.
@@ Line 24: / Line 24: @@
 :* in the ''Log Description Template'' box, type the Service name followed by a descriptive title &ldquo;template&rdquo; for all Logs, for example '''Production log for %$A, %Y-%m-%d''' (this results in Log descriptions like ''Tuesday, 2020-03-01'')
 :* in the ''Log Name Template'' blank, enter '''%Y%m%d''' (this results in logs named for the four-digit year, two digit month, and two-digit day of the month)
-:* check the &ldquo;Insert CHAIN TO at log end&rdquo; box; this tells Rivendell to insert a command at the end of each log instructing RDAirPlay to automatically load and continue playing &ldquo;tomorrow's&rdquo; Log at the end of each broadcast day
+:* check the &ldquo;'''Insert CHAIN TO at log end'''&rdquo; box; this tells Rivendell to insert a command at the end of each log instructing RDAirPlay to automatically load and continue playing &ldquo;tomorrow&rsquo;s&rdquo; Log at the end of each broadcast day
 :* save settings and close RDAdmin
-See ''Appendix D. Filepath Wildcards'' in the [http://opsguide.rivendellaudio.org/html/appendix.filepath_wildcards.html Rivendell Operations and Administration Guide] for all the available &ldquo;wildcards&rdquo; you can use in the ''Log Description Template'' and the ''Log Name Template''.
+See ''[http://opsguide.rivendellaudio.org/html/appendix.filepath_wildcards.html Appendix D. Filepath Wildcards]'' in the [http://opsguide.rivendellaudio.org/html/ Rivendell Operations and Administration Guide] for all the available &ldquo;wildcards&rdquo; you can use in the ''Log Description Template'' and the ''Log Name Template''.
-[[Image:Edit-service-3.4.1.png|center]]
+[[Image:Edit-service-3.4.1.png|center|443px|thumb|border|Service settings for Log generation]]
 Log creation occurs within RDLogManager so start RDLogManager to begin this tutorial.
@@ Line 39: / Line 39: @@
 Lets create a station ID event. Click &ldquo;Edit Events&rdquo; then &ldquo;Add&rdquo; and type in &ldquo;ID&rdquo; or whatever you like. Locate the ''IMPORT'' section of the screen and click the radio button next to ''Select from''. In the dropdown (circled in red), select the Group that contains your legal station identification announcements. You probably want your ID to start close to the time you schedule it so check &ldquo;Use hard start time&rdquo; and &ldquo;Make Next&rdquo; (also circled in red). Transition should be &ldquo;PLAY&rdquo; or &ldquo;SEGUE&rdquo; Lastly, choose a unique Color via the bottom button and click &ldquo;OK&rdquo; to save.
-[[Image:Event-toh-3.41..png]]
+[[Image:Event-toh-3.41..png|center|617px|thumb|border|Event settings for an example top of hour legal ID]]
 Follow the same first steps to create a Liner event, but let's choose a specific Liner Cart to play every time this Event is scheduled. Rather than Importing from the Liner group, click and hold a Liner Cart on the left and drag it into the &ldquo;PRE-IMPORT CARTS&rdquo; box as shown in the image.
-[[Image:Liner-event.gif|center]]
+[[Image:Liner-event.gif|center|1023px|thumb|border|Cart drag-n-drop to Event Pre-Import box]]
 Finally, we need to create an event to schedule a song. Again, create a new event. On the &ldquo;Import&rdquo; line
@@ Line 52: / Line 52: @@
 :* change First Cart transition to &ldquo;'''Segue'''&rdquo;
-[[Image:Music-event.png|center]]
+[[Image:Music-event.png|center|624px|thumb|border|Example Music Event]]
-NOTE: If you are using an external Music Scheduler, your &ldquo;Music&rdquo; event will instead be set to import '''From Music'''.
+NOTE: If you are using an external Music Scheduler, your &ldquo;Music&rdquo; event will instead be set to '''IMPORT''' ... '''From Music'''.
-(As an aside, this is where you place Voice Track markers in your events for later processing with [[RDLogManager]] and then [[RDLogEdit]]. While editing an event you need to right-click in either the PRE-IMPORT CARTS or the POST-IMPORT CARTS boxes and choose &ldquo;Insert Voice Track&rdquo;. See figure.)
+This is where you place Voice Track markers in your events for later processing with [[RDLogManager]] and then [[RDLogEdit]]. While editing an event you need to right-click in either the PRE-IMPORT CARTS or the POST-IMPORT CARTS boxes and choose &ldquo;Insert Voice Track&rdquo;. See figure. It is common practice to have an Event that contains only a &ldquo;Voice Track Placeholder&rdquo; in the &ldquo;PRE-IMPORT CARTS&rdquo; section; you can then use this Event in many positions in many different Clocks. See ''[http://opsguide.rivendellaudio.org/html/chapter.voicetracking.html Chapter 9. VoiceTracking]'' in the Rivendell Operations and Administration Guide for more details about voice tracking with Rivendell.
-[[File:Editing Event - 00 Voice Track (on ram) 001.png|thumb|600px|left]]
+[[File:Editing Event - 00 Voice Track (on ram) 001.png|center|824px|thumb|border|Right-click to add VoiceTrack placeholder]]
 <div style="clear: both"></div>
@@ Line 64: / Line 64: @@
 === Clocks ===
-A clock is a series of &ldquo;Events&rdquo; that occur during an hour. You will need to create one clock for each ''unique'' hour. For example, if you are a music station and play music 24/7 with each hour being EXACTLY the same then you will only need one clock. If you play different styles of music during certain hours (and don't use an external music scheduler), you need a separate clock for those hours. If you air programs, you will probably need a separate clock for each hour.
+A Rivendell Clock contains a series of &ldquo;Events&rdquo; that occur during an hour. You will need to create one Clock for each ''unique'' hour. For example, if you are a music station and play music 24/7 with each hour being EXACTLY the same then you will only need one Clock. If you play different styles of music during certain hours (and don't use an external music scheduler), you need a separate Clock for those hours. If you air programs, you will probably need a separate Clock for each hour.
-We will create just one clock to keep things simple but you will be able to easily create additional clocks to meet your needs.
+We will create just one Clock to keep things simple but you will be able to easily create additional Clocks to meet your needs.
-First, click &ldquo;Edit Clocks&rdquo; from the RDLogManager opening screen and then &ldquo;Add&rdquo; and name your new clock something like &ldquo;Music&rdquo;. You will now see a blank clock. Each clock must have a unique 3 alpha-numeric code so type in something like &ldquo;MU1&rdquo; (i.e. Music 1) in the &ldquo;Code&rdquo; field near the top. Note that the codes are case-sensitive, so you can have lots of them.
+First, click &ldquo;Edit Clocks&rdquo; from the RDLogManager opening screen and then &ldquo;Add&rdquo; and name your new Clock something like &ldquo;Music&rdquo;. You will now see a blank Clock. Each Clock must have a unique 3 alpha-numeric code so type in something like &ldquo;MU1&rdquo; (i.e. Music 1) in the &ldquo;Code&rdquo; field near the top. Note that the codes are case-sensitive, so you can have lots of them.
-Click the &ldquo;Add&rdquo; button to start adding &ldquo;Events&rdquo; which you created during the previous step. Click &ldquo;Select&rdquo;, choose your &ldquo;ID&rdquo; event, and click &ldquo;OK&rdquo;. Start time should be 00:00 (MM:SS) and end time should be the ''approximate length'' of your ID cart. My stop time is 00:10 for a ten second ID. Click OK to finish adding the Event. You should now see the thin sliver of your ID in the clock on the right and in the list on the left. Notice the color is the one you chose when creating the event.
+Click the &ldquo;Add&rdquo; button to start adding &ldquo;Events&rdquo; which you created during the previous step. Click &ldquo;Select&rdquo;, choose your &ldquo;ID&rdquo; event, and click &ldquo;OK&rdquo;. Start time should be 00:00 (MM:SS) and end time should be the ''approximate length'' of your ID cart. My stop time is 00:10 for a ten second ID. Click OK to finish adding the Event. You should now see the thin sliver of your ID in the Clock on the right and in the list on the left. Notice the color is the one you chose when creating the event.
-Now we want to schedule some songs. We'll have 3 songs then a liner and continue that pattern until we fill the entire clock (hour). To add a song, we:
+Now we want to schedule some songs. We'll have 3 songs then a liner and continue that pattern until we fill the entire Clock (hour). To add a song, we:
 :* click &ldquo;Add&rdquo;
@@ Line 86: / Line 86: @@
 We've completed our 3 songs and it's time for a &ldquo;Liner&rdquo; event. Add the &ldquo;Liner&rdquo; event with a start time of 09:00 and a stop time of 09:10 (for a ten second liner). The next &ldquo;Music&rdquo; event well be from 09:10 to 12:00.
-Continue repeating those steps until the clock (hour) is filled from 00:00 to 59:59.
+Continue repeating those steps until the Clock (hour) is filled from 00:00 to 59:59.
-Use the &ldquo;Color&rdquo; button to assign a unique color to your &ldquo;Music&rdquo; clock. You can also click the &ldquo;Scheduler Rules&rdquo; button and adjust Music Scheduler rules (like avoiding playing two heavy metal songs back-to-back). Finally, touch &ldquo;OK&rdquo; to save your new clock.
+Use the &ldquo;Color&rdquo; button to assign a unique color to your &ldquo;Music&rdquo; Clock. You can also click the &ldquo;Scheduler Rules&rdquo; button and adjust Music Scheduler rules (like avoiding playing two heavy metal songs back-to-back). Finally, touch &ldquo;OK&rdquo; to save your new Clock.
-[[Image:Clock-3.4.1.png|center]]
+[[Image:Clock-3.4.1.png|center|1030px|thumb|border|Edit Clock showing a completed Clock]]
 Congratulations! You are almost done.
-NOTE: If you are using an external Music Scheduler, your &ldquo;Music&rdquo; event will span the entire sweep (i.e. 00:10 to 09:00) so that all songs in your music log appearing during that time frame will be imported. You will have to adjust the time frame so the clocks in Rivendell mesh with those in your Music Scheduler.
+NOTE: If you are using an external Music Scheduler, your &ldquo;Music&rdquo; event will span the entire sweep (i.e. 00:10 to 09:00) so that all songs in your music log appearing during that time frame will be imported. You will have to adjust the time frame so the Clocks in Rivendell mesh with those in your Music Scheduler.
 === Grids ===
-Click '''Edit Grids''' from the RDLogManager main window and then choose your service (there may only be one). You will see buttons representing each hour of every day (yes, 168 of them). The &ldquo;Grids&rdquo; allow you to choose which &ldquo;Clock&rdquo; is used for every hour of the week. In our case, we will set each hour to use our &ldquo;Music&rdquo; clock we created in the previous step.
+Click '''Edit Grids''' from the RDLogManager main window and then choose your service (there may only be one). You will see buttons representing each hour of every day (yes, 168 of them). The &ldquo;Grids&rdquo; allow you to choose which &ldquo;Clock&rdquo; is used for every hour of the week. In our case, we will set each hour to use our &ldquo;Music&rdquo; Clock we created in the previous step.
-[[Image:Grid-3.4.1.png|center]]
+[[Image:Grid-3.4.1.png|center|1027px|thumb|border|A completed Grid]]
 Note: this screenshot shows a few different Clocks, yours will show the same Clock in all hours.
-This step is simple. Click or touch the '''Change All''' button. Select your Music Clock and click '''OK''', then click '''Yes''' to confirm that you want to set all 168 hours to use the same clock. Click '''Close''' when done setting all the Clocks in the Grid.
+This step is simple. Click or touch the '''Change All''' button. Select your Music Clock and click '''OK''', then click '''Yes''' to confirm that you want to set all 168 hours to use the same Clock. Click '''Close''' when done setting all the Clocks in the Grid.
 === Generating Logs ===

@@ Line 5: / Line 5: @@
 You need to do some setup in [[RDAdmin]] for the '''Service''' you will be using. Then it is a matter of creating:
-'''[[Events]]''' - Events are items (lines) in a [[Log]]. An Event could be a song that is picked using criteria you specify, a specific Cart number, one or more macros, etc. An Event can also be a place holder for, notes, voice-tracks, and for importing a "track" from an external, third-party music or traffic scheduling application.
+'''[[Events]]''' - Events are items (lines) in a [[Log]]. An Event could be a song that is picked using criteria you specify, a specific Cart number, one or more macros, etc. An Event can also be a place holder for, notes, voice-tracks, and for importing a &ldquo;track&rdquo; from an external, third-party music or traffic scheduling application.
 '''[[Clocks]]''' - Clocks represent one hour of '''Events''' in your broadcast. You can have as many or as few Clocks as you need. If you have broadcast hours where the format is exactly the same you can use the same clock for all those hours. You fill clocks with '''Events'''.
@@ Line 20: / Line 20: @@
 :* log in to RDAdmin
-:* touch &ldquo;Manage Services"
+:* touch &ldquo;Manage Services&rdquo;
-:* select your service and touch &ldquo;Edit"
+:* select your service and touch &ldquo;Edit&rdquo;
 :* in the ''Log Description Template'' box, type the Service name followed by a descriptive title &ldquo;template&rdquo; for all Logs, for example '''Production log for %$A, %Y-%m-%d''' (this results in Log descriptions like ''Tuesday, 2020-03-01'')
 :* in the ''Log Name Template'' blank, enter '''%Y%m%d''' (this results in logs named for the four-digit year, two digit month, and two-digit day of the month)
@@ Line 37: / Line 37: @@
 Events are the building blocks of log creation. An Event can be anything from playing a station ID to importing traffic or music from external logs to switching ports on your audio switcher. There are several options on this screen but let's keep things simple to start.
-Lets create a station ID event. Click &ldquo;Edit Events" then &ldquo;Add" and type in &ldquo;ID" or whatever you like. Locate the ''IMPORT'' section of the screen and click the radio button next to ''Select from''. In the dropdown (circled in red), select the Group that contains your legal station identification announcements. You probably want your ID to start close to the time you schedule it so check &ldquo;Use hard start time" and &ldquo;Make Next" (also circled in red). Transition should be &ldquo;PLAY" or &ldquo;SEGUE" Lastly, choose a unique Color via the bottom button and click &ldquo;OK" to save.
+Lets create a station ID event. Click &ldquo;Edit Events&rdquo; then &ldquo;Add&rdquo; and type in &ldquo;ID&rdquo; or whatever you like. Locate the ''IMPORT'' section of the screen and click the radio button next to ''Select from''. In the dropdown (circled in red), select the Group that contains your legal station identification announcements. You probably want your ID to start close to the time you schedule it so check &ldquo;Use hard start time&rdquo; and &ldquo;Make Next&rdquo; (also circled in red). Transition should be &ldquo;PLAY&rdquo; or &ldquo;SEGUE&rdquo; Lastly, choose a unique Color via the bottom button and click &ldquo;OK&rdquo; to save.
 [[Image:Event-toh-3.41..png]]
-Follow the same first steps to create a Liner event, but let's choose a specific Liner Cart to play every time this Event is scheduled. Rather than Importing from the Liner group, click and hold a Liner Cart on the left and drag it into the &ldquo;PRE-IMPORT CARTS" box as shown in the image.
+Follow the same first steps to create a Liner event, but let's choose a specific Liner Cart to play every time this Event is scheduled. Rather than Importing from the Liner group, click and hold a Liner Cart on the left and drag it into the &ldquo;PRE-IMPORT CARTS&rdquo; box as shown in the image.
 [[Image:Liner-event.gif|center]]
-Finally, we need to create an event to schedule a song. Again, create a new event. On the &ldquo;Import" line
+Finally, we need to create an event to schedule a song. Again, create a new event. On the &ldquo;Import&rdquo; line
 :* choose &ldquo;'''Select From'''&rdquo;

@@ Line 5: / Line 5: @@
 You need to do some setup in [[RDAdmin]] for the '''Service''' you will be using. Then it is a matter of creating:
-'''[[Event]]''' - a single item in a log. An Event could be a song that is picked using criteria you specify, a specific Cart number, one or more macros, etc. An Event can also be a place holder for, notes, voice-tracks, and for importing a "track" from the external, third-party music or traffic scheduling software.
+'''[[Events]]''' - Events are items (lines) in a [[Log]]. An Event could be a song that is picked using criteria you specify, a specific Cart number, one or more macros, etc. An Event can also be a place holder for, notes, voice-tracks, and for importing a "track" from an external, third-party music or traffic scheduling application.
-'''[[Clock]]''' - a Clock represents one hour of '''Events''' in your broadcast. You can have as many or as few clocks as you need. If you have broadcast hours where the format is exactly the same you can use the same clock for all those hours. You fill clocks with '''Events'''.
+'''[[Clocks]]''' - Clocks represent one hour of '''Events''' in your broadcast. You can have as many or as few Clocks as you need. If you have broadcast hours where the format is exactly the same you can use the same clock for all those hours. You fill clocks with '''Events'''.
-−
-'''[[Grid]]''' - A Grid represents one week (168 hours) of a '''Service''''s broadcast time. You fill the grid with '''Clocks'''.
+After you have Clocks with Events in them, you tell Rivendell which Clock to use in each of the 168 hours in a week. You do this by setting the Clocks in the '''[[Grid]]'''. A Grid represents one week of a '''Service''''s broadcast time. In other words, you  &ldquo;fill the grid with '''Clocks'''&rdquo;.
 From these, you can produce Logs. This all happens in '''[[RDLogManager]]'''

@@ Line 27: / Line 27: @@
 :* save settings and close RDAdmin
-See table E.2. Metadata DateTime Specification in the [http://opsguide.rivendellaudio.org/html/appendix.metadata_wildcards.html#table.metadata_wildcards.datetimes Rivendell Operations and Administration Guide] for all the available "wildcards" you can use in the ''Log Description Template'' and the ''Log Name Template''.
+See ''Appendix D. Filepath Wildcards'' in the [http://opsguide.rivendellaudio.org/html/appendix.filepath_wildcards.html Rivendell Operations and Administration Guide] for all the available "wildcards" you can use in the ''Log Description Template'' and the ''Log Name Template''.
 [[Image:Edit-service-3.4.1.png|center]]

@@ Line 33: / Line 33: @@
 Log creation occurs within RDLogManager so start RDLogManager to begin this tutorial.
-== Events ==
+=== Events ===
 Events are the building blocks of log creation. An Event can be anything from playing a station ID to importing traffic or music from external logs to switching ports on your audio switcher. There are several options on this screen but let's keep things simple to start.
@@ Line 62: / Line 62: @@
 <div style="clear: both"></div>
-== Clocks ==
+=== Clocks ===
 A clock is a series of "Events" that occur during an hour. You will need to create one clock for each ''unique'' hour. For example, if you are a music station and play music 24/7 with each hour being EXACTLY the same then you will only need one clock. If you play different styles of music during certain hours (and don't use an external music scheduler), you need a separate clock for those hours. If you air programs, you will probably need a separate clock for each hour.
@@ Line 96: / Line 96: @@
 NOTE: If you are using an external Music Scheduler, your "Music" event will span the entire sweep (i.e. 00:10 to 09:00) so that all songs in your music log appearing during that time frame will be imported. You will have to adjust the time frame so the clocks in Rivendell mesh with those in your Music Scheduler.
-== Grids ==
+=== Grids ===
 Click '''Edit Grids''' from the RDLogManager main window and then choose your service (there may only be one). You will see buttons representing each hour of every day (yes, 168 of them). The "Grids" allow you to choose which "Clock" is used for every hour of the week. In our case, we will set each hour to use our "Music" clock we created in the previous step.
@@ Line 106: / Line 106: @@
 This step is simple. Click or touch the '''Change All''' button. Select your Music Clock and click '''OK''', then click '''Yes''' to confirm that you want to set all 168 hours to use the same clock. Click '''Close''' when done setting all the Clocks in the Grid.
-== Generating Logs ==
+=== Generating Logs ===
 You are now ready to generate a log. Click "Generate Logs" from the RDLogManager main window. Adjust the date as required and click "Create New Log." That's it!
@@ Line 112: / Line 112: @@
 You can view and edit the log using [[RDLogEdit]]. To play the log, load it in [[RDAirPlay]].
-== Loading Next Day's Log ==
+=== Loading Next Day's Log ===
 Using [[RDAdmin]] you can configure Rivendell to load the next day's Log at Midnight. Touch

@@ Line 43: / Line 43: @@
 [[Image:event-music.jpg]]
 NOTE: If you are using an external Music Scheduler, your "Music" event will instead be set to import "from music."
 == Clocks ==