Dave Smith Instruments SYNTHESIZERS

From: "Bernie Kornowicz" <kornowicz@...>

> They tell me that my M-Audio Audiophile 2496 has a bad driver, yet the
> Soundtower Alesis QS editor works fine with my QS6.2 and the same
> soundcard.
>
This is just plain retarded. everyone else can write programs that handle
different MIDI ports. Especially these days where it's all abstracted away
into the OS anyway so no matter what MIDI port you own, the software just
opens a port and chucks data into it.

the reason it doesn't work is it's sloppy sloppy software.

hurry up, Psicraft, please!



julian

Hi Julian/Bernie and anyone else,

Normally, when responding to questions regarding Midi communication 
and Evolver we assume that the Evolver is setup correctly (eg. 
Evolver Main Setting: Midi Transmit/Receive).

Well sometimes it is just that: an assumption but hey ... check those 
settings then read on. So even though we are not there to check your 
cables and setup, a couple comments/observations from our experiences 
might be of help.

The editor for PC has the same engine to access MIDI ports as any 
other our products including QSEditPro. There are many Midi 
Interfaces around and it is simply not true that all work well and 
that our programm is "...sloppy, sloppy." If this was true the 
program would work no matter what or not work at all. If the PC user 
has any of those there interfaces: Terratec AWS, old MOTO paraller 
port interface or M-Audio 2496, it is a common knowledge (please 
check corresponding user mailing groups if you wish) that those 
products have problems with data transmission.

They are all good for playing notes and etc. but their drivers have 
either inadequate buffers settings or bad memory allocation. Some 
interfaces do not sort the data properly with the midi clock data 
being sent along with the data evolver is sending. Simply, they are 
not fully suitable for the data transfer with the Midi Clock ON. The 
editor, as opposed to other Midi programs like Midi-OX, checks the 
incoming data for it's size and validity. If the incoming data is 
missing even one data packet it is simply discharged. The other 
general midi programs have no such filters and they may give users an 
impression that everything is working well but our editor is more 
honest. 

cheers
Derek

SoundTower Help Desk

www.soundtower.com         

--- In DSI_Evolver@yahoogroups.com, "mr julian" <jujulilianan@w...> 
wrote:
>
> 
> From: "Bernie Kornowicz" <kornowicz@c...>
> 
> > They tell me that my M-Audio Audiophile 2496 has a bad driver, 
yet the
> > Soundtower Alesis QS editor works fine with my QS6.2 and the same
> > soundcard.
> >
> This is just plain retarded. everyone else can write programs that 
handle
> different MIDI ports. Especially these days where it's all 
abstracted away
> into the OS anyway so no matter what MIDI port you own, the 
software just

> opens a port and chucks data into it.
> 
> the reason it doesn't work is it's sloppy sloppy software.
> 
> hurry up, Psicraft, please!
> 
> 
> 
> julian
>

Hi Derek,

Thanks for the reply. Looks like my Poly is set up correctly for 
midi, so the problem must be the soundcard. However, I'm not about 
to go out and buy a new one when it works fine with all of my other 
software. Looks like I'll just have to wait for another editor.

Bernie


--- In DSI_Evolver@yahoogroups.com, "soundtower_helpdesk" 
<soundtower_helpdesk@y...> wrote:
>
> Hi Julian/Bernie and anyone else,
> 
> Normally, when responding to questions regarding Midi 
communication 
> and Evolver we assume that the Evolver is setup correctly (eg. 
> Evolver Main Setting: Midi Transmit/Receive).
> 
> Well sometimes it is just that: an assumption but hey ... check 
those 
> settings then read on. So even though we are not there to check 
your 
> cables and setup, a couple comments/observations from our 
experiences 
> might be of help.
> 
> The editor for PC has the same engine to access MIDI ports as any 
> other our products including QSEditPro. There are many Midi 
> Interfaces around and it is simply not true that all work well and 
> that our programm is "...sloppy, sloppy." If this was true the 
> program would work no matter what or not work at all. If the PC 
user 
> has any of those there interfaces: Terratec AWS, old MOTO paraller 
> port interface or M-Audio 2496, it is a common knowledge (please 
> check corresponding user mailing groups if you wish) that those 
> products have problems with data transmission.
> 
> They are all good for playing notes and etc. but their drivers 
have 
> either inadequate buffers settings or bad memory allocation. Some 
> interfaces do not sort the data properly with the midi clock data 
> being sent along with the data evolver is sending. Simply, they 
are 
> not fully suitable for the data transfer with the Midi Clock ON. 
The 
> editor, as opposed to other Midi programs like Midi-OX, checks the 
> incoming data for it's size and validity. If the incoming data is 
> missing even one data packet it is simply discharged. The other 
> general midi programs have no such filters and they may give users 
an 
> impression that everything is working well but our editor is more 
> honest. 
> 
> cheers
> Derek
> 
> SoundTower Help Desk
> 
> www.soundtower.com         
> 
> --- In DSI_Evolver@yahoogroups.com, "mr julian" 
<jujulilianan@w...> 
> wrote:
> >
> > 
> > From: "Bernie Kornowicz" <kornowicz@c...>
> > 
> > > They tell me that my M-Audio Audiophile 2496 has a bad driver, 
> yet the
> > > Soundtower Alesis QS editor works fine with my QS6.2 and the 
same
> > > soundcard.
> > >
> > This is just plain retarded. everyone else can write programs 
that 

> handle
> > different MIDI ports. Especially these days where it's all 
> abstracted away
> > into the OS anyway so no matter what MIDI port you own, the 
> software just
> > opens a port and chucks data into it.
> > 
> > the reason it doesn't work is it's sloppy sloppy software.
> > 
> > hurry up, Psicraft, please!
> > 
> > 
> > 
> > julian
> >
>

No problem; thanks for your candor.

I wish you all the best. If you find another editor that works for 
the M-Audio Audiophile 2496 sound card I'd love to hear from you. 

cheers
Derek

SoundTower Help Desk

www.soundtower.com


--- In DSI_Evolver@yahoogroups.com, "Bernie Kornowicz" 
<kornowicz@c...> wrote:
>
> Hi Derek,
> 
> Thanks for the reply. Looks like my Poly is set up correctly for 
> midi, so the problem must be the soundcard. However, I'm not about 
> to go out and buy a new one when it works fine with all of my other 
> software. Looks like I'll just have to wait for another editor.
> 
> Bernie
> 
> 
> --- In DSI_Evolver@yahoogroups.com, "soundtower_helpdesk" 
> <soundtower_helpdesk@y...> wrote:
> >
> > Hi Julian/Bernie and anyone else,
> > 
> > Normally, when responding to questions regarding Midi 
> communication 
> > and Evolver we assume that the Evolver is setup correctly (eg. 
> > Evolver Main Setting: Midi Transmit/Receive).
> > 
> > Well sometimes it is just that: an assumption but hey ... check 
> those 
> > settings then read on. So even though we are not there to check 
> your 
> > cables and setup, a couple comments/observations from our 
> experiences 
> > might be of help.
> > 
> > The editor for PC has the same engine to access MIDI ports as any 
> > other our products including QSEditPro. There are many Midi 
> > Interfaces around and it is simply not true that all work well 
and 
> > that our programm is "...sloppy, sloppy." If this was true the 
> > program would work no matter what or not work at all. If the PC 
> user 
> > has any of those there interfaces: Terratec AWS, old MOTO 
paraller 
> > port interface or M-Audio 2496, it is a common knowledge (please 
> > check corresponding user mailing groups if you wish) that those 
> > products have problems with data transmission.
> > 
> > They are all good for playing notes and etc. but their drivers 
> have 
> > either inadequate buffers settings or bad memory allocation. Some 
> > interfaces do not sort the data properly with the midi clock data 
> > being sent along with the data evolver is sending. Simply, they 
> are 
> > not fully suitable for the data transfer with the Midi Clock ON. 
> The 
> > editor, as opposed to other Midi programs like Midi-OX, checks 
the 
> > incoming data for it's size and validity. If the incoming data is 
> > missing even one data packet it is simply discharged. The other 
> > general midi programs have no such filters and they may give 
users 
> an 
> > impression that everything is working well but our editor is more 
> > honest. 
> > 
> > cheers
> > Derek
> > 
> > SoundTower Help Desk
> > 
> > www.soundtower.com         
> > 
> > --- In DSI_Evolver@yahoogroups.com, "mr julian" 
> <jujulilianan@w...> 
> > wrote:
> > >
> > > 
> > > From: "Bernie Kornowicz" <kornowicz@c...>
> > > 
> > > > They tell me that my M-Audio Audiophile 2496 has a bad 
driver, 

> > yet the
> > > > Soundtower Alesis QS editor works fine with my QS6.2 and the 
> same
> > > > soundcard.
> > > >
> > > This is just plain retarded. everyone else can write programs 
> that 
> > handle
> > > different MIDI ports. Especially these days where it's all 
> > abstracted away
> > > into the OS anyway so no matter what MIDI port you own, the 
> > software just
> > > opens a port and chucks data into it.
> > > 
> > > the reason it doesn't work is it's sloppy sloppy software.
> > > 
> > > hurry up, Psicraft, please!
> > > 
> > > 
> > > 
> > > julian
> > >
> >
>

Bernie, why dont you just get a 1x1 USB midi interface? Im sure that a
used one could be had for next to nothing.

And Derek,
It says alot about a company when their reps peruse internet boards.
Bravo and good looking out. 

--- In DSI_Evolver@yahoogroups.com, "Bernie Kornowicz"
<kornowicz@c...> wrote:

>
> Hi Derek,
> 
> Thanks for the reply. Looks like my Poly is set up correctly for 
> midi, so the problem must be the soundcard. However, I'm not about 
> to go out and buy a new one when it works fine with all of my other 
> software. Looks like I'll just have to wait for another editor.
> 
> Bernie
> 
> 
> --- In DSI_Evolver@yahoogroups.com, "soundtower_helpdesk" 
> <soundtower_helpdesk@y...> wrote:
> >
> > Hi Julian/Bernie and anyone else,
> > 
> > Normally, when responding to questions regarding Midi 
> communication 
> > and Evolver we assume that the Evolver is setup correctly (eg. 
> > Evolver Main Setting: Midi Transmit/Receive).
> > 
> > Well sometimes it is just that: an assumption but hey ... check 
> those 
> > settings then read on. So even though we are not there to check 
> your 
> > cables and setup, a couple comments/observations from our 
> experiences 
> > might be of help.
> > 
> > The editor for PC has the same engine to access MIDI ports as any 
> > other our products including QSEditPro. There are many Midi 
> > Interfaces around and it is simply not true that all work well and 
> > that our programm is "...sloppy, sloppy." If this was true the 
> > program would work no matter what or not work at all. If the PC 
> user 
> > has any of those there interfaces: Terratec AWS, old MOTO paraller 
> > port interface or M-Audio 2496, it is a common knowledge (please 
> > check corresponding user mailing groups if you wish) that those 
> > products have problems with data transmission.
> > 
> > They are all good for playing notes and etc. but their drivers 
> have 
> > either inadequate buffers settings or bad memory allocation. Some 
> > interfaces do not sort the data properly with the midi clock data 
> > being sent along with the data evolver is sending. Simply, they 
> are 
> > not fully suitable for the data transfer with the Midi Clock ON. 
> The 
> > editor, as opposed to other Midi programs like Midi-OX, checks the 
> > incoming data for it's size and validity. If the incoming data is 
> > missing even one data packet it is simply discharged. The other 
> > general midi programs have no such filters and they may give users 
> an 
> > impression that everything is working well but our editor is more 
> > honest. 
> > 
> > cheers
> > Derek
> > 
> > SoundTower Help Desk
> > 
> > www.soundtower.com         
> > 
> > --- In DSI_Evolver@yahoogroups.com, "mr julian" 
> <jujulilianan@w...> 
> > wrote:
> > >
> > > 
> > > From: "Bernie Kornowicz" <kornowicz@c...>
> > > 
> > > > They tell me that my M-Audio Audiophile 2496 has a bad driver, 
> > yet the
> > > > Soundtower Alesis QS editor works fine with my QS6.2 and the 
> same
> > > > soundcard.
> > > >
> > > This is just plain retarded. everyone else can write programs 
> that 
> > handle
> > > different MIDI ports. Especially these days where it's all 
> > abstracted away
> > > into the OS anyway so no matter what MIDI port you own, the 
> > software just
> > > opens a port and chucks data into it.
> > > 
> > > the reason it doesn't work is it's sloppy sloppy software.
> > > 
> > > hurry up, Psicraft, please!
> > > 
> > > 
> > > 
> > > julian
> > >
> >
>

Thanks for the tip. I just happen to have one lying around and will 
give it a try.

Bernie


--- In DSI_Evolver@yahoogroups.com, "altitude909" <altitude@o...> 
wrote:
>
> Bernie, why dont you just get a 1x1 USB midi interface? Im sure 
that a
> used one could be had for next to nothing.
> 
> And Derek,
> It says alot about a company when their reps peruse internet 
boards.
> Bravo and good looking out. 
> 
> --- In DSI_Evolver@yahoogroups.com, "Bernie Kornowicz"
> <kornowicz@c...> wrote:
> >
> > Hi Derek,
> > 
> > Thanks for the reply. Looks like my Poly is set up correctly for 
> > midi, so the problem must be the soundcard. However, I'm not 
about 
> > to go out and buy a new one when it works fine with all of my 
other 
> > software. Looks like I'll just have to wait for another editor.
> > 
> > Bernie
> > 
> > 
> > --- In DSI_Evolver@yahoogroups.com, "soundtower_helpdesk" 
> > <soundtower_helpdesk@y...> wrote:
> > >
> > > Hi Julian/Bernie and anyone else,
> > > 
> > > Normally, when responding to questions regarding Midi 
> > communication 
> > > and Evolver we assume that the Evolver is setup correctly (eg. 
> > > Evolver Main Setting: Midi Transmit/Receive).
> > > 
> > > Well sometimes it is just that: an assumption but hey ... 
check 
> > those 
> > > settings then read on. So even though we are not there to 
check 
> > your 
> > > cables and setup, a couple comments/observations from our 
> > experiences 
> > > might be of help.
> > > 
> > > The editor for PC has the same engine to access MIDI ports as 
any 
> > > other our products including QSEditPro. There are many Midi 
> > > Interfaces around and it is simply not true that all work well 
and 
> > > that our programm is "...sloppy, sloppy." If this was true the 
> > > program would work no matter what or not work at all. If the 
PC 
> > user 
> > > has any of those there interfaces: Terratec AWS, old MOTO 
paraller 
> > > port interface or M-Audio 2496, it is a common knowledge 
(please 
> > > check corresponding user mailing groups if you wish) that 
those 
> > > products have problems with data transmission.
> > > 
> > > They are all good for playing notes and etc. but their drivers 
> > have 
> > > either inadequate buffers settings or bad memory allocation. 
Some 
> > > interfaces do not sort the data properly with the midi clock 
data 
> > > being sent along with the data evolver is sending. Simply, 
they 
> > are 
> > > not fully suitable for the data transfer with the Midi Clock 
ON. 
> > The 
> > > editor, as opposed to other Midi programs like Midi-OX, checks 
the 
> > > incoming data for it's size and validity. If the incoming data 
is 
> > > missing even one data packet it is simply discharged. The 
other 
> > > general midi programs have no such filters and they may give 
users 
> > an 
> > > impression that everything is working well but our editor is 
more 
> > > honest. 
> > > 
> > > cheers
> > > Derek
> > > 
> > > SoundTower Help Desk
> > > 
> > > www.soundtower.com         
> > > 
> > > --- In DSI_Evolver@yahoogroups.com, "mr julian" 
> > <jujulilianan@w...> 
> > > wrote:
> > > >
> > > > 
> > > > From: "Bernie Kornowicz" <kornowicz@c...>
> > > > 
> > > > > They tell me that my M-Audio Audiophile 2496 has a bad 
driver, 
> > > yet the
> > > > > Soundtower Alesis QS editor works fine with my QS6.2 and 
the 
> > same
> > > > > soundcard.
> > > > >
> > > > This is just plain retarded. everyone else can write 
programs 

> > that 
> > > handle
> > > > different MIDI ports. Especially these days where it's all 
> > > abstracted away
> > > > into the OS anyway so no matter what MIDI port you own, the 
> > > software just
> > > > opens a port and chucks data into it.
> > > > 
> > > > the reason it doesn't work is it's sloppy sloppy software.
> > > > 
> > > > hurry up, Psicraft, please!
> > > > 
> > > > 
> > > > 
> > > > julian
> > > >
> > >
> >
>

--- In DSI_Evolver@yahoogroups.com, "Bernie Kornowicz"
<kornowicz@c...> wrote:
>
> Thanks for the tip. I just happen to have one lying around and will 
> give it a try.
> 
> Bernie
> 
> 
> --- In DSI_Evolver@yahoogroups.com, "altitude909" <altitude@o...> 
> wrote:
> >
> > Bernie, why dont you just get a 1x1 USB midi interface? Im sure 
> that a
> > used one could be had for next to nothing.
> > 
> > And Derek,
> > It says alot about a company when their reps peruse internet 
> boards.
> > Bravo and good looking out. 
> > 

I've never heard anything bad about the M-audio 2496, I thought it was
one of the most widely used cards for "home" studios.  I did have an
old MOTU paralell interface at one point I could never get to work
though. 

That being said my Soundtower editor is working great and doing almost
everything I need it do. I think the Psi-craft is going to cost about
half of an Evolver, which makes it not worth it to me.  The soundtower
guys are responsive, even though it's hard to get "on the same page"
with them at times. 

> > --- In DSI_Evolver@yahoogroups.com, "Bernie Kornowicz"
> > <kornowicz@c...> wrote:
> > >
> > > Hi Derek,
> > > 
> > > Thanks for the reply. Looks like my Poly is set up correctly for 
> > > midi, so the problem must be the soundcard. However, I'm not 
> about 
> > > to go out and buy a new one when it works fine with all of my 
> other 
> > > software. Looks like I'll just have to wait for another editor.
> > > 
> > > Bernie
> > > 
> > > 
> > > --- In DSI_Evolver@yahoogroups.com, "soundtower_helpdesk" 
> > > <soundtower_helpdesk@y...> wrote:
> > > >
> > > > Hi Julian/Bernie and anyone else,
> > > > 
> > > > Normally, when responding to questions regarding Midi 
> > > communication 
> > > > and Evolver we assume that the Evolver is setup correctly (eg. 
> > > > Evolver Main Setting: Midi Transmit/Receive).
> > > > 
> > > > Well sometimes it is just that: an assumption but hey ... 
> check 
> > > those 
> > > > settings then read on. So even though we are not there to 
> check 
> > > your 
> > > > cables and setup, a couple comments/observations from our 
> > > experiences 
> > > > might be of help.
> > > > 
> > > > The editor for PC has the same engine to access MIDI ports as 
> any 
> > > > other our products including QSEditPro. There are many Midi 
> > > > Interfaces around and it is simply not true that all work well 
> and 
> > > > that our programm is "...sloppy, sloppy." If this was true the 
> > > > program would work no matter what or not work at all. If the 
> PC 
> > > user 
> > > > has any of those there interfaces: Terratec AWS, old MOTO 
> paraller 
> > > > port interface or M-Audio 2496, it is a common knowledge 
> (please 
> > > > check corresponding user mailing groups if you wish) that 
> those 
> > > > products have problems with data transmission.
> > > > 
> > > > They are all good for playing notes and etc. but their drivers 
> > > have 
> > > > either inadequate buffers settings or bad memory allocation. 
> Some 
> > > > interfaces do not sort the data properly with the midi clock 
> data 
> > > > being sent along with the data evolver is sending. Simply, 
> they 
> > > are 
> > > > not fully suitable for the data transfer with the Midi Clock 
> ON. 
> > > The 
> > > > editor, as opposed to other Midi programs like Midi-OX, checks 
> the 
> > > > incoming data for it's size and validity. If the incoming data 
> is 
> > > > missing even one data packet it is simply discharged. The 
> other 
> > > > general midi programs have no such filters and they may give 
> users 
> > > an 
> > > > impression that everything is working well but our editor is 
> more 
> > > > honest. 
> > > > 
> > > > cheers
> > > > Derek
> > > > 
> > > > SoundTower Help Desk
> > > > 
> > > > www.soundtower.com         
> > > > 
> > > > --- In DSI_Evolver@yahoogroups.com, "mr julian" 
> > > <jujulilianan@w...> 
> > > > wrote:
> > > > >
> > > > > 
> > > > > From: "Bernie Kornowicz" <kornowicz@c...>
> > > > > 
> > > > > > They tell me that my M-Audio Audiophile 2496 has a bad 
> driver, 
> > > > yet the
> > > > > > Soundtower Alesis QS editor works fine with my QS6.2 and 
> the 
> > > same
> > > > > > soundcard.
> > > > > >
> > > > > This is just plain retarded. everyone else can write 
> programs 
> > > that 
> > > > handle
> > > > > different MIDI ports. Especially these days where it's all 
> > > > abstracted away
> > > > > into the OS anyway so no matter what MIDI port you own, the 
> > > > software just
> > > > > opens a port and chucks data into it.
> > > > > 
> > > > > the reason it doesn't work is it's sloppy sloppy software.
> > > > > 
> > > > > hurry up, Psicraft, please!
> > > > > 
> > > > > 
> > > > > 
> > > > > julian
> > > > >
> > > >
> > >
> >
>

An alternative interface, like the M-Audio 1x1 USB MIDI I/F,
is a fine idea. It's cheap, it's easy to 'install', and it works.

However, if you are having trouble with an M-Audio 2496,
you might try updating the driver first. Checking their web site,
M-Audio released updated drivers for XP and 2000 back in 
May of this year. A driver update might provide a no-cost solution.

FWIW, M-Audio seem to do a good job supporting their products
in general.

Greg


--- In DSI_Evolver@yahoogroups.com, "rickyannotta" <rickyannotta@y...> wrote:

>
> --- In DSI_Evolver@yahoogroups.com, "Bernie Kornowicz"
> <kornowicz@c...> wrote:
> >
> > Thanks for the tip. I just happen to have one lying around and will 
> > give it a try.
> > 
> > Bernie
> > 
> > 
> > --- In DSI_Evolver@yahoogroups.com, "altitude909" <altitude@o...> 
> > wrote:
> > >
> > > Bernie, why dont you just get a 1x1 USB midi interface? Im sure 
> > that a
> > > used one could be had for next to nothing.
> > > 
> > > And Derek,
> > > It says alot about a company when their reps peruse internet 
> > boards.
> > > Bravo and good looking out. 
> > > 
> 
> I've never heard anything bad about the M-audio 2496, I thought it was
> one of the most widely used cards for "home" studios.  I did have an
> old MOTU paralell interface at one point I could never get to work
> though. 
> 
> That being said my Soundtower editor is working great and doing almost
> everything I need it do. I think the Psi-craft is going to cost about
> half of an Evolver, which makes it not worth it to me.  The soundtower
> guys are responsive, even though it's hard to get "on the same page"
> with them at times. 
> 
>     
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> > > --- In DSI_Evolver@yahoogroups.com, "Bernie Kornowicz"
> > > <kornowicz@c...> wrote:
> > > >
> > > > Hi Derek,
> > > > 
> > > > Thanks for the reply. Looks like my Poly is set up correctly for 
> > > > midi, so the problem must be the soundcard. However, I'm not 
> > about 
> > > > to go out and buy a new one when it works fine with all of my 
> > other 
> > > > software. Looks like I'll just have to wait for another editor.
> > > > 
> > > > Bernie
> > > > 
> > > > 
> > > > --- In DSI_Evolver@yahoogroups.com, "soundtower_helpdesk" 
> > > > <soundtower_helpdesk@y...> wrote:
> > > > >
> > > > > Hi Julian/Bernie and anyone else,
> > > > > 
> > > > > Normally, when responding to questions regarding Midi 
> > > > communication 
> > > > > and Evolver we assume that the Evolver is setup correctly (eg. 
> > > > > Evolver Main Setting: Midi Transmit/Receive).
> > > > > 
> > > > > Well sometimes it is just that: an assumption but hey ... 
> > check 
> > > > those 
> > > > > settings then read on. So even though we are not there to 
> > check 
> > > > your 
> > > > > cables and setup, a couple comments/observations from our 
> > > > experiences 
> > > > > might be of help.
> > > > > 
> > > > > The editor for PC has the same engine to access MIDI ports as 
> > any 
> > > > > other our products including QSEditPro. There are many Midi 
> > > > > Interfaces around and it is simply not true that all work well 
> > and 
> > > > > that our programm is "...sloppy, sloppy." If this was true the 
> > > > > program would work no matter what or not work at all. If the 
> > PC 
> > > > user 
> > > > > has any of those there interfaces: Terratec AWS, old MOTO 
> > paraller 
> > > > > port interface or M-Audio 2496, it is a common knowledge 
> > (please 
> > > > > check corresponding user mailing groups if you wish) that 
> > those 
> > > > > products have problems with data transmission.
> > > > > 
> > > > > They are all good for playing notes and etc. but their drivers 
> > > > have 
> > > > > either inadequate buffers settings or bad memory allocation. 
> > Some 
> > > > > interfaces do not sort the data properly with the midi clock 
> > data 
> > > > > being sent along with the data evolver is sending. Simply, 
> > they 
> > > > are 
> > > > > not fully suitable for the data transfer with the Midi Clock 
> > ON. 
> > > > The 
> > > > > editor, as opposed to other Midi programs like Midi-OX, checks 
> > the 
> > > > > incoming data for it's size and validity. If the incoming data 
> > is 
> > > > > missing even one data packet it is simply discharged. The 
> > other 
> > > > > general midi programs have no such filters and they may give 
> > users 
> > > > an 
> > > > > impression that everything is working well but our editor is 
> > more 
> > > > > honest. 
> > > > > 
> > > > > cheers
> > > > > Derek
> > > > > 
> > > > > SoundTower Help Desk
> > > > > 
> > > > > www.soundtower.com         
> > > > > 
> > > > > --- In DSI_Evolver@yahoogroups.com, "mr julian" 
> > > > <jujulilianan@w...> 
> > > > > wrote:
> > > > > >
> > > > > > 
> > > > > > From: "Bernie Kornowicz" <kornowicz@c...>
> > > > > > 
> > > > > > > They tell me that my M-Audio Audiophile 2496 has a bad 
> > driver, 
> > > > > yet the
> > > > > > > Soundtower Alesis QS editor works fine with my QS6.2 and 
> > the 
> > > > same
> > > > > > > soundcard.
> > > > > > >
> > > > > > This is just plain retarded. everyone else can write 
> > programs 
> > > > that 
> > > > > handle
> > > > > > different MIDI ports. Especially these days where it's all 
> > > > > abstracted away
> > > > > > into the OS anyway so no matter what MIDI port you own, the 
> > > > > software just
> > > > > > opens a port and chucks data into it.
> > > > > > 
> > > > > > the reason it doesn't work is it's sloppy sloppy software.
> > > > > > 
> > > > > > hurry up, Psicraft, please!
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > julian
> > > > > >
> > > > >
> > > >
> > >
> >
>

I had a Motu midi-PC flyer.  Couldn't even get it to turn on (this 
one receives power form the Parallel port itself no wart. MOTU 
support was the most useless if you own a PC (makes soundtower look 
like pros).  I'm no slouch at getting these devices to work, but 
even with Sweetwaters tech's and trying 2 different PC flyers, it 
wouldn't even turn on.  I tried another MOTU interface(not the XT 
but similar) and it worked but the drivers for XP were not written 
well - it was a little flakey.  I think when Motu tried to enter the 
PC midi device market it was like an after-thought. Although I heard 
the XT works well on Win'98.  


--- In DSI_Evolver@...m, "Jeff Storm" <jeff@j...> wrote:
>
> sorry I know this stuff is off topic but ...
> 
> I dont get the bad rap the parallel motu midi gets ( I have the 
xt).  Yah the driver is kinda odd on the install but I have never 
had a problem in windows xp on 2 different boxes now 865pe chipset 
intel machine and a current 939 chipset a64 machine.  I dont get 
into the crazy routing that can be done with the machine.  Now I did 
have issues when I tried to have a usb midi interface and the motu 
xt hooked up at the same time.  That was a timing mess.  The guy I 
got it from couldn't get it to work either.  I wonder if it has 
problems playing with soundcards with built in midi?  I use a rme 
hammerfall so no midi there and all works very good.
>   ----- Original Message ----- 
>   From: rickyannotta 
>   To: DSI_Evolver@yahoogroups.com 
>   Sent: Sunday, December 11, 2005 12:06 AM
>   Subject: [Evolver] Re: Psicraft editor
> 
> 
>   --- In DSI_Evolver@yahoogroups.com, "Bernie Kornowicz"
>   <kornowicz@c...> wrote:
>   >
>   > Thanks for the tip. I just happen to have one lying around and 
will 
>   > give it a try.
>   > 
>   > Bernie
>   > 
>   > 
>   > --- In DSI_Evolver@yahoogroups.com, "altitude909" 
<altitude@o...> 
>   > wrote:
>   > >
>   > > Bernie, why dont you just get a 1x1 USB midi interface? Im 
sure 
>   > that a
>   > > used one could be had for next to nothing.
>   > > 
>   > > And Derek,
>   > > It says alot about a company when their reps peruse internet 
>   > boards.
>   > > Bravo and good looking out. 
>   > > 
> 
>   I've never heard anything bad about the M-audio 2496, I thought 
it was
>   one of the most widely used cards for "home" studios.  I did 
have an
>   old MOTU paralell interface at one point I could never get to 
work
>   though. 
> 
>   That being said my Soundtower editor is working great and doing 
almost
>   everything I need it do. I think the Psi-craft is going to cost 
about
>   half of an Evolver, which makes it not worth it to me.  The 
soundtower
>   guys are responsive, even though it's hard to get "on the same 
page"
>   with them at times. 
> 
>       
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>   > > --- In DSI_Evolver@yahoogroups.com, "Bernie Kornowicz"
>   > > <kornowicz@c...> wrote:
>   > > >
>   > > > Hi Derek,
>   > > > 
>   > > > Thanks for the reply. Looks like my Poly is set up 
correctly for 
>   > > > midi, so the problem must be the soundcard. However, I'm 
not 
>   > about 
>   > > > to go out and buy a new one when it works fine with all of 
my 
>   > other 
>   > > > software. Looks like I'll just have to wait for another 
editor.
>   > > > 
>   > > > Bernie
>   > > > 
>   > > > 
>   > > > --- In DSI_Evolver@yahoogroups.com, "soundtower_helpdesk" 
>   > > > <soundtower_helpdesk@y...> wrote:
>   > > > >
>   > > > > Hi Julian/Bernie and anyone else,
>   > > > > 
>   > > > > Normally, when responding to questions regarding Midi 
>   > > > communication 
>   > > > > and Evolver we assume that the Evolver is setup 
correctly (eg. 
>   > > > > Evolver Main Setting: Midi Transmit/Receive).
>   > > > > 
>   > > > > Well sometimes it is just that: an assumption but 
hey ... 
>   > check 
>   > > > those 
>   > > > > settings then read on. So even though we are not there 
to 
>   > check 
>   > > > your 
>   > > > > cables and setup, a couple comments/observations from 
our 
>   > > > experiences 
>   > > > > might be of help.
>   > > > > 
>   > > > > The editor for PC has the same engine to access MIDI 
ports as 
>   > any 
>   > > > > other our products including QSEditPro. There are many 
Midi 
>   > > > > Interfaces around and it is simply not true that all 
work well 
>   > and 
>   > > > > that our programm is "...sloppy, sloppy." If this was 
true the 
>   > > > > program would work no matter what or not work at all. If 
the 
>   > PC 
>   > > > user 
>   > > > > has any of those there interfaces: Terratec AWS, old 
MOTO 
>   > paraller 
>   > > > > port interface or M-Audio 2496, it is a common knowledge 
>   > (please 
>   > > > > check corresponding user mailing groups if you wish) 
that 
>   > those 
>   > > > > products have problems with data transmission.
>   > > > > 
>   > > > > They are all good for playing notes and etc. but their 
drivers 
>   > > > have 
>   > > > > either inadequate buffers settings or bad memory 
allocation. 
>   > Some 
>   > > > > interfaces do not sort the data properly with the midi 
clock 
>   > data 
>   > > > > being sent along with the data evolver is sending. 
Simply, 
>   > they 
>   > > > are 
>   > > > > not fully suitable for the data transfer with the Midi 
Clock 
>   > ON. 
>   > > > The 
>   > > > > editor, as opposed to other Midi programs like Midi-OX, 
checks 
>   > the 
>   > > > > incoming data for it's size and validity. If the 
incoming data 
>   > is 
>   > > > > missing even one data packet it is simply discharged. 
The 
>   > other 
>   > > > > general midi programs have no such filters and they may 
give 
>   > users 
>   > > > an 
>   > > > > impression that everything is working well but our 
editor is 
>   > more 
>   > > > > honest. 
>   > > > > 
>   > > > > cheers
>   > > > > Derek
>   > > > > 
>   > > > > SoundTower Help Desk
>   > > > > 
>   > > > > www.soundtower.com         
>   > > > > 
>   > > > > --- In DSI_Evolver@yahoogroups.com, "mr julian" 
>   > > > <jujulilianan@w...> 
>   > > > > wrote:
>   > > > > >
>   > > > > > 
>   > > > > > From: "Bernie Kornowicz" <kornowicz@c...>
>   > > > > > 
>   > > > > > > They tell me that my M-Audio Audiophile 2496 has a 
bad 
>   > driver, 
>   > > > > yet the
>   > > > > > > Soundtower Alesis QS editor works fine with my QS6.2 
and 
>   > the 
>   > > > same
>   > > > > > > soundcard.
>   > > > > > >
>   > > > > > This is just plain retarded. everyone else can write 
>   > programs 
>   > > > that 
>   > > > > handle
>   > > > > > different MIDI ports. Especially these days where it's 
all 
>   > > > > abstracted away
>   > > > > > into the OS anyway so no matter what MIDI port you 
own, the 
>   > > > > software just
>   > > > > > opens a port and chucks data into it.
>   > > > > > 
>   > > > > > the reason it doesn't work is it's sloppy sloppy 
software.
>   > > > > > 
>   > > > > > hurry up, Psicraft, please!
>   > > > > > 
>   > > > > > 
>   > > > > > 
>   > > > > > julian
>   > > > > >
>   > > > >
>   > > >
>   > >
>   >
> 
> 
> 
> 
> 
> 
>   SPONSORED LINKS Electronic instrument  Keyboard synthesizers  
Synthesizer music  
>         Electronic music  Music sampler  Electronic musical 
instrument  
> 
> 
> -------------------------------------------------------------------
-----------
>   YAHOO! GROUPS LINKS 
> 
>     a..  Visit your group "DSI_Evolver" on the web.
>       
>     b..  To unsubscribe from this group, send an email to:
>      DSI_Evolver-unsubscribe@yahoogroups.com
>       
>     c..  Your use of Yahoo! Groups is subject to the Yahoo! Terms 
of Service. 
> 
> 
> -------------------------------------------------------------------
-----------
>

From: "bcomnes" <bcomnes@...>

> What should an owner of 2 Mono Evolvers with OS 3.0 polyphonically
> linked together do?
>
> Get the December release?  or wait for the Poly-Release??
>
I'd guess you would get the december release, because two mono evolvers have
a different setup to a polyevolver. :-)

Though monoevolver price plus polyevolver upgrade price is exactly the same
as just the polyevolver price too, so I suppose there will be a few
polyevolver owners working with the mono editor till the version they really
want is released.

Personally, I love the idea of being able to run my monoevolver with a
completely VSTi compatible software interface. Think of all the crazy
automation you'll be able to do from cubase, but with a fantastic real
analogue synth.... I'm going to go nuts! Also a decent standalone editor
function will be very much appreciated.

Though I'm not holding my breath for the new published release dates....
this software has been "about to come out any time now" for what seems like
a year and a half at least...... well, at least we should be able to be
confident that it's had a lot of time to be debugged before we get it!



julian

Hi Mr. Julian & Co,

It's no secret that Vyzor Evolver has been 'soon to be released' for 
over a year now. The reasons for the unintended vaporware FX are 
four-fold:

1. The Evolver has been a monster product to virtualize. Psicraft's 
Vyzors are more than just automatable editors. They are closer 
to 're-imaginings' of what the hardware interface would have been if 
the manufacturer had an unlimited budget for metalwork, controls and 
display hardware. Consequently, whenever we encounter a killer 
feature in the instrument that seems difficult to use via the 
established front-panel paradigm, we develop and implement a new 
paradigm that will stoke the creative fire of the user. The best 
example of this in Vyzor Evolver is the sequencer mode 

http://www.psicraft.com/Products/images/VyzorEvolver_Seq.jpg 

which is visually interactive and includes multitrack muting, 
soloing and recording, scalic and chordal arpeggio generation, as 
well as drag editors and keyboard controls as part of its design. 
Incidentally, having to program sequence 'end' steps has also been 
done away with, allowing you to simply set each sequence's length 
and forget about the number codes. Against the standard business 
practice of releasing a basic version early on and then releasing 
paid upgrades over time, I have opted to postpone the product 
release several times in order to implement features such as these 
so we can release a version 1.0 product that (hopefully) thrills and 
excites all who invest in a copy. 

2. A number of these new features actually forced us to go back and 
change the deep functionality of our editor architecture to make it 
totally robust when interacting with the Evolver's Midi clocks, SPP 
messages etc. Much rework and testing was required to do this right, 
which (once again) pushed back the release.

3. We've been very busy this year with OEM Vyzor editors for other 
manufacturers (TC-Helicon and Akai Professional). For Psicraft, 
these projects were critical because they a) paid the bills, and b) 
they allowed us to 'beta-test' our product release and support 
systems on non-paying customers. We're a new company, and 2005 was 
in many ways our 'baby-steps' year.

4. The underlying editor architecture we have had to rework is in 
fact Sound Quest's Midi Quest XL application. Although separately 
owned, both companies have had a symbiotic relationship since 
Psicraft co-designed the Midi Quest 9 & XL user interface in 2002 
(before this I worked for Sound Quest as their product and marketing 
manager). Psicraft is the only company allowed to licence the MQ 
architecture for 3rd party editor products, and as we have an 
ongoing stake in MQ's features, we spend a lot of our development 
time working with Sound Quest to improve and enhance Midi Quest. Of 
course this works both ways - Sound Quest spends a lot of their 
development time working on the features that we request in order to 
make our latest editor designs possible. In the case of the Evolver, 
there have been major changes (indeed!) this year to the Midi Quest 
architecture, most of which will be announced by Sound Quest when 
Midi Quest 10 is released in early 2006.

...And this is why it's taken so long without a release. In-house 
beta testing is underway now, and (no surprise) we are slipping a 
little bit on the release schedule - Late December is now looking 
more like the 1st week of January as members of our team disappear 
for the holidays, but we may still pull a hat-trick and have Vyzor 
Evolver ready before 2005 is over. As I've said before - It will be 
worth the wait, nonetheless.

With regards to Vyzor integration with Midi Quest: All our Vyzor 
editors will also be available as add-on instrument module upgrades 
for MQ 10 and MQ 10 XL owners. OEM Vyzors such as TC-Helicon Vyzor 
VoiceLive will be free (since these editors were paid for by the 
manufacturer), while Vyzors that have been developed as retail 
products by Psicraft will available for purchase from our Web Store. 
As instrument module upgrades, each of these Vyzors will typically 
cost $20 to $30 less than the complete version that runs without 
requiring Midi Quest. 

I hope this addresses some of your concerns as well as casts some 
light on what's going on with Psicraft and Sound Quest. If any of 
you are planning to be at NAMM, please email me off-list and I will 
be happy to meet up with you in person at the show next month!

Cheers and a very happy holidays to all,

Tony

-----------------
Tony Antoniou,
Psicraft Designs, Inc.


--- In DSI_Evolver@yahoogroups.com, "mr julian" <jujulilianan@w...> 
wrote:
>
> 
> From: "bcomnes" <bcomnes@y...>
> 
> > What should an owner of 2 Mono Evolvers with OS 3.0 
polyphonically
> > linked together do?
> >
> > Get the December release?  or wait for the Poly-Release??
> >
> I'd guess you would get the december release, because two mono 
evolvers have
> a different setup to a polyevolver. :-)
> 
> Though monoevolver price plus polyevolver upgrade price is exactly 
the same
> as just the polyevolver price too, so I suppose there will be a few
> polyevolver owners working with the mono editor till the version 
they really
> want is released.
> 
> Personally, I love the idea of being able to run my monoevolver 
with a
> completely VSTi compatible software interface. Think of all the 
crazy
> automation you'll be able to do from cubase, but with a fantastic 
real
> analogue synth.... I'm going to go nuts! Also a decent standalone 
editor
> function will be very much appreciated.
> 
> Though I'm not holding my breath for the new published release 
dates....
> this software has been "about to come out any time now" for what 
seems like
> a year and a half at least...... well, at least we should be able 
to be
> confident that it's had a lot of time to be debugged before we get 
it!

> 
> 
> 
> julian
>

hey tony,

thanks for taking the time to show your future customers what you've 
been up to. its nice to know you care about us little guys, sitting 
around waiting, and I'm looking forward to its release even more now.

anyway... nuff said. I want it as soon as its ready to sell, so good 
luck with the beta testing, I hope it all goes great for you!



julian

Yahoo! Photos
Ring in the New Year with Photo Calendars. Add photos, events, holidays, whatever.

Hi Jim,

We're still bashing away on it... Many other things have come up to
serve as major distractions and the pending NAMM show is starting to
look like an obstacle too: The last thing we want to do is release 
the product and have our webstore start processing orders when we've 
left town for two weeks: Since all of us will be down at the show, 
there would be nobody minding the shop to handle tech or sales 
support - A potentially nasty situation for our first customers if 
they were to encounter issues with their transactions, downloads or 
configurations. We'll have to postpone the actual release until 
February to avoid such potential problems for our users if the 
editor gets finished too close to our NAMM departure time (two weeks 
from now).

With regards to Vyzor Ion and Micron - These haven't been explicitly
announced in the Ion/Micron forum since they are much further away
from being releasable - I think I've gotten enough of a reputation as
a vapor-merchant from the slipped Vyzor Evolver deadlines that I have
posted here over the last year, and I'm not eager to add to it by
getting the Ion/Micron users stoked up and waiting in high
anticipation as well. This said, I am willing to mention that the Ion
and Micron editors we have under development look really REALLY cool
and have a host of unexpected features beyond VST automation and
intuitive editing interfaces. They are planned for release in Q2 of
2006 - Around May.

"We'll sell no wine before its time" comes to mind... Now I know how
the gang at Access felt last September...

Cheers,

Tony



--- In DSI_Evolver@yahoogroups.com, James Elliott <johans121@y...> 
wrote:
>
>   Tony, any news? I am itchin to get my hands on the evolver and 
the ion versions of your software.
>    
>   Also, I am a member of the ion-micron yahoo group, and I do not 
remember any mention of your products over there. If you did, I may 
have missed it. Anyway, ion and micron users are always complaining 
that there are NO editors or real time librarians for the ion or 
micron (especially the micron-o-nites). You might want to make a 
short visit over there to explain your product in detail. I'm pretty 
positive most of the people in the group would be interested....
>    
>   Regards,
>   Jim
> 
> psicraft_designs <tony@p...> wrote:
>   Hi Mr. Julian & Co,
> 
> It's no secret that Vyzor Evolver has been 'soon to be released' 
for 
> over a year now. The reasons for the unintended vaporware FX are 
> four-fold:
> 
> 1. The Evolver has been a monster product to virtualize. 
Psicraft's 
> Vyzors are more than just automatable editors. They are closer 
> to 're-imaginings' of what the hardware interface would have been 
if 
> the manufacturer had an unlimited budget for metalwork, controls 
and 
> display hardware. Consequently, whenever we encounter a killer 
> feature in the instrument that seems difficult to use via the 
> established front-panel paradigm, we develop and implement a new 
> paradigm that will stoke the creative fire of the user. The best 
> example of this in Vyzor Evolver is the sequencer mode 
> 
> http://www.psicraft.com/Products/images/VyzorEvolver_Seq.jpg 
> 
> which is visually interactive and includes multitrack muting, 
> soloing and recording, scalic and chordal arpeggio generation, as 
> well as drag editors and keyboard controls as part of its design. 
> Incidentally, having to program sequence 'end' steps has also been 
> done away with, allowing you to simply set each sequence's length 
> and forget about the number codes. Against the standard business 
> practice of releasing a basic version early on and then releasing 
> paid upgrades over time, I have opted to postpone the product 
> release several times in order to implement features such as these 
> so we can release a version 1.0 product that (hopefully) thrills 
and 
> excites all who invest in a copy. 
> 
> 2. A number of these new features actually forced us to go back 
and 
> change the deep functionality of our editor architecture to make 
it 
> totally robust when interacting with the Evolver's Midi clocks, 
SPP 
> messages etc. Much rework and testing was required to do this 
right, 
> which (once again) pushed back the release.
> 
> 3. We've been very busy this year with OEM Vyzor editors for other 
> manufacturers (TC-Helicon and Akai Professional). For Psicraft, 
> these projects were critical because they a) paid the bills, and 
b) 
> they allowed us to 'beta-test' our product release and support 
> systems on non-paying customers. We're a new company, and 2005 was 
> in many ways our 'baby-steps' year.
> 
> 4. The underlying editor architecture we have had to rework is in 
> fact Sound Quest's Midi Quest XL application. Although separately 
> owned, both companies have had a symbiotic relationship since 
> Psicraft co-designed the Midi Quest 9 & XL user interface in 2002 
> (before this I worked for Sound Quest as their product and 
marketing 
> manager). Psicraft is the only company allowed to licence the MQ 
> architecture for 3rd party editor products, and as we have an 
> ongoing stake in MQ's features, we spend a lot of our development 
> time working with Sound Quest to improve and enhance Midi Quest. 
Of 
> course this works both ways - Sound Quest spends a lot of their 
> development time working on the features that we request in order 
to 
> make our latest editor designs possible. In the case of the 
Evolver, 
> there have been major changes (indeed!) this year to the Midi 
Quest 
> architecture, most of which will be announced by Sound Quest when 
> Midi Quest 10 is released in early 2006.
> 
> ...And this is why it's taken so long without a release. In-house 
> beta testing is underway now, and (no surprise) we are slipping a 
> little bit on the release schedule - Late December is now looking 
> more like the 1st week of January as members of our team disappear 
> for the holidays, but we may still pull a hat-trick and have Vyzor 
> Evolver ready before 2005 is over. As I've said before - It will 
be 
> worth the wait, nonetheless.
> 
> With regards to Vyzor integration with Midi Quest: All our Vyzor 
> editors will also be available as add-on instrument module 
upgrades 
> for MQ 10 and MQ 10 XL owners. OEM Vyzors such as TC-Helicon Vyzor 
> VoiceLive will be free (since these editors were paid for by the 
> manufacturer), while Vyzors that have been developed as retail 
> products by Psicraft will available for purchase from our Web 
Store. 
> As instrument module upgrades, each of these Vyzors will typically 
> cost $20 to $30 less than the complete version that runs without 
> requiring Midi Quest. 
> 
> I hope this addresses some of your concerns as well as casts some 
> light on what's going on with Psicraft and Sound Quest. If any of 
> you are planning to be at NAMM, please email me off-list and I 
will 
> be happy to meet up with you in person at the show next month!
> 
> Cheers and a very happy holidays to all,
> 
> Tony
> 
> -----------------
> Tony Antoniou,
> Psicraft Designs, Inc.
> 
> 
> --- In DSI_Evolver@yahoogroups.com, "mr julian" 
<jujulilianan@w...> 
> wrote:
> >
> > 
> > From: "bcomnes" <bcomnes@y...>
> > 
> > > What should an owner of 2 Mono Evolvers with OS 3.0 
> polyphonically
> > > linked together do?
> > >
> > > Get the December release?  or wait for the Poly-Release??
> > >
> > I'd guess you would get the december release, because two mono 
> evolvers have
> > a different setup to a polyevolver. :-)
> > 
> > Though monoevolver price plus polyevolver upgrade price is 
exactly 
> the same
> > as just the polyevolver price too, so I suppose there will be a 
few
> > polyevolver owners working with the mono editor till the version 
> they really
> > want is released.
> > 
> > Personally, I love the idea of being able to run my monoevolver 
> with a
> > completely VSTi compatible software interface. Think of all the 
> crazy
> > automation you'll be able to do from cubase, but with a 
fantastic 
> real
> > analogue synth.... I'm going to go nuts! Also a decent 
standalone 
> editor
> > function will be very much appreciated.
> > 
> > Though I'm not holding my breath for the new published release 
> dates....
> > this software has been "about to come out any time now" for what 
> seems like
> > a year and a half at least...... well, at least we should be 
able 
> to be
> > confident that it's had a lot of time to be debugged before we 
get 
> it!
> > 
> > 
> > 
> > julian
> >
> 
> 
> 
> 
> 
> 
> 
>   SPONSORED LINKS 
>         Electronic instrument   Keyboard synthesizers   
Synthesizer music     Electronic music   Music sampler   Electronic 
musical instrument 
>     
> ---------------------------------
>   YAHOO! GROUPS LINKS 
> 
>     
>     Visit your group "DSI_Evolver" on the web.
>     
>     To unsubscribe from this group, send an email to:
>  DSI_Evolver-unsubscribe@yahoogroups.com
>     
>     Your use of Yahoo! Groups is subject to the Yahoo! Terms of 
Service. 
> 
>     
> ---------------------------------
>   
> 
>   
> 
> 
> 
> 			
> ---------------------------------
> Yahoo! Photos
>  Ring in the New Year with Photo Calendars. Add photos, events, 
holidays, whatever.
>

On Jan 6, 2006, at 12:46 PM, psicraft_designs wrote:

> "We'll sell no wine before its time" comes to mind... Now I know how
> the gang at Access felt last September...

Hopefully the editor will be substantially more non-beta at release 
time than the Virus TI.

Amen to that!

Tony

> -----Original Message-----
> From: DSI_Evolver@yahoogroups.com 
> [mailto:DSI_Evolver@yahoogroups.com] On Behalf Of M Stevens
> Sent: January 6, 2006 4:03 PM
> To: DSI_Evolver@yahoogroups.com
> Subject: Re: [Evolver] Re: Psicraft editor
> 
> 
> 
> On Jan 6, 2006, at 12:46 PM, psicraft_designs wrote:
> 
> > "We'll sell no wine before its time" comes to mind... Now I 
> know how 
> > the gang at Access felt last September...
> 
> Hopefully the editor will be substantially more non-beta at release 
> time than the Virus TI.
> 
> 
> 
>  
> Yahoo! Groups Links
> 
> 
> 
>  
> 
> 
> 
> 
> 
> 
> 
>

Yahoo! Photos
Ring in the New Year with Photo Calendars. Add photos, events, holidays, whatever.

Yahoo! Photos
Got holiday prints? See all the ways to get quality prints in your hands ASAP.

Hi,

check that you don't have Lock Seq still on after copying patterns.
Also check the global Clock Division knob on the main row.

.jon


2006/1/9, peter sedin <midihooker@...>:

>
> sorry i ment of course that the clock modulation did change on all copied
> patches.
>
> peter sedin <midihooker@...> wrote:
>  hello evolvers.
>  when i have clock resolution as mod. dest and seq.1 as source, and then
> copy that patch. when i then make new step modulations from seq.1 on the new
> copied patch, the old patch seq.1 modulation source allso changes!! very
> anoying!! did some incredible rythmics and wanted to make changes in
> tempo(fills and such) but when i hade made a bunch of them i noticed that
> the old patches had changed also.
>  ??
>  peace out
>  peter
>
>  ________________________________
> Yahoo! Photos
>  Ring in the New Year with Photo Calendars. Add photos, events, holidays,
> whatever.
>
>
>  ________________________________
> Yahoo! Photos
>  Got holiday prints? See all the ways to get quality prints in your hands
> ASAP.
>
>
>  SPONSORED LINKS
>  Electronic instrument Keyboard synthesizers Synthesizer music
>  Electronic music Music sampler Electronic musical instrument
>
>  ________________________________
>  YAHOO! GROUPS LINKS
>
>
>  Visit your group "DSI_Evolver" on the web.
>
>  To unsubscribe from this group, send an email to:
>  DSI_Evolver-unsubscribe@yahoogroups.com
>
>  Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
>
>  ________________________________
>

hi there

has anybody an idea how I can create a text (txt) file that contains  
the memory contents of my polyevolver rack?  (In order to paste it  
into a Logic Environment Multi Instrument for example)
In the Soundtower Editor this doesn't seem possible.

Thanks, best wishes

Ulrich

What format does the file have to be in for logic? Is it just a text representation of the data in hex (such as C0 54 A9). If so, it might be pretty easy to whip something up.

----- Original Message ----
From: Ulrich Reuter <ulireuter@...>
To: DSI_Evolver@yahoogroups.com
Sent: Sunday, January 15, 2006 5:55:16 AM
Subject: [Evolver] patches as text file

    hi there
 
 has anybody an idea how I can create a text (txt) file that contains  
 the memory contents of my polyevolver rack?  (In order to paste it  
 into a Logic Environment Multi Instrument for example)
 In the Soundtower Editor this doesn't seem possible.
 
 Thanks, best wishes
 
 Ulrich
             

        SPONSORED LINKS   
                                                    Electronic instrument                                       Keyboard synthesizers                                       Synthesizer music                                                                     Electronic music                                       Music sampler                                       Electronic musical instrument                                                                 
         YAHOO! GROUPS LINKS 
 
     Visit your group "DSI_Evolver" on the web.
     To unsubscribe from this group, send an email to:
 DSI_Evolver-unsubscribe@yahoogroups.com
     Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

Hi Ulrich

It is possible to copy/get patch names using Patch View window of 
the SoundTower Evolver Editor. Let me know how it works out.

Derek
SoundTower Help Desk

www.soundtower.com

--- In DSI_Evolver@yahoogroups.com, Ulrich Reuter <ulireuter@a...> 
wrote:
>
> hi there
> 
> has anybody an idea how I can create a text (txt) file that 
contains  
> the memory contents of my polyevolver rack?  (In order to paste 
it  

> into a Logic Environment Multi Instrument for example)
> In the Soundtower Editor this doesn't seem possible.
> 
> Thanks, best wishes
> 
> Ulrich
>

Hi... any news on the OSX update?

Many thanks

-Matt

www.bitbin.co.uk
www.tlso.co.uk




--- In DSI_Evolver@yahoogroups.com, "soundtower_helpdesk" 
<soundtower_helpdesk@y...> wrote:

>
> Hi Ulrich
> 
> It is possible to copy/get patch names using Patch View window of 
> the SoundTower Evolver Editor. Let me know how it works out.
> 
> Derek
> SoundTower Help Desk
> 
> www.soundtower.com
> 
> --- In DSI_Evolver@yahoogroups.com, Ulrich Reuter <ulireuter@a...> 
> wrote:
> >
> > hi there
> > 
> > has anybody an idea how I can create a text (txt) file that 
> contains  
> > the memory contents of my polyevolver rack?  (In order to paste 
> it  
> > into a Logic Environment Multi Instrument for example)
> > In the Soundtower Editor this doesn't seem possible.
> > 
> > Thanks, best wishes
> > 
> > Ulrich
> >
>

Ulrich,

Right you are, there is no Patch View window in the MAC editor. 
There is one in the PC version. We will add it in the bext MAC 
update (hopefuly
tomorrow...next day?)

Sorry for the assumption; I guess I am a victem of what Benni Hill 
was so fond of saying: You have to be careful, when you 'Assume,' 
you make an 'A**' of 'u' and 'me.' Next time I'll make sure I know 
if it's MAC or PC.

Cheers!
Derek
SoundTower Help Desk
www.soundtower.com

--- In DSI_Evolver@yahoogroups.com, Ulrich Reuter <ulireuter@a...> 
wrote:
>
> Hello,
> 
> I searched the Program (1.4.2 Mac) and the manual but found 
no "Patch  
> View Window"...
> the "Main window" won't let me select multiple patches in order to 
do  
> "copy" or "paste", maybe of the names. Which command should do 
this job?
> 
> 
> Best
> 
> Ulrich
> 
> 
> Am 16.01.2006 um 02:32 schrieb soundtower_helpdesk:
> 
> > Hi Ulrich
> >
> > It is possible to copy/get patch names using Patch View window of
> > the SoundTower Evolver Editor. Let me know how it works out.
> >
> > Derek
> > SoundTower Help Desk
> >
> > www.soundtower.com
> >
> > --- In DSI_Evolver@yahoogroups.com, Ulrich Reuter 
<ulireuter@a...>

> > wrote:
> > >
> > > hi there
> > >
> > > has anybody an idea how I can create a text (txt) file that
> > contains
> > > the memory contents of my polyevolver rack?  (In order to paste
> > it
> > > into a Logic Environment Multi Instrument for example)
> > > In the Soundtower Editor this doesn't seem possible.
> > >
> > > Thanks, best wishes
> > >
> > > Ulrich
> > >
> >
> >
> >
> >
>

Thanks Derek at least I know now I can trust my senses. Looking  
forward to the next day---

Ulrich


Am 17.01.2006 um 04:04 schrieb soundtower_helpdesk:

> Ulrich,
>
> Right you are, there is no Patch View window in the MAC editor.
> There is one in the PC version. We will add it in the bext MAC
> update (hopefuly
> tomorrow...next day?)
>
> Sorry for the assumption; I guess I am a victem of what Benni Hill
> was so fond of saying: You have to be careful, when you 'Assume,'
> you make an 'A**' of 'u' and 'me.' Next time I'll make sure I know
> if it's MAC or PC.
>
> Cheers!
> Derek
> SoundTower Help Desk
> www.soundtower.com

Hi Jim,

It was an excellent NAMM show - I had a couple of quick chats with 
Dave (he had a lot of celebs demoing the PEK and MEK througout the 
show, by the way - It was very busy in his booth). Elsewhere in the 
show, the control surface / controller keyboard craze continues to 
grow with more and more of these affordable studio options popping 
up from manufacturers across the board. In the next 6 months 
Psicraft will be releasing many more OEM Vyzors as well as several 
much-anticipated retail Vyzors. See www.vyzor.com for a quick 
overview.

Ok, ok, I'm teasing you by not getting to the real news on Vyzor 
Evolver - Sorry. We've started on the manual now and are about to 
start external beta testing on Monday. 

Those who can't wait for the official release can contact me off-
list to arrange a pre-release download purchase: This will make you 
part of the beta team for $59 USD (This is the $79 price minus $20 
crossgrade discount which will be automatically applied to pre-
release purchases). Pre-releasers will also get the release version 
when it's ready, of course.

All the best,

Tony

--- In DSI_Evolver@yahoogroups.com, James Elliott <johans121@...> 
wrote:
>
> Ok, NAMM is over, what's the news ;-)
> 
> psicraft_designs <tony@...> wrote:     Hi Jim,
>  
>  We're still bashing away on it... Many other things have come up 
to
>  serve as major distractions and the pending NAMM show is starting 
to
>  look like an obstacle too: The last thing we want to do is 
release 
>  the product and have our webstore start processing orders when 
we've 
>  left town for two weeks: Since all of us will be down at the 
show, 
>  there would be nobody minding the shop to handle tech or sales 
>  support - A potentially nasty situation for our first customers 
if 
>  they were to encounter issues with their transactions, downloads 
or 
>  configurations. We'll have to postpone the actual release until 
>  February to avoid such potential problems for our users if the 
>  editor gets finished too close to our NAMM departure time (two 
weeks 
>  from now).
>  
>  With regards to Vyzor Ion and Micron - These haven't been 
explicitly
>  announced in the Ion/Micron forum since they are much further away
>  from being releasable - I think I've gotten enough of a 
reputation as
>  a vapor-merchant from the slipped Vyzor Evolver deadlines that I 
have
>  posted here over the last year, and I'm not eager to add to it by
>  getting the Ion/Micron users stoked up and waiting in high
>  anticipation as well. This said, I am willing to mention that the 
Ion
>  and Micron editors we have under development look really REALLY 
cool
>  and have a host of unexpected features beyond VST automation and
>  intuitive editing interfaces. They are planned for release in Q2 
of
>  2006 - Around May.
>  
>  "We'll sell no wine before its time" comes to mind... Now I know 
how

>  the gang at Access felt last September...
>  
>  Cheers,
>  
>  Tony
>

Tony,

>Ok, ok, I'm teasing you by not getting to the real news on Vyzor
>Evolver - Sorry. We've started on the manual now and are about to
>start external beta testing on Monday.

Quick question: using the evolver vyzor as a VSTi in cubase SX, do you have 
to employ the standard two track method for controlling external 
instruments? i.e. one MIDI track for the editor routed to the midi out that 
the evolver is connected to, and another MIDI track also routed to the 
evolver that holds the note data.  Or have you guys come up with a way 
around that?

Also, how does it work with data from the evolver?  If I adjust a setting on 
the evolver itself, will the vyzor editor pick it up?

thanks,

Pierre

_________________________________________________________________
Find just what you're after on your PC with Windows Desktop Search - FREE! 
http://desktop.msn.co.za/

Tony, 

How about Poly compatibility?

Bodie

--- In DSI_Evolver@yahoogroups.com, "psicraft_designs" <tony@...> wrote:

>
> Hi Jim,
> 
> Ok, ok, I'm teasing you by not getting to the real news on Vyzor 
> Evolver - Sorry. We've started on the manual now and are about to 
> start external beta testing on Monday. 
>

Hi Bodie,

The version that we are about to beta test is tailored to the Mono 
Evolver. It will work with the Poly however, but multis are not 
supported and there is no provision for working with multiple 
evolvers within the software. For sound design, however it excels on 
both instruments.

We will be releasing a Poly version of the software several months 
from now - Users of the mono version will be able to upgrade for the 
difference in price, so there is no financial reason to play the 
waiting game if you own a poly.

For all those who emailed me off list to get the pre-release 
version: Thanks and I will be contacting you with details to arrange 
your download. We will be using PayPal to authorize the downloads. 
All pre-releasers will have access to the beta report section of the 
website so that we can respond to issues as quick as possible.

To make matters even crazier, we are in the middle of moving our 
offices this week so I apologize for not responding as quickly or as 
personally as I would like to - Despite all this, we are still 
looking good to go for Monday!

Best regards,

Tony

Psicraft Designs
 

--- In DSI_Evolver@yahoogroups.com, "Bodie" <bodie@...> wrote:
>
> Tony, 
> 
> How about Poly compatibility?
> 
> Bodie
> 
> --- In DSI_Evolver@yahoogroups.com, "psicraft_designs" <tony@> 
wrote:
> >
> > Hi Jim,
> > 
> > Ok, ok, I'm teasing you by not getting to the real news on Vyzor 
> > Evolver - Sorry. We've started on the manual now and are about 
to 

> > start external beta testing on Monday. 
> >
>

Hi Pierre,

These are very good questions. In Cubase 3.1, the external 
instruments feature does away with the two-track method and even 
lets you dial in latency compensation for each hardware instrument 
connected via MIDI. For earlier versions, yes - the two track method 
it is.

As for the editor's response to front panel edits, this is a feature 
that will be added prior to the software's first release. Our 
designers started from the premise that users who use the editor 
would not combine it's use with front panel maneuvering. 

Best regards,

Tony

Psicraft Designs  

--- In DSI_Evolver@yahoogroups.com, "Pierre Zeeman" <pierrezee@...> 
wrote:
>
> Tony,
> 
> >Ok, ok, I'm teasing you by not getting to the real news on Vyzor
> >Evolver - Sorry. We've started on the manual now and are about to
> >start external beta testing on Monday.
> 
> Quick question: using the evolver vyzor as a VSTi in cubase SX, do 
you have 
> to employ the standard two track method for controlling external 
> instruments? i.e. one MIDI track for the editor routed to the midi 
out that 
> the evolver is connected to, and another MIDI track also routed to 
the 
> evolver that holds the note data.  Or have you guys come up with a 
way 
> around that?
> 
> Also, how does it work with data from the evolver?  If I adjust a 
setting on 
> the evolver itself, will the vyzor editor pick it up?
> 
> thanks,
> 
> Pierre
> 
> _________________________________________________________________
> Find just what you're after on your PC with Windows Desktop 
Search - FREE! 
> http://desktop.msn.co.za/
>

Tony,

>These are very good questions. In Cubase 3.1, the external
>instruments feature

>As for the editor's response to front panel edits, this is a feature
>that will be added prior to the software's first release. Our


Excellent.  Now I'm very interested :)

rgds

Pierre

_________________________________________________________________
Looking for that special gift? Find it with MSN Search! 
http://search.msn.co.za