From: "=?utf-8?Q?Mathias_M=C3=B6hl?=" Received: from mail-wm0-f49.google.com ([74.125.82.49] verified) by media-motion.tv (CommuniGate Pro SMTP 6.1.0) with ESMTPS id 6331767 for AE-List@media-motion.tv; Sat, 07 Oct 2017 09:06:42 +0200 Received: by mail-wm0-f49.google.com with SMTP id l68so11940535wmd.5 for ; Sat, 07 Oct 2017 00:08:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=from:message-id:mime-version:subject:date:references:to:in-reply-to; bh=Frf4Y42PCkPxULHoU8B4EZ3TWLI/TnJOJIB1IMgU5zw=; b=pkNdT1RwOm7SNyGkbRny9K+dvgtFlByK5jqNtQL2PhnixuQ2nM7VuzBpr8nGFVn4GL c2M3hKQpfosVoge0c2D2imI3D3USkLkXpsynEt7WLVzusaZI8z3JpUNmaaXy1JJ3VSlD pYlawqRhvrYIgC/FJl8rD2Y/SDOuS8XtMyrjafjqWpAlvQ6NDjDtq1XDZhLQCCO+/JJF OVyGets4aj1p2BewicBiWgHKjR2EO/yfHW0ClrBtZ+bIotImJcx40l5YZ+NMCpi3w9CJ XVBKQehpgqvAoEMFReg0ZjCSLfOVi7VPC1+WZQLgp+0121qaHjfQG274TRjF29/tg+fg v57Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :references:to:in-reply-to; bh=Frf4Y42PCkPxULHoU8B4EZ3TWLI/TnJOJIB1IMgU5zw=; b=BJ0W4yEfoan+GRmHsB1pEGUGuVyc2Ve8RoJTKuFigySNoC/8rvl4zR+GaiKFMZ6sto O9lklQaJUVdwNOyCOyPdNFBw0FTq84JxrWftSUvM3fYTMuYO8IW47E4yIRVI+0tX8KkE G7WozzifYJPjBI2QLAQtnalRVeoXcbVL9lTzXl5pTyKBMq4UraPEBzBgXjGseoTYFmPu Df7DgaEvf3a4/IfNxGeg/6LXp9OHlhcrFGBA0FxLhV7IW9sIa9yXaRNr/twhP0FGVPom ooeSDxnMjZQprFYeRFmzQoJo6Asj6+urFHxBU8MhK8R9loHkYHHhlbUokrb0DofE5q8Y YtHA== X-Gm-Message-State: AMCzsaUA76j+0gHdBD1RCfeexCE0jZHMpjKBNCAcpKmBUTlXqWF1+zeX ka03qJbW/2OWrh77OyPE83WNpGSj X-Google-Smtp-Source: AOwi7QBJN3/imzgja0oo25rjEp9ntCGs/dKA2oNSAVRCqXMIbQUF6iWihf5wIDZl6ipiIv3HN2LRvw== X-Received: by 10.28.209.200 with SMTP id i191mr3323272wmg.156.1507360117944; Sat, 07 Oct 2017 00:08:37 -0700 (PDT) Return-Path: Received: from mathiasmac-3.fritz.box (p5DC64E02.dip0.t-ipconnect.de. [93.198.78.2]) by smtp.googlemail.com with ESMTPSA id a195sm2052821wme.34.2017.10.07.00.08.36 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sat, 07 Oct 2017 00:08:36 -0700 (PDT) Content-Type: multipart/alternative; boundary="Apple-Mail=_FF1752C8-862F-4792-9B3F-3E759CE9CDBE" Message-Id: Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: [AE] Inaccurate marker timings in CC 2017 Date: Sat, 7 Oct 2017 09:08:35 +0200 References: To: After Effects Mail List In-Reply-To: X-Mailer: Apple Mail (2.3124) --Apple-Mail=_FF1752C8-862F-4792-9B3F-3E759CE9CDBE Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi Phil, Filing a bug report is always a good idea, the Ae team is really happy = about any feedback! If you need to generate beat markers frequently, you might consider = using my extension BeatEdit for Premiere Pro to write beat markers in = the audio files that then also show up as clip markers in Ae. Here is a one minute tutorial showing this workflow: = https://mamoworld.com/tutorials/beatmarkers-after-effects-beatedit-premier= e-pro = Cheers, Mathias > On 06 Oct 2017, at 13:22, Phil Bearman = wrote: >=20 > Does anybody else find that adding markers in time with audio is = extremely inaccurate in CC 2017? >=20 > I've found in previous versions that when I added markers to the beat = of a piece of music they were typically a couple of frames out, but were = consistently out so that I could just correct them using Rift. >=20 > In CC2017 they get further and further out of sync as the timeline = progresses. In a project I've just been working on the first marker was = out by about 10 frames, and after 30 seconds the markers were about 30 = frames out, meaning I'm having to manually reposition the markers.=20 >=20 > See a screenshot here - https://imgur.com/a/bjX4A = - showing a simple drum track where I've = tapped out markers on every other beat with the asterisk key. (This is = in an empty project with nothing other than the drum track imported). >=20 > They start off 2 frames out and over the course of 10 seconds they = have drifted to 7 frames out. >=20 > If I repeat the same experiment in CC 2014 they are consistently 2 = frames out. >=20 > It does seem like another example of degraded performance in CC2017 vs = earlier versions. >=20 > Just wanted to see if anybody else experiences this before I file a = bug report. >=20 > Cheers, > Phil > --=20 > Phil Bearman >=20 > Phil Bearman Creative Media Solutions=20 > Motion Graphics Design >=20 > PhilBearman.co.uk >=20 > 0161 236 2581 - 9am-5pm, Monday-Friday >=20 > This message contains confidential information and is intended only = for the individual named. If you are not the named addressee you should = not disseminate, distribute or copy this E-Mail. Please notify the = sender immediately by E-Mail if you have received this E-Mail by mistake = and delete the E-Mail from your system. E-Mail transmission cannot be = guaranteed to be secure or error-free as information could be = intercepted, corrupted, lost, destroyed, arrive late or incomplete, or = contain viruses. The sender therefore does not accept liability for any = errors or omissions in the contents of this message or attached = documents or for any damage suffered by your computer system caused by = any errors or viruses contained in the E-Mail message or any attached = documents. >=20 --Apple-Mail=_FF1752C8-862F-4792-9B3F-3E759CE9CDBE Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
Hi Phil,
Filing a bug report is always a = good idea, the Ae team is really happy about any feedback!

If you need to generate = beat markers frequently, you might consider using my extension BeatEdit = for Premiere Pro to write beat markers in the audio files that then also = show up as clip markers in Ae.
Here is a one minute = tutorial showing this workflow:
https://mamoworld.com/tutorials/beatmarkers-after-effects-beate= dit-premiere-pro

Cheers,
Mathias


On = 06 Oct 2017, at 13:22, Phil Bearman <AE-List@media-motion.tv> wrote:

Does anybody else find that adding markers in time with audio = is extremely inaccurate in CC 2017?

I've found in previous versions that = when I added markers to the beat of a piece of music they were typically = a couple of frames out, but were consistently out so that I could just = correct them using Rift.

In CC2017 they get further and further out of sync as the = timeline progresses.  In a project I've just been working on the = first marker was out by about 10 frames, and after 30 seconds the = markers were about 30 frames out, meaning I'm having to manually = reposition the markers. 

See a = screenshot here -  https://imgur.com/a/bjX4A - showing a simple drum = track where I've tapped out markers on every other beat with the = asterisk key. (This is in an empty project with nothing other than the = drum track imported).

They start off 2 frames out and over the course of 10 seconds = they have drifted to 7 frames out.

If I repeat the same experiment in CC = 2014 they are consistently 2 frames out.

It does seem like another example of = degraded performance in CC2017 vs earlier versions.

Just wanted to see if = anybody else experiences this before I file a bug report.

Cheers,
Phil
-- 

Phil Bearman

Phil Bearman Creative Media = Solutions=20
Motion Graphics Design

PhilBearman.co.uk


0161 236 2581 - 9am-5pm, = Monday-Friday

This message=20 contains confidential information and is intended only for the = individual named.=20 If you are not the named addressee you should not disseminate, = distribute or=20 copy this E-Mail. Please notify the sender immediately by E-Mail if = you have=20 received this E-Mail by mistake and delete the E-Mail from your = system. E-Mail=20 transmission cannot be guaranteed to be secure or error-free as = information=20 could be intercepted, corrupted, lost, destroyed, arrive late or = incomplete,=20 or contain viruses. The sender therefore does not accept liability for = any errors=20 or omissions in the contents of this message or attached documents or = for any=20 damage suffered by your computer system caused by any errors or = viruses contained=20 in the E-Mail message or any attached = documents.


= --Apple-Mail=_FF1752C8-862F-4792-9B3F-3E759CE9CDBE--