Hi,
I have scope4.0
I knew it was possible to use the plugins and synths of scope in cubase it all seems so logic just push the XTC button
Did i know that you have to let them work seperetly and not hmmmm
Cubase opens is for you when xtc is on
ok nice ...
I changed xtcproject.pro to my needs
It seems to open ok
Asio xtc mode no problem when opening cubase
At the end of loading cubase still having a error code -99 (1036) scope driverloctl
Hmmm ''happy'' to see Audiodan solved his problem maybe there others who can tell more about it
Still having some questions
Which filles like ddl have to be in the same one ass where cubase loads his plugins?
Are there other ones that should be there?
When i know want to do something (xtc mode) in my previous files in cubase i'm getting a message like
Samplerate could not be set
This may be due to the sampleclock being set to external sync
Does scope samplerate sync has to be master or slave in xtc mode?
I cant seems to phix the problem from whitin cubase sx
I cant change anything the place where ''normally'' you ste the sample rate in cubase is empty ( devices - etc... )
Maybe somebody knows something that i dont
Probably
I hope so or else itwould be a strange place after all
Pure xtc is better Pills no i'm not sure whats in
Since I just got through sorting through some XTC setup issues, I'll try to offer some assistance. Sounds like you're talking about several different things - but, maybe not 
BTW, I'm using Cubase SX 3, but most Cubase SX <i>should</i> be similar
First things first...ASIO drivers should load properly when you fire up Cubase. Without that, all else is moot.
I'd test by running your XTCproject.pro in SFP mode: with Scope open and your XTCproject.pro loaded, startup Cubase and see if it will then load the ASIO properly.(You can turn off the XTC checkbox in Scope Settings for the testing if you want, if on it only cause a warning). If you receive notification to test ASIO setup, go ahead and select yes (I seem to recall a situation where I couldn't get going until I let it run that test... It won't hurt anything)
If Cubase still doesn't load the Scope ASIO correctly, check which ASIO device is selected in Cubase device setup. If it's not already selected, manually select "ASIO Scope" and click "Switch" on the dialog. If ASIO Scope is not present in the device list, of course, there are other issues (reinstall SFP).
If it still will not load, double-check the Settings in your open project in Scope... is sync present (showing a valid samplerate in the indicator)? Is Scope acting as master or slave? NOTE: Unless you have an external device serving as your studio's master digital clock, you'll use Master for sync in your Scope Projects (an outboard A/D/D/A converter like an A16 can be used as a master clock). Samplerate is up to you 44.1k - 96k
Try a couple of options there in the open Scope project, restarting Cubase each time. I'd recommend trying "Master" and 44.1kHz at first, just to keep things simple.
NOTE: You can only change settings for Sync in XTC in the XTCProject.pro - these are not saved when changed in Cubase.
If you get it to work with Scope open (which is SFP mode), you should:
- Turn back on the XTC flag in settings
- Save as SFPAppXTCAppxtcproject.pro
- Close Cubase
- Close Scope
Then fire up Cubase and all should be well.
If you can't get it to run in SFP mode, I'd try reinstalling Scope4.0.
If still not loading XTC mode (but is loading SFP mode) post the first error/issue you observe in loading or using Cubase.
Hope this helps. I hope I've not over-done the detail, just basing on your post-count
Later, after you get it running, you'll probably want to adjust latency for your XTC setup: http://www.planetz.com/forums/viewtopic ... 1&forum=32
BTW, I'm using Cubase SX 3, but most Cubase SX <i>should</i> be similarFirst things first...ASIO drivers should load properly when you fire up Cubase. Without that, all else is moot.
I'd test by running your XTCproject.pro in SFP mode: with Scope open and your XTCproject.pro loaded, startup Cubase and see if it will then load the ASIO properly.(You can turn off the XTC checkbox in Scope Settings for the testing if you want, if on it only cause a warning). If you receive notification to test ASIO setup, go ahead and select yes (I seem to recall a situation where I couldn't get going until I let it run that test... It won't hurt anything)
If Cubase still doesn't load the Scope ASIO correctly, check which ASIO device is selected in Cubase device setup. If it's not already selected, manually select "ASIO Scope" and click "Switch" on the dialog. If ASIO Scope is not present in the device list, of course, there are other issues (reinstall SFP).
If it still will not load, double-check the Settings in your open project in Scope... is sync present (showing a valid samplerate in the indicator)? Is Scope acting as master or slave? NOTE: Unless you have an external device serving as your studio's master digital clock, you'll use Master for sync in your Scope Projects (an outboard A/D/D/A converter like an A16 can be used as a master clock). Samplerate is up to you 44.1k - 96k
Try a couple of options there in the open Scope project, restarting Cubase each time. I'd recommend trying "Master" and 44.1kHz at first, just to keep things simple.
NOTE: You can only change settings for Sync in XTC in the XTCProject.pro - these are not saved when changed in Cubase.
If you get it to work with Scope open (which is SFP mode), you should:
- Turn back on the XTC flag in settings
- Save as SFPAppXTCAppxtcproject.pro
- Close Cubase
- Close Scope
Then fire up Cubase and all should be well.
If you can't get it to run in SFP mode, I'd try reinstalling Scope4.0.
If still not loading XTC mode (but is loading SFP mode) post the first error/issue you observe in loading or using Cubase.
Hope this helps. I hope I've not over-done the detail, just basing on your post-count
Later, after you get it running, you'll probably want to adjust latency for your XTC setup: http://www.planetz.com/forums/viewtopic ... 1&forum=32
Hi,
Narly thankxxs for replying
My xtcproject.pro works well in sfp mode
But when i open it true cubase xtc i get these messages:
driverloctl (1036) error code -99
cant find riff dll.
and samplerate could not be set due to the sampleclock being set to external sync
My questions are:
What about these messages?
Which files have to be in the same folder ass the one where cubase opens his plugins?
Narly thankxxs for replying
My xtcproject.pro works well in sfp mode
But when i open it true cubase xtc i get these messages:
driverloctl (1036) error code -99
cant find riff dll.
and samplerate could not be set due to the sampleclock being set to external sync
My questions are:
What about these messages?
Which files have to be in the same folder ass the one where cubase opens his plugins?
On my system (XP Pro, SP 2) riff.dll is only located in the "Program FilesSFPAppBin" folder. I can sucessfully run XTC on my system in this configuration.
I read a post here that suggested riff.dll needed to be in "WindowsSystem32". You could make a copy of it there to see if that works.
My sync source happens to be external. If I happen to try to start Cubase/XTC with that clock source off, I will get errors, since it can't load Scope ASIO as previously defined, it will try to load ASIO MME and request the config test, etc. On re-opening Cubase the next time (clock source on) I have to manually reselect the ASIO Scope driver, but it loads okay... provided my clock source is set correctly! So maybe I don't have a direct answer for you.
Regarding other Scope related .dll file placement, I have "asioScop.DLL" also in "Program FilesSFPAppBin"
Plugin DLL's on my system for Scope XTC/VST use reside in the master VST plugin folder, in "Program FilesSteinbergCubase SX 3VSTPluginsXTC"
Post a copy of your cset.ini if you want. Maybe there's something there. This seems an odd error - several postings on the forums, but no direct resolutions that I've seen...
I read a post here that suggested riff.dll needed to be in "WindowsSystem32". You could make a copy of it there to see if that works.
My sync source happens to be external. If I happen to try to start Cubase/XTC with that clock source off, I will get errors, since it can't load Scope ASIO as previously defined, it will try to load ASIO MME and request the config test, etc. On re-opening Cubase the next time (clock source on) I have to manually reselect the ASIO Scope driver, but it loads okay... provided my clock source is set correctly! So maybe I don't have a direct answer for you.
Regarding other Scope related .dll file placement, I have "asioScop.DLL" also in "Program FilesSFPAppBin"
Plugin DLL's on my system for Scope XTC/VST use reside in the master VST plugin folder, in "Program FilesSteinbergCubase SX 3VSTPluginsXTC"
Post a copy of your cset.ini if you want. Maybe there's something there. This seems an odd error - several postings on the forums, but no direct resolutions that I've seen...
Hi,
I'm back. Lucky for you I have solved the problem, but you're not going to like the solution.
XTC mode doesn't like dual-processing systems. Creamware GmBh has grudgingly admitted this to a fine gentlemen at Major Music (the Australian Creamware Distributor)who has been trying to find a solution for me. I've tried everything else I can think of but still got the same results. "ScopedriverIOctl...error code -99" etc, etc, boring.
So....are you running one of the following:
*Dual Processor PC
OR
*Single Pentium 4 with Hyperthreading
Either one will give you that error message. I'm not sure that everyone has these problems, but obviously it's happening on some motherboards.
The solution?...XTC doesn't like dual processing, so don't allow it access to more than one CPU. Remember please that HYPERTHREADING IS CLASSED AS TWO CPU'S. Or at least Cubase SX sees it as such.
When you press Ctrl+Alt+Delete and open task manager, go to the "Processes" tab and right-click on one of the processes that is running with your profile name against it (not System, Network, or Local precoesses) You'll see an option in the right-click menu that says "Set Affinity". Click on that and you will be given a list of the available CPU's in the system from 0-31. (Ha! I can just imagaine a Windows-based computer running 32 CPU's....it has enough trouble with just one....). If you have a dual processor or Hyperthreading computer, you'll have two CPU's to select from. By un-ticking one or the other, Windows XP denys the process access to the un-ticked CPU so all processing for that program will go the the CPU that is selected.
Here's the catch!!!...to deny dual processor access to XTC you must also deny Cubase of dual processor access. In the case of Hyperthreading, simply disable the Hyperthreading option from the bios and both Cubase and XTC should work properly from then on.
For poor slobs like me that went and spent exorbitant sums on money on dual Xeon systems, this will involve changing the CPU Affinity of Cubase/Nuendo every time you use it.....not acceptable.
You will of course notice a marked rduction on the power and capabilities of the computer when using Cubase.
My helpful contact at Major Music is going to get back to me with possible Dual Xeon motherbaords that Creamware can recommend....if any.
Bare with me 'cause I only cracked this whole thing last night. I've treated the offending session very badly since then, doing all the things to it that would have been sure to induce the error code -99, but as yet, when only allowed access to one CPU XTC in Nuendo has performed as well as anybody could ask for.
More on this when I find out.
Sorry if this spoils your day....goodluck.
AudioDan
I'm back. Lucky for you I have solved the problem, but you're not going to like the solution.
XTC mode doesn't like dual-processing systems. Creamware GmBh has grudgingly admitted this to a fine gentlemen at Major Music (the Australian Creamware Distributor)who has been trying to find a solution for me. I've tried everything else I can think of but still got the same results. "ScopedriverIOctl...error code -99" etc, etc, boring.
So....are you running one of the following:
*Dual Processor PC
OR
*Single Pentium 4 with Hyperthreading
Either one will give you that error message. I'm not sure that everyone has these problems, but obviously it's happening on some motherboards.
The solution?...XTC doesn't like dual processing, so don't allow it access to more than one CPU. Remember please that HYPERTHREADING IS CLASSED AS TWO CPU'S. Or at least Cubase SX sees it as such.
When you press Ctrl+Alt+Delete and open task manager, go to the "Processes" tab and right-click on one of the processes that is running with your profile name against it (not System, Network, or Local precoesses) You'll see an option in the right-click menu that says "Set Affinity". Click on that and you will be given a list of the available CPU's in the system from 0-31. (Ha! I can just imagaine a Windows-based computer running 32 CPU's....it has enough trouble with just one....). If you have a dual processor or Hyperthreading computer, you'll have two CPU's to select from. By un-ticking one or the other, Windows XP denys the process access to the un-ticked CPU so all processing for that program will go the the CPU that is selected.
Here's the catch!!!...to deny dual processor access to XTC you must also deny Cubase of dual processor access. In the case of Hyperthreading, simply disable the Hyperthreading option from the bios and both Cubase and XTC should work properly from then on.
For poor slobs like me that went and spent exorbitant sums on money on dual Xeon systems, this will involve changing the CPU Affinity of Cubase/Nuendo every time you use it.....not acceptable.
You will of course notice a marked rduction on the power and capabilities of the computer when using Cubase.
My helpful contact at Major Music is going to get back to me with possible Dual Xeon motherbaords that Creamware can recommend....if any.
Bare with me 'cause I only cracked this whole thing last night. I've treated the offending session very badly since then, doing all the things to it that would have been sure to induce the error code -99, but as yet, when only allowed access to one CPU XTC in Nuendo has performed as well as anybody could ask for.
More on this when I find out.
Sorry if this spoils your day....goodluck.
AudioDan
@AudioDan - You may be on to something there. I run in HT, I think I was able to get better results this way, but I did have to set processor affinity for my apps (e.g. Cubase, SFP, GigaStudio) for it to work well.
However, you don't have to set processor affinity each time you start up - you can use "Imagecfg.exe" to set the processor affinity for each executable (SFP.exe, Cubase.exe, GStudio.exe, etc.). You should be able to find it for download via Google search. It includes command line info in a readme file. Also search PlanetZ, I believe this is where I first read about it.
I can't recall off the top of my head which processor affinity I've set for which application, but will be happy to look into it and post the info tomorrow - too late today to get into that...
However, you don't have to set processor affinity each time you start up - you can use "Imagecfg.exe" to set the processor affinity for each executable (SFP.exe, Cubase.exe, GStudio.exe, etc.). You should be able to find it for download via Google search. It includes command line info in a readme file. Also search PlanetZ, I believe this is where I first read about it.
I can't recall off the top of my head which processor affinity I've set for which application, but will be happy to look into it and post the info tomorrow - too late today to get into that...
Hi,
Uhu uhu
I have a p4t533 motherboard its not a dual proccessor.
Here is an idea
Special Features
Supports RIMM 4200/3200 (PC1066/800)
Supports ATA-133 IDE Hard Drive
ASUS EZ-PLUG
EZ Flash BIOS
POST Reporter
Q-Fan
Promise IDE RAID
NEC USB 2.0
Integrated Audio (C-Media 6-channel)
CPU
Socket 478 for Intel Pentium 4 Northwood/Willamette
Chipset
Intel i850E/ICH2
400/533MHz FSB
AGP 4x
Support for dual-channel RDRAM
Still got the message
Know i rebooted the thing and after many fitting and trying, i found out that pci slot 6 has its own irq adress Yeah...
What about this ?
Where do you change it?
- The driver setup (Windows Device Manager) includes the option 'Always open device'.
This option is important for the XTC mode.
It should be enabled with Cubase VST and disabled with Logic Audio.
Let you know how everything evolves
Thanks for replying
Uhu uhu
I have a p4t533 motherboard its not a dual proccessor.
Here is an idea
Special Features
Supports RIMM 4200/3200 (PC1066/800)
Supports ATA-133 IDE Hard Drive
ASUS EZ-PLUG
EZ Flash BIOS
POST Reporter
Q-Fan
Promise IDE RAID
NEC USB 2.0
Integrated Audio (C-Media 6-channel)
CPU
Socket 478 for Intel Pentium 4 Northwood/Willamette
Chipset
Intel i850E/ICH2
400/533MHz FSB
AGP 4x
Support for dual-channel RDRAM
Still got the message
Know i rebooted the thing and after many fitting and trying, i found out that pci slot 6 has its own irq adress Yeah...
What about this ?
Where do you change it?
- The driver setup (Windows Device Manager) includes the option 'Always open device'.
This option is important for the XTC mode.
It should be enabled with Cubase VST and disabled with Logic Audio.
Let you know how everything evolves
Thanks for replying
A few more questions for you. There are no really wrong answers, but the current settings might be helpful to know(?).
Do you have Hyperthreading enabled in BIOS?
What Windows OS are you running (98, 2000, XP)?
If 2000 or XP, is your system installed as Standard PC or ACPI PC? (Check in Computer in Device Manager). Specifically does device manager report: Uniprocessor ACPI PC, Multiprocessor ACPI PC, Standard PC, other?
How many and what types of Scope/Pulsar cards are you running?
Some suggestions (may or may not help your issue directly, but best practices advice):
In your system BIOS, disable USB 2.0 if possible, unless you have a specific reason to have it enabled.
In system BIOS, disable the C-Media audio device, unless you have...
In system BIOS, disable IRQ for USB.
In system BIOS, disable IRQ for VGA.
Regarding your PCI slot 6: Is this the slot your CWA card is in? The IRQ for the PCI slot shouldn't be a problem if it's assigning a unique IRQ. If you're system is set up as an ACPI machine (see above) the hardware IRQ isn't as important (sanity check someone?). If the IRQ can be set, it would be in your system BIOS setup. Typically, there are 2 PCI busses to the PCI slots, so you probably have 3 different hardware IRQ's available for cards in those slots. Best to have CWA card on it's own IRQ. I'm not familiar with that board, but you may be able to dig up info on it to indicate which slots share IRQ's with each other and avoid sharing IRQ's. As a trial-and-error method of establishing IRQ settings on a pre-configured mainboard, it's pretty easy to pause your system during the early stages of a boot when the system parameters are displayed to see what devices have which IRQ's set. If there are shared IRQ's on your multimedia card(s) you can power down, swap slots, and run the same check on startup. Again, BIOS assigned hardware IRQ's are important if you're running Windows as "Standard PC." Many people recommend "Standard PC" and not running HT for stability and best overall results. My setup uses HT enabled in BIOS and XP Pro setup as "Multiprocessor ACPI." I thought AudioDan's post might have raised a good point for consideration, but this seems difficult to nail down.
Not meaning to re-visit ground already covered - just running through all the things I'd be checking myself...
<font size=-1>[ This Message was edited by: narly on 2005-07-07 22:45 ]</font>
Do you have Hyperthreading enabled in BIOS?
What Windows OS are you running (98, 2000, XP)?
If 2000 or XP, is your system installed as Standard PC or ACPI PC? (Check in Computer in Device Manager). Specifically does device manager report: Uniprocessor ACPI PC, Multiprocessor ACPI PC, Standard PC, other?
How many and what types of Scope/Pulsar cards are you running?
Some suggestions (may or may not help your issue directly, but best practices advice):
In your system BIOS, disable USB 2.0 if possible, unless you have a specific reason to have it enabled.
In system BIOS, disable the C-Media audio device, unless you have...
In system BIOS, disable IRQ for USB.
In system BIOS, disable IRQ for VGA.
Regarding your PCI slot 6: Is this the slot your CWA card is in? The IRQ for the PCI slot shouldn't be a problem if it's assigning a unique IRQ. If you're system is set up as an ACPI machine (see above) the hardware IRQ isn't as important (sanity check someone?). If the IRQ can be set, it would be in your system BIOS setup. Typically, there are 2 PCI busses to the PCI slots, so you probably have 3 different hardware IRQ's available for cards in those slots. Best to have CWA card on it's own IRQ. I'm not familiar with that board, but you may be able to dig up info on it to indicate which slots share IRQ's with each other and avoid sharing IRQ's. As a trial-and-error method of establishing IRQ settings on a pre-configured mainboard, it's pretty easy to pause your system during the early stages of a boot when the system parameters are displayed to see what devices have which IRQ's set. If there are shared IRQ's on your multimedia card(s) you can power down, swap slots, and run the same check on startup. Again, BIOS assigned hardware IRQ's are important if you're running Windows as "Standard PC." Many people recommend "Standard PC" and not running HT for stability and best overall results. My setup uses HT enabled in BIOS and XP Pro setup as "Multiprocessor ACPI." I thought AudioDan's post might have raised a good point for consideration, but this seems difficult to nail down.
Not meaning to re-visit ground already covered - just running through all the things I'd be checking myself...
<font size=-1>[ This Message was edited by: narly on 2005-07-07 22:45 ]</font>
Hi,
C'ant seem to find anything about hyperthreading in my bios.
I'm running windows xp withscope platform 4(6dsp).
Uniprocessor ACPI PC
My scope has its own irq adress.
Bios.
I used to have '' the message -99 '' but after rebooting, installing xtc seems to work.
Still some questions dowww:
Everything seems to load perfectelly.
Update vst plugins in cubase no problem.
Why is that i still cant open a synth or effect from CW in Cubase?
Thats the idea right?
Why is that i have no sound?
Strange....
Don't seem to understand where to put the directmixercontainer module...
Between asio source and mixer?
Read the post about the matter but dont get...
I cant seem to put an asio source into a merger?
What with the outs of the mixercontainer?
Do i connect the to analogue dest?
Or are there other possibiltities?
C'ant seem to find anything about hyperthreading in my bios.
I'm running windows xp withscope platform 4(6dsp).
Uniprocessor ACPI PC
My scope has its own irq adress.
Bios.
I used to have '' the message -99 '' but after rebooting, installing xtc seems to work.
Still some questions dowww:
Everything seems to load perfectelly.
Update vst plugins in cubase no problem.
Why is that i still cant open a synth or effect from CW in Cubase?
Thats the idea right?
Why is that i have no sound?
Strange....
Don't seem to understand where to put the directmixercontainer module...
Between asio source and mixer?
Read the post about the matter but dont get...
I cant seem to put an asio source into a merger?
What with the outs of the mixercontainer?
Do i connect the to analogue dest?
Or are there other possibiltities?
Hi,
I just looked through the forum 'cause I had a hunch, and every instance that I can find of this error message, has been happening using ASUS brand motherboards (including my own). I don't know if this counts for anything, but it's certainly something to consider.
Protone, I believe that your CPU will pre-date Hyperthreading. On this point I'm stumped. I can't give you any solution other than what worked on my machine, and the fact that this problem seems to have occured only on ASUS motherboards thus far.
Do also try removing from the "cset.ini" file, any reference to host cards in XTC.
Off the top of my head I think the standard entry will look something like
[XTC-Config]
AddHost=1
[Host-Config]
Scoperev=128
That's what mine says when I install SFP4 but then I'm running two LunaII's and a 14DSP booster.
Take out the "Addhost=1" and anything under and including the "[Host-Config]" line.
I found that the system is a little more stable when it discovers this for itself as Cubase/Nuendo boots up. Again, this is on my own system. I think we're all finding XTC to be a bit inconsistent....
If you're looking for Hyperthreading options in the BIOS it can sometimes be called a "Logic Processor". In the BIOS of my motherboard the option is called "Hyperthreading", but when the BIOS goes through its boot process when the computer starts, it finds what it calls "Logic Processors". Just a thought...
Anyway, again, goodluck.
Maybe think of replacing you motherboard/CPU in a brand other than ASUS, but beware! I don't think XTC works with Athlon 64. I tried my Creamware cards on my spare machine (which has an Athlon64) and when Nuendo tried to boot ASIO SCOPE I got an error message saying "XTC did not install properly". Tried reinstalling and a few other things but I'm pretty sure it's the Athlon64 that's the problem.
Cheers,
AudioDan
I just looked through the forum 'cause I had a hunch, and every instance that I can find of this error message, has been happening using ASUS brand motherboards (including my own). I don't know if this counts for anything, but it's certainly something to consider.
Protone, I believe that your CPU will pre-date Hyperthreading. On this point I'm stumped. I can't give you any solution other than what worked on my machine, and the fact that this problem seems to have occured only on ASUS motherboards thus far.
Do also try removing from the "cset.ini" file, any reference to host cards in XTC.
Off the top of my head I think the standard entry will look something like
[XTC-Config]
AddHost=1
[Host-Config]
Scoperev=128
That's what mine says when I install SFP4 but then I'm running two LunaII's and a 14DSP booster.
Take out the "Addhost=1" and anything under and including the "[Host-Config]" line.
I found that the system is a little more stable when it discovers this for itself as Cubase/Nuendo boots up. Again, this is on my own system. I think we're all finding XTC to be a bit inconsistent....
If you're looking for Hyperthreading options in the BIOS it can sometimes be called a "Logic Processor". In the BIOS of my motherboard the option is called "Hyperthreading", but when the BIOS goes through its boot process when the computer starts, it finds what it calls "Logic Processors". Just a thought...
Anyway, again, goodluck.
Maybe think of replacing you motherboard/CPU in a brand other than ASUS, but beware! I don't think XTC works with Athlon 64. I tried my Creamware cards on my spare machine (which has an Athlon64) and when Nuendo tried to boot ASIO SCOPE I got an error message saying "XTC did not install properly". Tried reinstalling and a few other things but I'm pretty sure it's the Athlon64 that's the problem.
Cheers,
AudioDan
Cubase is running with ASIO Scope as the audio driver?On 2005-07-08 00:01, Protone wrote:
...installing xtc seems to work.
Where are your XTC dll's installed to? Do the Creamware plugin's show in Cubase's Plugin-Information window?On 2005-07-08 00:01, Protone wrote:
Why is that i still cant open a synth or effect from CW in Cubase?
Thats the idea right?
Is ASIO Scope loaded in in Cubase Devices? Does your output bus direct audio to the VST output channels that your XTC project uses for audio output?On 2005-07-08 00:01, Protone wrote:
Why is that i have no sound?
Don't worry about that yet. You should be able to have audio and VSTs without that.On 2005-07-08 00:01, Protone wrote:
Don't seem to understand where to put the directmixercontainer module...
You lost me... You should focus on the Audio/VST working first.On 2005-07-08 00:01, Protone wrote:
I cant seem to put an asio source into a merger?
What with the outs of the mixercontainer?
Do i connect the to analogue dest?
Or are there other possibiltities?
Hi,
I'm very glad there are some ears who are listening. Thank you for that.
Cubase is running with ASIO Scope as the audio driver? Yes
Where are your XTC dll's installed to? Do the Creamware plugin's show in Cubase's Plugin-Information window?
The ddl's are installed in the same folder where Cubase opens his vst.
I can update the plugin information window.
Xtc loads some stuff...
The CW plugins are showed.
I see them but when i double click on it ( in cubase ) it opens half...
It's like they are not there... Spookey
But when i load effects in my xtc project then i can open them in Cubase... in xtc
Is it so that: To open effects or synths from CW in Cubase (XTC mode) they have to be there in your routing window of you xtcproject????
Is ASIO Scope loaded in in Cubase Devices? Does your output bus direct audio to the VST output channels that your XTC project uses for audio output?
Don't understand the question...
Damn...
The thing i do is: routing window xtc pro..
i use stm 1632 for mixer
an asio 2 16bit source and an asio2 dest 64
those are connected to each other...with the mixer....
My analog source and dest to
And then midi of course...
Midi a source in mixer to merger into the merger also sequencer midi source
From merger to sequencer dest
From sequencer source Midi a dest....
Hope you still follow pfeeuw
In Sfp this ''setup'' if i explained it wright works good...
Don't seem to understand where to put the directmixercontainer module...
Don't worry about that yet. You should be able to have audio and VSTs without that.
So what it for then???
Many thankss to narly and audiodan
I'm very glad there are some ears who are listening. Thank you for that.
Cubase is running with ASIO Scope as the audio driver? Yes
Where are your XTC dll's installed to? Do the Creamware plugin's show in Cubase's Plugin-Information window?
The ddl's are installed in the same folder where Cubase opens his vst.
I can update the plugin information window.
Xtc loads some stuff...
The CW plugins are showed.
I see them but when i double click on it ( in cubase ) it opens half...
It's like they are not there... Spookey
But when i load effects in my xtc project then i can open them in Cubase... in xtc
Is it so that: To open effects or synths from CW in Cubase (XTC mode) they have to be there in your routing window of you xtcproject????
Is ASIO Scope loaded in in Cubase Devices? Does your output bus direct audio to the VST output channels that your XTC project uses for audio output?
Don't understand the question...
Damn...
The thing i do is: routing window xtc pro..
i use stm 1632 for mixer
an asio 2 16bit source and an asio2 dest 64
those are connected to each other...with the mixer....
My analog source and dest to
And then midi of course...
Midi a source in mixer to merger into the merger also sequencer midi source
From merger to sequencer dest
From sequencer source Midi a dest....
Hope you still follow pfeeuw
In Sfp this ''setup'' if i explained it wright works good...
Don't seem to understand where to put the directmixercontainer module...
Don't worry about that yet. You should be able to have audio and VSTs without that.
So what it for then???
Many thankss to narly and audiodan
Hi Protone,
Sorry I haven't been addressing the other issues you've been having. You kinda touched on something that's been vexing me over the past four or so months.
OK I don't know if you understand this yet, but I'll explain anyway. Scope Fusion Platform is an environment that runs the majority of its processing power off the DSP cards (Scope Home, Project and Studio) that you have installed in you computer. As you have found it gives you remarkable flexibility, routing audio and MIDI from physical external sources - eg. analaog inputs - into a multitude of mixers, FX, software driver source and destination modules such as ASIO and GSIF, as well as running synths and various other goodies. The SFP environment is a remarkable feat of computer ingenuity and a credit to the Creamware company. However - again, cheers to Creamware - for those of us who want to limit ourselves to one environment that is more suited to editing of both MIDI and audio (susch as Cubase) Creamware created a different mode for their cards to run in so that our type of user could still utilise Creamware FX and synths in our own way. XTC.
XTC and SFP are two entirely independent modes for the DSP cards. To be running plugins in XTC you MUST have the SFP environment shut down. Only when SFP is turned off does your ASIO host program (Cubase) have access to XTC. In this mode, Cubase uses the Creamware plugins like normal VST plugins, but having initialized the plugin the first time you ran XTC, Cubase knows that the plugin is processed at the DSP card and not at the computer's CPU.
So, because Cubase is sensitive to any licenced plugin that it has initialized at least once, it will show the contents of you XTC plugin folder even when XTC is not operating. The plugins however, will not run when you try to activate them. They will open as the default FX window in Cubase with nothing in it. That's why you were seeing a "half opened" plugin.
When you are not running XTC you must open all FX, Synths and Mixers (not to mention your ASIO driver modules) within the SFP evironment and rout Audio and MIDI in and out of the environment via the ASIO sources and destinations.
For those of us who have Cubase/Nuendo version 3, the option of "External FX" is available, and from there you can set up, up to 62 channels to route in and out of Cubase/Nuendo to FX and mixers. To achieve this number of I/O you must of course load and ASIO64 module. Two ins and outs will be used as stereo record and playback I/O for Cubase so that you can here what you're mixing, the other 62 channels are free to use as you wish. I'm not sure of the implications of CPU load doing things this way. I think the load on the computer will be much higher as two independent audio environments are running on the computer, and a large portion of RAM and CPU is being used by video tasks to keep each one looking piddy.
This is where XTC comes in. It's a much more efficient way of running the Creamware FX and synths if you don't need the flexibility of the SFP environment in your workflow. Only one Audio environment with one set of video tasks for the CPU and a whole heap of load not lumped on the CPU because XTC FX are procesed on the DSP cards.
Although there are a number of other companies - TC and Universal Audio to mention a couple - making big bucks out of the 'DSP for host VST enviroments' industry, Creamware apparently considers this function (XTC mode) of their cards to be a 'dead concept'. They won't be putting any more effort into making it more stable (as far as we've all heard so far) so it's really up to us as Creamware customers to try to wrangle out of their support - not an easy thing at all....I can't log into the FAQ's section or even download my "Allkeys.skf" at the moment - specs of a system that might be stable with their products.
Having spent a considerable sum of money on my Dual Xeon system, I'm now regretting having not done my homework, and thinking it might be better to get a G5 and a few Universal Audio UA-1 cards and maybe even switch over to Logic Pro.....I'm a bit disheartened at the moment.
Anyway, I hope you have more luck than me.
Cheers,
AudioDan
<font size=-1>[ This Message was edited by: AudioDan on 2005-07-08 18:10 ]</font>
Sorry I haven't been addressing the other issues you've been having. You kinda touched on something that's been vexing me over the past four or so months.
OK I don't know if you understand this yet, but I'll explain anyway. Scope Fusion Platform is an environment that runs the majority of its processing power off the DSP cards (Scope Home, Project and Studio) that you have installed in you computer. As you have found it gives you remarkable flexibility, routing audio and MIDI from physical external sources - eg. analaog inputs - into a multitude of mixers, FX, software driver source and destination modules such as ASIO and GSIF, as well as running synths and various other goodies. The SFP environment is a remarkable feat of computer ingenuity and a credit to the Creamware company. However - again, cheers to Creamware - for those of us who want to limit ourselves to one environment that is more suited to editing of both MIDI and audio (susch as Cubase) Creamware created a different mode for their cards to run in so that our type of user could still utilise Creamware FX and synths in our own way. XTC.
XTC and SFP are two entirely independent modes for the DSP cards. To be running plugins in XTC you MUST have the SFP environment shut down. Only when SFP is turned off does your ASIO host program (Cubase) have access to XTC. In this mode, Cubase uses the Creamware plugins like normal VST plugins, but having initialized the plugin the first time you ran XTC, Cubase knows that the plugin is processed at the DSP card and not at the computer's CPU.
So, because Cubase is sensitive to any licenced plugin that it has initialized at least once, it will show the contents of you XTC plugin folder even when XTC is not operating. The plugins however, will not run when you try to activate them. They will open as the default FX window in Cubase with nothing in it. That's why you were seeing a "half opened" plugin.
When you are not running XTC you must open all FX, Synths and Mixers (not to mention your ASIO driver modules) within the SFP evironment and rout Audio and MIDI in and out of the environment via the ASIO sources and destinations.
For those of us who have Cubase/Nuendo version 3, the option of "External FX" is available, and from there you can set up, up to 62 channels to route in and out of Cubase/Nuendo to FX and mixers. To achieve this number of I/O you must of course load and ASIO64 module. Two ins and outs will be used as stereo record and playback I/O for Cubase so that you can here what you're mixing, the other 62 channels are free to use as you wish. I'm not sure of the implications of CPU load doing things this way. I think the load on the computer will be much higher as two independent audio environments are running on the computer, and a large portion of RAM and CPU is being used by video tasks to keep each one looking piddy.
This is where XTC comes in. It's a much more efficient way of running the Creamware FX and synths if you don't need the flexibility of the SFP environment in your workflow. Only one Audio environment with one set of video tasks for the CPU and a whole heap of load not lumped on the CPU because XTC FX are procesed on the DSP cards.
Although there are a number of other companies - TC and Universal Audio to mention a couple - making big bucks out of the 'DSP for host VST enviroments' industry, Creamware apparently considers this function (XTC mode) of their cards to be a 'dead concept'. They won't be putting any more effort into making it more stable (as far as we've all heard so far) so it's really up to us as Creamware customers to try to wrangle out of their support - not an easy thing at all....I can't log into the FAQ's section or even download my "Allkeys.skf" at the moment - specs of a system that might be stable with their products.
Having spent a considerable sum of money on my Dual Xeon system, I'm now regretting having not done my homework, and thinking it might be better to get a G5 and a few Universal Audio UA-1 cards and maybe even switch over to Logic Pro.....I'm a bit disheartened at the moment.
Anyway, I hope you have more luck than me.
Cheers,
AudioDan
<font size=-1>[ This Message was edited by: AudioDan on 2005-07-08 18:10 ]</font>
With ASIO driver loading in Cubase XTC Mode and proper I/O mapping (ASIO>Cubase busses)you should be able to run audio, Steinberg VSTi's successfully. If there is no audio going in or coming out there is a problem with I/O Mapping or the ASIO driver. Out of curiosity, what input/output latency is Cubase reporting with the ASIO Scope audio driver loaded?
You shouldn't be loading effect devices in xtcproject.pro to make them available in Cubase XTC mode.
If the XTC synths/effects are available for selection in Cubase but choosing one loads only a very small window with nothing in it you will need to verify the paths in Scopevst.cfg in your SFPAppBin folder actually point to the location of the Scope .dev files (Cubase is finding the .dll wrappers for the Scope devices, but not the device files because it can't find them).
<font size=-1>[ This Message was edited by: narly on 2005-07-08 19:41 ]</font>
You shouldn't be loading effect devices in xtcproject.pro to make them available in Cubase XTC mode.
If the XTC synths/effects are available for selection in Cubase but choosing one loads only a very small window with nothing in it you will need to verify the paths in Scopevst.cfg in your SFPAppBin folder actually point to the location of the Scope .dev files (Cubase is finding the .dll wrappers for the Scope devices, but not the device files because it can't find them).
<font size=-1>[ This Message was edited by: narly on 2005-07-08 19:41 ]</font>
Hi again,
Something I sould have mentioned...
Protone, you really shouldn't need to edit you XTCproject.pro at all especially if you're really only starting to work through these different modes.
The Merge module was made redundant when Cubase SX 2 came out with Real-Time Audio Mixdown. This option eliminated the problems of Cubase trying to mixdown faster than real-time through the DSP FX which made any sound with an XTC effect on it sound like it had been slowed down to almost nothing, slurred and distorted.
The merge module was Creamware's solution for doing a real-time mixdown, by giving Cubase a way to record its own playback signal into itself.
Thus far I have not needed to have the DirectPlayMixer connected either. This is Creamware's ASIO direct monitoring option. I usually find that without any XTC FX running, the latency from ASIO Scope is low enough to monitor through Cubase/Nuendo anyway, but if you have a mixer as the front end to your computer, you can use that for monitoring of live sources, and hopefully listen back to the outputs of Cubase through it all at once.
I only discovered recently the fact that the XTC project can be edited, so you can see that I've never really needed to change it. You can change the available ins and outs from Cubase anyway and the XTCProject.pro is changed for you. In VST Audiobay under the SCOPE heading click the Control Panel button and you'll have the option to enable any or all of the available ins and outs.
NOTE: XTC doesn't remember the Latency that you set in the previous session. To have XTC load up with a set low latency every time you need to add an entry to your 'cset.ini' file. This is part of GonZoft's amazing guide to XTC setup modestly called "Some hints as to XTC mode".
7. XTC mode does not remember your ULLI settings unless you do the following:
Add the following entry into your /SFP/App/Bin/Cset.ini under item
[XTC-config]:
intBlkSize=x
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
A wrong latency will still be displayed in the ULLI Settings of the ASIO Control Panel, but you can ignore this.
It is a good idea to refresh the plugin info display after changing ULLI settings.
Thankyou GonZoft.....
This is about as high-powered in setup as you'll need to get at this stage.
Hope this helps you out.
Cheers again,
AudioDan
Something I sould have mentioned...
Protone, you really shouldn't need to edit you XTCproject.pro at all especially if you're really only starting to work through these different modes.
The Merge module was made redundant when Cubase SX 2 came out with Real-Time Audio Mixdown. This option eliminated the problems of Cubase trying to mixdown faster than real-time through the DSP FX which made any sound with an XTC effect on it sound like it had been slowed down to almost nothing, slurred and distorted.
The merge module was Creamware's solution for doing a real-time mixdown, by giving Cubase a way to record its own playback signal into itself.
Thus far I have not needed to have the DirectPlayMixer connected either. This is Creamware's ASIO direct monitoring option. I usually find that without any XTC FX running, the latency from ASIO Scope is low enough to monitor through Cubase/Nuendo anyway, but if you have a mixer as the front end to your computer, you can use that for monitoring of live sources, and hopefully listen back to the outputs of Cubase through it all at once.
I only discovered recently the fact that the XTC project can be edited, so you can see that I've never really needed to change it. You can change the available ins and outs from Cubase anyway and the XTCProject.pro is changed for you. In VST Audiobay under the SCOPE heading click the Control Panel button and you'll have the option to enable any or all of the available ins and outs.
NOTE: XTC doesn't remember the Latency that you set in the previous session. To have XTC load up with a set low latency every time you need to add an entry to your 'cset.ini' file. This is part of GonZoft's amazing guide to XTC setup modestly called "Some hints as to XTC mode".
7. XTC mode does not remember your ULLI settings unless you do the following:
Add the following entry into your /SFP/App/Bin/Cset.ini under item
[XTC-config]:
intBlkSize=x
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
A wrong latency will still be displayed in the ULLI Settings of the ASIO Control Panel, but you can ignore this.
It is a good idea to refresh the plugin info display after changing ULLI settings.
Thankyou GonZoft.....
This is about as high-powered in setup as you'll need to get at this stage.
Hope this helps you out.
Cheers again,
AudioDan
Im new to this but I think wat you sould do is, put back the original XTC.pro file
then go through the synths in :-
c:creamwaredevicessynths
and copy one of them to a new folder on your desktop ie. [BlueSynth.dev]
ant the end of each one before the .dev add in the letters XTC ie:-
BlueSynth.dev becomes BlueSynthXTC.dev
when you have done one of them put it back into the folder:-
creamwareDevicesSynths
then goto:-
creamwareAppBin
and get the file VstSynth.dll
copy this to your desktop and rename it the same as the 'XTC enabled' synth but instead of .dev its now a .dll :-
BlueSynthXTC.dll
put this file into your VST folder in cubase its found at:-
SteinbergCubase SX3VstpluginsXTC
pop it in there
Make sure that scope is off and launch cubase
then load up the BlueSynth as a VST in the normal way
et Viola
then ya gotta repeat ot for all the synths ya want to use in XTC
hope Im right, and it helps
cheers
-Me$$iah
then go through the synths in :-
c:creamwaredevicessynths
and copy one of them to a new folder on your desktop ie. [BlueSynth.dev]
ant the end of each one before the .dev add in the letters XTC ie:-
BlueSynth.dev becomes BlueSynthXTC.dev
when you have done one of them put it back into the folder:-
creamwareDevicesSynths
then goto:-
creamwareAppBin
and get the file VstSynth.dll
copy this to your desktop and rename it the same as the 'XTC enabled' synth but instead of .dev its now a .dll :-
BlueSynthXTC.dll
put this file into your VST folder in cubase its found at:-
SteinbergCubase SX3VstpluginsXTC
pop it in there
Make sure that scope is off and launch cubase
then load up the BlueSynth as a VST in the normal way
et Viola
then ya gotta repeat ot for all the synths ya want to use in XTC
hope Im right, and it helps
cheers
-Me$$iah
Hi,
The last postsss where very helpfull indeed.
Who said learnig can't be fun.
Since my first post a lot of happend for the better. I run xtc mode now apperently. Yeah...
The thing i did was rebooting the computer.
Searching for that PCI slot that has his own irq. Everything out your PCI slots and i started with only the creamware card in.
From one to six.
I reinstalled creamware and cubase sx, etc...
So i thougth to change the xtc project file to my needs but that wasn't a good idea so i but the original back and all seems to work.
I didn't have to copy and dragg the things messiah said. Tried one like messiah opend cubase and could open all my synth...
Narly:
If the XTC synths/effects are available for selection in Cubase but choosing one loads only a very small window with nothing in it you will need to verify the paths in Scopevst.cfg in your SFPAppBin folder actually point to the location of the Scope .dev files (Cubase is finding the .dll wrappers for the Scope devices, but not the device files because it can't find them).
So now i can open my synths like plugins in cubase. Thats cool i...
I found the Scopevst.cfg file but can't seem to open it. It's like you said but now i only have ''the half open'' problem with the effects...
How do you change and verify the path i can't open the cfg file you've mentioned?
Does this have anything to do with it
[SCOPE]
Application=D:/Program Files/Creamware/App/XTCApp/XTC.pro
Bin=D:/Program Files/Creamware/App/Bin
Config=XTC-Config
It's a file like cset but calls himself xtc.
It's located together with the dll from the synths and effect in the folder where xtc mode loads it.
Fieuw...
Audiodan:
Add the following entry into your /SFP/App/Bin/Cset.ini under item
[XTC-config]:
intBlkSize=x
I did that i got a lot off messages like sampelrate blablabla and some new ones...
Thats whats there now:
[XTC-Config]
DirectPlayOutPad2=RIn
DirectPlayOutPad1=LIn
DirectPlayOut=Pulsar2 Analog Dest
AddHost=1
[hw]
intBlkSize=64
I hope this hasn't be posted before euhm...
But does hw has to go?
What about xtc config is it ''ok'' ?
If i ignore the sample rate message i don't have sound...
If nobody knows what to do this summer there a good festival in Belgium
Go and take a look
http://www.rhaktidei.be
Have Fun
The last postsss where very helpfull indeed.
Who said learnig can't be fun.
Since my first post a lot of happend for the better. I run xtc mode now apperently. Yeah...
The thing i did was rebooting the computer.
Searching for that PCI slot that has his own irq. Everything out your PCI slots and i started with only the creamware card in.
From one to six.
I reinstalled creamware and cubase sx, etc...
So i thougth to change the xtc project file to my needs but that wasn't a good idea so i but the original back and all seems to work.
I didn't have to copy and dragg the things messiah said. Tried one like messiah opend cubase and could open all my synth...
Narly:
If the XTC synths/effects are available for selection in Cubase but choosing one loads only a very small window with nothing in it you will need to verify the paths in Scopevst.cfg in your SFPAppBin folder actually point to the location of the Scope .dev files (Cubase is finding the .dll wrappers for the Scope devices, but not the device files because it can't find them).
So now i can open my synths like plugins in cubase. Thats cool i...
I found the Scopevst.cfg file but can't seem to open it. It's like you said but now i only have ''the half open'' problem with the effects...
How do you change and verify the path i can't open the cfg file you've mentioned?
Does this have anything to do with it
[SCOPE]
Application=D:/Program Files/Creamware/App/XTCApp/XTC.pro
Bin=D:/Program Files/Creamware/App/Bin
Config=XTC-Config
It's a file like cset but calls himself xtc.
It's located together with the dll from the synths and effect in the folder where xtc mode loads it.
Fieuw...
Audiodan:
Add the following entry into your /SFP/App/Bin/Cset.ini under item
[XTC-config]:
intBlkSize=x
I did that i got a lot off messages like sampelrate blablabla and some new ones...
Thats whats there now:
[XTC-Config]
DirectPlayOutPad2=RIn
DirectPlayOutPad1=LIn
DirectPlayOut=Pulsar2 Analog Dest
AddHost=1
[hw]
intBlkSize=64
I hope this hasn't be posted before euhm...
But does hw has to go?
What about xtc config is it ''ok'' ?
If i ignore the sample rate message i don't have sound...
If nobody knows what to do this summer there a good festival in Belgium
Go and take a look
http://www.rhaktidei.be
Have Fun
Narly:
If the XTC synths/effects are available for selection in Cubase but choosing one loads only a very small window with nothing in it you will need to verify the paths in Scopevst.cfg in your SFPAppBin folder actually point to the location of the Scope .dev files (Cubase is finding the .dll wrappers for the Scope devices, but not the device files because it can't find them).
So now i can open my synths like plugins in cubase. Thats cool.
I found the Scopevst.cfg file but can't seem to open it. It's like you said but now i only have ''the half open'' problem with the effects...
But not all of them.
I can open most of the effects with the letter S behind. Not all the S's maybe 4 not
but no M's...
So this said to addition to my preyious post.
Whats the difference between M/S?
Why cant't I open the M's?
How do you change and verify the path i can't open the cfg file you've mentioned?
Wich program to use?
If the XTC synths/effects are available for selection in Cubase but choosing one loads only a very small window with nothing in it you will need to verify the paths in Scopevst.cfg in your SFPAppBin folder actually point to the location of the Scope .dev files (Cubase is finding the .dll wrappers for the Scope devices, but not the device files because it can't find them).
So now i can open my synths like plugins in cubase. Thats cool.
I found the Scopevst.cfg file but can't seem to open it. It's like you said but now i only have ''the half open'' problem with the effects...
But not all of them.
I can open most of the effects with the letter S behind. Not all the S's maybe 4 not
but no M's...
So this said to addition to my preyious post.
Whats the difference between M/S?
Why cant't I open the M's?
How do you change and verify the path i can't open the cfg file you've mentioned?
Wich program to use?