pulsar xtc?
-
Guest
-
Guest
Subject: Re: To Ingo
Hello Ingo:
I feel that I'm wasting my time trying to get from CW emplooyees a little more than marketing definitions.
I wrote you more than one long letter detailing what I consider professional features and what not.
My particural opinion coincide with what most important audio and music instruments magazines ( MIX, Keyboard, Audiomedia, Electronic Musician )think about what are professional features and what not.
For to give an example the A16 with 18 bit converters, even it has some problems, is a much more professional device than Luna.
If you wish to simplify my opinions saying that for me the only important point are the balanced I/Os you'r wrong (of course that balanced I/O are VERY important).
About automation, the MIDI of Pulsar is near in the same place that in ver 1.0.
When I asked you in a recent private mail about which is CW's target for Pulsar, you repply that Pulsar was created for "amateurs, semi-Pro and professional users":
Recognize that this is a very strange definition.
I don't know any other mark that points to a so wide universe, without running the risk of disapoint everybody.
I have nothing to hide, if you wish to transcrip our private e-mails in this forum, do it.
But of course publish the complete texts.
Hello Ingo:
I feel that I'm wasting my time trying to get from CW emplooyees a little more than marketing definitions.
I wrote you more than one long letter detailing what I consider professional features and what not.
My particural opinion coincide with what most important audio and music instruments magazines ( MIX, Keyboard, Audiomedia, Electronic Musician )think about what are professional features and what not.
For to give an example the A16 with 18 bit converters, even it has some problems, is a much more professional device than Luna.
If you wish to simplify my opinions saying that for me the only important point are the balanced I/Os you'r wrong (of course that balanced I/O are VERY important).
About automation, the MIDI of Pulsar is near in the same place that in ver 1.0.
When I asked you in a recent private mail about which is CW's target for Pulsar, you repply that Pulsar was created for "amateurs, semi-Pro and professional users":
Recognize that this is a very strange definition.
I don't know any other mark that points to a so wide universe, without running the risk of disapoint everybody.
I have nothing to hide, if you wish to transcrip our private e-mails in this forum, do it.
But of course publish the complete texts.
-
Guest
Subject: Re: just to ask
>yes, please. just symm. inputs would be great, with a >little higher SNR... (don´t need the racksize)
Let's see. BTW, our SNR is measured under 'real' conditions which means inside a PC, and not just the figures of the converter manufacturer as it is often the case.
>do you mean the second board generation? could you >recommend a chipset? (i´m using intel bx, is solano better >for using more reverbs, because of the hub structure?
Yes, the 2nd generation (Pulsar 2, Luna, Elektra, PowerSampler,..)
I think we got 11 Timeworks in an ASUS CUSL-II (i815) (with a SCOPE board, but you can load many reverbs with a Pulsar II as well, don't know hom many at the moment). This board is exceptionally fine, since neither the EIDE nor the USB controller affect PCI performance.
There are also some good experiences with the AMD 760, we got 10 Timeworks here.
See you at the Messe
Ingo,
CreamWare
>yes, please. just symm. inputs would be great, with a >little higher SNR... (don´t need the racksize)
Let's see. BTW, our SNR is measured under 'real' conditions which means inside a PC, and not just the figures of the converter manufacturer as it is often the case.
>do you mean the second board generation? could you >recommend a chipset? (i´m using intel bx, is solano better >for using more reverbs, because of the hub structure?
Yes, the 2nd generation (Pulsar 2, Luna, Elektra, PowerSampler,..)
I think we got 11 Timeworks in an ASUS CUSL-II (i815) (with a SCOPE board, but you can load many reverbs with a Pulsar II as well, don't know hom many at the moment). This board is exceptionally fine, since neither the EIDE nor the USB controller affect PCI performance.
There are also some good experiences with the AMD 760, we got 10 Timeworks here.
See you at the Messe
Ingo,
CreamWare
-
Guest
Subject: stop this lame crap
Pablo
Pardon me for making assumptions, but it seems to me that you have a severe moaning problem. I agree it does sometimes feel good to moan (I have been known to do so myself), but dragging Ingo into this ridiculous charade isn't going to do any good. Ingo is a tech-support guy, he's not responsible for Creamware's company policy. Having worked in tech support myself, I have to say I am astounded by his willingness to read and post to these forums on top of his usual duties at Creamware.
I am not trying to lick Creamware's ass - I disagree with some of their policies too - but talking vague crap like this is just going to make Ingo less inclined to hang around in these forums.
If your first post was bad, then your second, after Ingo's reply (where he answered pretty much all of your queries and rants) was pretty pathetic. FOR FUCKS SAKE, he gave you some pretty good indications that things are being looked at and changed but this doesn't seem to be good enough for you.
Let me also point out that your infinite faith in magazines is misplaced - magazines are by far the most biased forms of information - they are in their advertisers' pockets. If you don't know and realise this then you really do need to re-examine things. I have worked in the music retail industry and let me tell you, it is a severely fucked up business. They tailor their marketing to anal retentives like you who go on and on about features and stupid inconsequential crap.
Also, let me just say how ugly it is to see private email conversations dragged out in public. Get some fucking manners boy.
This isn't meant as an insult to you at all (I don't know or care enough about you to warrant any particular hostility) I just thought I had to point out an example of extremely lame behaviour, and to let Ingo know that not all of the people who frequent this forum are brain dead morons.
budz
Pablo
Pardon me for making assumptions, but it seems to me that you have a severe moaning problem. I agree it does sometimes feel good to moan (I have been known to do so myself), but dragging Ingo into this ridiculous charade isn't going to do any good. Ingo is a tech-support guy, he's not responsible for Creamware's company policy. Having worked in tech support myself, I have to say I am astounded by his willingness to read and post to these forums on top of his usual duties at Creamware.
I am not trying to lick Creamware's ass - I disagree with some of their policies too - but talking vague crap like this is just going to make Ingo less inclined to hang around in these forums.
If your first post was bad, then your second, after Ingo's reply (where he answered pretty much all of your queries and rants) was pretty pathetic. FOR FUCKS SAKE, he gave you some pretty good indications that things are being looked at and changed but this doesn't seem to be good enough for you.
Let me also point out that your infinite faith in magazines is misplaced - magazines are by far the most biased forms of information - they are in their advertisers' pockets. If you don't know and realise this then you really do need to re-examine things. I have worked in the music retail industry and let me tell you, it is a severely fucked up business. They tailor their marketing to anal retentives like you who go on and on about features and stupid inconsequential crap.
Also, let me just say how ugly it is to see private email conversations dragged out in public. Get some fucking manners boy.
This isn't meant as an insult to you at all (I don't know or care enough about you to warrant any particular hostility) I just thought I had to point out an example of extremely lame behaviour, and to let Ingo know that not all of the people who frequent this forum are brain dead morons.
budz
-
Guest
Subject: Re: stop this lame crap
Sorry if you don't like my posts.
Ingo Raven and Rembert Gantke, independent that I think that they are intelligent and good persons, speak in the name of CreamWare.
Everything they post is what CW allow to be posted.
In private e-mails we spoke in extensive and with much more details about strong and weak points of Pulsar, and I will not publish private mails.
I really prefer that Frank Hund show his face, instead of sending his employees to repply things that he has not courage to repply, but the life is like it is.
Unfortunately I must repply to Ingo, a person that I apreciate to much.
Is far from my wishes to kick Ingo's ass, I can't say the same about other CW's people.
As a proof of good faith to Frank Hund, here is a transcription of the basic MIDI messages (VER 1.0), probably they could help CW WHAT IS A COMPLETE MIDI IMPLEMENTATION.
Probably they have lost the details of the complete MIDI protocol and this is the reason due they can't upgrade the BigMixer BV2 for create a decent automation system.
------------------------------------------------------------
MIDI Manufacturers Association
Table 1 - Summary of MIDI Messages
The following table lists many of the major MIDI messages in numerical
(binary) order. This table is intended as an overview of MIDI, and is by no
means complete. Additional tables are provided through links following.
Additional messages are listed in the printed documentation available from
the MMA.
WARNING! Details about implementing these messages can dramatically impact
compatibility with other products. We strongly recommend consulting the
official Complete MIDI 1.0 Detailed Specification for additional
information.
------------------------------------------------------------------------
=========================================================================
Table 1: MIDI 1.0 Specification Message Summary
Updated 1995 By the MIDI Manufacturers Association
Status Data Byte(s) Description
D7----D0 D7----D0
-------------------------------------------------------------------------
Channel Voice Messages
-------------------------------------------------------------------------
Note Off event
Status Data Byte 1 Data Byte
1000cccc 0kkkkkkk 0vvvvvvv
This message is sent when a
note is released (ended).
(kkkkkkk) is the key (note) number.
(vvvvvvv) is the velocity.
Note On event
Status Data Byte 1 Data Byte
1001cccc 0kkkkkkk 0vvvvvvv
This message is sent when a
note is depressed (start).
(kkkkkkk) is the key (note) number.
(vvvvvvv) is the velocity.
Polyphonic Key Pressure (Aftertouch)
Status Data Byte 1 Data Byte
1010cccc 0kkkkkkk 0vvvvvvv
This message is most often sent by pressing down on the key after it
"bottoms out".
(kkkkkkk) is the key (note) number.
(vvvvvvv) is the pressure value.
Control Change
Status Data Byte 1 Data Byte
1011cccc 0kkkkkkk 0vvvvvvv
This message is sent when a controller
value changes. Controllers include devices
such as pedals and levers.
Certain controller numbers are reserved
for specific purposes. See Channel Mode Messages.
(ccccccc) is the controller number.
(vvvvvvv) is the new value.
Program Change
Status Data Byte 1 Data Byte 2
1100cccc 0ppppppp no data byte 2
This message sent when the patch number changes.
(ppppppp) is the new program number.
Channel Pressure (After-touch)
Status Data Byte 1 Data Byte 2
1101nnnn 0vvvvvvv no data byte 2
This message is most often sent by pressing down
on the key after it "bottoms out". This message
is different from polyphonic after-touch. Use
this message to send the single greatest
pressure value (of all the current depressed keys).
(vvvvvvv) is the pressure value.
Pitch Wheel Change
Status Data Byte 1 Data Byte 2
1110nnnn 0LLLLLLL 0mmmmmmm
This message is sent to indicate a change in the
pitch wheel. The pitch wheel is measured by a
fourteen bit value. Center (no pitch change) is
2000H. Sensitivity is a function of the
transmitter.
(LLLLLLL) are the least significant 7 bits.
(mmmmmm) are the most significant 7 bits.
-------------------------------------------------------------------------
Channel Mode Messages (See also Control Change, above)
-------------------------------------------------------------------------
Status Data Byte 1 Data Byte 2
1011cccc 0kkkkkkk 0vvvvvvv
Channel Mode Messages.
This the same code as the Control
Change (above), but implements Mode
control by using reserved controller
numbers. The numbers are:
Local Control
When Local Control is Off, all devices
on a given channel will respond only to
data received over MIDI. Played data, etc.
will be ignored. Local Control On
restores the functions of the normal
controllers.
c = 122, v = 0: Local Control Off
c = 122, v = 127: Local Control On
All Notes Off
When an All Notes Off is received,
all oscillators will turn off.
c = 123, v = 0: All Notes Off
(See text for description of actual
mode commands.)
c = 124, v = 0: Omni Mode Off
c = 125, v = 0: Omni Mode On
c = 126, v = M: Mono Mode On (Poly Off)
where M is the number of channels
(Omni Off) or 0 (Omni On)
c = 127, v = 0: Poly Mode On (Mono Off)
(Note: These four messages also cause
All Notes Off)
-------------------------------------------------------------------------
System Common Messages
-------------------------------------------------------------------------
System Exclusive
Status(1st byte) Header Bytes
11110000 0iiiiiii
0ddddddd This message makes up for all that MIDI
.. doesn't support. (iiiiiii) is usually a
.. seven-bit Manufacturer's I.D. code. If the Data Bytes synthesizer recognizes the I.D. code as
0ddddddd its own, it will listen to the rest of
.. the message (ddddddd). Otherwise, the
.. message will be ignored. System Exclusive
EOX is used to send bulk dumps such as patch
11110111 parameters and other non-spec data.
(Note: Real-Time messages ONLY may be
interleaved with a System Exclusive.)
This message also is used for extensions
called Universal Exclusive Messages.
________________________________________________________________________
Code Undefined
11110001
_________________________________________________________________________
Song Position Pointer
Status Data Byte 1 Data Byte 2
11110010 0LLLLLLL 0mmmmmmm
This is an internal 14 bit register that
holds the number of MIDI beats (1 beat=
six MIDI clocks) since the start of
the song. L is the LSB, m the MSB.
Song Select
Status Data Byte 1
11110011 0sssssss
The Song Select specifies which sequence
or song is to be played.
Code Undefined
11110100
Code Undefined
11110101
Tune Request
11110110
Tune Request.
Upon receiving a Tune Request, all analog
synthesizers should tune their oscillators.
End of Exclusive (EOX)
11110111
Used to terminate a System Exclusive
dump (see above).
-------------------------------------------------------------------------
System Real-Time Messages
-------------------------------------------------------------------------
Timing Clock
11111000
Sent 24 times per quarter note when
synchronization is required (see text).
Code Undefined
11111001
Start
11111010
Start the current sequence playing.
(This message will be followed with
Timing Clocks).
Continue
11111011
Continue at the point the sequence was
Stopped.
Stop
11111100
Stop the current sequence.
Code Undefined
11111101
Active Sensing
11111110
Use of this message is optional. When
initially sent, the receiver will expect
to receive another Active Sensing message
each 300ms (max), or it will be assume
that the connection has been terminated.
At termination, the receiver will turn off
all voices and return to normal (non-
active sensing) operation.
Reset
11111111
Reset all receivers in the system to
power-up status. This should be used
sparingly, preferably under manual
control. In particular, it should not
be sent on power-up.
------------------------------------------------------------------------
* Table 2 - Expanded Messages List (Status Bytes)
* Table 3 - Summary of Controller Messages (Data Bytes)
* Table 4 - Summary of Note Numbers by Octave
------------------------------------------------------------------------
To MIDI Information Page
Return to MMA Home Page
Sorry if you don't like my posts.
Ingo Raven and Rembert Gantke, independent that I think that they are intelligent and good persons, speak in the name of CreamWare.
Everything they post is what CW allow to be posted.
In private e-mails we spoke in extensive and with much more details about strong and weak points of Pulsar, and I will not publish private mails.
I really prefer that Frank Hund show his face, instead of sending his employees to repply things that he has not courage to repply, but the life is like it is.
Unfortunately I must repply to Ingo, a person that I apreciate to much.
Is far from my wishes to kick Ingo's ass, I can't say the same about other CW's people.
As a proof of good faith to Frank Hund, here is a transcription of the basic MIDI messages (VER 1.0), probably they could help CW WHAT IS A COMPLETE MIDI IMPLEMENTATION.
Probably they have lost the details of the complete MIDI protocol and this is the reason due they can't upgrade the BigMixer BV2 for create a decent automation system.
------------------------------------------------------------
MIDI Manufacturers Association
Table 1 - Summary of MIDI Messages
The following table lists many of the major MIDI messages in numerical
(binary) order. This table is intended as an overview of MIDI, and is by no
means complete. Additional tables are provided through links following.
Additional messages are listed in the printed documentation available from
the MMA.
WARNING! Details about implementing these messages can dramatically impact
compatibility with other products. We strongly recommend consulting the
official Complete MIDI 1.0 Detailed Specification for additional
information.
------------------------------------------------------------------------
=========================================================================
Table 1: MIDI 1.0 Specification Message Summary
Updated 1995 By the MIDI Manufacturers Association
Status Data Byte(s) Description
D7----D0 D7----D0
-------------------------------------------------------------------------
Channel Voice Messages
-------------------------------------------------------------------------
Note Off event
Status Data Byte 1 Data Byte
1000cccc 0kkkkkkk 0vvvvvvv
This message is sent when a
note is released (ended).
(kkkkkkk) is the key (note) number.
(vvvvvvv) is the velocity.
Note On event
Status Data Byte 1 Data Byte
1001cccc 0kkkkkkk 0vvvvvvv
This message is sent when a
note is depressed (start).
(kkkkkkk) is the key (note) number.
(vvvvvvv) is the velocity.
Polyphonic Key Pressure (Aftertouch)
Status Data Byte 1 Data Byte
1010cccc 0kkkkkkk 0vvvvvvv
This message is most often sent by pressing down on the key after it
"bottoms out".
(kkkkkkk) is the key (note) number.
(vvvvvvv) is the pressure value.
Control Change
Status Data Byte 1 Data Byte
1011cccc 0kkkkkkk 0vvvvvvv
This message is sent when a controller
value changes. Controllers include devices
such as pedals and levers.
Certain controller numbers are reserved
for specific purposes. See Channel Mode Messages.
(ccccccc) is the controller number.
(vvvvvvv) is the new value.
Program Change
Status Data Byte 1 Data Byte 2
1100cccc 0ppppppp no data byte 2
This message sent when the patch number changes.
(ppppppp) is the new program number.
Channel Pressure (After-touch)
Status Data Byte 1 Data Byte 2
1101nnnn 0vvvvvvv no data byte 2
This message is most often sent by pressing down
on the key after it "bottoms out". This message
is different from polyphonic after-touch. Use
this message to send the single greatest
pressure value (of all the current depressed keys).
(vvvvvvv) is the pressure value.
Pitch Wheel Change
Status Data Byte 1 Data Byte 2
1110nnnn 0LLLLLLL 0mmmmmmm
This message is sent to indicate a change in the
pitch wheel. The pitch wheel is measured by a
fourteen bit value. Center (no pitch change) is
2000H. Sensitivity is a function of the
transmitter.
(LLLLLLL) are the least significant 7 bits.
(mmmmmm) are the most significant 7 bits.
-------------------------------------------------------------------------
Channel Mode Messages (See also Control Change, above)
-------------------------------------------------------------------------
Status Data Byte 1 Data Byte 2
1011cccc 0kkkkkkk 0vvvvvvv
Channel Mode Messages.
This the same code as the Control
Change (above), but implements Mode
control by using reserved controller
numbers. The numbers are:
Local Control
When Local Control is Off, all devices
on a given channel will respond only to
data received over MIDI. Played data, etc.
will be ignored. Local Control On
restores the functions of the normal
controllers.
c = 122, v = 0: Local Control Off
c = 122, v = 127: Local Control On
All Notes Off
When an All Notes Off is received,
all oscillators will turn off.
c = 123, v = 0: All Notes Off
(See text for description of actual
mode commands.)
c = 124, v = 0: Omni Mode Off
c = 125, v = 0: Omni Mode On
c = 126, v = M: Mono Mode On (Poly Off)
where M is the number of channels
(Omni Off) or 0 (Omni On)
c = 127, v = 0: Poly Mode On (Mono Off)
(Note: These four messages also cause
All Notes Off)
-------------------------------------------------------------------------
System Common Messages
-------------------------------------------------------------------------
System Exclusive
Status(1st byte) Header Bytes
11110000 0iiiiiii
0ddddddd This message makes up for all that MIDI
.. doesn't support. (iiiiiii) is usually a
.. seven-bit Manufacturer's I.D. code. If the Data Bytes synthesizer recognizes the I.D. code as
0ddddddd its own, it will listen to the rest of
.. the message (ddddddd). Otherwise, the
.. message will be ignored. System Exclusive
EOX is used to send bulk dumps such as patch
11110111 parameters and other non-spec data.
(Note: Real-Time messages ONLY may be
interleaved with a System Exclusive.)
This message also is used for extensions
called Universal Exclusive Messages.
________________________________________________________________________
Code Undefined
11110001
_________________________________________________________________________
Song Position Pointer
Status Data Byte 1 Data Byte 2
11110010 0LLLLLLL 0mmmmmmm
This is an internal 14 bit register that
holds the number of MIDI beats (1 beat=
six MIDI clocks) since the start of
the song. L is the LSB, m the MSB.
Song Select
Status Data Byte 1
11110011 0sssssss
The Song Select specifies which sequence
or song is to be played.
Code Undefined
11110100
Code Undefined
11110101
Tune Request
11110110
Tune Request.
Upon receiving a Tune Request, all analog
synthesizers should tune their oscillators.
End of Exclusive (EOX)
11110111
Used to terminate a System Exclusive
dump (see above).
-------------------------------------------------------------------------
System Real-Time Messages
-------------------------------------------------------------------------
Timing Clock
11111000
Sent 24 times per quarter note when
synchronization is required (see text).
Code Undefined
11111001
Start
11111010
Start the current sequence playing.
(This message will be followed with
Timing Clocks).
Continue
11111011
Continue at the point the sequence was
Stopped.
Stop
11111100
Stop the current sequence.
Code Undefined
11111101
Active Sensing
11111110
Use of this message is optional. When
initially sent, the receiver will expect
to receive another Active Sensing message
each 300ms (max), or it will be assume
that the connection has been terminated.
At termination, the receiver will turn off
all voices and return to normal (non-
active sensing) operation.
Reset
11111111
Reset all receivers in the system to
power-up status. This should be used
sparingly, preferably under manual
control. In particular, it should not
be sent on power-up.
------------------------------------------------------------------------
* Table 2 - Expanded Messages List (Status Bytes)
* Table 3 - Summary of Controller Messages (Data Bytes)
* Table 4 - Summary of Note Numbers by Octave
------------------------------------------------------------------------
To MIDI Information Page
Return to MMA Home Page
-
Guest
Subject: we are no soccer-fan-club-i know!
hi,
you have to relax while we are moaning about this prblems we all have wirh our special working-environments.
this is an area where people can meet who can not meet people like soccerfans on each edge of your hometown...
we only have this small area to speak with other people who obviously have some same problems like we have... AND: if this would not be possible, we would still think the problems are still inside of each of us... but that´s not true- we can see it clearly, that there are different problems we can not solve only with our interest and intelligence... there are still many problems (different to all the promises that were following since the first releases of pulsarcards!) ...
and that all is good to know and to exchange with people (you don´t have to forget!) who are really working on their systems and dealing to get rid of their problems...
and: see that we all try to give tipps here in this area... we are not only moaning... not only crap! sometimes it´s necessary to get rid of all this trouble we sometimes have with our machines- sometime we share our success!
... oups, my english is not that good... can´t get the real point but you will understand, i think!
good luck, greetings
t.
hi,
you have to relax while we are moaning about this prblems we all have wirh our special working-environments.
this is an area where people can meet who can not meet people like soccerfans on each edge of your hometown...
we only have this small area to speak with other people who obviously have some same problems like we have... AND: if this would not be possible, we would still think the problems are still inside of each of us... but that´s not true- we can see it clearly, that there are different problems we can not solve only with our interest and intelligence... there are still many problems (different to all the promises that were following since the first releases of pulsarcards!) ...
and that all is good to know and to exchange with people (you don´t have to forget!) who are really working on their systems and dealing to get rid of their problems...
and: see that we all try to give tipps here in this area... we are not only moaning... not only crap! sometimes it´s necessary to get rid of all this trouble we sometimes have with our machines- sometime we share our success!
... oups, my english is not that good... can´t get the real point but you will understand, i think!
good luck, greetings
t.
ingo,
Is it true that pulsar xtc will not run existing vst plug-ins? if not is creamware planning on making a dsp card that will run ANY vst plug-ins?
i am VERY interested in getting a dsp card for my computer but this would detract me from getting one immediately.
ellipsis
<font size=-1>[ This Message was edited by: ellipsis on 2001-08-20 13:40 ]</font>
Is it true that pulsar xtc will not run existing vst plug-ins? if not is creamware planning on making a dsp card that will run ANY vst plug-ins?
i am VERY interested in getting a dsp card for my computer but this would detract me from getting one immediately.
ellipsis
<font size=-1>[ This Message was edited by: ellipsis on 2001-08-20 13:40 ]</font>
ellipsis,
There isn't a single product on the market that runs VST plugins besides a computer running the appropriate OS.
Pulsar XTC runs Creamware plugins (and eventually the 100's of 3rd party developer plugins, but they have to be ported over to work with the XTC interface -- something that isn't supposed to be too hard, but we'll see).
Some of the Creamware plugins are spectacular, particularly those that come inside SCOPE/SP (STS5000 comes to mind here).
There isn't a single product on the market that runs VST plugins besides a computer running the appropriate OS.
Pulsar XTC runs Creamware plugins (and eventually the 100's of 3rd party developer plugins, but they have to be ported over to work with the XTC interface -- something that isn't supposed to be too hard, but we'll see).
Some of the Creamware plugins are spectacular, particularly those that come inside SCOPE/SP (STS5000 comes to mind here).