you can let your breath out now...
-
- Posts: 100
- Joined: Wed Mar 31, 2004 4:00 pm
-
- Posts: 307
- Joined: Thu Nov 13, 2003 4:00 pm
- Location: Oregon
- Contact:
I see a lot of agreement about PCIe here, but I suspect that the ones at the top (so to speak) will interpret the market success of usb2 & firewire devices as a sign that it's a good marketable direction to head. So...we should list some of the reasons why we think we'd prefer PCIe (technical and otherwise).
Personally, from using both proprietary firewire based protocols hooked to a PCI/PCIe card (RME, Scope, MOTU etc ALL use firewire chipsets in a proprietary way in some of their products) and comparing this to similar devices implemented on Firewire (compared my Multiface to the fireface400 for instance) the slot based solution seems to achieve better latency figures, higher stability and less overhead for the system overall (assuming proper engineering).
In fact the new PCIe based RME stuff seems poised to allow some rather insane i/o counts when paired with MADI or other high i/o connector types. When I think of that number of datastreams going at once it really makes me wonder if resynthesis on the fly & various granular/timestretching stuff couldn't be pushed much farther on a new Scope platform (ie, since STS5000 already implements it to a certain degree).
With PCIe 4 cards in a system is feasable without bus contention.
With PCIe you don't have to worry about having limited external storage or having to add in a PCIe/PCI based firewire solution just because your bandwidth is gone.
Oh, and some onboard ram like the original DP toolkit does seem like it would be ideal, especially since I can't imagine that the cards would require anything expensive.
Personally, from using both proprietary firewire based protocols hooked to a PCI/PCIe card (RME, Scope, MOTU etc ALL use firewire chipsets in a proprietary way in some of their products) and comparing this to similar devices implemented on Firewire (compared my Multiface to the fireface400 for instance) the slot based solution seems to achieve better latency figures, higher stability and less overhead for the system overall (assuming proper engineering).
In fact the new PCIe based RME stuff seems poised to allow some rather insane i/o counts when paired with MADI or other high i/o connector types. When I think of that number of datastreams going at once it really makes me wonder if resynthesis on the fly & various granular/timestretching stuff couldn't be pushed much farther on a new Scope platform (ie, since STS5000 already implements it to a certain degree).
With PCIe 4 cards in a system is feasable without bus contention.
With PCIe you don't have to worry about having limited external storage or having to add in a PCIe/PCI based firewire solution just because your bandwidth is gone.
Oh, and some onboard ram like the original DP toolkit does seem like it would be ideal, especially since I can't imagine that the cards would require anything expensive.
- cannonball
- Posts: 344
- Joined: Wed Sep 26, 2001 4:00 pm
- Location: italia
hi
i know most people here prefer the scope environments, but
a revisited and better integration or XTC would be cool
and if done right a good marketin step,
most people want the creamware sound on the hand
the equation must be open sfp open audiosequencer
open the creamware vsti or vstfx in the sequencer without too much
tweak or workaround
at the end an easy easy use of creamwareplug or the dsppower in one click
Alesssandro
i know most people here prefer the scope environments, but
a revisited and better integration or XTC would be cool
and if done right a good marketin step,
most people want the creamware sound on the hand
the equation must be open sfp open audiosequencer
open the creamware vsti or vstfx in the sequencer without too much
tweak or workaround
at the end an easy easy use of creamwareplug or the dsppower in one click

Alesssandro
-
- Posts: 83
- Joined: Sat Mar 19, 2005 4:00 pm
- Location: unknown galaxy
-
- Posts: 117
- Joined: Sun Oct 08, 2006 4:00 pm
my 2 cents
Support for control surfaces to work with Scope mixer's or creamware design their own control surface to work with the platform.
Better XTC mode
Vista Drivers
If possible or worth it, Linking a PCIe card with a PCI card, using a Stdm-like cable. PCIe being master to take advantage of its benifits and the older cards can just be Xtra DSP so you can keep the cards you have.

Support for control surfaces to work with Scope mixer's or creamware design their own control surface to work with the platform.
Better XTC mode
Vista Drivers

If possible or worth it, Linking a PCIe card with a PCI card, using a Stdm-like cable. PCIe being master to take advantage of its benifits and the older cards can just be Xtra DSP so you can keep the cards you have.
An stdm like cable is a great idea but I would have thought that there need to be some kind of reclocking to synchronise the data as the pcie would be running alot faster, thus the benifit might be lost.Conqueror's Reign wrote:my 2 cents![]()
Support for control surfaces to work with Scope mixer's or creamware design their own control surface to work with the platform.
Better XTC mode
Vista Drivers![]()
If possible or worth it, Linking a PCIe card with a PCI card, using a Stdm-like cable. PCIe being master to take advantage of its benifits and the older cards can just be Xtra DSP so you can keep the cards you have.
XTC could be made better by allowing project configuration while the host is running but mabye keeping the asio i/o locked. To have mixers that load in a vsti shell would be more user freindly. Then again(thinking aloud here) XTC shouldn't have to be configured at all, it should work "out of the box" so to speak.
-
- Posts: 1963
- Joined: Tue Aug 19, 2003 4:00 pm
- Location: Bath, England
4?darkrezin wrote:ahh, it's not 5 minutes since the announcement and we have 3 pages of speculations on new hardware. It's so boring. Give the guys a break, they'll unleash new hardware when it's the right time :p

At least it shows we're keen


My only advice is that they don't spend all the money on R&D and manufacturing.
Save a third of the budget for marketing, otherwise they will be a tree falling in the forest again.
Budget for support personnel. Do not make this an afterthought.
There was never anything wrong with the product, it was just everything else that was not executed properly. A good product is simply not enough anymore, you need to tell people about it and then support it well.
That is all I have to say on the matter.
Good Luck with the new business.
Save a third of the budget for marketing, otherwise they will be a tree falling in the forest again.
Budget for support personnel. Do not make this an afterthought.
There was never anything wrong with the product, it was just everything else that was not executed properly. A good product is simply not enough anymore, you need to tell people about it and then support it well.
That is all I have to say on the matter.
Good Luck with the new business.