i build a patch which loads (and remembers) Nord Modular Patch files in the Nord Modular Editor, from a M4L midi effect. I was placing a loadbang in the patch which (should) trigger the load process when the Live set is loaded (the midi device is loaded). But i have to trigger the load process manually. it doesn't work with loadbang and loadmess.

can someone have a look on this and make a suggestion? Thanks!

Hi,
i build a patch which loads (and remembers) Nord Modular Patch files in the Nord Modular Editor, from a M4L midi effect. I was placing a loadbang in the patch which (should) trigger the load process when the Live set is loaded (the midi device is loaded). But i have to trigger the load process manually. it doesn't work with loadbang and loadmess.
can someone have a look on this and make a suggestion? Thanks!


what-am-im-doing-wrong-loadbang

Try a [deferlow] after the loadbang/loadmess. That work?

It's very unlikely that loadbang is malfunctioning. Your patch is a little messy, my advice to you is tidy it up so it's clear to you how the internal logic is working. Then check your message ordering, possibly replace your button objects by using the trigger object to control which bangs are sent first.

i tried [deferlow] after loadbang...does not work

i'm quite new to m4l. the data flow is from top to bottom, right.

so, when the device is loaded, first thing should happen is a bang which triggers the file load. so, loadbang is on the most top of the patch,right?

@ AlexHarker
i tried [deferlow] after loadbang...does not work

@ David Butler
i'm quite new to m4l. the data flow is from top to bottom, right.
so, when the device is loaded, first thing should happen is a bang which triggers the file load. so, loadbang is on the most top of the patch,right?


i just discovered that [loadbang] does it's job if i open the patcher window. just dragging the device in the set, or open the Liveset with the device won't [loadbang]to bang.

if this is correct, than a device which gets active on startup isnot possible without opnening the patcher?

i just discovered that [loadbang] does it's job if i open the patcher window. just dragging the device in the set, or open the Liveset with the device won't [loadbang]to bang. 

if this is correct, than a device which gets active on startup isnot possible without opnening the patcher?
can anyone help me on this.

The data flow is from to bottom to top and right to left. Have a look at Max tutorial five on message ordering.

(i think David meant 'top to bottom and right to left'(typo?), right to left takes precedence... maybe i'm wrong, that's how i've come to understand it, though...)

________________________________
*Never fear, Noob4Life was never here!*


I think it is bottom to top as illustrated here

[Edit: you don't really need the extra [t b] objects for that patch, though, eh? or do they help with something i'm not seeing?]

ah, thanks for clarifying this!
[Edit: you don't really need the extra [t b] objects for that patch, though, eh? or do they help with something i'm not seeing?]

correct-- just my habit of using trigger objects unnecessarily manifested...

without looking at the patch my guess would be that the patch is not responsible

for the problem, but live and the concept of live devices / m4l is.

something is wrong with the order of loadbanging the m4l patch and the midi

initialisation of live, or , eventually, your specific hardware/software setup.

you said it works when the window is open ... does it also work when you

bng the loadbang again? does it also work with a delay 15 behind the loadbangs?

without looking at the patch my guess would be that the patch is not responsible
for the problem, but live  and the concept of live devices / m4l is.

something is wrong with the order of loadbanging the m4l patch and the midi
initialisation of live, or , eventually, your specific hardware/software setup.

you said it works when the window is open ... does it also work when you
bng the loadbang again? does it also work with a delay 15 behind the loadbangs?


yep, [loadbang] works if the patcher window is opened with the edit button.

is this a genaral flaw that just dropping a m4l device into Live, doesn't force [loadbang] to bang ?!

yep, [loadbang] works if the patcher window is opened with the edit button.
is this a genaral flaw that just dropping a m4l device into Live, doesn't force [loadbang] to bang ?!


I think Roman is on the right track. The issue has been discussed here.

https://cycling74.com/forums/initialization-order-inconsistency

See in particular the explanation from Jeremy Bernstein at the end.

Yes, i figured out. I was indeed the order of events specific to m4l handling of [loadbang]. Thanks for giving the info on the thread!

Hey Roman, the [delay] worked out :-) patch loads now as it should!

as the most files are openend by their specific windows programs, the Nord Modular Editor (and notepad for .txt files) just opens as process in the taskmanager, butnot as GUI. Anyone knows what can causes this? any specific windows way for opening files? (btw. picture, mp3, word docs, are opened fine with GUI).

Another question:
as the most files are openend by their specific windows programs, the Nord Modular Editor (and notepad for .txt files) just opens as process in the taskmanager, butnot as GUI. Anyone knows what can causes this? any specific windows way for opening files? (btw. picture, mp3, word docs, are opened fine with GUI).


What am i'm doing wrong ? [loadbang]