Higher latency on one machine than another

[eschewary]

My Unity app with LASP has substantially greater latency on one device than another. The first computer is substantially more powerful, but there's a greater latency between a sound and the reaction in the application. The latency is ~.5 seconds on the newer, more powerful machine, and ~.1 seconds on the older computer; almost imperceptible lag. What might cause this and how can I diagnose it?

[keijiro]

What kind of audio interface are you using?

[eschewary]

On both machines I'm mostly using a Blue Yeti Nano with a standard USB input, is that what you mean? But it also happens with the built-in laptop mics.

The latency will fluctuate over time while the application is open, and there's always more lag right when I launch it. The app on my 2017 laptop will quickly catch up and function properly, while on my 2022 laptop it almost never catches up and has a continuous .5 second delay.

There's also frequently static or distortion, present maybe ~40% of the times I launch the app, but it's frequently strong enough to ruin the recording or activity. Not sure if this is a separate issue or will help diagnose, but it seems to be related because it seems to often co-occur with the lag. If distortion is a known bug I'd be grateful if you can point me to any discussion about it.

[keijiro]

Thanks for the explanation. Does it reproduce with the sample project in this repository?

[eschewary]

I'll test, which scene would be best to test with?

[keijiro]

Either one is okay.

[eschewary]

Ok I've got part of the LASP project in my project files, I'm trying to import the scenes and the rest to test but it's not letting me place them there, I think because it's immutable. I've run into this before when trying to move LASP files around. How can I do this?

[keijiro]

Please clone or download this repository and open it as an existing Unity project.

[eschewary]

Ok, just tried two scenes from a fresh project on the newer PC, it looks like they both have almost no lag, I'll let you know if I find differently. So do you have an idea how I can diagnose why my project scenes are laggy on only one of my computers?

Also I would want to know how I can get around the immutable aspect, or is that disabled because of attribution? I'd like to distribute my project with functional LASP built-in, I would obviously give credit to you and link to this github, but if that's purposefully disallowed I understand.

[keijiro]

So do you have an idea how I can diagnose why my project scenes are laggy on only one of my computers?

Honestly saying, I have no idea because I have zero knowledge about your project. If you can reproduce the issue with a public project (like samples in this repository), I can investigate it.

Also I would want to know how I can get around the immutable aspect, or is that disabled because of attribution?

Packages managed by Unity Package Manager are read-only. You have to import it as a package in the local file system. Please check the Package Manager documentation.

https://docs.unity3d.com/Manual/upm-ui.html

I would obviously give credit to you and link to this github

That's not needed. You can use Lasp without any attribution (it's public domain).

[eschewary]

@keijiro Do you have a way of playing the LASP mic audio simultaneously? I combined LASP with this script here to do that, I think that may be causing problems.

[keijiro]

If your problem in the original post has been resolved, please close this issue and create a new issue for the new topic.

[eschewary]

It has not, I'm troubleshooting the increased latency and distortion, trying to isolate the problem to determine if it's a LASP issue or not. I'm thinking this other real-time audio playback solution might be the source of the problems. So if there's a way to play LASP audio in real-time I can try that and compare the results to what I'm seeing with my current solution. Is there a way to play LASP audio in real-time? If you like I can move this question to the discussion page. Thank you.

…

On Sat, Apr 22, 2023, 9:31 PM Keijiro Takahashi ***@***.***> wrote: If your problem in the original post has been resolved, please close this issue and create a new issue for the new topic. — Reply to this email directly, view it on GitHub <#59 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2NPRMN7O4PNBQFEO6JSGFTXCSWB3ANCNFSM6AAAAAATHL42PQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>