SOLVED: Inconsistent playback, found a repeatable bug.

[Architeuthis]

Set rate to 1/16D, turn off every other step in the chord tab:

[ ][off][ ][off][ ][off][ ][off][ ][off] etc.

Set your host to loop one long midi note. Every 3 times it loops, it will sound the same. Every 2nd loop of those 3 will be the correct playback.

kirnu_bug_inconsistent_playback.wav
kirnu_bug_inconsistent_playback.RPP (add your own synth)

[Kirnu]

Set rate to 1/16D, turn off every other step in the chord tab:

[ ][off][ ][off][ ][off][ ][off][ ][off] etc.

Set your host to loop one long midi note. Every 3 times it loops, it will sound the same. Every 2nd loop of those 3 will be the correct playback.

kirnu_bug_inconsistent_playback.wav
kirnu_bug_inconsistent_playback.RPP (add your own synth)

I don't think this is a bug but a feature you have to know how to use.

Please glue all your items in the project and join the notes so there will only be one long note.
Record the output and see that Cream behaves correctly.

The problem is that when using uneven rate values they don't snap to the beat.
Using of long notes is recommended in this situation.

-Arto

[Architeuthis]

Yes, when I use a long note it indeed behaves well. However, I still think there's something undesirable in Cream's behavior. Firstly you should notice the first note of the pattern, when it lands on the 2nd of ever 3 bars, the first note is squelched, the gate length is really short, it seems to be getting cut short.


kirnu_bug_inconsistent_playback2.wav

If I set "Start notes immediately" and have midi that starts on the first beat, I expect the pattern to reset itself so that the first midi note from Cream is on the first beat.

However, this is what happens instead: The arbitrary position of the midi in relation to the host time will dictate where the beat lands INSTEAD OF the actual midi dictating it. Sometimes it will start on beat and sometimes it won't depending on where the midi is placed in the host.

I expect the pattern to reset itself when it recieves a new note, but the pattern does not reset itself. It only repeats every 3 bars.



Edit: Let me rephrase that. Yes, IT IS ALWAYS ON BEAT! It's just not always on the *right* beat.

[paterpeter]

I can confirm that this behavior is a bit weird.

If I set a rate of e.g. 1/8D I'd expect the pattern to reset each time a new note is played. Instead steps are constantly emitted within the ongoing 1/8D rate. "Start note immediately" only forces an additional step to play as soon as a new note plays (if the start of the note does not coincides with a 1/8D note).

Maybe there could be an option to make "Reset on new note" also reset the rate clock.

[Architeuthis]

paterpeter, which version of Cream are you using? This issue has been solved. I'm not sure if Kirnu uploaded the latest version yet.

The only problem I still see that could be improved upon is the automatic quantizing of midi sent to Cream. If the midi isn't right on or very close to being perfectly quantized, Cream will skip a beat with 1/8D and other odd timings. But, I don't want to report this other bug until this first bug has been officially solved for the public, as this original bug needs to be dealt with first before we deal with the next stage of this bug/feature.

Paterpeter, I'll make sure it's reported.

[Kirnu]

The fix for the original problem will be released in v1.0.2

[paterpeter]

paterpeter, which version of Cream are you using? This issue has been solved. I'm not sure if Kirnu uploaded the latest version yet.

I've downloaded the latest version today (1.0.1). I'll see what 1.0.2 brings.