## Translating from SDK-Klingon to Terrestrial

Scope and XITE Development

Original topic on PlanetZ: https://forums.scopeusers.com/viewtopic.php?t=20426

#### Translating from SDK-Klingon to Terrestrial

Posted: Sat Oct 28, 2006 1:58 am
by erminardi
I've found a couple of points, that are for me a bit "blurry" about SDK:
1) when I import a VU meter group (stolen from another device) into my new interface, I can easily link the meters to the VU meter source device, but I can't achieve the "peak hold" feature. Does is, the peak hold, another different device?
2) the user manual and the (very) good tutorial from SDK forum lacks of "interface design" deepening: how to create/manage new animation (like i.e. vintage VUmeters) and hot to import/manage correctly the textures... I've realized a pair of beta devices with several fortuitos experiments that I sincerely cannot conscious repeat now!
3) how I can export the module as *.dev instead *.mdl? The official manual (file management chapter, page 5) shows a menu about this... I can't found it!
4) does exist a list with short description of every circuit/device/surface present in the "packages" folder into SDK program? I've found some similarities with modular modules, but some parameters & behaviours are for me different...
5) same question but about "atoms". Some atom names seems to be very cryptic...
Uh, that's all for now
If anyone knows an easy solution about one or more of these points...
Thanks in advance

####

Posted: Sat Oct 28, 2006 5:29 am
by erminardi
Another question is about knobs curve response, how much curves are available? And the description? I can't find info about it into manuals...
(yeah, I know, I'm a bit "dummy"...)
ps. I'm, now, at 2 beta devices about dynamic... I've some problems vith conclusion (mainly inteface, vars definition & preset list)...

#### Re: Translating from SDK-Klingon to Terrestrial

Posted: Sun Oct 29, 2006 12:24 am
by djmicron

> erminardi wrote:I've found a couple of points, that are for me a bit "blurry" about SDK:
> 1) when I import a VU meter group (stolen from another device) into my new interface, I can easily link the meters to the VU meter source device, but I can't achieve the "peak hold" feature. Does is, the peak hold, another different device?

you should connect the "peak hold" value (in surface mode) to the "p1" pad of the device (in circuit mode)

> 2) the user manual and the (very) good tutorial from SDK forum lacks of "interface design" deepening: how to create/manage new animation (like i.e. vintage VUmeters) and hot to import/manage correctly the textures... I've realized a pair of beta devices with several fortuitos experiments that I sincerely cannot conscious repeat now!

under the gotree panel, you can see all the graphic components of a vu meter and the easiest way is to replace the existing parts of an interface.
If under the gotree panel you select the single parts of a vu meter, then you can replace it by importing your custom design (from the preview panel).

> 3) how I can export the module as *.dev instead *.mdl? The official manual (file management chapter, page 5) shows a menu about this... I can't found it!

when you save the device, choose "all file types" and name the device as .dev

> 4) does exist a list with short description of every circuit/device/surface present in the "packages" folder into SDK program? I've found some similarities with modular modules, but some parameters & behaviours are for me different...

most of the devices are very similar to the modular ones, so it's not so hard to use the most of them.

> 5) same question but about "atoms". Some atom names seems to be very cryptic...

if you look inside the dsp folder there is a short description of some of the dsp modules.

####

Posted: Sun Oct 29, 2006 12:32 am
by djmicron

> erminardi wrote:Another question is about knobs curve response, how much curves are available? And the description? I can't find info about it into manuals...
> (yeah, I know, I'm a bit "dummy"...)

the response curve of a knob is managed from the padlist(min, max, intensity, mod range and so on) and the best way for the first devices is to copy the values from the existing ones.

> ps. I'm, now, at 2 beta devices about dynamic... I've some problems vith conclusion (mainly inteface, vars definition & preset list)...

the shayne white tutorial explains how to create presets....

####

Posted: Sun Oct 29, 2006 1:42 am
by erminardi

> djmicron wrote:

> > ps. I'm, now, at 2 beta devices about dynamic... I've some problems vith conclusion (mainly inteface, vars definition & preset list)...

> the shayne white tutorial explains how to create presets....

Thanks a lot =)
I know, in TD-1 the preset setting works... in LE-1 no! Very strange, I've tried it several times, maybe I should restart from an older level of backup.
In example (regarding point 4) I've found difference from adder and modular adder (A+B/2), in gain12db (I suspect some phase inversion with this dev), etc... in this way it's not so simply to port my old modular schemes into devices.
Maybe I should start to use the basic atom for some functions.
Anyway in one week, with your tips, I've learn several new things, I thin that in one month I can become an expert
See U =)