Edius didn't need anything fancy until now. Playing back H.264/H.265-footage on the timeline has been greatly improved as well as enabling to smoothly edit 4K-material even with a less then optimized office PC. Not only does Quick Sync speed up the encoding of H.264/H.265 exporting files up to 10 times faster. just trying to get a little more out of it. EDIUS X is optimized for Intel Quick Sync like no other NLE. My question is: Is there a Quick Sync capable graphics card that will work in this computer? I do have a decent laptop that is capable of taking advantage of Quick Sync (H.264 encoding is about 5 times faster than RT), but it would be nice to have the workstation doing the same. Some of my clients started asking for MPEG4/H.264, and where Edius is 4-5 times faster than RT with MPEG2, it takes RT or a bit more for H.264. I am transcoding that material (in real-time) to H.264-MP. My source content is encoded using HEVC, 640x360, 30f/s 550kb/s, packaged in MPG2TS/UDP. Most of my deliverables are MPEG2, and I edit on Edius Pro 8. Im trying to determine how many QuickSync H264 encodes I can simultaneously run (at real-time) on a 3rd-gen i7 2.1GHz w/ 16GB of RAM. It served me well and it's still working perfectly fine. I built this machine myself back in 2010. With the diversity nowadays, one needs to be a computer engineer to keep up. If your CPU does not appear in the list, then you do not have Intel Quick Sync available with your computer's processor. In a web browser, navigate to this list and find your CPU model (Tip: Use the CTRL+F/CMD+F search function in your browser and type in the model ID). Ive heard that Quick Sync is really the best of both worlds, so I definitely want that. Your CPU model will be displayed underneath. Well, the NVenc gives poor quality, and the x264 decreases my FPS way too much for my liking. WorkSurface->Info.CropW, workSurface->Info.I was able to follow the development of computers. The 2600k, Quicksync notwithstanding, is a great CPU for both gaming and streaming, even today. MSG(cerr Data.Y, workSurface->Data.UV, workSurface->Data.Pitch, The function named cvtBGRtoTwoPlaneYUV() does the conversion from BGR->YUV.(TAKES 200 MS ) bool VideoWriter_IntelMFX::write_one(cv::InputArray bgr) Okay, so this is the write_one() function from OpenCV, it converts the frame to YUV and encodes it.This function is callled in every frame. I was thinking the encoding would take time, but apparently conversion part takes a lot more, which is odd. The encoding function takes about 0.045(~20FPS) seconds. The conversion function BGR->YUV takes about 0.20 seconds(~5 FPS). Quick Sync is a hardware implemented GPU-feature offered by many of Intel’s current Core i9, i7, Core i5 and even Core i3 processors. That computer only has intel integrated GPU.(so, Using FFMPEG with NVIDIA GPU is not possible.) Also, in my case, there is one dedicated computer and camera for this software. Intel Quick Sync Video1 uses the dedicated media processing capabilities of Intel Graphics Technology to decode and encode fast, enabling the processor to. However, The problem is, I want to get 10 FPS from my video.(I mean the video eventually becomes 10FPS, but while encoding process, it doesn't get all the frames.(I am getting in between 3-5 FPS).When I dig the code I have realized that, the encoding function is okay but the function that converts BGR->YUV is pretty slow. I want to develop one software that takes frames from 4K camera and encodes it simultaneously.Īnd right-now I can get the frames and compress it to a.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |