Robin Price

I can send from a bpatcher to another subpatch else where but I cannot grab. Why is this?

bug-grab-doesnt-work-from-inside-a-bpatcher-embedded-or-not-but-send-does

As much as I liked grab when it first arrived, it's a legacy object that won't do a lot of things. You're probably better off with pattr & Co. or pvar objects.

I realize this isn't much of an answer to your question "why?". I recall discussions from many years back to the effect that developers at Cycling '74 considered grab something of a dark hack to do things that pvar and pattr do in a cleaner manner. The grab object seems to be maintained mainly to allow old patches using it to continue to run.

This makes me sad, I understand grab, I'd go as far to say it was one of my favourite objects. pattr consistently melts my brain when I try to do more than basic preset storing and interpolation. Specifically I always get stuck with sharing data between pattrs in different sub patches. Back to the tutorials and forum surfing I go.

Well, some years later I had the same problem. As this might be useful to others I add a reply. 

Grab together with a send to a receive inside a bpatcher does not work! It should, though! 

Grab doesn't get the data back through the patcher path – really annoying because the reference states clearly, that grab works perfectly fine through sends and receives – why the hell not with bpatcher... ?

If you use a pattr @bindto and ad the path of your bpatchers object you want to "grab", grab will work perfectly fine. This means that you'll have to give your object in the bpatcher a scripting name (varname).

Well, some years later I had the same problem. As this might be useful to others I add a reply. 
Actually, this is a bug from CYCLING74. 
Grab together with a send to a receive inside a bpatcher does not work! It should, though! 
Grab doesn't get the data back through the patcher path – really annoying because the reference states clearly, that grab works perfectly fine through sends and receives – why the hell not with bpatcher... ?
The "workaround": 
If you use a pattr @bindto and ad the path of your bpatchers object you want to "grab", grab will work perfectly fine. This means that you'll have to give your object in the bpatcher a scripting name (varname). 

[bug ?] grab doesn't work from inside a bpatcher (embedded or not) but send does