Bug Report Streaming and recording at the same time still doesn't work with type MP4?

CommanderCH

New Member
It has been like that since the beginning. It appears that only .flv is working to stream and record at the same time but I don't want it to be .flv. That filetype is used like nowhere and takes up hours to convert from .flv to .mp4, depending on filequality and length and yes my streams may take up to several hours and therefor also the recordings.

Why do I even want to stream and record at the same time?

Well as you might know, the max bitrate is 3500kbps so quality's gotta suffer from it slightly, whenever there's quick turns and things like that if you're running a 1080p 60fps stream. On a stream, this is kinda common and people usually don't care much. However for a recording (at least for me) this is garbage.

Here's an example: https://www.youtube.com/watch?v=rKYIwVQiBVk
Go to about 1:00 in videotime or so, whenever I turn around, quality is dropping. You might wanna read the green text in the video and put the video to fullscreen of course.

So anyways, I still don't understand how .mp4 is somewhat not a vaild type to stream AND record at the same time. Now at least OBS Studio no longer crashes with the new option "Automatically record when streaming" in the "General" settings but it doesn't record at all, eventhough it shows on the mainscreen, that recording is actually running (I could stop recording but it doesn't do anything than constantly telling me "Stopping Recording..." or actually "topping Recording.." because there isn't enough room for the entire text -> another bug).

Is it still "supposed" to be like that? Or is there actually an issue with my software?

Thank you in advance.
 
That filetype is used like nowhere
Youtube is able to use it fine and most of the post-production software in https://obsproject.com/forum/threads/post-production-tools-you-can-use.34080/ can read it just fine.

and takes up hours to convert from .flv to .mp4
Are you doing multi-day streams? If not, then you're doing something wrong if this conversion takes hours. File -> Remux Recordings exists for a reason.

Saving directly to mp4 is NOT a good idea regardless. If ANYTHING interrupts the finalization of the file, the entire recording is rendered useless.

You're missing your OBS log from the session.

Also, try simple output mode, setting 3500kbit bitrate for the stream, but using the "indistinguishable" quality and software (x264 low cpu use) for recording, saving to FLV.
 
Hello Harold

Thanks for your reply in advance.
Interestingly enough, the .flv files never were accepted by YT earlier for me and Sony Vegas couldn't deal with them either when testing it.
I tried Davinci Resolve when Sony Vegas couldn't deal with a 17h file. Davinci Resolve couldn't even deal with a single file without crashing so I had to go with something completely different but I prefer to stay with Sony Vegas if possible of course.

No I've never done a multi-day stream and it still took hours because the last time I asked for that, people suggested me some free software to convert from FLV to MP4 instead of the remux option. Guess it didn't exist up to then or I don't know.

I had that happen multiple times already with the interruption. ^^ I was used to it with xsplit because for some reason, there it works just all absolutely fine... (if you ask why I didn't stay with xsplit, because xsplit can't deal with the Elgato HD60...)

I hope the upload of the logfile works now.

I already had all these options set. An additional question came up if it's possible for me to possibly decrease the qualitydropping thingy that you see in the video I sent above. For instance a lower Encoder Preset or something. I have quite a solid CPU so, I can definitely change some stuff there. However my GC is a little low so...

I will so try it with .flv again then, thank you for your support. Hope everything goes fine from now on. ^^
 

Attachments

I grabbed that logfile from Help > Log Files > View Current Log

Here's another one with the flv type enabled. Same thing now happens for that just like it did for the mp4 type. Either the stream works, or the recording. Both show as running but when I want to stop them, the one that wasn't running won't stop anyways of course and be stuck on "Stop XXXXXX..."
 

Attachments

And you're using x264 for the encoder for both?

nVidia is prone to breaking nvenc with their driver packs.
 
Alright here we go. I uninstalled the program (and had to kill the hidden task!) and now we're back on track.
Still doesn't work with .flv. ^^ Same thing happens as before.
But I actually think I sent you the wrong file... here we go, there's some errors encoding with h264 apparently...

Also, I did stop the recording, but it gets stuck at "topping Recording.." and somehow doesn't show up in the log since it already crashed inbefore. It did not however crash the program itself, only the recording button is frozen.
 

Attachments

It seems to be having issues while encoding two "files" or whatsoever. Because I get the exact same issue for both situations. If I first start the stream, recording gets the following error:

13:48:44.994: ==== Recording Start ===============================================
13:48:44.994: [ffmpeg muxer: 'simple_file_output'] Writing file 'C:/Users/Livio/Videos/2016-07-12 13-48-44.flv'...
13:48:45.332: [x264 encoder: 'simple_h264_recording'] encode failed
13:48:45.351: Error encoding with encoder 'simple_h264_recording'
13:48:45.351: Called profile end with mismatching name: start("do_encode"[0FBC96A0]) <-> end("receive_video"[0FBC96AC])

If I first start the recording, the streaming gets the following error:

14:03:58.978: ==== Streaming Start ===============================================
14:03:59.621: [x264 encoder: 'streaming_h264'] encode failed
14:03:59.654: Error encoding with encoder 'streaming_h264'
14:03:59.654: Called profile end with mismatching name: start("do_encode"[0F8396A0]) <-> end("receive_video"[0F8396AC])
 
Edit: Try to remove 'Video Capture Device (Elgato)' source from Sources list and try again (just black screen or what ever you have).

This messages says that input video exceed max/min requirements of the encoder in some part.

And I have a question, is it right setting for Elgato device - 60fps, while output is 59.94fps?
 
Last edited:
The Elgato is actually my main required source. Otherwise all of my tracks I play on Guitar Hero will be muted and are uneditable. Additionally, that source wasn't used on the scene where I tried recording and streaming anyways. So it would be weird enough if the Elgato is causing the crash. I can remove it and see what happens. What I'm aware of is, that for whatsoever reason, OBS Studio couldn't deal with the Elgato running on 1080p 60fps and crashed after a while so I set it down to 720p 60fps.

I can change it to 60fps in the Video settings. I can't do much differences to the Elgato though. Only 30fps, 60fps or max. fps (which should be 60fps).
 
It's this problem still, I used to have this when recording but it's gone away for me for quite a few versions ago:

"Called profile end with mismatching name: start("do_encode"[0FE096A0]) <-> end("receive_video"[0FE096AC])"

I'm not sure if @Jim or @Osiris know what causes this, I thought it was actually fixed, vaguely remember seeing a bug resolved but can't remember all the details.

@CommanderCH this is a weird intermittent problem that seems to afflict a few people who are trying to stream and record (or sometimes just record) hopefully someone knows what is causing it in your specific configuration.
 
Set output 5000x5000 and even x264 software encoder should rise:

Called profile end with mismatching name: start("do_encode"[5F4396A0]) <-> end("receive_video"[5F4396AC])

and this is empty black scene. There was thread:Files not exporting
Also, happens at:
Recording No Longer Working?
and for hardware encoders:
AVerMedia hardware encoder support?

So, or Elgato device produces wrong data, or...

By the way, this error makes Stopping Recording... stacked and process running in the task manager (for me).
 
But it doesn't look like the OP has any of that, he seems to be on a pretty standard 1080p video with normal encoder configuration and game capture, doesn't appear to be a capture device at all or am I missing something?
 
No the Elgato doesn't do a difference. I killed the source and the same issue still happened.
I tried switching over to that portable mode. I copied the two folders "scenes" and "profiles" to the desired folder, however the "config" folder didn't exist so I had to create these folders as written there. I then also updated the source path with the "--portable" parameter. Now when I try to start up OBS Studio, I receive two errors:

Screenshot_44.png
Screenshot_45.png
 
I mean, main menu options Profile and Scene Collection. More info there, OBS Studio Help Guide: https://obsproject.com/forum/resour...ware-studio-multiplatform-help-guide-pdf.365/

Look. To make portable OBS Studio, you need follow instructions posted above.
  1. Download .zip file of the Studio latest version.
  2. Unpack it to any folder on your pc, for example to "C:\myportableOBS".
  3. Open "C:\myportableOBS" folder in explorer.
  4. Create new empty file "portable_mode.txt" and save it to the "C:\myportableOBS" , where folders "bin", "data", "obs-plugins" lies.
  5. Navigate to the "C:\myportableOBS\bin\32bit" folder and run "obs32.exe" (you may send shortcut to the desktop). (32 - because you are using win x86 not x64).
Now you have to accept license agreement and use your OBS Studio portable mode.
 
Last edited:
Oh I misunderstood something. Alright got that done now. Gonna run a few tests with the portable OBS Studio now.

I'm actually running 64bit... might that have been the issue? I just always thought a 64bit version doesn't exist. ._.
 
Alright so here we go. With the portable 64bit version of OBS Studio I can stream and do local recordings at the same time (yay). BUT I can no longer see my Elgato capture card. D: The source runs all fine on the portable 32bit version but just gives me a black screen (because it can't find it for some odd reason) on the 64bit version. :/
Do you want me to open up a new discussion for that issue? Because the actual problem here seems to be solved, it's just another one that popped up.
 
Back
Top