Recherche avancée

Sur d’autres sites (14530)

• examples : rename demuxing_decoding to demux_decode

  15 janvier 2023, par Stefano Sabatini

  examples : rename demuxing_decoding to demux_decode
  Follow general scheme VERB_OBJECT.
  

  • [DH] configure
  • [DH] doc/examples/Makefile
  • [DH] doc/examples/Makefile.example
  • [DH] doc/examples/demux_decode.c
  • [DH] doc/examples/demuxing_decoding.c

• Missing Library Error in Mac Catalyst when distributed through Testflight

  25 avril 2023, par STerrier

  The iOS version of the app is functioning correctly on TestFlight, and there are no issues when building the Mac Catalyst version of the app from Xcode. However, when distributing the app to TestFlight for Mac Catalyst, the FFmpegkit library fails to load, resulting in a crash. The crash report indicates that the library is missing and cannot be located in the designated file path.

  


  Specifically, the crash report states that the library could not be loaded from "@rpath/ffmpegkit.framework/ffmpegkit". Despite extensive efforts, I have been unable to resolve this issue.

  


  This is error message in the crash report.

  


  Termination Reason : Namespace DYLD, Code 1 Library missing&#xA;Library not loaded : @rpath/ffmpegkit.framework/ffmpegkit&#xA;Referenced from : <9162F8B0-7112-310B-8EDA-59766087927F> /Applications/MyApp.app/Contents/MacOS/MyApp&#xA;Reason : tried : '/System/Library/Frameworks/ffmpegkit.framework/ffmpegkit' (no such file, not in dyld cache), (security policy does not allow @ path expansion)&#xA;(terminated at launch ; ignore backtrace)

  &#xA;

  Are there any alternative solutions to resolve this problem ?

  &#xA;

  UPDATE

  &#xA;

  &#xA;
  • I tried Eugene Dudnyk Solutions but I still received the same error

  &#xA;

  • I checked the package content found in Testflight and the paths are correctly matching the following /System/Library/Frameworks/ffmpegkit.framework/ffmpegkit

  &#xA;

  • I ran the app scheme as release within Xcode and it build and ran fine with no issues

  &#xA;

  • I manually loaded the signing certificates for mac catalyst and still getting the error

  &#xA;

  • Deleted all derived data

  &#xA;

  • Deleted and reinstalled Xcode and also tried previous Xcode versions.

  &#xA;

  • Deleted the project completely

  &#xA;

  &#xA;

  I tried most of the solutions mentioned in this post with no avail.&#xA;iOS app with framework crashed on device, dyld : Library not loaded, Xcode 6 Beta

  &#xA;

• Frame Accurate Seeking in WebM

  11 janvier 2016, par SapphireSun

  I’m trying to do a somewhat tricky thing with WebM. I am trying to encode a stack of 256 biological images as a WebM. The time dimension of motion is very similar to the space dimension of the image stack so the compression ratios are insanely good. However, I am having trouble decoding the movie frames. I know that WebM uses an IPB predictive coding scheme, but I was reading several blog posts and discussion groups from WHATWG from 2011, and they said that frame accurate seeking was working in Chrome at that time.

  When I do video.currentTime = 0, I correctly get this :

  

  However, if I do video.currentTime = 0.34 (for example) I get something that looks like this :

  

  It looks like I’m getting a random poorly predicted frame. Am I just encoding the video wrong ? When I play it normally it looks fine.

  I encoded the video using 256 pngs using ffmpeg compiled with libvpx using the VP8 codec.

  ffmpeg -y -framerate 60 -start_number 0 -pattern_type glob -i '*.png' -qmin 10 -qmax 42 out.webm

  References to the WHATWG and some other info from 2011 :

  WHATWG discusses frame accuracy :

  https://lists.w3.org/Archives/Public/public-whatwg-archive/2011Jan/0372.html

  BBC Tech Director talking about frame accuracy :

  http://www.bbc.co.uk/blogs/bbcinternet/2011/02/frame_accurate_video_in_html5.html