On Thu, 20 Aug 2020 16:33:54 -0400
"D. Michael McIntyre" wrote:
> On 8/20/20 1:40 AM, david wrote:
>
> > Also, RG experts correct where I'm wrong - but aren't rests calculated
> > rather than being actual events?
>
> Under most circumstances, rests are just calculated to fill empty space
On 8/20/20 1:40 AM, david wrote:
Also, RG experts correct where I'm wrong - but aren't rests calculated
rather than being actual events?
Under most circumstances, rests are just calculated to fill empty space
on the fly.
I've been way too overworked to do more than glance at this thread,
On 8/19/20 1:02 AM, krsg...@trixtar.org wrote:
On Tue, 18 Aug 2020 19:19:00 -1000
david wrote:
On 8/18/20 3:26 AM, krsg...@trixtar.org wrote:
Whenever a midi instrument is used to lay down a midi track (next imported into
RG) there are the inevitable inconsistancies like an 8th note
On Tue, 18 Aug 2020 19:19:00 -1000
david wrote:
> On 8/18/20 3:26 AM, krsg...@trixtar.org wrote:
> > Whenever a midi instrument is used to lay down a midi track (next imported
> > into RG) there are the inevitable inconsistancies like an 8th note repeated
> > in the next bar becomes a 16th
On 8/18/20 3:26 AM, krsg...@trixtar.org wrote:
Whenever a midi instrument is used to lay down a midi track (next imported into
RG) there are the inevitable inconsistancies like an 8th note repeated in the
next bar becomes a 16th plus a 16th rest. Is there a way to clean this up by
asking RG
Whenever a midi instrument is used to lay down a midi track (next imported into
RG) there are the inevitable inconsistancies like an 8th note repeated in the
next bar becomes a 16th plus a 16th rest. Is there a way to clean this up by
asking RG to feed rests of a certain duration or less to
