This is looking really great and interesting !
good luck to you and success!

Cheers
Rene

On 11/23/09, Mildon Maducdoc <mildonm@...> wrote:
> wow. really cool. :-)
>
> On Mon, Nov 23, 2009 at 6:22 AM, sonicflash1980
> <sonicflash1980@...>wrote:
>
>>
>>
>> Hi folks,
>>
>> just wanted to inform you that my new Livemachine will be released on
>> Dec.
>> 06th 2009! Synthedit made it happen!!
>>
>> Check it out if you want: http://prodyon.kilu.de/livemachine.html
>>
>> Thanks to Jeff, all ModuleDevelopers and all others!
>>
>> Cheers!
>> -Dennis
>>
>>
>>
>

--- In syntheditusers@yahoogroups.com, "Jeff McClintock" <jef@...> wrote:
> > To further assist with testing the MTS feature, I've uploaded to the
> Simple MTS Synth directory a ZIP archive
>
> Cheers, will investigate
>
> Best Regards!,
>
> Jeff
>
> To further assist with testing the MTS feature, I've uploaded to the Simple
> MTS Synth directory a ZIP archive containing MTS MID files, created with
> Scala, for equal temperaments 5, 7, 11, 12, 13, 15, and 17.

Here's a little food for thought. I was just refreshing my memory about the
standard by reading here:

http://www.midi.org/techspecs/midituning.php

Found this bit interesting:

"The specification provides for 128 tuning memory locations (programs). As with
the MIDI program change message, this is a maximum value. An instrument
supporting MIDI Tuning may have any lesser number of tuning programs. The
specification requires only that all existing tuning programs respond to the
messages as specified (See section 3, "Continuous Controller Messages")."

So, this begs the question of how to provide these 128 tuning memory locations.
Perhaps some sort of SYSEX transmission module, kind of like the MIDI Player,
that would enable the user to load up to 128 microtuning programs and switch
between them using a list selector. If list selection of the microtunings could
also be changed with MIDI CCs that would be very useful.

Thanks,

J

OK. I just needed to know, because one of my synths first created in V1.0
allowed users to enter values via text entry - which would have been nice to
have kept. I've just disabled the writeable parameter in the text entry module.

Jez


--- In syntheditusers@yahoogroups.com, "Jeff McClintock" <jef@...> wrote:
>
> > Are there any plans of this being implemented in the near future?
>
>
>
> Hi, No not in the near future.
>
> Jeff
>
>
>
> From: syntheditusers@yahoogroups.com [mailto:syntheditusers@yahoogroups.com]
> On Behalf Of jezprice
> Sent: Sunday, 22 November 2009 5:55 a.m.
> To: syntheditusers@yahoogroups.com
> Subject: [syntheditusers] Jeff, I'll ask again.
>
>
>
>
>
> It states in the V1.1 help files that the GUI converters are bi-directional,
> and I complained the 'Float To Text' converter would not format the Text
> Entry 3 Module to numbers, and also accepted letter character entry, which
> wasn't possible in V1.0.
>
> You suggested a dedicated number-entry sem would be useful.
> Are there any plans of this being implemented in the near future?
>
> Jez
>

Can't thank you guys enough for the help! (I can't believe i missed the module
in the examples folder either, whoops!)


--- In syntheditusers@yahoogroups.com, Eric Langou <elangou@...> wrote:
>
> it's a "FAQ" you should find a few solution previously posted here.
>
> my favorite is :
> [one to many]->[volt to bool]->[container]
>
> >> Soo... Does anyone know if it's possible to create seperate pages for the
GUI(one for OSC 1, one for OSC2, one for the filter(s), etc...)
>

I installed 1.1 yesterday, and overall I'm really impressed, however ADSR2 seems
to be processing duration inaccurately. Here is a link to Audacity screenshots
of the output of a patch identical but for the use of ADSR vs. ADSR2. The
desired duration is 800 mSec. ADSR is pretty close, but ADSR2 gives about 300
mSec.

http://www.mediafire.com/?sharekey=9509e7633e4e6059ab1eab3e9fa335ca291f2b5ae28a9\
60e

Regards,
Jonathan Murphy.

What I found to be really interesting is to redirect the aduio-output of the
synthesizer into it's own parameters (pitch, volume, filter cut/res, sustain,
etc etc). I made a matrix into which the output is routed, then a row of
'sliders'+'leveladjust's to determine how much is being returned to each
parameter.
Of course, you could also use adsr's to define the amount of feedback.
The synth I've come up with can produce sounds of really weird noise up to
trumpet and other 'other-worldly' sounds.
Connect a random-osc+sample&hold+glidemodule to the leveladjust to randomize the
character of each sound.

sirsicksik

--- In syntheditusers@yahoogroups.com, pat2070 <no_reply@...> wrote:
>
> Check out De La Mancha plugins
>
> Two that spring to mind include --->
http://www.delamancha.co.uk/dirty_harry.htm
>
> and also
>
> http://www.delamancha.co.uk/bent.htm
>
> De La Mancha are my favourite Synthedit developer! :)
>
> Pat
>
>
>
> --- In syntheditusers@yahoogroups.com, "Scott Muir" <blacklight9@> wrote:
> >
> > I was just curious if anyone has ever made anything REALLY chaotic with
Synthedit, perhaps something similar to a circuit bent instrument ?
> > I've taken existing Reaktor synths and stuck random modules in all over the
place on occasion (especially math ones) that turn them into circuit bent
instruments that really generate a lot of interesting, barely controllable
sounds and noise.  Has anyone done anything like this with Synthedit ?  I'd love
to see your stuff if you have !  8)
> >
>

Ah thanks!
I knew I read it somewhere, just forgot that it's name wasn't 'midi-recorder'!
I'll check it out tonight and see if I can build some new midi-automation vst's
for my hardware stuff :)
I've jsut bought a new kicksynthesizer 'Jomox mBase01' and I must say I'm really
REALLY impressed :P, just one problem is that it only has one single know to
adjust parameters, so a controller-automator made with synthedit would come in
really useful :)

sik

--- In syntheditusers@yahoogroups.com, "Jeff McClintock" <jef@...> wrote:
>
> ?Anyone knows about anything about a new 'midi-record-module'?
>
>
>
> Insert/Diagnostic/MIDI Logger ?
>
>
>
> From: syntheditusers@yahoogroups.com [mailto:syntheditusers@yahoogroups.com]
> On Behalf Of sirsicksik
> Sent: Wednesday, 18 November 2009 11:32 p.m.
> To: syntheditusers@yahoogroups.com
> Subject: [syntheditusers] Re: A-still problem SE 1.1 B- Midi recorder?
>
>
>
>
>
> *Kick*
>
> Anyone knows about anything about a new 'midi-record-module'? (I'm pretty
> sure I read about it somewhere, but can't remember where...)
>
> also,
> as I have a new house (WHOOHOO!! freaking finally after 9 years of
> waiting!!) ......without internet.....which will be the reason I won't be
> online much.. So people asking me questions or trying to get in touch with
> me have to be a little patient as I'll only be checking out my e-mail once
> every week..
>
> sik
>
> --- In syntheditusers@yahoogroups.com
> <mailto:syntheditusers%40yahoogroups.com> , "sirsicksik" <R_V_D_M@>
> wrote:
> >
> > A- Hi, I've still got my loading problems using synthedit 1.1 I found out
> that it DOES load, but only after waiting for longer than 5 minutes..
> >
> > B- I think I remember to have read a thread on here that tells something
> about a module for recording midi(automation?)... now I was wondering...
> which module is that?? Is that in synthedit 1.1 or only a beta version?
> >
> > sik
> >
>

Screenshots probably not all that helpful. Here is the link to a zip containing
a prefab, a midi file, the rendered wave file, and a comparative screenshot.
Left channel is adsr2, right channel adsr.

http://www.mediafire.com/file/gkjmjkymn4o/adsr_vs_adsr2.zip

Synthedit version is 1.17.

Regards,
Jonathan.

--- In syntheditusers@yahoogroups.com, "typetosmurky" <typetosmurky@...> wrote:
>
> I installed 1.1 yesterday, and overall I'm really impressed, however ADSR2
seems to be processing duration inaccurately. Here is a link to Audacity
screenshots of the output of a patch identical but for the use of ADSR vs.
ADSR2. The desired duration is 800 mSec. ADSR is pretty close, but ADSR2 gives
about 300 mSec.
>
>
http://www.mediafire.com/?sharekey=9509e7633e4e6059ab1eab3e9fa335ca291f2b5ae28a9\
60e
>
> Regards,
> Jonathan Murphy.
>

----- Original Message -----

From: Jeff McClintock

To: 'superwave support'

Cc: syntheditusers@yahoogroups.com

Sent: Wednesday, November 25, 2009 10:36 PM

Subject: [syntheditusers] RE: Dual Layer Synth, Patch Automator Setup?

 

> I'm not sure how to handle patch organization using two separate synths in one VST instrument, is it possible to use a Patch Automator in each layer or can only one Patch Automator be used in a single VST instrument before the two synth containers?

Hi Chris,

I’ve never tried dual patches. Several people have asked for this feature but I simply ran out of time before I could add this to SE 1.1

 I suggest you experiment with two patch-automators, each in its own container.

Best Regards!,

Jeff

Update:

OK - I just tried transmitting the SYSEX again from the MIDI Player, and while
it does not work inside of SynthEdit, it *does* however work perfectly within
the VSTi when after using Save As VST.

So, here we are folks - full keyboard microtuning with MTS!

For anyone interested, you can download the MTS Synth from the files section of
this forum, and save the VST, and it should work with the single note MTS files
just as it is configured now. The MIDI Player will automatically transmit the
SYSEX, and retune the entire instrument, as soon as you open one of the MID
files.

So now we can add microtuning functionality to any SE synth without hassles.
This is a fantastic development.

Thanks Jeff!

J

--- In syntheditusers@yahoogroups.com, "Jeff McClintock" <jef@...> wrote:
>
> > So, this begs the question of how to provide these 128 tuning memory
> locations. Perhaps some sort of SYSEX transmission module, kind of like the
> MIDI Player, that would enable the user to load up to 128 microtuning
> programs and switch between them using a list selector. If list selection of
> the microtunings could also be changed with MIDI CCs that would be very
> useful.
>
> I've added the Unison-Fix module source-code to the SDK download.  This may
> be helpful to someone because it shows how to send and receive MIDI tuning
> messages.
>
> Jeff

--- In syntheditusers@yahoogroups.com, "Jeff McClintock" <jef@...> wrote:
>
> Hi All,
> SynthEdit Beta V 1.172 available
>
> http://www.synthedit.com/beta.htm
>
> * SYSEX - Now support Roland checksum (SS).
> * Micro-Tuning - Added support for recieving 'SINGLE NOTE TUNING CHANGE
> (REAL-TIME)' and 'KEY-BASED TUNING DUMP'.
> * Unison Fix - Now supports microtuning.
> * MIDI Monitor - Shows more SYSEX message bytes.
> * SDK Modules can now use chm (compiled html) help files.
>
> Best Regards,
> Jeff M

Hi Jeff,

I've just tested the newest beta and have been able to do full keyboard
microtuning using the single note MTS (used the Scala files I created before).

To retune the MTS synth, I removed the MIDI Player module, and sent the MIDI to
the synth from a track in Reaper.

I also tried retuning the synth with the KEY-BASED TUNING DUMP, which is the
more common format used by synths like FM7/8 etc, but this didn't seem to work.
I'll work with it some more tomorrow and create a batch of MID files to
experiment with.

It would be really nice if we could come up with a solution to transmitting the
SYSEX within the plugin itself. Even if we are limited to only one tuning at a
time, this would still enable us to use the new feature for microtuning our VSTi
without having to do it by transmitting the MIDI externally - but we are close
it seems.

This is very exciting to see this working. Thanks very much for the effort!

J

A parting thought:

It is possible, if you have CK Pack 9, to use CK_128x_Filename_Table connected
to the MIDI Player module File Name In, to create a switchable bank of 128
microtunings. The only small problem is that what you will see in the List Entry
are numbers 1-128 rather than the names of the microtunings. All the same, this
could be very useful where one might like to be able to have more than one
tuning available at a time.

If it were that CK_128x_Filename_Table could display the file names (and maybe
the numbers too), then it would be close to perfect for this application.

J

--- In syntheditusers@yahoogroups.com, "stridulationist" <stridulationist@...>
wrote:
>
> Update:
>
> OK - I just tried transmitting the SYSEX again from the MIDI Player, and while
it does not work inside of SynthEdit, it *does* however work perfectly within
the VSTi when after using Save As VST.
>
> So, here we are folks - full keyboard microtuning with MTS!
>
> For anyone interested, you can download the MTS Synth from the files section
of this forum, and save the VST, and it should work with the single note MTS
files just as it is configured now. The MIDI Player will automatically transmit
the SYSEX, and retune the entire instrument, as soon as you open one of the MID
files.
>
> So now we can add microtuning functionality to any SE synth without hassles.
This is a fantastic development.
>
> Thanks Jeff!
>
> J
>

Hi,

The last time i tried SYSEX, to change the data thru a slider "<vv vv>" was
used. I think i was able to reach FFh (255 volts), now it's "LL MM", but when i
test this i can only get to 77h ( 127 volts, going higher doesn't increase the
value ).

Check out this screenshot:
[ http://img209.imageshack.us/img209/7775/sysexse.gif ]

The fake SYSEX msg used:
F0 43 1C 01 LL MM SS F7

Say i want to do this fake msg, how to set it up correctly in the slider?:
F0 43 1C 01 02 03 <datachange: 40h to 70h> F7


It's still confusing me, and i would like to request a resizable MIDI monitor..
long messages can't fully be seen.

That would be it then. Thanks for the explanation, Jeff. I'm having some
problems with Yahoo group search, sorry if this was the 10th time you've had to
answer that question.

Regards,
Jonathan.

--- In syntheditusers@yahoogroups.com, "Jeff McClintock" <jef@...> wrote:
>
> Hi,
>
> Due to customer requests, the ADSR2 is faster (1ms at 0V). I've updated the
> help file to explain...
>
>
>
> ADSR2
>
> Provides a standard Envelope. This Envelope offers faster response than the
> old ADSR.
>
> Segment timing
>
> seconds = 10 0.4 volts - 3
>
> e.g. 0 Volts gives 0.001 seconds (1 ms).
> 10 Volts gives 10 seconds
>
>
>
>
>
> From: syntheditusers@yahoogroups.com [mailto:syntheditusers@yahoogroups.com]
> On Behalf Of typetosmurky
> Sent: Thursday, 26 November 2009 3:29 a.m.
> To: syntheditusers@yahoogroups.com
> Subject: [syntheditusers] Re: ADSR2 Incorrect Duration
>
>
>
>
>
>
>
> Screenshots probably not all that helpful. Here is the link to a zip
> containing a prefab, a midi file, the rendered wave file, and a comparative
> screenshot. Left channel is adsr2, right channel adsr.
>
> http://www.mediafire.com/file/gkjmjkymn4o/adsr_vs_adsr2.zip
>
> Synthedit version is 1.17.
>
> Regards,
> Jonathan.
>
> --- In syntheditusers@yahoogroups.com
> <mailto:syntheditusers%40yahoogroups.com> , "typetosmurky"
> <typetosmurky@> wrote:
> >
> > I installed 1.1 yesterday, and overall I'm really impressed, however ADSR2
> seems to be processing duration inaccurately. Here is a link to Audacity
> screenshots of the output of a patch identical but for the use of ADSR vs.
> ADSR2. The desired duration is 800 mSec. ADSR is pretty close, but ADSR2
> gives about 300 mSec.
> >
> >
> http://www.mediafire.com/?sharekey=9509e7633e4e6059ab1eab3e9fa335ca291f2b5ae
> 28a960e
> >
> > Regards,
> > Jonathan Murphy.
> >
>

--- In syntheditusers@yahoogroups.com, "Jeff McClintock" <jef@...> wrote:
> Hi All,
> SynthEdit Beta V 1.172 available
> * Micro-Tuning - Added support for recieving 'SINGLE NOTE TUNING CHANGE
> (REAL-TIME)' and 'KEY-BASED TUNING DUMP'.
> * Unison Fix - Now supports microtuning.
> Best Regards,
> Jeff M

Hi Jeff,

The 'KEY-BASED TUNING DUMP' appears to not be working.

To help with troubleshooting the bulk dump microtuning, in the files section,
I've updated the MTS_Equal_Temperaments.zip archive to include both MTS Single
Note and Bulk Dump Equal Temperaments. Same as before, there are 2 folders, one
for 60.C.262 and 69.A.440.

These are created with Scala using the synth setting "107: MIDI Tuning Standard
bulk tuning dump, 3 byte".

BTW – I've thoroughly checked the Single Note microtuning and that is working
perfectly.

Thanks,

J

I'm itching to forge ahead with my new project but this is a real show-stopper
right now. Jeff, you said you were going to look into it last week, how did that
go?

BONES

Hi Jeff,

I don't want the change the range, just the databyte value :)

I just want to know the correct way to change the data byte, from 40h (64v) to
like 70h (112v)..just as an example:

F0 43 1C 01 02 03 40 F7
to
F0 43 1C 01 02 03 70 F7


The old method was using <vv vv>:

F0 43 1C 01 02 03 <vv vv> F7   (correct?)

The new method is <LL MM>:

F0 43 1C 01 02 03 <LL MM> F7   (correct?)

..now, when i try the new method. The max. hexidecimal value i can get is 77h 
...i would expect 7Fh.
See the screenshot, in my previous post.
Or am a doing something wrong, that's what i want to know.

cheers,
rob




--- In syntheditusers@yahoogroups.com, "Jeff McClintock" <jef@...> wrote:

> DO you want the range 40-70h?, Currently the SYSEX controller will always
> send a full range 0-127 (0 - 7Fh).