This is an example of how to use Reaper - a much more powerful DAW (digital audio workstation) than Winamp - to send timecode to Titan, assuming both are installed on two separate PCs. MIDI is being sent over network using rtpMIDI.

1. of course both computers need to be networked and configured properly (same network mask, correct IP addresses etc.)
2. Titan PC-Suite, from v12 on (External AvoKey or T2 required - T1 or Editor Avokey does not work)
3. rtpMIDI (see Software List, to route the MIDI signal from one computer to the other
4. Reaper (see Software List)
5. you may consider using the vVIMTC plugin for Reaper in order to have timecode also when stopped or paused

This needs to installed on both machines. rtpMIDI provides a virtual MIDI port which is then bein forwarded over the network to other participants of this session. There is a compact tutorial provided at the rtpMIDI website. Usually setting this up is as easy as checking the session is enabled in both machines, and both see each other.

The two pictures show the setup which was used in the a.m. youtube video - SB-HP is the laptop running Titan while rtp1 is the session on the laptop running Reaper.

rtpMIDI on the computer running Titan

rtpMIDI on the computer running Reaper

I found that Titan is allergic to MIDI ports being added or removed while Titan is running. The safest route is, after installing and configuring rtpMIDI, to completely restart the computer which runs Titan.

In order to initially watch the timecode open a timecode workspace window (e.g. Timecode 1) and select MIDI as timecode source.

Launch Reaper. Load a track if you want (not required for this to function). However here are the steps to configure Reaper correctly:

In the Options menu select Preferences - this opens the preferences window. Find MIDI devices in the Audio section. This should list the virtual MIDI port you created in rtpMIDI as MIDI output:

Right-click on the port in the output section and either tick Enable output from the menu…

… or select Configure output… and make the settings there:

Confirm the settings with OK to close the preferences window.

Rewind the timeline to 0:00:00 (simply press <Pos 1>). From the Insert menu select SMPTE LTC/MTC Timecode Generator. This inserts this generator as new track.

If you had already inserted an audio track then probably the timecode track was inserted on the same track. Simply click, drag and drop it onto a new track:

Also, it's a good idea to bring the timecode track (at least) to the same length like the music:

Right-click on the new timecode track, and from the context menu select Item properties:

(or, with the timecode track selected hit F2).

This opens the Media Item Properties window:

If you want then you can change length, position and other details. In any case you need to make sure it is MTC (MIDI timecode): click on the Properties button (at the bottom). In the new little window set the properties to Send MIDI (MTC):

Confirm/close both windows by clicking OK.

This button slightly depends from your reaper version:

In Reaper v5, click on the routing button in the track controls (left to the timecode track):

In Reaper v6, right-click on the volume knob ov the timecode track.

This opens the routing window for this track. Under MIDI Hardware Output (top-right) select your virtual MIDI port:

Close the routing window.

Essentially this should work straight away: as soon as you hit Play in Reaper, the timecode value in Titan starts to run. It is advisable to change the time units in Reaper: right-click on the timeline or the displayed time, and from the context menu select Hours:Minutes:Seconds:Frames.

This also works together with Reaper being controlled by Titan via MMC, like described in Controlling Reaper from Titan on the same PC

You can now use this as timecode source to sync cuelists to music coming from Reaper.

I noticed a gap between the timestamps in Reaper and in Titan. This seems to be due to both, Reaper, as well as Titan/USB Expert, and needs to be investigated further.

Also, Reaper doesn't generate timecode when being stopped or paused. There is a little plugin available called vVIMTC which circumvents this:

• download the plugin from https://forum.cockos.com/showthread.php?t=43606 or from here vvimtc_generator.txt
• on your Reaper computer, copy this file to %appdata%\REAPER\Effects
• in Reaper, disable (Mute) the previously added timecode track
• add a new empty track
• on tjhis track, add the effect JS vVIMTC Generator, add its properties (framerate etc.)
• route this track's MIDI output to your virtual port as decribed above
• record/arm this track

Now, the timecode sent is accurate also when reaper is stopped or paused.

If things do not work as expected then there are some tools which help finding the fault:

You may route the signal via loopMIDI as explained in Sending Timecode from Reaper to Titan on the same PC. Please install loopMIDI and apply the correct settings in Reaper.

Also, in this case rtpMIDI needs to be told to take its input from loopMIDI:

loopMIDI shows the number of transmitted data. This number increases with every command, note or message. With timecode, this number increases continuously and rather fast.

Open the USB Expert Console. This must show your virtual MIDI port as connected panel (top-left). Select the MIDI tab top-right, click Watch MIDI, in the MIDI watcher window select MIDI Input and Raw MIDI. Now, as you send a command, it is shown in the MIDI watcher, with continuously incoming data like this:

Additionally, on the Timecode tab (top-right), you should see the real timecode values running:

Another great tool for fault finding (but also for fault generating) is MIDI-OX. One of the things you should be aware of is that it may take the MIDI signal and doesn't forward it unless told to do so - you may see proper MIDI messages and wonder why nothing is passed on, and as soon as you close MIDI-OX, suddenly everything works flawlessly. You have been warned… (Thus, usually use this together with loopMIDI in order to tap into the signal)

Install and launch MIDI-OX (see Software List. From the Options menu select MIDI Devices. Make sure loopMIDI Port is listed as MIDI Input but isn't mapped to any output (yes, you can create a feedback loop, and yes, you do not want to do this…)

From the View menu select Input Monitor…. In this window, all incoming MIDI data are shown. You will see the cpntinuous stream of MTC Quarter Freame messages: