Hi guys - trying to help my buddy get connected using a Avid M-Audio Fast Track Duo into his Windows 10 laptop (brand new). He's not good with computers so I remoted in and tried installing the Avid drivers but Jamulus didn't like those drivers so uninstalled them and installed Asio4All drivers and that allowed him to get into Jamulus and then connect with our private server (which I host and is working). I can see him connected to the server and in my Jamulus app. On his computer I can see the input levels going up and down as he played guitar but no sound in his headphones and no sound on my end either nor do I see any level movement on his fader. Seems like his guitar sound is getting to the Jamulus client but not getting out to the server (I guess). What firewall ports need to be open for him on his laptop and could that be the problem?
His internet connection kind of sucks too. SpeedTest was showing 3Mb down and 0.6Mb up.
Update: I checked at my Central Server provider homepage and there was indeed some short outage of the Central Server because the Linux kernel was replaced and a reboot was required. The outage should have been for just a short period of time last night.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Kevin - the overall delay and ping time is very high according to your screenshot. I'm afraid that even if you could hear him, you wouldn't have much of a jam :-(
What happens if you both connect to a public server? Do you still have the same issues? BTW his bandwidth might just about be OK as long as he doesn't do anything else on his network while playing (so no Netflix, etc.)
If so, then it might be a firewall issue at his end. Does he have one running on his machine (this includes anti-virus)? If so just turn it off completely for a test at least.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Gilgongo, yea I realize the jam would be terrible with this much latency but I'm looking to get basic connectivity and sound going then dial in the performance after (I'm an IT guy). That said, good to know about his available bandwidth and funny, his wife and kids where watching Netflix when we were testing but I told them I would remote in tomorrow to test when they aren't using it. Everyone is on Netflix these days! lol
You read my mind about the firewall, may as well disable and eliminate that as the problem. I did have a quick look at it lastnight and I didn't see any rules in there for Jamulus so I suspect when he was prompted to allow access he probably denied it. Anyway, I'll completely disable it and see what happens. If it works, I'll re-enable and open the Jamulus UDP ports I see configured in my Windows firewall. Same with a/v. All good tips - thanks!
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just tried it again and it didn't work. The firewall already had the Jamulus rules in there (exact same rules as I have so I didn't bother disabling the f/w). This is an older audio interface and I suspect it is a driver issue. One thing I did notice is a constart sort of tapping noise on my end when he is connected to the server. I think it may be his sound trying to come through but is so buffered it comes in extremely chopped and only for a split second then cuts out and repeats. The rate is like one mississippi two mississippi etc (sorry best timing description off the top of my head). I'll have to google around to see what drivers people are using for the the Avid M-Audio Fast Track Duo. I don't thing the Asio4All is cutting it.
Should mention I did another speed test, It was slightly better at 4.2Mb down and 0.5Mb up. I think his internet package is only 6Mb down and 1Mb up anyway so this is to be expected, especially these days.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just bought an old M-Audio Fastrack Pro interface in hopes of giving it to a freind so we could jam on Jamulus. Im running Windows 10 and these drivers are pretty old but supposedly work on Windows 10. Uploading the driver was only part of the solutiopn, I had to update the firmware as well. That appeares to have solved the problem.
I know you're an IT guy, but, for the benefit of those who might later read this, to update the firmware, I had to have the M-Audio device plugged into the PC while running the updater sofware. There were some onscreen instruction to turn the deivce off for several seconds, then on again. I think I even had to use a Windows 10 Toubleshooter, but it got it going.
I then tested the interface by running Jamulus in client mode. I was able to listen but didn't try anything else.
In my general IT experience, I rarely know what I did to screw things up, and - almost as bad, I can't figure out what I did to fix it!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Kevin: I fully tested my newly updated firmware on my M-Audio Fast Track Pro on Jamulus and it appears to work fine. WhIt defaults to 48000 (it would not operte under the old firmware which was limited to 44100. There is a A/B push switch whcih need to be left in the out position. Good luck. Hope this helps.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi guys - trying to help my buddy get connected using a Avid M-Audio Fast Track Duo into his Windows 10 laptop (brand new). He's not good with computers so I remoted in and tried installing the Avid drivers but Jamulus didn't like those drivers so uninstalled them and installed Asio4All drivers and that allowed him to get into Jamulus and then connect with our private server (which I host and is working). I can see him connected to the server and in my Jamulus app. On his computer I can see the input levels going up and down as he played guitar but no sound in his headphones and no sound on my end either nor do I see any level movement on his fader. Seems like his guitar sound is getting to the Jamulus client but not getting out to the server (I guess). What firewall ports need to be open for him on his laptop and could that be the problem?
His internet connection kind of sucks too. SpeedTest was showing 3Mb down and 0.6Mb up.
See attached screen shot of settings.
i think the problem is because right now the centra server is down
I can see the server list and the Central Server works just fine.
Update: I checked at my Central Server provider homepage and there was indeed some short outage of the Central Server because the Linux kernel was replaced and a reboot was required. The outage should have been for just a short period of time last night.
Hi Kevin - the overall delay and ping time is very high according to your screenshot. I'm afraid that even if you could hear him, you wouldn't have much of a jam :-(
What happens if you both connect to a public server? Do you still have the same issues? BTW his bandwidth might just about be OK as long as he doesn't do anything else on his network while playing (so no Netflix, etc.)
If so, then it might be a firewall issue at his end. Does he have one running on his machine (this includes anti-virus)? If so just turn it off completely for a test at least.
Hi guys and thanks for the feedback.
Gilgongo, yea I realize the jam would be terrible with this much latency but I'm looking to get basic connectivity and sound going then dial in the performance after (I'm an IT guy). That said, good to know about his available bandwidth and funny, his wife and kids where watching Netflix when we were testing but I told them I would remote in tomorrow to test when they aren't using it. Everyone is on Netflix these days! lol
You read my mind about the firewall, may as well disable and eliminate that as the problem. I did have a quick look at it lastnight and I didn't see any rules in there for Jamulus so I suspect when he was prompted to allow access he probably denied it. Anyway, I'll completely disable it and see what happens. If it works, I'll re-enable and open the Jamulus UDP ports I see configured in my Windows firewall. Same with a/v. All good tips - thanks!
Just tried it again and it didn't work. The firewall already had the Jamulus rules in there (exact same rules as I have so I didn't bother disabling the f/w). This is an older audio interface and I suspect it is a driver issue. One thing I did notice is a constart sort of tapping noise on my end when he is connected to the server. I think it may be his sound trying to come through but is so buffered it comes in extremely chopped and only for a split second then cuts out and repeats. The rate is like one mississippi two mississippi etc (sorry best timing description off the top of my head). I'll have to google around to see what drivers people are using for the the Avid M-Audio Fast Track Duo. I don't thing the Asio4All is cutting it.
Should mention I did another speed test, It was slightly better at 4.2Mb down and 0.5Mb up. I think his internet package is only 6Mb down and 1Mb up anyway so this is to be expected, especially these days.
I just bought an old M-Audio Fastrack Pro interface in hopes of giving it to a freind so we could jam on Jamulus. Im running Windows 10 and these drivers are pretty old but supposedly work on Windows 10. Uploading the driver was only part of the solutiopn, I had to update the firmware as well. That appeares to have solved the problem.
I know you're an IT guy, but, for the benefit of those who might later read this, to update the firmware, I had to have the M-Audio device plugged into the PC while running the updater sofware. There were some onscreen instruction to turn the deivce off for several seconds, then on again. I think I even had to use a Windows 10 Toubleshooter, but it got it going.
I then tested the interface by running Jamulus in client mode. I was able to listen but didn't try anything else.
In my general IT experience, I rarely know what I did to screw things up, and - almost as bad, I can't figure out what I did to fix it!
where did you find the firmware for the fasttrack? i cant find it..
Kevin: I fully tested my newly updated firmware on my M-Audio Fast Track Pro on Jamulus and it appears to work fine. WhIt defaults to 48000 (it would not operte under the old firmware which was limited to 44100. There is a A/B push switch whcih need to be left in the out position. Good luck. Hope this helps.