![]() I tried to convert them to Constant Frame Rate. You need to set 'Read & execute' rights for MediaInfo.dll when deploying. When I started to analyze recorded files, they all recorded in peak framerate mode. Other programs you use M and N where M is the size of BP groups and N is the number of BP groups and I frames per GOP. Simply it was not enough internal resources to handle smooth 50FPS internal data throughput somewhere in VGA - CPU chain. in x264 you use -b or -bframes to specify the number of consecutive b-frames, -I or -keyint to indicate the maximum GOP size. I'm not sure for 100%, but I think that was the problem. ![]() Today from early morning I started to search a problem and found, that only the first slot of PCIe in my motherboard (ASUS X99 WS-E) supports 16 lanes. When the show ended I tried to play recorded files with various players (vMix, VLC, QuickTime, WMP) but result was the same - about half a second faster video, half a second freeze frame. Then I saw strange numbers in the recording area - last digit was probably recorded frames, but first always jumped between 18 and 46 (vMix project 50FPS). Almost at the end of the show I found, that I have some audio glitches on SDI Out (we used SDI as video return to camera mans only). All the time I watched resources in vMix and in Task Manager Performance - CPU about 18% (Xeon 2686 v3), GPU about 58%. I decided to make a record H.264 at 28Mbps in vMix. also en.Example. When setting a size visual variable on a renderer using an. Large Newspapers batch imports are possible by few clicks using smart variables. mediaInfo.image meshSymbol3D modifications. Note that this is batch stuff, no more MediaInfo (please test first with MediaInfo alone). MediaINFO allows you to freely define your own Metadata schemas, and modify. It was simple project: 2 CAM's via SDI, 2 PC's via NDI, also 2 SDI and 2 NDI Outputs. Comment edited again with moving a quote in the initial code to the right place. If I do the same with an x265 in an MP4 container, Mediainfo shows me the correct scan-type and plays correctly as interlaced. If I play the video on the VLC player, it is interlaced. I put my video card to another slot and did not had enough time to test the system. I hadnt really noticed that mediainfo mentioned the frame rate was variable, as I had been blind sided by the original frame rate of 23.976, which I had seen as the 'correct' frame rate. When I create an x264 in an MP4 container with FFMPEG, Mediainfo shows me that the video is progressive. If you believe you have a variable frame rate MP4 recorded directly in vMix, please first confirm it is so using the latest MediaInfoĪnd then email it to us at a hardware encoder is overwriting the vMix internal recording settings, though it seems unlikely. This extremely unlikely, as our previous comments in this thread have confirmed. MP4 recording is 100% VFR (variable frame-rate).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |