Développeurs

Decoding performance issue

Hi guys,

I am working on Hardware decoding, the decoder gets initialized fine with MFX_IMPL_HARDWARE2|MFX_IMPL_VIA_D3D9 and i am using vpp for the colourspace conversion NV12->RGB4. My system configuration is i7-2600k and I am using 2013 R2 SDK. Everything is working fine except for the CPU usage which is about 32% throughout the decoding process and i am decoding @25fps 1920*1080.

Here is how i am setting up the VPP structure

Diagnostic for incompatible arguments to MOVE_ALLOC

MOVE_ALLOC requires that `to` be type compatible with `from`.  Could the compiler please diagnose when this requirement is not met.

MODULE m
  IMPLICIT NONE
  TYPE :: NotMyParent
  END TYPE NotMyParent
  TYPE :: NotAnExtension
  END TYPE NotAnExtension
CONTAINS
  SUBROUTINE proc
    CLASS(NotMyParent), ALLOCATABLE :: to
    TYPE(NotAnExtension), ALLOCATABLE :: from
    !****
    CALL MOVE_ALLOC(from, to)
  END SUBROUTINE proc
END MODULE m

 

I have several problems with intel MSDK

1. I am getting permanently MFX_WRN_VIDEO_PARAM_CHANGED on some live streams.

2. I am getting permanently MFX_WRN_DEVICE_BUSY, which stops repeating only after decode_reset.

3. sometimes program freezes on mfxclose.

4. sometimes libmfxhw64.so crashes with segfault.

I have collected debug informations, stream files and soon, but I couldn't find a way how to give them to Intel to analyze it.

 

here is just one sample output from gdb.

 

fatal error LNK1104 cannot open file "\Debug\...EXE"

Hi

I always got the same error when I rebuilding the project in in fortran complier on Visual Studio. And It seems that the .EXE in debug folder couldn't be delected when I rebuild the project, thus the error occurs.

I using Microsoft Visual Studio 2008 Tools for Office, and Intel(R) Visual Fortran Composer XE 2013 Update 3 Integration for Microsoft Visual Studio* 2008, 13.0.3624.2008, Copyright (C) 2002-2013 Intel Corporation.

thanks

Youwei

What's status code - 2000 meaning for MFXVideoCORE_SyncOperation

I'm using intel SDK to decode mpeg2 video, and faced a strange issue with status code -2000

In my code,  MFXVideoDECODE_DecodeFrameAsync  always returns 0

 but MFXVideoCORE_SyncOperation  returns different in different hardware settings....

My notebook has 2 graphic card, intel hd and  NVidia GT730M.  And I have tested libmfxhw64.dll version 3.x and 4.x. Following is the test result:

1. Intel HD with GT730M, using libmfxhw64.dll 4.x, MFXVideoCORE_SyncOperation does not work, it returns -2000

video memory lock, memory type

I've got a very slow user plugin when using video memory. Is the memory address returned from

sts = m_pAlloc->Lock(m_pAlloc->pthis, frame->Data.MemId, &frame->Data);

system memory (as in, copy from video to system on lock, copy back on unlock), or is it simply video memory being mapped to user space?

Video memory is taking 100+ ms to perform the plugin Process (between the locks/unlocks, and the lock/unlock contribute no measureable time).

Forrtl: List Directed I/O Syntax Error

Hello,

               After successfully compiling this code - https://software.intel.com/en-us/comment/1798317#comment-1798317 (thanks to Tim Prince) when I run this I get the error below. I know there is nothing with the data. So I am enclosing the f90 file and maybe somebody can help me what is the error with it.

Regards,

Ashwin.

HAXM memory setting not updated

I got an intel processor supporting virtualization technology and is already enabled in BIOS.

I run the HAXM and set memory limit manually and installed successfully.

But the saved memory limit is always the default value 1024 MB.

I run the set up again and change it to even lower limit but it is not saved either.

Anyone got the same issue before??

Thank you!

Must nullify a pointer before check associated status in IVF.

hi,

I do known that pointers should be nullified by null() or nullify or associated to variable before checking associated status in deed.

Now I have a very large project in Lahey fortran, all pointers are not nullified before checking associated status, but it have worked well for decades of years. 

S’abonner à Développeurs