Dave Smith Instruments SYNTHESIZERS group photo

Yahoo Groups archive

Dave Smith Instruments SYNTHESIZERS

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

Message

[Evolver] Re: Psicraft editor

2005-12-09 by Bernie Kornowicz

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
> >
>

Attachments

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.