mono/stereo?
you can't put a mono device into a stereo slot or vice-versa.
Pure xtc is better Pills no i'm not sure whats in
Hi Protone,
Here is that general section of my cset.ini:
[board2]
boardid=0
[board1]
boardid=1
[board0]
boardid=2
[SEQPATH]
Path2=C:/xSource
Path1=C:/Program Files/Steinberg/VST Plugins
[ASIO]
XTCMode=1
application=C:/SCOPE/App/XTCApp/XTC.pro
Pluginwrapper1=C:/SCOPE/App/XTCApp/vstsynthplugin.mdl
Pluginwrapper2=C:/SCOPE/App/XTCApp/vstplugin.mdl
Pluginwrapper3=C:/SCOPE/App/XTCApp/vstplugin.mdl
Pluginwrapper4=C:/SCOPE/App/XTCApp/vsthostplugin.mdl
[XTC-Config]
AddHost=1
intBlkSize=256
[Host-Config]
Scoperev=128
[Host-Config]
Numboards=3
Board0=Host
Now, as I said perviously, I have no need for the DirectPlayMixer. I don't have it connected and I get along just fine. For me, having it connected or not has not made my Creamware system any more or less stable that it ever was. My system has other problems, as specified previously. But, it's a personal thing so you choose.
Note: When SFP4.0 was installing I made sure the xSource folder went onto C: drive instead of the default D: drive. I also made sure that the XTC folder went into a generic "VSTPlugins" folder. ie,
C:Program FilesSteinbergVSTPluginsXTC
When I do this, Cubase and Nuendo will both find the folder without any prompting so the first time I load either of those programs after installing XTC, the plugins are already available.
One other thing you might want to try is uninstalling SFP (again...sorry) and before you reinstall it, write this path in:
C:SCOPEAppOxe
From the "Optioanl Plugins" folder on your SFP installation disc (or in the folders that you downloaded off the net) copy any .oxe plugin that you have the licence to use inlucing plugin packs and mixer packs, and paste them into the "Oxe" folder you created on C: Drive.
Do the SFP installation normally, making sure it's putting it's installation in the correct place. The first time you boot SFP all the .oxe's will be registered. The process of activating the .oxe files also copies them into the VSTPluginsXTC folder that you've specified and often makes them run properly.
I had serious troubles with synths in XTC myself....not the same as what you're getting, but errors nonetheless. Since I've been using this method I haven't had any issues at all.
Oh, and by the way for just mixing, try not to have the 'intBlksize' down too low. It puts uneccessary strain on the computer. Obviously you'll need it down farely low when you're triggering synths though. Just be aware that if you're getting crackling and the computer feesl like it's struggling, you should set the sample buffer a bit higher.
Goodluck again,
AudioDan
<font size=-1>[ This Message was edited by: AudioDan on 2005-07-09 19:33 ]</font>
Here is that general section of my cset.ini:
[board2]
boardid=0
[board1]
boardid=1
[board0]
boardid=2
[SEQPATH]
Path2=C:/xSource
Path1=C:/Program Files/Steinberg/VST Plugins
[ASIO]
XTCMode=1
application=C:/SCOPE/App/XTCApp/XTC.pro
Pluginwrapper1=C:/SCOPE/App/XTCApp/vstsynthplugin.mdl
Pluginwrapper2=C:/SCOPE/App/XTCApp/vstplugin.mdl
Pluginwrapper3=C:/SCOPE/App/XTCApp/vstplugin.mdl
Pluginwrapper4=C:/SCOPE/App/XTCApp/vsthostplugin.mdl
[XTC-Config]
AddHost=1
intBlkSize=256
[Host-Config]
Scoperev=128
[Host-Config]
Numboards=3
Board0=Host
Now, as I said perviously, I have no need for the DirectPlayMixer. I don't have it connected and I get along just fine. For me, having it connected or not has not made my Creamware system any more or less stable that it ever was. My system has other problems, as specified previously. But, it's a personal thing so you choose.
Note: When SFP4.0 was installing I made sure the xSource folder went onto C: drive instead of the default D: drive. I also made sure that the XTC folder went into a generic "VSTPlugins" folder. ie,
C:Program FilesSteinbergVSTPluginsXTC
When I do this, Cubase and Nuendo will both find the folder without any prompting so the first time I load either of those programs after installing XTC, the plugins are already available.
One other thing you might want to try is uninstalling SFP (again...sorry) and before you reinstall it, write this path in:
C:SCOPEAppOxe
From the "Optioanl Plugins" folder on your SFP installation disc (or in the folders that you downloaded off the net) copy any .oxe plugin that you have the licence to use inlucing plugin packs and mixer packs, and paste them into the "Oxe" folder you created on C: Drive.
Do the SFP installation normally, making sure it's putting it's installation in the correct place. The first time you boot SFP all the .oxe's will be registered. The process of activating the .oxe files also copies them into the VSTPluginsXTC folder that you've specified and often makes them run properly.
I had serious troubles with synths in XTC myself....not the same as what you're getting, but errors nonetheless. Since I've been using this method I haven't had any issues at all.
Oh, and by the way for just mixing, try not to have the 'intBlksize' down too low. It puts uneccessary strain on the computer. Obviously you'll need it down farely low when you're triggering synths though. Just be aware that if you're getting crackling and the computer feesl like it's struggling, you should set the sample buffer a bit higher.
Goodluck again,
AudioDan
<font size=-1>[ This Message was edited by: AudioDan on 2005-07-09 19:33 ]</font>
Hi,
Question for audiodan and others...
I've been looking to your cset.ini file.
What about the differences could you explain?
Mine:
[XTC-Config]
DirectPlayOutPad2=RIn
DirectPlayOutPad1=LIn
DirectPlayOut=Pulsar2 Analog Dest
AddHost=1
Yours:
[XTC-Config]
AddHost=1
intBlkSize=256
Do you also have something like this in your cset.ini file?
[hw]
intBlkSize=64
And what is it for?
Question for audiodan and others...
I've been looking to your cset.ini file.
What about the differences could you explain?
Mine:
[XTC-Config]
DirectPlayOutPad2=RIn
DirectPlayOutPad1=LIn
DirectPlayOut=Pulsar2 Analog Dest
AddHost=1
Yours:
[XTC-Config]
AddHost=1
intBlkSize=256
Do you also have something like this in your cset.ini file?
[hw]
intBlkSize=64
And what is it for?
Hi Protone,
I explained in my previous post that my cset.ini file will probably look different to yous as I do not use the DirectPlayMixer module. I personally have no use for it. I really just wanted to let you know that it's not a crucial things to have in your XTCProject.pro .
I beleive the:
[hw]
intBlksize=64
...entry is to specify the sample buffer that SFP will run when it loads up.
Just to emphasise, SFP sample buffer.....not XTC sample buffer. As I explained in an earlier post, SFP and XTC are two seperate entities and so both need their own configuration in the cset.ini file.
Hope that helps,
Cheers,
AudioDan
<font size=-1>[ This Message was edited by: AudioDan on 2005-07-10 09:03 ]</font>
I explained in my previous post that my cset.ini file will probably look different to yous as I do not use the DirectPlayMixer module. I personally have no use for it. I really just wanted to let you know that it's not a crucial things to have in your XTCProject.pro .
I beleive the:
[hw]
intBlksize=64
...entry is to specify the sample buffer that SFP will run when it loads up.
Just to emphasise, SFP sample buffer.....not XTC sample buffer. As I explained in an earlier post, SFP and XTC are two seperate entities and so both need their own configuration in the cset.ini file.
Hope that helps,
Cheers,
AudioDan
<font size=-1>[ This Message was edited by: AudioDan on 2005-07-10 09:03 ]</font>
Hi,
Me again...
The day I know it all will be the day the chosen one arrives....
XTC works swell know.
Stupid question about M/S but ok.
The only thing know is that I cant audiomixdown in cubase know...
From the default xtcproject.pro to your own xtcproject.pro:
Tried it failed it.
It's not the same ass SFP where my project works well and I can audiomixdown in cubase.
So what the difference between the two.
In the default xtcproject.pro there isn't a mixer.
Is it needed and where would I put it?
What is the connections you want to make to be sure that you can audiomixdown in cubase under XTC?
What about midiconnections and is the one in the default xtcproject.pro enough?
I think about the mixer...
I asking because in my default xtcproject.pro
I can do ''what i want'' but not audiomixdown...
Greetzzz
Me again...
The day I know it all will be the day the chosen one arrives....
XTC works swell know.
Stupid question about M/S but ok.
The only thing know is that I cant audiomixdown in cubase know...
From the default xtcproject.pro to your own xtcproject.pro:
Tried it failed it.
It's not the same ass SFP where my project works well and I can audiomixdown in cubase.
So what the difference between the two.
In the default xtcproject.pro there isn't a mixer.
Is it needed and where would I put it?
What is the connections you want to make to be sure that you can audiomixdown in cubase under XTC?
What about midiconnections and is the one in the default xtcproject.pro enough?
I think about the mixer...
I asking because in my default xtcproject.pro
I can do ''what i want'' but not audiomixdown...
Greetzzz
Tried it again and succes.
I can record in Cubase again...
Put in the Stm 1632, did some ''logic'' connections and boom...
It worked...
On 2005-07-08 00:01, Protone wrote:
Don't seem to understand where to put the directmixercontainer module...
Narly:
Don't worry about that yet. You should be able to have audio and VSTs without that.
I'm wondering and tried to disconnect it but I don't have any sound then...
When I start Cubase I don't have sound but when I go to control panel - direct monitoring - connect to Pulsar2 Analg Dest.
The sound is there...
Asio2 16bit source to (directplaymixercontainer?) to STM 1632
P2 Analog Source to STM 1632
STM 1632 Asio2 Dest
STM 1632 mix to P2 Analog Dest ?
I can record in Cubase again...
Put in the Stm 1632, did some ''logic'' connections and boom...
It worked...
On 2005-07-08 00:01, Protone wrote:
Don't seem to understand where to put the directmixercontainer module...
Narly:
Don't worry about that yet. You should be able to have audio and VSTs without that.
I'm wondering and tried to disconnect it but I don't have any sound then...
When I start Cubase I don't have sound but when I go to control panel - direct monitoring - connect to Pulsar2 Analg Dest.
The sound is there...
Asio2 16bit source to (directplaymixercontainer?) to STM 1632
P2 Analog Source to STM 1632
STM 1632 Asio2 Dest
STM 1632 mix to P2 Analog Dest ?
Hi Protone,
My advice to you is to completely forget about the idea of including a mixer in your XTCProject.pro. In fact you really should forget about editing the XTC project at all.
The Scope control panel where you've been activating in and outs, ASIO and direct monitoring, is the official way of editing the XTCProject.pro . When you change you ins and outs in that control panel, the hardware inputs and outputs in XTCProject.pro are added/removed and routed autmatically, so you don't have to do anything. As I said in a previous post, I didn't know it was possible to edit the XTCProject until a month or so ago, and I've got along just fine without it for about three years now.
Now, as far as I'm concerned any FX based module, that is synths, effects and mixers, won't work in the XTCProject.pro . The only modules that will work in that are physical input/output modules eg Analog in/out, MIDI In/Out etc. They are really all you need anyway.
I'm assuming you're using Cubase SX3 here....let me know if you're not.
In the Scope/XTC control panel, have all your available ins and outs active, and you really should have ASIO 2 + 24bit....16 bit is boring so use the best resolution you can. At this point leave the Direct Play option at "not connected".
'Reload IOs' - 'Apply' - then go to 'VST Inputs' (just below VST Audiobay) and press 'Reset'. You may notice - if the I/O configuration has changed - that the list of available I/O changes in 'VST Inputs'. Do the same thing in 'VST Outputs'.
Click 'OK' and get out of 'Device Setup' Menu. Go to 'VST Connections' and add enough input and output busses (I generally have Mono inputs and Stereo outputs) to cover all you available ins and outs, assign them in order or how frequently they will be used and then save them as presets. Note: you must save the Input Preset seperately from the Output Preset. They don't save as one. (If you have any I/O that you just won't be using at all, don't bother adding those in...for example, if you have a Z-Link port, but no Z-link converter, there's no point in having it in there)
Set the physical output off the card that you have connected to your monitoring system, as the default output in VST Connections.
Now you're ready to open a session. When the session is open, add in a MIDI track and then load up the XTC synth that you want to use. Set the output of the MIDI track to the XTC Synth and the input from the MIDI device you're pluging you keyboard through. (I'm assuming that you have a keyboard too). Activate the 'Monitor' button (located directly to the right of the 'Record Enable' button) on the MIDI channel. You should be able to hit a key on you MIDI keyboard now, and hear a sound from the XTC Synth. If you can't and you've followed these steps carefully, then there's something else wrong in the system.
If this is the case and you're using an edited version of XTCProject.pro, please try to restore the origianl, and repeat the first few Scope/XTC related steps of this proceedure.
OK let me know how you go.
Goodluck,
AudioDan
<font size=-1>[ This Message was edited by: AudioDan on 2005-07-10 21:12 ]</font>
My advice to you is to completely forget about the idea of including a mixer in your XTCProject.pro. In fact you really should forget about editing the XTC project at all.
The Scope control panel where you've been activating in and outs, ASIO and direct monitoring, is the official way of editing the XTCProject.pro . When you change you ins and outs in that control panel, the hardware inputs and outputs in XTCProject.pro are added/removed and routed autmatically, so you don't have to do anything. As I said in a previous post, I didn't know it was possible to edit the XTCProject until a month or so ago, and I've got along just fine without it for about three years now.
Now, as far as I'm concerned any FX based module, that is synths, effects and mixers, won't work in the XTCProject.pro . The only modules that will work in that are physical input/output modules eg Analog in/out, MIDI In/Out etc. They are really all you need anyway.
I'm assuming you're using Cubase SX3 here....let me know if you're not.
In the Scope/XTC control panel, have all your available ins and outs active, and you really should have ASIO 2 + 24bit....16 bit is boring so use the best resolution you can. At this point leave the Direct Play option at "not connected".
'Reload IOs' - 'Apply' - then go to 'VST Inputs' (just below VST Audiobay) and press 'Reset'. You may notice - if the I/O configuration has changed - that the list of available I/O changes in 'VST Inputs'. Do the same thing in 'VST Outputs'.
Click 'OK' and get out of 'Device Setup' Menu. Go to 'VST Connections' and add enough input and output busses (I generally have Mono inputs and Stereo outputs) to cover all you available ins and outs, assign them in order or how frequently they will be used and then save them as presets. Note: you must save the Input Preset seperately from the Output Preset. They don't save as one. (If you have any I/O that you just won't be using at all, don't bother adding those in...for example, if you have a Z-Link port, but no Z-link converter, there's no point in having it in there)
Set the physical output off the card that you have connected to your monitoring system, as the default output in VST Connections.
Now you're ready to open a session. When the session is open, add in a MIDI track and then load up the XTC synth that you want to use. Set the output of the MIDI track to the XTC Synth and the input from the MIDI device you're pluging you keyboard through. (I'm assuming that you have a keyboard too). Activate the 'Monitor' button (located directly to the right of the 'Record Enable' button) on the MIDI channel. You should be able to hit a key on you MIDI keyboard now, and hear a sound from the XTC Synth. If you can't and you've followed these steps carefully, then there's something else wrong in the system.
If this is the case and you're using an edited version of XTCProject.pro, please try to restore the origianl, and repeat the first few Scope/XTC related steps of this proceedure.
OK let me know how you go.
Goodluck,
AudioDan
<font size=-1>[ This Message was edited by: AudioDan on 2005-07-10 21:12 ]</font>
By the way....'M' and 'S' stand for Mono and Stereo (I think you have already worked that one out, but just to clarify).
Any mixing in the XTC session is done by the Cubase mixer. Think of XTC as a way of providing Cubase with some nice FX plugins and Synths....but no more than that.
Mixdowns are are done through Cubase in the:
'File' - 'Export' - 'Audio Mixdown' menu. You MUST MUST MUST do a "Realtime Mixdown". If you don't then the sound that is mixed down will be completely messed up.
A "Realtime Mixdown" mixes everything down at normal playback speed so that if you have any external FX, either DSP (like Creamware) or physical FX racks, then everything sounds the way it should.
See how you go and let me know if you come up against any problems....but follow my steps closely....that way, if you don't get the correct result we know it's something else in the system that needs changing.
Bye for now,
AudioDan
Any mixing in the XTC session is done by the Cubase mixer. Think of XTC as a way of providing Cubase with some nice FX plugins and Synths....but no more than that.
Mixdowns are are done through Cubase in the:
'File' - 'Export' - 'Audio Mixdown' menu. You MUST MUST MUST do a "Realtime Mixdown". If you don't then the sound that is mixed down will be completely messed up.
A "Realtime Mixdown" mixes everything down at normal playback speed so that if you have any external FX, either DSP (like Creamware) or physical FX racks, then everything sounds the way it should.
See how you go and let me know if you come up against any problems....but follow my steps closely....that way, if you don't get the correct result we know it's something else in the system that needs changing.
Bye for now,
AudioDan
A Good day
My mixdown problem was like you said Audiodan -
'File' - 'Export' - 'Audio Mixdown' menu. You MUST MUST MUST do a "Realtime Mixdown". If you don't then the sound that is mixed down will be completely messed up.
A "Realtime Mixdown" mixes everything down at normal playback speed so that if you have any external FX, either DSP (like Creamware) or physical FX racks, then everything sounds the way it should.
----- REALTIME mixdown -------
Everything is allmost solved....
The synth works, the effects, i can record,...
Nice
Now I changed the xct config but the intBlksize x but damn all those problems:
They start when opening cubase sx 2.0 ( no 3 ) for the future
Illegal interrupt blksize 0
Please delete the intblksize entry in cset.ini
Could not gain acces to the creamware hardware.
SFP is not running or asio source and asio dest modules are not included in your current project. ( I was running Xtc )
When opening an old or new cubase file it says:
Sampelrate could not be set...
In cubase there is nothing I can do or to choose from in:
No clock source
No control panel
No sampel rate
All this ends when I delete the intblksize in cset.ini file...
My latency then in ass pointed in cubase:
24.694 ms...
Why all these troubles?
What am i doing wrong?
It seems easy just add intblksize - but then again check the problems?
I'm forgetting about the mixer but i did connect it the xtcproject.pro... And it seems to work but what do I now
Greetzzzzzzzzzzzzzzzz
My mixdown problem was like you said Audiodan -
'File' - 'Export' - 'Audio Mixdown' menu. You MUST MUST MUST do a "Realtime Mixdown". If you don't then the sound that is mixed down will be completely messed up.
A "Realtime Mixdown" mixes everything down at normal playback speed so that if you have any external FX, either DSP (like Creamware) or physical FX racks, then everything sounds the way it should.
----- REALTIME mixdown -------
Everything is allmost solved....
The synth works, the effects, i can record,...
Nice
Now I changed the xct config but the intBlksize x but damn all those problems:
They start when opening cubase sx 2.0 ( no 3 ) for the future
Illegal interrupt blksize 0
Please delete the intblksize entry in cset.ini
Could not gain acces to the creamware hardware.
SFP is not running or asio source and asio dest modules are not included in your current project. ( I was running Xtc )
When opening an old or new cubase file it says:
Sampelrate could not be set...
In cubase there is nothing I can do or to choose from in:
No clock source
No control panel
No sampel rate
All this ends when I delete the intblksize in cset.ini file...
My latency then in ass pointed in cubase:
24.694 ms...
Why all these troubles?
What am i doing wrong?
It seems easy just add intblksize - but then again check the problems?
I'm forgetting about the mixer but i did connect it the xtcproject.pro... And it seems to work but what do I now
Greetzzzzzzzzzzzzzzzz
The is a quick one 'cause I'm in New Zealand on pay interent.
Try using an intBlksize=256. If that works, try =128. It may be that your computer can't handle the load of 64. Be careful with the entry too...I beleive that cset.ini is case-sensitive (as code usually is) so make sure you got the capital letters in the right places....off the top if my head I think it's "intBlksize=x" .
When you get messages like "No SFP modules loaded..." and you don't have options any more, it just means options where you should, it just means that XTC ASIO didn't load properly and that Cubase has lost track of the Creamware cards. A lot of time this corrupts XTC and you have to restart the computer.
Get the sample rate to work, and you'll be fine.
That's all for now.
Cheers,
AudioDan
Try using an intBlksize=256. If that works, try =128. It may be that your computer can't handle the load of 64. Be careful with the entry too...I beleive that cset.ini is case-sensitive (as code usually is) so make sure you got the capital letters in the right places....off the top if my head I think it's "intBlksize=x" .
When you get messages like "No SFP modules loaded..." and you don't have options any more, it just means options where you should, it just means that XTC ASIO didn't load properly and that Cubase has lost track of the Creamware cards. A lot of time this corrupts XTC and you have to restart the computer.
Get the sample rate to work, and you'll be fine.
That's all for now.
Cheers,
AudioDan
I concur w/ AudioDan on intBlksize. I typically run with it set to 128, but 256 is a good place to start.
There was a link in my first reply to another thread which covered those settings, if you haven't already visited it. My cset.ini has 2 occurances of intBlkSize, like yours; under the [XTC-Config] and [hw] blocks. I believe the [hw] value is used for SFP mode (?) and for XTC operation you'll be interested in the [XTC-Config] value. Regardless, I think you'll want both in there. When in doubt, you can always move your cset.ini and let Scope create a new one from scratch. Then just update the necessary buffer and XTC mode values.
Regarding xtcproject.pro, I simply have ASIO (and GSIF) I/O modules in the project and the necessary interconnects to support the number of channels my system has and the audio routing is set for the places I need the channels to go to. No other mixers, etc. I am using ASIO1-32bit ASIO modules, but you may choose another that better suits your need.
I don't have the the Merge/DirectMixer modules incorporated and everything seems to work well for me. If it only works for you with the DirectMixer installed, then you should probably go that way!
<font size=-1>[ This Message was edited by: narly on 2005-07-12 10:13 ]</font>
There was a link in my first reply to another thread which covered those settings, if you haven't already visited it. My cset.ini has 2 occurances of intBlkSize, like yours; under the [XTC-Config] and [hw] blocks. I believe the [hw] value is used for SFP mode (?) and for XTC operation you'll be interested in the [XTC-Config] value. Regardless, I think you'll want both in there. When in doubt, you can always move your cset.ini and let Scope create a new one from scratch. Then just update the necessary buffer and XTC mode values.
Regarding xtcproject.pro, I simply have ASIO (and GSIF) I/O modules in the project and the necessary interconnects to support the number of channels my system has and the audio routing is set for the places I need the channels to go to. No other mixers, etc. I am using ASIO1-32bit ASIO modules, but you may choose another that better suits your need.
I don't have the the Merge/DirectMixer modules incorporated and everything seems to work well for me. If it only works for you with the DirectMixer installed, then you should probably go that way!
<font size=-1>[ This Message was edited by: narly on 2005-07-12 10:13 ]</font>
Hi,
First of all I want to thank Audiodan and narly for their help. Nice.
I didn't realized you had to put a number in.
Kieken would they say in dutch.
Now everything solved they computer is nicer to work with of course.
whereby x is a values out of 64, 128, 256, 512 or 1024 and translates as follows to the card's latency:
64: latency = 3 ms
128: latency = 4 ms
256: latency = 7 ms
512: latency = 13 ms
1024: latency = 25 ms
Was I blind?
Put in 256 and had a latency of 7 ms
Cool demax be sure to visit rakti dei
First of all I want to thank Audiodan and narly for their help. Nice.
I didn't realized you had to put a number in.
Kieken would they say in dutch.
Now everything solved they computer is nicer to work with of course.
whereby x is a values out of 64, 128, 256, 512 or 1024 and translates as follows to the card's latency:
64: latency = 3 ms
128: latency = 4 ms
256: latency = 7 ms
512: latency = 13 ms
1024: latency = 25 ms
Was I blind?
Put in 256 and had a latency of 7 ms
Cool demax be sure to visit rakti dei
Case closed. Hope it all works better for you tham it did for me.
I have since found out that Creamware do not recommend ANY dual CPU motherboards with their products so I've spent a lot of money on a computer that won't work properly with the even more expensive Creamware gear I've bought.
The SFP environment works OK as far as I've seen, but XTC doesn't.
I'm thinking at this point of using that computer as an external FX and synth unit with SFP, and getting myself a G5 and a couple of UAD-1 cards. At least Universal Audio specify on their site, model of G5 that work the best with their cards. It's only because I work in a music shop and have direct contact with the Australian distributor of Creamware that I was able to have this information squeezed out of Creamware.
Support at the moment is pretty ordinary. I can't even download my Allkeys file, nor can I log onto the FAQ's section on the site. If it's a global fault at Creamware's end then they're not leaping out of their skins to fix the problem 'cause it's been like that for a long time now.
Anyway, that's my rant.
Glad everything's working for you now Protone.
Thankyou to everyone else for your confirmations of things that I've been saying. It helps to reinforce all of this in my own head.
Cheers,
AudioDan
I have since found out that Creamware do not recommend ANY dual CPU motherboards with their products so I've spent a lot of money on a computer that won't work properly with the even more expensive Creamware gear I've bought.
The SFP environment works OK as far as I've seen, but XTC doesn't.I'm thinking at this point of using that computer as an external FX and synth unit with SFP, and getting myself a G5 and a couple of UAD-1 cards. At least Universal Audio specify on their site, model of G5 that work the best with their cards. It's only because I work in a music shop and have direct contact with the Australian distributor of Creamware that I was able to have this information squeezed out of Creamware.
Support at the moment is pretty ordinary. I can't even download my Allkeys file, nor can I log onto the FAQ's section on the site. If it's a global fault at Creamware's end then they're not leaping out of their skins to fix the problem 'cause it's been like that for a long time now.
Anyway, that's my rant.
Glad everything's working for you now Protone.
Thankyou to everyone else for your confirmations of things that I've been saying. It helps to reinforce all of this in my own head.
Cheers,
AudioDan
@Dan
In the past when I've noticed that server is down I think I sent an email to support at creamware.de and informed them of the error I was getting and they were able to do whatever they needed to get it up again. Kind of odd, but it seems like it goes down and they're not aware of it until someone notifies them. If you already have, then I guess that blows my theory out of the water
In the past when I've noticed that server is down I think I sent an email to support at creamware.de and informed them of the error I was getting and they were able to do whatever they needed to get it up again. Kind of odd, but it seems like it goes down and they're not aware of it until someone notifies them. If you already have, then I guess that blows my theory out of the water
Back...
Better then ever...
So midi problems. A new chapter awaits us.
In SFP no problem recording hardware.
In XTC problems recording hardware.
What about this:
CW midi in/out 1-8 emulated?
I have in out thru of Creamware and motu usb 1-5 midi in out.
The thing is I think when I put CR on the computer you could choose between something midi and I choose 1-8 blabla emulated.
Whats the diverence?
Recording hardware in cubase is midi channel audio channel both record and record...
Nothings there...
Am I missing something?
Yes I do know my head still on
Better then ever...
So midi problems. A new chapter awaits us.
In SFP no problem recording hardware.
In XTC problems recording hardware.
What about this:
CW midi in/out 1-8 emulated?
I have in out thru of Creamware and motu usb 1-5 midi in out.
The thing is I think when I put CR on the computer you could choose between something midi and I choose 1-8 blabla emulated.
Whats the diverence?
Recording hardware in cubase is midi channel audio channel both record and record...
Nothings there...
Am I missing something?
Yes I do know my head still on
I'm not sure I know what you mean, but here are some things in the area you're speaking of...
I believe it is recommended to use Windows midi ports, not emulated ports. Windows MIDI works better for me, anyway. Ports are only useful for SFP mode, right? No devices in XTCproject to control w/ midi. Studio MIDI in to Cubase via your MOTU unit and you should be set.
For SFP mode, I'd think that 8 Creamware ports are a lot to have running w/ 16 channels available each. I guess if you need that many channels...
I actually gave up on Creamware/Sequencer midi - lot's of drag on VST performance on my system resulting in audio noise. I may have been doing something wrong, but ultimately decided if running SFP mode to just push Midi out through my MidiSport 4x4 back into Pulsar's hardware MIDI connection.
Works better for me.
Shouldn't need Creamware MIDI in Cubase in XTC mode, yes?
<font size=-1>[ This Message was edited by: narly on 2005-07-14 12:49 ]</font>
I believe it is recommended to use Windows midi ports, not emulated ports. Windows MIDI works better for me, anyway. Ports are only useful for SFP mode, right? No devices in XTCproject to control w/ midi. Studio MIDI in to Cubase via your MOTU unit and you should be set.
For SFP mode, I'd think that 8 Creamware ports are a lot to have running w/ 16 channels available each. I guess if you need that many channels...
I actually gave up on Creamware/Sequencer midi - lot's of drag on VST performance on my system resulting in audio noise. I may have been doing something wrong, but ultimately decided if running SFP mode to just push Midi out through my MidiSport 4x4 back into Pulsar's hardware MIDI connection.
Works better for me.
Shouldn't need Creamware MIDI in Cubase in XTC mode, yes?
<font size=-1>[ This Message was edited by: narly on 2005-07-14 12:49 ]</font>