Charly Beck

this bpatcher does not open the edit window in max4live when ctrl+dblclick. Instead just the parent window flashes. The behaviour remains after copy+paste. And i got more bpatchers that react like this. Others are opening. What's wrong here?

bpatcher

message

comment

inlet

prepend

unpack

route

outlet

zl.join

zl.nth

pack

zl.sub

matrixctrl

patcherargs

append

zl.rev

zl.group

live.text

this bpatcher does not open the edit window in max4live when ctrl+dblclick. Instead just the parent window flashes. The behaviour remains after copy+paste. And i got more bpatchers that react like this. Others are opening.  What's wrong here? 

Hi,
this bpatcher does not open the edit window in max4live when ctrl+dblclick. Instead just the parent window flashes. The behaviour remain

bpatcher-does-not-show-edit-window

Ok i created a new bpatcher with command RightClick->Object->New PAtcher with contents of embedded patcher.

maybe you embedded one bpatcher and the other one not?

well no i dont think so.. you can check it if you paste the bpatcher...

unembedded patchers with no file set cant have a content. that is protected by max gui. unchecking the embedd checkbox after adding conetnt will delete the content i think.

i think Roman is just pointing out the main difference here...

your first post shows the bpatcher is embedded:

Screen Shot 2021-02-19 at 10.29.57 AM.png

this is probably a confusion about expectations of the interface as it works in M4L, but in regular Max you would need to use "RightClick->Object->New Patcher With Contents Of Embedded Patcher" to edit: embedding things will create a fixed copy embedded into the patcher, to edit further, you 'right-click->object->new patcher...' in order to copy the embedded form into a newer editable form(you would need to re-embed that edit in order for the changes to register in the original bpatcher as well).

your first post shows the bpatcher is embedded:


i am not sure if i would see this when i paste only the bpatcher itself, however, they both open for me after pasting. 

my speculation was based only on the fact that i never use embedded bpatchers (or images for that matter) myself, that is probably a bit less to speculate.

i am not sure if i would see this when i paste only the bpatcher itself, however, they both open for me after pasting. 
my speculation was based only on the fact that i never use embedded bpatchers (or images for that matter) myself, that is probably a bit less to speculate.

i posted something else before, but i see a weird difference now:

if i try "Right-Click->Object->New View Of Embedded Patcher" (instead of 'new patcher with contents...'), the first bpatcher posted in this thread seems to defocus from any window(as if it's trying to display some other view), but doesn't display anything.... while the second bpatcher posted does actually open a 'new view'.

interesting... i'm not sure why that difference is 🧐🤔

i posted something else before, but i see a weird difference now:
if i try "Right-Click->Object->New View Of Embedded Patcher" (instead of 'new patcher with contents...'), the first bpatcher posted in this thread seems to defocus from any window(as if it's trying to display some other view), but doesn't display anything.... while the second bpatcher posted does actually open a 'new view'.

interesting... i'm not sure why that difference is 🧐🤔


it appears as a bug to me. Strange thing: I worked for about 10-20 hours on the device and within 30 minutes 2 bpatchers got corrupted in that way. well, at least i found a way to recover, so i was able to continue developing the device.

@roman: I often use (b)patchers, which i copy /paste and later, when i extend one (b)patcher i use paste-replace command. that is faster than doing the change several times.

you can use patcherargs or messages to configure the bpatcher instances in a different way.

@roman: I often use (b)patchers, which i copy /paste and later, when i extend one (b)patcher i use paste-replace command. that is faster than doing the change several times. 

on old times sometimes you had bugs in patchers, not only but mainly when switching between mac and windows. then it could happen that you did not notice it in time, made copies of the file for another patch and the bug was copied, too.

go for a forensic search in the json, if there is a difference somewhere, aim at it and shoot twice.


on old times sometimes you had bugs in patchers, not only but mainly when switching between mac and windows. then it could happen that you did not notice it in time, made copies of the file for another patch and the bug was copied, too.

go for a forensic search in the json, if there is a difference somewhere,  aim at it and shoot twice.


ah right, i could do that, yes. but now as it works for me , i don't feel the effort in comparing these json files ;)

(i missed that i can also use the normal copy-command and see a json structure - good idea.)

BPatcher does not show edit window