Presets and how to create them? (SDK 7)

[RA]

Select your device. Open both parameterlist and presetlist. Freeze them. Now...in the left column of parameterlist initialize tree(right click) dunno how it is called exactly...at work here haha. Now you get a folder with all your vars sorted. Drag and drop that folder to your presetlist(make new list if it doesnt already exist....in your project tree you should see a go for the preset list. You should get a list of your vars and parameters in that list. Save your device and just to be sure reload it. It should now be capable of saving presets. Hope it helps a bit...cause yes...it is a pain in the ass to figure out

If you fail...ill check later today for the exact procedure and names.

[RA]

In the presetlist window....create a new one. That creates a default go or module for the device.

[RA]

Did you save your device and loaded the newly saved device in your project to check the workings?

Else i could make a reader on this

[RA]

Hi dragonsf, my kids slurped all my time.

Good to read that you got it working for you. Although it works different for me and i dont have to protect nor include magic parameters to get it working. Still...im gonna make a reader on this so you can try. Hopefully it will be of some help in the future. Also you dont want it to work with the parameters on the surface...connect those to dummy pads...and save the dummypads instead. This way if you change surface knobs and buttons you keep compatibility.

[RA]

I have started to make some readers on the SDK, which can be found here:
http://dnamusic.nl/dNa.Scope/index.php/ ... s-n-tricks

Maybe you can check if all works out for you. Thanks!

I will be making some more in the next couple of days i hope

[garyb]

wow! that's great!

[RA]

As you can see in the reader on dummypads i use the audio and/or control pad to make dummy pads.

For moving stuff on the panel...goto surface mode and with the cursor in move or edit mode i can move gui parts around

[RA]

There is another hidden option when you right click the panel module...think it is hidden there...or the surface interface module connected to panel...disable move...maybe that flag or another is causing this.

Or what you can do...open a basic empty effect or something....and copy all your stuff into that panel...does it work then? Gui editing is one of the harder things todo in sdk.

[RA]

Try to unset the custom vert and horiz size....so the viewtree group to auto. Do this in the GO editor. Probably there is a clip select flag set to the panel or group and the size is incorrectly set. Together with the clip select this can be the problem. Clip select means you cannot select outside the group.

[sunmachine]

IIRC you have to be on the topmost level of your circuit to be able to move the controls onto the panel.
So try this:
- Goto to the topmost level in Circuit mode
- Switch to Surface mode and Move mode
- Drag the control to the panel

[RA]

Actually, i can move controls inside groups that are in the panel, so in the sdk4 you dont have to be in top level. Just as extra info

[RA]

Oh right...it called different in 7. Will check for you later

[RA]

Okay DragonSF,

it is called the same in SDK7, but some things in the GO editor, actually it is called GO-Tree, are a bit fiddly.
The parameters which are of special interest are:

ViewTree Group(VTG),
Custom Horizontal Size(CHS)
Custom Vertical Size(CVS).

These interact. I'll explain how to use them:
1-Make sure you have your project onscreen, so viewing all the way up, not looking into devices. You should also see the in and outputs of the card/xite.
2-Enter your device/doubleclick on it. You will now see your circuits and you should also see a SurfaceInterface module connected to Panel module, aka your main GUI.
3-Don't enter any sub modules, but just switch from circuit mode to surface mode. You should now see your main GUI on screen!
4-Select(not enter) the main panel object/background and open your GO-Tree window; it will show a panel folder, with a ClientArea subfolder inside.
5-See the attached screenshot of such a ViewTree. You see that the Panel folder(GO-Tree), is a group containing your ClientArea. In the actual module, as shown in your Project explorer will have more elements such as knobs, faders, controllers, text etc. You can also group elements or objects on your GUI for keeping them together while moving for example. Groups can be very handy. In Surface mode They are the equivalent of folders in the Circuit mode.
6-When things are grouped, certain flags on the GO-Tree editor are set by default. To cut things short: while you are developing your device and the GUI is not finished, the flags on a group, and also the main panel one!: VTG should be enabled, and the CHS and CVS should be enabled.

The ViewTree option, makes the group as large as is needed to included ALL it's siblings. Also the ones which are placed outside a panel, or you placed it outside the group when it didn't have the correct dimensions! (this is how you lose controls from screen when moving them around when the size is fixed and things are clipped. I'll come back to this later on)

So while developing: VTG on, CHS and CVS off.
When your finished: Watch order!!!!! CHS and CVS on, and then VTG off. NOT the other way around!

The CHS and CVS will be set to current size, including the siblings/elements of the group.

Now: Select Clipping, will make sure a user cannot select outside that group's dimensions. It is possible to place things outside a group after the size has been set to custom. That is....if DrawClipping isn't enabled. DrawClipping will make sure that elements outside the groups dimension are not drawn onto screen, they are invisible (if size is at custom). You CAN enter any group, and the elements hidden or outside a group can be seen after entering a group. This is all done in surface mode!

When you finalize your device, you should first check and optimize. Probably you will get a lot of ViewTree messages. We have all seen them. Make sure you set ALL the groups to correct parameters. So...select a group, enable CHS and CVS and then disable VTG. If you have done that all correct, and thought about the SelectClipping and DrawClipping you should have a fast GUI as far as user experience goes.

GO-Tree.png (12.03 KiB) Viewed 20683 times