Hi,
Since I'll be away for a couple days, I'm gonna go ahead and reply to this
one instead of waiting for Jakob to reply with, "What?? Are you crazy??"
:-)
On Fri, 24 Jul 2009, Gabriel M. Beddingfield wrote:
>
>> Very good idea! Inputs hould have to use _either_ ticks or ms/frames, though,
>
> I was thinking ticks + ms for Inputs.
>
Let me explain this one a little more, since I'm not dead set on ticks +
ms... and I think I've changed my mind. Also, I need to hunt down the guy
who did lead/lag and give him a hug or something. Lead/lag is the coolest
thing in H2.[1]
Currently, H2 sequences schedule things like lead/lag and "humanize" based
on audio frames and ticks (I don't remember which does what). Further,
the user edits lead/lag by setting it to "a little before" or "a lot
behind." IIRC, the behavior of these things change when the sample rate
or even the tick size changes.[2]
However, when I'm editing a sequence, I want better control over these.
On the whole, I think I would prefer if I was editing lead/lag in
milliseconds OR ticks.
Reason for milliseconds: If I have a sample of a snare drum 'ghost' or
'dittle' hit, want the hit to lead or lag the beat by a specific time. If
the tempo changes... this type of thing won't scale with the tempo.
Reason for ticks: If I'm doing a hard rock mash... I want the high-hat to
lead the beat a little bit. I *think* I want it to scale with the tempo
(but I'm not sure). In that case, I'd want the lead/lag to be edited in
ticks.
So... what I *really* want is for .h2song to store <leadlag
units='ms'>65.3</leadlag> and/or <leadlag units='ticks'>2.1</leadlag>
(user gets the option).
Looking at SeqScript, when adding notes, SongSequencer can translate the
millisecond lead/lags to the current tick size. If a tempo change happens
after the note is scheduled... then they won't *quite* happen at the right
time... but I think it will be close enough.[3]
If we do ticks + ms... then we can keep it accurate even during a tempo
change... but at the cost of more complexity.
So, I'm now in favor of floating-point ticks... not ticks + ms.... but I'm
still mulling it over. What are your thoughts?
Peace,
Gabriel
[1] I was working on a funk groove, and I needed a
hard rock mash. Kick on 1 & 3, snare on 1 & 4,
half-open high-hat 8ths. Without lead/lag, it
sounds like... well... MIDI. :-) WITH lead/lag,
it sounds freaking awesome.
[2] Tick size doesn't currently change in H2, but it
might in the future.
[3] Suppose tempo is 80 bpm with 48 ticks/beat. I
want a 100 ms lead... which translates to 6.4
ticks. After being scheduled, the tempo changes
to 180 bpm. 6.4 ticks is now 44 ms (for an
error of 66 ms). "They say" that 20 ms is the
minimum delay that a human can perceive.
------------------------------------------------------------------------------
_______________________________________________
Hydrogen-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hydrogen-devel
