|
|
Post by cohort1000 on Mar 11, 2014 20:09:17 GMT 1
started a new project but can't get the container to open a window (yes, I clicked it). I'm using 1.19 in Win7. any ideas?
thanks in advance.
|
|
setronic
Synthedit regular
Posts: 293
Posts: 293
|
Post by setronic on Mar 11, 2014 21:01:41 GMT 1
right click, 'panel edit'
|
|
|
|
Post by cohort1000 on Mar 12, 2014 19:50:21 GMT 1
That just gives me the GUI window. I want to create a container to put most of the modules in, or is this not the right way to do it. So far all the tutorials I've seen suggest I do this for better control.
|
|
|
|
Post by cohort1000 on Mar 12, 2014 19:52:19 GMT 1
ok, here's a step missed. click "structure" next. done! thanks.
|
|
setronic
Synthedit regular
Posts: 293
Posts: 293
|
Post by setronic on Mar 13, 2014 23:15:11 GMT 1
>'File'>'New'
(nb: i still use synthedit v1.017, which is different from 1.1(v1.1914)
and from the current 1.2 betas - so you'll maybe have a slightly different
construction. i have 1.017 projects i'm trying to complete..)
so your main workspace page is titled 'Synthedit'.
right click there: 'insert' > 'container'
double click that, on the blue bar. now you're in that container.
right click, insert 'knob'/etc.
anyway: doubleclick, here's the structure of (a control object).
select all, move it to the middle to pull it around,drag the iomod
over to the right(this is for inputs and output on the container you're in)
do the same with the float to volt and put the patchmem in the middle.
right click on the patchmem, select 'properties.
you can edit the module's title, if you want to(best to keep 'patch' in
any name, to identify it-i sometimes edit the name if it is useful to
help remember what it's for; not necessary most of the time)
'name' is whatever is displayed on the text entry2 module; it is
also what is displayed in your plugin's parameter list later, when
you edit controllers in the key edit page of a VST host.
if you don't have a text entry2, you can just type in here, if not
the text entry takes precedence, and you have to type in there.
'animation position' is the position of the image,
range 0 to 1 in fine increments.
'value' is the actual value, based on the min/max range. and it's
sent out as the 'grey background'/'dsp' float pin/cable type, at
the corresponding value- then float to volt, which connects to all
your dsp modules.
there are two float pin/cable types, GUIFloat and Float.
GUIFloat can have multiple inputs, which then share position+value,
but only one output.
Float has only one input, and can have multiple cables coming from
the output. Float is 1way, and GUIFloat is 2way/synchronised/same
value at both ends.
|
|
alienoiz
Synthedit regular
Posts: 148
Return Goku!
Posts: 148 
|
Post by alienoiz on Mar 14, 2014 18:02:22 GMT 1
Hey, since you are beginning in SE i want to give you an info that i consider very important and is not shown in SE help files.
In SE help files is said that the Sound Out module does not means anything if you leave it in your project when you export it, but it does.
Very carefull, NEVER LEAVE YOUR SOUND OUT MODULE IN THE EXPORTED VSTi!
I made this mistake and the result was ruinned RAM cards.
It seems that by leaving the Sound Out module in the exported project the DAW has problems in redirecting the sound.. it plays good, but after sometime and with multiple plugins, origins constant crashes and blue screens in your system.
Best regards:
Duarte V.
|
|
setronic
Synthedit regular
Posts: 293
Posts: 293
|
Post by setronic on Mar 15, 2014 23:48:55 GMT 1
hey very interesting: i had to replace a RAM last year,
and it was bluescreening a lot before.
VST plugins can really break your computer?
if someone distributes a plugin with this error? they render
themselves liable for the damage caused? need a disclaimer
with every release :/
i have made a plugin that blackscreens the PC. happened
twice, as soon as i ran it, didn't try it again after that!
i don't think i made that mistake though.
|
|
alienoiz
Synthedit regular
Posts: 148
Return Goku!
Posts: 148
|
Post by alienoiz on Mar 16, 2014 0:25:35 GMT 1
Well, noone told me this for sure but im almost 100% positive that my plugins were the cause.... i made an exaustive test.
All was good in my PC, and after working with a lot of my creations this started to happen. I thought it was a normal PC problem and i ended ruin my laptop. I got another computer and i started to produce music again with my creations and i ended replacing my RAMs again. Then it broke so i set my office PC into music too, and once again the crashes started so i made a test.
I had around 7 vsti and 17 effects and i was producing music, so i had several projects. I kept one project with around 10 plugins and for each crash and blue screen, i rebooted and removed one plugin from the project. When i reached 1 plugin the time to the pc crash had increased around 50%. So i removed all Sound Out modules and replaced the RAMs and i never had crashes again. I also fixed my laptop and it is still working with no problems.
And there is someone that told me that using the Sound Out module in exported VSTi give sound redirecting problems.
Maybe thats why you can only insert one in each SynthEdit project?!!!!
Duarte V.
|
|
|
|
Post by Cajhmere on Jan 17, 2015 14:52:08 GMT 1
Umm... Maybe the dumbest question ever in this forum for the future, but: what does it mean? "using the Sound Out module in exported VSTi"? Kinda example?
|
|
alienoiz
Synthedit regular
Posts: 148
Return Goku!
Posts: 148
|
Post by alienoiz on Jan 20, 2015 13:00:03 GMT 1
Umm... Maybe the dumbest question ever in this forum for the future, but: what does it mean? "using the Sound Out module in exported VSTi"? Kinda example? When you make your VST or plugin you use the Sound Out Module to hear the sounds, but when you export the VSTi to .dll this module is not necessary and if you do not remove it from the structure in SE, when using the exported and complete VSTi on the DAW, it might cause routing errors and conflicts... I made several basic VSTi when i started to work with SE, and left the Sound Out module inside the structure, and then exported the plugins. By using those VSTs in my projects i have ruined my Ram cards. I know this was the problem cause i made a debugging and after removing the 2 pair of bad Ram cards i also removed the Sound Out modules from all VSTi and it stopped. The signal to this is several crashes during the usage of the VSTi and further blue screens.... which almost always mean Ram Cards problems. |
|
|
|
Post by Cajhmere on Jan 20, 2015 14:50:36 GMT 1
Well I tested that now. Being a totally newbie I was sure u need the sound out. I really don't know if it's really possible to bring heat on RAM through that Soundout module, but the chance that it could happen...
I will make an extra info in my tutorials, to delete all soundouts before export. hank you for that info!
|
|
|
|
Post by Cajhmere on Jan 22, 2015 23:08:55 GMT 1
|
|
alienoiz
Synthedit regular
Posts: 148
Return Goku!
Posts: 148
|
Post by alienoiz on Jan 23, 2015 12:06:45 GMT 1
|
|
|
|
Post by Cajhmere on Jan 23, 2015 18:41:06 GMT 1
Welcome...  |
|
