Return-Path: Received: from [208.97.132.66] (HELO homiemail-a23.g.dreamhost.com) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP id 4820166 for AE-List@media-motion.tv; Tue, 21 Aug 2012 22:51:35 +0200 Received: from homiemail-a23.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a23.g.dreamhost.com (Postfix) with ESMTP id E3B7D4B0063 for ; Tue, 21 Aug 2012 13:52:08 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; c=nofws; d=aescripts.com; h=mime-version :in-reply-to:references:from:date:message-id:subject:to: content-type; q=dns; s=aescripts.com; b=atwioeRGOSgfpifN66knDeni uSIG5AB2OllDZS0idr+URXCgbCB0vIPsWZLsWmX9YwcKvCP9Fl3SQDe8nylgGsaL CnQoMwCxHw4ziu027nxvExD2SX6dHrqfL0nG+rxl6p94q7QhsW8Pd36r6ezMsTYp 2SDP1h8q16EbcEQjJ+Y= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=aescripts.com; h= mime-version:in-reply-to:references:from:date:message-id:subject :to:content-type; s=aescripts.com; bh=7sZ0dcRTjtxlRgHWIbUBZn9Do3 w=; b=scocpL5DLI7utE+zBWqM19oBZ6g4SqAF+gourxgbpZkfIMyY+Fk01xN9pl 9A1X7iSIpFmCNMZCXzh+WTI5pLKFwbssRfs5NZVuPZRib9zOPqx6G9eOhorxgbg/ BPTm4nmXMC54RIjpufllJN5lkUuQ8Y7TOtkWZ4yJLWOSjCefs= Received: from mail-pb0-f41.google.com (mail-pb0-f41.google.com [209.85.160.41]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: lists@aescripts.com) by homiemail-a23.g.dreamhost.com (Postfix) with ESMTPSA id B31A44B0062 for ; Tue, 21 Aug 2012 13:52:08 -0700 (PDT) Received: by pbbro12 with SMTP id ro12so412735pbb.28 for ; Tue, 21 Aug 2012 13:52:08 -0700 (PDT) Received: by 10.66.89.234 with SMTP id br10mr40885459pab.25.1345582328294; Tue, 21 Aug 2012 13:52:08 -0700 (PDT) MIME-Version: 1.0 Received: by 10.66.157.129 with HTTP; Tue, 21 Aug 2012 13:51:27 -0700 (PDT) In-Reply-To: References: From: Lloyd Alvarez Date: Tue, 21 Aug 2012 16:51:27 -0400 Message-ID: Subject: Re: [AE] [Semi-OT] Welcome to The Aescripts + Aeplugins Playground To: After Effects Mail List Content-Type: multipart/alternative; boundary=f46d042dfbcdb1aee204c7cccc9a --f46d042dfbcdb1aee204c7cccc9a Content-Type: text/plain; charset=ISO-8859-1 Indeed! Not only is Ariel incredibly talented but he is by far one of the nicest guys i've ever worked with. If anyone wants to hire him he is highly recommended by me! And glad you guys like the piece! :-) -Lloyd On Tue, Aug 21, 2012 at 3:58 PM, Greg Balint wrote: > Holy Schnikeez.. this is an awesome piece by Ariel Costa / Blinkmybrain > > https://vimeo.com/47684693 > > Lloyd?, you picked a winner with this guy.. Geez that's fun to watch and > very well designed. Very inspiring. > > > > ///Greg Balint > //Art Director / Motion Graphics Designer > /321.514.4839 > delRAZOR.com/ > > On 8/21/2012 3:39 PM, Byron Nash wrote: > > I'm with Robert, I don't get the Match Source on anything but what he > listed. This is for both Mac & Windows. > > On Tue, Aug 21, 2012 at 2:39 PM, Glen Tubbesing wrote: > >> Just a heads up for everyone. Make sure you put that extra 'u' in studio >> in Robert's link. I didn't the first time and got a 404 error. >> >> Glen Tubbesing >> Caples Productions >> Las Vegas, NV >> >> >> On Tue, Aug 21, 2012 at 10:03 AM, Robert Kjettrup wrote: >> >>> that sounds weird... >>> >>> Am i overlooking something really simple here that i have wanted in >>> AME all these years? >>> Are you seeing "match source" as an option for all quicktime codecs when >>> entering the "export settings" dialog box? >>> Is there really a difference in the win and mac versions of AME? >>> >>> I use FFMPEG and "Another GUI" as a frontend to generate Prores files, >>> and it seems to work ok, no FCP user i have delivered to has complained yet >>> :-) >>> It doesn't make Prores output possible through any regular programs you >>> have to do this extra step to convert the files, maybe Adobe could include >>> FFMPEG as an encoder engine in AME someday :-) >>> Only problem with this workflow is i can't get ffmpeg to encode excact >>> colors in the Prores if my input file is a YUV file, it only seems to work >>> 100% correct with RGB encoded input files, but maybe there is some obscure >>> ffmpeg setting that i can't figure out how to use. >>> Heres a link to any windows user who doesn't know this small program: >>> http://www.stuudio.ee/anothergui/ >>> >>> >>> >>> Robert Kjettrup / Grafiker / STV Mayday >>> Mobil: 25 18 95 16 >>> Mail: robert@stvmayday.dk >>> >>> >>> 2012/8/21 Jim Curtis >>> >>>> That you're on Windows may explain it. >>>> >>>> I have read of a method to encode to ProRes on Windows, but it >>>> requires a third-party app, and some hoop-jumping, IIRC. So, I presume >>>> even with this software installed, you wouldn't see ProRes as an export >>>> option in AME, Ae or Pr. >>>> >>>> What about AVI? Isn't that available as a Match Source option? >>>> >>>> I just tried Avid Meridian Compressed, as an experiment, as a Preview >>>> option, and Match Settings works for Export there, too. >>>> >>>> I'm on Mac, BTW. >>>> >>>> >>>> >>>> On Aug 21, 2012, at 10:54 AM, Robert Kjettrup wrote: >>>> >>>> hmmmm.... >>>> >>>> i just checked here again.... i only get the "Automatic (based on >>>> source)" option on the different properties on the following formats: >>>> MPEG2 Blu-ray >>>> MPEG2-DVD >>>> H.264 Blu-ray (Legacy) >>>> FLV >>>> F4V >>>> ...the two last there is only the framerate that you can take from >>>> source, but it automaticly takes the size from source, then you have to >>>> check a box to force it to resize. Another inconsistency in AME. >>>> I am on a windows machine so i don't have access to the Prores encode >>>> presets, but none of my quicktime codecs has the option to use the source >>>> attributes. ? >>>> >>>> >>>> Robert Kjettrup / Grafiker / STV Mayday >>>> Mobil: 25 18 95 16 >>>> Mail: robert@stvmayday.dk >>>> >>>> >>>> 2012/8/21 Jim Curtis >>>> >>>>> Robert, I use ProRes as a Preview format, and Match Source Attributes >>>>> is available to me. >>>>> >>>>> Byron, to your OP, once you change anything, you're not matching >>>>> source attributes any longer. So, there's your answer. >>>>> >>>>> It's easy to make presets. Just pick an export format that contains >>>>> the codec you want, modify anything else, and save it. >>>>> >>>>> Presets sort alphanumerically, so that's something I keep in mind >>>>> when naming them. Putting the most used ones at the top saves a bit of >>>>> time. Consistent naming methods keep everything grouped nicely, and >>>>> minimize my searching for the one I want. >>>>> >>>>> >>>>> >>>>> On Aug 21, 2012, at 10:02 AM, Robert Kjettrup wrote: >>>>> >>>>> Hi >>>>> >>>>> I think it is only mpeg2 that has the "match source attributes" >>>>> setting, which is a shame since it could be nice to have in every format... >>>>> AME could use a good cleanup in making the settings for the different >>>>> formats more alike. Some has bitrate in Kbps others in more useful Mbps, >>>>> some has a framerate setting, some don't. >>>>> And the "Filters"tab should just be removed and replaced with a >>>>> effectpreset independent of the encodesettings, so you could add different >>>>> effects to a clip, like add black leadin/leadout, adjust volume, apply a >>>>> LUT, timecode burnin, etc... >>>>> >>>>> >>>>> Robert Kjettrup / Grafiker / STV Mayday >>>>> Mobil: 25 18 95 16 >>>>> Mail: robert@stvmayday.dk >>>>> >>>>> >>>>> 2012/8/21 Byron Nash >>>>> >>>>>> Sorry for the OT, I haven't been able to find an answer to this and >>>>>> usually assume if this list doesn't know, it's the end of the road. ;-) >>>>>> >>>>>> Some of the presets in Adobe Media Encoder(CS6 here) have "Match >>>>>> Source Attributes" for the size, frame rate, etc.. I would like to make >>>>>> some presets that convert footage to other formats without changing the >>>>>> size and frame rate. I see no way to set values to "Match Source" when >>>>>> making a preset. Looks like I would have to create presets for every size I >>>>>> might run into. Has anyone found a good workaround for this? >>>>>> >>>>>> Thanks, >>>>>> Byron >>>>>> >>>>> >>>>> >>>>> >>>> >>>> >>> >> > > --f46d042dfbcdb1aee204c7cccc9a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Indeed! =A0Not only is Ariel incredibly talented but he is by far one of th= e nicest guys i've ever worked with. =A0If anyone wants to hire him he = is highly recommended by me!

And glad you guys like the = piece! :-)

-Lloyd

On Tue, Aug 21= , 2012 at 3:58 PM, Greg Balint <greg@delrazor.com> wrote:
=20 =20 =20
Holy Schnikeez.. this is an awesome piece by Ariel Costa / Blinkmybrain

https://vime= o.com/47684693

Lloyd?, you picked a winner with this guy.. Geez that's fun to watch and very well designed.=A0 Very inspiring.



///Greg Balint
//Art Director / Motion Graphics Designer
/321.=
514.4839
delRAZOR.com/
On 8/21/2012 3:39 PM, Byron Nash wrote:
I'm with Robert, I don't get the Match Source on anything but what he listed. This is for both Mac & Windows.

On Tue, Aug 21, 2012 at 2:39 PM, Glen Tubbesing <gtubbesing@gmail.com> wrote:
Just a heads up for everyone. =A0Make sure you put that extra 'u' in s= tudio in Robert's link. =A0I didn't the first time and got a 40= 4 error.

Glen Tubbesing
Caples Productions
Las Vegas, NV


On Tue, Aug 21, 2012 at 10:03 AM, Robert Kjettrup <robert@stvmayday.dk> wrote:
that sounds weird...

Am i overlooking something really simple here that i have wanted in AME all these years?=A0
Are you seeing "match source" as an opti= on for all quicktime codecs when entering the "export settings" dialog box?
Is there really a difference in the win and mac versions of AME?

I use FFMPEG and "Another GUI" as a frontend = to generate Prores files, and it seems to work ok, no FCP user i have delivered to has complained yet :-)
It doesn't make Prores output possible through an= y regular programs you have to do this extra step to convert the files, maybe Adobe could include FFMPEG as an encoder engine in AME someday :-)
Only problem with this workflow is i can't get ffmpeg to encode excact colors in the Prores if my input file is a YUV file, it only seems to work 100% correct with RGB encoded input files, but maybe there is some obscure ffmpeg setting that i can't figure out how to use.
Heres a link to any windows user who doesn't know this small program:



Robert Kjettrup / Grafiker / STV Mayday
Mobil: 25 18 95 16
Mail: robert@stvmayday.dk


2012/8/21 Jim Curtis <jpcurtis@me.com>
That you're on Windows may explain it. =A0

I have read of a method to encode to ProRes on Windows, but it requires a third-party app, and some hoop-jumping, IIRC. =A0So, I presume even with this software installed, you wouldn't see ProRes as an expor= t option in AME, Ae or Pr.

What about AVI? =A0Isn't that available as a Match Source option?

I just tried Avid Meridian Compressed, as an experiment, as a Preview option, and Match Settings works for Export there, too.

I'm on Mac, BTW.



On Aug 21, 2012, at 10:54 AM, Robert Kjettrup wrote:
hmmmm..= ..=A0

i just checked here again.... i only get the "Automatic (based on source)" option on the different properties on the following formats:
MPEG2 Blu-ray
MPEG2-DVD
H.264 Blu-ray (Legacy)
FLV
F4V
...the two last there is only the framerate that you can take from source, but it automaticly takes the size from source, then you have to check a box to force it to resize. Another inconsistency in AME.
I am on a windows machine so i don't have access to the Prores encode presets, but none of my quicktime codecs has the option to use the source attributes. ?


Robert Kjettrup / Grafiker / STV Mayday
Mobil: 25 18 95 16
Mail: robert@stvmayday.dk


20= 12/8/21 Jim Curtis <jpcurtis@me.com<= /a>>
Robert, I use ProRes as a Preview format, and Match Source Attributes is available to me.

Byron, to your OP, once you change anything, you're not matching source attributes any longer. =A0So, there's your answer.

It's easy to make presets. =A0Just pick an export format that contains the codec you want, modify anything else, and save it. =A0

Presets sort alphanumerically, so that's something I keep in mind when naming them. =A0Putting the most used ones at the top saves a bit of time. =A0Consistent naming methods keep everything grouped nicely, and minimize my searching for the one I want.



On Aug 21, 2012, at 10:02 AM, Robert Kjettrup wrote:

Hi

I think it is only mpeg2 that has the "match sourc= e attributes" setting, which is a shame since it could be nice to have in every format... AME could use a good cleanup in making the settings for the different formats more alike. Some has bitrate in Kbps others in more useful Mbps, some has a framerate setting, some don't.
And the "Filters&quo= t;tab should just be removed and replaced with a effectpreset independent of the encodesettings, so you could add different effects to a clip, like add black leadin/leadout, adjust volume, apply a LUT, timecode burnin, etc...


Robert Kjettrup / Grafiker / STV Mayday
Mobil: 25 18 95 16
Mail: robert@stvmayday.dk


2012/8/21 Byron Nash <by= ronnash@gmail.com>
Sorry for the OT, I haven't been able to find an answer to this and usually assume if this list doesn't know, it's the end of the road. ;-)

Some of the presets in Adobe Media Encoder(CS6 here) have "Match Sourc= e Attributes" for the size, frame rate, etc.. I would like to make some presets that convert footage to other formats without changing the size and frame rate. I see no way to set values to "Match Source"=A0wh= en making a preset. Looks like I would have to create presets for every size I might run into. Has anyone found a good workaround for this?

Thanks,
Byron









--f46d042dfbcdb1aee204c7cccc9a--