Académique Documents
Professionnel Documents
Culture Documents
Message-ID: <mailman.10.1415332793.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 03:59:56 2014
Subject: No subject
Message-ID: <mailman.11.1415332796.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:01 2014
Subject: No subject
Message-ID: <mailman.12.1415332801.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:07 2014
Subject: No subject
Message-ID: <mailman.13.1415332805.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:10 2014
Subject: No subject
Message-ID: <mailman.14.1415332810.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:12 2014
Subject: No subject
Message-ID: <mailman.15.1415332812.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:15 2014
Subject: No subject
Message-ID: <mailman.16.1415332815.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:17 2014
Subject: No subject
Message-ID: <mailman.17.1415332817.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:19 2014
Subject: No subject
Message-ID: <mailman.18.1415332819.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:27 2014
Subject: No subject
Message-ID: <mailman.19.1415332827.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:29 2014
Subject: No subject
Message-ID: <mailman.20.1415332829.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:33 2014
Subject: No subject
Message-ID: <mailman.21.1415332833.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:36 2014
Subject: No subject
Message-ID: <mailman.22.1415332836.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:36 2014
Subject: No subject
Message-ID: <mailman.23.1415332836.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:39 2014
Subject: No subject
Message-ID: <mailman.24.1415332839.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:41 2014
Subject: No subject
Message-ID: <mailman.25.1415332841.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:42 2014
Subject: No subject
Message-ID: <mailman.26.1415332842.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:42 2014
Subject: No subject
Message-ID: <mailman.27.1415332842.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:43 2014
Subject: No subject
Message-ID: <mailman.28.1415332843.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:43 2014
Subject: No subject
Message-ID: <mailman.29.1415332843.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:46 2014
Subject: No subject
Message-ID: <mailman.30.1415332846.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:46 2014
Subject: No subject
Message-ID: <mailman.31.1415332846.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:47 2014
Subject: No subject
Message-ID: <mailman.32.1415332847.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:47 2014
Subject: No subject
Message-ID: <mailman.33.1415332847.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:48 2014
Subject: No subject
Message-ID: <mailman.34.1415332848.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:48 2014
Subject: No subject
Message-ID: <mailman.35.1415332848.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:48 2014
Subject: No subject
Message-ID: <mailman.36.1415332848.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:49 2014
Subject: No subject
Message-ID: <mailman.37.1415332849.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:49 2014
Subject: No subject
Message-ID: <mailman.38.1415332849.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:50 2014
Subject: No subject
Message-ID: <mailman.39.1415332850.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:50 2014
Subject: No subject
Message-ID: <mailman.40.1415332850.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:53 2014
Subject: No subject
Message-ID: <mailman.41.1415332853.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:54 2014
Subject: No subject
Message-ID: <mailman.42.1415332854.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:54 2014
Subject: No subject
Message-ID: <mailman.43.1415332854.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:54 2014
Subject: No subject
Message-ID: <mailman.44.1415332854.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:55 2014
Subject: No subject
Message-ID: <mailman.45.1415332855.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:55 2014
Subject: No subject
Message-ID: <mailman.46.1415332855.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:56 2014
Subject: No subject
Message-ID: <mailman.47.1415332856.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:56 2014
Subject: No subject
Message-ID: <mailman.48.1415332856.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:58 2014
Subject: No subject
Message-ID: <mailman.49.1415332858.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:58 2014
Subject: No subject
Message-ID: <mailman.50.1415332858.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:59 2014
Subject: No subject
Message-ID: <mailman.51.1415332859.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:00:59 2014
Subject: No subject
Message-ID: <mailman.52.1415332859.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:01:00 2014
Subject: No subject
Message-ID: <mailman.53.1415332860.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:01:00 2014
Subject: No subject
Message-ID: <mailman.54.1415332860.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:01:07 2014
Subject: No subject
Message-ID: <mailman.55.1415332867.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:01:08 2014
Subject: No subject
Message-ID: <mailman.56.1415332868.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:01:13 2014
Subject: No subject
Message-ID: <mailman.57.1415332872.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:01:17 2014
Subject: No subject
Message-ID: <mailman.58.1415332877.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:01:20 2014
Subject: No subject
Message-ID: <mailman.59.1415332880.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:01:23 2014
Subject: No subject
Message-ID: <mailman.60.1415332883.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:01:25 2014
Subject: No subject
Message-ID: <mailman.61.1415332885.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:01:32 2014
Subject: No subject
Message-ID: <mailman.62.1415332891.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:01:36 2014
Subject: No subject
Message-ID: <mailman.63.1415332896.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:01:44 2014
Subject: No subject
Message-ID: <mailman.64.1415332904.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:01:59 2014
Subject: No subject
Message-ID: <mailman.65.1415332918.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:05 2014
Subject: No subject
Message-ID: <mailman.66.1415332925.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:05 2014
Subject: No subject
Message-ID: <mailman.67.1415332925.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:06 2014
Subject: No subject
Message-ID: <mailman.68.1415332926.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:06 2014
Subject: No subject
Message-ID: <mailman.69.1415332926.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:09 2014
Subject: No subject
Message-ID: <mailman.70.1415332929.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:09 2014
Subject: No subject
Message-ID: <mailman.71.1415332929.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:10 2014
Subject: No subject
Message-ID: <mailman.72.1415332930.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:11 2014
Subject: No subject
Message-ID: <mailman.73.1415332931.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:11 2014
Subject: No subject
Message-ID: <mailman.74.1415332931.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:13 2014
Subject: No subject
Message-ID: <mailman.75.1415332933.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:14 2014
Subject: No subject
Message-ID: <mailman.76.1415332934.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:15 2014
Subject: No subject
Message-ID: <mailman.77.1415332935.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:15 2014
Subject: No subject
Message-ID: <mailman.78.1415332935.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:16 2014
Subject: No subject
Message-ID: <mailman.79.1415332936.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:17 2014
Subject: No subject
Message-ID: <mailman.80.1415332937.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:17 2014
Subject: No subject
Message-ID: <mailman.81.1415332937.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:18 2014
Subject: No subject
Message-ID: <mailman.82.1415332938.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:18 2014
Subject: No subject
Message-ID: <mailman.83.1415332938.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:22 2014
Subject: No subject
Message-ID: <mailman.84.1415332942.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:23 2014
Subject: No subject
Message-ID: <mailman.85.1415332943.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:25 2014
Subject: No subject
Message-ID: <mailman.86.1415332945.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:27 2014
Subject: No subject
Message-ID: <mailman.87.1415332947.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:28 2014
Subject: No subject
Message-ID: <mailman.88.1415332948.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:29 2014
Subject: No subject
Message-ID: <mailman.89.1415332949.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:30 2014
Subject: No subject
Message-ID: <mailman.91.1415332950.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:32 2014
Subject: No subject
Message-ID: <mailman.92.1415332952.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:33 2014
Subject: No subject
Message-ID: <mailman.93.1415332953.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:47 2014
Subject: No subject
Message-ID: <mailman.94.1415332966.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:52 2014
Subject: No subject
Message-ID: <mailman.95.1415332971.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:55 2014
Subject: No subject
Message-ID: <mailman.96.1415332975.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:57 2014
Subject: No subject
Message-ID: <mailman.97.1415332977.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:02:58 2014
Subject: No subject
Message-ID: <mailman.98.1415332978.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:03:04 2014
Subject: No subject
Message-ID: <mailman.99.1415332984.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:03:09 2014
Subject: No subject
Message-ID: <mailman.100.1415332989.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:03:11 2014
Subject: No subject
Message-ID: <mailman.101.1415332991.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:03:12 2014
Subject: No subject
Message-ID: <mailman.102.1415332992.2343.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 7 02:50:35 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 7 04:03:13 2014
Subject: No subject
Message-ID: <mailman.103.1415332993.2343.htk-users@eng.cam.ac.uk>
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri Nov 7 04:29:00 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
Subject: No subject
Message-ID: <mailman.9.1416368525.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:15 2014
Subject: No subject
Message-ID: <mailman.10.1416368534.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:17 2014
Subject: No subject
Message-ID: <mailman.11.1416368537.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:20 2014
Subject: No subject
Message-ID: <mailman.12.1416368540.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:24 2014
Subject: No subject
Message-ID: <mailman.13.1416368544.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:24 2014
Subject: No subject
Message-ID: <mailman.14.1416368544.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:25 2014
Subject: No subject
Message-ID: <mailman.15.1416368545.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:27 2014
Subject: No subject
Message-ID: <mailman.16.1416368547.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:29 2014
Subject: No subject
Message-ID: <mailman.17.1416368549.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:32 2014
Subject: No subject
Message-ID: <mailman.18.1416368552.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:40 2014
Subject: No subject
Message-ID: <mailman.19.1416368560.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:42 2014
Subject: No subject
Message-ID: <mailman.20.1416368562.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:48 2014
Subject: No subject
Message-ID: <mailman.21.1416368568.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:52 2014
Subject: No subject
Message-ID: <mailman.22.1416368572.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:52 2014
Subject: No subject
Message-ID: <mailman.23.1416368572.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:54 2014
Subject: No subject
Message-ID: <mailman.24.1416368574.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:56 2014
Subject: No subject
Message-ID: <mailman.25.1416368576.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:56 2014
Subject: No subject
Message-ID: <mailman.26.1416368576.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:57 2014
Subject: No subject
Message-ID: <mailman.27.1416368577.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:58 2014
Subject: No subject
Message-ID: <mailman.28.1416368578.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:42:58 2014
Subject: No subject
Message-ID: <mailman.29.1416368578.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:01 2014
Subject: No subject
Message-ID: <mailman.30.1416368581.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:01 2014
Subject: No subject
Message-ID: <mailman.31.1416368581.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:02 2014
Subject: No subject
Message-ID: <mailman.32.1416368582.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:02 2014
Subject: No subject
Message-ID: <mailman.33.1416368582.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:03 2014
Subject: No subject
Message-ID: <mailman.34.1416368583.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:03 2014
Subject: No subject
Message-ID: <mailman.35.1416368583.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:04 2014
Subject: No subject
Message-ID: <mailman.36.1416368584.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:04 2014
Subject: No subject
Message-ID: <mailman.37.1416368584.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:05 2014
Subject: No subject
Message-ID: <mailman.38.1416368585.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:06 2014
Subject: No subject
Message-ID: <mailman.39.1416368586.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:06 2014
Subject: No subject
Message-ID: <mailman.40.1416368586.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:09 2014
Subject: No subject
Message-ID: <mailman.41.1416368589.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:09 2014
Subject: No subject
Message-ID: <mailman.42.1416368589.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:10 2014
Subject: No subject
Message-ID: <mailman.43.1416368590.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:10 2014
Subject: No subject
Message-ID: <mailman.44.1416368590.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:11 2014
Subject: No subject
Message-ID: <mailman.45.1416368591.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:11 2014
Subject: No subject
Message-ID: <mailman.46.1416368591.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:12 2014
Subject: No subject
Message-ID: <mailman.47.1416368592.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:13 2014
Subject: No subject
Message-ID: <mailman.48.1416368593.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:20 2014
Subject: No subject
Message-ID: <mailman.49.1416368600.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:23 2014
Subject: No subject
Message-ID: <mailman.50.1416368603.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:27 2014
Subject: No subject
Message-ID: <mailman.51.1416368607.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:30 2014
Subject: No subject
Message-ID: <mailman.52.1416368610.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:32 2014
Subject: No subject
Message-ID: <mailman.53.1416368612.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:32 2014
Subject: No subject
Message-ID: <mailman.54.1416368612.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:33 2014
Subject: No subject
Message-ID: <mailman.55.1416368613.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:33 2014
Subject: No subject
Message-ID: <mailman.56.1416368613.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:34 2014
Subject: No subject
Message-ID: <mailman.57.1416368614.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:34 2014
Subject: No subject
Message-ID: <mailman.58.1416368614.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:35 2014
Subject: No subject
Message-ID: <mailman.59.1416368615.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:35 2014
Subject: No subject
Message-ID: <mailman.60.1416368615.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:35 2014
Subject: No subject
Message-ID: <mailman.61.1416368615.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:37 2014
Subject: No subject
Message-ID: <mailman.62.1416368617.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:41 2014
Subject: No subject
Message-ID: <mailman.63.1416368621.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:45 2014
Subject: No subject
Message-ID: <mailman.64.1416368625.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:47 2014
Subject: No subject
Message-ID: <mailman.65.1416368627.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:47 2014
Subject: No subject
Message-ID: <mailman.66.1416368627.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:49 2014
Subject: No subject
Message-ID: <mailman.67.1416368629.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:50 2014
Subject: No subject
Message-ID: <mailman.68.1416368630.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:52 2014
Subject: No subject
Message-ID: <mailman.69.1416368632.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:43:59 2014
Subject: No subject
Message-ID: <mailman.70.1416368639.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:01 2014
Subject: No subject
Message-ID: <mailman.71.1416368641.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:04 2014
Subject: No subject
Message-ID: <mailman.72.1416368644.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:06 2014
Subject: No subject
Message-ID: <mailman.73.1416368646.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:09 2014
Subject: No subject
Message-ID: <mailman.74.1416368649.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:11 2014
Subject: No subject
Message-ID: <mailman.75.1416368651.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:14 2014
Subject: No subject
Message-ID: <mailman.76.1416368654.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:17 2014
Subject: No subject
Message-ID: <mailman.77.1416368657.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:19 2014
Subject: No subject
Message-ID: <mailman.78.1416368659.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:23 2014
Subject: No subject
Message-ID: <mailman.79.1416368663.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:25 2014
Subject: No subject
Message-ID: <mailman.80.1416368665.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:27 2014
Subject: No subject
Message-ID: <mailman.81.1416368667.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:28 2014
Subject: No subject
Message-ID: <mailman.82.1416368668.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:29 2014
Subject: No subject
Message-ID: <mailman.83.1416368669.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:30 2014
Subject: No subject
Message-ID: <mailman.84.1416368669.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:31 2014
Subject: No subject
Message-ID: <mailman.85.1416368671.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:33 2014
Subject: No subject
Message-ID: <mailman.86.1416368673.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:34 2014
Subject: No subject
Message-ID: <mailman.87.1416368673.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:34 2014
Subject: No subject
Message-ID: <mailman.88.1416368674.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:35 2014
Subject: No subject
Message-ID: <mailman.89.1416368675.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:36 2014
Subject: No subject
Message-ID: <mailman.91.1416368676.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:38 2014
Subject: No subject
Message-ID: <mailman.92.1416368678.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:39 2014
Subject: No subject
Message-ID: <mailman.93.1416368679.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:41 2014
Subject: No subject
Message-ID: <mailman.94.1416368681.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:42 2014
Subject: No subject
Message-ID: <mailman.95.1416368682.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:43 2014
Subject: No subject
Message-ID: <mailman.96.1416368683.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:45 2014
Subject: No subject
Message-ID: <mailman.97.1416368685.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:46 2014
Subject: No subject
Message-ID: <mailman.98.1416368686.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:48 2014
Subject: No subject
Message-ID: <mailman.99.1416368688.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:49 2014
Subject: No subject
Message-ID: <mailman.100.1416368689.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:50 2014
Subject: No subject
Message-ID: <mailman.101.1416368690.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:50 2014
Subject: No subject
Message-ID: <mailman.102.1416368690.1610.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Wed Nov 19 02:50:31 2014
From: bogus@does.not.exist.com ()
Date: Wed Nov 19 03:44:51 2014
Subject: No subject
Message-ID: <mailman.103.1416368691.1610.htk-users@eng.cam.ac.uk>
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Nov 19 04:00:56 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:00:51 2014
Subject: No subject
Message-ID: <mailman.1.1416456051.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:00:59 2014
Subject: No subject
Message-ID: <mailman.2.1416456059.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:01:02 2014
Subject: No subject
Message-ID: <mailman.3.1416456060.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:01:03 2014
Subject: No subject
Message-ID: <mailman.4.1416456063.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:01:04 2014
Subject: No subject
Message-ID: <mailman.5.1416456064.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:01:04 2014
Subject: No subject
Message-ID: <mailman.6.1416456064.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 20 04:01:05 2014
Subject: No subject
Message-ID: <mailman.7.1416456065.17853.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 20 02:53:16 2014
From: bogus@does.not.exist.com ()
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:16 2014
Subject: No subject
Message-ID: <mailman.1.1416543676.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:19 2014
Subject: No subject
Message-ID: <mailman.2.1416543679.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:20 2014
Subject: No subject
Message-ID: <mailman.3.1416543680.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:20 2014
Subject: No subject
Message-ID: <mailman.4.1416543680.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:21 2014
Subject: No subject
Message-ID: <mailman.5.1416543681.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:22 2014
Subject: No subject
Message-ID: <mailman.6.1416543682.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:22 2014
Subject: No subject
Message-ID: <mailman.7.1416543682.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:23 2014
Subject: No subject
Message-ID: <mailman.8.1416543683.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:23 2014
Subject: No subject
Message-ID: <mailman.9.1416543683.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:27 2014
Subject: No subject
Message-ID: <mailman.10.1416543687.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:27 2014
Subject: No subject
Message-ID: <mailman.11.1416543687.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:29 2014
Subject: No subject
Message-ID: <mailman.12.1416543689.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:29 2014
Subject: No subject
Message-ID: <mailman.13.1416543689.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:30 2014
Subject: No subject
Message-ID: <mailman.14.1416543690.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:31 2014
Subject: No subject
Message-ID: <mailman.15.1416543691.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:31 2014
Subject: No subject
Message-ID: <mailman.16.1416543691.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:32 2014
Subject: No subject
Message-ID: <mailman.17.1416543692.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:32 2014
Subject: No subject
Message-ID: <mailman.18.1416543692.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:34 2014
Subject: No subject
Message-ID: <mailman.19.1416543694.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:35 2014
Subject: No subject
Message-ID: <mailman.20.1416543695.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:36 2014
Subject: No subject
Message-ID: <mailman.21.1416543696.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:39 2014
Subject: No subject
Message-ID: <mailman.22.1416543699.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:40 2014
Subject: No subject
Message-ID: <mailman.23.1416543700.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:42 2014
Subject: No subject
Message-ID: <mailman.24.1416543702.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:44 2014
Subject: No subject
Message-ID: <mailman.25.1416543704.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:44 2014
Subject: No subject
Message-ID: <mailman.26.1416543704.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:45 2014
Subject: No subject
Message-ID: <mailman.27.1416543705.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:45 2014
Subject: No subject
Message-ID: <mailman.28.1416543705.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:46 2014
Subject: No subject
Message-ID: <mailman.29.1416543706.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:49 2014
Subject: No subject
Message-ID: <mailman.30.1416543709.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:50 2014
Subject: No subject
Message-ID: <mailman.31.1416543710.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:50 2014
Subject: No subject
Message-ID: <mailman.32.1416543710.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:51 2014
Subject: No subject
Message-ID: <mailman.33.1416543711.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:52 2014
Subject: No subject
Message-ID: <mailman.34.1416543712.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:52 2014
Subject: No subject
Message-ID: <mailman.35.1416543712.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:53 2014
Subject: No subject
Message-ID: <mailman.36.1416543713.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:54 2014
Subject: No subject
Message-ID: <mailman.37.1416543713.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:54 2014
Subject: No subject
Message-ID: <mailman.38.1416543714.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:55 2014
Subject: No subject
Message-ID: <mailman.39.1416543715.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:56 2014
Subject: No subject
Message-ID: <mailman.40.1416543716.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:21:59 2014
Subject: No subject
Message-ID: <mailman.41.1416543719.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:00 2014
Subject: No subject
Message-ID: <mailman.42.1416543720.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:01 2014
Subject: No subject
Message-ID: <mailman.43.1416543721.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:01 2014
Subject: No subject
Message-ID: <mailman.44.1416543721.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:02 2014
Subject: No subject
Message-ID: <mailman.45.1416543722.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:02 2014
Subject: No subject
Message-ID: <mailman.46.1416543722.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:03 2014
Subject: No subject
Message-ID: <mailman.47.1416543723.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:03 2014
Subject: No subject
Message-ID: <mailman.48.1416543723.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:06 2014
Subject: No subject
Message-ID: <mailman.49.1416543726.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:06 2014
Subject: No subject
Message-ID: <mailman.50.1416543726.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:07 2014
Subject: No subject
Message-ID: <mailman.51.1416543727.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:07 2014
Subject: No subject
Message-ID: <mailman.52.1416543727.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:08 2014
Subject: No subject
Message-ID: <mailman.53.1416543728.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:09 2014
Subject: No subject
Message-ID: <mailman.54.1416543729.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:09 2014
Subject: No subject
Message-ID: <mailman.55.1416543729.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:10 2014
Subject: No subject
Message-ID: <mailman.56.1416543730.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:10 2014
Subject: No subject
Message-ID: <mailman.57.1416543730.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:11 2014
Subject: No subject
Message-ID: <mailman.58.1416543731.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:11 2014
Subject: No subject
Message-ID: <mailman.59.1416543731.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:13 2014
Subject: No subject
Message-ID: <mailman.60.1416543733.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:13 2014
Subject: No subject
Message-ID: <mailman.61.1416543733.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:14 2014
Subject: No subject
Message-ID: <mailman.62.1416543734.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:14 2014
Subject: No subject
Message-ID: <mailman.63.1416543734.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:15 2014
Subject: No subject
Message-ID: <mailman.64.1416543735.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:15 2014
Subject: No subject
Message-ID: <mailman.65.1416543735.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:16 2014
Subject: No subject
Message-ID: <mailman.66.1416543736.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:17 2014
Subject: No subject
Message-ID: <mailman.67.1416543737.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:17 2014
Subject: No subject
Message-ID: <mailman.68.1416543737.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:18 2014
Subject: No subject
Message-ID: <mailman.69.1416543738.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:20 2014
Subject: No subject
Message-ID: <mailman.70.1416543740.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:21 2014
Subject: No subject
Message-ID: <mailman.71.1416543741.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:21 2014
Subject: No subject
Message-ID: <mailman.72.1416543741.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:22 2014
Subject: No subject
Message-ID: <mailman.73.1416543742.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:22 2014
Subject: No subject
Message-ID: <mailman.74.1416543742.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:23 2014
Subject: No subject
Message-ID: <mailman.75.1416543743.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:24 2014
Subject: No subject
Message-ID: <mailman.76.1416543744.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:24 2014
Subject: No subject
Message-ID: <mailman.77.1416543744.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:25 2014
Subject: No subject
Message-ID: <mailman.78.1416543745.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:25 2014
Subject: No subject
Message-ID: <mailman.79.1416543745.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:26 2014
Subject: No subject
Message-ID: <mailman.80.1416543746.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:26 2014
Subject: No subject
Message-ID: <mailman.81.1416543746.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:27 2014
Subject: No subject
Message-ID: <mailman.82.1416543747.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:28 2014
Subject: No subject
Message-ID: <mailman.83.1416543748.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:29 2014
Subject: No subject
Message-ID: <mailman.84.1416543749.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:30 2014
Subject: No subject
Message-ID: <mailman.85.1416543750.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:33 2014
Subject: No subject
Message-ID: <mailman.86.1416543753.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:34 2014
Subject: No subject
Message-ID: <mailman.87.1416543754.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:35 2014
Subject: No subject
Message-ID: <mailman.88.1416543755.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:38 2014
Subject: No subject
Message-ID: <mailman.89.1416543758.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:39 2014
Subject: No subject
Message-ID: <mailman.91.1416543759.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:40 2014
Subject: No subject
Message-ID: <mailman.92.1416543760.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:41 2014
Subject: No subject
Message-ID: <mailman.93.1416543761.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:43 2014
Subject: No subject
Message-ID: <mailman.94.1416543763.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:45 2014
Subject: No subject
Message-ID: <mailman.95.1416543765.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:49 2014
Subject: No subject
Message-ID: <mailman.96.1416543769.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:54 2014
Subject: No subject
Message-ID: <mailman.97.1416543774.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:22:57 2014
Subject: No subject
Message-ID: <mailman.98.1416543777.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:23:01 2014
Subject: No subject
Message-ID: <mailman.99.1416543781.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:23:05 2014
Subject: No subject
Message-ID: <mailman.100.1416543785.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:23:08 2014
Subject: No subject
Message-ID: <mailman.101.1416543788.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:23:12 2014
Subject: No subject
Message-ID: <mailman.102.1416543792.32149.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Fri Nov 21 02:53:25 2014
From: bogus@does.not.exist.com ()
Date: Fri Nov 21 04:23:15 2014
Subject: No subject
Message-ID: <mailman.103.1416543795.32149.htk-users@eng.cam.ac.uk>
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri Nov 21 04:37:50 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:21:47 2014
Subject: No subject
Message-ID: <mailman.1.1416630107.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:21:54 2014
Subject: No subject
Message-ID: <mailman.2.1416630114.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:21:56 2014
Subject: No subject
Message-ID: <mailman.3.1416630116.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:22:01 2014
Subject: No subject
Message-ID: <mailman.4.1416630121.14632.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 22 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 22 04:22:04 2014
Subject: No subject
Message-ID: <mailman.5.1416630124.14632.htk-users@eng.cam.ac.uk>
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:39:38 2014
Subject: No subject
Message-ID: <mailman.1.1416713976.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:39:42 2014
Subject: No subject
Message-ID: <mailman.2.1416713982.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:39:45 2014
Subject: No subject
Message-ID: <mailman.3.1416713985.2880.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 23 02:50:29 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 23 03:39:48 2014
Subject: No subject
Message-ID: <mailman.4.1416713988.2880.htk-users@eng.cam.ac.uk>
Message-ID: <mailman.3.1416808204.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:50:09 2014
Subject: No subject
Message-ID: <mailman.4.1416808209.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:50:14 2014
Subject: No subject
Message-ID: <mailman.5.1416808214.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:50:18 2014
Subject: No subject
Message-ID: <mailman.6.1416808218.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:50:20 2014
Subject: No subject
Message-ID: <mailman.7.1416808220.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:50:24 2014
Subject: No subject
Message-ID: <mailman.8.1416808224.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:50:28 2014
Subject: No subject
Message-ID: <mailman.9.1416808228.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:50:37 2014
Subject: No subject
Message-ID: <mailman.10.1416808237.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:50:41 2014
Subject: No subject
Message-ID: <mailman.11.1416808241.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:50:48 2014
Subject: No subject
Message-ID: <mailman.12.1416808248.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:50:54 2014
Subject: No subject
Message-ID: <mailman.13.1416808254.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:50:59 2014
Subject: No subject
Message-ID: <mailman.14.1416808259.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:51:03 2014
Subject: No subject
Message-ID: <mailman.15.1416808263.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:51:09 2014
Subject: No subject
Message-ID: <mailman.16.1416808268.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:51:15 2014
Subject: No subject
Message-ID: <mailman.17.1416808275.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:51:22 2014
Subject: No subject
Message-ID: <mailman.18.1416808282.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:51:35 2014
Subject: No subject
Message-ID: <mailman.19.1416808295.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:51:42 2014
Subject: No subject
Message-ID: <mailman.20.1416808302.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:51:54 2014
Subject: No subject
Message-ID: <mailman.21.1416808314.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:52:06 2014
Subject: No subject
Message-ID: <mailman.22.1416808325.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:52:13 2014
Subject: No subject
Message-ID: <mailman.23.1416808333.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:52:19 2014
Subject: No subject
Message-ID: <mailman.24.1416808339.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:52:27 2014
Subject: No subject
Message-ID: <mailman.25.1416808347.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:52:31 2014
Subject: No subject
Message-ID: <mailman.26.1416808351.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:52:34 2014
Subject: No subject
Message-ID: <mailman.27.1416808354.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:52:36 2014
Subject: No subject
Message-ID: <mailman.28.1416808356.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:52:38 2014
Subject: No subject
Message-ID: <mailman.29.1416808358.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:52:47 2014
Subject: No subject
Message-ID: <mailman.30.1416808367.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:52:50 2014
Subject: No subject
Message-ID: <mailman.31.1416808370.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:52:54 2014
Subject: No subject
Message-ID: <mailman.32.1416808374.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:52:57 2014
Subject: No subject
Message-ID: <mailman.33.1416808377.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:52:59 2014
Subject: No subject
Message-ID: <mailman.34.1416808379.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:53:05 2014
Subject: No subject
Message-ID: <mailman.35.1416808385.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:53:10 2014
Subject: No subject
Message-ID: <mailman.36.1416808390.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:53:15 2014
Subject: No subject
Message-ID: <mailman.37.1416808395.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:53:20 2014
Subject: No subject
Message-ID: <mailman.38.1416808400.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:53:23 2014
Subject: No subject
Message-ID: <mailman.39.1416808403.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:53:26 2014
Subject: No subject
Message-ID: <mailman.40.1416808406.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:53:39 2014
Subject: No subject
Message-ID: <mailman.41.1416808419.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:53:46 2014
Subject: No subject
Message-ID: <mailman.42.1416808426.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:53:53 2014
Subject: No subject
Message-ID: <mailman.43.1416808433.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:54:00 2014
Subject: No subject
Message-ID: <mailman.44.1416808440.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:54:05 2014
Subject: No subject
Message-ID: <mailman.45.1416808445.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:54:08 2014
Subject: No subject
Message-ID: <mailman.46.1416808448.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:54:12 2014
Subject: No subject
Message-ID: <mailman.47.1416808452.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:54:16 2014
Subject: No subject
Message-ID: <mailman.48.1416808456.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:54:24 2014
Subject: No subject
Message-ID: <mailman.49.1416808464.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:54:31 2014
Subject: No subject
Message-ID: <mailman.50.1416808471.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:54:39 2014
Subject: No subject
Message-ID: <mailman.51.1416808479.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:54:47 2014
Subject: No subject
Message-ID: <mailman.52.1416808486.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:54:57 2014
Subject: No subject
Message-ID: <mailman.53.1416808497.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:07 2014
Subject: No subject
Message-ID: <mailman.54.1416808507.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:10 2014
Subject: No subject
Message-ID: <mailman.55.1416808510.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:12 2014
Subject: No subject
Message-ID: <mailman.56.1416808512.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:14 2014
Subject: No subject
Message-ID: <mailman.57.1416808514.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:16 2014
Subject: No subject
Message-ID: <mailman.58.1416808516.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:18 2014
Subject: No subject
Message-ID: <mailman.59.1416808518.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:21 2014
Subject: No subject
Message-ID: <mailman.60.1416808521.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:24 2014
Subject: No subject
Message-ID: <mailman.61.1416808524.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:28 2014
Subject: No subject
Message-ID: <mailman.62.1416808528.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:30 2014
Subject: No subject
Message-ID: <mailman.63.1416808530.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:33 2014
Subject: No subject
Message-ID: <mailman.64.1416808533.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:35 2014
Subject: No subject
Message-ID: <mailman.65.1416808535.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:39 2014
Subject: No subject
Message-ID: <mailman.66.1416808538.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:42 2014
Subject: No subject
Message-ID: <mailman.67.1416808542.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:45 2014
Subject: No subject
Message-ID: <mailman.68.1416808545.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:47 2014
Subject: No subject
Message-ID: <mailman.69.1416808547.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:54 2014
Subject: No subject
Message-ID: <mailman.70.1416808554.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:56 2014
Subject: No subject
Message-ID: <mailman.71.1416808556.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:55:58 2014
Subject: No subject
Message-ID: <mailman.72.1416808558.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:56:01 2014
Subject: No subject
Message-ID: <mailman.73.1416808561.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:56:04 2014
Subject: No subject
Message-ID: <mailman.74.1416808564.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:56:06 2014
Subject: No subject
Message-ID: <mailman.75.1416808566.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:56:09 2014
Subject: No subject
Message-ID: <mailman.76.1416808568.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:56:11 2014
Subject: No subject
Message-ID: <mailman.77.1416808571.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:56:14 2014
Subject: No subject
Message-ID: <mailman.78.1416808574.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:56:16 2014
Subject: No subject
Message-ID: <mailman.79.1416808576.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:56:19 2014
Subject: No subject
Message-ID: <mailman.80.1416808579.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:56:22 2014
Subject: No subject
Message-ID: <mailman.81.1416808582.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:56:25 2014
Subject: No subject
Message-ID: <mailman.82.1416808584.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:56:31 2014
Subject: No subject
Message-ID: <mailman.83.1416808591.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:56:33 2014
Subject: No subject
Message-ID: <mailman.84.1416808593.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:56:36 2014
Subject: No subject
Message-ID: <mailman.85.1416808596.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:56:52 2014
Subject: No subject
Message-ID: <mailman.86.1416808612.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:56:55 2014
Subject: No subject
Message-ID: <mailman.87.1416808615.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:56:59 2014
Subject: No subject
Message-ID: <mailman.88.1416808619.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:57:01 2014
Subject: No subject
Message-ID: <mailman.89.1416808621.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:57:03 2014
Subject: No subject
Message-ID: <mailman.91.1416808623.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:57:06 2014
Subject: No subject
Message-ID: <mailman.92.1416808626.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:57:08 2014
Subject: No subject
Message-ID: <mailman.93.1416808628.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:57:15 2014
Subject: No subject
Message-ID: <mailman.94.1416808635.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:57:18 2014
Subject: No subject
Message-ID: <mailman.95.1416808638.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:57:20 2014
Subject: No subject
Message-ID: <mailman.96.1416808640.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:57:27 2014
Subject: No subject
Message-ID: <mailman.97.1416808647.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:57:30 2014
Subject: No subject
Message-ID: <mailman.98.1416808650.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:57:37 2014
Subject: No subject
Message-ID: <mailman.99.1416808657.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:57:41 2014
Subject: No subject
Message-ID: <mailman.100.1416808661.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:57:44 2014
Subject: No subject
Message-ID: <mailman.101.1416808664.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:57:48 2014
Subject: No subject
Message-ID: <mailman.102.1416808668.17107.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Mon Nov 24 02:56:06 2014
From: bogus@does.not.exist.com ()
Date: Mon Nov 24 05:57:52 2014
Subject: No subject
Message-ID: <mailman.103.1416808672.17107.htk-users@eng.cam.ac.uk>
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Mon Nov 24 06:29:46 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:17 2014
Subject: No subject
Message-ID: <mailman.1.1416886757.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:19 2014
Subject: No subject
Message-ID: <mailman.2.1416886759.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:20 2014
Subject: No subject
Message-ID: <mailman.3.1416886760.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:20 2014
Subject: No subject
Message-ID: <mailman.4.1416886760.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:21 2014
Subject: No subject
Message-ID: <mailman.5.1416886761.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:21 2014
Subject: No subject
Message-ID: <mailman.6.1416886761.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:22 2014
Subject: No subject
Message-ID: <mailman.7.1416886762.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:22 2014
Subject: No subject
Message-ID: <mailman.8.1416886762.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:23 2014
Subject: No subject
Message-ID: <mailman.9.1416886763.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:28 2014
Subject: No subject
Message-ID: <mailman.10.1416886768.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:31 2014
Subject: No subject
Message-ID: <mailman.11.1416886771.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:36 2014
Subject: No subject
Message-ID: <mailman.12.1416886776.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:40 2014
Subject: No subject
Message-ID: <mailman.13.1416886780.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:43 2014
Subject: No subject
Message-ID: <mailman.14.1416886783.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:47 2014
Subject: No subject
Message-ID: <mailman.15.1416886787.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:50 2014
Subject: No subject
Message-ID: <mailman.16.1416886790.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:53 2014
Subject: No subject
Message-ID: <mailman.17.1416886793.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:54 2014
Subject: No subject
Message-ID: <mailman.18.1416886794.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:56 2014
Subject: No subject
Message-ID: <mailman.19.1416886796.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:57 2014
Subject: No subject
Message-ID: <mailman.20.1416886797.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:39:59 2014
Subject: No subject
Message-ID: <mailman.21.1416886799.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:01 2014
Subject: No subject
Message-ID: <mailman.22.1416886801.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:02 2014
Subject: No subject
Message-ID: <mailman.23.1416886802.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:04 2014
Subject: No subject
Message-ID: <mailman.24.1416886804.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:07 2014
Subject: No subject
Message-ID: <mailman.25.1416886807.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:07 2014
Subject: No subject
Message-ID: <mailman.26.1416886807.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:08 2014
Subject: No subject
Message-ID: <mailman.27.1416886808.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:10 2014
Subject: No subject
Message-ID: <mailman.28.1416886810.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:10 2014
Subject: No subject
Message-ID: <mailman.29.1416886810.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:17 2014
Subject: No subject
Message-ID: <mailman.30.1416886817.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:20 2014
Subject: No subject
Message-ID: <mailman.31.1416886820.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:23 2014
Subject: No subject
Message-ID: <mailman.32.1416886823.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:27 2014
Subject: No subject
Message-ID: <mailman.33.1416886827.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:29 2014
Subject: No subject
Message-ID: <mailman.34.1416886829.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:29 2014
Subject: No subject
Message-ID: <mailman.35.1416886829.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:30 2014
Subject: No subject
Message-ID: <mailman.36.1416886830.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:31 2014
Subject: No subject
Message-ID: <mailman.37.1416886831.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:32 2014
Subject: No subject
Message-ID: <mailman.38.1416886832.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:32 2014
Subject: No subject
Message-ID: <mailman.39.1416886832.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:33 2014
Subject: No subject
Message-ID: <mailman.40.1416886833.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:37 2014
Subject: No subject
Message-ID: <mailman.41.1416886837.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:37 2014
Subject: No subject
Message-ID: <mailman.42.1416886837.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:38 2014
Subject: No subject
Message-ID: <mailman.43.1416886838.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:39 2014
Subject: No subject
Message-ID: <mailman.44.1416886839.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:39 2014
Subject: No subject
Message-ID: <mailman.45.1416886839.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:41 2014
Subject: No subject
Message-ID: <mailman.46.1416886841.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:41 2014
Subject: No subject
Message-ID: <mailman.47.1416886841.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:49 2014
Subject: No subject
Message-ID: <mailman.48.1416886849.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:56 2014
Subject: No subject
Message-ID: <mailman.49.1416886856.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:40:58 2014
Subject: No subject
Message-ID: <mailman.50.1416886858.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:01 2014
Subject: No subject
Message-ID: <mailman.51.1416886861.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:04 2014
Subject: No subject
Message-ID: <mailman.52.1416886864.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:07 2014
Subject: No subject
Message-ID: <mailman.53.1416886867.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:09 2014
Subject: No subject
Message-ID: <mailman.54.1416886869.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:12 2014
Subject: No subject
Message-ID: <mailman.55.1416886872.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:15 2014
Subject: No subject
Message-ID: <mailman.56.1416886875.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:17 2014
Subject: No subject
Message-ID: <mailman.57.1416886877.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:20 2014
Subject: No subject
Message-ID: <mailman.58.1416886880.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:22 2014
Subject: No subject
Message-ID: <mailman.59.1416886882.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:23 2014
Subject: No subject
Message-ID: <mailman.60.1416886883.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:24 2014
Subject: No subject
Message-ID: <mailman.61.1416886884.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:25 2014
Subject: No subject
Message-ID: <mailman.62.1416886885.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:25 2014
Subject: No subject
Message-ID: <mailman.63.1416886885.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:25 2014
Subject: No subject
Message-ID: <mailman.64.1416886885.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:26 2014
Subject: No subject
Message-ID: <mailman.65.1416886886.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:27 2014
Subject: No subject
Message-ID: <mailman.66.1416886887.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:27 2014
Subject: No subject
Message-ID: <mailman.67.1416886887.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:28 2014
Subject: No subject
Message-ID: <mailman.68.1416886888.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:28 2014
Subject: No subject
Message-ID: <mailman.69.1416886888.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:31 2014
Subject: No subject
Message-ID: <mailman.70.1416886891.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:31 2014
Subject: No subject
Message-ID: <mailman.71.1416886891.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:32 2014
Subject: No subject
Message-ID: <mailman.72.1416886892.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:32 2014
Subject: No subject
Message-ID: <mailman.73.1416886892.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:33 2014
Subject: No subject
Message-ID: <mailman.74.1416886893.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:33 2014
Subject: No subject
Message-ID: <mailman.75.1416886893.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:34 2014
Subject: No subject
Message-ID: <mailman.76.1416886894.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:35 2014
Subject: No subject
Message-ID: <mailman.77.1416886895.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:35 2014
Subject: No subject
Message-ID: <mailman.78.1416886895.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:36 2014
Subject: No subject
Message-ID: <mailman.79.1416886896.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:36 2014
Subject: No subject
Message-ID: <mailman.80.1416886896.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:37 2014
Subject: No subject
Message-ID: <mailman.81.1416886897.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:37 2014
Subject: No subject
Message-ID: <mailman.82.1416886897.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:38 2014
Subject: No subject
Message-ID: <mailman.83.1416886898.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:39 2014
Subject: No subject
Message-ID: <mailman.84.1416886899.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:40 2014
Subject: No subject
Message-ID: <mailman.85.1416886900.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:42 2014
Subject: No subject
Message-ID: <mailman.86.1416886902.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:42 2014
Subject: No subject
Message-ID: <mailman.87.1416886902.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:43 2014
Subject: No subject
Message-ID: <mailman.88.1416886903.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:44 2014
Subject: No subject
Message-ID: <mailman.89.1416886904.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:45 2014
Subject: No subject
Message-ID: <mailman.91.1416886905.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:46 2014
Subject: No subject
Message-ID: <mailman.92.1416886906.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:47 2014
Subject: No subject
Message-ID: <mailman.93.1416886907.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:49 2014
Subject: No subject
Message-ID: <mailman.94.1416886909.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:50 2014
Subject: No subject
Message-ID: <mailman.95.1416886910.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:51 2014
Subject: No subject
Message-ID: <mailman.96.1416886910.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:52 2014
Subject: No subject
Message-ID: <mailman.97.1416886912.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:54 2014
Subject: No subject
Message-ID: <mailman.98.1416886914.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:55 2014
Subject: No subject
Message-ID: <mailman.99.1416886915.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:56 2014
Subject: No subject
Message-ID: <mailman.100.1416886916.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:57 2014
Subject: No subject
Message-ID: <mailman.101.1416886917.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:58 2014
Subject: No subject
Message-ID: <mailman.102.1416886918.14847.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Tue Nov 25 02:50:32 2014
From: bogus@does.not.exist.com ()
Date: Tue Nov 25 03:41:59 2014
Subject: No subject
Message-ID: <mailman.103.1416886919.14847.htk-users@eng.cam.ac.uk>
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Tue Nov 25 04:05:54 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From bogus@does.not.exist.com Wed Nov 26 02:50:34 2014
From: bogus@does.not.exist.com ()
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:14:45 2014
Subject: No subject
Message-ID: <mailman.10.1417061685.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:14:46 2014
Subject: No subject
Message-ID: <mailman.11.1417061686.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:14:49 2014
Subject: No subject
Message-ID: <mailman.12.1417061689.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:14:49 2014
Subject: No subject
Message-ID: <mailman.13.1417061689.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:14:50 2014
Subject: No subject
Message-ID: <mailman.14.1417061690.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:14:50 2014
Subject: No subject
Message-ID: <mailman.15.1417061690.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:14:51 2014
Subject: No subject
Message-ID: <mailman.16.1417061691.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:14:51 2014
Subject: No subject
Message-ID: <mailman.17.1417061691.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:14:52 2014
Subject: No subject
Message-ID: <mailman.18.1417061692.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:14:56 2014
Subject: No subject
Message-ID: <mailman.19.1417061695.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:14:56 2014
Subject: No subject
Message-ID: <mailman.20.1417061696.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:14:59 2014
Subject: No subject
Message-ID: <mailman.21.1417061699.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:01 2014
Subject: No subject
Message-ID: <mailman.22.1417061701.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:03 2014
Subject: No subject
Message-ID: <mailman.23.1417061703.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:05 2014
Subject: No subject
Message-ID: <mailman.24.1417061705.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:07 2014
Subject: No subject
Message-ID: <mailman.25.1417061707.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:08 2014
Subject: No subject
Message-ID: <mailman.26.1417061708.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:08 2014
Subject: No subject
Message-ID: <mailman.27.1417061708.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:09 2014
Subject: No subject
Message-ID: <mailman.28.1417061709.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:10 2014
Subject: No subject
Message-ID: <mailman.29.1417061710.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:17 2014
Subject: No subject
Message-ID: <mailman.30.1417061717.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:21 2014
Subject: No subject
Message-ID: <mailman.31.1417061721.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:25 2014
Subject: No subject
Message-ID: <mailman.32.1417061725.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:29 2014
Subject: No subject
Message-ID: <mailman.33.1417061729.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:30 2014
Subject: No subject
Message-ID: <mailman.34.1417061730.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:31 2014
Subject: No subject
Message-ID: <mailman.35.1417061730.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:31 2014
Subject: No subject
Message-ID: <mailman.36.1417061731.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:32 2014
Subject: No subject
Message-ID: <mailman.37.1417061732.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:33 2014
Subject: No subject
Message-ID: <mailman.38.1417061733.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:34 2014
Subject: No subject
Message-ID: <mailman.39.1417061734.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:34 2014
Subject: No subject
Message-ID: <mailman.40.1417061734.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:41 2014
Subject: No subject
Message-ID: <mailman.41.1417061741.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:43 2014
Subject: No subject
Message-ID: <mailman.42.1417061743.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:43 2014
Subject: No subject
Message-ID: <mailman.43.1417061743.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:44 2014
Subject: No subject
Message-ID: <mailman.44.1417061744.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:46 2014
Subject: No subject
Message-ID: <mailman.45.1417061746.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:50 2014
Subject: No subject
Message-ID: <mailman.46.1417061749.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:53 2014
Subject: No subject
Message-ID: <mailman.47.1417061753.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:15:57 2014
Subject: No subject
Message-ID: <mailman.48.1417061757.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:03 2014
Subject: No subject
Message-ID: <mailman.49.1417061763.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:03 2014
Subject: No subject
Message-ID: <mailman.50.1417061763.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:04 2014
Subject: No subject
Message-ID: <mailman.51.1417061764.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:05 2014
Subject: No subject
Message-ID: <mailman.52.1417061765.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:06 2014
Subject: No subject
Message-ID: <mailman.53.1417061766.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:06 2014
Subject: No subject
Message-ID: <mailman.54.1417061766.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:07 2014
Subject: No subject
Message-ID: <mailman.55.1417061767.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:07 2014
Subject: No subject
Message-ID: <mailman.56.1417061767.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:08 2014
Subject: No subject
Message-ID: <mailman.57.1417061768.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:08 2014
Subject: No subject
Message-ID: <mailman.58.1417061768.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:09 2014
Subject: No subject
Message-ID: <mailman.59.1417061769.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:11 2014
Subject: No subject
Message-ID: <mailman.60.1417061771.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:14 2014
Subject: No subject
Message-ID: <mailman.61.1417061774.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:16 2014
Subject: No subject
Message-ID: <mailman.62.1417061776.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:19 2014
Subject: No subject
Message-ID: <mailman.63.1417061779.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:24 2014
Subject: No subject
Message-ID: <mailman.64.1417061784.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:27 2014
Subject: No subject
Message-ID: <mailman.65.1417061787.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:29 2014
Subject: No subject
Message-ID: <mailman.66.1417061789.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:33 2014
Subject: No subject
Message-ID: <mailman.67.1417061793.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:36 2014
Subject: No subject
Message-ID: <mailman.68.1417061795.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:39 2014
Subject: No subject
Message-ID: <mailman.69.1417061799.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:42 2014
Subject: No subject
Message-ID: <mailman.70.1417061802.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:43 2014
Subject: No subject
Message-ID: <mailman.71.1417061803.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:43 2014
Subject: No subject
Message-ID: <mailman.72.1417061803.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:44 2014
Subject: No subject
Message-ID: <mailman.73.1417061804.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:45 2014
Subject: No subject
Message-ID: <mailman.74.1417061805.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:45 2014
Subject: No subject
Message-ID: <mailman.75.1417061805.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:46 2014
Subject: No subject
Message-ID: <mailman.76.1417061806.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:46 2014
Subject: No subject
Message-ID: <mailman.77.1417061806.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:47 2014
Subject: No subject
Message-ID: <mailman.78.1417061807.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:48 2014
Subject: No subject
Message-ID: <mailman.79.1417061808.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:49 2014
Subject: No subject
Message-ID: <mailman.80.1417061809.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:50 2014
Subject: No subject
Message-ID: <mailman.81.1417061810.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:50 2014
Subject: No subject
Message-ID: <mailman.82.1417061810.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:51 2014
Subject: No subject
Message-ID: <mailman.83.1417061811.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:52 2014
Subject: No subject
Message-ID: <mailman.84.1417061812.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:53 2014
Subject: No subject
Message-ID: <mailman.85.1417061813.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:56 2014
Subject: No subject
Message-ID: <mailman.86.1417061816.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:16:57 2014
Subject: No subject
Message-ID: <mailman.87.1417061817.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:17:00 2014
Subject: No subject
Message-ID: <mailman.88.1417061820.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:17:02 2014
Subject: No subject
Message-ID: <mailman.89.1417061822.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:17:03 2014
Subject: No subject
Message-ID: <mailman.91.1417061823.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:17:04 2014
Subject: No subject
Message-ID: <mailman.92.1417061824.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:17:05 2014
Subject: No subject
Message-ID: <mailman.93.1417061825.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:17:07 2014
Subject: No subject
Message-ID: <mailman.94.1417061827.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:17:08 2014
Subject: No subject
Message-ID: <mailman.95.1417061828.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:17:19 2014
Subject: No subject
Message-ID: <mailman.96.1417061839.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:17:25 2014
Subject: No subject
Message-ID: <mailman.97.1417061845.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:17:30 2014
Subject: No subject
Message-ID: <mailman.98.1417061850.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:17:32 2014
Subject: No subject
Message-ID: <mailman.99.1417061852.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:17:33 2014
Subject: No subject
Message-ID: <mailman.100.1417061853.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:17:34 2014
Subject: No subject
Message-ID: <mailman.101.1417061854.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:17:35 2014
Subject: No subject
Message-ID: <mailman.102.1417061855.3593.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Thu Nov 27 02:50:44 2014
From: bogus@does.not.exist.com ()
Date: Thu Nov 27 04:17:36 2014
Subject: No subject
Message-ID: <mailman.103.1417061856.3593.htk-users@eng.cam.ac.uk>
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Thu Nov 27 04:37:36 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:04:42 2014
Subject: No subject
Message-ID: <mailman.1.1417233882.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:06:28 2014
Subject: No subject
Message-ID: <mailman.2.1417233987.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:06:58 2014
Subject: No subject
Message-ID: <mailman.3.1417234017.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:07:25 2014
Subject: No subject
Message-ID: <mailman.4.1417234044.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:07:56 2014
Subject: No subject
Message-ID: <mailman.5.1417234076.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:08:23 2014
Subject: No subject
Message-ID: <mailman.6.1417234102.14239.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sat Nov 29 02:50:38 2014
From: bogus@does.not.exist.com ()
Date: Sat Nov 29 04:08:49 2014
Subject: No subject
Message-ID: <mailman.7.1417234128.14239.htk-users@eng.cam.ac.uk>
Message-ID: <mailman.6.1417319783.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:56:23 2014
Subject: No subject
Message-ID: <mailman.7.1417319783.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:56:24 2014
Subject: No subject
Message-ID: <mailman.8.1417319784.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:56:25 2014
Subject: No subject
Message-ID: <mailman.9.1417319785.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:56:31 2014
Subject: No subject
Message-ID: <mailman.10.1417319791.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:56:32 2014
Subject: No subject
Message-ID: <mailman.11.1417319792.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:56:35 2014
Subject: No subject
Message-ID: <mailman.12.1417319795.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:56:37 2014
Subject: No subject
Message-ID: <mailman.13.1417319797.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:56:41 2014
Subject: No subject
Message-ID: <mailman.14.1417319800.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:56:43 2014
Subject: No subject
Message-ID: <mailman.15.1417319803.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:56:46 2014
Subject: No subject
Message-ID: <mailman.16.1417319806.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:56:49 2014
Subject: No subject
Message-ID: <mailman.17.1417319809.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:56:52 2014
Subject: No subject
Message-ID: <mailman.18.1417319811.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:56:59 2014
Subject: No subject
Message-ID: <mailman.19.1417319819.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:02 2014
Subject: No subject
Message-ID: <mailman.20.1417319822.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:05 2014
Subject: No subject
Message-ID: <mailman.21.1417319825.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:07 2014
Subject: No subject
Message-ID: <mailman.22.1417319827.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:08 2014
Subject: No subject
Message-ID: <mailman.23.1417319828.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:10 2014
Subject: No subject
Message-ID: <mailman.24.1417319830.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:12 2014
Subject: No subject
Message-ID: <mailman.25.1417319832.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:13 2014
Subject: No subject
Message-ID: <mailman.26.1417319833.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:14 2014
Subject: No subject
Message-ID: <mailman.27.1417319834.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:14 2014
Subject: No subject
Message-ID: <mailman.28.1417319834.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:15 2014
Subject: No subject
Message-ID: <mailman.29.1417319835.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:18 2014
Subject: No subject
Message-ID: <mailman.30.1417319838.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:18 2014
Subject: No subject
Message-ID: <mailman.31.1417319838.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:19 2014
Subject: No subject
Message-ID: <mailman.32.1417319839.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:20 2014
Subject: No subject
Message-ID: <mailman.33.1417319840.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:20 2014
Subject: No subject
Message-ID: <mailman.34.1417319840.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:21 2014
Subject: No subject
Message-ID: <mailman.35.1417319841.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:21 2014
Subject: No subject
Message-ID: <mailman.36.1417319841.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:22 2014
Subject: No subject
Message-ID: <mailman.37.1417319842.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:23 2014
Subject: No subject
Message-ID: <mailman.38.1417319843.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:24 2014
Subject: No subject
Message-ID: <mailman.39.1417319844.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:24 2014
Subject: No subject
Message-ID: <mailman.40.1417319844.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:27 2014
Subject: No subject
Message-ID: <mailman.41.1417319847.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:28 2014
Subject: No subject
Message-ID: <mailman.42.1417319848.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:28 2014
Subject: No subject
Message-ID: <mailman.43.1417319848.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:29 2014
Subject: No subject
Message-ID: <mailman.44.1417319849.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:30 2014
Subject: No subject
Message-ID: <mailman.45.1417319850.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:30 2014
Subject: No subject
Message-ID: <mailman.46.1417319850.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:31 2014
Subject: No subject
Message-ID: <mailman.47.1417319851.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:31 2014
Subject: No subject
Message-ID: <mailman.48.1417319851.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:33 2014
Subject: No subject
Message-ID: <mailman.49.1417319853.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:34 2014
Subject: No subject
Message-ID: <mailman.50.1417319854.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:34 2014
Subject: No subject
Message-ID: <mailman.51.1417319854.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:35 2014
Subject: No subject
Message-ID: <mailman.52.1417319855.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:35 2014
Subject: No subject
Message-ID: <mailman.53.1417319855.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:36 2014
Subject: No subject
Message-ID: <mailman.54.1417319856.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:36 2014
Subject: No subject
Message-ID: <mailman.55.1417319856.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:37 2014
Subject: No subject
Message-ID: <mailman.56.1417319857.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:41 2014
Subject: No subject
Message-ID: <mailman.57.1417319861.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:43 2014
Subject: No subject
Message-ID: <mailman.58.1417319863.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:45 2014
Subject: No subject
Message-ID: <mailman.59.1417319865.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:48 2014
Subject: No subject
Message-ID: <mailman.60.1417319868.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:52 2014
Subject: No subject
Message-ID: <mailman.61.1417319871.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:54 2014
Subject: No subject
Message-ID: <mailman.62.1417319874.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:57:58 2014
Subject: No subject
Message-ID: <mailman.63.1417319878.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:01 2014
Subject: No subject
Message-ID: <mailman.64.1417319881.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:03 2014
Subject: No subject
Message-ID: <mailman.65.1417319883.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:06 2014
Subject: No subject
Message-ID: <mailman.66.1417319886.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:08 2014
Subject: No subject
Message-ID: <mailman.67.1417319888.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:11 2014
Subject: No subject
Message-ID: <mailman.68.1417319891.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:14 2014
Subject: No subject
Message-ID: <mailman.69.1417319894.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:21 2014
Subject: No subject
Message-ID: <mailman.70.1417319901.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:22 2014
Subject: No subject
Message-ID: <mailman.71.1417319902.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:25 2014
Subject: No subject
Message-ID: <mailman.72.1417319905.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:26 2014
Subject: No subject
Message-ID: <mailman.73.1417319906.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:27 2014
Subject: No subject
Message-ID: <mailman.74.1417319907.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:27 2014
Subject: No subject
Message-ID: <mailman.75.1417319907.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:28 2014
Subject: No subject
Message-ID: <mailman.76.1417319908.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:29 2014
Subject: No subject
Message-ID: <mailman.77.1417319909.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:29 2014
Subject: No subject
Message-ID: <mailman.78.1417319909.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:30 2014
Subject: No subject
Message-ID: <mailman.79.1417319910.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:31 2014
Subject: No subject
Message-ID: <mailman.80.1417319911.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:31 2014
Subject: No subject
Message-ID: <mailman.81.1417319911.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:32 2014
Subject: No subject
Message-ID: <mailman.82.1417319912.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:32 2014
Subject: No subject
Message-ID: <mailman.83.1417319912.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:34 2014
Subject: No subject
Message-ID: <mailman.84.1417319914.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:35 2014
Subject: No subject
Message-ID: <mailman.85.1417319915.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:37 2014
Subject: No subject
Message-ID: <mailman.86.1417319917.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:38 2014
Subject: No subject
Message-ID: <mailman.87.1417319918.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:39 2014
Subject: No subject
Message-ID: <mailman.88.1417319919.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:40 2014
Subject: No subject
Message-ID: <mailman.89.1417319920.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:41 2014
Subject: No subject
Message-ID: <mailman.91.1417319921.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:43 2014
Subject: No subject
Message-ID: <mailman.92.1417319923.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:44 2014
Subject: No subject
Message-ID: <mailman.93.1417319924.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:46 2014
Subject: No subject
Message-ID: <mailman.94.1417319926.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:47 2014
Subject: No subject
Message-ID: <mailman.95.1417319927.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:48 2014
Subject: No subject
Message-ID: <mailman.96.1417319928.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:50 2014
Subject: No subject
Message-ID: <mailman.97.1417319930.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:51 2014
Subject: No subject
Message-ID: <mailman.98.1417319931.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:53 2014
Subject: No subject
Message-ID: <mailman.99.1417319933.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:54 2014
Subject: No subject
Message-ID: <mailman.100.1417319934.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:55 2014
Subject: No subject
Message-ID: <mailman.101.1417319935.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:56 2014
Subject: No subject
Message-ID: <mailman.102.1417319936.28676.htk-users@eng.cam.ac.uk>
From bogus@does.not.exist.com Sun Nov 30 02:51:37 2014
From: bogus@does.not.exist.com ()
Date: Sun Nov 30 03:58:57 2014
Subject: No subject
Message-ID: <mailman.103.1417319937.28676.htk-users@eng.cam.ac.uk>
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sun Nov 30 04:17:23 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Mon Dec 1 04:39:01 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Dec 3 04:49:55 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri Dec 5 04:56:42 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sat Dec 6 04:47:34 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Dec 10 04:42:13 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri Dec 12 04:58:45 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sat Dec 13 05:02:45 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Dec 17 04:41:44 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri Dec 19 04:43:00 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sat Dec 20 04:42:30 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Dec 24 04:50:56 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri Dec 26 04:18:56 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sat Dec 27 04:18:41 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Mon Dec 29 04:38:18 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Dec 31 04:46:25 2014
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Thu Jan 1 04:47:04 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Mon Jan 5 04:31:11 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Jan 7 04:55:44 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Thu Jan 8 05:00:34 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sat Jan 10 04:35:18 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Mon Jan 12 04:56:14 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Tue Jan 13 04:20:12 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sat Jan 17 04:58:06 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Mon Jan 19 04:50:50 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Tue Jan 20 05:04:51 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Thu Jan 22 04:53:37 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sat Jan 24 04:20:10 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sun Jan 25 05:03:57 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Thu Jan 29 05:06:27 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sat Jan 31 05:12:50 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sun Feb 1 05:05:41 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Tue Feb 3 04:36:23 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Thu Feb 5 04:29:41 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri Feb 6 04:27:21 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Tue Feb 10 04:25:05 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Thu Feb 12 04:47:37 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri Feb 13 04:59:33 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sun Feb 15 04:31:03 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Tue Feb 17 04:27:45 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Feb 18 04:25:48 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sun Feb 22 04:24:56 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Tue Feb 24 04:37:39 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Feb 25 06:04:20 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri Feb 27 05:03:56 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sun Mar 1 04:50:11 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Mon Mar 2 04:29:15 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri Mar 6 05:27:18 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sun Mar 8 04:40:52 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Mon Mar 9 05:14:30 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Mar 11 05:05:21 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri Mar 13 05:16:21 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sat Mar 14 05:22:44 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Mar 18 05:20:47 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri Mar 20 04:22:51 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sat Mar 21 05:29:08 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Mon Mar 23 04:51:39 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Mar 25 05:25:47 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Thu Mar 26 05:48:17 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Mon Mar 30 04:34:05 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Wed Apr 1 05:36:29 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Thu Apr 2 05:20:47 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sat Apr 4 05:35:50 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Mon Apr 6 05:25:24 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Tue Apr 7 05:32:42 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sat Apr 11 05:37:03 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Mon Apr 13 05:09:54 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Tue Apr 14 05:30:10 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Thu Apr 16 05:46:59 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sat Apr 18 05:30:28 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sun Apr 19 05:51:21 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Thu Apr 23 04:18:27 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sat Apr 25 04:25:11 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Sun Apr 26 04:14:24 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Tue Apr 28 04:12:11 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Thu Apr 30 04:11:29 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497
Company reg no GB 05697423, VAT reg no 925606030
51 Canterbury Street, Cambridge, CB4 3QG, UK
From tonyr at cantabResearch.com Tue Nov 4 20:04:46 2014
From: tonyr at cantabResearch.com (Tony Robinson)
Date: Fri May 1 04:11:31 2015
Subject: [HTK-Users] HTK license agreement
In-Reply-To: <545241EC02000049000E3077@pta-emo.csir.co.za>
References: <545241EC02000049000E3077@pta-emo.csir.co.za>
Message-ID: <5459315E.9030409@cantabResearch.com>
I just saw this post - I hope I haven't also missed any replies.
It's been a while since I read the HTK licence, but from memory and past
commercial practices I believe that what you are proposing is entirely
acceptable according to the HTK licence.
In fact I think www.speechmatics.com uses HVite in exactly this way to
do some final tidying up of the large vocabulary speech recognition output.
Tony
On 30/10/14 11:49, Georg Schlunz wrote:
> Good day
>
> Regarding the HTK license, as specified at http://htk.eng.cam.ac.uk/docs/licen
se.shtml , I would like to know whether the following scenario is permitted:
>
> The HTK software (including HVite) sits on a server in-house in our organisati
on, as per license sections 2.1 and 2.3.
> The HTK software (including HVite) is never distributed to a commercial (or no
n-commercial) party, as per license section 2.2.
>
> We have written our own server-client software, where:
> a) the client records speech and sends the audio file to the server, which pas
ses it on to HVite (the server software and HTK sit on the same in-house machine
)
> b) HVite decodes the audio into text
> c) the server replies to the client with the decoded text and the client proce
sses the text somehow
>
> Naturally, the client software contains no HTK code; it only processes data pr
oduced by HTK.
>
> Therefore, may this client software and decoding SERVICE be sold commercially
(as long as we agree to license sections 2.4 and 2.5)?
>
> Thank you
> Georg Schlunz
>
-- ** Cantab is hiring: www.cantabResearch.com/openings ** -Dr A J Robinson, Founder, Cantab Research Ltd
Phone direct: 01223 778240 office: 01223 794497