PlanetZ forums - scopeusers.com

Hi,

Does anybody know if scope 4.0 has been updated to support hyperthreading? When I use scope v3.1c and HT has been actived I get lock ups frequently.
I hope this has been solved in scope 4.0.

Best regards,
Dennis.

Sorry,

This should have been placed in General Discussion.

Scope software and hyperthreading has been discussed before (how to set up affinity etc). Search this and Creamware forum.

The hyperthreading lock ups are caused by the midi ports...i don't use the Pulsar midi ports anymore, just my Midisport and no more lockups!

Dunno if this is fixed in SFP4 tho?

No, nothing has been fixed: the driver is the 3.1c one, but i was thinking "well, so they resolved the issue!".. but nothing more than some logos and a recompile..

CW seems to be quite focused on plugin dev, while SFP still has problems: it's inadmissible P4-HT issues has to be resolved, i payed for a board and now i want it working well. That's the point: i choosed CW for his reputation, not for the price: there are a lot of boards at 1/3 of the CW price... and i know *they* work, so, this is my last CW board, i will never buy another one.


<font size=-1>[ This Message was edited by: DudeZ on 2004-04-24 09:52 ]</font>

Having just bought a Pulsar 2 AND a shiny new P4 3.4 with hyperthreading this is a bit disconcerting to hear about. I will be using hyperthreading as my PC is intended for 2D and 3D graphics - not just audio. Turning it off is not an option - nor is turning off my midi in/out as I'll need that for my keyboard. I hope a fix is on the way asap - they really should prioritise this or I for one will be emailing them to sort it out.

<font size=-1>[ This Message was edited by: Kymeia on 2004-05-03 18:44 ]</font>

well, an external (possibly 2nd hand) midi interface at SUCH a shiny new box shouln't be a show stopper

the CWA midiports are somewhat sensitive - don't flood them with time code, for example...

I have no insights on the programming, but 'those' infamous drivers have a lot more to do than soundcard midi ports.
Almost any item on the GUI is midi automatable in both directions.
If you move a slider it actually has to send the assigned controller values and since the GUI (as the trigger) is cross platform it probably doesn't care (or know) much about HT.
At least in some situations the system has to be prepared for a heavy midi load not immediately visible.

cheers, Tom

Do the HT lock ups occur with XTC mode as well?

On 2004-04-22 14:01, BingoTheClowno wrote:
Scope software and hyperthreading has been discussed before (how to set up affinity etc). Search this and Creamware forum.

Thanks - that's a useful tip - I found this:

http://www.planetz.com/forums/viewtopic ... forum=19&0

and will try it first if I get the same problems.

Otherwise I could always try a Midex or Midisport - anyone know which is better? (Steiny say Midex has lower latency - true/false??)

Don't ignore Astroman's comment too, it is very important, MIDI clock messages will bring the system down.

Also, stay away from USB MIDI, that's another wet dream .

<font size=-1>[ This Message was edited by: BingoTheClowno on 2004-05-04 10:53 ]</font>

I'm not sure I understood it. How would you flood a midi port with timecode? (I'm no expert on hardware). All I'm using midi input wise is a Korg Workststation that doubles as controller keyboard - that should be safe enough shouldn't it?

Oh and you say stay away from USB midi - does that rule out the suggested Midisport etc? I though it was a midi to USB device, no?

<font size=-1>[ This Message was edited by: Kymeia on 2004-05-04 10:58 ]</font>

I dont know,

- ACPI Mode With HT running.
- P4 3.2c
- Intel D875PBZ
- Steinberg Midex8 *USB
- ScopePro Running SP4.0

Working like a charm, and thats also with a UAD-1 and a Powercore in the same box, no issues as of yet with my CW card and HT.

EDIT: just wanted to add that the way I control midi in the CW enciorment is I rout an Midex output into the CW in's, and in the enviorment I removed all sequencer host/dest, and midi dest module, the only module concerning midi is Scope Midi Source (hardware).

Cheers!

<font size=-1>[ This Message was edited by: Basic Pitch on 2004-05-04 11:07 ]</font>

If you set your external keyboard as Master, it will start sending out MIDI clock messages at very frequent and precise intervals (500ms - 1s, not sure how much exactly) that your sequencer or other devices will use to syncronize themselves too. Those MIDI clock messages apparently overwhelm Pulsar's MIDI input.

If you see any MIDI lights pulsing on any synths loaded in your project, that means some device is transmitting MIDI clock messages, save your work and prepare for a BSOD

About my comment about USB MIDI, USB MIDI is riddled with latency problems, see Steinberg company, they came up with some low latency USB drivers.

<font size=-1>[ This Message was edited by: BingoTheClowno on 2004-05-04 11:23 ]</font>

<font size=-1>[ This Message was edited by: BingoTheClowno on 2004-05-04 11:28 ]</font>

On 2004-05-04 08:48, Kymeia wrote:

http://www.planetz.com/forums/viewtopic ... forum=19&0

I 've tried to assign CPU affinity to CPU 0 for SFP and it works fine but when I reboot the all is restored : SFP affinity for both CPU.
do u know how make definitive (after the reboot) this change in the task manager ?

There is way to assign affinity permanently but you need Win2K Resource Kit. In there there is a utility that will do that. I don recall the name of that utility at the moment but if you have patience, I will get it by tomorrow

You can also try to search for it on Microsoft's site, try Windows 2000 Professional Resource Kit and then browse thru all utilities.

The whole resource kit is available here:

http://www.dynawell.com/support/Reskit/win2k.asp

which file were you referring to? Was it the The Interrupt Affinity Tool or another?

<font size=-1>[ This Message was edited by: Kymeia on 2004-05-10 20:24 ]</font>

thanks for the answers , but this is for Win2k but it will work with Win XP ?

<font size=-1>[ This Message was edited by: claudioD on 2004-05-10 21:28 ]</font>

It should as win2k = Nt5.0 and winxp = nt5.1. That's not to say it WILL but it is probably worth a shot
I think they did add 2 additional priority levels for cpu priority in Xp. I doubt that broke backwards compatibility with anything else though.

They changed a lot in Win XP (as far as APIs goes) but everything is backwards compatible with Win2k. I couldn't find the utility that assigned the process to the CPU permanently (I know I saw it somewhere). I'll have to look more. It wasn't the Interrupt Affinity.

<font size=-1>[ This Message was edited by: BingoTheClowno on 2004-05-11 10:41 ]</font>

The tool and how to use it.

Here's another similar program:
http://www.appliedvisual.com/xcpu.htm