DNA makes cool stuff, we don't want to annoy him any further, i made here a new wish pool
>DNA patchbay,- label issue
>> Device/Module Wishlist
Bud Weiser wrote: ↑Thu Aug 06, 2020 7:53 amI tried using DNA patchbay in SCOPE v7 x64, Win7 Pro SP1 64Bit.
When I save the patchbay´s settings and routing as a preset, recall the project and DNa patchbay preset list as well, then load the given preset,- patchbay forgot it´s name and I/O labels (p.ex. Mix L+R, CtrRoom L+R, Bus 1-8, ASIO D 1-10, Z-Link 1-8 and so on) .
Any explanation ?
Do I something wrong ?
Bud Weiser wrote: ↑Thu Aug 06, 2020 5:22 pmWell, I tried to achieve STM 24/48 busses to get routed to ASIO OR Z-Link via Dna patchbay and by switching between 2 Dna-patchbay presets,- and all inside the same project which I made my default one incl screenset.
But already when I recall the 1st preset doing the routing to ASIO,- patchbay´s name and names for patchbay´s inputs and outputs are gone while routing is intact.
The upper label row still shows numbered sources and lower row shows numbered destinations.
User colors are recalled though.
2nd level upper row (devided in pairs) show "XITE" in every label area.
Before I created the preset, I named I/Os like (inputs) Mix L+R / CtrRoom L+R / Std. L+R, STM-Bus 1 (... ´til and so on,- and for outputs:
ASIO 1+2 / 3+4 ... 7+8 or Z-Link A or B-1 ... 8.
(XITE) anal.L+R, phones and AES/EBU too.
But when I recall,- all gone.
yayajohn wrote: ↑Sat Aug 08, 2020 2:13 amMaus has a couple you can try.
viewtopic.php?f=16&t=34758&p=344530&hil ... vu#p344530
Spielraum wrote: ↑Sun Aug 09, 2020 11:43 pmhey bud, routing is more complicated than we think.
the sources and targets receive temporary IDs, which fortunately are saved in the project. this makes recall possible. the preset engine v1 + 2 cannot save any IDs. With the connections, the names of the counterparts are also readed. these are mirrored in the text field. DNA should have write-protected the text to "READ" fields only. There are no additional "write" fields (note), as in the mixers, not even in MAUS iPatch, i think. his iRouter has, love this toy, but unfortunately i quickly get SAT probs here on XITE.
if the text"READ" fields are empty, but the connection is available, then there are apparently double assignments or splits. Note that name-logic need only "one" source refers to only "one" goal! sorry, multiconnection can empty the string after project reload.
Tip: for wireless connections, e.g. meterbridge, look for the connection with DOT [*] in the dropdown menu.
Warning: the "none" button does not always work (probably if the structure tree logic is inconsistent)
that's all normal scopydoo flexibility that i love sooo much!
maybe i'm completely wrong, because i'm not a scope programmer and i get my knowledge through try and error
# perhaps the routing in scope v8 will be even more flexible and can be saved in presets? anything is possible. by the way, that would be one of my greatest wishes!!
Bud Weiser wrote: ↑Tue Aug 11, 2020 2:19 amHello Spielraum !
Thx for all the info !
Very interesting in deed.
Yes,- changing multiple routings on the fly within a given project and via MIDI PrgCh. commands recalling presets would be awesome.
In fact It´d replace hardware units like the old AKAI MB76 I love and still own.
As a reminder,- that was/is a 7-input/ 6-output MIDI controlled audio matrix switcher which allowed multi-connections and there were 32 preset memories for recall.