by Liquidedge » Wed Jan 29, 2020 4:17 am
John Bowen wrote: Mon Jan 27, 2020 8:13 am
Unfortunately this has nothing to do with the plug-in construction, but rather, the sequencer module itself, over which I have no control.
Ah annoying. I suppose if holger gets that module/atom to work correctly on Xite the Solaris could be re packed to include fixed module?
Or, from what I understand by what’s been told to me, sequencer stuff that’s built around sync rather than async work fine on Xite. Could maybe the sequencer stuff be swapped over to that?
A third option, that’s probably not so reliable, is that these seq modules work fine on dsp2 on Xite. OSS did it with one of there synths, where there is an Xite version where the seq modules are locked to dsp2 in the code or something.but that’s more of a bandage type solution as sat issues get run into earlier!
[quote="John Bowen" post_id=23542 time=1580141621 user_id=2]
Unfortunately this has nothing to do with the plug-in construction, but rather, the sequencer module itself, over which I have no control.
[/quote]
Ah annoying. I suppose if holger gets that module/atom to work correctly on Xite the Solaris could be re packed to include fixed module?
Or, from what I understand by what’s been told to me, sequencer stuff that’s built around sync rather than async work fine on Xite. Could maybe the sequencer stuff be swapped over to that?
A third option, that’s probably not so reliable, is that these seq modules work fine on dsp2 on Xite. OSS did it with one of there synths, where there is an Xite version where the seq modules are locked to dsp2 in the code or something.but that’s more of a bandage type solution as sat issues get run into earlier!