i have never used cubase SX. nowhere in my email did i specify that i used cubase SX. in fact a specifically said i used fl studio. even if my problem wasnt solved i would not have been so annoyed had it not been for the fact i got blatently fobbed off. as for the problem being either with fl studio and/or my midi interface - i deduced that much on my own - thats why i contacted m-audio.
as for my email being long. i gave them every tiny bit of information that i possibly could including my own findings so that maybe they could shed some light on why this problem occurs. their telephone tech support was useless - was on hold on an international phone call for 3 minutes then i outlined the problem i had but of course, couldnt explain it in as much as detail as i could in email, consequently wasted more time filling in the person on the end of the line with info that id already explained in more detail to some other m-audio technician. this phone call had bloated to about 10 minutes and was costing me more than 5 quid by the time i got a firm answer. the advice i was given? you may want to check that your host is sending MIDI clock data.
no fucking shit sherlock. this conversation was clearly going around in circles so i hung up.
i dont think i would have been so annoyed if m-audio's tech support team didnt treat me like a fucking idiot. im deliberating whether to contact them or access again. i seriously dont think the problem is with the virus but...im beginning to think about just selling this 1010 on and looking for another 10 in/10 out midi interface. this time one that actually has a preamp on it. i wont get the price i paid for it despite it being only 4 months old and in immaculate condition. but this problem coupled with the fact that m-audio's ASIO drivers repeatedly crash my PC hard - it just seems more trouble than its worth. i cant afford a presonus firepod yet though.
|