Yes, that´s what I know and what I do,- but it would be an improvement when having better visual control about DSP placement,- especially when a project is already re-loaded and the "auto-optimize" algo had done it´s work,- the work it always does when loading a project.fra77x wrote: //You can use the DSP Load and your intuition. It's not complicated, it's straightforward. If a device-module is forced to load on a specific dsp then it loads on that one. If it can't loads (doesn't fits) it will pop a dsp error.
In addition, it´s not only me,- there are more users and potential buyers out there who´d like it simpler.
Not all users want to learn reading cryptic DSP meters, you know,- they want selecting a device from the SCOPE pulldown menue, throw it into a project, drag the cables and see it working instead dealing w/ all kind of weird messages.
When we had info which devices went to whatever DSPs after a formerly saved project is loaded again,- it would be much easier deciding how to assign next devices coming into that project.
I understand very well what you´re talking about,- but the average user/musician is not a developer and all he wants to do is paying money for a system and using it.fra77x wrote: //The most important is to understand that communication between dsps costs in communication channels but several devices loaded on a single dsp cost NO communication.
No one can expect the average user wants to learn what happens under the hood of DSP powered devices,- I do because I have lots of technical interest and you do because you develop devices,- but the average Joe doesn´t.
Good advice, because I normally click O.K. and NOT CANCEL when the system asks if I want optimization of my project.fra77x wrote: //When scope ask to "optimize the project" always press cancel. And delete the last module you added.
It´s nowhere in the manual and what BS it is when I click o.k. and from that point cannot remove anything anymore, nothing gets optimized and the s##t simply freezes for 2 minutes or such until I´m able to cancel the process and remove device.
We also need more or less unified devices for XITE-1.
When loading ZARG NSA devices,- I already get all kind of messages and popups because the devices look for data in folders which doesn´t exist on my machine.
There is simply no SFP on drive C because I have SCOPE 5.1 32Bit for XITE and it is impossible to change path in the ZARG devices.
Some presets request files which aren´t present in any zip package I downloaded for the installations, even not in these Jhulk offered later for download from his dropbox,- and I don´t mean the thing-A and thing-B samples which are in my samples folder but not under SFP on drive C.
I hope that´s correct and wonder why I cannot see p.ex. greyed out DSPs in the manual assignment pulldown DSP menu when a DSP is saturated already.fra77x wrote: //What means to optimise the project? It means that the algorithm will seek for any devices that are NOT assigned manually to some specific dsp, and try to assign these in a different manner so to find space for the module you last inserted. Manually assigned modules are not affected by "optimization" . These always stay where there should.
In fact, when a project is reloaded and I want to bring in more devices and assign manually,- it would be great help recognizing already occupied DSPs in this pulldown menue.
I hope so ...fra77x wrote:
//With proper manual assigning of the devices and organized interconnection between devices (connected group of devices at the same dsp and fewer traveling of signals between different dsps i.e by using submixers) you will first run out of windows space and "brain cycles" than from communication channels and dsp power.
Thx, good news !fra77x wrote: //It does always. At least the last 3000000 times i checked that.
Thank you,- John !fra77x wrote: //Always press cancel to the "optimize dsps " window. Then try to find with manual assigning the one that works.
Regards,
John
Bud
DSP resource distribution algorithms != music/mixing/mastering
