Moduut

[Liquid EDGE]

Nice one. Thanks a lot.

I love the Void2 synth. Glad they are not going anywhere, just on a temp re make .

[Bud Weiser]

In Scope Xite software you can't really see exactly where each module is loaded but in sdk you can.

That´s why we´d need some kind of information tool showing what is loaded on which chip and how these chips are interconnected communication wise IN THAT configuration of a/the project.
That should be available once a already programmed project is re-loaded.
Up to now, we don´t see what´s going where when the formerly saved project will be loaded again.
Some kind of, then extended, pull down list, we already use to assign to DSPs manually, could be used for this,- it should show which DSPs are already occupied by what and how much DSP power is free (left over) per chip.

And some times they get span to 2 or more dsps.

Yep, that info should be available too in such a list mentioned above.
I see that when maxing out voices in DSP and SAT % and as long there aren´t too many devices in the project window, but at some time the DSP spreads across almost all chips where some more DSP power is available and as long SAT connection errors won´t come up.
It´s not very clear what has priority,- the available DSP power or the count of SAT connection when auto-optimization kicks in.
It seems it all depends on the algorithm used, isn´t it ?

Also if a module is loaded for example in dsp 17 and is connected with another module in lets say dsp 16 and back to dsp 17 or somewhere else, then that costs in communication and leads eventually to SAT errors.

That´s it,- you run much earlier out of SAT connections then out of DSP power.

But you can assign them manually (right click -> assign to dsp Y) and it works fine... A whole pack of modules interconnected on the same dsp take no communication resources. Ok it's self-evident. That's it...
Regards

Well, that´s easier for you because you have that visible control in SDK.
Without that control,- it´s much harder to decide which device should go to which chip just because the DSP/SAT/% meter becomes irritating after some time.
You see where load and SAT connection rise but don´t see which devices cause that.
It´s comparable to devices in the project being shuffled around the DSPs as long as the project is up and running and when more devices are been loaded,- just to optimize the count of SAT connections.

Also, I´m not sure if manual DSP assigned for a given project you work on is memorized perfectly once the project is recalled later.
I fear it´s not exactly the same then,- but it should.
Otherwise the "shuffeling devices around DSP chips" by "auto-optimize" starts again.

I imagine it´s hard to find criteria for an auto-optimizing algorythm in general.
Maybe there should be a on/off switch so the user can decide to manually assign only and then can be sure the project loads exactly the same again.

Bud

[Bud Weiser]

Leave it assigned....

Lot´s of useful info in your posts b.t.w.,- thank you !

Bud

[fra77x]

--

[dawman]

Great tip on VDAT.
I always put ASIO on 1 and VDAT on 2 and seemed to be OK, but this seems to improve things, and you confirmed my suspicions about the "cancel" tip on the Optimize Project messages. I always say no, then try to rearrange things.

Also I wanted to say thanks but I noticed I can't see the modules GUI to change parameters with the exception of HP EQ, and MasterVerb...
I always double check by deleting the routing window and collapsing the Live Bar as sometimes they are off to the side or hidden, but just thought I'd tell you what I am seeing.
Would really love to see the SAL Chorus SDRAM for editing purposes.

[fra77x]

-0i

[dawman]

OK, thanks John.
Just tried that and it worked. Excellent.
I always get worried when I load something and it doesn't show up in my Live Bar.
I am on the Chorus as we speak.....

CiaoMein

[fra77x]

---

[dawman]

I have to finish my newest way to use Solaris live this weekend,
and MIDI FX Switch has really been helpful, but I couldn't find a
really clean chorus.
I love the color of such FX but on synths, detuning is usually my
preferred choice.
However I noticed how the signal is not phasy/colored, and reminded
me of my Ensoniq DP4 I use to use Post analog mixer live years ago
so I decided to try something, and now I am quite satisfied.
I was ready to sell Solaris and the XITE-1 after learning they were half
full jars.
Thanks for filling my jar more and saving me from that back of the cone
sound that plagues Native synths on larger midfield monitors and full
systems controlld by FOHs...

Sweetness.JPG (53.17 KiB) Viewed 6586 times

[fra77x]

-0-0

[dawman]

I do have a question though.
Is the clarity I am hearing because of the SDRAM?
I just finsihed using several other Chorus Devices and the 4 clearest choices
are your Module and RoyTs Flanger/Pitch Shift modules.
These IMHO are too clean to use on samples, i.e. A Fender Rhodes sound
through Flu-Liq, Modular Choruses, and other Scope FX, Nuetron ADT, etc. are my
choices as the coloring is georgeous and well suited.
I am very pleased as I have flip/flopped w/ chorus FX for years, to the point of using
no Modulation, but the PShifters and your Chorus are perfect for synthesizers.
Is this possible due to the SDRAM...?

Thanks Again

[fra77x]

--

[dawman]

I think the latter maybe. As the more delay brings me into more coloring.
I like my rates at .11-.52 depending if it's a Modulating Waldorf Wavetable, or straight waveforms i.e. synthstrings.
Just curious as when I decide to change current choices for new ones, I seem to need
clarification, not that it matters, as long as I can get that DP4/Enevtide thing, I'm fine.

Back To Work

Have a great Sunday

[dante]

From my understanding its all about phase.

Bear in mind a developer may have assigned DSP's in respect of maintaining phase integrity, and with overriding those assignments the onus is then back on the user to test and correct any phase issues.

[Eanna]

This is one of the first posts on planetz where I -truly- said "Damn, I *really* wish I had an Xite"...

Superb work John! Huge respect for high-quality work..
And be sure to be careful with strain. About ten years ago, my buddy (a programmer) ignored stiff tingling in his hand. Ended up doing bad nerve damage. Couldn't work at a machine for nine months under doctor's orders... Also, my friend who did a PhD got herself in a right painful muddle coming up towards the end of her thesis, and ended up spending good money on an ergonomic mouse and keyboard, which she said helped loads....

[katano]

WOW fra, that's the first time i see a Xite-1 maxed out!

[neuromantik]

This is great stuff!! Is there a method or technique besides what you describe for DSP assignment and running SCOPE @ 96Khz? I'm having trouble getting the latter to work properly, and there are many bits and pieces around the forum but it's hard to bring some order from the chaos

[djmicron]

thank you

[dawman]

Well I am going to try the 96k thing again right now.
I know 48k is perfect fine 4 me, and my jar/meter is @ 50%.
I am hoping that at0m's explanation of less smearing of the waveforms in Modular is accurate.
As of right now @ 48k the sound of the XITE-1 is impressive, Solaris is equally impressive, but clarity of signals is what I want to see increase.
Solaris gets this extra punch because it's processing the entire design at a higher rate, not just converting audio.
But less smearing might just equate to even more pristine sound quality.

Wish me luck, and thanks DJMic and Fra77x.
The Stereo chorus is of finest quality I have heard. Even more pristine than the DP4, and on par with the HD5000 Ultra my bassist uses.
That alone justifies my expenditures.

So it took 4 years of making money to figure this out.........fine, maybe I'll get Jurgens ADAT MKII now and treat my bandmates to the beauty of DSP in a live format.
As long as I don't end becoming the BLB, similar to FOH (Front of house). BSB translates to back line bitch..

[mausmuso]

That is fantastic!
This maybe the beginning of answer to some of the connection issues I have had with SpaceF's marvellous Modular Mixer?
Also using VDAT with more than 8 tracks, I could not save the project, maybe this info will fix that little issue?
Thanks for the valuable tips
maus