Issue with Beast IPTV recording - Skipping + Doesn't record full show abrupt ending

[russmehta01]

Hello there. I recently installed nextpvr(4.1 latest version) on my windows 10 pc, and am using Beast IPTV. I assume the Nshared.dll is not configured for Beast, so thought'd I'd go about troubleshooting here.

Anyways, I am running into problems when trying to record via Beast. Playing and viewing live tv via tv guide works well, however i am having trouble recording. Setting the recording works, as i am able to select a show to record, however the problem lies in the playback. Whenever i try to play a recorded tv, it skips part of the show, and "blips" all throughout the duration of the video, Or the video fails to completely record and abruptly ends Half way through. Is there any way to get an Updated NShared.dll to fix the aforementioned problems? To ensure a seamless recording, i have done the following :

I have installed Lav Decoders as instructed on your site

I replaced my Nshared.dll with the newest version as discussed on another thread

I disabled auto sleep in windows to prevent nextpvr from shutting down

I have a google drive link, to log files, which is below. Please help asap

https://drive.google.com/file/d/1FEOXJWt...sp=sharing

[sub]

Playing and viewing live tv via tv guide works well, however i am having trouble recording.

Using the same channel? Ultimately a recording and live tv are pretty much identical, and use all the same code. If live tv works fine with a channel, I'd expect recording to as well. (since live tv is effectively just a recording that is being played)

[russmehta01]

Using the same channel? Ultimately a recording and live tv are pretty much identical, and use all the same code. If live tv works fine with a channel, I'd expect recording to as well. (since live tv is effectively just a recording that is being played)

Hey, just tested again, looks like the same problem exists via live tv? Any fix. THe IPTV provider is solid via Raw m3u. Any ideas sub?

[sub]

Your logs are full of all sorts of stuff, so it's hard to see where exactly the problem is happening.

Can you post the logs immediately after the problem occurs, so I know where to look in the logs?