Do you mean RotarySwitch?
It's under Controls > List Entry, then right-click the module, select Properties
and look for Rotary Switch in one of the dropdown menus.

--- In syntheditusers@yahoogroups.com, stefanmedia@... <no_reply@...> wrote:
>
> hello all,
>
> i need to know how can i make a stepped (midi) knob which than can send a
message for example at position 1,2,3... to Volts to List or something else, to
realise a switch of for example a preset.
>
> thanks s.
>

just a heads up - we can use reajs http://www.kvraudio.com/get/4329.html
to write code within SE.

I've only had a quick look but it seems to work fine and it has more features
than SM's code component.

cheers

mark

Hi All,

I took great care in designing my synth to make all of the 'automatable'
parameters display the correct values/ranges.  For instance, the LFO Rate slider
readout displays 0 to 80 Hz.  But when I export the synth as VSTi and try to
automate the LFO rate in the host, the host's automation graph is set at the
range of 0 - 1.  So if I want to dial in a precise LFO frequency (say, 7 Hz)
from the host's automation graph, I have to convert: (1/80) * 7 =  0.0875.

It's do-able, but kind of a pain.  Is there a way to add some kind of
functionality from within SE so that the host will automatically know the
correct ranges of each parameter?

FWIW, I'm using Reaper and FL Studio as a host.

Thanks!

hi,
set the knob to 0 to 80 then rescale the value
to drive your LFO.

>Hi All,
>
>I took great care in designing my synth to make all of the 'automatable'
parameters display the correct values/ranges.  For instance, the LFO Rate slider
readout displays 0 to 80 Hz.  But when I export the synth as VSTi and try to
automate the LFO rate in the host, the host's automation graph is set at the
range of 0 - 1.  So if I want to dial in a precise LFO frequency (say, 7 Hz)
from the host's automation graph, I have to convert: (1/80) * 7 =  0.0875.
>
>It's do-able, but kind of a pain.  Is there a way to add some kind of
functionality from within SE so that the host will automatically know the
correct ranges of each parameter?
>
>FWIW, I'm using Reaper and FL Studio as a host.
>
>Thanks!
>
>
>
>------------------------------------
>
>Yahoo! Groups Links
>
>
>
>

I wrote a code module for SE a few years ago.
Ok for none samplerate stuff like pan pots, mixers, level adjs, routers
converters etc... but when uses at samplerate for filters, oscillators etc...
it used very too much CPU. If the reajs is precompiling code like a JIT compiler
then it might be feasible.

Regards
Etric


--- In syntheditusers@yahoogroups.com, "markbolitho" <mbolitho1@...> wrote:
>
> just a heads up - we can use reajs http://www.kvraudio.com/get/4329.html
> to write code within SE.
>
> I've only had a quick look but it seems to work fine and it has more features
than SM's code component.
>
> cheers
>
> mark
>

> just a heads up - we can use reajs http://www.kvraudio.com/get/4329.html
> to write code within SE.
>
> I've only had a quick look but it seems to work fine and it has more features
than SM's code component.
>
>

Thanks, that looks intriguing.  Unfortunately the page doesn't explain
how it works - does it interpret the code in real-time, or is it
compiled first?  If so, to what?  Native (SSE accelerated) code?
--
gl

Thanks Eric,

Scaling the slider within SE is not the issue - I already did that.  The rate
slider's voltage range is set to 0-80.  I then divide the output by 1000 to
drive the LFO, which is set to 1V/KHz.  So no problem there at all.

The problem is in the host.  When I try and automate that parameter (using an
automation track, where I draw a graph of how the values change over time) in
Reaper, the automation graph reads 0 at its minimum and  1 at it's maximum.  Or
if I try it in FL Studio, it reads 0% at minimum, and 100% at maximum.

Keep in mind that when I change the values in the host's automation graphs, the
VST GUI does update to the correct value in Hz.  But  it's a pain to keep
checking on the GUI to see if I've dialed in the right value.  It would be nice
if the host displayed the correct value right from the start.

Do you know if there's any way to make this happen?

Thanks!




--- In syntheditusers@yahoogroups.com, Eric Langou <elangou@...> wrote:
>
> hi,
> set the knob to 0 to 80 then rescale the value
> to drive your LFO.
>
> >Hi All,
> >
> >I took great care in designing my synth to make all of the 'automatable'
parameters display the correct values/ranges.  For instance, the LFO Rate slider
readout displays 0 to 80 Hz.  But when I export the synth as VSTi and try to
automate the LFO rate in the host, the host's automation graph is set at the
range of 0 - 1.  So if I want to dial in a precise LFO frequency (say, 7 Hz)
from the host's automation graph, I have to convert: (1/80) * 7 =  0.0875.
> >
> >It's do-able, but kind of a pain.  Is there a way to add some kind of
functionality from within SE so that the host will automatically know the
correct ranges of each parameter?
> >
> >FWIW, I'm using Reaper and FL Studio as a host.
> >
> >Thanks!
> >
> >
> >
> >------------------------------------
> >
> >Yahoo! Groups Links
> >
> >
> >
> >
>

Thanks, daz

That's kind of what I feared.  Oh well.

I had hoped that maybe sub-controls or something could offer a way to
communicate with the host & tell it what ranges to display.  But if I have to do
a little math before plotting my automation graphs, then so be it.






--- In syntheditusers@yahoogroups.com, daz diamond <daz.diamond@...> wrote:
>
> afaik its locked into each daw ... the values only appear on control surface
> screen readouts ...
>
> hth ?
> daz
>
> On 2 March 2010 15:38, rubik909 <no_reply@yahoogroups.com> wrote:
>
> >
> >
> > Thanks Eric,
> >
> > Scaling the slider within SE is not the issue - I already did that. The
> > rate slider's voltage range is set to 0-80. I then divide the output by 1000
> > to drive the LFO, which is set to 1V/KHz. So no problem there at all.
> >
> > The problem is in the host. When I try and automate that parameter (using
> > an automation track, where I draw a graph of how the values change over
> > time) in Reaper, the automation graph reads 0 at its minimum and 1 at it's
> > maximum. Or if I try it in FL Studio, it reads 0% at minimum, and 100% at
> > maximum.
> >
> > Keep in mind that when I change the values in the host's automation graphs,
> > the VST GUI does update to the correct value in Hz. But it's a pain to keep
> > checking on the GUI to see if I've dialed in the right value. It would be
> > nice if the host displayed the correct value right from the start.
> >
> > Do you know if there's any way to make this happen?
> >
> > Thanks!
> >
> >
> > --- In syntheditusers@yahoogroups.com <syntheditusers%40yahoogroups.com>,
> > Eric Langou <elangou@> wrote:
> > >
> > > hi,
> > > set the knob to 0 to 80 then rescale the value
> > > to drive your LFO.
> > >
> > > >Hi All,
> > > >
> > > >I took great care in designing my synth to make all of the 'automatable'
> > parameters display the correct values/ranges. For instance, the LFO Rate
> > slider readout displays 0 to 80 Hz. But when I export the synth as VSTi and
> > try to automate the LFO rate in the host, the host's automation graph is set
> > at the range of 0 - 1. So if I want to dial in a precise LFO frequency (say,
> > 7 Hz) from the host's automation graph, I have to convert: (1/80) * 7 =
> > 0.0875.
> > > >
> > > >It's do-able, but kind of a pain. Is there a way to add some kind of
> > functionality from within SE so that the host will automatically know the
> > correct ranges of each parameter?
> > > >
> > > >FWIW, I'm using Reaper and FL Studio as a host.
> > > >
> > > >Thanks!
> > > >
> > > >
> > > >
> > > >------------------------------------
> > > >
> > > >Yahoo! Groups Links
> > > >
> > > >
> > > >
> > > >
> > >
> >
> >
> >
>

http://www.youtube.com/watch?v=f89sSAeMBwU

old version of my overdub looper now updated
gui done with help from daz d
cheers bud

its included in the download for this

http://www.youtube.com/watch?v=JTzRtoDxzzE
my kaoss pad 3 to ableton session view controler

done using delay2 module and an xfader module
simple
then added alsorts of stuff to it to sync it and warp it

al.

--- In syntheditusers@yahoogroups.com, "aversanomusic" <aversanomusic@...>
wrote:
>
> In tips and traps in the Synthedit help, you can find a section called
feedback paths which explains how feedback works in SE.
>
> hope that helps!
>
> --- In syntheditusers@yahoogroups.com, "Scott Muir" <blacklight9@> wrote:
> >
> > Thanks !  I'll do some experimentation with it and see where it leads me. 
8)
> >   ----- Original Message -----
> >   From: daz diamond
> >   To: syntheditusers@yahoogroups.com
> >   Sent: Friday, February 26, 2010 7:19 PM
> >   Subject: Re: [syntheditusers] feedback loops ? Possible ?
> >
> >
> >
> >   feedback at a sample-level is not possible in SE ... at a block level,
however, all you need is the feedback(delayed) module .... insert > special >
feedback ... voila ...
> >
> >   daz
> >
> >
> >
> >   On 26 February 2010 21:30, Scott Muir <blacklight9@> wrote:
> >
> >
> >
> >     Maybe I should clarify.  These videos explain everything.  You can
actually get some amazing and interesting sounds out of just a mixer, a couple
of cables, and some guitar pedals (I've sampled quite a few to use in my music):
> >     Part 1:
> >     http://www.youtube.com/user/F7sound#p/u/51/qk6NQvXSizg
> >
> >     Part 2:
> >     http://www.youtube.com/user/F7sound#p/u/50/hiV5xHQNv_4
> >
> >     Part 3:
> >     http://www.youtube.com/user/F7sound#p/u/47/npBwHTqcaEI
> >
> >     My old mixer doesn't have an Aux Send, but I use the headphone jack and
I get the same results.
> >     You just have to make sure that you keep the volume levels of your
speakers down because you CAN blow them this way.
> >     Synthedit unfortunately seems to restrict us from making loop
connections like this (at least in the modulle collection that I have).  I was
thinking that this would be interesting to do in something like Synthedit
because of all the wacky connections you can do with it.
> >
> >
> >       ----- Original Message -----
> >       From: Eric Langou
> >       To: syntheditusers@yahoogroups.com
> >       Sent: Friday, February 26, 2010 1:47 AM
> >       Subject: Re: [syntheditusers] feedback loops ? Possible ?
> >
> >
> >
> >       insert/Feedback (delayed) ?
> >
> >       >>>Is using synthedit to create feeback loop based instruments a
possibility ?
> >
>

hey,

maybe you remember me.. I have the exact same question as last time.

I created a synth and now wish to save as vsti.  however,  I haven't quite
figured out the container and IO mod yet.  my synth is in a container yet when I
choose to save,  it doesn't ask plugin is synth.

I'm almost there.  help with the last steps and I'd really appreciate it.

Logan

> see attached a picture showing something weird :
the midi monitor must display C-1, like the KDL captured bellow and a small
rectangle appears at the EOF.

Thanks Eric,
That's the 'newline' character, I'll remove it.

Best Regards!,
Jeff



-----Original Message-----
From: Eric L
Sent: Sunday, 28 February 2010 1:17 a.m.
To: Jeff McClintock
Subject: midi monitor

hi,
see attached a picture showing something weird :
the midi monitor must display C-1, like the KDL captured bellow and a small
rectangle appears at the EOF.

cheers,
eric

hi all,
there is a tool from DAV permitting to concatenate
the .sem but it have a default (reported to the author)
it save always the new module with the same internal name
(conflict)


>Hi Efflam,
>
>There is a limit to how many dlls (SEMs and VSTs) can load at the same time.
Approx 300. So you can load say 10 different VST plugins, each with 30 SEMS, but
any more than that will fail. This is a limitation of Windows unfortunately.
>
>You can improve things by using SEMs that contain multiple modules, e.g. I
recently combined all the Patch-Mem modules into one SEM file. Also use
SynthEdit’s built-in modules if possible. In Version 1.1 many conversion
modules are now included with SynthEdit. This can reduce your overall SEM-count.
>
>3rd party developers can also help by packaging related modules together in one
SEM.
>
>
>Hope that’s helpful,
>
>Jeff
>


>
>Hi Jeff,
>
>I was reported that my SE plugins crashed some system when you load around 6 or
8 plugins.
>It heppanned to me too, but it seems not to happen to most users.
>
>I attached you a screen shot.
>The sem file mentionned on the message window isn't the problem i think, since
when crash occurs, a message like this appears for almost all the modules
contained...
>
>If you have any clue.
>
>Best,
>
>Efflam
>

Hi,

> there is a tool from DAV permitting to concatenate
> the .sem

I did some tests a while back on this and unfortunately it did not seem that
SEMs merged with this tool helped on the issue. SEMs have to be merged at
compile time.

Here are a couple of general notes about what I've found regarding this
issue:

1) As Jeff described the limitation of SEMs is shared amongst all plug-ins
loaded. Multiple instances of the same plug-in do not seem to use more of
the limited SEM count. What matters is the number of *different* plug-ins
and the number of SEMs they use.

2) Possibly merging in other resources when Saving-as-VST (like txt, pdf,
sf2, wav) also impacts the number of plug-ins the system can load.

3) Some hosts allow more plug-ins to be loaded than others. A light host
like VSTHost seems to allow more plug-ins than Cubase.

4) Native SE modules that are extracted as SEMs (Spring2, FloatLimiter, .)
are very easy to recompile in a merged SEM (especially with the sdk3). These
can also be combined with any other custom modules used in the project.

5) The limitation also applies to SE1.0 projects.

Regards,
Rune

Well, I did notice only normal controls as knobs and sliders can be reassigned
with MIDI CC by the user but not the subcontrol type of controls as only the
about box pops up in that cases. Sure it would be helpful if MIDI CC could be
reassigned on subcontrol based controls too.

cheers
HG

Thanks HEAPS ... any chance of exposing the "Polyphony" and "Polyphony Reserve"
pins on the "Midi to CV" module as well, or am I really pushing it this time?
Perhaps this is not a sensible option, but I like the idea or reducing memory
usage on really complex synths when you don't NEED millions of components
duplicated, except for those few "special" patches (atmospheric/evolving pads in
particular) with very long release times.

Thanks again!

--- In syntheditusers@yahoogroups.com, "Jeff McClintock" <jef@...> wrote:
>
> >Hi. The Midi to CV module has "Soft Steal", "Hard Steal" and "Overlap" ...
> but there is no option to make these selectable via a List Entry, i.e. there
> is no connector pin for them on the Midi to CV module.
>
> I'll expose that pin so you can hook up a list entry. Available next beta.
>
>
>
> Best regards,
>
> Jeff
>
>
>
> From: syntheditusers@yahoogroups.com [mailto:syntheditusers@yahoogroups.com]
> On Behalf Of simonecuttlefish
> Sent: Friday, 19 February 2010 5:00 p.m.
> To: syntheditusers@yahoogroups.com
> Subject: [syntheditusers] Midi to CV Polyphony Mode
>
>
>
>
>
> Hi. The Midi to CV module has "Soft Steal", "Hard Steal" and "Overlap" modes
> selectable on the module for the polyphony mode setting. These implement
> some seriously different modes, but there is no option to make these
> selectable via a List Entry, i.e. there is no connector pin for them on the
> Midi to CV module.
>
> Is it possible to make this a selectable option, or is the only way to put
> in three Midi to CV modules in separate containers, and select which one is
> outputting to the rest of the synth via flow control options?
>
> Thanks.
>