Dave Smith Instruments SYNTHESIZERS group photo

Yahoo Groups archive

Dave Smith Instruments SYNTHESIZERS

Index last updated: 2026-04-28 22:43 UTC

Thread

Re: [Evolver] Re: Soundtower Update

Re: [Evolver] Re: Soundtower Update

2005-11-30 by Stefan Trippler

Rick, the controller thing works for me, values in the editor are updated as 
well as in the Evolver if I turn knobs on my BCR2000.

Maybe the problem is in your midi chain. Are you sure that the Remote send 
the controllers to both Midi Out and USB at a time ? If yes the problem may 
also be in the editor.
I can imagine that the editor might not exploit middi CCs directly, but 
reacts on the echoed Sysex data from the Evolver. In this case your setup 
wouldn't work.

Regards
Stefan

----- Original Message ----- 
Show quoted textHide quoted text
From: "rickyannotta" <rickyannotta@...>
To: <DSI_Evolver@yahoogroups.com>
Sent: Wednesday, November 30, 2005 5:41 PM
Subject: [Evolver] Re: Soundtower Update


> Okay - contacted soundtower...wait & see what happens. In the
> meantime if anyone has tested the editor responding to CC#'s
> automatically let me know. I would love to start programming with
> the editor via my Novation Remote for cetain things (sliders work
> better for envelope's than knobs).
>
> Here's my routing:
> Evolver Midi Out > Remote Midi In #1 > Remote USB Out > Editor In
> Editor Out > Remote USB In > Remote Midi Out #1 > Evolver Midi
> in
>
>
> --- In DSI_Evolver@yahoogroups.com, "rickyannotta"
> <rickyannotta@y...> wrote:
>>
>>
>> Just installed the 3.0 update and I can't get the editor to update
> CC#
>> parameters in realtime (for ex. I turn a knob on my controller
>> assigned to a CC#, the Evo responds, but the editor does not
> respond).
>>  Just wondering if anyone tried before I contacted soundtower.
>>
>> Thanks
>>
>> Rick
>>
>
>
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>

[Evolver] Re: Soundtower Update

2005-11-30 by rickyannotta

Stephan - thanks for your insight.
The thing is, if the editor is responding to Evolver's front panel 
(in realtime), then "echo'd" cc#'s should logically be working. 
HHMmmmm...
       
The great thing about the Remote is not only does Midi(2x)/USB work 
at the same time, but you have lots of control over *where* midi 
data is routed as well for each I/O. Well thought out gear, but 
things can get confusing too...I will check a few things tonight 
with a fine tooth comb.


--- In DSI_Evolver@yahoogroups.com, "Stefan Trippler" <doct@o...> 
wrote:
>
> Rick, the controller thing works for me, values in the editor are 
updated as 
> well as in the Evolver if I turn knobs on my BCR2000.
> 
> Maybe the problem is in your midi chain. Are you sure that the 
Remote send 
> the controllers to both Midi Out and USB at a time ? If yes the 
problem may 
> also be in the editor.
> I can imagine that the editor might not exploit middi CCs 
directly, but 
> reacts on the echoed Sysex data from the Evolver. In this case 
your setup 
> wouldn't work.
> 
> Regards
> Stefan
> 
> ----- Original Message ----- 
> From: "rickyannotta" <rickyannotta@y...>
> To: <DSI_Evolver@yahoogroups.com>
> Sent: Wednesday, November 30, 2005 5:41 PM
> Subject: [Evolver] Re: Soundtower Update
> 
> 
> > Okay - contacted soundtower...wait & see what happens. In the
> > meantime if anyone has tested the editor responding to CC#'s
> > automatically let me know. I would love to start programming with
> > the editor via my Novation Remote for cetain things (sliders work
> > better for envelope's than knobs).
> >
> > Here's my routing:
> > Evolver Midi Out > Remote Midi In #1 > Remote USB Out > Editor In
> > Editor Out > Remote USB In > Remote Midi Out #1 > Evolver Midi
> > in
> >
> >
> > --- In DSI_Evolver@yahoogroups.com, "rickyannotta"
> > <rickyannotta@y...> wrote:
> >>
> >>
> >> Just installed the 3.0 update and I can't get the editor to 
update
Show quoted textHide quoted text
> > CC#
> >> parameters in realtime (for ex. I turn a knob on my controller
> >> assigned to a CC#, the Evo responds, but the editor does not
> > respond).
> >>  Just wondering if anyone tried before I contacted soundtower.
> >>
> >> Thanks
> >>
> >> Rick
> >>
> >
> >
> >
> >
> >
> >
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
> >
> >
>

[Evolver] Re: Soundtower Update

2005-11-30 by altitude909

Sounds like your routing may be at issue.  I use the 3.0 software with
my Remote 25 and the CC's work perfectly (in fact I am using the
template offered here).

My routing: Evo In/out: Midex 1 in/out, Novation Remote set as
"keyboard" under midi settings in the ST editor.  Thats it

-alt

--- In DSI_Evolver@yahoogroups.com, "rickyannotta" <rickyannotta@y...>
wrote:
Show quoted textHide quoted text
>
> 
> Stephan - thanks for your insight.
> The thing is, if the editor is responding to Evolver's front panel 
> (in realtime), then "echo'd" cc#'s should logically be working. 
> HHMmmmm...
>        
> The great thing about the Remote is not only does Midi(2x)/USB work 
> at the same time, but you have lots of control over *where* midi 
> data is routed as well for each I/O. Well thought out gear, but 
> things can get confusing too...I will check a few things tonight 
> with a fine tooth comb.
> 
> 
> --- In DSI_Evolver@yahoogroups.com, "Stefan Trippler" <doct@o...> 
> wrote:
> >
> > Rick, the controller thing works for me, values in the editor are 
> updated as 
> > well as in the Evolver if I turn knobs on my BCR2000.
> > 
> > Maybe the problem is in your midi chain. Are you sure that the 
> Remote send 
> > the controllers to both Midi Out and USB at a time ? If yes the 
> problem may 
> > also be in the editor.
> > I can imagine that the editor might not exploit middi CCs 
> directly, but 
> > reacts on the echoed Sysex data from the Evolver. In this case 
> your setup 
> > wouldn't work.
> > 
> > Regards
> > Stefan
> > 
> > ----- Original Message ----- 
> > From: "rickyannotta" <rickyannotta@y...>
> > To: <DSI_Evolver@yahoogroups.com>
> > Sent: Wednesday, November 30, 2005 5:41 PM
> > Subject: [Evolver] Re: Soundtower Update
> > 
> > 
> > > Okay - contacted soundtower...wait & see what happens. In the
> > > meantime if anyone has tested the editor responding to CC#'s
> > > automatically let me know. I would love to start programming with
> > > the editor via my Novation Remote for cetain things (sliders work
> > > better for envelope's than knobs).
> > >
> > > Here's my routing:
> > > Evolver Midi Out > Remote Midi In #1 > Remote USB Out > Editor In
> > > Editor Out > Remote USB In > Remote Midi Out #1 > Evolver Midi
> > > in
> > >
> > >
> > > --- In DSI_Evolver@yahoogroups.com, "rickyannotta"
> > > <rickyannotta@y...> wrote:
> > >>
> > >>
> > >> Just installed the 3.0 update and I can't get the editor to 
> update
> > > CC#
> > >> parameters in realtime (for ex. I turn a knob on my controller
> > >> assigned to a CC#, the Evo responds, but the editor does not
> > > respond).
> > >>  Just wondering if anyone tried before I contacted soundtower.
> > >>
> > >> Thanks
> > >>
> > >> Rick
> > >>
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Yahoo! Groups Links
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
>

Re: [Evolver] Re: Soundtower Update

2005-11-30 by Stefan Trippler

> My routing: Evo In/out: Midex 1 in/out, Novation Remote set as
> "keyboard" under midi settings in the ST editor.  Thats it

That's my setting too.
Works perfectly.

----- Original Message ----- 
Show quoted textHide quoted text
From: "altitude909" <altitude@...>
To: <DSI_Evolver@yahoogroups.com>
Sent: Wednesday, November 30, 2005 10:34 PM
Subject: [Evolver] Re: Soundtower Update


> Sounds like your routing may be at issue.  I use the 3.0 software with
> my Remote 25 and the CC's work perfectly (in fact I am using the
> template offered here).
> 
> My routing: Evo In/out: Midex 1 in/out, Novation Remote set as
> "keyboard" under midi settings in the ST editor.  Thats it
> 
> -alt
> 
> --- In DSI_Evolver@yahoogroups.com, "rickyannotta" <rickyannotta@y...>
> wrote:
>>
>> 
>> Stephan - thanks for your insight.
>> The thing is, if the editor is responding to Evolver's front panel 
>> (in realtime), then "echo'd" cc#'s should logically be working. 
>> HHMmmmm...
>>        
>> The great thing about the Remote is not only does Midi(2x)/USB work 
>> at the same time, but you have lots of control over *where* midi 
>> data is routed as well for each I/O. Well thought out gear, but 
>> things can get confusing too...I will check a few things tonight 
>> with a fine tooth comb.
>> 
>> 
>> --- In DSI_Evolver@yahoogroups.com, "Stefan Trippler" <doct@o...> 
>> wrote:
>> >
>> > Rick, the controller thing works for me, values in the editor are 
>> updated as 
>> > well as in the Evolver if I turn knobs on my BCR2000.
>> > 
>> > Maybe the problem is in your midi chain. Are you sure that the 
>> Remote send 
>> > the controllers to both Midi Out and USB at a time ? If yes the 
>> problem may 
>> > also be in the editor.
>> > I can imagine that the editor might not exploit middi CCs 
>> directly, but 
>> > reacts on the echoed Sysex data from the Evolver. In this case 
>> your setup 
>> > wouldn't work.
>> > 
>> > Regards
>> > Stefan
>> > 
>> > ----- Original Message ----- 
>> > From: "rickyannotta" <rickyannotta@y...>
>> > To: <DSI_Evolver@yahoogroups.com>
>> > Sent: Wednesday, November 30, 2005 5:41 PM
>> > Subject: [Evolver] Re: Soundtower Update
>> > 
>> > 
>> > > Okay - contacted soundtower...wait & see what happens. In the
>> > > meantime if anyone has tested the editor responding to CC#'s
>> > > automatically let me know. I would love to start programming with
>> > > the editor via my Novation Remote for cetain things (sliders work
>> > > better for envelope's than knobs).
>> > >
>> > > Here's my routing:
>> > > Evolver Midi Out > Remote Midi In #1 > Remote USB Out > Editor In
>> > > Editor Out > Remote USB In > Remote Midi Out #1 > Evolver Midi
>> > > in
>> > >
>> > >
>> > > --- In DSI_Evolver@yahoogroups.com, "rickyannotta"
>> > > <rickyannotta@y...> wrote:
>> > >>
>> > >>
>> > >> Just installed the 3.0 update and I can't get the editor to 
>> update
>> > > CC#
>> > >> parameters in realtime (for ex. I turn a knob on my controller
>> > >> assigned to a CC#, the Evo responds, but the editor does not
>> > > respond).
>> > >>  Just wondering if anyone tried before I contacted soundtower.
>> > >>
>> > >> Thanks
>> > >>
>> > >> Rick
>> > >>
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > > Yahoo! Groups Links
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> >
>>
> 
> 
> 
> 
> 
> 
> 
> 
> Yahoo! Groups Links
> 
> 
> 
> 
> 
> 
> 
>

[Evolver] Re: Soundtower Update

2005-12-01 by rickyannotta

Okay got it!

I needed to activate the keyboard setting in the editor. It always
these littlest thing...

Thanks  

--- In DSI_Evolver@yahoogroups.com, "Stefan Trippler" <doct@o...> wrote:
Show quoted textHide quoted text
>
> > My routing: Evo In/out: Midex 1 in/out, Novation Remote set as
> > "keyboard" under midi settings in the ST editor.  Thats it
> 
> That's my setting too.
> Works perfectly.
> 
> ----- Original Message ----- 
> From: "altitude909" <altitude@o...>
> To: <DSI_Evolver@yahoogroups.com>
> Sent: Wednesday, November 30, 2005 10:34 PM
> Subject: [Evolver] Re: Soundtower Update
> 
> 
> > Sounds like your routing may be at issue.  I use the 3.0 software with
> > my Remote 25 and the CC's work perfectly (in fact I am using the
> > template offered here).
> > 
> > My routing: Evo In/out: Midex 1 in/out, Novation Remote set as
> > "keyboard" under midi settings in the ST editor.  Thats it
> > 
> > -alt
> > 
> > --- In DSI_Evolver@yahoogroups.com, "rickyannotta" <rickyannotta@y...>
> > wrote:
> >>
> >> 
> >> Stephan - thanks for your insight.
> >> The thing is, if the editor is responding to Evolver's front panel 
> >> (in realtime), then "echo'd" cc#'s should logically be working. 
> >> HHMmmmm...
> >>        
> >> The great thing about the Remote is not only does Midi(2x)/USB work 
> >> at the same time, but you have lots of control over *where* midi 
> >> data is routed as well for each I/O. Well thought out gear, but 
> >> things can get confusing too...I will check a few things tonight 
> >> with a fine tooth comb.
> >> 
> >> 
> >> --- In DSI_Evolver@yahoogroups.com, "Stefan Trippler" <doct@o...> 
> >> wrote:
> >> >
> >> > Rick, the controller thing works for me, values in the editor are 
> >> updated as 
> >> > well as in the Evolver if I turn knobs on my BCR2000.
> >> > 
> >> > Maybe the problem is in your midi chain. Are you sure that the 
> >> Remote send 
> >> > the controllers to both Midi Out and USB at a time ? If yes the 
> >> problem may 
> >> > also be in the editor.
> >> > I can imagine that the editor might not exploit middi CCs 
> >> directly, but 
> >> > reacts on the echoed Sysex data from the Evolver. In this case 
> >> your setup 
> >> > wouldn't work.
> >> > 
> >> > Regards
> >> > Stefan
> >> > 
> >> > ----- Original Message ----- 
> >> > From: "rickyannotta" <rickyannotta@y...>
> >> > To: <DSI_Evolver@yahoogroups.com>
> >> > Sent: Wednesday, November 30, 2005 5:41 PM
> >> > Subject: [Evolver] Re: Soundtower Update
> >> > 
> >> > 
> >> > > Okay - contacted soundtower...wait & see what happens. In the
> >> > > meantime if anyone has tested the editor responding to CC#'s
> >> > > automatically let me know. I would love to start programming with
> >> > > the editor via my Novation Remote for cetain things (sliders work
> >> > > better for envelope's than knobs).
> >> > >
> >> > > Here's my routing:
> >> > > Evolver Midi Out > Remote Midi In #1 > Remote USB Out > Editor In
> >> > > Editor Out > Remote USB In > Remote Midi Out #1 > Evolver Midi
> >> > > in
> >> > >
> >> > >
> >> > > --- In DSI_Evolver@yahoogroups.com, "rickyannotta"
> >> > > <rickyannotta@y...> wrote:
> >> > >>
> >> > >>
> >> > >> Just installed the 3.0 update and I can't get the editor to 
> >> update
> >> > > CC#
> >> > >> parameters in realtime (for ex. I turn a knob on my controller
> >> > >> assigned to a CC#, the Evo responds, but the editor does not
> >> > > respond).
> >> > >>  Just wondering if anyone tried before I contacted soundtower.
> >> > >>
> >> > >> Thanks
> >> > >>
> >> > >> Rick
> >> > >>
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> > > Yahoo! Groups Links
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> >
> >>
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Yahoo! Groups Links
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> >
>

[Evolver] Re: Soundtower Update

2005-12-01 by rickyannotta

Played around with the new version last night. I feel I have hands 
on control of this beast for the first time! Whether I decide to 
edit from the Remote, the Evo or the editor everything works 
together for the first time. Turning knobs & sliders on the Remote 
and having it update on the screen in realtime is *very* nice. The 
Remote template posted here is excellent BTW.

One last wish for the Soundtower.  The editor does not seem to 
follow program/bank changes made from the Evo or the midi 
controller, only from within the editor itself.  It's a small gripe, 
but would be a *nice* finishing touch. No more mousing and such just 
to change a bank/program.

Thanks
Rick   


--- In DSI_Evolver@yahoogroups.com, "altitude909" <altitude@o...> 
wrote:
>
> Sounds like your routing may be at issue.  I use the 3.0 software 
with
> my Remote 25 and the CC's work perfectly (in fact I am using the
> template offered here).
> 
> My routing: Evo In/out: Midex 1 in/out, Novation Remote set as
> "keyboard" under midi settings in the ST editor.  Thats it
> 
> -alt
> 
> --- In DSI_Evolver@yahoogroups.com, "rickyannotta" 
<rickyannotta@y...>
> wrote:
> >
> > 
> > Stephan - thanks for your insight.
> > The thing is, if the editor is responding to Evolver's front 
panel 
> > (in realtime), then "echo'd" cc#'s should logically be working. 
> > HHMmmmm...
> >        
> > The great thing about the Remote is not only does Midi(2x)/USB 
work 
> > at the same time, but you have lots of control over *where* midi 
> > data is routed as well for each I/O. Well thought out gear, but 
> > things can get confusing too...I will check a few things tonight 
> > with a fine tooth comb.
> > 
> > 
> > --- In DSI_Evolver@yahoogroups.com, "Stefan Trippler" 
<doct@o...> 
> > wrote:
> > >
> > > Rick, the controller thing works for me, values in the editor 
are 
> > updated as 
> > > well as in the Evolver if I turn knobs on my BCR2000.
> > > 
> > > Maybe the problem is in your midi chain. Are you sure that the 
> > Remote send 
> > > the controllers to both Midi Out and USB at a time ? If yes 
the 
> > problem may 
> > > also be in the editor.
> > > I can imagine that the editor might not exploit middi CCs 
> > directly, but 
> > > reacts on the echoed Sysex data from the Evolver. In this case 
> > your setup 
> > > wouldn't work.
> > > 
> > > Regards
> > > Stefan
> > > 
> > > ----- Original Message ----- 
> > > From: "rickyannotta" <rickyannotta@y...>
> > > To: <DSI_Evolver@yahoogroups.com>
> > > Sent: Wednesday, November 30, 2005 5:41 PM
> > > Subject: [Evolver] Re: Soundtower Update
> > > 
> > > 
> > > > Okay - contacted soundtower...wait & see what happens. In the
> > > > meantime if anyone has tested the editor responding to CC#'s
> > > > automatically let me know. I would love to start programming 
with
> > > > the editor via my Novation Remote for cetain things (sliders 
work
> > > > better for envelope's than knobs).
> > > >
> > > > Here's my routing:
> > > > Evolver Midi Out > Remote Midi In #1 > Remote USB Out > 
Editor In
> > > > Editor Out > Remote USB In > Remote Midi Out #1 > Evolver 
Midi
> > > > in
> > > >
> > > >
> > > > --- In DSI_Evolver@yahoogroups.com, "rickyannotta"
> > > > <rickyannotta@y...> wrote:
> > > >>
> > > >>
> > > >> Just installed the 3.0 update and I can't get the editor to 
> > update
> > > > CC#
> > > >> parameters in realtime (for ex. I turn a knob on my 
controller
> > > >> assigned to a CC#, the Evo responds, but the editor does not
> > > > respond).
> > > >>  Just wondering if anyone tried before I contacted 
soundtower.
Show quoted textHide quoted text
> > > >>
> > > >> Thanks
> > > >>
> > > >> Rick
> > > >>
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Yahoo! Groups Links
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> >
>

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.