Recherche avancée

Sur d’autres sites (2648)

• IOS compile FFMpeg xcode 4.3 IOS5.1 Warning

  18 mars 2013, par user1589842

  Ld /Users/eric/Library/Developer/Xcode/DerivedData/iFrameExtractor-gqrehoaizgqylqfdiyfeasbifzbc/Build/Products/Debug-iphoneos/iFrameExtractor.app/iFrameExtractor normal armv7
  
      cd /Users/eric/Documents/iFrameExtractor
  
      setenv IPHONEOS_DEPLOYMENT_TARGET 5.1
  
      setenv PATH "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin"
  
      /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/llvm-gcc-4.2 -arch armv7 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS5.1.sdk -L/Users/eric/Library/Developer/Xcode/DerivedData/iFrameExtractor-gqrehoaizgqylqfdiyfeasbifzbc/Build/Products/Debug-iphoneos -L/Users/eric/Documents/iFrameExtractor/ffmpeg -L/Users/eric/Documents/iFrameExtractor/ffmpeg/libavcodec -L/Users/eric/Documents/iFrameExtractor/ffmpeg/libavdevice -L/Users/eric/Documents/iFrameExtractor/ffmpeg/libavformat -L/Users/eric/Documents/iFrameExtractor/ffmpeg/libavutil -L/Users/eric/Documents/iFrameExtractor/ffmpeg/libswscale -L/Users/eric/Documents/iFrameExtractor/ffmpeg/universal -L/Users/eric/Documents/iFrameExtractor/ffmpeg/lib -F/Users/eric/Library/Developer/Xcode/DerivedData/iFrameExtractor-gqrehoaizgqylqfdiyfeasbifzbc/Build/Products/Debug-iphoneos -filelist /Users/eric/Library/Developer/Xcode/DerivedData/iFrameExtractor-gqrehoaizgqylqfdiyfeasbifzbc/Build/Intermediates/iFrameExtractor.build/Debug-iphoneos/iFrameExtractor.build/Objects-normal/armv7/iFrameExtractor.LinkFileList -dead_strip -miphoneos-version-min=5.1 -lbz2.1.0 -framework Foundation -lavformat -framework CoreGraphics -framework UIKit -lavcodec -lavdevice -lavutil -lswscale -lz -o /Users/eric/Library/Developer/Xcode/DerivedData/iFrameExtractor-gqrehoaizgqylqfdiyfeasbifzbc/Build/Products/Debug-iphoneos/iFrameExtractor.app/iFrameExtractor
  
  
  
  ld: warning: ARM function not 4-byte aligned: ff_j_rev_dct_arm from /Users/eric/Documents/iFrameExtractor/ffmpeg/lib/libavcodec.a(jrevdct_arm.o)
  
  ld: warning: ARM function not 4-byte aligned: _ff_j_rev_dct_arm from /Users/eric/Documents/iFrameExtractor/ffmpeg/lib/libavcodec.a(jrevdct_arm.o)
  
  ld: warning: ARM function not 4-byte aligned: row_loop from /Users/eric/Documents/iFrameExtractor/ffmpeg/lib/libavcodec.a(jrevdct_arm.o)
  
  ld: warning: ARM function not 4-byte aligned: empty_row from /Users/eric/Documents/iFrameExtractor/ffmpeg/lib/libavcodec.a(jrevdct_arm.o)
  
  ld: warning: ARM function not 4-byte aligned: end_of_row_loop from /Users/eric/Documents/iFrameExtractor/ffmpeg/lib/libavcodec.a(jrevdct_arm.o)
  
  ld: warning: ARM function not 4-byte aligned: start_column_loop from /Users/eric/Documents/iFrameExtractor/ffmpeg/lib/libavcodec.a(jrevdct_arm.o)

  ..............................................................................................
  ...........................................
  Showing first 200 warnings only

• How to use sexagesimal syntax in arguments of FFmpeg or if impossible how to convert it in Windows CMD shell

  6 décembre 2020, par Link-akro

  Question updated 2020-12-06 to enlarge the scope without discarding the prior answer which applies to both prior and larger cases.

  


  I had trouble to provide a sexagesimal time (HH:MM:SS.mm) to a filter option that was not an expression. For instance trim filter.
It happens there is an escaping rule i did not know yet when i first asked, and was addressed in the first comment by @Gyan.

  


  The problem is universal, but the solution may depend on the shell if we go the scripting route... and i am currently stuck with Windows's CMD.exe.

  


  For instance the following skips one minute and 4 tenths of seconds in all streams as accurately as it can seek each, then invokes the trim filter to keep the segment between one and two minutes of the remaining duration, and do so with two different syntaxes. This example happens to be compatible with both CMD and BASH shells so no escaping hell.

  


  ffmpeg -ss "1:00.4" -i INPUT -vf "trim=start='1\:00':end='120'" OUTPUT


  


  Then how do we achieve the same in the expressions within the filters ?
If we cannot avoid using the scripting of the shell, i am looking for a Windows CMD solution.
I had posted one answer with a piece of script to convert a textual sexagesimal time to a textual decimal fractional time in seconds, which was not useful for the original case, but may apply to more generic cases and in particular to the expressions.

  


  Example of failed attempt with one expression in the select filter.

  


  ffmpeg -ss "1:00.4" -i INPUT -vf "select='between(t,1\:00',120)'" OUTPUT


  


  The sexagesimal notation seems to not be supported by ffmpeg filter expressions as i found no reference of it in the documentation nor in SO/web.

  


  I browsed through the list of functions defined in ffmpeg expression library but did not find any way to parse the sexagesimal input there yet, nor any way to use text in its semantics.

  


  However i found some unrelated example that hard-coded some arithmetical expression to provide the numerical decimal amount of seconds equivalent to what was intended, such as 2*60+2 to mean 2:02.

  


  The polynome used above to compute seconds may use preprocessing of shell variable, whichever shell it is, but we need to parse the components of HH:MM:SS.mm to put them in those variable first. You know, using bash $var or cmd %var%/%~1 styles. Otherwise we may compute the polynome completely in the shell instead of the expression but it is so much trouble for little gain.

  


  So while CMD still exists like an undead and becomes really dead , and while i do not have the opportunity yet to replace it, i wish for an answer that either :

  


  

  • does not need the shell/script at all, OR

  


  • provide a solution in Windows CMD, although relying on it as little as possible.

  


  


  Reminder and clarification, the use case assumes that we are given a textual sexagesimal time as input and intend to use it in an expression of ffmpeg filter with as little shell dependency as possible or otherwise satisfy Windows CMD.

  


• Developers and vendors : Want a Matomo Hoodie ? Add a tag to the Matomo Open Source Tag Manager and this could be yours !

  7 juin 2018, par Matomo Core Team — Community, Development

  The Free Open Source Tag Manager is now available as a public beta on the Matomo Marketplace. Don’t know what a Tag Manager is ? Learn more here. In Short : It lets you easily manage all your third party JavaScript and HTML snippets (analytics, ads, social media, remarketing, affiliates, etc) through a single interface.

  Over the last few months we have worked on building the core for the Matomo Tag Manager which comes with a great set of features and a large set of pre-configured triggers and variables. However, we currently lack tags.

  This is where we need your help ! Together we can build a complete and industry leading open source tag manager.

  Tag examples include Google AdWords Conversion Tracking, Facebook Buttons, Facebook Pixels, Twitter Universal Website Tags, LinkedIn Insights.

  Are you a developer who is familiar with JavaScript and keen on adding a tag ? Or are you a vendor ? Don’t be shy, we appreciate any tags, even analytics related :) We have documented how to develop a new tag here, which is quite easy and straightforward. You may also need to understand a tiny bit of PHP but you’ll likely be fine even if you don’t (here is an example PHP file and the related JS file).

  As we want to ship the Matomo Tag Manager with as many tags as possible out of the box, we appreciate any new tag additions as a pull request on https://github.com/matomo-org/tag-manager.

  We will send out “Matomo Contributor” stickers that cannot be purchased anywhere for every contributor who contributes a tag within the next 3 months. As for the top 3 contributors… you’ll receive a Matomo hoodie ! Simply send us an email at hello@matomo.org after your tag has been merged. If needed, a draw will decide who gets the hoodies.

  FYI : The Matomo Tag Manager is already prepared to be handled in different contexts and we may possibly generate containers for Android and iOS. If you are keen on building the official Matomo SDKs for any of these mobile platforms, please get in touch.