The only time I've had the fans crank up on the MBP in any app is for comps in
the QC Editor. I'm talking about comps running at n/a FPS with a handful of
patches when there's nothing new to evaluate?!
I haven't run any games or GPU intensive apps but that is crazy, I've tried
turning GPU switcher on and off — no diff.
I've just had three crashes in a row. One was dragging the Editor window 20px
over another was opening a macro and a third hovering over an output port. This
is getting really bad. At least QC reboots in a mere seconds with mostly intact
as compared to the 20 seconds it took on my PPC with last few operations lost
even with Kineme Core Crash recovery saving most changes :-)
Thanks for the pointers on the macro. I'll try creating the virtual patch
through the Library rather than moving the file and look at your other points
now.
The machine does not isolate man from the great problems of nature but plunges
him more deeply into them.
Antoine de Saint-Exupery
On 22/05/2012, at 3:31 PM, George Toledo wrote:
> Try unpublishing all of the inputs on the macro that's listing "input" for
> all of those ports.
>
> The published "name" value is still present in the file even though it's not
> showing at root. Over here, if I unpublish all of those values from root, it
> reverts back to your naming. So, that's one way to get your names back
> potentially.
>
> Right now, for whatever reason through the sequence of events, it's showing
> the "original name" of each port... which is "input" for all of those input
> splitters inside of that macro (save for the font size input, which has it's
> name dictated by the image with string patch).
>
> I did a quick test, and if that "virtual macro" is flattened through the
> standard dialogue, you can get an editable macro with the right port names
> with no shenanigans.
>
> As far as Lion's Editor goes, I don't use it much, but it sure seems like
> I've seen a litany of complaints about it in recent days. I don't think
> you're alone. I noticed some weird lagging with entering values in published
> ports while the Viewer was running, with compositions with about 4 or so
> patches. I suspect there has to be a bug in the editor because of the extreme
> lagginess; hopefully someone might give it a look.
>
> Files seem to run ok in Lion when used as resources outside of the
> QuartzComposer.app, in some cases with some patch bugs from SL seemingly
> solved.
>
> Best regards,
> George Toledo
>
>
>
> On May 22, 2012, at 1:04 AM, Alastair Leith wrote:
>
>> I note the Library has the right click option of Edit Patch… so I tried
>> that. It opened up my screen printing debugger which over time has grown to
>> 3 data inputs and 9 inputs styling/layout options in a new file… select all…
>> copy&paste into current composition… create macro with selected patches… oh
>> dear all the published outputs bar one have been published as "Input" rather
>> than the previous input labels. And they're published to root level not
>> Macro level. Cmd+3 to see published inputs there they all are with correct
>> labels and even editing them they still aren't published as they should be.
>> And what's so special about Font Size input that it's gets the good oil?
>>
>> So it turns out I have to make a new macro; go inside; paste my patch into
>> it (copied from the "Edit Patch…" contextual menu item); come out and the
>> Inputs are now published correctly. Hmmm… room for improvement Apple. Some
>> patches you just always need to re-use and tinker with. Convert Patch to
>> Clip as an editor contextual menu item is definitely a feature request from
>> here.
>>
>> Anecdotally QC 4.6 crashes about ten times more often than QC 3 and from
>> ridiculously minor changes to QC Editor state. A good portion of my crashes
>> are not even from changing the composition state just clicking on a port to
>> preview (number) output?!
>>
>> Alastair I Leith
>> Useful Design
>>
>> <Screen Shot 2012-05-22 at 2.51.44 PM.png>
>>
>> <copy&paste_from_a_library_patch.qtz>
>>
>> The machine does not isolate man from the great problems of nature but
>> plunges him more deeply into them.
>> Antoine de Saint-Exupery
>>
>>
>>
>> On 19/05/2012, at 2:52 AM, Alastair Leith wrote:
>>
>>> I guess Virtual Patches seem more powerful on the face of it to software
>>> engineers being more dynamic than Clips so they trumped Clips (didn't want
>>> to create confusion b/w the two styles of home made patches?). Since I
>>> haven't got into Virtual Patches yet I can say if I prefer them or not but
>>> it seems like a no-brainer that similar to the addition of "Explode Macro…"
>>> QC should have a "Convert Virtual Patch…" or "Embed Virtual Patch…" seeing
>>> as they have to be embedded in the comp as a fall back anyhow.
>>>
>>> If another version of QC ever comes out (be it 4.7 or 5.0), I vote for a
>>> "Convert this Virtual Patch to Macro…" contextual menu item as a
>>> recognition of the importance of ad-hoc changes on the fly to regularly
>>> used Library patches made with QC itself.
>>>
>>> Your plugin sounds interesting, George by all means mail me a sample to
>>> check it out on a 'take it or leave it' basis.
>>>
>>> The machine does not isolate man from the great problems of nature but
>>> plunges him more deeply into them.
>>> Antoine de Saint-Exupery
>>>
>>> On 19/05/2012, at 1:15 AM, George Toledo wrote:
>>>
>>>> You know, on a similar note, I wound up making a plugin not too long ago
>>>> for the purpose of registering qtz files and plugins from an arbitrary
>>>> location. It could pretty easily be edited to allow a user to load qtz's
>>>> into the patch list from their own folder, separate from the Quartz
>>>> Composer Patches stuff, which would be good for the sake of organization.
>>>> If there's any interest in that, I'd consider cleaning that up and
>>>> releasing as time allows.
>>>>
>>>> Doesn't help your desire to flatten per patch, but I'm reminded of the
>>>> issues you were having on Migration, and having to sort Apple stuff from
>>>> personal stuff. You could keep one folder in Documents or something, to
>>>> load personal stuff from, for example.
>>>>
>>>> -gt
>>>>
>>>> On May 18, 2012, at 10:54 AM, Alastair Leith wrote:
>>>>
>>>>> Thanks George. I was hoping to convert on an individual-patch-basis when
>>>>> I determine that I need to make a one-off change to a regularly used
>>>>> Virtual Macro… Guess I have to choose Edit Patch… in Patch Library
>>>>> window's menu and select-all, copy, paste, make macro, rewire noodles
>>>>> from old patch. Or use flatten if that suits the situation.
>>>>>
>>>>> Strange the Release Notes reference to default behaviour ("By default,
>>>>> macros added…") when there doesn't seem to be any other behaviour
>>>>> available. Unless it's a nod to the fact that, as you indicated, Clips
>>>>> can be added to Library. Although I haven't been able to confirm that one.
>>>>>
>>>>> I tried copying my Clips from OLD_HD/Library/Application
>>>>> Support/Apple/Developer Tools/Quartz Composer/Clips to
>>>>> Macintosh HD/Library/Application Support/Apple/Developer Tools/Quartz
>>>>> Composer/Clips (which already had 4 clips that must have been migrated
>>>>> from somewhere the BCM2000 ones (Behringer) but none of these clips are
>>>>> appearing in QC's Library after a reboot of QC… :-\
>>>>>
>>>>>
>>>>> The machine does not isolate man from the great problems of nature but
>>>>> plunges him more deeply into them.
>>>>> Antoine de Saint-Exupery
>>>>>
>>>>> On 18/05/2012, at 11:14 PM, George Toledo wrote:
>>>>>
>>>>>> You flatten the composition.
>>>>>>
>>>>>> You should be able to choose "Option" while looking at the Save menu,
>>>>>> and there should be an option to save a flattened version of the qtz
>>>>>> file. That will make the previously "virtual patches" turn into regular,
>>>>>> editable macros.
>>>>>>
>>>>>> Clips behavior is still active, just not present in the GUI. If you
>>>>>> store your macros in the valid clip folder (can't remember where that is
>>>>>> at the moment), QC will still load the macro into the Patch Library and
>>>>>> let you use it like a clip.
>>>>>>
>>>>>> -gt
>>>>>>
>>>>>> On May 18, 2012, at 9:13 AM, Alastair Leith wrote:
>>>>>>
>>>>>>> In the release notes for QC 4.6:
>>>>>>> A Virtual Macro is a reference to a composition that allows the
>>>>>>> composition to be used in multiple places, requiring only changes to
>>>>>>> the original composition when updates are needed. By default, macros
>>>>>>> added to a composition from the Patch Library are added as Virtual
>>>>>>> Macros.
>>>>>>>
>>>>>>> I can't find anyway to get a 'non-default' behaviour from the Patch
>>>>>>> Library does it exist?
>>>>>>>
>>>>>>> A way to add a Virtual Macro converted to a regular Macro (as clips
>>>>>>> were in QC 3) would be nice. Even better the ability to embed a virtual
>>>>>>> macro already used in the composition as a normal macro that can be
>>>>>>> opened and edited would be great. There's a way to do this, right?
>>>>>>> _______________________________________________
>>>>>>> Do not post admin requests to the list. They will be ignored.
>>>>>>> Quartzcomposer-dev mailing list
>>>>>>> ([email protected])
>>>>>>> Help/Unsubscribe/Update your Subscription:
>>>>>>> https://lists.apple.com/mailman/options/quartzcomposer-dev/gtoledo3%40gmail.com
>>>>>>>
>>>>>>> This email sent to [email protected]
>>>>>>
>>>>>> _______________________________________________
>>>>>> Do not post admin requests to the list. They will be ignored.
>>>>>> Quartzcomposer-dev mailing list ([email protected])
>>>>>> Help/Unsubscribe/Update your Subscription:
>>>>>> https://lists.apple.com/mailman/options/quartzcomposer-dev/usefuldesign.au%40gmail.com
>>>>>>
>>>>>> This email sent to [email protected]
>>>>>
>>>>
>>>> _______________________________________________
>>>> Do not post admin requests to the list. They will be ignored.
>>>> Quartzcomposer-dev mailing list ([email protected])
>>>> Help/Unsubscribe/Update your Subscription:
>>>> https://lists.apple.com/mailman/options/quartzcomposer-dev/usefuldesign.au%40gmail.com
>>>>
>>>> This email sent to [email protected]
>>>
>>> _______________________________________________
>>> Do not post admin requests to the list. They will be ignored.
>>> Quartzcomposer-dev mailing list ([email protected])
>>> Help/Unsubscribe/Update your Subscription:
>>> https://lists.apple.com/mailman/options/quartzcomposer-dev/usefuldesign.au%40gmail.com
>>>
>>> This email sent to [email protected]
>>
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Quartzcomposer-dev mailing list ([email protected])
>> Help/Unsubscribe/Update your Subscription:
>> https://lists.apple.com/mailman/options/quartzcomposer-dev/gtoledo3%40gmail.com
>>
>> This email sent to [email protected]
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Quartzcomposer-dev mailing list ([email protected])
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/quartzcomposer-dev/usefuldesign.au%40gmail.com
>
> This email sent to [email protected]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com
This email sent to [email protected]
