Hello group,
I changed the step sequencer thus:
- tempo is given in beats per minute
- notes are separated with a dash, a simple 4 note pattern is written as
"1-2-3-4"
- notes can be subdivided, subdivisions are separated with a comma. To play an
alternating pattern of two eighth notes and one eighth triplet you would give
the sequence as "1,2-1,2,3".
- The pause the beginning is given relative to the beat length, i.e. enter 0.5
to wait for half a beat, 2 for two beats etc.
- A constant time offset can be given that is independent from the tempo.
Again, you can find it here: control.my/qc
Comments, criticism and grammatical corrections are always welcome!
Regards,
Sebastian Mecklenburg
On 30.09.2011, at 18:05, George Toledo wrote:
>
>
> On Fri, Sep 30, 2011 at 11:10 AM, Sebastian Mecklenburg
> <s...@happyhappyboy.de> wrote:
> Hello George and all,
>
> I think I know what the misunderstanding is: At the same tempo in beats per
> minute a 12/8 bar takes 1.5 times longer to finish than a 4/4 bar.
>
> Yes! Exactly. :-) Also... somewhere around here on list I made a little
> engine that does this pretty darn well (I've tweaked it some since). You put
> in a BPM, and then I believe it delivers whole notes, 1/4, 1/8 and 1/16, and
> you can set how many beats should be a in a bar, and the time subdivision (I
> think that's the one I uploaded). Anyways, it seems like plenty of other
> users have done this too :-) I haven't used lov's engine, but clips I've seen
> of it sure seem to work well.
>
>
> But that is not what I wanted, I wanted to play all the given notes in the
> same amount of time. So my nomenclature in the description is wrong. The
> number of values in the "Sequence" field is NOT the time signature, it is the
> subdivision and the time signature is always 1/4. The given tempo in the
> "Bars per Minute" field is actually beats per minute and when you enter three
> values in the "Sequence" field my step sequencer plays eighth triplets, when
> you enter four values it plays 16th notes and so on. So my step sequencer
> does what I wanted it to do, it just does fit for a very different reason
> than I thought it would and I didn't describe what it does correctly. I will
> definitely go back to beats per minute and think up another way to specify
> subdivisions and all should become clear.
> As Jeff put it quite aptly, "Every step sequencer known to mankind before you
> is measured in beats per minute, not bars per minute." and now I know why :-)
>
> It's a nice piece of work, and it looks like you got all of the major bits in
> there :-)
>
>
> Thanks for pointing out the "Whole notes" issues. Since english is not my
> mother tongue I really appreciate corrections there. I thought that "Wholes"
> would be short for "Whole notes". I changed it to "Whole Notes Pause".
>
> I'd need to look at it again, but it should probably be "whole note pause",
> if it just pauses for one whole note, and it's a boolean, because none of the
> words need to be "plural". (Thanks for taking that comment well, because I'm
> sincerely trying to help it be as you might wish, not be nitpicky). If you
> allow integers (eg., it can delay more than a whole note) you may want to
> choose "Whole Note Pause Count". You took the zip offline, so I can't check
> it out :-/
>
>
> Also it is not "whole note or nothing", you can enter floating-point numbers
> there. I did that so that you can enter things like 0.333 to create a triplet
> offset or whatever.
> Latency correction seems a rather exotic feature to me in this context, do
> you think it would be useful in Quartz composer? It would be easy to add
> though and wouldn't hurt probably...
>
> I think that having one input on the front end that allows you to subtract or
> add to the output value by a floating point is likely handy, depending on
> what the output result of this patch delivers (I didn't dl it right away, and
> I'm guessing you took it down to do some changes). I don't think it's exotic,
> because one may wish to cue a visual event ever so slightly ahead or behind
> the actual beat, or more complexly, fluctuate at a given pace to affect a
> "groove template".
>
> Best regards,
> gt
>
> Thanks and regards,
> Sebastian Mecklenburg
>
>
> On 29.09.2011, at 21:36, George Toledo wrote:
>
> >
> >
> > On Thu, Sep 29, 2011 at 5:26 AM, Sebastian Mecklenburg
> > <s...@happyhappyboy.de> wrote:
> > hello,
> > I chose bars per minute as a tempo specifier because it is way easier then
> > to synchronize different step sequencers with different time signatures.
> > you can just enter 16 values in the sequence field. if one values is
> > supposed to play every beat just enter your required beats per minute
> > divided by 16 into the "Bars per Minute" field.
> >
> > regards,
> > sebastian mecklenburg
> >
> >
> > If you choose BPM instead of measures per minute though, one machine can be
> > running 12/8 and the other 4/4, and stuff will still line up/tend to make
> > sense.
> >
> > You may want to consider calling the "Wholes pause at Start" something
> > else, because it's slightly unclear, and also grammatically incorrect (not
> > trying to be hard here, totally just trying to help it be a better end
> > result). "Whole Note Pause", or maybe "Whole Note Offset" might be more
> > appropriate. I appreciate the reasons why you chose that function and agree
> > with them, but it might be even handier if you had one initial offset
> > that's beat based, and in subdivisions of quarter note (or preferably 16th
> > or 32nd notes) not just whole note or nothing, and then also had a
> > millisecond based offset to help with tweaking latency issues.
> >
> >
> > On 29.09.2011, at 11:15, Stuart Warren-Hill wrote:
> >
> > > Hi
> > > I like the idea, I could definitly use a step sequencer patch.
> > > I would like it to have Beats per minute 'BPM' rather than Bars per
> > > minute.
> > > I need a 16 beats to the bar step sequencer. will this do this?
> > >
> > > Thanks
> > >
> > > Stuart Warren-Hill
> > >
> > > Hexstatic / Holotronica
> > >
> > >
> > >
> > > On 29 Sep 2011, at 09:22, Sebastian Mecklenburg wrote:
> > >
> > >> Hello, thanks for your reply.
> > >>
> > >> On 29.09.2011, at 09:23, Achim Breidenbach wrote:
> > >>
> > >>> - Rename "Wholes pause at Start" to "Delay", this tells me more about
> > >>> what is does.
> > >> "Whole pause" is a musical term. A step sequencer is a musical device so
> > >> I chose to use musical terminology. Maybe I should change that naming,
> > >> but the pause is relative to the tempo, i.e. to the length of a whole
> > >> note. This is important to be able to synchronize several step
> > >> sequencers. If you would have to specify a delay in seconds you would
> > >> have to fire up a calculator and do loads of ugly calculations every
> > >> time you use this patch. So "Delay" wouldn't be a good choice either.
> > >> Hmm, I'll think about it.
> > >>
> > >>> - "Pattern doesn't change" is something you should check yourself
> > >>> within the patch.
> > >> Well, I guess you are absolutely right on this one. This would increase
> > >> the computation cost by a simple string compare every time the patch is
> > >> executed, which is neglectable.
> > >>
> > >>
> > >>> - I would recommend not to "min/max" your inputs ("Bars per Minute" and
> > >>> "Wholes pause at Start"). Currently I am not able to put in a delay of
> > >>> 10 seconds. If your patch is depending on min/max values for a certain
> > >>> input, but I can't see a reason why I shouldn't have a delay of 10
> > >>> seconds (or any other number).
> > >> Again I followed the music customs here. With a time signature of 4/4
> > >> and a tempo of 300 bars per minute you get a tempo of 1200 beats per
> > >> minute which is by far faster than any song ever written. But maybe
> > >> people are not using it for music only. My rationale about the delay was
> > >> like this: When you specify a delay of 1 you could just as well rotate
> > >> the pattern by one. But, come to think of it, this doesn't really make
> > >> sense, maybe someone wants a pause of a whole bar at the beginning or
> > >> so. So I guess it's ok to specify these two values in a range of [0, ∞).
> > >>
> > >> I implemented the changes and uploaded the new version to control.my/qc
> > >> again.
> > >>
> > >> Thanks and regards,
> > >> Sebastian Mecklenburg
> > >>
> > >>>
> > >>>
> > >>>
> > >>> On 28.09.2011, at 20:50, Sebastian Mecklenburg wrote:
> > >>>
> > >>>> Hello Group,
> > >>>>
> > >>>> I wrote a simple step sequencer patch as a part of a larger project
> > >>>> (which is not finished yet) and want to make it available to the
> > >>>> community. Since i just started using qc and writing qc patches I
> > >>>> would like to hear some feedback about it's usefulness.
> > >>>> You can download it from control.my/qc
> > >>>> This is beta software located on my new (i.e. also not yet finished)
> > >>>> beta site, so please do not yet link to it from somewhere else please.
> > >>>>
> > >>>> Thanks and regards,
> > >>>> Sebastian Mecklenburg
> > >>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list (Quartzcomposer-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
