SynthMakeraliasant ·
If a module has an "After Load" prim inside the "After Load" will not send a trigger if the module is pasted into the schematic or dragged in from the toolbox.
After Load prim...
From the original SynthMaker forum (2004–2014), with its members’ names and dates.
trogluddite ·
No trigger when dragging or pasting - but I do get a trigger when the schematic is saved and then loaded again (using latest 1.1.6 full release). Is this not the correct behavior? It's what I would have expected.
oddson ·
Do you mean it doesn't trigger when added in these ways once opened in a VST/DLL?
trogluddite ·
Just tested this with exe, and a dll loaded into VSThost. All behaves as expected.
aliasant ·
It works perfectly fine as VST and exe but not inside SM. Malc already said it should and that he will try to fix that in 1.1.7
For me this is a problem cause some of my graphics are cached and when copied or dagged into a schematic the graphic isnt updated until I resize or "touch" the module.
oddson ·
I can't replicate with the simplest case (After Load stored inside a module on it's own and this stored in a toolbox then added to file, then save and close -- on reopen it always triggers).
It must be some sort of interaction with other elements.
aliasant ·
No No No
Take the After Load Put it in an empty module. Add a tick counter after the After Load.
Now Copy the module with the After Load and Tick counter. And now Paste that module back in and look inside at the tick counter. It will read 0 ticks.
Test 2: Take the same module and drag it to the toolbox. Take it from the toolbox and drag it back to a schematic and check the trigge. Again it will read 0.
It has nothing to do with opening a schematic.
infuzion ·
aliasant wrote: Take the After Load Put it in an empty module. Add a tick counter after the After Load.
Now Copy the module with the After Load and Tick counter. And now Paste that module back in and look inside at the tick counter. It will read 0 ticks.
Test 2: Take the same module and drag it to the toolbox. Take it from the toolbox and drag it back to a schematic and check the trigge. Again it will read 0.
You just proved it is working perfectly.
aliasant wrote: It has nothing to do with opening a schematic.
You are wrong here. Sorry.
aliasant ·
I dont get it Infuzion ?
My claim is that the ticker Should give 1 tick when dropped into a schematic and it doesnt. Yours is that it shouldnt?
stw ·
aliasant wrote: I dont get it Infuzion ?
My claim is that the ticker Should give 1 tick when dropped into a schematic and it doesnt. Yours is that it shouldnt?
Hmm maybe some kind f misunderstanding. AFAIK (and that's what the help text says) the AfterLoad tick should give a tick if a vst/exe/osm is loaded and initialized. Not if the module is dropped in. And this works pretty well.
aliasant ·
stw wrote: aliasant wrote: I dont get it Infuzion ?
My claim is that the ticker Should give 1 tick when dropped into a schematic and it doesnt. Yours is that it shouldnt?
Hmm maybe some kind f misunderstanding. AFAIK (and that's what the help text says) the AfterLoad tick should give a tick if a vst/exe/osm is loaded and initialized. Not if the module is dropped in. And this works pretty well.
Well. Maybe it has just been forgotten or something but Malc did say that he too thinks it shoud give that tick when dropped in. Why shouldnt it? Would there be a problem if it did? I guess it might if you drop something into a schematic that starts a huge calculation or a loop with no limit but if that happens maybe its not the After Loads tick that is the problem? I have a lot of modules that needs a tick when placed in a schematic so for me its a no brainer. It is also a great way to check if it actually works. The After Load that is. As it is now I have to save, close and reopen the schematic evey time to see if it actualy works. Simply sending a trigger hasnt always worked.
rl ·
> Why shouldnt it?
From my understanding the purpose of the module is to fire a trigger when the whole schematic (or should I rather say: synthmaker engine) starts.
aliasant ·
rl wrote: > Why shouldnt it?
From my understanding the purpose of the module is to fire a trigger when the whole schematic (or should I rather say: synthmaker engine) starts.
True enough but it stil annoys me that it doesnt fire that trigger. Been trying to find a workaround and I thought I wasw on to something but it didnt work =( The MGUI prim sends out 1 trigger for Width and one for Height when dropped in fro the toolbox ( inside a module). It even send 2 triggers for each W & H if Pasted into the schematic.
I tried to use the last of those as a substitute but even if I pass it directly + a second via a trigger delay and I can see on the trig counter that the trigs have been sent ok they still dont update my schematic. I stil have to interact with a mouseclick to make it look as it should.
Weird.
malc ·
I did indeed say that I thought that the After Load should behave as aliasant wants it to.
This is probably because I had my programmers head on and because copy and paste and dragging from the toolbox all involve saving and loading my first instinct was that the After Load should fire on these occasions too.
But of course After Load should mean 'after loading' and that should be after loading in the mind of the user, not mine, so that's only after the schematic loads.
Now that all said, there is still a problem here. It's already been pointed out that there are situations when you may want to fire something off on schematic load and there are other situations where you want something to happen on pasting, duplicating or dragging from the toolbox. There might also be situations where you want a trigger when any of these situations arise.
I need to think some more about this but one solution would be to create a new component to cover these other situations - a kind of 'After Duplicate' component if you like.
aliasant ·
malc wrote: I did indeed say that I thought that the After Load should behave as aliasant wants it to.
This is probably because I had my programmers head on and because copy and paste and dragging from the toolbox all involve saving and loading my first instinct was that the After Load should fire on these occasions too.
But of course After Load should mean 'after loading' and that should be after loading in the mind of the user, not mine, so that's only after the schematic loads.
Now that all said, there is still a problem here. It's already been pointed out that there are situations when you may want to fire something off on schematic load and there are other situations where you want something to happen on pasting, duplicating or dragging from the toolbox. There might also be situations where you want a trigger when any of these situations arise.
I need to think some more about this but one solution would be to create a new component to cover these other situations - a kind of 'After Duplicate' component if you like.
Totaly agree.
Ill send you one of my little things that really needs this. It has a cached gui part that needs that trigger and it could be a good example to ponder over.
oddson ·
malc wrote: ...I need to think some more about this but one solution would be to create a new component to cover these other situations - a kind of 'After Duplicate' component if you like.
Or you could make AfterLoad work the way both you and aliasant thought it should... I can't see that this would break anything for anyone.
infuzion ·
oddson wrote: malc wrote: ...I need to think some more about this but one solution would be to create a new component to cover these other situations - a kind of 'After Duplicate' component if you like.
Or you could make AfterLoad work the way both you and aliasant thought it should... I can't see that this would break anything for anyone.
I find extra triggers annoying, so I'd be against this. I imagine I could live with it. Or have the "After Load trigger with placement also []" in the options is anther idea.
oddson ·
infuzion wrote: ...I find extra triggers annoying, so I'd be against this...
But it would only fire a trigger when you paste something with an AfterLoad primitive in it... it would otherwise change nothing on existing schematics...
I love new primitives but only when they do something useful.
DigitalWhiteByte ·
I think that might be useful to have a primary that would give a trig, when it is taken from the toolbox, because when the block of the module will work, could be used to initialize some function in it. To me it seems useful.
oddson ·
But what I'm saying is that useful thing could be done by the same very useful AlfterLoad primitive which would only fire the extra trigger in the very specific circumstance of when it's pasted as part of a module...
But if there's a new primitive all it would be good for is on pasting to initialize parameter settings, but chances are you'd also need to add an AfterLoad to make sure they also initialize on loading the VST/exe... why not do both with the same one... which is what Aliasant expected in the first place and what Malc assumed it would do.
aliasant ·
oddson wrote: But what I'm saying is that useful thing could be done by the same very useful AlfterLoad primitive which would only fire the extra trigger in the very specific circumstance of when it's pasted as part of a module...
But if there's a new primitive all it would be good for is on pasting to initialize parameter settings, but chances are you'd also need to add an AfterLoad to make sure they also initialize on loading the VST/exe... why not do both with the same one... which is what Aliasant expected in the first place and what Malc assumed it would do.
🙂
(meaningless comment from a tired, pretty much useless brain not yet had its coffe.... )
Wrote something here? To have a post removed or your name hidden, write to [email protected].