Author Topic: MediaBox (LAV version)  (Read 555 times)

Patrice Terrier

  • Administrator
  • *****
  • Posts: 376
    • zapsolution
MediaBox (LAV version)
« on: August 07, 2017, 02:11:28 pm »
Here is the full C++ VS2017 MediaBox project for test purpose.

It has the same scope of features found in MBox64, except for video zooming that is not working, and of course the video engine that is different.

So far the resource used by the LAV version are much bigger than in the MF's, for a same visual quality.
LAV works in synchronous mode, while MF's is asynchronous

In case of trouble, please try to give a detailed description on how to reproduce the problem, thank you!

The latest changed are in patch.zip that must be used after you have installed MediaBox.zip into a new root folder.

KVideoPlayer_x64.zip is the latest video DLL to use with the project (must be unziped into debug and release folder)

...
« Last Edit: August 17, 2017, 05:33:26 pm by Patrice Terrier »

Patrice Terrier

  • Administrator
  • *****
  • Posts: 376
    • zapsolution
Re: MediaBox (LAV version)
« Reply #1 on: August 07, 2017, 02:45:56 pm »
Here is the result of my own test with the MBox64.mp4 video played from local disk.

       
        Processor   Memory      Disk     Network
MBox64     3%       210 Mb    4.1 Mb/s      0
MediaBox   20%      418 Mb    0             0
KVPlayer   18%      370 Mb    0           


Quote
if run in Debug moder the File Close with this mesage
Das Programm "[6296] MediaBox.exe" wurde mit Code -1073740777 (0xc0000417) beendet.
What about a break point in wWinMain to tell me where it occures.
« Last Edit: August 07, 2017, 02:49:48 pm by Patrice Terrier »

Patrice Terrier

  • Administrator
  • *****
  • Posts: 376
    • zapsolution
Re: MediaBox (LAV version)
« Reply #2 on: August 12, 2017, 09:29:10 pm »
Emil

For the sake of comparison i have be playing both MediaBox and MBox64 synchronized exactly onto the same movie frame.

There is absolutly no visual quality difference.

However see the values reported by the task manager.

This is the reason why i wanted to know if switching KVideoPlayer_x64.dll to the latest DirectX could change anything to reduce the memory foot print, or if there is another reason that explains the big difference between the CPU use by DirectShow and Media Foundation.  ???

Patrice Terrier

  • Administrator
  • *****
  • Posts: 376
    • zapsolution
Re: MediaBox (LAV version)
« Reply #3 on: August 13, 2017, 08:46:12 am »
For now DirectShow keeps working on Creators, however for how long that is the question.

"Movie & TV" (MF) because of lower CPU impact works also on ARM Platforms, while DirectShow no.
« Last Edit: August 13, 2017, 08:51:08 am by Patrice Terrier »

Emil Weiss

  • Full Member
  • ***
  • Posts: 139
Re: MediaBox (LAV version)
« Reply #4 on: August 17, 2017, 06:03:42 pm »
Quote
I have updated the first post of this thread with a new MediaBox.zip (with the full complete project)
ok.. thanks

if your want use zoom.. you can do it self.

use
Code: [Select]
BOOL KVIDEOPLAYERDEF(KVideo_GetViewSize)(int OUT *Width, int OUT *Height);or Play with

Code: [Select]
gP.aMediaProperty.Video_Width
gP.aMediaProperty.Video_Height

greets
« Last Edit: August 17, 2017, 06:17:56 pm by Emil Weiss »

Patrice Terrier

  • Administrator
  • *****
  • Posts: 376
    • zapsolution
Re: MediaBox (LAV version)
« Reply #5 on: August 18, 2017, 10:05:40 am »
Code: [Select]
if your want use zoom.. you can do it self.
I can't see how that could work, without a dedicated function, because the size of the gP.hVideo window must be kept the same.
And KVideo_GetMediaProperty is read only, thus no way to change the settings of video_Width and Video_Height.

« Last Edit: August 18, 2017, 10:49:42 am by Patrice Terrier »