Hi,
Hard Drive of my old PC has broken. I can`t find USB driver for the WaveIO
Please give me a link to download ?
WBR
V. Bausen
Hard Drive of my old PC has broken. I can`t find USB driver for the WaveIO
Please give me a link to download ?
WBR
V. Bausen
Driver updated to v5.57.0 and v5.58.0 (both in the same day as I had to catch up with .. things
)
I replied to some emails, I don't know if it was yours but I'll give PMs

I replied to some emails, I don't know if it was yours but I'll give PMs
hi lorien;
i also need the latest driver. my recent one (3.34) does not work with windows 10.
its true, that the driver is not downloadable from the website, right?
are there older boards, the newest driver is not compatible with?
thanks for your help!
i also need the latest driver. my recent one (3.34) does not work with windows 10.
its true, that the driver is not downloadable from the website, right?
are there older boards, the newest driver is not compatible with?
thanks for your help!
my recent one (3.34) does not work with windows 10.
Microsoft Windows [Version 10.0.19041.1288]
2.23 and 3.20 works.
Did you make a firmware update of the board, too?
I have different XMOS boards, my own.
But it doesn't matter - any XMOS-based board will work if it's USB PID&VID are exists in the driver's .inf file.
but would love to have the new driver, too, if available!
It depends whats new in the newer version and is it useful.
I have no ideea where you got that information but, from what I know, I struggle over the years to make drivers compatible with all my WaveIO boards. The main problem was to run drivers on different Windows OSes as those are changing over time.are there older boards, the newest driver is not compatible with?
thanks for your help!
As for the driver pack, I give you a PM with link to it so you can enjoy.
Well, this is the problem I'm facing starting back in 2011 and it seems that is not over now...I have different XMOS boards, my own.
But it doesn't matter - any XMOS-based board will work if it's USB PID&VID are exists in the driver's .inf file.
Compared to your alternative (to change usb vids and pids in a couple of minutes - at most!), I have to pay for new driver releases to Thesycon just to gain access to whatever is new in that release and freely offering it to anyone who owns a WaveIO card and an Windows-powered host. I would LOVE to have that driver free of charge but those are Thesycon's therms. I tried to get it for "free" but got stuck in some sort of NDA agreement and commercial things which only free cannot be called...
I know this forum is a diy place, I'm a diy-er myself but some things cannot be solved as easy as you say! From what I remember, in 2014 when changing USB VIDs and PIDs was something common (my drivers were changed in particular, especially by a huge number of chinese copycats...), in our long discussion, Mrs. Ute and Mr. Udo from Thesycon called this approach to be "stealing". Not my word, theirs...
I guess this USB VID/PID changing approach is the reason why they've abandon the way of configuring drivers on customer's side (using their own signing cetificate - at that time) to Thesycon side.
Well, this is boring stuff... I'm sure you can easily find alternatives for downloading latest drivers from other companies that are offering it free to download!
Last edited:
Why do you need the Windows driver at all? (Win10 has internal).
I know only one reason - "Native DSD" (because it required ASIO).
DSD DoP have some limitations, but DSD64-128 works well.
For PCM - WASAPI is no worse than ASIO and works w/o driver.
I know only one reason - "Native DSD" (because it required ASIO).
DSD DoP have some limitations, but DSD64-128 works well.
For PCM - WASAPI is no worse than ASIO and works w/o driver.
It wasn't always like this! I remember back in the day when there was no driver support from Microsoft, that's why XMOS worked with Thesycon for their audio solutions. In my eyes, Thesycon proved their quality over the years (my honest opinion, I'm not making any advertising for them) so I guess it's some sort of inertia. As you already said above, there are some things covered by this driver that MS native ones don't do it till now...Why do you need the Windows driver at all? (Win10 has internal).
hi everybody,
sorry @Lorien, i mixed up two things. i thought there are (older) boards which are not compatible with the latest FIRMWARE.
and thanks for the driver via pn. yesterday i was able to install ver. 2.23, which worked with win 10.
anyway, i like to be up to date with drivers and firmware, to get dsd support e.g.
and of course thanks to @Lorien for all your support. its a wonderful board!
kind regards!
sorry @Lorien, i mixed up two things. i thought there are (older) boards which are not compatible with the latest FIRMWARE.
and thanks for the driver via pn. yesterday i was able to install ver. 2.23, which worked with win 10.
@altor: without the driver, i could not use asio and had crackles during playback.Why do you need the Windows driver at all?
anyway, i like to be up to date with drivers and firmware, to get dsd support e.g.
and of course thanks to @Lorien for all your support. its a wonderful board!
kind regards!
Exactly, but...I have different XMOS boards, my own.
But it doesn't matter - any XMOS-based board will work if it's USB PID&VID are exists in the driver's .inf file.
The board descriptions will stick to what is contained in the already builded driver file. "DAC XYZ" 😒
A rustic way around this is manually editing the descriptions through the Windows registry after it's installed, but that's annoying. 🙄
Is there any way to edit the files before installation?
No, not in reristry, but in .inf files.through the Windows registry after it's installed
Is there any way to edit the files before installation?
Yes. The same .inf files.
If you installer is one .zip file, you need previously unpack it.
But, all thes may have a problem with the driver;s Digital Sign.
The setup is just an .exe fileYes. The same .inf files.
If you installer is one .zip file, you need previously unpack it.
"XMOS_USBAudio_v5.58.0_2023-05-25_setup.exe"
I can't extract the files to edit before it installs. How did you do it?
For the latest versions - I don't know yet.How did you do it?
I did this on previous versions - .exe is self-extracting archive, and it is possible to extract files with winrar or winzip.
For the previous version after extraction, there is a set of the normal files (exe, dll, sys, and also inf), whic can be edited. Not need to pack it back to /exe to run setup. But fo some versions it might be a conflict with the Digital Sign.
Latest version - the is one .mst file and one .msi file inside .exe.
.msi is also possible to extract (using winrar, 7z, msiexec, etc.) but after that we got a set of files, like "fil0a4a1a914d0d4ad5ae4591f7080a01cb" - and I don't know what to do next.
Maybe is possible to edit .inf files after install, but I did not try.
No it isn't that's why I politely ask you to not do it! I understand that we all are diy-ers and I kinda allow this kind of discussion on this thread but Thesycon stated clearly this type of modifications is equal with theft! If you have any doubts then please feel free to ask Mrs. Ute or Mr. Udo Eberhardt directly!I'm not going to post a tutorial because don't know if it's allowed, but the mission was completed successfully.
Back around 2014 there was someone else who did the same thing: trying to "adjust" a pack of drivers for their needs and because of that Thesycon didn't allowed anymore for any users to release their own drivers using personal Microsoft certificates. I was affected directly because those drivers were meant for WaveIO.
So, given all above if you need to share your findings with someone else please open a separate thread or... pay 499 Euros for your own driver version, like I'm doing for more than 12 years. As you can see we take different paths so altor and felipeunix please stop discussing about how to hack drivers on this thread.
Lorien, I agree, however, the technique is well known.
I personally have never hacked them (I use Android and Linux, so do not need the drivers).
I just simply described how to unpack a self-extracting archive in .exe to the separate files.
I personally have never hacked them (I use Android and Linux, so do not need the drivers).
I just simply described how to unpack a self-extracting archive in .exe to the separate files.
I understand that we all are diy-ers
No. I'm diy, the forum is diy, you is a Vendor.
I do not have a registered trademark, nor any product for sale.
I want to clarify that i only did tests for my own knowledge. So much so that, I haven't shared how to "hack" any product here.
Back around 2014 there was someone else who did the same thing: trying to "adjust" a pack of drivers for their needs and because of that Thesycon didn't allowed anymore for any users to release their own drivers using personal Microsoft certificates. I was affected directly because those drivers were meant for WaveIO.
It is obvious that you have to pay for a license if you want to use it in your products. Nothing extraordinary in his attitude.
I agree! I'm not a vendor, only DIY person in my spare time, don't want to make money from it.As you can see we take different paths
From my part, the discussion is closed.
I'm sorry for anything. And don't worry friend, i will never be your competitor.
yep! i also use Linux.I use Android and Linux
who depends on Windows in 2023?
but knowledge is always good.
I meant for audio only - I use Android+Kodi at NVIDIA Shield and Yoctoap at NUC- https://albumplayer.ru/linux/english.htmlwho depends on Windows in 2023?
But for general computer work I use Windows, of course.
- Home
- Source & Line
- Digital Line Level
- XMOS-based Asynchronous USB to I2S interface