hello all,

-this is cross posted @ kineme forums, apologies, but i don't know the
overlap between that community and this mailer. -

i am trying to using midi data to smoothly rotate a image on a billboard in
a loop once every x bars. qc is receiving midi data via iac bus from
ableton.

using a linear cc curve which climbs from 0-1 (x360) over the length of the
bar (s) should do it, but when i watch this number as a string i see the
frequency at which qc is reading this number is not high enough to capture
the rotation at full resolution, therefore the image moves in choppy
fashion.

this same lack of sufficient resolution results in qc being unable to make a
stable calculation of bpm using the two bpm calculator patches others have
built. so i can't use the midi clock receiver and/or either of those bpm
calculators to generate a non-choppy interpolation 0 - 360 using the
interpolation patch with external timebase or other calculation techniques
I'm familiar with.

is there any other way to do this? some other calculation method? some way
to stabilize the calculation of bmp? anything? for all other modulations
this lack of smoothness is not an issue for me, but i really need
interpolation to be smooth for continuous rotation.

anyone?

thanks a bunch

r.





On Sat, May 30, 2009 at 3:07 AM, <[email protected]
> wrote:

> Send Quartzcomposer-dev mailing list submissions to
>        [email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        http://lists.apple.com/mailman/listinfo/quartzcomposer-dev
> or, via email, send a message with subject or body 'help' to
>        [email protected]
>
> You can reach the person managing the list at
>        [email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Quartzcomposer-dev digest..."
>
>
> Today's Topics:
>
>   1. javascript crash (Christopher Wright)
>   2. Re: javascript crash (Dan Winckler)
>   3. Implicit animations of inputs?  (Chase Meadors)
>   4. Re: Implicit animations of inputs?  (Chris Wood)
>   5. Changing Camera Field of View? (Karl Channell)
>   6. Re: Changing Camera Field of View? (Christopher Wright)
>   7. Re: Changing Camera Field of View? (George Toledo)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 28 May 2009 15:29:53 -0400
> From: Christopher Wright <[email protected]>
> Subject: javascript crash
> To: quartzcomposer-dev list list <[email protected]>
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="us-ascii"
>
> Skipped content of type multipart/mixed-------------- next part
> --------------
> A non-text attachment was scrubbed...
> Name: smime.p7s
> Type: application/pkcs7-signature
> Size: 2419 bytes
> Desc: not available
> Url :
> http://lists.apple.com/pipermail/quartzcomposer-dev/attachments/20090528/e46637f4/smime.bin
>
> ------------------------------
>
> Message: 2
> Date: Thu, 28 May 2009 16:11:32 -0400
> From: Dan Winckler <[email protected]>
> Subject: Re: javascript crash
> To: quartzcomposer-dev list list <[email protected]>
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
>
> Reproduced it here with the same sort of backtraces.  Here's the
> beginning of a couple of crash reports.
>
> dan
>
> Process:         Quartz Composer [5176]
> Path:            /Developer/Applications/Quartz Composer.app/Contents/
> MacOS/Quartz Composer
> Identifier:      com.apple.QuartzComposer.editor
> Version:         3.1 (63.2)
> Build Info:      QuartzComposerEditor-630200~2
> Code Type:       X86 (Native)
> Parent Process:  launchd [230]
>
> Interval Since Last Report:          301802 sec
> Crashes Since Last Report:           4
> Per-App Interval Since Last Report:  24950 sec
> Per-App Crashes Since Last Report:   1
>
> Date/Time:       2009-05-28 16:04:51.665 -0400
> OS Version:      Mac OS X 10.5.7 (9J61)
> Report Version:  6
> Anonymous UUID:  29545AC5-AE33-48B6-81D2-E487CAC3FAFA
>
> Exception Type:  EXC_BAD_ACCESS (SIGBUS)
> Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
> Crashed Thread:  0
>
> Thread 0 Crashed:
> 0   ???                                 0000000000 0 + 0
> 1   ???                                 0x010bb625 0 + 17544741
>
> ****and****
>
> Process:         Quartz Composer [5207]
> Path:            /Developer/Applications/Quartz Composer.app/Contents/
> MacOS/Quartz Composer
> Identifier:      com.apple.QuartzComposer.editor
> Version:         3.1 (63.2)
> Build Info:      QuartzComposerEditor-630200~2
> Code Type:       X86 (Native)
> Parent Process:  launchd [230]
>
> Interval Since Last Report:          59 sec
> Crashes Since Last Report:           1
> Per-App Interval Since Last Report:  32 sec
> Per-App Crashes Since Last Report:   1
>
> Date/Time:       2009-05-28 16:07:27.073 -0400
> OS Version:      Mac OS X 10.5.7 (9J61)
> Report Version:  6
> Anonymous UUID:  29545AC5-AE33-48B6-81D2-E487CAC3FAFA
>
> Exception Type:  EXC_BAD_ACCESS (SIGBUS)
> Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000010
> Crashed Thread:  0
>
> Thread 0 Crashed:
> 0   com.apple.JavaScriptCore            0x9288e764 JSObjectCallAsFunction +
> 260
> 1   libobjc.A.dylib                     0x965e7800 0x965a6000 + 268288
>
>
>
>
>
> On May 28, 2009, at 3:29 PM, Christopher Wright wrote:
>
> > Granted, this is an unspeakably bad thing to do in javascript, but
> > starting/stopping this composition multiple times will cause QC to
> > crash.
> >
> > <badJS.qtz>
> >
> >
> > Steps:
> >   * load the composition
> >   * open the viewer
> >   * cmd-., cmd-r repeatedly (sometimes it only takes a couple
> > cycles, sometimes more than a dozen).
> >
> > The pertinent script is:
> >
> > var rand = Math.random();
> > Log("rand:"+rand);
> > if(rand > 0.5)
> > {
> >       eval("\
> >       function doStuff(){return 42;}\
> >       function (__number outputNumber) main (__number inputNumber[2])\
> >       {\
> >               var result = new Object();\
> >               result.outputNumber = doStuff();\
> >               return result;\
> >       }");
> > }
> > else
> > {
> >       eval("function (__number cool) main (__number what)\
> >       {\
> >               var result = new Object();\
> >               result.outputNumber = 24;\
> >               return result;\
> >       }");
> > }
> >
> > (Yes, you'd never have a reason ever to do anything like this in
> > real life that I can think of, but crashing might be a problem)
> >
> > backtrace varies, either calling a null function (top address is
> > 0x00000000), or sometimes JSObjectCallAsFunction, as in:
> > Thread 0 Crashed:
> > 0   com.apple.JavaScriptCore            0x95bfd764
> > JSObjectCallAsFunction + 260
> > 1   libobjc.A.dylib                     0x9247d800 0x9243c000 + 268288
> >
> > Can anyone else reproduce this?
> >
> > --
> > [ christopher wright ]
> > [email protected]
> > http://kineme.net/
> >
> > _______________________________________________
> > Do not post admin requests to the list. They will be ignored.
> > Quartzcomposer-dev mailing list      ([email protected]
> > )
> > Help/Unsubscribe/Update your Subscription:
> >
> http://lists.apple.com/mailman/options/quartzcomposer-dev/dan%40danwinckler.com
> >
> > This email sent to [email protected]
>
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 29 May 2009 00:03:52 -0500
> From: Chase Meadors <[email protected]>
> Subject: Implicit animations of inputs?
> To: [email protected]
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
>
> I've been beating my head today trying to find a way to accomplish
> this seemingly simple task in QC. Is there some way, either in QC or
> programatically, to implicitly animate a published input, similar to
> core animation? For example, I want a circular area of my composition
> to be able to expand and contract on command. Not a repetitive
> animation. Long story short, after some googling, my solution involves
> a large web of interpolation patches and stop watches. And it's still
> not working right. Can anybody point me in the right direction?
>
>
> ------------------------------
>
> Message: 4
> Date: Fri, 29 May 2009 09:29:12 +0100
> From: Chris Wood <[email protected]>
> Subject: Re: Implicit animations of inputs?
> To: Chase Meadors <[email protected]>
> Cc: [email protected]
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
>
> It's a little difficult to tell without knowing exactly what you're
> after, but with a few assumptions:
> - You're animating some input value, say the strength value of the
> bump filter
> - You don't want just plain on/off, but a nice transition between the
> two states
> - Your input is plain on/off
>
> If that's roughly right, an easy way to handle it would be:
> - Connect your input to a Smooth patch. You can set the duration, ease
> in/out etc. in that
> - Adjust the output of that with a math expression patch so it matches
> the range of values you need
> - Connect that to the bump patch
>
> That will give you a smooth transition when the input changes. If
> you're after more complex animation or animating multiple things, you
> can use a timeline patch to set up the animation sequence, set the
> timebase to external, and use the output of the smooth patch as the
> time signal. Then your animation will play forwards when the input
> turns on, and backwards when it turns off.
>
> Chris
>
>
>
> On 29 May 2009, at 06:03, Chase Meadors wrote:
>
> > I've been beating my head today trying to find a way to accomplish
> > this seemingly simple task in QC. Is there some way, either in QC or
> > programatically, to implicitly animate a published input, similar to
> > core animation? For example, I want a circular area of my
> > composition to be able to expand and contract on command. Not a
> > repetitive animation. Long story short, after some googling, my
> > solution involves a large web of interpolation patches and stop
> > watches. And it's still not working right. Can anybody point me in
> > the right direction?
> > _______________________________________________
> > Do not post admin requests to the list. They will be ignored.
> > Quartzcomposer-dev mailing list      ([email protected]
> > )
> > Help/Unsubscribe/Update your Subscription:
> >
> http://lists.apple.com/mailman/options/quartzcomposer-dev/psonice%40gmail.com
> >
> > This email sent to [email protected]
>
>
>
> ------------------------------
>
> Message: 5
> Date: Fri, 29 May 2009 09:45:13 -0700
> From: Karl Channell <[email protected]>
> Subject: Changing Camera Field of View?
> To: [email protected]
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="utf-8"
>
> Anyone know the best technique for altering the field of view in QC?
> Any tips or tricks to achieving an orthographic projection space.
>
>
> Thanks,
>
> Karl
>
>
> _______________________________________________________________
>
> Karl Channell |  Interactive Developer | 571.276.6903 | [email protected]
> om
>
>
>
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.apple.com/pipermail/quartzcomposer-dev/attachments/20090529/53a8e3ce/attachment.html
>
> ------------------------------
>
> Message: 6
> Date: Fri, 29 May 2009 12:55:57 -0400
> From: Christopher Wright <[email protected]>
> Subject: Re: Changing Camera Field of View?
> To: Karl Channell <[email protected]>
> Cc: [email protected]
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="us-ascii"
>
> > Anyone know the best technique for altering the field of view in QC?
> > Any tips or tricks to achieving an orthographic projection space.
>
>
> There's a private patch for FoV (hold option while opening
> Preferences, under (System) select "QCShowPrivatePatches"), but I'm
> not certain how it works (I've only toyed with it briefly).
>
> For Orthographic projection, you either have to write a custom GLSL
> shader, a custom QC plugin, or use our GLTools plugin (which has an
> Ortho patch, along with an alternative FoV patch, among a zillion
> other little things).
>
> --
> [ christopher wright ]
> [email protected]
> http://kineme.net/
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: smime.p7s
> Type: application/pkcs7-signature
> Size: 2419 bytes
> Desc: not available
> Url :
> http://lists.apple.com/pipermail/quartzcomposer-dev/attachments/20090529/ad42c84d/smime.bin
>
> ------------------------------
>
> Message: 7
> Date: Fri, 29 May 2009 14:33:40 -0400
> From: George Toledo <[email protected]>
> Subject: Re: Changing Camera Field of View?
> To: Christopher Wright <[email protected]>
> Cc: [email protected]
> Message-ID:
>        <[email protected]>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I strongly recommend Chris's GL Tools. The viewpoint stuff, like the FOV
> and
> the Ortho are totally indispensable. I use these constantly, and they are
> highly reliable. GL Tools is, in my opinion, the second thing that everyone
> working with QC should look at after unhiding the "hidden" patches.
> -George Toledo
>
> On Fri, May 29, 2009 at 12:55 PM, Christopher Wright <[email protected]
> >wrote:
>
> > Anyone know the best technique for altering the field of view in QC? Any
> >> tips or tricks to achieving an orthographic projection space.
> >>
> >
> >
> > There's a private patch for FoV (hold option while opening Preferences,
> > under (System) select "QCShowPrivatePatches"), but I'm not certain how it
> > works (I've only toyed with it briefly).
> >
> > For Orthographic projection, you either have to write a custom GLSL
> shader,
> > a custom QC plugin, or use our GLTools plugin (which has an Ortho patch,
> > along with an alternative FoV patch, among a zillion other little
> things).
> >
> > --
> > [ christopher wright ]
> > [email protected]
> > http://kineme.net/
> >
> >
> >  _______________________________________________
> > Do not post admin requests to the list. They will be ignored.
> > Quartzcomposer-dev mailing list      ([email protected]
> )
> > Help/Unsubscribe/Update your Subscription:
> >
> >
> http://lists.apple.com/mailman/options/quartzcomposer-dev/gtoledo3%40gmail.com
> >
> > This email sent to [email protected]
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.apple.com/pipermail/quartzcomposer-dev/attachments/20090529/b95cf699/attachment.html
>
> ------------------------------
>
> _______________________________________________
> Quartzcomposer-dev mailing list
> [email protected]
> http://lists.apple.com/mailman/listinfo/quartzcomposer-dev
>
>
> End of Quartzcomposer-dev Digest, Vol 51, Issue 18
> **************************************************
>
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to