Synapse connection to QC flakey for me... ideas?

[jdjd]

Hello gang! Need a hand please....

Have installed all the synapse setup according to directions.
Can get the:
"01s_bodybuilder sample puppet synapse.qtz"
to work occasionally, (what GREAT FUN!!) but have never gotten any of
the other comps to work (such as: 01_01s single skeleton.qtz)

I can have Synapse.app running, have a skeleton actively tracking,
open the QC comp named
"01s_bodybuilder sample puppet synapse.qtz"

Inside, the "SkeletonStruct" output of the macro patch "01s_kinect
skeleton synapse to skeletonstruct" in the comp will show (when it
works)

3 Members(s):
0: "players" = <Structure>
0: "0" = <Structure>
and all the regular data flow of Head/neck/torso/etc.etc

When it doesn't, I get:
3 Members(s):
0: "players" = <Structure>
0: "0" = (unplugged)
but the head/torso/neck data is still flowing....

When I open the Synapse version of
"01_01s single skeleton.qtz" all I ever get is the unplugged version,
and no skeleton "love"

When I do have it working at some very random time QC will
inexplicably stop updating the puppet. No crash. Reboots dont help,
nor powering up/down the Kinect. Usually it's "come back tomorrow and
we'll see"

What could I be doing wrong? Have tried the instructions word for
word, then tried them out of order, have reinstalled, have offered
sacrifices to Trump's Hair, but cannot get it working reliably.

Lastly, I am getting these issues on two different computers, so must
be me somehow, right?

your thoughts!
jdjd

[Andrew Mc Govern]

Hi!,

I got the same sometimes it works ok and sometimes it just crashes!! Dont have a clue how to rectify the problem though!

Andy

[Sebastian Kox (gMail)]

Hi!

What OS&xcode are you on? I never tested it on lion/latest qc, don't know if it breaks something.

Hmm a quick fix for this might be to add an input splitter set to index, with a 0 value attached to the id input of your patches.
Let me know how this works out!

Sebastian.

[Sebastian Kox (gMail)]

Does it crash or stop working? If it crashes, can you send a screenshot/crash report?

Sebastian.

[John Daniel]

thanks for your input gang!!!

One system I Mac 10.6.7 ( I think am not in front of machine)

On system 10.6.5 Mac Mini

No "crashes", just the connection from Synapse.app>QC seems to punt. QC is alright, Synapse.app still keeps working solid, chasing my skeleton all over the room.

The only difference is the "unplugged" in the patch as in the quoted text below

0: "players" = <Structure>
0: "0" = (unplugged)

 

A lil more info for you guys, after I wrote the initial email, it all worked perfectly for about two hours, I could walk out of room, Synapse.app re-grabbed skeleton multiple times and QC continued just dandy.

I found that every time I loaded a new example comp in QC, then restarted sysnapse.app it worked flawlessly. Thought I had it down.

This morning tho - ' after shutting down for sleep, same problem reared it's head and was never able to get QC to see the Synapse data, with the identical comps I worked with last night....    weird. 

Hope this stirs some "synapses" out there. (sorry, had to ; )

jdjd

[jdjd]

hmmmmmmm new info... I bet there is a smoking gun in this for
someone......

Within about 5 seconds of turning off airport, I lose the
Synapse.app>QC connection.
Turn it back on, wait 5 seconds, data starts flowing!

I usually keep my airport off, and then put it on just to do
internet... would explain the timing of (possibly) 100% of my
problems....

Will test this long term tomorrow, see if I get drops with airport
never being off.


huh.
jdjd

On Oct 13, 10:58 am, John Daniel <jdjdd...@gmail.com> wrote:
> thanks for your input gang!!!
>
> One system I Mac 10.6.7 ( I think am not in front of machine)
> On system 10.6.5 Mac Mini
>
> No "crashes", just the connection from Synapse.app>QC seems to punt. QC is
> alright, Synapse.app still keeps working solid, chasing my skeleton all over
> the room.
> The only difference is the "unplugged" in the patch as in the quoted text
> below
>
> 0: "players" = <Structure>
>
> > 0: "0" = (unplugged)
> > A lil more info for you guys, after I wrote the initial email, it all
> > worked perfectly for about two hours, I could walk out of room, Synapse.app
> > re-grabbed skeleton multiple times and QC continued just dandy.
>
> I found that every time I loaded a new example comp in QC, then restarted
> sysnapse.app it worked flawlessly. Thought I had it down.
>
> This morning tho - ' after shutting down for sleep, same problem reared it's
> head and was never able to get QC to see the Synapse data, with the
> identical comps I worked with last night....    weird.
>
> Hope this stirs some "synapses" out there. (sorry, had to ; )
> jdjd
>
> On Thu, Oct 13, 2011 at 10:29 AM, Sebastian Kox (gMail) <
>

> sebastian...@gmail.com> wrote:
> > Does it crash or stop working? If it crashes, can you send a
> > screenshot/crash report?
>
> > Sebastian.
>
> > Op 13 okt 2011, om 14:39 heeft Andrew Mc Govern het volgende geschreven:
>
> > Hi!,
>
> > I got the same sometimes it works ok and sometimes it just crashes!! Dont
> > have a clue how to rectify the problem though!
>
> > Andy
>

[Sebastian Kox (gMail)]

Synapse uses OSC, and that is a network protocol. You'll probably always need an network adapter turned on, or at least a IP address configured for it to work. I'll update the manual.

Sebastian.

[John Daniel]

ahhhhh!  Love it. Will test more later tonight, but the flakey aspect seems to be in the past.

I love this! thank you!

jdjd

[Gabe Mott]

This may explain the problem I have been having. Synapse and qc would work flawlessly at my house.

But the last two times I've down shows it acted very very strange-- not responding to anything, then responding as if I had gestured when my hand covered the camera completely.

Going home to test this out- never occurred to me to think about a network connection.

Wonder why I never had any problem with the original OSCtryplex --- or did I?

[John Daniel]

Hey gabe (@ gang)

Yes, I think that was it, I cannot get it to screw up at all now.
The only weirdness I still have is everytime I open a new QC comp I have to quit/restart Synapse.app to get the connection restarted...    that's all.  I can WAY deal with that.  Not even sure if that is a problem, or just "sumpin' ya gotta do"
Is consistent. That's what I needed....

I am, shall I say it? - deliriously happy now.
Looking forward to getting the Tryplex rig going when I have time for the install...

thank you Tryplex and Hexler crew!!!        U Rock. - Hard.  

cheers!
jd

[John Daniel]

New wrinkle. I am at a place with no wi-fi, and even with Airport turned on, I get no synapse>QC connection.

Sebastion, you mentioned something about a network adapter and a IP configured.... any suggestions on a standalone way to set this up?

I know very very little about networks connections, and could flail endlessly, could you point me in a good direction?

thanks!!!!!

jdjd

[victor morales]

Yes,I have had similar problems.
one thing that worked was to edit the tryplex macro called "01s_Kinect
Skeleton Synapse settings.qtz"
located on library/graphics/quartz composer patches

there, on the osc sender patch/node, change the settings of the IP
address from 0.0.0.0 to 127.0.0.1
that basically tells quartz to send messages in the local machine.
after changing it, save it.

maybe sebastian could fix this for future releases, or maybe is a
feature. the fact is if you want it local, you have to change that
value

hope it works

victor

On Oct 16, 7:14 pm, John Daniel <jdjdd...@gmail.com> wrote:
> New wrinkle. I am at a place with no wi-fi, and even with Airport turned on,
> I get no synapse>QC connection.
> Sebastion, you mentioned something about a network adapter and a IP
> configured.... any suggestions on a standalone way to set this up?
> I know very very little about networks connections, and could flail
> endlessly, could you point me in a good direction?
>
> thanks!!!!!
> jdjd
>
>
>
>
>
>
>
> On Sat, Oct 15, 2011 at 12:43 AM, John Daniel <jdjdd...@gmail.com> wrote:
> > Hey gabe (@ gang)
>
> > Yes, I think that was it, I cannot get it to screw up at all now.
> > The only weirdness I still have is everytime I open a new QC comp I have to
> > quit/restart Synapse.app to get the connection restarted...    that's all.
> > I can WAY deal with that.  Not even sure if that is a problem, or just
> > "sumpin' ya gotta do"
> > Is consistent. That's what I needed....
>
> > I am, shall I say it? - deliriously happy now.
> > Looking forward to getting the Tryplex rig going when I have time for the
> > install...
>
> > thank you Tryplex and Hexler crew!!!        U Rock. - Hard.
>
> > cheers!
> > jd
>

[trypl...@gmail.com]

Will do, haven't used synapse that much to run into these problems.
Thanks for the heads up!

[John Daniel]

Have I told you guys lately how much I love you?   Well I do - so there.
Works perfect - that did it.

Thank you!
jd

[Gabe Mott]

So glad you all sorted this out! I was having a devil of a time understanding why I was falling on my face doing installs on site! 

Has anyone else implemented Victor's solution?

there, on the osc sender patch/node, change the settings of the IP 
address from 0.0.0.0 to 127.0.0.1 

 I'm hoping this solves all the problems as I am mostly installing outdoors without internet connections...

Thanks again!

[John Daniel]

Hey Gabe!
Yes, has been flawless ever since. I was SO glad to get that info (0.0.0.0 to 127.0.0.1 )
because even tho my stuff was working. the next weekend I had a gig scheduled (with no net connections of any kind) and I would have been SOOOO boned.

I absolutely love what I can do with this, and the over 1000 kids at the event I did thought so too.

THANKS Tryplex/Synapse/anybody else "responsible" You rock!

jd

[trypl...@gmail.com]

Great to hear!

Do you have any documentation or pictures on the project you're doing? I'm curious!

Sebastian.

[mike]

Hey All,

I made the change(via Victor) to the IP address inside of the synapse
settings to 127.0.0.1, but am still not getting osc data flowing in my
compositions. Am I confusing the port numbers? I'm used to the
standalone synapse tutorial that uses a max patch to transmit osc
data, which used 12348.

My current config is:

1.Launch Synapse and register my skeleton
2.Launch Quartz Passthrough (Max Patch)
3.Launch Quartz 01s_bodybuilder sample puppet synapse.qtz
4.nothing happens

Any help would be great.

Mike

On Oct 26, 3:23 am, "tryplex...@gmail.com" <tryplex...@gmail.com>
wrote:

> Great to hear!
>
> Do you have any documentation or pictures on the project you're doing? I'm curious!
>
> Sebastian.
>
> Op 25 okt 2011, om 23:44 heeft John Daniel het volgende geschreven:
>
>
>
>
>
>
>
> > Hey Gabe!
> > Yes, has been flawless ever since. I was SO glad to get that info (0.0.0.0 to 127.0.0.1 )
> > because even tho my stuff was working. the next weekend I had a gig scheduled (with no net connections of any kind) and I would have been SOOOO boned.
>
> > I absolutely love what I can do with this, and the over 1000 kids at the event I did thought so too.
>
> > THANKS Tryplex/Synapse/anybody else "responsible" You rock!
>
> > jd
>

[JaredFromSubway]

Hey Mike,

If you install the latest version of Synapse (in the Triplex toolkit),
you shouldn't need the max patch to run it.

[Mike Wirth]

Thanks Jared. Is the version from the triplex site the most recent version?

Sent from my iPhone

[JaredFromSubway]

As far as I know, it's the one I'm using.

On Nov 13, 7:33 pm, Mike Wirth <mike.drew.wi...@gmail.com> wrote:
> Thanks Jared. Is the version from the triplex site the most recent version?
>
> Sent from my iPhone
>

[mike]

Hi Jared,

I am now using the version of synapse that came with the toolkit only
(no max patch) and am still not getting input. It works for a split
second(meaning the skeleton maps to the body) and then the skeleton
becomes unresponsive. No other compositions are responding either.

Best,
Mike

[JaredFromSubway]

I wish I could say I know, Mike. I've only played with QC a few times.
I am mostly working with ableton.

This question is for everyone please.

Is there a way to turn the OSC data coming from the kinect into MIDI
data?

Thanks all.

[jon hammod (Just add music)]

Make sure you have the '01s_Kinect Skeleton Synapse settings' patch on
the top root of your QC patch.

@JaredFromSubway look at FSK midi plugin http://kineme.net/forum/Discussion/Programming/MIDIplugin

On Nov 22, 6:17 pm, mike <mike.drew.wi...@gmail.com> wrote:

[wagedu]

Hi, from a similar experience (ehem) I've learnt that the order of your steps matters. You should FIRST launch your .qtz file and SECOND after that, stand in the cactus position to calibrate.

If you calibrate BEFORE opening the .qtz file it won't work.

Also, another question of the thread is giving me trouble. I read about the problems to use the macros without a connection to the internet. So I tested and, yeah, it stops working.

Now, I cannot solve it following your instructions. So the problem "works" while the solution doesn't :(

I don't have the tryplex macros on Library/Graphics/Quartz Composer Patches, but in their original folder. They seem to work anyway.

But when I open the above mentioned file "01s_Kinect Skeleton Synapse settings.qtz", there's no OSC sender patch/node, just a "Synapse settings" (blue) one.

I'm on Snow Leopard, QC 4.

Thanks and many thanks... tryplex is great! I wish I'd know it before.

[mike]

Hey All,

Id love to get this working.

I've tried all of the tips and tweaks on this thread and I'm hoping
someone could give me a clear cut path of needed steps to get things
going.

I'm on Mac osx lion. I've downlaoded the newest Synapse that is
bundled with the Tryplex toolkit and have adjusted the port numbers in
the patches.

I start up by launching Synapse, then QC (puppet or 1 skeleton
composition) and then I cactus pose calibrate. If I'm lucky, I
sometimes get motion for about 3-10 seconds and then it goes dead.
Otherwise, I get nothing.

Best,
Mike

[mike]

Hey John,

You seem to have solved the setup issues. Can you shed some light on
your step by step process?

Best,
Mike

[stu shapiro]

THANK YOU!!!!!!!!!!!!!!!!!!! Wow , oh wow, i have spent hours trying to figure out what i did wrong. 

[Frank Napolski]

Hey Mike, you may be long gone by this time but can you check the model number of your Kinect? 

It's on the bottom, in the top right—I believe any model that is not Model 1414 will not work properly.