Re: Plugin cached?

[Martin Chatterjee]

Hey Dan, hope you're well!


Well, I usually get the handle on both the Property itself and the Layout
and then pass those to my method:

*oProp = PPG.Inspected[0]*
*oLayout = PPG.PPGLayout*
*buildPPGLayout(oProp, oLayout)*

The other thing I noticed is that your itemsComboArray initialisation has
been missing the corresponding integer values, it should be something like
this:

*itemsComboArray = ["ItemA", 0, "ItemB", 1, "ItemC", 2]*


Here's a pastebin link to a version that's working on my side:
http://pastebin.com/CvT5VmE6



Cheers, Martin

--
   Martin Chatterjee

[ Freelance Technical Director ]
[   http://www.chatterjee.de   ]
[ https://vimeo.com/chatterjee ]

On Fri, Dec 11, 2015 at 11:08 AM, Dan Yargici  wrote:

> OK, I'll admit I'm little wet behind the ears when it comes to this sort
> of thing.
>
> Could someone explain why I get a "# NameError: global name 'PPG' is not
> defined" error with this test property.
>
> http://pastebin.com/Z0YYSVbs
>
> Many thanks,
>
> DAN
>
>
> On Fri, Dec 11, 2015 at 12:14 AM, Stephen Blair 
> wrote:
>
>> Plugins are cached (right click one in the Plugin Manager).
>>
>> And there's a cache of PPG layouts.
>>
>> Never had the global PPG not defined problem.
>>
>> On Thu, Dec 10, 2015 at 4:54 PM, Dan Yargici 
>> wrote:
>>
>>> I have been tearing my hear out for hours now while working with a
>>> plugin not knowing if I'm seeing the updates I've been making.
>>>
>>> It's total voodoo.  Sometimes when I reload, all is well, sometimes I'll
>>> break something on purpose to be certain that it's reloading/updating
>>> correctly only to find that it actually isn't and it still works despite
>>> the fact that I broke *hard coded paths*!
>>>
>>> I just thought I'd finally got this thing nailed and then restarted Soft
>>> only to find it was broken again!
>>>
>>> What's puzzling me is that accessing PPG from the plugin seems to be
>>> intermittent (it complains that no global 'PPG' has been defined) and also
>>> sometimes it won't fire the callbacks like OnChanged.
>>>
>>> Anyone else experienced this behaviour?
>>>
>>> Tried on 2013_SP2 and the trial for 2015_SP2, both the same.
>>>
>>> Cheers,
>>>
>>> DAN
>>>
>>
>>
>

Re: Plugin cached?

[Dan Yargici]

Thank you Stephen.

Martin had helped me resolve this off-list and I was about to post the
solution.  That was indeed the issue.

Ended up like this:

def DY_propTest_DefineLayout( in_ctxt ):
return True

def DY_propTest_ComboMode_OnChanged():
oProp = PPG.Inspected[0]
oLayout = PPG.PPGLayout
buildPPGLayout(oProp, oLayout)
return True

def DY_propTest_OnInit( ):
oProp = PPG.Inspected[0]
oLayout = PPG.PPGLayout
buildPPGLayout(oProp, oLayout)

Cheers,

DAN


On Fri, Dec 11, 2015 at 11:12 AM, Stephen Blair 
wrote:

>
> The PPG object is available in callbacks like OnClicked. Like the doc says:
>
> This object can be manipulated within the event handling script code
> associated with a PPGLayout.
>
>
> So, not in DefineLayout.
>
> In DefineLayout, you should get the PPGLayout object and pass that to your
> rebuild function.
>
> On Fri, Dec 11, 2015 at 5:08 AM, Dan Yargici  wrote:
>
>> OK, I'll admit I'm little wet behind the ears when it comes to this sort
>> of thing.
>>
>> Could someone explain why I get a "# NameError: global name 'PPG' is not
>> defined" error with this test property.
>>
>> http://pastebin.com/Z0YYSVbs
>>
>> Many thanks,
>>
>> DAN
>>
>>
>> On Fri, Dec 11, 2015 at 12:14 AM, Stephen Blair 
>> wrote:
>>
>>> Plugins are cached (right click one in the Plugin Manager).
>>>
>>> And there's a cache of PPG layouts.
>>>
>>> Never had the global PPG not defined problem.
>>>
>>> On Thu, Dec 10, 2015 at 4:54 PM, Dan Yargici 
>>> wrote:
>>>
 I have been tearing my hear out for hours now while working with a
 plugin not knowing if I'm seeing the updates I've been making.

 It's total voodoo.  Sometimes when I reload, all is well, sometimes
 I'll break something on purpose to be certain that it's reloading/updating
 correctly only to find that it actually isn't and it still works despite
 the fact that I broke *hard coded paths*!

 I just thought I'd finally got this thing nailed and then restarted
 Soft only to find it was broken again!

 What's puzzling me is that accessing PPG from the plugin seems to be
 intermittent (it complains that no global 'PPG' has been defined) and also
 sometimes it won't fire the callbacks like OnChanged.

 Anyone else experienced this behaviour?

 Tried on 2013_SP2 and the trial for 2015_SP2, both the same.

 Cheers,

 DAN

>>>
>>>
>>
>

Re: Plugin cached?

[Stephen Blair]

The PPG object is available in callbacks like OnClicked. Like the doc says:

This object can be manipulated within the event handling script code
associated with a PPGLayout.


So, not in DefineLayout.

In DefineLayout, you should get the PPGLayout object and pass that to your
rebuild function.

On Fri, Dec 11, 2015 at 5:08 AM, Dan Yargici  wrote:

> OK, I'll admit I'm little wet behind the ears when it comes to this sort
> of thing.
>
> Could someone explain why I get a "# NameError: global name 'PPG' is not
> defined" error with this test property.
>
> http://pastebin.com/Z0YYSVbs
>
> Many thanks,
>
> DAN
>
>
> On Fri, Dec 11, 2015 at 12:14 AM, Stephen Blair 
> wrote:
>
>> Plugins are cached (right click one in the Plugin Manager).
>>
>> And there's a cache of PPG layouts.
>>
>> Never had the global PPG not defined problem.
>>
>> On Thu, Dec 10, 2015 at 4:54 PM, Dan Yargici 
>> wrote:
>>
>>> I have been tearing my hear out for hours now while working with a
>>> plugin not knowing if I'm seeing the updates I've been making.
>>>
>>> It's total voodoo.  Sometimes when I reload, all is well, sometimes I'll
>>> break something on purpose to be certain that it's reloading/updating
>>> correctly only to find that it actually isn't and it still works despite
>>> the fact that I broke *hard coded paths*!
>>>
>>> I just thought I'd finally got this thing nailed and then restarted Soft
>>> only to find it was broken again!
>>>
>>> What's puzzling me is that accessing PPG from the plugin seems to be
>>> intermittent (it complains that no global 'PPG' has been defined) and also
>>> sometimes it won't fire the callbacks like OnChanged.
>>>
>>> Anyone else experienced this behaviour?
>>>
>>> Tried on 2013_SP2 and the trial for 2015_SP2, both the same.
>>>
>>> Cheers,
>>>
>>> DAN
>>>
>>
>>
>

Re: Plugin cached?

[Dan Yargici]

OK, I'll admit I'm little wet behind the ears when it comes to this sort of
thing.

Could someone explain why I get a "# NameError: global name 'PPG' is not
defined" error with this test property.

http://pastebin.com/Z0YYSVbs

Many thanks,

DAN


On Fri, Dec 11, 2015 at 12:14 AM, Stephen Blair 
wrote:

> Plugins are cached (right click one in the Plugin Manager).
>
> And there's a cache of PPG layouts.
>
> Never had the global PPG not defined problem.
>
> On Thu, Dec 10, 2015 at 4:54 PM, Dan Yargici  wrote:
>
>> I have been tearing my hear out for hours now while working with a plugin
>> not knowing if I'm seeing the updates I've been making.
>>
>> It's total voodoo.  Sometimes when I reload, all is well, sometimes I'll
>> break something on purpose to be certain that it's reloading/updating
>> correctly only to find that it actually isn't and it still works despite
>> the fact that I broke *hard coded paths*!
>>
>> I just thought I'd finally got this thing nailed and then restarted Soft
>> only to find it was broken again!
>>
>> What's puzzling me is that accessing PPG from the plugin seems to be
>> intermittent (it complains that no global 'PPG' has been defined) and also
>> sometimes it won't fire the callbacks like OnChanged.
>>
>> Anyone else experienced this behaviour?
>>
>> Tried on 2013_SP2 and the trial for 2015_SP2, both the same.
>>
>> Cheers,
>>
>> DAN
>>
>
>

Re: Color shift w/ QuickTime

[Sebastien Sterling]

Time for H.265 !

On 11 December 2015 at 09:29, christian  wrote:

> what codec are you using though ? the quicktime h.264 i assume which is
> horrible with gamma and colors.
>
> we usually use not the quicktime > h.264 one but the one just labeled
> h.264. file ending should then end up .mp4 by default, not .mov.
> then just rename afterwards and things look better.
>
> mileage may vary of course, its all a big mumbo jumbo. willing to bet your
> movie also looks ok in VLC and similiar players.
>
> c.
>
> On Fri, Dec 11, 2015 at 3:08 AM, John Clausing 
> wrote:
>
>> I tried that (I'm on a Mac), but I'll give it another shot with those
>> instructions..
>>
>> There's are two "alpha" settings, one white, one black.any difference
>> do you know?
>>
>> Thanks for the help
>>
>> J
>>
>> Sent from my iPhone
>>
>> On Dec 10, 2015, at 8:07 PM, Mirko Jankovic 
>> wrote:
>>
>> Just for comparison, up is image before the trick, down after that
>>  procedure.
>> [image: Inline image 1]
>>
>> On Fri, Dec 11, 2015 at 2:04 AM, Mirko Jankovic <
>> mirkoj.anima...@gmail.com> wrote:
>>
>>> Try this trick:
>>>
>>> - Open up movie in QT
>>> - Window -> movie properties
>>> - select video track (don't turn it off on checkbox just select)
>>> - Down in transparency from drop down menu select Blend and then pull
>>> transparency level to 100%. Image should loko like whitish and washed out
>>> - then back to dropdown menu and select Alpha
>>> - and finaly press play.
>>>
>>> Colors should be  back to normal now and then just exit QT and accept
>>> save.
>>> Let me know if that did the trick
>>>
>>> On Fri, Dec 11, 2015 at 1:45 AM, John Clausing 
>>> wrote:
>>>
 Hey all

 We're making a sequence in 3D that's lit and rendered fine, (Arnold ,
 exr), composited in Nuke, and rendered from Nuke as 8 bit . Tiffs..then
 brought into After Effects to edit and make a QT, for Facebook.

 Up until the QT is made, the color is just right, upon viewing the QT,
 the gamma is off and looks less saturated and dull.

 If I bring the QT back into AE or Nuke it is fine

 Clearly this is a QT viewer issue long known, but the client doesn't
 like it and insists on QTs for its FB postings

 Any thoughts? We've tried every color adjustment we can think of from
 QT Pro, media encoder and various color settings in Project Settings in AE

 Thoughts? Thanks,

 John

 Sent from my iPhone

>>>
>>>
>>
>

Friday Flashback #253

[Stephen Blair]

>From the pile of old graphic elements: a Sumatra banner (circa 07 April
1999)
http://wp.me/powV4-3fL

Re: Color shift w/ QuickTime

[Nono]

Hello, here we usually don't conform media with an adobe product, the
quality is horrible.
The keep the gamma right from top to bottom first, use a proper codec, the
"x264" encoder.

This codec is 100% compatible and used by every "Linux" server, YouTube /
Vimeo / also The codec behind nuke h264 etc...

So in short, output a QuickTime animation or an uncompressed file format
and use:

-"Handbrake" this is the best tool ! free, osx, windows, Linux, perfect
quality.
-"ffmpeg" the best command line convert tool
-or any x264 based encoder like VLC

Cheers

Nono


Le ven. 11 déc. 2015 à 14:38, Sebastien Sterling <
sebastien.sterl...@gmail.com> a écrit :

> Time for H.265 !
>
> On 11 December 2015 at 09:29, christian  wrote:
>
>> what codec are you using though ? the quicktime h.264 i assume which is
>> horrible with gamma and colors.
>>
>> we usually use not the quicktime > h.264 one but the one just labeled
>> h.264. file ending should then end up .mp4 by default, not .mov.
>> then just rename afterwards and things look better.
>>
>> mileage may vary of course, its all a big mumbo jumbo. willing to bet
>> your movie also looks ok in VLC and similiar players.
>>
>> c.
>>
>> On Fri, Dec 11, 2015 at 3:08 AM, John Clausing 
>> wrote:
>>
>>> I tried that (I'm on a Mac), but I'll give it another shot with those
>>> instructions..
>>>
>>> There's are two "alpha" settings, one white, one black.any
>>> difference do you know?
>>>
>>> Thanks for the help
>>>
>>> J
>>>
>>> Sent from my iPhone
>>>
>>> On Dec 10, 2015, at 8:07 PM, Mirko Jankovic 
>>> wrote:
>>>
>>> Just for comparison, up is image before the trick, down after that
>>>  procedure.
>>> [image: Inline image 1]
>>>
>>> On Fri, Dec 11, 2015 at 2:04 AM, Mirko Jankovic <
>>> mirkoj.anima...@gmail.com> wrote:
>>>
 Try this trick:

 - Open up movie in QT
 - Window -> movie properties
 - select video track (don't turn it off on checkbox just select)
 - Down in transparency from drop down menu select Blend and then pull
 transparency level to 100%. Image should loko like whitish and washed out
 - then back to dropdown menu and select Alpha
 - and finaly press play.

 Colors should be  back to normal now and then just exit QT and accept
 save.
 Let me know if that did the trick

 On Fri, Dec 11, 2015 at 1:45 AM, John Clausing 
 wrote:

> Hey all
>
> We're making a sequence in 3D that's lit and rendered fine, (Arnold ,
> exr), composited in Nuke, and rendered from Nuke as 8 bit . 
> Tiffs..then
> brought into After Effects to edit and make a QT, for Facebook.
>
> Up until the QT is made, the color is just right, upon viewing the QT,
> the gamma is off and looks less saturated and dull.
>
> If I bring the QT back into AE or Nuke it is fine
>
> Clearly this is a QT viewer issue long known, but the client doesn't
> like it and insists on QTs for its FB postings
>
> Any thoughts? We've tried every color adjustment we can think of from
> QT Pro, media encoder and various color settings in Project Settings in AE
>
> Thoughts? Thanks,
>
> John
>
> Sent from my iPhone
>


>>>
>>
>