Page 1 of 1

Faulty card: help

Posted: Mon Oct 05, 2020 10:18 pm
by the19thbear
Hi.
I got a 15 dsp card that kind of works.
It opens up fine in scope 4.5 and I can load things on it, but whatever midi comes in from the hardware midi input is garbled.

Hanging notes here and there, weird low key randomly triggered etc.

I have not succesfully gotten it to recieve midi from an internal source (reaper etc). Might be a settings thing, might be a faulty card.
It has been about 12 years since i last used scope, but dont you just use the sequencer midi source and connect it to a scope synth?

I also tried to use the built in mini-midi keyboard to trigger synths, but that never works for some reason.

Has anyone else ever experienced these problem?


Next step is to completely remove the cable snake. Maybe it is causing weird shorts. Will route adat out instead and try internal midi.

Really sad because this card works 95% it seems.


If all fails, I will go for the "bake in oven" approach. I have salvaged a macbook pro that way in the past.

Thanks
:)

Re: Faulty card: help

Posted: Mon Oct 05, 2020 10:52 pm
by valis
Is this the only card in the system?

Cable whip won't affect internal midi the same as external midi, in that case midi timing is dependant not just on the DSP card but how well it's playing with the host system. What's the masterverb test giving you right now with that setup? What's your DPC latency?

Re: Faulty card: help

Posted: Tue Oct 06, 2020 12:34 am
by the19thbear
Will do a masterverb test and DPC latency test and report back.

Will also try on my brothers computer. I think it has a PCI slot.

Thanks:)

Re: Faulty card: help

Posted: Tue Oct 06, 2020 2:21 am
by the19thbear
when loading the 9th masterverb (not classic), it stopped working. So 8 masterverbs.

Unplugged the cable whip and playing with scope virtual midi keyboard works fine when connected to Uknow.

This is on XP so its hard to run another daw etc.
Will have to get a temporary v7 key from garyB.

Hmmm... will investigate further

Re: Faulty card: help

Posted: Tue Oct 06, 2020 11:41 am
by valis
5.1 & 7 were both much better in regards to 'performance tuning' much like 4.5 eliminated the need to play with CSET.ini to get board order correct. I didn't find this gave me more system headroom, just that it took less fiddling to make my Scope cards happy within the performance that a board would offer.

That being said, you've disabled unnecessary devices on that motherboard and reduced background stuff with windows I presume?

Also DPC latency tests to ensure you don't have an errant driver/hardware combo at present: https://www.sweetwater.com/sweetcare/articles/solving-dpc-latency-issues/

Re: Faulty card: help

Posted: Wed Oct 07, 2020 7:01 am
by the19thbear
Ok. Will look at Dpc.
Emailed Gary the other day. Waiting for a temporary v7 key. Then I will test further.

Re: Faulty card: help

Posted: Wed Oct 07, 2020 2:57 pm
by valis
Are you using XP for this?

Re: Faulty card: help

Posted: Thu Oct 08, 2020 1:35 am
by the19thbear
Using win 10.

Testing so far: using scope midi input= weirdness.
Using another usb to midi convert and routing that to scope seq source, everything seems to work fine. Will let the computer stay on for now to see if it craps out.

Current dsp load is about 95% (maxed out the system on purpose). Will see if I get any pci/dsp errors.

Will have to test further.
Looks promising so far.

Re: Faulty card: help

Posted: Thu Oct 08, 2020 5:59 am
by garyb
sounds like a bad cable whip...