Midi Problem / PC Freezes

astroman · Post by **astroman** » Tue Jan 03, 2006 3:50 am

nice to read it's just the label on your side, too - it IS a bug (of course), but one of those I immediately forget about and ignore.
Maybe I'm more forgiving because I've spend endless nights in front of the screen programming (years ago)

BUT... I've done it on a Mac, with sophisticated software ($10k toolkit) - it still was hard enough, and often small things suddenly revealed a potential to become complete showstoppers.

I wouldn't even dare to THINK to try the same with M$ tools like visual-I-dunno_sh*t under what they consider 'operating system'.
I remember well an Oracle developer on CeBit fair who told me '...Win NT is bullsh*t - but our customers want it, we get paid for it and so we'll do it...'

That was many years ago and for sure things haven't turned out to become more simple on the developement side of things

On 2006-01-02 22:30, psionic wrote:
...But, I have checked again the 'ControlRoom', and output 5 is dead for sure.
...
Please try ControlRoom on WindowsXP, and post a reply.

My opinion is if they have bugs on their basic modules - it could be a bug in the midi system that causes freezing problem. Active sensing, clock, etc., it must be handled properly by the hardware/software.
... and they aren't cheap at all

any 'candidate' for a (partly) functional replacement starts at least 4 times as expensive AND comes with regular update fees PLUS the requirement for new hardware 'sorry we don't support this anymore...'

I don't use the control room device myself, but if it would behave strange, I'd just replace it with a micromixer and a couple of switches or a modular patch or whatever.
Since the usual remedy is a complete re-install (which is quicker than trying to dig up the source anyway), I'd just delay it to the next unavoidable Win cleanup and live with the cludge above.
But that's just me.
I get paid for making systems run to do a certain job - it's that job that counts, whatever it takes, in the end nobody cares

cheers, tom

ps: done that control room thing
you're correct about #5 - it does not live...
an easter egg ?

check out the devices forum for switches - there have been many to supply this function

<font size=-1>[ This Message was edited by: astroman on 2006-01-03 04:15 ]</font>

ARCADIOS · Post by **ARCADIOS** » Wed Jan 04, 2006 4:59 am

standard pc

ARCADIOS · Post by **ARCADIOS** » Tue Jan 24, 2006 7:42 am

i thought northwood does not support huperthreading.

anyway, hi mexxx
my previous motherboard was asus p4c800e.
i had exactly the same problem in the beggining.
the same happens with abit ic7g.
check out if the midi module output sends clock or active sensing. to do this connect a midi monitor.(you can load midi monitor from scopes routing window at the midi path)
if the midi monitor shows these unwanted things, load a midi filter and connect it to midi output, and after connect to synths or sequencer midi dest.
another solution which is more professional is to install all your system in standard pc mode(not acpi mode).
it is better to install a fresh xp installation and at the beggining of the instalation when you are asked to press F6 to install drivers for your hard disc controllers you have to press F5.
If you install drivers for sata then press both F5 and F6 a few times.
you will be asked to install at the mode you wish.
choose "standard pc" and then the installation will continue.
with standard pc, recommended for audio at your system (i think) you will see that there is no need for midi filters at all.
also there are going to be less chances for trouble.
for example: only in standard pc i can work with three rewired applications simultaneusly without clicks and pops.
acpi caused hard clicking with two rewired programs.
note that if possible disable every bad for audio things that work together. it is better to disable from bios: firewire usb(put your mouse on the serial port) and every onboard unnecessary thing.
"also check to put the card in a pci slot that does not share the irq with other devices".

_________________
ELVIS LIVES

<font size=-1>[ This Message was edited by: ARCADIOS on 2006-01-24 07:45 ]</font>

psionic · Post by **psionic** » Tue Jan 24, 2006 4:52 pm

Standard PC...
I will try this ( last ) step of workaround to get my comp working, but I must say that if I have to bring my PC back to stone age of computers, it is not really a good solution.
Anyhow, this thread isn't about it, but if it is a price to pay, I will pay. I will miss all the colorful animated windows and other cool Micro$oft stuff

...
BTW. I read something about PCI 2.2 and 2.3 recently, so maybie there is the problem.

paulrmartin · Post by **paulrmartin** » Tue Jan 24, 2006 5:16 pm

No. Standard PC is the solution that worked for me. Ask yourself if you really, really need to see all those CPU-hungry cool animated windows(or were you joking?)

Post by **garyb** » Tue Jan 24, 2006 6:09 pm

animated windows??

turn all that off and use the midifilter. better yet, turn active sensing off on your controller.

just for yucks, go to start/accessories/system tools/syem information and check resources/sharing. is your card sharing an irq?

Spirit · Post by **Spirit** » Wed Jan 25, 2006 1:01 am

An obvious question, but I haven't seen it mentioned so far: Does your PC crash only when the keyboard is connected ?

Also, perhaps now you have fiddled with things so much that there may be new conflicts created. I always go for the "dog standard" approach and change as little as possible from all the defaults.

I just bought a new P5P-based DAW and just set it to background priority, HT off, and no animated XP crap and it all works flawlessly. That's no help to you as such, but merely to say that deep fiddling can sometimes just bring more problems.