yayajohn wrote:I can get 16 voice poly on the Minimax, Profit, and Prodessey with my Xite. That's without manual DSP allocation and not having to optimize. These synths were said to have been optimized when the Xite came out, I am not sure what Holger did to optimize them but it worked.
That´s why I said XITE-1 and SCOPE 5.1 works for me w/ S|C stock devices.
Only very few stock devices show (minor) issues I don´t want to discuss here but as an example, STM 2448X works better than all the other mixers when it comes to auto-DSP allocation.
But once you´ve found out what fits best, it works stable and sounds good !
yayajohn wrote:
Working out the allocation of resources on the Xite takes time and some study and some experimentation. Everything comes at a cost. People who are thinking of purchasing one in the future have to rearrange their thinking of comparing it to the PCI's on a one for one DSP usage.
This !
But they also compare it to the behaviour of native DAW and VST stuff and expect the same now from realtime DSP.
IMO, these expectations are the culprit 1st place.
yayajohn wrote:
To those that already own an Xite and it keeps pissing them off, I would recommend you experiment with loading a blank project and load different devices and watch your DSP meter and see what it is doing. A lot of times it will not do the same thing and will load things differently based on what you load first. If you start getting SAT messages and such then sometimes it is best to back off your load by a high margin and start to load it again.
QFT !
But,- that DSP meter doesn´t show you everything, even it helps.
I often see 100% SAT connections w/o having issues and next time I see 100% SAT connections I get warnings, depending on the project build and devices used.
So,- the DSP load itself shown you can trust, but not the column to the very right showing SAT connections in %.
It´s hard to decide what to change in a given project once error warnings come up.
Sometimes, you cannot do anything because the response of the project is so slow, you think it´s frozen already and even it isn´t.
The problem w/ the DSP meter is, it doesn´t show you which device(s) is/are allocated to which DSP once you did any manual DSP assignment and then cleared the assignment.
It also doesn´t show what´s assigned where when you did NO manual DSP assignment at all.
And once a successfully built project is re-loaded later, it doesn´t tell you what´s re-shuffled to where.
So, when you get a warning message, reporting there are no more SAT connections available between DSP #X and #Y, you´re lost because you have no idea what to remove and what to re-load to where for project optimization.
Optimizing the DSP allocation- and SAT connection meters, both giving better info (may be appearing in the warning windows text) would be a step forward.
I imagine some kind of graphic showing which device consumates what amount of DSP power and percentage of SAT connections on which DSP, p.ex. by showing the device´s name inside the graph.
Dunno how to realize, but would be cool !
Since I guess most 3rd party devices available aren´t optimized for XITE-1 and SCOPE 5.1, the above would be big help using the feature of manual DSP assignment,- thus user-optimization of projects.
yayajohn wrote:
I have only reached a "maximum" DSP load on the Xite a few times but it was a combination of effects, mixers and synths.
I have
never reached the max. DSP on XITE-1 that way and even I created big projects w/ S|C stock devices for XITE-1.
The max. DSP was about 60 - 65%, never more.
But I was able running out of SAT connections much, much earlier and when using 3rd party devices in a project.
These were not strtikly ZARG, because the smaller ZARG synths work.
And when I say "smaller", these are still not so tiny toys,- think Ambient sc, Orion Custom sc, even Prowave and others.
yayajohn wrote:
You will definitely run into SAT errors if you load up your mixer inserts because it will naturally want to load those on the same DSP as the mixer is on.
As a keyboard player and for the synth projects, I never did that because many synths come w/ their own FX.
I used the aux- sends and -returns though.
yayajohn wrote:
What I have been more successful at is using the AUX outs and manually placing high load effects like reverbs and delays on their own DSP's.
This !
But nonetheless, I build projects w/ a single modular or a single big ZARG synth alone, then ran out of SAT connections even not using any insert- or aux-effect nor using a mixer at all, no ADAT or ASIO, just only XITE MIDI-In and going directly from modular or single big ZARG synth audio outputs to XITE-1 main out.
When loading p.ex. HPM control pack between output of modular/ big Zarg and XITE-1 analog out, it happened already !
yayajohn wrote:
Also keep in mind what has just been mentioned here with how the slots are laid out.
All of this has been discussed at various time here and there is more technical info posted on Scoperise.(thanks to dante)
I do that all the time and from the very beginning since I own XITE.
Before I used it and because I were at PlanetZ before I bought XITE and as an owner of a 15DSP PCI card too, I investigated for optimized DSP assignment.
I have a shortcut to that DSP layout pic in my taskbar, so when building projects, I have a look at it when in need.
yayajohn wrote:
The Xite is imho the best bargain out there. No it can't do everything, it does some things really great and some things not so really great but I dare you to find a one box solution that covers so much ground for the cost than the mighty Xite-1.
I agree !
And I´d say: XITE-1 and SCOPE 5.1 can do almost everything advertised, but not everything SIMULTANEOUSLY.
Anyway, the biggest issue for me is the reliable and permanent storage of MIDI presets/ MIDI CC assignments for any device used in a project.
If that would be fixed one day, that would be a big step forward for me.
Bud
