some tips ..

A place for developers to share ideas and assist each other in solving problems.

Moderators: valis, garyb

Post Reply
wolf
Posts: 593
Joined: Tue Dec 23, 2003 4:00 pm
Location: hamburg
Contact:

some tips ..

Post by wolf »

Hi all,

some hints for you SKD'ers. I hope they are of use for you !
Btw, as DP'ers using an older version we don't have access to the SDK forum.
I'm even not shure, if all hints will work for you, but I think so.


Here's a way to midify existing, but protected devices:
- load i.e. TransientDesigner into SDK/DP.
- also drag the Midi Controller Linker & the Midi Channel Linker Module into the project
- connect "CCon" pad of the channel module to "Ch" pad of the contr. module
- connect a midi source to the "Midi" pad (green) of the channel module
- connect a midi destination to the "Mid1" pad (red) of the channel module
- select the Midi Controller Linker & the Midi Channel Linker Module
- click on "move into"
- click on the TransientDesigner module
- save it as new device with its new midi in/outs
done ..

"integer division by zero"
either while project load or while doing something this alert might pop up and is always frustrating. If it doesn't stop to pop up, there's usualy a dynamic signal like a LFO fed to it.
If you have the project running as slave, switch off the master clock. If you have it running as master, switch to slave. Both ways have the goal to "disable" the dsp processing. This gets you rid of the reoccuring alerts and lets you remove the reason for it.
Basically you should save the async division module with the value 2 for in2 and use that from now on.

Beeing able to track pad connections, after you've forgotten the routing :
Export pads and other connections to graphic elements and connect them from the exported pad to the graphics elements. This way you'll see the connections in the connections window (direct connections from some pads aren't shown there).
Of course this is not a good idea for the topmost module.
If not needed for connections to other modules, you can hide the pads by selecting it and hitting "H"


In case this was not clear, you can move the pads of modules to any side:
Select the pad, you want to move and hit T(op), B(ottom), L(eft) or R(ight).
This helps cleaning up the design.
The first exported pad will be listed first, if more pads are in a row.

Some more keycommands for the pad list:
I(nput) sets pad to green arrow
O(utput) sets pad to red arrow
E(xport) exports the pad (rename pads before exporting them)
S(tore) stores the pad
C(onnect) connects the pad to the previous stored pad

Using these with the arrow keys lets you change lots of pads in short time.

have fun !
User avatar
erminardi
Posts: 1575
Joined: Fri Apr 30, 2004 4:00 pm

Post by erminardi »

Yeee, some developers are alive :D
Thanks for your support, Wolf!
4PC + Scope 5.0 + no more Xite + 2xScope Pro + 6xPulsarII + 2xLunaII + SDK + a lot of devices (Flexor III & Solaris 4.1 etc.) + Plugiator.
User avatar
Shroomz~>
Posts: 5669
Joined: Wed Feb 23, 2005 4:00 pm
Location: The Blue Shadows

Post by Shroomz~> »

Hey Erminardi, you stirred up some life !!

Keep these tips coming wolf & thanks!!
User avatar
spacef
Posts: 3340
Joined: Sun Jun 17, 2001 4:00 pm
Contact:

Post by spacef »

some very advanced tips... thanks mr wolfgang
Post Reply