TUNETRACKER SYSTEM IN ACTION - TuneTracker

# FadeInto (Command Center Only)

In situations where you anticipate joining an audio event "in progress," an abrupt "chopped transition" into the next event can sound harsh and unprofessional. The "fade into" feature lets you ease into the next event by starting it at zero volume and fading it up, a feature commonly used when a live audio source such as a network broadcast is "joined in progress."

Fading-into is useful in circumstances where either the exact time when you go to a live event is unpredictable, or you are joining an event at an exact time but that live event is already providing audio. These are the two classic "join-in-progress" scenarios you're likely to encounter.

With the fadeinto event, you can control exactly how slowly or quickly you'd like the fade-up to happen, by changing the value of the number at the end of the fadeinto line, as shown below.

Below are three example situations where a fadeinto comes in handy.

---

# FadeInto


Let's say you have a live church service scheduled for broadcast on a Sunday morning. You want TuneTracker to start broadcasting at exactly 9:00 a.m., even though the actual service varies a bit as to what is happening at straight-up 9 a.m. It might be music, while it might already be someone talking. The answer is to add a fadeinto, to soften the blow of joining the service in the midst of a song or spoken words. Note that the syntax includes a number that indicates how many seconds long the fade will be.

•   Example:
  
  # Hour 9
  # interrupt@:00:00 5
  Play /boot/path/StationID.wav
  Play /boot/path/WeNowJoinChurchServiceInProgress.wav
  # FadeInto 2
  # Live-For 01:00:00 (etc.)
  
  

In this second example, we are coming out of an audio file that has an unpredictable length (weather-related closures and cancellations), joining a live network talk show as soon as the file is done playing, and keeping the live network talk show on the air until :20 past the hour. Since we are joining the network in progress, there's no way to know in advance how long to schedule the live event to run. So we will make the live event supermegaextra long (we call it "infinite length") and then we'll break away from it with an interrupt.

•   Example
  
  # Hour 14
  # interrupt@:00:00 5
  Play /boot/path/StationID.wav
  play /boot/path/ClosuresAndCancellations.wav
  Play /boot/path/WeNowJoinTalkNetworkInProgress.wav
  # fadeinto 3
  # Live-For 99:00:00
  # interrupt@:20:00
  (etc.)
  
  

It's unlikely you'll ever need to fade into a digital audio file, but it is indeed doable, in case the need should ever arise, as shown below.

•   Example:
  
  play /boot/path/Announcement.mp3
  # fadeinto 5
  play /boot/path/SomeOtherFile.wav
  (etc.)
  
  

Note that fadeinto is not a "crossfade" feature, so there is no worrying that using it will cause TuneTracker to prematurely fade out of whatever event preceeds it.

Table of Contents