Question / Help Need help with Audio desync and OBS Test Build

[CrazyLink1]

Okay so, I have an Avermedia Live Gaming Portable and based on Google searches, I see that for years now, people have been talking about a need of a solution for the audio/video desync.

There was one thread I came across where people used a test build that solved the issue. It was Test Build 0.60, and the thread is here:

https://obsproject.com/forum/threads/avermedia-live-gamer-portable-audio-drift.9137/

That said, I would imagine the current available build, 0.656b, is the official live version of this test build? Or at least I assume. I also assume that the builds that have come out of late would have any fixes that that test build has, but apparently I am wrong because the issue is still happening.

My question is really simple. How to I get the test build? I downloaded the file, and I extracted, but I dont know how to actually install or use said test build. Do I have to extract anywhere specific? The thread stated that you extract and just open OBS like normal, but if I do that, it shows its the 0,656b build, not the 0.60 test build.

Any help?

And heck, while I am at it, has there been any solution to this issue after all these years? I use my Avermedia LGP to use my Laptop as a streaming PC, playing my games on my desktop. I have audio connected via 3.5mm.


Thanks in Advance.

 

[Harold]

The "Test build 0.60" was a special test build made TWO YEARS AGO for the specific problem back then.

Any actual fixes done to OBS in regards to that problem are already included in 0.656.

 

[CrazyLink1]

The "Test build 0.60" was a special test build made TWO YEARS AGO for the specific problem back then.

Any actual fixes done to OBS in regards to that problem are already included in 0.656.

Thats what I figured but I am curious why 0.656 still has the issue when Test Build 0.60 apparently fixed it for a number of people that tried it out.

 

[Harold]

The most recent post in that thread is from june of 2014. I wouldn't recommend following it and would instead recommend following normal troubleshooting procedures including posting an OBS log with the current version.