Table of Contents

Preface

• In Schedule Mode a Channel records clips based on Calendar Events from the Apple macOS Calendar application of the machine running the just:in User Interface (=which is part of just:control).
• After configuring a Channel in the just:in Configuration Panel, a Calendar with that same name will be automatically created in Apple's Calendar app for that Channelthe Channel's name will beadded to the Calendar app.
• You may also use any other Calendar , which can be added to the Apple Calendar app , – like a Calendar from iCloud or Gmail Accounts or from Mail/Calendar servers.
• The Channel Events scheduled in the corresponding Calendar will automatically switch the Channel to Schedule Mode and start recording, when there is an Event scheduled and a Recording (if the Channel is in Idle mode and in a different Channel Modeidle).

Selecting a Calendar for a Channel

1. Open the just:in Configuration Panel

...

1. .
2. Go to the Channel Settings.

...

2. Select the appropriate Calendar for each Channel.

Adding Calendar Events for Schedule Mode

1. Open the Apple Calendar application.
2. Select the desired Channel in the list of Calendars on the left or the appropriate desired Calendar for this channelChannel.
   Image RemovedImage Added
   
   
3. Add Events to the Calendar. An Event may not exceed 12 hours.
   Image RemovedImage Added
   
   
4. The Events will show up in the Inspector of the just:in User interface. Each Event will result in one Recording.
   

...

Additional Functionality

Custom Calendar Events Variables

There are three custom Calendar Event Variables which can be used to make the naming of the scheduled events easier:

• <Channel> will be replaced with the actual Channel Name of the Channel.
• <Date> will be replaced with the actual date of the current recording (Format: "yyyy-mm-dd").
• <Time> will be replaced with the actual start recording time of the current recording.

Date & Time Format

Changing the format of these Calendar Event Variables is also very easy and straightforward. In order to make this as flexible as possible, we are using the default system settings for that. To change that, open the custom format settings for “Dates” and “Times”, which can be found here:

1. Open the macOS System Preferences and open the Date & Time Preferences Panel
   Image Added
   
   
2. Open Language & Region Settings
   Image Added
   
   
3. Switch to the Advanced Settings
   Image Added
   
   
4. Change Dates and/or Times Format Settings here ("Full:")
   Image AddedImage Added

Repeating Calendar Events

Repeating a Calendar Event would result in a file which gets overwritten every time the same event is executed again. To avoid this you can add the Variables <Channel>, <Date> and <Time> to the Calendar Event. This appends the channel name, date and time (= beginning of the corresponding Calendar Event) to the Clip Name.

Using Naming Presets in Schedule Mode

This will be available in an upcoming version. If you need more information about that , please contact us.

Maximum Record Length

It is not possible to use Calendar Events which exceed a length of 12 hours. just:in will truncate the Recording length automatically, if required.

Image RemovedImage Added

Adjustable Event End Time while Recording

Starting with v4.0, the The Recording Event End Time can be changed during recording. This is especially useful when if you have to make changes during an ongoing recording. Simply adapt the Event End Time in the macOS Calendar application and just:in will recognise the change.

Manually

...

stopping a Scheduled Recording

You can manually stop a scheduled recording Scheduled Recording by simply pressing the recording Record button within the Channel Preview. Doing so will also delete the Calendar Event in the macOS Calendar application.

List of

...

Scheduled Events in the Inspector

The Schedule Scheduled Event List only shows the upcoming ten events scheduled in the chosen Schedule Calendar and only if these events are within the next 24 hours. All further events are only visible in the Calendar itself and they get displayed within the just:in user interface as soon as one of the previous recording events are finished.

Quitting the User Interface

When trying to quit the Quitting the just:in User Interface, just:in is warning you that results in the application can not longer receive update no longer receiving updates or new eventsEvents. It is necessary to have the just:in User Interface (=which is part of just:control) open all the time when using Schedule Mode for a Channel.

Image Added

Further Notes

Working with shared Calendars in Schedule Mode

As mentioned above you can also work with shared Calendars (like Gmail, iCloud or any other Mail/Calendar server which can be added to the macOS Calendar application) in Schedule Mode. This enables you to use two ore more machines for adding recording events to the appropriate Calendar. Just make sure that the User Interface machine has access to the Calendar and the User Interface application is running. Then you can use all machines/devices for adding recording events and you are not limited to the User Interface machine anymore.

Multiple just:control client systems

Please beware that it is not recommended to use multiple just:control client systems when working in Schedule Mode, as this will introduce unexpected behaviour.

Importance of Timecode Source in Schedule Mode

When using the Schedule Mode in just:in (mac and linux), the Timecode Source is an important setting and therefore it should be chosen correctly to ensure a smooth operation.

In general all available Timecode Sources can be used for Schedule Mode. System administrators only have to take care that the just:in engine (mac and linux) gets fed with the same Timecode Source as the macOS machine, where the Scheduling (just:in User Interface and macOS Calendar application) is running. For instance, when using a NTP Server as Source (=Computer Time), then the macOS machine for the just:in engine and the machine for the just:in User Interface have to have the same NTP server configured (same for a Channel.Image Removedjust:in linux).

It is also possible to use a LTC source (AJA Capture Card LTC) for Scheduling, then the LTC generator only need a NTP option as well and then it will also work correctly, as the engine can get fed via the Timecode In of the video card and the machine for the User Interface can be configured with NTP.