[TritonXParticipant]

I’m still in communication with Intel support since A&H points the responsibility to them.

After cursing at them a few time the support guy finally seems to try hard to help me(us). I made them a explanatory video and gave them a hardware report and I’m waiting for a follow up…

[TritonXParticipant]

I purchased a MSI A68MH motherboard, a cheap 4.1 GHZ AMD CPU (not the cheapest but close, forgot which one) to go with it. 8 GB of 1666MHZ, a 256GB SSD and the rest (case, PSU, HDD, monitor) I already had at home. All that for less than 500$.

It’s not as good and fast as the Intel laptop I planned to use but it’s still perfectly usable and had no issue recording with it in 2-3 weeks of usage.

I wouldn’t call buying another computer “A SOLUTION”. When I made the joke to the Intel support guy he told me, ” I’m happy you found a solution”, replied with “I think you didn’t get the joke… Joking aside, while not very useful, I have nothing to say against the guy who I was in contact with for the support. I have the impression he really tried to make a follow up and solve my issue but since it would require a rewrite of their drivers his bosses weren’t really willing to go that way…

Probably that there is no issues with other Intel chipsets but screw them …

[TritonXParticipant]

Use mix 1 to 4 to send whatever(click) you want from the inputs or computer to any of the 4 mono xlr outputs in the back to the FOH.

As for the st3 output, you have to switch the preamp(top left of the console) to USB mode and make sure your computer is set to use it.

[TritonXParticipant]

Welcome to the club. See my other posts, I made a follow up with Intel and to make it short.

You are screwed, buy another computer without INTEL parts because they don’t deserve your money anymore …

[TritonXParticipant]

Follow up from Intel

“I have gotten the research done to find out what is required to create the logs for this matter.

It would be required to purchase hardware devices and download the software form the vendor to perform the validation test to get the log files. Customer can consultant vendor for further information.

For hardware required please visit: https://teledynelecroy.com/protocolanalyzer/protocolstandard.aspx?standardid=4&capid=103&mid=511

Since the current OS is Windows 10*, and the USB 2.0 driver is native driver which means it comes from Microsoft, so if this is an driver issue, customer needs to get support from MS for a solution.

I understand it may be tricky to proceed with the tests, but in case you are able to, it would be great.
”

I’m not buying a hardware that cost more than my laptop without billing them…

Admit that it is a good way for them to dodge the issue and put the blame on me…

BOYCOTT INTEL

[TritonXParticipant]

I did found the solution to the problem.

Buy a new computer with AMD part, that’s exactly what Intel suggested me to do…

It did fixed my issue…

[TritonXParticipant]

Congratulaion, welcome to the club I’m not alone and you just inherited a brick!!!!

Buy a new computer made with AMD part like I did and you will be fine.

I just got a follow up from Intel and here is what they want… since apparently it is not Q&H problems… there is no problem with your console as I was told.

FROM INTEL support after I offered them to do whatever they need to get more info about the issue:

“I have gotten the research done to find out what is required to create the logs for this matter.

It would be required to purchase hardware devices and download the software form the vendor to perform the validation test to get the log files. Customer can consultant vendor for further information.

For hardware required please visit: https://teledynelecroy.com/protocolanalyzer/protocolstandard.aspx?standardid=4&capid=103&mid=511

Since the current OS is Windows 10*, and the USB 2.0 driver is native driver which means it comes from Microsoft, so if this is an driver issue, customer needs to get support from MS for a solution.

I understand it may be tricky to proceed with the tests, but in case you are able to, it would be great.
”

They want me to buy a very rare hardware that is probably more expensive than my laptop to start with, this is a joke and the joke is on us.

[TritonXParticipant]

I got this from them this morning after a few email back and forth,
, I guess it is proper to share with you so you know what to expect:

From A&H support:

”
Yes… Well…. It should be backwards compatible of course. My point is that there is nothing wrong with your Qu, but I am trying to help as best I can.

We have been able to reproduce the issue here, the problem is that it is not a reliable reproduce.
For example, if you monitor the USB bus, the issue can resolve itself.
It can appear for seemingly no reason, then disappear without reason too.
We could soak a unit for a week and have no problem, then suddenly it appears again in general use.
”

Then the answer from Intel support(all in the same day, wow)

”
It is much appreciated that you reported this matter with us.

At this point, we are aware of this and the current status would be No plan to fix it.

Sorry for any inconveniece this may cause.

Please double check this link https://intel.ly/2uOHDon to find the Errata where this is mentioned (Page 15 Bullet #1).

”

Make up what you want of those “official” answer.

In the Intel link they sent there is even a solution(good practice lesson) to their incompetence, how nice of them.

”
Isochronous traffic is periodic and cannot be retried thus it is considered good
practice for software to schedule isochronous transactions to start at the beginning
of a microframe. Known software solutions follow this practice.

• To sensitize the system to the issue additional traffic such as other isochronous
transactions or retries of asynchronous transactions would be required to push the
inbound isochronous transaction to the end of the microframe.
”

… I don’t expect a fix anytime soon :/

[TritonXParticipant]

Well, apparently everyone with a Intel chipset7 is left behind, Got an answer from Intel. They know, they don’t care, won’t fix. A&H position is that there is nothing wrong with the QU so they aren’t putting much effort into fixing this as much as I understood.

Will try to boycott Intel but those f_____s are everywhere.

Those Ryzen look interesting suddenly. Guess I’ll go back to AMD for a while, like in my youth.

[TritonXParticipant]

Answer from Intel

“It is much appreciated that you reported this matter with us.

At this point, we are aware of this and the current status would be No plan to fix it.

Sorry for any inconveniece this may cause.

Please double check this link https://intel.ly/2uOHDon to find the Errata where this is mentioned (Page 15 Bullet #1).”

So expect no progress from Intel side and A&H also is not in a hurry to fix this since, “there is nothing wrong with my QU”

I’ll make sure to boycott Intel… if it’S possible… sigh

[TritonXParticipant]

I tried and all the ports became unusable. Blutooth and the built-in camera also.

[TritonXParticipant]

Oh yeah that will run a lot of vts…

I understand some of you are well meant when they suggest alternatives but if that’s what I’d wanted, that’s what I would have asked for.

Pardon my naivety for assuming that my top of the line brand new laptop would be more than enough to run cubase(with almost real-time effects) and a state of the art console.

I’ll try again to contact Intel next week since it is obvious that they should be the one fixing it and I never said otherwise.

BUT, if A&H engineer have an idea how to fix this… even if it means starting their drivers from scratch, maybe that’s what they should do. Because as someone else said, this is not a problem that will go away just by managing around it.

[TritonXParticipant]

“recording instead directly to a stand-alone hard drive, then off-loading recordings into the box.”

That’s not a solution that is abdication and not very possible with the workflow I had setup with the console, my laptop and cubase.

I am also in contact with Intel since A&H seems to not want to make it their problem.

They made it clear that Intel made a mistake in their xHCI drivers, then why doesn’t Intel(a huge company) want to fix this ?

I blame the manufacturer because they were aware of this possible issue and made no warning in the documentation about it.

[TritonXParticipant]

So it’s been more than a year and they don’t even have the honesty to warns us when we buy a console that USB 3.0 is broken? This is kind of important because I bought it to be the interface of my studio…

The official answer I got was that Intel messed the xHCI drivers and when I went to Intel they don’t seem to care much about the issue…

Any other hardware manufacturer having this problem with their consoles ?

So what the …. is going on ?

Time to put more pressure on them an go public?

[TritonXParticipant]

That’s why I put them pre fader somewhere in the setup.

[Author]

Posts