sx and windows hanging

Shroomz~> · Post by **Shroomz~>** » Fri Aug 11, 2006 1:04 pm

It shouldn't make a difference to be honest (or at least, hasn't for me .. either way)

gustav · Post by **gustav** » Sat Aug 12, 2006 3:55 am

I have now a PC with winXP
I put the Pulsar2 in the PC and installed the driver CW

Now do I
* put in the scope srb 14
* install driver srb
* install sx
* install sfp 4.5
or should it be done in another order ?

[ This Message was edited by: gustav on 2006-08-12 04:56 ]

tgstgs · Post by **tgstgs** » Sat Aug 12, 2006 4:25 am

i do it 1. scope platform 2. sequenzer install but i dont use xtc dont know how to then

gustav · Post by **gustav** » Sat Aug 12, 2006 5:51 am

I installed SFP4.5
i created a new project
When I add the sts5000 :

PROBLEM
Can't find DSP file S4K Master Gain - Please check installation

Sorry I found the post and the .bat file to fix this problem - thanks to valis !

[ This Message was edited by: gustav on 2006-08-12 07:25 ]

gustav · Post by **gustav** » Sat Aug 12, 2006 7:24 am

First impressions :
After a very simple test with only a sts i'm going for a more real one (1 bass, many drums):
for some minutes : sts stable - loop stable - then windows is hanging !
I will see the next days how it goes ...

Shroomz~> · Post by **Shroomz~>** » Sat Aug 12, 2006 7:51 am

Gustav, for testing purposes try looping SX on a 1 or 2 bar loop instead of 2 beats (half a bar) It should be less likely to crash that way.

gustav · Post by **gustav** » Sat Aug 12, 2006 1:24 pm

Yes I'm testing in general looping on multiples of 1 bar.

more tests with sts :
playback on 2 bars : hanging after 30-180 secondes
playback on 2 bars with strong midi editing : hanging

testing with vst LM-7 :
recording bass on 3 bars : stable
playback on 2 bars with strong midi editing : stable

[ This Message was edited by: gustav on 2006-08-12 14:25 ]

Post by **garyb** » Sat Aug 12, 2006 5:57 pm

are you sure that there is no midi feedback loop using the sts? if you are throughputting midiclock, that can fill the buffers and make a feeze occur. how are you routing the sts?

Shroomz~> · Post by **Shroomz~>** » Sun Aug 13, 2006 3:49 am

Are you still using STS-3000 ?

[edit] sorry, I see you're now using STS-5000, is that right? [edit]

[ This Message was edited by: Shroomz on 2006-08-13 04:50 ]

gustav · Post by **gustav** » Sun Aug 13, 2006 4:49 am

On 2006-08-12 18:57, garyb wrote:
are you sure that there is no midi feedback loop using the sts? if you are throughputting midiclock, that can fill the buffers and make a feeze occur. how are you routing the sts?

In my present testing phase I did not connect any external midi equipement (except the noah) and the problem occurs.

I already encountered that what I imagine you understand by midifeedback, because I wanted to get back the feedback of controlers to bfc2000 and in the first time I did not pay attention to this problem : midi looped around ad infinitum and the system hanged, BUT this happened immediatly.

I corrected this problem and I experienced good results on 2 projects.

In the next days I will test this kind of projects - so nevertheless I give you the midi routing to see if there is any problem about it :

* midi master keyboard SL880Pro
* midi fader box BCF2000 (USB mode)
This is the way that midi will take on my sfp routing :

Used for playing VST, SST, Noah :
Pulsar2MidiASource => SequencerMidiDest1
Noah : MidiNoah
SequencerMidiSource1 => STS5000

Used for Fader feedback :
Cubase first bcf2000-track :
records midi coming from bcf2000 and sends to :
SequencerMidiSource2 => STM1632MIn
STM1632MOut => Merger
SequencerMidiSource2 => Merger
Merger => SequencerMidiDest2
Cubase second bcf2000-track :
Midi comes back to be sent back to bcf2000

gustav · Post by **gustav** » Sun Aug 13, 2006 4:52 am

Yes I am now exclusively using STS5000

gustav · Post by **gustav** » Sun Aug 13, 2006 5:03 am

again more tests with sts :
it appears to me that the probleme is very often related to an action on the screen (selecting or editing events, ...)

is there anything I can do to eliminate some of this sharing conflicts :

I/O Port 0x00000000-0x00000CF7 Bus PCI
I/O Port 0x00000000-0x00000CF7 Contrôleur d'accès direct en mémoire

IRQ 20 Intel(R) 82801GB USB Universal Host Controller - 27C8
IRQ 20 Intel(R) 82801GB USB2 Enhanced Host Controller - 27CC

I/O Port 0x000003C0-0x000003DF Intel(R) 955X PCI Express Root Port - 2775
I/O Port 0x000003C0-0x000003DF Matrox Parhelia APVe

Memory Address 0xE8000000-0xEFFFFFFF Intel(R) 955X PCI Express Root Port - 2775
Memory Address 0xE8000000-0xEFFFFFFF Matrox Parhelia APVe

I/O Port 0x00000400-0x0000041F Ressources de la carte mère
I/O Port 0x00000400-0x0000041F Intel(R) 82801GB SMBus Controller - 27DA

IRQ 16 Intel(R) 955X PCI Express Root Port - 2775
IRQ 16 Matrox Parhelia APVe
IRQ 16 Intel(R) 82801GB PCI Express Root Port - 27D0

Memory Address 0xA0000-0xBFFFF Bus PCI
Memory Address 0xA0000-0xBFFFF Intel(R) 955X PCI Express Root Port - 2775
Memory Address 0xA0000-0xBFFFF Matrox Parhelia APVe

I/O Port 0x000003B0-0x000003BB Intel(R) 955X PCI Express Root Port - 2775
I/O Port 0x000003B0-0x000003BB Matrox Parhelia APVe

Shroomz~> · Post by **Shroomz~>** » Sun Aug 13, 2006 9:57 am

Take it one step at a time would be my advise. Don't connect up lots of midi gear until you've got a clear picture of what may be the problem. For example, if you suspect STS to be the problem, I'd do some serious testing without STS involved. If you have no problems until adding STS into the picture, then you'll have found the source, if not, you'll have eliminated a possible suspect.

Post by **garyb** » Sun Aug 13, 2006 1:24 pm

the irq sharing does not look like a problem. often ati cards cause problems because their software sets them up with ridiculous pci latency settings. perhaps an application like double dawg would help.

cemhot · Post by **cemhot** » Sun Aug 13, 2006 4:17 pm

I cant follow all the technical details folks posted.
But:
This sounds very similar to the problem i had.
After doing researches for half a year i disabled Hyperthreading in Bios.
Since that everything is ok.
Asus P4P800 Deluxe.

gustav · Post by **gustav** » Tue Aug 15, 2006 4:11 am

I had a look at the bios settings and the asus utilities and the P5WD2 spec's :
I installed AI Booster - not to o/c but to get information about the system.

1)
The multiplier is not always on 15 but goes sometimes on 14 - the frequencie is in a range between 28000 and 3000 MHz

2)
the votltage varies IMHO in a wide range : it comes up to 1.42 - on the cpu specifications says : Core Voltage 1.25V-1.4V

Shroomz~> · Post by **Shroomz~>** » Tue Aug 15, 2006 4:47 am

Have you got those settings running on 'auto' mode? If so, try setting them manually instead. If you still notice abnormal voltage fluctuations I'd change the PSU.

gustav · Post by **gustav** » Tue Aug 15, 2006 5:32 am

In the first time I was on Auto mode.
Now I'm in Manual mode :
Here I can fix :
CPU Frequency = 200
But I can't find a place where I can enter the Bus/Core Ratio
I found a nice page for those who have this mb :
http://vip.asus.com/forum/view.aspx?id= ... uage=en-us
Ther is mentionned the bios option AI CPU Lock Free : Only D 8x0 procs. Disabled for stock
I have a D 830 proc - but what does mean "stock" ?

PS : what means PSU ?

[ This Message was edited by: gustav on 2006-08-15 06:33 ]

Shroomz~> · Post by **Shroomz~>** » Tue Aug 15, 2006 5:41 am

Depending on the context stock means either 'by default' or 'off the shelf' (new) I'd say in your case it maybe means 'by default', but I don't have that mobo.

PSU means 'power supply unit'

gustav · Post by **gustav** » Tue Aug 15, 2006 6:52 am

I fixed the Core Voltage manually - now the max is 1.34 which seems to be ok

But problem remains !

in the bios my CPU VCore Voltage setting is now always yellow ! (all the other coulors are blue/grey/white) : does this mean anything ? its not explained in the user guide.

remains this continous variation of the multiplier (15 => 14 => 15 => 14 => ...) !
if there is somebody with the same mb : could you check this tool AI booster (to make sure if it comes not from this soft)