Bug Report My rate goes up and down to 0 kb / s

[Mario345]

The version of OBS makes no difference if you're having connection issues.

You can't say it DOESN'T make a difference if it clearly is making a difference. The issue is NOT our connections, it's the version of OBS. Even if we disable our Anti-Virus altogether, the issue is still there. Yet when we try OBS 18.0.2, things are fine. The new build is fine too, but only after overwriting the ZIP install files over the old one, instead of running the installer.exe itself.

 

[PrinceVinc]

for the x time it is NOT a connection Issue.
Here I stream with x264 Encoder and the same bitrate as with the AMD Encoder and there is no "connection issue" whatsoever.

It only exclusively happens with the AMD Encoder on any OBS Version beyond 19.0.2

Btw I used the Portable Version for the Tests 20.0.1 so the Zip file.

So do I need the Installer and overwrite it with the 20.0.1 Zip for it to work with AMD Encoder?
Shouldn't be the Zip File enough?

 

[Osiris]

Your problem might not be a connection issue no, but the TS' issue is definitely a connection issue.

So when you are using the AMD encoder on 19.0.1 you don't get dropped frames? And when using 20.0.1 you do?
Perhaps you can try to get the enc-amf.dll from 19.0.1 and copy it to the corresponding folder for 20.0.1? And see if that version of the enoder also exhibits this issue.

 

[PrinceVinc]

@Osiris YES that does it! The Files have a different size even. The "old" one is bigger, than the new one!
I used the Version 19.0.2 AMD Encoder btw not the 19.0.1

 

[Osiris]

Size doesn't really mean anything, but this might be a temporary workaround, I myself can't test anything with the AMD encoder since I don't have a AMD GPU.

So with the older version of the plugin copied to 20.0.1, the dropped frames stop?
On a sidenote, you had the latest drivers from AMD the entire time you tested this?

 

[PrinceVinc]

How can I forward this to the Dev's? I mean I can't be the only one who streams with the AMD Encoder for the sake of Recording with x264 at the same time. @Osiris

But thank you so much >.<!

 

[Osiris]

Just to be sure, when you put the 20.0.1 enc-amf.dll back the dropped frames start again?

 

[PrinceVinc]

Yes I tested it with a clean Zip Version and by copying it back into the folder.

The kb/s reverted back to trash. So should I post this in the Dev forum to forward this? @Osiris

No, first I had old AMD Driver and the Problem.

Than I had the same Problem even with the newest Driver.

And those tests right now are with the newest Driver 17.7.2

 

[Osiris]

Check this out: https://github.com/Xaymar/obs-studio_amf-encoder-plugin/wiki/Guide:-Troubleshooting
The plugin is not maintained by Jim, so you probably want to report it directly to the plugin's dev.

 

[Mario345]

Your problem might not be a connection issue no, but the TS' issue is definitely a connection issue.

So when you are using the AMD encoder on 19.0.1 you don't get dropped frames? And when using 20.0.1 you do?
Perhaps you can try to get the enc-amf.dll from 19.0.1 and copy it to the corresponding folder for 20.0.1? And see if that version of the enoder also exhibits this issue.

even though the ts issue isnt a connection issue considering this issue only happened recently with the recent releases

 

[Osiris]

the TS did not say it happened after he updated.

 

[Mario345]

the TS did not say it happened after he updated.

well you seem to be a mind reader can you tell me why other versions ie 18.0 to 19.0.1 are fine but 0.2 for 19 and the new 20.0,1 are bad with encoding? he may have not said he updated but you got to remember a page that says update is always shown before open is fully open so chances are they updated,
Also the Thread Starter hasn't ever replied.

 

[Osiris]

Those versions are not bad with encoding, they work perfectly fine here.
And you should probably stop posting in other people's threads, if you have issues with OBS create your own topic and post logs.

 

[Mario345]

Those versions are not bad with encoding, they work perfectly fine here.
And you should probably stop posting in other people's threads, if you have issues with OBS create your own topic and post logs.

Well I have to post on threads like these so people actually get help, and like I said, the INSTALLER seems to have something wrong with it. When I revert to 18.0.2, then update using just the zip files, I don't get any dropped frames. I seriously suggest you take a look at it.

 

[Fenrir]

Which zip file are you using to update? The full or small zip?

EDIT: Can you also provide a log from OBS that was updated with the .zip that shows no dropped frames? I'm noticing a small inconsistency in the files, I'd like to verify if they're the same versions.

 

[Mario345]

Which zip file are you using to update? The full or small zip?

EDIT: Can you also provide a log from OBS that was updated with the .zip that shows no dropped frames? I'm noticing a small inconsistency in the files, I'd like to verify if they're the same versions.

im using the full .zip version and here is the log file

 

[Fenrir]

im using the full .zip version and here is the log file

Thanks, everything looks good there, outside some weird NVENC settings.

Can you grab a log from the installer version that shows the dropped frames? Apologies if you posted it somewhere else already (if you did, please relink it), I didn't see it in this thread though.

 

[Mario345]

Thanks, everything looks good there, outside some weird NVENC settings.

Can you grab a log from the installer version that shows the dropped frames? Apologies if you posted it somewhere else already (if you did, please relink it), I didn't see it in this thread though.

i am running with the same settings with the installer version, heres the results in my second test

 

[Fenrir]

So far, the major difference I can see is that on the .zip test log you did, you're capturing an emulator (which doesn't use the network at all) and on the full install log, you're capturing PUBG (which definitely uses network resources).

I apologize for making you do all this extra work, but can you test the .zip version again with PUBG running? Or might be easier to test the installer without PUBG running.

 

[Mario345]

So far, the major difference I can see is that on the .zip test log you did, you're capturing an emulator (which doesn't use the network at all) and on the full install log, you're capturing PUBG (which definitely uses network resources).

I apologize for making you do all this extra work, but can you test the .zip version again with PUBG running? Or might be easier to test the installer without PUBG running.

Here you go, installer version with emulator, same settings