Does anybody know if there is any new devices planned for the release? I've read about QA402 in several places, but it looks like rumors. Any info?
Does anybody know, if the Quant Asylum 400 is working still with windows 10? Or does it only run with the windows 7 software ?
Would be very helpful, if someone of the members has an idea!
best regards form germany
Joachim
Would be very helpful, if someone of the members has an idea!
best regards form germany
Joachim
Does anybody know, if the Quant Asylum 400 is working still with windows 10?
Hi Joachim, unfortunately it doesn't work with Win10 after build 1803. Your best bet is to run an old OS in a VirtualBox VM if you'd like to keep it running on a Win10 desktop.
Does anyone know which DAC/ADC that is used in QA400?
Hi MrT, It's a CS4271.
Unrelated to the above, release 1.821 is out and there are two new items that might be of interest. The first is a way to quickly verify large speaker cabinets with integrated amps (500 to 1500W) are working to spec. This is hopefully useful to those that run speaker rental businesses.
NAMM 2020 and Speaker Compression
The second is a way to export notch filter performance, and then apply that notch to measuring a really good DAC (eg ~-110 dB THDN)
Notch Filters
As always, comments/questions welcome
Last edited:
Unrelated to the above, release 1.821 is out
On my Windows 10 Pro (1909) laptop with all the latest updates, V 1.821 installs (and works) great. But V 1.900...V 1.905 not so much. They all kick out a bunch of errors immediately on starting the install and it doesn't continue.
Great work on all the nifty additions since V 1.750! 🙂 That represents a *huge* amount of work.
I still dream about a QA40(5) some day with a USB 3.0 connector (lol is that "USB 3.1 gen 1" with a USB-C these days?) and +/-15Vdc or +/-18Vdc rails, running this same wonderful software. 😀 Then I can let my cat use my trusty USB Y-cable as a cat toy. 😛
On my Windows 10 Pro (1909) laptop with all the latest updates, V 1.821 installs (and works) great. But V 1.900...V 1.905 not so much. They all kick out a bunch of errors immediately on starting the install and it doesn't continue.
Hi agdr, oh no! Can you be more specific about the errors you are seeing? Is it in the installer? There were two updates this week fixing some minor issues in the main app, and there will be another update next week too, so if we learn how to repro what you are seeing I can get it fixed.
Thanks, Matt
Hi M5c, agdr, How did you get your QA400 to work on your win10 box?
Mine just sits there and doesn't respond to anything.
When in created an old os box virtual machine win7, I spent almost a month
fooling around with it but still had the same problem, it wouldn't work.
Couldn't get anything running with it.
That was my whole point of getting the Dell Lap-top so that it would work.
I do have an older Dell Laptop around here but it has no battery and the
strange power supply plug is of the squeeze together type that is in storage
around here. I found it once again that put it where I could remember to
use it when I found the computer again, but then couldn't find the computer.
I have used the Jim Williams method of organization, which worked until
I got married. Then she baggied up everything WillieNillie in various ziplocs,
and boxed them in unrelated boxes etc then moved them all over the house,
attic, garage, closet, workBench room etc and well y'all know....
So what's the secret to getting the QA400 working with win 10?
Cheers,
Mine just sits there and doesn't respond to anything.
When in created an old os box virtual machine win7, I spent almost a month
fooling around with it but still had the same problem, it wouldn't work.
Couldn't get anything running with it.
That was my whole point of getting the Dell Lap-top so that it would work.
I do have an older Dell Laptop around here but it has no battery and the
strange power supply plug is of the squeeze together type that is in storage
around here. I found it once again that put it where I could remember to
use it when I found the computer again, but then couldn't find the computer.
I have used the Jim Williams method of organization, which worked until
I got married. Then she baggied up everything WillieNillie in various ziplocs,
and boxed them in unrelated boxes etc then moved them all over the house,
attic, garage, closet, workBench room etc and well y'all know....
So what's the secret to getting the QA400 working with win 10?
Cheers,
Sorry for very late response: I haven´t got the QA 400 working with Windows 10. I ´ll use an older lenovo Windows 7 laptop with QA 400, works fine.
But I´m looking for an alternative, because windows stopped support for windows 7. Are there other analyzers which are not to expensive?
best regards from Germany in my home-office
Joachim
But I´m looking for an alternative, because windows stopped support for windows 7. Are there other analyzers which are not to expensive?
best regards from Germany in my home-office
Joachim
It's always sad to see how hardware stops working just because vendors stop supporting their proprietary software... will the open-source QA401 ASIO driver work with the QA400?
It works perfectly with Windows 7 just make a boot able USB stick with that and the required software. Boot up with that when you want to make measurements.
It's always sad to see how hardware stops working just because vendors stop supporting their proprietary software... will the open-source QA401 ASIO driver work with the QA400?
I think Cypress is the root cause of the incompatibility. When you design around a chip you can't really know what the vendor's plans are and Win 10 was a problem. QA switched to a different chip in the QA401 which is better supported. Since the protocol is proprietary to the device it becomes quite a chore to sort it out with a platform change if your vendor chooses too not support it.
Hi Demian
I suspect you are referring to the FW download part of the cypress driver? As it should be possible to sort out the standard USB issues if any.
I understand that if Cypress doesn't maintain the Windows USB driver anymore it would be time consuming develop a new driver. However, I do think, and have previously suggested, that Quantasylum released the schematic. At least this would give someone a chance to do something I would think.
Besides, Quantasylum them self have in the past benefited from a kind soul that wrote the ASIO driver for the Q401. I don't think they lost any business from that.
Just my thoughts.
Mogens
I suspect you are referring to the FW download part of the cypress driver? As it should be possible to sort out the standard USB issues if any.
I understand that if Cypress doesn't maintain the Windows USB driver anymore it would be time consuming develop a new driver. However, I do think, and have previously suggested, that Quantasylum released the schematic. At least this would give someone a chance to do something I would think.
Besides, Quantasylum them self have in the past benefited from a kind soul that wrote the ASIO driver for the Q401. I don't think they lost any business from that.
Just my thoughts.
Mogens
I think Cypress is the root cause of the incompatibility. When you design around a chip you can't really know what the vendor's plans are and Win 10 was a problem. QA switched to a different chip in the QA401 which is better supported. Since the protocol is proprietary to the device it becomes quite a chore to sort it out with a platform change if your vendor chooses too not support it.
Honestly, IMO the root cause is choosing a chip that has a proprietary undisclosed communication protocol in the first place. The chip and firmware can be fixed, but the OS side is certain to change, especially if it's closed-source and dependent on single vendor decision (MS). Chip manufacturers are known to abandon their proprietary drivers, there was a very high chance of this situation, known from the beginning, sorry to say that.
The same is relation manufacturer - consumer. People keep paying for expensive proprietary solutions with closed-source proprietary software and then complain that the vendor stopped supporting them when the surrounding software ecosystem changes.
The same is relation manufacturer - consumer. People keep paying for expensive proprietary solutions with closed-source proprietary software and then complain that the vendor stopped supporting them when the surrounding software ecosystem changes.
Yup. But who is at fault? Is it the vendor who stops the support, or is it the consumer expecting eternal support? Where is the line?
In all fairness I don't think Quantasylum can be blamed. As I understand it's a small company and instead of developing there own solution for everything from the bottom up they choose to use libraries provided by the chipset vendor. Same thing if they selected XMOS.
Anyways, it's a bit of a waste of a good unit so it would be nice to have had the schematic instead of having to reverse the unit.
Btw. if anyone is interested in a open-source USB stack they should take a look at GitHub - hathach/tinyusb: An open source cross-platform USB stack for embedded system. It doesn't support audio class yet. But, that could be changed.
Mogens
Anyways, it's a bit of a waste of a good unit so it would be nice to have had the schematic instead of having to reverse the unit.
Btw. if anyone is interested in a open-source USB stack they should take a look at GitHub - hathach/tinyusb: An open source cross-platform USB stack for embedded system. It doesn't support audio class yet. But, that could be changed.
Mogens
Anyways, it's a bit of a waste of a good unit so it would be nice to have had the schematic instead of having to reverse the unit.
IMO there is no reason for a vendor to release schematics. It will not help with making the device working in upgraded/another OS and it contains the core of vendor's know-how.
Communication protocol is what users need to be safe for the future changes. Basically random-selected IDs of HID messages or registers carry no real know-how but releasing their values and formats makes the device future-proof. QA401 falls in that category as its open source ASIO driver is available now. If someone really wants he can write e.g. linux drivers. Kudos to QA for such move. Perhaps the next model will use standard USB audio class protocol for even more flexible use 🙂 That would allow the advanced software accompanying the device to be used (i.e. sold) separately for any USB-audio device.
Last edited:
- Home
- Design & Build
- Equipment & Tools
- QuantAsylum QA400 and QA401