From a3a398242bbb1149611ba03a8ee717e9af07de75 Mon Sep 17 00:00:00 2001
From: Robin Gareus <robin@gareus.org>
Date: Mon, 5 Nov 2012 11:26:27 +0000
Subject: [PATCH] tigten LTC Slave resolution.

The reason for this is that the LTC generator uses the slave's
resolution as watermark for max-drift, resync. A possible drawback:
session-process will force silent rolls if the delta is larger
than the resolution. LTC has a carrier freq of ~2kHz, choosing
half of that seems a good compromise.

git-svn-id: svn://localhost/ardour2/branches/3.0@13380 d708f5d6-7413-0410-9779-e7cbd77b26cf
---
 libs/ardour/ltc_slave.cc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libs/ardour/ltc_slave.cc b/libs/ardour/ltc_slave.cc
index 5afb1dfb6d..ea40fea654 100644
--- a/libs/ardour/ltc_slave.cc
+++ b/libs/ardour/ltc_slave.cc
@@ -80,7 +80,7 @@ LTC_Slave::~LTC_Slave()
 ARDOUR::framecnt_t
 LTC_Slave::resolution () const
 {
-	return (framecnt_t) (frames_per_ltc_frame);
+	return (framecnt_t) (session.frame_rate() / 1000);
 }
 
 bool
-- 
2.30.2