Premiere - NVENC codec files from OBS - issues

[Tigersan]

Gameplay files recorded in 2560x1600 mov NVENC coded on OBS Studio 17.0.0, import just fine, but the preview

is green, when you play your sequence it's so slow you cant even edit the clips. When you render 2.5hour sequence

in 1080p renders in about 10 minutes, resulting file is unplayable and is about 60kb instead of 12gb as predicted.

Help I cant update my youtube channel...

😕

[chrisw44157881]

time to pull out the old chestnut.

1.uncheck h.264 acceleration in preferences

2. convert any variable framerate footage with handbrake before importing. you can check the info with mediainfo software.

[John T Smith]

NOTE - do NOT use a Variable Frame Rate capture setting... it does NOT edit well !!!

Free Open Source software http://camstudio.org/

-for best quality use with Lossless Lagarith http://forums.adobe.com/thread/875797

[Tigersan]

NVENC codec doesn't have variable framerate capturing option, only x264 does.

Unchecking h264 acceleration didnt do anything ... 😕

[Sulaco]

I had a similar problem in a previous version of PP; all my Live Gamer Portable MP4 files turned out green in PP. They worked fine in the previous version. I never got an explanation to why this happened, but I came up with a pretty silly way of fixing it. I just renamed all video files from .MP4 to .TS ... and then all files worked again! I don't quite understand how this would help, obviously some sort of container problem. Avermedia's reply was that the problem was in PP, I am inclined to believe them...

I am not sure this will help you of course, but might be worth trying. Can you capture to a different container using OBS?

[excited_Genie16B8]

Your material is unsuitable for editing with professional software.

Use something else.

[Tigersan]

Your response is kinda ridiculous... I'm a professional videographer and a photographer, and I expect my "Professional" program to be able to import clips i film, or capture... it only says alot about the premiere...

To the point tho, i switched to Fraps (not a professional program by any means) and it works just fine now. But anyways Thanks so much for everyone trying to help, I appreciate it very much!

[scrozier]

Yeah one of those codecs that just doesn't play well with premiere yet even though other software can scrub and playback without issue....Seems to cause a massive Spike in GPU usage and instability in premiere overall when using in a timeline. 

[R Neil Haugen]

Playing back long-GOP files is one thing, in a player that only plays the things.

An NLE is an entirely different beast, however ... which needs to be able on the fly to grab bits & pieces of video files, add the effects listed in the metadata for the sequence, and play the result back.

Ain't the same thing at all.

I work for/with/teach pro colorists, who have truly massive hardware ... their computers often are well north of $12,000, with monitors costing well more ... they probably have more in the monitor calibration gear than your entire system costs. Easily.

And if they get much long-GOP delivered to them for a job, nearly all of them immediately transcode it. They don't even load that orginal stuff into the system, as they don't want the mess of trying to play it back under the grade.

[scrozier]

I can see why that would be the case, but just as a test i brought this xml into Resolve and it played it back like it was butter. Premiere can, and should do better. 

[scrozier]

Neil. know that this rant is not pointed at you, it's just I'm tired of hearing the same arguments when the grass is definitely greener on the other side.  

Resolve has hands down better GPU decoding code for H.264/H.265 footage. It rarely slows down. Whereas whenever I try to pull in some H.264 into Premiere it chokes and I get weird things that make me think the GPU code isn't very well implemented(see GPU graph overload above)  Playback and the interface esentially crashes to the point where I have to restart the software.

One of the great promises of Premeire circa CS6/CC2015 marketing was that we would never have to transcode media again becasue the Mercury playback engine would play back anything, even your hereforeto impossible to play Canon 7D footage!

Now we are all having to take a step back and transcode everything again, becasue h.264 causes Premeire to be unstable or non-performant. I would accept this argument if Resolve's playback engine didn't do laps around Premiere's. 

For the record I'm not talking about scrubbing, I expect that to be choppy with Long-Gop or H.264, but premiere should be able to at least playback this media without throwing a fit and crashing the GPU driver. 

Maybe its becasue I don't have an Quick-Step CPU but it shouldn't matter becasue I can take the same media into Resolve and get my job done without having to lap everything through media encoder for every job. 

[R Neil Haugen]

Uff da, that comment about never needing to transcode again!

Yea, that was something I've heard numerous comments about over the years. It did not seem particularly  ... wise, at the time. To me at least. Ahem.

Sure made them look sorta foolish, again, to me.

I know others have posted about much better H.264 in Resolve, but that's one of those things I can't personally seem to experience. Unfortunately.

As performance in these apps, at this time, is so befuddling. Another user with such an identical rig to my desktop it must also be a Puget build was getting total crud in Premiere which sails on mine. Why? Dunno.

Some Resolve users are posting that 18 x is the worst ever, but others are doing fine. I am, thankfully, one where Resolve is doing sweetness.

Except on my 4 year old Acer Triton laptop where it's a total dog. But Pr 24.x runs great on the old thing. Why? Dunno.

Others with old laptops are getting great Resolve play. Why again? Dunno.

[RjL190365]

There is a big catch for hardware acceleration in Resolve:

You absolutely need to purchase the paid Studio edition just to get hardware decoding and encoding. The free version sends all decoding and encoding straight to the CPU (software only), while it's GPU rendering support is much more limited than in the Studio version.