Since I used Jamulus I have been unable to use my interface with any other program afterwards. My computer shows the interface as connected but it's not recieving any sound, including under audio devices and system settings. I have tried restarting the computer, turning the interface on and off, all sorts of disabling/enabling, uninstalling jamulus-- everything short of hard resetting my computer.
I was sucessfully able to get a signal from my mic once, but I don't know how. I also was able to get a signal by restoring the computer to before I installed janalus, but my attempt to re-restore failed.
Is there an easy solution I don't understand? I am running windows 10 and using a phonic helix board 18 as my interface.
When you setup Jamulus, if you have it configured correctly with direct monitoring disabled, you won't hear sound from your interface until you are connected to a server. So, double-check your interface and see if you can re-enable direct monitoring, see if that helps. Are you using ASIO4ALL as the audio driver, or did the interface come with it's own native driver?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The problem isn't that Jamulus isn't working-- it appears to be working fine with both the interface's native driver and asio4all. The problem is that after I use Jamulus I cannot access my interface with OBS, Reaper, etc.. The other software identifies the separate interface channels (they recognize the interface as on), but none of them have any signal. I only get a signal from my mic on Jamulus
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When Jamulus is running, it will lock your interface for exclusive use. That is how ASIO drivers work, they only allow one device at a time to access the hardware. I would try closing Jamulus, then opening another app like Reaper, go into Options and then Devices, and verify that it is using the correct device, then try adding a track and assigning one of the interface inputs to the track, arm the track for recordng, and see if it works.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes I have done all of that with multiple programs-- other software recognizes the interface but doesnt recieve a signal. Restarting and uninstalling Jamulus doens't fix the problem. I would assume its a problem with the driver or ASIO
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I figured out a workaround-- if I uninstall and reinstall the interface itself, everything returns to normal. You can see from the photo I posted
This still doesn't explain why I couldn't get a signal from my interface. Anybody know why this was happening? So I don't have to uninstall and reinstall the device + driver(?) every time I use Jamulus.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Since I used Jamulus I have been unable to use my interface with any other program afterwards. My computer shows the interface as connected but it's not recieving any sound, including under audio devices and system settings. I have tried restarting the computer, turning the interface on and off, all sorts of disabling/enabling, uninstalling jamulus-- everything short of hard resetting my computer.
I was sucessfully able to get a signal from my mic once, but I don't know how. I also was able to get a signal by restoring the computer to before I installed janalus, but my attempt to re-restore failed.
Is there an easy solution I don't understand? I am running windows 10 and using a phonic helix board 18 as my interface.
When you setup Jamulus, if you have it configured correctly with direct monitoring disabled, you won't hear sound from your interface until you are connected to a server. So, double-check your interface and see if you can re-enable direct monitoring, see if that helps. Are you using ASIO4ALL as the audio driver, or did the interface come with it's own native driver?
The problem isn't that Jamulus isn't working-- it appears to be working fine with both the interface's native driver and asio4all. The problem is that after I use Jamulus I cannot access my interface with OBS, Reaper, etc.. The other software identifies the separate interface channels (they recognize the interface as on), but none of them have any signal. I only get a signal from my mic on Jamulus
When Jamulus is running, it will lock your interface for exclusive use. That is how ASIO drivers work, they only allow one device at a time to access the hardware. I would try closing Jamulus, then opening another app like Reaper, go into Options and then Devices, and verify that it is using the correct device, then try adding a track and assigning one of the interface inputs to the track, arm the track for recordng, and see if it works.
Yes I have done all of that with multiple programs-- other software recognizes the interface but doesnt recieve a signal. Restarting and uninstalling Jamulus doens't fix the problem. I would assume its a problem with the driver or ASIO
I figured out a workaround-- if I uninstall and reinstall the interface itself, everything returns to normal. You can see from the photo I posted
This still doesn't explain why I couldn't get a signal from my interface. Anybody know why this was happening? So I don't have to uninstall and reinstall the device + driver(?) every time I use Jamulus.
photo
Last edit: Harrison Thurman 2020-08-01