From: "Jim Curtis" Received: from sonic305-9.consmr.mail.bf2.yahoo.com ([74.6.133.48] verified) by media-motion.tv (CommuniGate Pro SMTP 6.1.0) with ESMTP id 7199494 for AE-List@media-motion.tv; Fri, 30 Nov 2018 19:54:11 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=flash.net; s=s2048; t=1543604849; bh=5M+BTOH7Tz/XS5xR9FvtxxDD5Fe6FARG5JW4rZYEmo4=; h=From:Subject:Date:References:To:In-Reply-To:From:Subject; b=dQLxxsTTVI1AUMfpuWpIb3vS5Yi86gK3OL1nYcyaRP8/OSB0bS+5z5ET8N7OBlm+U3EyOstEy2rlEQbGgAZw2VaP5jrvBDLzpbld/NPKzNG+DcZ9r3Mj6Tq0LeClrswOTUIeUbZc35e3IUWoc3PqvRTDGWv0C5siiT+i/rFLtMgZ8XwO/71VYJT/RyeScBeegNrB2YNWUQoF2bpJZ41a6hPSOURG5ZhVsTbwZiKTtbMlTiSOqsyfeEPrUBEr1Uqxv716Dg7fGecOFYsXYn1bKvSs6WlzvUjOpbIrEIsTCMtSdKsmtET0dCFGcnr1vsYNWheoMpOzFi8RfqCPTtJmGA== X-YMail-OSG: HqkF9nQVM1nXtg3QaZk1evBNhj_FdoYr4t5TXN7gKvZwdJdqOu.DaqOds_UufIP tSHdb3JyFt1.5tMm3qbc40v2_pDmOPssA9Z8xpZnEkJvjQO.6kQjVM86cnmiJykk_uodxk6onV8D h56uV3J.WWBiMOYjYkEpAdFeFTcO_ehZjxh21N_RUxtQVDspXaNPVQwRqZP52e1LvEK3R_3Q.73Q SlwzWcrcJhVMfBiJIl3SMO51zJJxcNt8MEz01N_DW1A75pNoRc1wJ.e3GzstxV964sNplvu7l5E3 yH5.8_4TkBhOgcjZVFjH7sJxGXP6cypskza3plHUrUaO8u9NvWOCeP._HFByS791SJyts_yDRCqq JC__T9M8hBDxwfSTqxV0pc3IBgjSgh93xzp2FfwagTNnFPP54c4ZRS.5IPFcfLub2MvBGY9TAqRo iHVAXCUqiPXjcS56r77LC4G59w8XFGrrMz.NXfrgz7Hud9Y7M3fGqBi4KpZlAJtG1MD3bswJsH5W 5PQbWVcrb4zkYzSZATZaqfvydb15hxk9UY_Z0rfir7mHjQMBz71kXYdEUcfvl9Fhde39sXepjV2j 7Lm4wFU9HZAg0c0CBU3uEonx2G3.fBUkaLMm35.lwia.VKkxfdIHDcuRATDsgCMdG9qrT4hWiRX8 fmoTJP4x5VLy8eNpro5ps3TLkFHxSDX.A62SF01vVmuxtdPtzifrhGaOPj0tqHOIqcNucmrxDA.2 oChA5SSdELr0ftJZ5tVBix6ZMUB61NHlJOhLVVhcWXKc3iJfcADgxnqwlnEn5N8nA5zIRskgACIb Xns5yjkpomOdotNthXuna35kKYZQbFxS87pT08xTeNWvShMIfxc3AOMCMdeHxGcgj790vWQjkVVv Zr8mMKS0Tp8ZlWhnsoEWlvnxA_JhiQzU_HNeiPdft90iTrAinmqNMZIIX1y6uJ5Bk0sk.c3etBGQ HI2E2ur2yKI_sBGS.zZIxdKkpo8iSS7H8.L6aO5cKc68XWU6c3tCawqjX.DC79YWOy1D2AlJNr1M kIua1X8Sovu2ueXVBupBuNLHY8ch99stHeWIpVwWwHu6MEFdw1bx6tRaaw_p8sGNokvhmm1rmNXe NGDh_ZFPJWcQzEw-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic305.consmr.mail.bf2.yahoo.com with HTTP; Fri, 30 Nov 2018 19:07:29 +0000 Received: from 104-48-143-159.lightspeed.rcsntx.sbcglobal.net (EHLO mac-pro.attlocal.net) ([104.48.143.159]) by smtp404.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID f08e0b9c0366ba12e1782b46f2cd6f3b for ; Fri, 30 Nov 2018 19:07:23 +0000 (UTC) Content-Type: multipart/alternative; boundary="Apple-Mail=_12DEC047-4E0A-4D0A-89F1-EF31E60EBE76" Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: [AE] reluctant to commit to CC 2019 Date: Fri, 30 Nov 2018 13:07:21 -0600 References: To: After Effects List In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.3445.9.1) --Apple-Mail=_12DEC047-4E0A-4D0A-89F1-EF31E60EBE76 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Greg, your troubles are exactly the kind of thing I fear - that I=E2=80=99= ll get into a project and everything will be fine=E2=80=A6 until I try = to do something that triggers or discovers a bug for which there=E2=80=99s= no workaround. At least Ae allows us to Save to two prior versions. And now I know about the converter for Pr that Danny mentioned ( = http://www.joshcluderay.com/downgrade-premiere-project-converter/ ), I = feel a little better about being able to bail if I ever get tempted = again.=20 > On Nov 30, 2018, at 11:29 AM, Greg Balint = wrote: >=20 > 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..=20 >=20 > I've started 2 projects now, since it's been out, and I've TRIED to = use 2019 for them.. however little weird things happen that literally = halt all production in 2019. >=20 > 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 constraints to the other = layer. (move it around freely, but when I get to a certain position, the = other layer acts like it's parented and will attach and follow" = 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 = 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) =20 >=20 > 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..=20 >=20 > Sucks, because now I've got 2014, 2018, and 2019 installed all to use = different portions of the programs that are better at different things.. = 2018 being the main work environment, but 2014 being around to wrangle = heavy renders with multi-frame rendering, and 2019 being around to use = the Mocha AE plugin mainly.=20 >=20 > I wish each version didn't introduce these showstopping bugs in the = first year it's around.. It just doesn't give me much faith in new = versions being anything to "flock to" >=20 >=20 > ///Greg Balint > //Art Director / Motion Graphics Designer > /321.514.4839 > delRAZOR.com / >> On 11/30/2018 11:54:53 AM, Ross Shain = wrote: >>=20 >> Hey Jim,=20 >> 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 (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 midnight.=20 >>=20 >> Compare Mocha Pro to Mocha AE: = https://borisfx.com/products/mocha-pro/#compare = >>=20 >> Sale info: = https://borisfx.com/news/black-friday-2018-up-to-50-off-all-products/ = >>=20 >>=20 >> On Fri, 30 Nov 2018 at 11:28, Jim Curtis > wrote: >> Sorry for the long post. If you=E2=80=99re busy, just ignore this. = Part of it is griping. >>=20 >> I wonder how many others here are in the same boat. =20 >>=20 >> My favorite feature of Ae CC 2019, and the ONLY new feature that = interests me is the Mocha 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 effect. The enhanced Puppet Tool may come in = handy at some point. Otherwise, meh. >>=20 >> 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. >>=20 >> 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. It worked OK, but there are still some 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. >>=20 >> So, I got a new project that requires me to use footage from my = previous ten projects. I started it in Pr 2018. Everything was fine = except 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, = and then import that into Pr 2018, losing all the animated masking I did = in Pr 2019 (quite a bit). I was pleased to see some of my Lumetri Color = effects were retained. =20 >>=20 >> 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. Alas. >>=20 >> 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. If = you=E2=80=99re experiencing issues, what are they? Are there = workarounds? =20 >>=20 >> My biggest fear is encountering a job-killing bug that will inhibit = timely delivery of a paying project (see link below).=20 >>=20 >> I=E2=80=99m on Mac High Sierra with a Nvidia Titan GPU. >>=20 >> Jim C. >>=20 >>=20 >> Posts like this aren=E2=80=99t encouraging: >>=20 >> https://forums.adobe.com/thread/2556384 = >>=20 >>=20 >> . >>=20 >>=20 >> --=20 >>=20 >> Ross Shain >> Chief Product Officer: Mocha >> +1.646.298.6458 | borisfx.com >>=20 >>=20 >>=20 >>=20 >>=20 >>=20 >>=20 >>=20 --Apple-Mail=_12DEC047-4E0A-4D0A-89F1-EF31E60EBE76 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Greg,= your troubles are exactly the kind of thing I fear - that I=E2=80=99ll = get into a project and everything will be fine=E2=80=A6 until I try to = do something that triggers or discovers a bug for which there=E2=80=99s = no workaround.

At = least Ae allows us to Save to two prior versions.
And now I know about the converter for = Pr that Danny mentioned ( http://www.joshcluderay.com/downgrade-premiere-project-converte= r/ ), I feel a little better about being able to bail if I ever get = tempted again. 




On Nov = 30, 2018, at 11:29 AM, Greg Balint <AE-List@media-motion.tv> wrote:

=20 =20 =20 =20 =20 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 2019 for them.. however little weird = things happen that literally halt all production 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 constraints to the other layer. = (move it around freely, but when I get to a certain position, the other = layer acts like it's parented and will attach and follow"   = 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 = 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) =  

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.. 

Sucks, because now I've got = 2014, 2018, and 2019 installed all to use different portions of the = programs that are better at different things.. 2018 being the main work = environment, but 2014 being around to wrangle heavy renders with = multi-frame rendering, and 2019 being around to use the Mocha AE plugin = mainly. 

I wish each = version didn't introduce these showstopping bugs in the first year 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/
=20

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

Hey Jim, 
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 (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 = midnight. 

Compare Mocha Pro to Mocha AE: https://borisfx.com/products/mocha-pro/#compare

Sale info: https://borisfx.com/news/black-friday-2018-up-to-50-off-all-pro= ducts/

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 busy, just = ignore this.  Part of it is griping.

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

My favorite feature of Ae CC 2019, = and the ONLY new feature that interests me is the Mocha 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 = effect.  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 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.  = It worked OK, but there are still some 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 previous ten projects.  I started it in Pr 2018.  = Everything was fine except 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, and then import that into Pr 2018, = losing all the animated masking I did in Pr 2019 (quite a bit).  I = was pleased to see some of my Lumetri Color effects were retained. =  

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.  = 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.  If you=E2=80=99re = experiencing issues, what are they?  Are there workarounds? =  

My = biggest fear is encountering a job-killing bug that will inhibit timely = delivery of a paying project (see link below). 

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


.


--

Ross = Shain
Chief Product Officer: Mocha
+1.646.298.6458 | borisfx.com









= --Apple-Mail=_12DEC047-4E0A-4D0A-89F1-EF31E60EBE76--