paterpeter wrote:I tried the x86 version in Reaper x64, using the built-in bit bridge.
No crashes so far. But I noticed that when I arm a track with Cream on it the output becomes uneven (like in Studio One) and I even get pops and crackles in the audio. This gets even worse when I record arm more than one track with Cream on it.
Hmm, pops and crackles in audio are produced by the synth,... Cream is just sending midi data.
I know, but that's what I'm experiencing
Which latency setting do you use? Maybe the bridge is generating cpu hits...
I tried different settings, from 64 to 512 samples (at 44.1KHz) with no difference. The CPU is practically idling the whole time. I tried with four instances of Cream and four instances of Dune. Reaper reports a CPU usage of < 5%, the task manager shows similar results. It's ONLY if I enable Cream and ONLY if record arm is enabled.
Do you mean with "out of sync" completely different timing, or is the output just shifted 1-2 steps behind, but is in sync (=> 1/16) ?
It's not shifted by a specific number of 16ths. It's similar to the results in Studio one, e.g. 16ths aren't played evenly. As if the timing of the notes was heavily humanized.
More feature requests/suggestions/bug reports:
- "Transpose" should always be in semi-tones, not steps in the scale. If a scale is selected, snap note to nearest note in scale.
- Add a per-step toggle to turn on/off snap-to-scale. Default is on. Where snap-to-scale is turned off, the notes are transposed as per transpose graph. Where it is on, the notes are snapped to the nearest note in the scale (if enabled).
- Add a new graph: Probability, which sets the chance whether the note is played or not (see FXpansion's Tremor).
- Shuffle should lengthen the first note and shorten the second note, or at least shorten the second note. Otherwise, monophonic synths won't be triggered correctly even for gate < 0 (because the second note overlaps with the next note)
- The octave knob doesn't work here.
- Add mouse wheel support for step entry
- Some graphs probably should be displays as bars (order, Chordmem). Instead, they should look like "Seq" but with only one rectangle enabled at a time.
- The "Order" sequencer should always display the value of each step.