I can't have XTC working at all...
Hello,
I've spent all the day trying to have XTC working, with no success.
I never managed to have Cubase SX 2 starting in XTC mode. And I checked the "Enable XTC mode" option. I get a message box saying that the Scope platform isn't running when I launch SX.
So far I tried:
- Reinstalling Scope V4
- Reinstalling Scope V3.1a
- reinstalling scope driver
- installing plugins to different directories
- editing the XTCProject.pro
- editing other configuration files
... all this probably about 10 times already...
My setup is:
P4 3.2 HT
1.5 Gb RAM
Windows XP Pro SP2
Cubase SX 2
Next step would be to format my hard drive and make a fresh install of windows... but I'm fed up... I already had to do this two weeks ago because my computer crashed all the time when using my Powerpulsar... I don't know what to think of creamware anymore...
The concept is great but so far I've only run into trouble with this card.
So far I've used SFP mode. It's nice but I think XTC mode fits more the way I work. I don't use much the SFP, only to adjust some levels and panning sometimes... XTC mode would probably be easier for me, I end up not using any synths or effects because routing becomes uselessly difficult to do in SFP mode while it would be simple using XTC... anyway...
I'd be grateful if someone has some idea on how to solve this problem...
Many thanks
Breakthru
I've spent all the day trying to have XTC working, with no success.
I never managed to have Cubase SX 2 starting in XTC mode. And I checked the "Enable XTC mode" option. I get a message box saying that the Scope platform isn't running when I launch SX.
So far I tried:
- Reinstalling Scope V4
- Reinstalling Scope V3.1a
- reinstalling scope driver
- installing plugins to different directories
- editing the XTCProject.pro
- editing other configuration files
... all this probably about 10 times already...
My setup is:
P4 3.2 HT
1.5 Gb RAM
Windows XP Pro SP2
Cubase SX 2
Next step would be to format my hard drive and make a fresh install of windows... but I'm fed up... I already had to do this two weeks ago because my computer crashed all the time when using my Powerpulsar... I don't know what to think of creamware anymore...
The concept is great but so far I've only run into trouble with this card.
So far I've used SFP mode. It's nice but I think XTC mode fits more the way I work. I don't use much the SFP, only to adjust some levels and panning sometimes... XTC mode would probably be easier for me, I end up not using any synths or effects because routing becomes uselessly difficult to do in SFP mode while it would be simple using XTC... anyway...
I'd be grateful if someone has some idea on how to solve this problem...
Many thanks
Breakthru
- next to nothing
- Posts: 2521
- Joined: Mon Jul 29, 2002 4:00 pm
- Location: Bergen, Norway
I'd be grateful if someone has some idea on how to solve this problem...
ive only tried xtc mode a couple of times, and what made it work for me was these simple things:
-make sure xtc devs and the .dll's are in the right place
- tick the enable xtc-mode box
- turn off SFP
- launch Cubase
- activate the plugs (see tip and trick forum, cant remember off my head where u click etc, but i know there is a recent post about that and sx3 (applies to sx2 as well) )
I wouldnt be shocked if a message says that SFP aint running. because it shouldnt be. cant remember if i got that warning.
Best regards
Piddi
(edit: some nonsense i wrote before i read the post thourogly)
<font size=-1>[ This Message was edited by: piddi on 2005-02-20 19:09 ]</font>
Thanks for the answers!
>make sure xtc devs and the .dll's are in the right place
hum, I have all dll in the Vstplugins folder but I'm not sure where devs should be. I've tried copying them to the vstplugins folder as well but I won't work better.
Everythings else is ok, SFP is not running and enable XTC mode is ticked.
Plugins are not recognized inside Cubase (they appear in the list like they are not really plugins but any other kind of dll)
Well, SFP works well with Cubase (except a nasty freeze problem I had, but solved it by installing original drivers (3.1a) that came on the install CD), I'm only having problems with XTC.
I don't have any other ASIO soundcard in my system, but trying using one of the ASIO drivers installed by Cubase shows me the same error message...
>I wouldnt be shocked if a message says that SFP aint running. because it shouldnt be. cant remember if i got that warning.
I agree, the message is quite logical. The problem is that I don't have any Asio driver at all when SFP is closed (it is in the list, but the same error message appears again if I try to select it). Trying to open the control panel won't open the configuration window that is in the user's guide.
I'm probably doing something wrong, but can't figure out what... I'll try to investigate a bit more... and maybe forget about and use SFP instead... too bad.
Thanks for your answers it helps me searching other solutions!
Regards,
Breakthru
<font size=-1>[ This Message was edited by: Breakthru on 2005-02-21 17:21 ]</font>
<font size=-1>[ This Message was edited by: Breakthru on 2005-02-21 17:23 ]</font>
>make sure xtc devs and the .dll's are in the right place
hum, I have all dll in the Vstplugins folder but I'm not sure where devs should be. I've tried copying them to the vstplugins folder as well but I won't work better.
Everythings else is ok, SFP is not running and enable XTC mode is ticked.
Plugins are not recognized inside Cubase (they appear in the list like they are not really plugins but any other kind of dll)
Well, SFP works well with Cubase (except a nasty freeze problem I had, but solved it by installing original drivers (3.1a) that came on the install CD), I'm only having problems with XTC.
I don't have any other ASIO soundcard in my system, but trying using one of the ASIO drivers installed by Cubase shows me the same error message...
>I wouldnt be shocked if a message says that SFP aint running. because it shouldnt be. cant remember if i got that warning.
I agree, the message is quite logical. The problem is that I don't have any Asio driver at all when SFP is closed (it is in the list, but the same error message appears again if I try to select it). Trying to open the control panel won't open the configuration window that is in the user's guide.
I'm probably doing something wrong, but can't figure out what... I'll try to investigate a bit more... and maybe forget about and use SFP instead... too bad.
Thanks for your answers it helps me searching other solutions!
Regards,
Breakthru
<font size=-1>[ This Message was edited by: Breakthru on 2005-02-21 17:21 ]</font>
<font size=-1>[ This Message was edited by: Breakthru on 2005-02-21 17:23 ]</font>
- next to nothing
- Posts: 2521
- Joined: Mon Jul 29, 2002 4:00 pm
- Location: Bergen, Norway
Many thanks for your posts!
Unfortunately, using the .pro file suggested did not change anything, and the trick with SX plugins did not work (it ticked all the plugins, but when I reload Cubase, they are unticked again
)
Many thanks for spending time helping me... but I guess I'll stick to SFP for now, and investigate later to have XTC working.
Best regards,
Breakthru
Unfortunately, using the .pro file suggested did not change anything, and the trick with SX plugins did not work (it ticked all the plugins, but when I reload Cubase, they are unticked again

Many thanks for spending time helping me... but I guess I'll stick to SFP for now, and investigate later to have XTC working.
Best regards,
Breakthru
I'm glad you didn't format your harddrive!
Have fun with SFP again
Have fun with SFP again

more has been done with less
https://soundcloud.com/at0m-studio
https://soundcloud.com/at0m-studio
I had the same problems where nothing really worked, believe me I know what you've gone through...
But I've solved my problems! I uninstalled the complete Scope software and hardware. Then reboted my computer without any soundcard in it to see if the uninstall completely uninstalled. Afterwards I shutdown again, put the Pulsar card in another PCI-slot (important!) and installed the driver and software. It worked!
Please check if your computer has any IRQ-doubles, this can make XP very unstable.
Good luck...
But I've solved my problems! I uninstalled the complete Scope software and hardware. Then reboted my computer without any soundcard in it to see if the uninstall completely uninstalled. Afterwards I shutdown again, put the Pulsar card in another PCI-slot (important!) and installed the driver and software. It worked!
Please check if your computer has any IRQ-doubles, this can make XP very unstable.
Good luck...
-
- Posts: 17
- Joined: Fri Oct 08, 2004 4:00 pm
- Location: Rio de Janeiro - Brazil
I have also got the same problem, even tried the above fix of uninstalling everything and moving the card to a new slot. I did have this working many moons ago on a different computer, adifferent version of scope and an earlier version of Cubase SX, unfortunately I can't go back to that setup. I also have a hyperthreading P4, even turned off the hyperthreading, still no joy. It's a bit of a bugger.
It would be usefull if the people who have it working could list their specs as below.
P4 3.2GHz HT
Win XP Pro SP2
Cubase SX 3.1.1.944
Pulsar 2 with Scope v4.0
<font size=-1>[ This Message was edited by: ratkinson on 2005-11-28 00:00 ]</font>
It would be usefull if the people who have it working could list their specs as below.
P4 3.2GHz HT
Win XP Pro SP2
Cubase SX 3.1.1.944
Pulsar 2 with Scope v4.0
<font size=-1>[ This Message was edited by: ratkinson on 2005-11-28 00:00 ]</font>
Hello ratkinson,
I finally managed to have it working (though now I'm using Scope again because of latency of XTC mode... ironic but I had to give XTC a try)
In my case, it was a problem because of my PDA! Microsoft ActiveSync (for PDA Sync) uses the rapi.dll file (I guess it is in WindowsSystem32 dir, not sure though) and Creamware also uses a API from another file that is called rapi.dll as well.
What seems to happen is that Asio driver accesses the rapi.dll from ActiveSync (that is prioritary) thus never finding the tools it needs.
I solved the problem by renaming the rapi.dll present in the windows folder (ActiveSync one) and everything worked from there. Though, you won't be able to synchronize your PDA unless you rename the file again to its original name...)
Once I renamed de rapi.dll, everything worked without changing any of the scope files (I did not change xtcproject.pro, actually, changing it lead to problems instead, so try to use the original file first.)
I think you can find more info on rapi.dll by searching this forum.
I hope you'll manage to have XTC working, it's a nice feature.
Breakthru
I finally managed to have it working (though now I'm using Scope again because of latency of XTC mode... ironic but I had to give XTC a try)
In my case, it was a problem because of my PDA! Microsoft ActiveSync (for PDA Sync) uses the rapi.dll file (I guess it is in WindowsSystem32 dir, not sure though) and Creamware also uses a API from another file that is called rapi.dll as well.
What seems to happen is that Asio driver accesses the rapi.dll from ActiveSync (that is prioritary) thus never finding the tools it needs.
I solved the problem by renaming the rapi.dll present in the windows folder (ActiveSync one) and everything worked from there. Though, you won't be able to synchronize your PDA unless you rename the file again to its original name...)
Once I renamed de rapi.dll, everything worked without changing any of the scope files (I did not change xtcproject.pro, actually, changing it lead to problems instead, so try to use the original file first.)
I think you can find more info on rapi.dll by searching this forum.
I hope you'll manage to have XTC working, it's a nice feature.
Breakthru
Nice that you have it working now! About the error message, not all hosts show it... That's why I had the same problem as you.
Anyway, I've just tried the cset.ini trick, and it worked!
Can't believe I've been living without XTC, synths are so responsive now!
Thank you for mentioning it in your post, I would not have investigated in this direction without it! Thanks!
Anyway, I've just tried the cset.ini trick, and it worked!
Can't believe I've been living without XTC, synths are so responsive now!
Thank you for mentioning it in your post, I would not have investigated in this direction without it! Thanks!