Recherche avancée

Sur d’autres sites (14237)

• Can't compile project with ffmpeg-light

  27 octobre 2016, par wowofbob

  Compilation of any project which uses openFile function from Codec.FFmpeg.Decode fails with error :

  Couldn't match type ‘GHC.IO.Exception.IOException’ with ‘[Char]’
           arising from a functional dependency between:
             constraint ‘mtl-2.2.1:Control.Monad.Error.Class.MonadError
                           String IO’
               arising from a use of ‘openFile’
             instance ‘mtl-2.2.1:Control.Monad.Error.Class.MonadError
                         GHC.IO.Exception.IOException IO’
               at <no location="location" info="info"></no>

  As an example, compilation of this fails :

  openVideoFile :: String -> IO ()
  
  openVideoFile filePath = do
  
  
  
    initFFmpeg
  
  
  
    avFmtCtx <- openFile filePath
  
  
  
    return ()

  I guess the reason is that there is no ready instance of MonadError String IO. But, when I add a dummy instance like this :

  instance MonadError String IO where
  
    throwError _   = undefined
  
    catchError _ _ = undefined

  I’m getting another error :

  Functional dependencies conflict between instance declarations:
 instance MonadError String IO
   -- Defined at src/Video/Play/Base.hs:20:10
 instance [safe] MonadError GHC.IO.Exception.IOException IO
   -- Defined in ‘Control.Monad.Error.Class’

  I don’t know how to force compiler to use MonadError String IO instace here.

  • Should I assure GHC that my instance is better ?
  • Do I have a wrong environment setup ? I’m using ffmpeg-light clone from here and resolver lts-7.2. Host OS is Ubuntu.
  • There is commit which replaces import of Control.Monad.Error.Class by Control.Monad.Except. But, Control.Monad.Error.Class is still used in Codec.FFmpeg.Common. First time I thought it caused a problem. But it turns out that Control.Monad.Except just re-exports MonadError class from Control.Monad.Error.Class. So, it’s not a problem.

• RTCD build is bringing old errors to light

  27 octobre 2010, par Johann

  RTCD build is bringing old errors to light

• armv6 : Accelerate ff_fft_calc for general case (nbits != 4)

  16 juillet 2014, par Ben Avison

  armv6 : Accelerate ff_fft_calc for general case (nbits != 4)
  The previous implementation targeted DTS Coherent Acoustics, which only
  
  requires nbits == 4 (fft16()). This case was (and still is) linked directly
  
  rather than being indirected through ff_fft_calc_vfp(), but now the full
  
  range from radix-4 up to radix-65536 is available. This benefits other codecs
  
  such as AAC and AC3.
  The implementaion is based upon the C version, with each routine larger than
  
  radix-16 calling a hierarchy of smaller FFT functions, then performing a
  
  post-processing pass. This pass benefits a lot from loop unrolling to
  
  counter the long pipelines in the VFP. A relaxed calling standard also
  
  reduces the overhead of the call hierarchy, and avoiding the excessive
  
  inlining performed by GCC probably helps with I-cache utilisation too.
  I benchmarked the result by measuring the number of gperftools samples that
  
  hit anywhere in the AAC decoder (starting from aac_decode_frame()) or
  
  specifically in the FFT routines (fft4() to fft512() and pass()) for the
  
  same sample AAC stream :
                Before          After
  
                Mean   StdDev   Mean   StdDev  Confidence  Change
  
  Audio decode  2245.5 53.1     1599.6 43.8    100.0%      +40.4%
  
  FFT routines  940.6  22.0     348.1  20.8    100.0%      +170.2%
  Signed-off-by : Martin Storsjö <martin@martin.st>
  

  • [DH] libavcodec/arm/fft_init_arm.c
  • [DH] libavcodec/arm/fft_vfp.S