Frequently asked questions

A timecode editor for REAPER with a grandMA3 plug-in for two-way synchronization. Create and edit Timecodes, Tracks, Events, Sequences, and Cue data in either application. Run Update from grandMA3 to review and exchange changes in both directions.

Use REAPER 7.71 or newer. Release 4 is verified with grandMA3/onPC 2.4.2.2. The package includes Windows x64 and macOS REAPER components and the grandMA3 plug-in. Install both halves from the same TimecodeMate3 release.

Buy from the TimecodeMate3 page on Gumroad. Gumroad shows the current price and provides your purchase download and License key. If its payment options don’t suit you, email support@vldurnov.com.

A licence supports up to two machine/profile slots. The activation key is tied to the computer/profile it was issued for. For a machine replacement, contact support@vldurnov.com.

Release 4.1 fixes invisible table-editing text and vertically mirrored icons on macOS. Selected markers are now added to the selected Track. Only the REAPER component changed; the grandMA3 plug-in is unchanged from Release 4.

TimecodeMate3 accepts either a Gumroad License key (code) or a .tcm3lic licence file. Use the matching activation method in REAPER. Both return a computer-specific .tcm3key activation key.

Choose Open licence file... and select your .tcm3lic. Use the activation page or QR code to download the computer-specific .tcm3key. Install it with Install existing .tcm3key file... on Windows or Install .tcm3key... on macOS. See licence activation.

Open Extensions > TCM3: Show UI in REAPER. On Windows, paste the receipt’s License key into Enter your Gumroad code and select Activate code.

On macOS, choose Enter Gumroad code in browser..., enter the code, and download the .tcm3key. Back in REAPER, choose Install .tcm3key.... See installation and activation.

Yes. Use the activation QR code with a connected device, or create an offline .tcm3req request and transfer it to a connected device. Bring the returned .tcm3key back to the REAPER computer and install it. REAPER and grandMA3 still need a local connection for Update.

No. A Gumroad purchase uses the License key from your receipt. The .tcm3lic flow is for licences supplied as a file. The .tcm3key returned by activation is what activates the computer.

Check that REAPER is 7.71 or newer. On Windows, the DLL must be directly inside REAPER’s UserPlugins folder. On macOS, rerun the supplied installer and complete any macOS security confirmation. Restart REAPER and open Extensions > TCM3: Show UI.

Close the hosts, replace the REAPER component, and copy the complete grandMA3 plug-in folder from the release. Reimport the XML into the same Plugin Pool slot. Updating the extension does not remove your installed activation key. On macOS, use the supplied package; in-app update checks are Windows-only.

Yes. Update synchronizes in both directions. Edit the paired data in REAPER, grandMA3, or both, then run the grandMA3 plug-in. Changes made on only one side can be carried to the other; conflicting edits to the same value need a choice in the Summary.

Open the destination REAPER project and start its server. Run the plug-in in the correct grandMA3 Data Pool, choose + MA timecodes (Add from MA) in the Summary, and enter a Timecode selection such as 3 or 1 Thru 5. Choose Continue, review the Summary, and press Update. See the step-by-step import instructions.

No. After a Timecode is paired, use normal Update to exchange further edits in either direction. Use Add from MA when you want to include another unpaired MA Timecode.

If the edits conflict, choose the intended value in the Summary. Two-way Update keeps non-conflicting changes from both sides. The Reaper > and < MA options instead use the named side for differing synchronized values. See Update direction choices.

No. Start Update by running the grandMA3 plug-in. The Summary lets you review proposed changes and resolve required choices before applying them. Reconnecting may finish an already prepared exchange without asking for the same decisions again.

Yes, on a trusted private LAN. In the grandMA3 REAPER endpoint dialog, use the REAPER computer’s IPv4 address and server port (default 48003). Use 127.0.0.1 only when both applications run on the same computer. See the connection instructions.

A required choice is unresolved. Look for a conflicting value, target, or pool slot that needs a decision. Select the intended value or target. If you are unsure, cancel and compare your saved show material before proceeding.

No. Deleting a synchronized top-level Timecode or Sequence in REAPER leaves its grandMA3 counterpart in place. Deleting a synchronized Timecode on grandMA3 leaves the REAPER Timecode and pauses its sync. These protections do not mean every Event or Cue deletion is ignored: always read the Summary.

The Event, its Track, or its Timecode may be locked or disabled. The native marker is restored when that edit is not allowed. Unlock or enable the intended object in TimecodeMate3 and try again.

There is a migration action: TCM3: Convert TimecodeMate 2 markers to Events. Back up the project first, run the action, and inspect the Events and cue targets before the first grandMA3 Update. TimecodeMate3 uses an explicit Update workflow.

Email support@vldurnov.com with your operating system, REAPER version, grandMA3 version, TimecodeMate3 release, the steps that caused the problem, and the exact error text. A screenshot of the Summary or System Monitor can help explain an Update problem.