SynthMaker

Draw loop

Archive · 2010 9 old posts

From the original SynthMaker forum (2004–2014), with its members’ names and dates.

stw ·

Could you please test the attached draw loop BUG osm? Simply open the osm and click on the top (leftmost) display in the osm order in the upper overview row. On my machine SM crashes instantly. Remove the redraw trigger and everything is fine.

MichaelBenjamin ·

yes it crashes

loopeytunes ·

crashes in mine also

LT

infuzion ·

Crashes for me also, though it takes a 2-4 seconds.

trogluddite ·

Yes it crashes. Not sure it's really a bug though - normal usage would be to have one ReDraw to the left of the loop which ReDraws all looped elements in one go. Even if you could have a ReDraw triggered per iteration, the result on screen would be exactly the same - but the extra ReDraws would just add huge amounts of extra CPU load. If the intention is an animation showing a series of frames, then a normal green loop outside of the GUI part would be the way to do it - using a ticker to set the frame rate.

My guess at what is happening... Loop receives it's first ReDraw trigger - loop starts counting - on the first count a ReDraw is triggered - this new ReDraw re-triggers the loop (possibly nested within the initial loop) - which creates a new ReDraw trigger - which retriggers the loop - and so on ad infinitum until there are no more resources to create another nested loop.

aliasant ·

It aint a bug. I had a similar thing a year back and talked to Malc about it. Seems that you can cause a sort of feedback loop doing what you did.

Edit: Hee. Exactly what Trogg said.....

MegaHurtz ·

It delivers a full and fast crash at my place 😀

stw ·

OK than it seems that the behaviour isn't a bug but a mistreatment of the prims. Which should lead to a red line feedback loop crash avoider. So could the missing feedback loop recognize be considered as a bug? If not, at least the module description should mention how to treat redraws with using draw loops?

aliasant ·

stw wrote: OK than it seems that the behaviour isn't a bug but a mistreatment of the prims. Which should lead to a red line feedback loop crash avoider. So could the missing feedback loop recognize be considered as a bug? If not, at least the module description should mention how to treat redraws with using draw loops?

Absoluely. A red line AND a better description would be nice. Just add it to Malcs list 😉

Wrote something here? To have a post removed or your name hidden, write to [email protected].

Before your first post

A few rules keep this a friendly place. You agree to them once.

Shown next to what you post, here and in the app. It doesn’t have to be your real name: 3–24 lower-case letters, digits or _ (capitals become lower case, spaces become _).

    Then your post goes up straight away.

    Delete this reply?

    Open it in SynthMaker?

    It goes on the track you’re editing there, in place of that track’s sound, and into My sounds. Your other tracks stay as they are.

    Want to keep that track’s sound? Start a new song in SynthMaker first (Song › New song), then open this.

    Report this reply?

    Only the developer reads reports. The person isn’t told who reported them.

    What’s wrong with it?

    Block this person?

    You won’t see their posts and replies here any more. They aren’t told, and you can unblock them at any time.

    People you’ve blocked

    Their posts and replies are hidden from you. Unblock someone to see them again.

    The community rules

    A few rules keep this a friendly place. Everyone agrees to them once, before their first post.