Re: [LAU] harmonySEQ 0.16

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Rafał Cieślak <rafalcieslak256@...>
Cc: <linux-audio-user@...>
Date: Sunday, February 12, 2012 - 1:56 pm

--90e6ba6e8eded2003804b8c4b98e
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Sat, Feb 11, 2012 at 10:25 AM, Rafa=C5=82 Cie=C5=9Blak
wrote:

> Though I like Fons' suggestion concerning jumping to the nearest bar,

That would be great: Currently there is a bit of drift between the
programs, I reckon its in my own code
as the current transport / beat system is pretty basic and untested. It
will be rewritten at some point to
include JACK transport & BBT, but its not high on the priorites list :)

> Maybe I wasn't clear about the tags - these have nothing to do with

Yes, get you know. I meant consistent across different HarmonySeq projects,
but I realize now that's not possible due to the configurable nature.
Basically
the user will need to tell harmonySeq what it needs to do per scene of
Luppp.

That's the best way to go for now. It works so I'm happy with that! If we
could implement
Fons' beat sync idea (just for beats, sending BPM is no problem) that would
be great :)
-Harry

--90e6ba6e8eded2003804b8c4b98e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Sat, Feb 11, 2012 at 10:25 AM, Rafa=
=C5=82 Cie=C5=9Blak <rafalcieslak256@gmail.com> wrote:

Though I like Fons' suggestion concerning jumping to the nearest bar,
that seems a reasonable solution, will try to implement that once.
That would be great: Currently there is a bit of drift be=
tween the programs, I reckon its in my own codeas the current transport=
/ beat system is pretty basic and untested. It will be rewritten at some p=
oint to
include JACK transport & BBT, but its not high on the priorites list :)=
=C2=A0Maybe I w=
asn't clear about the tags - these have nothing to do with

OSC's own tags, and are indeed predefined, so that harmonySEQ will
react the same manner each time.Yes, get you know. I =
meant consistent across different HarmonySeq projects,but I realize now=
that's not possible due to the configurable nature. Basically
the user will need to tell harmonySeq what it needs to do per scene of Lupp=
p.That's the best way to go for now. It works so I'm happy =
with that! If we could implementFons' beat sync idea (just for beat=
s, sending BPM is no problem) that would be great :)
-Harry

--90e6ba6e8eded2003804b8c4b98e--

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[LAU] harmonySEQ 0.16, Rafał Cieślak, (Mon Feb 6, 3:57 pm)
Re: [LAU] harmonySEQ 0.16, Edgar Aichinger, (Mon Feb 13, 3:47 pm)
Re: [LAU] harmonySEQ 0.16, Rafał Cieślak, (Mon Feb 13, 6:05 pm)
Re: [LAU] harmonySEQ 0.16, Edgar Aichinger, (Tue Feb 14, 10:33 am)
Re: [LAU] harmonySEQ 0.16, Rafał Cieślak, (Tue Feb 14, 6:16 pm)
Re: [LAU] harmonySEQ 0.16, Edgar Aichinger, (Tue Feb 14, 10:21 am)
Re: [LAU] harmonySEQ 0.16, Hartmut Noack, (Wed Feb 8, 5:20 pm)
Re: [LAU] harmonySEQ 0.16, Rafał Cieślak, (Wed Feb 8, 5:55 pm)
Re: [LAU] harmonySEQ 0.16, Fons Adriaensen, (Wed Feb 8, 8:15 pm)
Re: [LAU] harmonySEQ 0.16, hermann, (Wed Feb 8, 8:31 pm)
Re: [LAU] harmonySEQ 0.16, Hartmut Noack, (Tue Feb 7, 8:34 am)
Re: [LAU] harmonySEQ 0.16, PMA, (Mon Feb 6, 8:23 pm)
Re: [LAU] harmonySEQ 0.16, Harry van Haaren, (Mon Feb 6, 8:09 pm)
Re: [LAU] harmonySEQ 0.16, Rafał Cieślak, (Mon Feb 6, 8:25 pm)
Re: [LAU] harmonySEQ 0.16, Harry van Haaren, (Sat Feb 11, 12:29 am)
Re: [LAU] harmonySEQ 0.16, Rafał Cieślak, (Sat Feb 11, 10:26 am)
Re: [LAU] harmonySEQ 0.16, Harry van Haaren, (Sun Feb 12, 1:56 pm)
Re: [LAU] harmonySEQ 0.16, Fons Adriaensen, (Sat Feb 11, 10:08 am)
Re: [LAU] harmonySEQ 0.16, Louigi Verona, (Tue Feb 7, 4:23 am)
Re: [LAU] harmonySEQ 0.16, James Mckernon, (Mon Feb 6, 5:46 pm)
Re: [LAU] harmonySEQ 0.16, mark hadman, (Mon Feb 6, 7:50 pm)
Re: [LAU] harmonySEQ 0.16, Rafał Cieślak, (Mon Feb 6, 7:58 pm)