Okay folks... I want to upgrade to SX, but I've been broke and scared. Anyone running the SX/Pulsar combo yet? Is it stable? All input appreciated. Peace
RL
Cubase SX and Pulsar opinions!!
Hi,
I tried installing SX on Win98 - didn't work - the installer checks your o/s first.
But SX and SFP run well on XP (home edition) on my system (AMD 1.2 Ghz with VIA Apollo KT133A mobo). My one piece of advice is, do a CLEAN install of XP. I tried upgrading from 98 but kept getting PCI overflows with SFP and SX. Once I blew 98 away and installed XP - I've had no problems.
Cheers
I tried installing SX on Win98 - didn't work - the installer checks your o/s first.
But SX and SFP run well on XP (home edition) on my system (AMD 1.2 Ghz with VIA Apollo KT133A mobo). My one piece of advice is, do a CLEAN install of XP. I tried upgrading from 98 but kept getting PCI overflows with SFP and SX. Once I blew 98 away and installed XP - I've had no problems.
Cheers
Just wanted to throw in my agreeance...
I'm running Win XP pro, Luna 3.01 and Cubase SX. It is very stable and works great.
The new Logic on the other hand does not work as hot. Makes me not care too much they're not making Logic for PC anymore.
I do really wish there was a sysex and/or controller dump request message on all creamware modules. It would make it much easier to interface w/ cubase and an external knob box or synth w/ knobs.
todd
I'm running Win XP pro, Luna 3.01 and Cubase SX. It is very stable and works great.
The new Logic on the other hand does not work as hot. Makes me not care too much they're not making Logic for PC anymore.
I do really wish there was a sysex and/or controller dump request message on all creamware modules. It would make it much easier to interface w/ cubase and an external knob box or synth w/ knobs.
todd
Hi,
I do really wish there was a sysex and/or controller dump request message on all creamware modules. It would make it much easier to interface w/ cubase and an external knob box or synth w/ knobs.
You can achieve the same by using presets and program changes. I know, you'll have to save the presets and assign program changes to them. But the upside is that this bottleneck of a midi connection will not be overloaded

You'd have to send like each preset-stored parameter via midi, which will take ages to receive/transmit. I agree, some CC# could be factory preset, but have you seen the variety of devices and controls? It would simply be undoable to make anything logic in that.
Now, each user, for himself and his midi controller, can bring logic in the CC# remote, according to his controller. Hardware synth users ie. GM/GS CC# setup, Phatboy uses (afaik) logical 1-127 CC#, which already would make the factory CC# presets unuseable.
I think the SFP preset list contains all secrets and novelties we'd wanted to know since longtime.
I did upload over 50 presets for PC1600x here, to control CW devices. No one else has ever sent me (or better, uploaded on z) one of his own PC1600x presets. Not even the ones who promised me to.
How can we expect CW to do better on automation? We can't. It's we the users that need to upload and distribute our Remote Control Presets. That seems most obvious to me.
When I find the time I will sure create and upload CW controller presets, parallel to my PC1600X presets. In the meanwhile, I ask you to upload your Controller Presets, to be used with whatever Remote Control hardware device that you're playing with. Have a look at my PC1600x presets, there might be usefull infomation for you about CC# assignments, which CC# to avoid etc etc.
Enjoy your weekend,
at0mic.
more has been done with less
https://soundcloud.com/at0m-studio
https://soundcloud.com/at0m-studio