From: "Greg Balint" Received: from mail-yb1-f176.google.com ([209.85.219.176] verified) by media-motion.tv (CommuniGate Pro SMTP 6.1.0) with ESMTPS id 7199139 for ae-list@media-motion.tv; Fri, 30 Nov 2018 18:16:21 +0100 Received: by mail-yb1-f176.google.com with SMTP id z2-v6so2517957ybj.2 for ; Fri, 30 Nov 2018 09:29:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:date:message-id:subject:from:to:in-reply-to:references :user-agent; bh=rtj2EGYiXjLFDHm4uCXnLJiz9tNSeBaOpb5GwuIW5Yg=; b=oi8jpywfmea9ydQYjzxpuhXONxoSf36zQad8TH0pSF6K1a2kiwEAmFnHWaYUENlHfZ R6awFtENq+tX6ayuyi+xwNwdx1NtDWzCBFJMlWPFa1AuqxRh2NNONsgF4Be8NdpncOUE KGU9pkARdeguUeAsr5UL5WxMBfA3jXaHSrR//+3Je1RAhANVkZ+xJLD5qQF1CF2/h/zv XdtRpueln1WMLBkaaIlMGvU71MgK2xvmiGVuhzRHHqPay5XGNiWsEzKi2uloFsNSzo97 LUrC5SBm+Nu/64qJ3d3+Fzt8ITaL2RreZb4sQjev3NT/ted3P5BII9dQzaepwk0t4hxr Txww== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :in-reply-to:references:user-agent; bh=rtj2EGYiXjLFDHm4uCXnLJiz9tNSeBaOpb5GwuIW5Yg=; b=PtnD085kDvDctLIs8fOKmili5UiOEZknsxFLXoPHlTlSFffAC+43QcsxWPtVUcNrUa hKJZO2X3iF7TEiX4qw84OnhO9bVPhiD/k2sMLpoJNvcc0QeFgl3Gu1rZnCBt32OSQjfc 0vVoFI6E+q7oADXfz8qLiPWvQio40QtGz6nuo/Uw+hXtwZfnfm7T18r+MYtMoai0Pid8 J8XHFHWzjroWI2zbm2OD3QG8+D/SO/9xNvnjqfDMP4G2QBToMl7ZbvRKfW4guishGV9h d6XWLRSy6Iz0gxrjqaWw+ZUn6tM1bhN3S1UnAuuVwgKgfVl8j4Xzt7v1fC0xOIjezZnH 4Biw== X-Gm-Message-State: AA+aEWZnt8cTeM1s/fFsgeVLDYCNs5SkgeohOYq6p4Av1ck0bBRj9J/C S/K5mgT0FyPpk/UyDMosZoGviOkf X-Google-Smtp-Source: AFSGD/WtWGzuzXhQFbUxclLHiJvoZipeOrILYSjVu6Mv/04biL/MiS+vGdRTDIhUGIUbGTzIuSufkQ== X-Received: by 2002:a25:afc3:: with SMTP id d3-v6mr6144030ybj.493.1543598978942; Fri, 30 Nov 2018 09:29:38 -0800 (PST) Return-Path: Received: from [192.168.1.9] ([66.18.44.243]) by smtp.gmail.com with ESMTPSA id w77sm2520224ywa.9.2018.11.30.09.29.37 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 30 Nov 2018 09:29:38 -0800 (PST) Content-Type: multipart/alternative; boundary="----=_NextPart_19537063.864808101927" MIME-Version: 1.0 Date: Fri, 30 Nov 2018 12:29:16 -0500 Message-ID: Subject: Re: [AE] reluctant to commit to CC 2019 To: "Ross Shain" In-Reply-To: References: User-Agent: Mailbird/2.5.24.0 X-Mailbird-ID: c43a0fde-8e4a-4ae3-9073-780849c29c06@getmailbird.com ------=_NextPart_19537063.864808101927 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable I'm sort of in the same boat.. I don't use PR that often, but with AE v16 (= 2019) I just can't find the stability i need in certain EASY tasks..=C2=A0 I've started 2 projects now, since it's been out, and I've TRIED to use 201= 9 for them.. however little weird things happen that literally halt all pro= duction in 2019. For instance. =C2=A0I bring in a 2 layer Illustrator logo.. One layer is th= e "logo" and the other layer is the "text". =C2=A0 This normally doesn't ha= ve an issue.. and I've tried to emulate the issue from a base start, and it= doesn't happen.. yet if I open that file I was working in, into 2019, it c= ontinues to happen, even though the comps are identical and reference the s= ame AI file. =C2=A0Basically one of the layers doesn't even display its con= tents.. and somehow, when I move that one layer around, it "sometimes" acts= like it's parented with constraints to the other layer. (move it around fr= eely, but when I get to a certain position, the other layer acts like it's = parented and will attach and follow" =C2=A0 Dropping a 3rd duplicate layer = of the same AI file will not fix anything, it'll show empty, and AE actuall= y crashes, every time.. This seems to happen more readily when I'm using 2 = displays for the interface (comp viewer on my left screen, everything else = on my middle screen) =C2=A0 That, along with finding the timecode issues when the update first came out= , and still not seeing it fixed with a hotfix patch, has me leery of using = anything in 2019 for a while..=C2=A0 Sucks, because now I've got 2014, 2018, and 2019 installed all to use diffe= rent portions of the programs that are better at different things.. 2018 be= ing the main work environment, but 2014 being around to wrangle heavy rende= rs with multi-frame rendering, and 2019 being around to use the Mocha AE pl= ugin mainly.=C2=A0 I wish each version didn't introduce these showstopping bugs in the first y= ear it's around.. It just doesn't give me much faith in new versions being = anything to "flock to" ///Greg Balint //Art Director / Motion Graphics Designer /321.514.4839 delRAZOR.com [http://www.delrazor.com/]/ On 11/30/2018 11:54:53 AM, Ross Shain wrote: Hey Jim,=C2=A0 I can not answer your Adobe questions... but just wanted you and others to = know that the Mocha Pro 2019 plug-in will work with older versions of AE (a= nd Premiere back to CC 2014. Most know that Mocha Pro adds some cool featur= es not found in Mocha AE. Mocha Pro annual sale ends tonight at midnight.= =C2=A0 Compare Mocha Pro to Mocha AE:=C2=A0https://borisfx.com/products/mocha-pro/= #compare [https://borisfx.com/products/mocha-pro/#compare] Sale info:=C2=A0https://borisfx.com/news/black-friday-2018-up-to-50-off-all= -products/ [https://borisfx.com/news/black-friday-2018-up-to-50-off-all-pro= ducts/] On Fri, 30 Nov 2018 at 11:28, Jim Curtis wrote: Sorry for the long post.=C2=A0 If you=E2=80=99re busy, just ignore this.=C2= =A0 Part of it is griping. I wonder how many others here are in the same boat. =C2=A0 My favorite feature of Ae CC 2019, and the ONLY new feature that interests = me is the Mocha Plug-in.=C2=A0 I=E2=80=99ve been using Ae 2019 just for tha= t one feature, but doing everything else in CC 2018.=C2=A0 Pr has one new f= eature only I=E2=80=99m interested in, and that=E2=80=99s the enhanced Lume= tri Color effect.=C2=A0 The enhanced Puppet Tool may come in handy at some = point.=C2=A0 Otherwise, meh. I use Pr as much as Ae.=C2=A0 If I want to use Dynamic Link, I have to use = the same versions.=C2=A0 IOW, I can=E2=80=99t use Ae 2018 with Pr 2019, and= expect DL to work.=C2=A0 I can=E2=80=99t even copy clips in Pr and paste t= hem in Ae if the versions don=E2=80=99t match. I made a mistake by testing Pr 2019 for one =E2=80=9Csmall=E2=80=9D project= for one client for whom I=E2=80=99d done about ten videos in Pr 2018.=C2= =A0 It worked OK, but there are still some bugs that make me reluctant to c= ommit to all of CC 2019.=C2=A0 Honestly, I can=E2=80=99t remember what they= were other than Pr taking an extremely long time to launch before getting = to the Open dialog. So, I got a new project that requires me to use footage from my previous te= n projects.=C2=A0 I started it in Pr 2018.=C2=A0 Everything was fine except= when I needed to access footage in that Pr 2019 project.=C2=A0 Not a show = stopper.=C2=A0 I just had to launch the Pr 2019 project, and do an XML expo= rt of my master Sequence and b-roll and interview select Sequences, and the= n import that into Pr 2018, losing all the animated masking I did in Pr 201= 9 (quite a bit).=C2=A0 I was pleased to see some of my Lumetri Color effect= s were retained. =C2=A0 I wish Adobe would figure out how to Save As... a previous version in Pr as= they have for Ae, or allow us to import Sequences from a later version of = Pr, or use Dynamic Link between different versions.=C2=A0 Alas. Anyway=E2=80=A6 I=E2=80=99m posting to ask if anybody else has committed to= CC 2019 and having good success with both Pr and Ae.=C2=A0 If you=E2=80=99= re experiencing issues, what are they?=C2=A0 Are there workarounds? =C2=A0 My biggest fear is encountering a job-killing bug that will inhibit timely = delivery of a paying project (see link below).=C2=A0 I=E2=80=99m on Mac High Sierra with a Nvidia Titan GPU. Jim C. Posts like this aren=E2=80=99t encouraging: https://forums.adobe.com/thread/2556384 [https://forums.adobe.com/thread/25= 56384] . -- Ross Shain Chief Product Officer: Mocha +1.646.298.6458 | borisfx.com [http://borisfx.com] ------=_NextPart_19537063.864808101927 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
=0A =0A = =0A = =0A =0A = =0A I'm sort of in the= same boat.. I don't use PR that often, but with AE v16 (2019) I just can't= find the stability i need in certain EASY tasks.. 

I've started 2 projects now, since it's been out, and I've TRIED to use 20= 19 for them.. however little weird things happen that literally halt all pr= oduction in 2019.

For instance.  I bring in a= 2 layer Illustrator logo.. One layer is the "logo" and the other layer is = the "text".   This normally doesn't have an issue.. and I've tried to = emulate the issue from a base start, and it doesn't happen.. yet if I open = that file I was working in, into 2019, it continues to happen, even though = the comps are identical and reference the same AI file.  Basically one= of the layers doesn't even display its contents.. and somehow, when I move= that one layer around, it "sometimes" acts like it's parented with constra= ints to the other layer. (move it around freely, but when I get to a certai= n position, the other layer acts like it's parented and will attach and fol= low"   Dropping a 3rd duplicate layer of the same AI file will not fix= anything, it'll show empty, and AE actually crashes, every time.. This see= ms to happen more readily when I'm using 2 displays for the interface (comp= viewer on my left screen, everything else on my middle screen)  
<= br>That, along with finding the timecode issues when the update first came = out, and still not seeing it fixed with a hotfix patch, has me leery of usi= ng anything in 2019 for a while.. 

Sucks, because now I've got = 2014, 2018, and 2019 installed all to use different portions of the program= s that are better at different things.. 2018 being the main work environmen= t, but 2014 being around to wrangle heavy renders with multi-frame renderin= g, and 2019 being around to use the Mocha AE plugin mainly. 
<= br>I wish each version didn't introduce these showstopping bugs in the firs= t year it's around.. It just doesn't give me much faith in new versions bei= ng anything to "flock to"


///Greg Ba= lint
//Art Director / Motion Graphics Designer
/321.514.4839
delRAZOR.com/
=0A = =0A
=0A

On 11/30/2018 11:54:53 AM, Ross Shain <ae-lis= t@media-motion.tv> wrote:

Hey Jim, = ;
I can not answer your Adobe questions... but just wanted you and othe= rs to know that the Mocha Pro 2019 plug-in will work with older versions of= AE (and Premiere back to CC 2014. Most know that Mocha Pro adds some cool = features not found in Mocha AE. Mocha Pro annual sale ends tonight at midni= ght. 




=
On Fri, 30 Nov 2018 at 11:28, Jim Curtis <AE-List@media-motion.tv= > wrote:
Sorry for the long post.  If you=E2=80=99re bu= sy, just ignore this.  Part of it is griping.

= I wonder how many others here are in the same boat.  

My favorite f= eature of Ae CC 2019, and the ONLY new feature that interests me is the Moc= ha Plug-in.  I=E2=80=99ve been using Ae 2019 just for that one feature= , but doing everything else in CC 2018.  Pr has one new feature only I= =E2=80=99m interested in, and that=E2=80=99s the enhanced Lumetri Color eff= ect.  The enhanced Puppet Tool may come in handy at some point.  = Otherwise, meh.

I use Pr as much as Ae.  If I want = to use Dynamic Link, I have to use the same versions.  IOW, I can=E2= =80=99t use Ae 2018 with Pr 2019, and expect DL to work.  I can=E2=80= =99t even copy clips in Pr and paste them in Ae if the versions don=E2=80= =99t match.

I made a mistake by testing Pr 2019 fo= r one =E2=80=9Csmall=E2=80=9D project for one client for whom I=E2=80=99d d= one about ten videos in Pr 2018.  It worked OK, but there are still so= me bugs that make me reluctant to commit to all of CC 2019.  Honestly,= I can=E2=80=99t remember what they were other than Pr taking an extremely = long time to launch before getting to the Open dialog.

=
So, I got a new project that requires me to use footage from my previo= us ten projects.  I started it in Pr 2018.  Everything was fine e= xcept when I needed to access footage in that Pr 2019 project.  Not a = show stopper.  I just had to launch the Pr 2019 project, and do an XML= export of my master Sequence and b-roll and interview select Sequences, an= d then import that into Pr 2018, losing all the animated masking I did in P= r 2019 (quite a bit).  I was pleased to see some of my Lumetri Color e= ffects were retained.  

I wish Adobe would fi= gure out how to Save As... a previous version in Pr as they have for Ae, or= allow us to import Sequences from a later version of Pr, or use Dynamic Li= nk between different versions.  Alas.

Anyway= =E2=80=A6 I=E2=80=99m posting to ask if anybody else has committed to CC 20= 19 and having good success with both Pr and Ae.  If you=E2=80=99re exp= eriencing issues, what are they?  Are there workarounds?  
<= div>
My biggest fear is encountering a job-killing bug that w= ill inhibit timely delivery of a paying project (see link below). 

I=E2=80=99m on Mac High Sierra with a Nvidia Titan GP= U.

Jim C.


Posts like th= is aren=E2=80=99t encouraging:


--
<= div dir=3D"ltr">
=0A
------=_NextPart_19537063.864808101927--