XITE1+Scope5.1+das-f07 // DSP HOT BUG

[Spielraum]

XITE1+Scope5.1+das-f07 // DSP HOT BUG
had to buy the nice f07 for xite, but xite crashed DSP when load preset
anyone help?
(connect only on DSP2 is to small for this fat dev)

garyb,
can you help me?
plan b:
'sn' for my pulsar-boards?

[garyb]

any error messages?
can you provide a screenshot?

[Spielraum]

BUG_F07 (DSP-Error) (WinXP_SP3-XITE1_Scope5.1-2015_09_24).JPG

[Spielraum]

BUG_F07 (DSP-Error) (Win7_x64-XITE1_Scope5.1-2015_09_24).jpg

[garyb]

it's not a bug. it's that you need to assign dsps for that device. all the connections between dsps are already used in the configuration you are running. moving that device or another device to another dsp would fix the problem. try reducing polyphony to get everything to fit, then move the dsp load around a bit.

everything has a limit.

[Spielraum]

F07-Benchmark (WinXP_SP3_x86-XITE1_Scope5_1).JPG

after delete mixer "STM1632"
the DSP-power auto-link main part from DSP-c to DSP-h,
and now, no more crash...
also without manual DSP-connection or Voice-limiting

conclusion > from bug to benchmark
or "STM1632" is XITE-bugi


edit: after delete reload mixer before benchmark-test

[garyb]

no, you're supposed to get that message when you use all the sat connections between dsps.

try moving the synth to another dsp. i believe there is a map here of the dsps and their connections. perhaps someone can point you to it.

there are different types of resources and all of them have limits. if all voices of the synth are on one chip, it's all good, but if you raise polyphony and then the load gets split up by two or more chips, then the limited number of connections between chips comes into play, especially if there is a mixer taking up the same real estate. there's no mixer bug.

just put the synth on one of the almost unused dsps on the other end of the board. it's all about how the load gets distributed. there is an algorithm for how things are loaded, but there's no way for the engineers to compensate for every possible order that every possible mix of devices users might load. yes, the order that things are loaded in matters, as far as what resources are available. you can shuffle dsp assignments by right clicking on a device and following the prompts. normally, you wouldn't need to mess with the automatic assignment, but sometimes it can be helpful.

it's possible that other mixers may handle resources more efficiently or in a different manner and might not even have this conflict, but that's not because of a bug. this is the first time ever that i've seen this complaint, but i don't think it's that surprising.

[Spielraum]

try moving the synth to another dsp. i believe there is a map here of the dsps and their connections. perhaps someone can point you to it..

no understand,
FAT Synth on 1 Dsp?
>> and then down to 0 Voices??
whats that...

or can i select multible DSP: from>to?
ok, i wait on Scope6

[garyb]

no, in an XITE, you can right click on a device's module and choose dsps.

[Spielraum]

no, in an XITE, you can right click on a device's module and choose dsps.

but only one!
when new open popup, then only new connet, no add dsp
- thats wish for next update...

...or I have a flaw

[garyb]

have you contacted DAS?

[Spielraum]

NO
is dsp-spread a DAS prob?

[garyb]

that's the only plugin that has that problem, right?

[Spielraum]

that's the only plugin that has that problem, right?

oh gary, always in the wound
...all old creamware-products without major-sc-update are not correct dsp-spread
specifically the seq-Themes... but this is a other xite-prob
zarg-devs are also very fat and critical...
correct auto dsp-spread is indispensable for a creative workflow!
wish: system-button to refresh project dsp-spread without reload or after dsp-crash

touch everything with kid gloves
...when run without error, then render immediately to wav-stem,
although inflexible but surely,
thanks to the cheap bits and bytes

[garyb]

you have a choice. less dsp, less flexibility and more automatic loading, or more power, more flexibility but you have to think about how you load some stuff. for crying out loud! the Zarg stuff you are talking about was made like 12-15 years ago! Zarg would have to rebuild those devices for them to be perfect.

there is a reload button, it's called global optimization. it's offered when that can easily be done. otherwise you have to spend a moment and find the best configuration. another way is to change the clock from master to slave and then back again(or vice versa) this will reload dsps. it may or may not help.

[dante]

try moving the synth to another dsp. i believe there is a map here of the dsps and their connections. perhaps someone can point you to it.

A map is here, but I don't think it will necessarily fix your issue @Spielraum, which I agree with GaryB seems more related to trying to get your system to do too much re interconnections.

http://www.hitfoundry.com/issue_07/xitemast.htm (DSP Layout (Graphical) )

this is also usefull :

http://www.hitfoundry.com/issue_22/dsp_mast.htm

[Spielraum]

thanks for the interesting info about the great DSP concept
i'm dsp-friend since 1992 atari falcon, since 2000 Pulsar1
and i love the modularstructure
... but i´m musican and producer, not technique-nerd

please, understand me
when I cry anyway about the XITE-DSP-philosophy
because the usage is low, that is my musical analysis

audio driver i/o
midi driver i/o
1x mixer
only 1x synth

@garyb
zarg bundle for me 2 years, not 15
2013_09_23-JOHN BOWEN Special_Collection
date to buy as NEW (not old)
found no info in store about the age, example no more supported or run instable or so...
the price was super friendly (many thanks), so i'm not angry, but interested in a modern solution
within the meaning of all SC fans
please understand

[Bud Weiser]

... XITE-DSP-philosophy ...
... the usage is low, that is my musical analysis

audio driver i/o
midi driver i/o
1x mixer
only 1x synth

In DSP meter window, click %,- it shows how much SAT connections are in use in percent.
The graph-bar showing DSP load on XITE-1 has nothing to do with SAT connections (communication lanes w/ old DSPs and computer).
Depending on device, you might run out of SAT connections far before you load more on XITE-1.
In theory, you can load over 90% on XITE-1 DSPs but in real world and because running out of SAT connections, it´s approx. 60-70% in most cases (projects).

You have something creating very high "sync" value on DSP#18.
Move that device to DSPs #7, 8, 9 or 10 because these are the top DSPs in each of the 4 DSP slots (array of 3 DSPs).
Try finding one of these showing lowest load in % !

DSP #18 is the last one in slot 4, o.k. for any device not needing more than 1 DSP, bad for others spreading their load across several DSPs (in a slot).

B.t.w., when using originally monophonic synths like they were in hardware,- Minimax, Prodyssey (2-voice) and ProTone and use ´em the same way in software,- you can assign all 3 to just only one DSP and it will be fine.
Profit-5 is fine w/ 6 voices on only 1 DSP and there are more working that way,- Prodyssey 4-6 voices too, depending on patch.

@garyb
zarg bundle for me 2 years, not 15
2013_09_23-JOHN BOWEN Special_Collection
date to buy as NEW (not old)
found no info in store about the age, example no more supported or run instable or so...
the price was super friendly (many thanks), so i'm not angry, but interested in a modern solution
within the meaning of all SC fans
please understand

I bought that bundle too,- it´s disappointing according to the big synths like Solaris v5, QuantumWave, RotorEX.
They all need too many SAT connections and were´nt made w/ XITE-1 as also not SCOPE 5 in mind.

John doesn´t or didn´t own a XITE and never developed w/ SDK5.
There was discussion w/ John here and over @J.B. Synth Design forum already, so I know well.
Also multiple PCI card systems don´t run perfect w/ p.ex. Solaris v5 and on a 15DSP PCI card you might get 2 voices, maybe 3 w/ simpler patch.
In general there aren´t enough communication lanes available for Solaris v5 on CW and S|C DSP systems.
It works in J.B. Solaris hardware synth because it doesn´t use a computer as a host as also not some older SHARC chips like we have in XITE-1D and XITE-1.
The old chips are for communication between the Xbox ( and/or PCI card) and the computer and that´s the bottleneck unfortunately.

The smaller ZARG devices like Ambient SC, DarkStar, Orion Custom and CombPlus Pro, they all work mono- and polyphonic and sound excellent.
ZARG ProWave and ProOne v3 work too on both the XITE-1D and XITE-1.

You also better use STM2448X than STM1632X.
I don´t know why, but STM1632 doesn´t work that smooth on XITE as STM2448 does and even it is a bigger mixer.

Bud

[JoPo]

I'd like to know if in the Example DSP setups part of the Hitfoundry page :
http://www.hitfoundry.com/issue_22/dsp_mast.htm
less ressource are in use by adding the micromixer, since there is 2 communication channels instead of 6 ?

(I'm wondering if I didn't asked this already... )

Thanks !

[Spielraum]

error messages at use 10% ??
scope can not make balanced project DSPload after load dev or voicenumber etc?
thats my question and wish

see previous example:
start project connected dsp-main-load on dsp 13
after reload on dsp 18, etc.
why only one dsp?
xite have 1-18 or not?

connect dev to only 1 dsp is no solution,
when like play a chord with release...
sorry, tested it over and over again the last years,
but ever with follow overloaed messages or so
despite lower overall utilization
Ferrari used as VW

ps.: i have interesting old realtime native software (no longer supported) on my 12 core cpu
it uses only one core, runs slowly, but without constant error messages...
thats better for workflow, really!