Planet Z

This device is intended to create modular patches without the need of doing it "all in one" modular shell, the advantage is that we can save several submodhost templates and simply add it in the modular as a module.

The use is very simple,
open the modules inside the submodhost and connect the output you need to the patchbay corrispective numbers.

The red connectors are ok for audio, freq, gates and so on.

24Dec 2006
device deleted (an explanation will come shortly)

The gold connectors are for esync.

The yellow connectors are for midi.

The submodhost is saved together with the modular patch, but if we need to create templates, it's not possible from the modular shell and to do it follow this procedure:

First of all, make copies of the "sub modular host.dev" and rename it.

open the submodhost from the scope environment, you'll notice that the device is not visible from the routing window, so, open it by clicking on the device icon in the live bar.
Make your patch and when you've finished, open the preset list by clicking on the button inside the submodhost and click on the "device" button located in the preset list window.
Now you have saved the template and when you'll open it from the modular shell, it will be ready to be connected.

There is sometime a small bug when overlapping modules inside the submodhost shell, i'm working on it and in the meantime, it's safe to avoid placing modules too near.

I'm making a short documentation and some video example, but the device is very simple to use.

Thanks

Micron


updated,
now the position of connection pads is static, so, the problem about hidden pads should be fixed.

update #2

fixed the bug when overlapping modules vertically.

update #3

fixed the issue related to cables position refresh.

many users are having problems making templates due to lost surface connectors after saving the patch, so, who need to save some template, let me know about the modular patch and i'll save the submod host template




<font size=-1>[ This Message was edited by: djmicron on 2006-06-14 15:55 ]</font><BR><BR><a name="planetz-fileimage"></a><IMG SRC="http://www.djmicron.org/submod.jpg" BORDER="0">

Micron I LOVE YOU!!!
I can't wait to test it, but I have to wait until tomorrow...
That seems to be exacly what i was searching when I worte this post:
http://www.planetz.com/forums/viewtopic ... forum=30&3

Thank you!

Great idea but not working correctly

When make patch and save it and load to mod shell - not visible cable color pad ( only grey color and not working it )

Please fix this great module

Very thanks

this is very clever! Object Orientated Modular Patching = OOMP. okay, can someone come up with an "H" so we can call it OOMPH?

<font size=-1>[ This Message was edited by: kensuguro on 2006-05-28 07:45 ]</font>

maybe a bit obvious Ken, but what about "Host"

Sorry mate, but it seems to be crashing quite a lot on SFP 4.5 (or 4, whatever 4.5 is)

Hey, is this re-skinable?

This is a great idea micron. Someone's getting very clever with their SDK

hi megerov,
could you explain a bit more what you mean?
do you mean the hide/show color tools?

Thanks

hi shrooms,
i've tested the device under 3.1 to 4.5 without crashes.
Which modular shell have you used to test it ?

About the skin, yes it's possible to change it, but just the module not the host.

Thanks

I'll do some more testing. I experienced crashes of SFP when making connections that I shouldn't have. Instead of just getting a popup error about the connection attempt, I got that, then an SFP crash. I'll try again later.

<font size=-1>[ This Message was edited by: Shroomz on 2006-05-29 05:15 ]</font>

it's a great idea!
the only suggestion, if it's possible, is that i would add a text board for writing comments and/or connections instructions...

yes bosone,
this will be implemented in the nex update.
thanks

Hi Djmicron,
after some more tests it seems that we have the same problem as megerov whereby the connection sockets don't appear or function as they should in the ModII shell. There's also some bugs in the patch lead graphics in the sub host. When you move modules which have I/O connections made, the patch leads stay where they were instead of moving to the new location. Giving the moved module another nudge seems to fix this & they jump to the new location. The other strange gfx bug we noticed was having an osc freq connected to I/O 13, then when moving the esync/midi I/O module the connection graphic detaches from it's osc freq connection & moves away with the esync/midi module which it's not connected to. I'll send you screenshots of these bugs.

Thanks, I will try it soon! Wow, after so many years scope is hotter than ever before!

thanks for bug reportings,
i'm working on it to fix it asap

check the new file,
this should fix the hidden pads problem.
Let me know....

Thanks

new update,
i've fixed the bug when overlapping modules vertically.

now it remains a minor graphical bug, when moving the 24 i/o module with red pads, the cables does not follow the position of the module and if it happens, just close the surface and reopen it.

Is it possible to make it able to load effects without insert effect and to load synths? This would be hughe for saving complex blocks of cabeling and loading it in another project...

Martin

I must be doing something wrong, as I'm still getting a graphic bug in the module inside the ModII shell after saving a device from the host.

I've made 3 copies named SMH_1,2 & 3 & after saving a patch/device from the host (SMH_1) when I then drag SMH_1 into the ModII shell, there's no patch sockets on the module, just the skin. I then tried dragging SMH_2 (which hasn't been saved over) into the ModII shell & the module appears as it should do. But SMH_2 doesn't have the saved patch/template.

Tell me where I'm going wrong micron. It's probably just me doing something stupid

it is not easy to me, because i've done several tests with more than one computer and all sfp versions from 3.1 to 4.5.
For sure, the hidden pads problem, is related to saving the device from the project window of scope.
To make you understand, try to open a modular module inside the scope project window, for example the pulse lfo and you'll see that the connection pads will be visible until you'll touch the pulse lfo surface..
This is why i've made the submodhost surface not visible from the scope project window.
I'm investigating to solve this issue, but to be sure, i would need to have the same problem here, but here it works
I'm testing it on win xp sp2, i don't know if this can be important...

it could be possible to make modular version of standard effects and maybe the synts too, i'll try to make a module and i'll let you know...