SynthMaker

Resetting the counter

Archive · 2005 9 old posts

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

fritzman ·

Hi folks,

I want to reset the counter module when the counter is at a certain number. I tried this:

This doesn't reset the counter. What am I doing wrong or is this a bug?

Thanx a lot, FRitz

oddson ·

Something's wrong there. (I'd use a boolean to trigger but that doesn't fix it anyway.)

The other counter is better for this type of thing but there seems to be something wrong with the reset on the simple counter.

fritzman ·

Thanx oddson,

that's what I thought but wasn't sure.

Best wishes, FRitz

oddson ·

In fact I've posted this exact thing elsewhere and it used to work fine.

fritzman ·

oddson wrote: In fact I've posted this exact thing elsewhere and it used to work fine.

Aha. This doesn't work here.

infuzion ·

fritzman wrote: oddson wrote: In fact I've posted this exact thing elsewhere and it used to work fine.

Aha. This doesn't work here.

1) I'm sure Counter has a crashproof thing that will prevent any looping triggers from flasely (& perhaps crashingly) triggering the reset. You have to put a TThread in to get what you want it to do. Not sure if this is an expected-behaviour bug, but I'll let you decide if it is.

2) If you do #1 right now on 0.9.5e, you'll crash SM. I've noticed a few days ago that the output for the comparison primitives send a trigger whenever they receive a new value; not just when the output boolian switches from True/False or False/True. I sent in a bug report just now about it. For now, you can use {edit} a Bool to True Trigger to get around this bug: [URL=http://rapidshare.de/files/8966076/bug0.9.5e-CompareOutputBounce2_infuzion.osm.html]

http://rapidshare.de/files/8966076/bug0 ... n.osm.html[/URL] (Bonus: Has updated Flipper 1.2) Hope this helps.

Sidenote to fritzman: I don't think this post should be in the "Sound" forum; it partains only to 1 non-audio making primitive. This question should have been posted in General. Also, if you can trim down your pic for us low-bandwidth users, that would help. cheers

fritzman ·

Hi Infuzion,

infuzion wrote: fritzman wrote: oddson wrote: In fact I've posted this exact thing elsewhere and it used to work fine.

Aha. This doesn't work here.

1) I'm sure Counter has a crashproof thing that will prevent any looping triggers from flasely (& perhaps crashingly) triggering the reset. You have to put a TThread in to get what you want it to do. Not sure if this is an expected-behaviour bug, but I'll let you decide if it is.

2) If you do #1 right now on 0.9.5e, you'll crash SM. I've noticed a few days ago that the output for the comparison primitives send a trigger whenever they receive a new value; not just when the output boolian switches from True/False or False/True. I sent in a bug report just now about it. For now, you can use {edit} a Bool to True Trigger to get around this bug: [URL=http://rapidshare.de/files/8966076/bug0.9.5e-CompareOutputBounce2_infuzion.osm.html]

http://rapidshare.de/files/8966076/bug0 ... n.osm.html[/URL] (Bonus: Has updated Flipper 1.2) Hope this helps.

oh yes, this helps. Thanx a lot. I already did it now with the bigger counter thingy but to know how to work around those bugs helps for sure. 😉

infuzion wrote: Sidenote to fritzman: I don't think this post should be in the "Sound" forum; it partains only to 1 non-audio making primitive. This question should have been posted in General. Also, if you can trim down your pic for us low-bandwidth users, that would help. cheers

Sorry man! I'm obviously too long on DSL that I don't care TOOOO much for bandwidth anymore. 🙁 The screenie was 35k big. Now it's only 14k. Will think about it in the future. Well, the category: I wasn't sure if it was a bug (BUG section) and I thought that it was relatively specific this little thingy that I didn't want to put it into general. I'm not sure where it really fits in!?

Best wishes, FRitz

infuzion ·

fritzman wrote: Well, the category: I wasn't sure if it was a bug (BUG section) and I thought that it was relatively specific this little thingy that I didn't want to put it into general. I'm not sure where it really fits in!?

Well, this question still isn't (directly) related to Sound, Graphics, not quite a Bug, it isn't "off topic", not really a working Example nor a Project... so I would say General would be the best bet.

fritzman ·

infuzion wrote: fritzman wrote: Well, the category: I wasn't sure if it was a bug (BUG section) and I thought that it was relatively specific this little thingy that I didn't want to put it into general. I'm not sure where it really fits in!?

Well, this question still isn't (directly) related to Sound, Graphics, not quite a Bug, it isn't "off topic", not really a working Example nor a Project... so I would say General would be the best bet.

Well, it's actually that what's left then, right? 😉

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.