Hi Guys,
I’m looking for some feedback on if the USB Audio is working for you.
So any issues post them here with the details of your machine, Windows/Mac/linux, os version etc.
Also anyone with no problems at all could you also please post here so we have some idea how widespread any issues may be?
Thanks
Andy
I don’t seem to be able to get the USBAudio to work here.
I’ve reflashed the firmware and have set the option up under preferences and made a very simple patch which just sends noise to the usbaudio/out stereo object. I’ve uploaded that as the start-up patch.
When I restart my Mac is can see the Ksoloti Core as a four channel soundcard option but I don’t seem to be able to hear anything using the Ksoloti headphone or master 1/4" outputs when I set some open input channels up in my DAW. Am I missing anything obvious here?
Ah, are you talking about sending audio from the DAW to the hardware outputs on the ksoloti?
If you want to send audio from your DAW to the outputs on the Ksoloti, and audio from the inputs of the ksoloti to the DAW do something like this:
p.s. You shouldn’t need to restart the Mac, the audio device should just appear without you needing to do that.
So I’ve loaded the example patch from the usbaudio example files as the startup file on the SD:
My audio settings look like this:
When I go into Reaper or Max etc having selected Ksoloti Core as the audio input and output device and open up an input channel I was expecting to hear the two sinewaves from the patch, what I’m getting is intermittenet like it’s in a feedback loop and shutting itself off
Hi @pmj
It could be a couple of things, maybe the USB audio is not working for you (bug) or there is a feedback loop in the host that is causing this. Without listening to the audio or seeing a wave it is hard to tell.
If you try that patch that I posted above which should turn the Ksoloti into a simple audio interface does it work as expected?
The patch you posted does allow me to send audio from the computer to the Kosolti but it’ll play for a short time and then overload into a high pitched sinewave / feedback. I’ve got a loop somewhere that isn’t immediately obvious I think
Sounds like something is very wrong!
What do you see in the Ksoloti log window?
@pmj, I just tested 1.1, the USB audio is broken in it. Will get back to you when we get to the bottom of it…
@pmj Could you power cycle the ksoloti (which seemed to sort it here) and try again with the original patch and just add a scope, when the audio is wrong could you take a screen grab of the scope and post it here. I would like to see if it was the same thing I was seeing here.
Also Make sure the Mac has not grabbed the ksoloti for it’s system sounds!
So I get the inital sine tones, which then multiply and then it locks up. Then it clears and repeats.
Thanks, so at the beginning of your video the sine is at a high frequency, do you get the correct lower frequency like in my image first and how long for?
Also just as an experiment could you change the oscillators to a different shape, say a saw or square. Then when it all goes wrong, do you see the high frequency sine, or the source oscillator at a higher frequency?
The frequency looks different because it’s a ksope (blue inlet)
So, I can’t replicate this here. Sorry I was confused by the scope earlier, I can see the problem now.
It looks like the sync between the host and the Ksoloti clock is not working, the usb code in the Ksoloti tries to keep the clocks in sync, if it can’t it will reset the usb audio and start again. This might mean a glitch for a few milliseconds not the large amount of time you are seeing there. So something is very wrong.
I tried using reaper as I had the idea that maybe reaper was running at 44.1k and the ksoloti at 48k. I couldn’t get reaper to do this but just to check can you look at the top of the reaper window and check it is at 48K?
Also when it is all going wrong do you see anything like this in the Patcher log window?
connectionFlags.usbActive = 1
Audio input state changed = 0
connectionFlags.usbActive = 0
Audio output state changed = 1
connectionFlags.usbActive = 1
Audio input state changed = 1
connectionFlags.usbActive = 1
What Mac do you have there as well, and OS? Are you using Aggregate Devices for testing?
Reaper is set to 48k, when things start going wrong I see this in the log window:
Audio output state changed = 1
connectionFlags.usbActive = 1
Audio input state changed = 1
connectionFlags.usbActive = 1
Audio output state changed = 0
connectionFlags.usbActive = 1
Audio input state changed = 0
connectionFlags.usbActive = 0
This is a Mac Mini M2 running Sequoia 15.3.2.
I haven’t created an Aggregate device for this so far as it felt like adding a potential clash of devices but can try it… Is the best approach to upload one of the USBAudio help patches as startup and make an Aggregate of the Ksoloti and my regular soundcard?
Thanks.
No the approach at the moment at least is to not use an Aggregate device, I was just checking as I thought that might be the problem.
I think we may have found the problem though, you should not be seeing those state change messages in the log window. These mean that Reaper is actually shutting down the audio interface (when 0) and starting it (when 1). I guess we need to work out why that is occurring.
As a simple test can we remove reaper from the equation.
If you set your Macs system audio output to the ksoloti and then play say some YouTube videos (or some music) with a simple patch like:
Does this work or do you get the same problems, including the log?
Same problems including the log I’m afraid.
Just out of interest I loaded that patch as startup and then tried to use the Ksoloti with my old High Sierra MacBook as a soundcard and it worked fine, was able to listen to music and send audio out without any glitches. Not sure if that says anything about Silicon vs Intel OS or machines?
There’s no weird bespoke routing going on in the background on the Silicon machine that I’ve set up, that’s not to say there isn’t something in the newer system stuff that’s grabbing the audio or creating a loop I don’t know about or typically use I guess?
Good to see it works on the other machine.
I’m trying to get everything running here on a M1/Sequoia machine so I can test it…
Right I have managed to set the Mac m1 up for development for ksoloti and I have a similar issue. With the YouTube test I get 6 seconds of audio and then 5 seconds of silence, then repeat.
I only get the log messages when the YouTube video starts playing though (so I don’t get the 0s) also I don’t get the corruption you see before it goes silent.
As I can replicate it here I can hopefully fix it 
It seems to work on my Mac Mini (M2, Sequoia), but my Gills would crash if I insert an SD card. Gone back to 1.0.12 for the time being, but very excited about these new directions!
