Sur d’autres sites (11862)

• Unable to 'make' android ndk project - build fails : [build-openh264-x86] Error 2

  18 décembre 2015, par NoobNinja

  I’ve attempted these two fixes I’ve found while researching the issue :

  android update project  --23 --/Users/ajswann/Downloads/android-sdk-macosx 
  
  
  
  make OS=android NDKROOT=/Users/ajswann/Downloads/android-sdk-macosx TARGET=android-19 ARCH=x86 clean

  ...however neither seems to resolve the issue.

  Any input/suggestions are appreciated.

  P.S.

  I’m running OSX - could this be an issue with attempting to run an x86 architecture on a 64 bit machine ?

  Error Message :

  chris-mini-mac:linphone-android ajswann$ sudo make
  
  ls: /opt/local/etc/openssl/certs: No such file or directory
  
  /Users/ajswann/Downloads/android-sdk-macosx/tools/android update project --path . --target android-23
  
  Updated project.properties
  
  Updated local.properties
  
  build.xml: Found version-tag: custom. File will not be updated.
  
  Updated file ./proguard-project.txt
  
  It seems that there are sub-projects. If you want to update them
  
  please use the --subprojects parameter.
  
  /Users/ajswann/Downloads/android-sdk-macosx/tools/android update test-project --path tests -m .
  
  Resolved location of main project to: /groupchat/linphone-android/tests
  
  Updated project.properties
  
  Updated local.properties
  
  Updated file tests/proguard-project.txt
  
  Updated ant.properties
  
  /Users/ajswann/Downloads/android-sdk-macosx/tools/android update project --path liblinphone_tester --target android-23
  
  Updated project.properties
  
  Updated local.properties
  
  Updated file liblinphone_tester/proguard-project.txt
  
  ant -e -S clean
  
  Buildfile: /groupchat/linphone-android/build.xml
  
  No sub-builds to iterate on
  
  mkdir -p /groupchat/linphone-android/submodules/externals/openh264/include/wels
  
  rsync -rvLpgoc --exclude ".git"  /groupchat/linphone-android/submodules/externals/openh264/codec/api/svc/* /groupchat/linphone-android/submodules/externals/openh264/include/wels/.
  
  building file list ... done
  
  
  
  sent 156 bytes  received 20 bytes  352.00 bytes/sec
  
  total size is 56216  speedup is 319.41
  
  mkdir -p /groupchat/linphone-android/submodules/externals/build/openh264
  
  mkdir -p /groupchat/linphone-android/submodules/externals/build/openh264/arm
  
  cd /groupchat/linphone-android/submodules/externals/build/openh264/arm \
  
      && rsync -rvLpgoc --exclude ".git"  /groupchat/linphone-android/submodules/externals/openh264/* .
  
  building file list ... done
  
  
  
  sent 18841 bytes  received 20 bytes  37722.00 bytes/sec
  
  total size is 48272799  speedup is 2559.40
  
  cd /groupchat/linphone-android/submodules/externals/build/openh264/arm && \
  
      make libraries -j4 OS=android ARCH=arm NDKROOT=/Users/ajswann/Downloads/android-ndk-r10e TARGET=android-19
  
  cd ./ && sh ./codec/common/generate_version.sh
  
  Keeping existing codec/common/inc/version_gen.h
  
  mkdir -p /groupchat/linphone-android/submodules/externals/build/openh264
  
  mkdir -p /groupchat/linphone-android/submodules/externals/build/openh264/x86
  
  cd /groupchat/linphone-android/submodules/externals/build/openh264/x86 \
  
      && rsync -rvLpgoc --exclude ".git"  /groupchat/linphone-android/submodules/externals/openh264/* .
  
  building file list ... done
  
  
  
  sent 18841 bytes  received 20 bytes  12574.00 bytes/sec
  
  total size is 48272799  speedup is 2559.40
  
  cd /groupchat/linphone-android/submodules/externals/build/openh264/x86 && \
  
      make libraries -j4 OS=android ARCH=x86 NDKROOT=/Users/ajswann/Downloads/android-ndk-r10e TARGET=android-19
  
  cd ./ && sh ./codec/common/generate_version.sh
  
  nasm -DX86_32 -f elf -I./codec/common/x86/   -o codec/decoder/core/x86/dct.o codec/decoder/core/x86/dct.asm
  
  codec/decoder/core/x86/dct.asm:1: error: label or instruction expected at start of line
  
  codec/decoder/core/x86/dct.asm:144: error: label or instruction expected at start of line
  
  codec/decoder/core/x86/dct.asm:234: error: symbol `IdctResAddPred_mmx' redefined
  
  codec/decoder/core/x86/dct.asm:262: error: symbol `WelsBlockZero16x16_sse2' redefined
  
  codec/decoder/core/x86/dct.asm:276: error: symbol `WelsBlockZero8x8_sse2' redefined
  
  codec/decoder/core/x86/dct.asm:287: error: label or instruction expected at start of line
  
  make[1]: *** [codec/decoder/core/x86/dct.o] Error 1
  
  make[1]: *** Waiting for unfinished jobs....
  
  Keeping existing codec/common/inc/version_gen.h
  
  make[1]: *** wait: No child processes.  Stop.
  
  make: *** [build-openh264-x86] Error 2

  Source Repository (I simply clone it, add the platform-tools and tools folder from my android-sdk and run ’make’ and I get this error) :

  https://github.com/TheBaobabTeam/linphone-android

• HEVC with alpha [closed]

  3 mai 2024, par foxhable

  I trying create HEVC with alpha video from png images through ffmpeg.

  


  When i try, it outputs a video that works, has a transparent background and opens in QuickTime, but does not open in Safari. Then i try creating in prores 4444 codec and convert from macOS Context Menu -> Encode Selected Video Files with HEVC 1080p and Preserve Transparency. It has work - video with transparent background, open in QuickTime and in Safari.

  


  So i tried understand what a difference in meta data and only what i find its working video has HVEC encoder, but not working has Lavc61.5.103 hevc_videotoolbox. Can i somehow programmatically or from utilities like ffmpeg create video with HEVC With alpha, which working like from macOS context menu ? macOS context menu doesnt fit because i cant compress or create many videos

  


  Detail info

  


  I have example of working video. Info from ffprobe

  


  ffprobe movie-hevc.mov
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '.\movie-hevc.mov':
  Metadata:
    major_brand     : qt
    minor_version   : 0
    compatible_brands: qt
    creation_time   : 2021-01-02T10:33:38.000000Z
  Duration: 00:00:09.02, start: 0.000000, bitrate: 4053 kb/s
  Stream #0:0[0x1](und): Video: hevc (Main) (hvc1 / 0x31637668), yuv420p(tv, progressive), 1280x720 [SAR 1:1 DAR 16:9], 4046 kb/s, 60 fps, 60 tbr, 600 tbn (default)
      Metadata:
        creation_time   : 2021-01-02T10:33:38.000000Z
        handler_name    : Core Media Video
        vendor_id       : [0][0][0][0]
        encoder         : HEVC


  


  Info about video which i create in prores by ffmpeg command, then convert through macOS context menu

  


  command :

  


  ffmpeg -i a%d.png -r 30 -c:v prores_ks -profile:v 4  -allow_sw 1 -alpha_quality 1 -vtag hvc1 prores.mov


  


  info after converting

  


  ffprobe .\native-hevc.mov
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '.\native-hevc.mov':
  Metadata:
    major_brand     : qt
    minor_version   : 0
    compatible_brands: qt
    creation_time   : 2024-05-03T07:04:26.000000Z
  Duration: 00:00:12.77, start: 0.000000, bitrate: 8796 kb/s
  Stream #0:0[0x1](und): Video: hevc (Main) (hvc1 / 0x31637668), yuv420p(tv, bt709), 1920x1920, 8792 kb/s, 30 fps, 30 tbr, 15360 tbn (default)
      Metadata:
        creation_time   : 2024-05-03T07:04:27.000000Z
        handler_name    : Core Media Video
        vendor_id       : [0][0][0][0]
        encoder         : HEVC


  


  Info about video which i`m create direct in hevc by ffmpeg command

  


  ffmpeg -i a%d.png -r 30 -c:v hevc_videotoolbox -allow_sw 1 -alpha_quality 1 -vtag hvc1 ffmpeg-hevc.mov


  


  Info :

  


  ffprobe .\ffmpeg-hevc.mov
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '.\ffmpeg-hevc.mov':
  Metadata:
    major_brand     : qt
    minor_version   : 512
    compatible_brands: qt
    encoder         : Lavf61.3.103
  Duration: 00:00:12.77, start: 0.000000, bitrate: 3437 kb/s
  Stream #0:0[0x1]: Video: hevc (Main) (hvc1 / 0x31637668), yuv420p(tv, bottom coded first (swapped)), 1920x1920, 3435 kb/s, 30 fps, 30 tbr, 15360 tbn (default)
      Metadata:
        handler_name    : VideoHandler
        vendor_id       : FFMP
        encoder         : Lavc61.5.103 hevc_videotoolbox


  


  also i tried :

  


  

  • props -allow_sw 0 - get error

  


  • -alpha-quality 0.75, -pix_fmt bgra - safari not open, QT yes, transparent bg

  


  • without -vtag hvc1 - QuickTime cannot open

  


  • Tried convert from webm to hevc_videotoolbox - safari not open, QT yes, transparent bg

  


  • tried convert webm into pngs and in hevc_videotoolbox - safari not open, QT yes, transparent bg

  


  


  Tried answers :

  


  

  • https://stackoverflow.com/a/61663438

  


  • https://stackoverflow.com/a/69262399/17330336

  


  


  mac info :

  


  

  • macOS Monterey 12.7.2

  


  • Mac mini (Late 2012)

  


  • Core i5 3210M

  


  • Graphics Intel HD 4000

  


  


• Nexus One

  19 mars 2010, par Mans — Uncategorized

  I have had a Nexus One for about a week (thanks Google), and naturally I have an opinion or two about it.
  

  Hardware

  With the front side dominated by a touch-screen and a lone, round button, the Nexus One appearance is similar to that of most contemporary smartphones. The reverse sports a 5 megapixel camera with LED flash, a Google logo, and a smaller HTC logo. Power button, volume control, and headphone and micro-USB sockets are found along the edges. It is with appreciation I note the lack of a front-facing camera ; the silly idea of video calls is finally put to rest.

  Powering up the phone (I’m beginning to question the applicability of that word), I am immediately enamoured with the display. At 800×480 pixels, the AMOLED display is crystal-clear and easily viewable even in bright light. In a darker environment, the display automatically dims. The display does have one quirk in that the subpixel pattern doesn’t actually have a full RGB triplet for each pixel. The close-up photo below shows the pattern seen when displaying a solid white colour.

  

  The result of this is that fine vertical lines, particularly red or blue ones, look a bit jagged. Most of the time this is not much of a problem, and I find it an acceptable compromise for the higher effective resolution it provides.

  Basic interaction

  The Android system is by now familiar, and the Nexus offers no surprises in basic usage. All the usual applications come pre-installed : browser, email, calendar, contacts, maps, and even voice calls. Many of the applications integrate with a Google account, which is nice. Calendar entries, map placemarks, etc. are automatically shared between desktop and mobile. Gone is the need for the bug-ridden custom synchronisation software with which mobile phones of the past were plagued.

  Launching applications is mostly speedy, and recently used apps are kept loaded as long as memory needs allow. Although this garbage-collection-style of application management, where you are never quite sure whether an app is still running, takes a few moments of acclimatisation, it works reasonably well in day to day use. Most of the applications are well-behaved and save their data before terminating.

  Email

  Two email applications are included out of the box : one generic and one Gmail-only. As I do not use Gmail, I cannot comment on this application. The generic email client supports IMAP, but is rather limited in functionality. Fortunately, a much-enhanced version, K-9, is available for download. The main feature I find lacking here is threaded message view.

  The features, or lack thereof, in the email applications is not, however, of huge importance, as composing email, or any longer piece of text, is something one rather avoids on a system like this. The on-screen keyboard, while falling among the better of its kind, is still slow to use. Lack of tactile feedback means accidentally tapping the wrong key is easily done, and entering numbers or punctuation is an outright chore.

  Browser

  Whatever the Nexus lacks in email abilities, it makes up for with the browser. Surfing the web on a phone has never been this pleasant. Page rendering is quick, and zooming is fast and simple. Even pages not designed for mobile viewing are easy to read with smart reformatting almost entirely eliminating the sideways scrolling which hampered many a mobile browser of old.

  Calls and messaging

  Being a phone, the Nexus One is obviously able to make and receive calls, and it does so with ease. Entering a number or locating a stored contact are both straight-forward operations. During a call, audio is clear and of adequate loudness, although I have yet to use the phone in really noisy surroundings.

  The other traditional task of a mobile phone, messaging, is also well-supported. There isn’t really much to say about this.

  Multimedia

  Having a bit of an interest in most things multimedia, I obviously tested the capabilities of the Nexus by throwing some assorted samples at it, revealing ample space for improvement. With video limited to H.264 and MPEG4, and the only supported audio codecs being AAC, MP3, Vorbis, and AMR, there are many files which will not play.

  To make matters worse, only selected combinations of audio and video will play together. Several video files I tested played without sound, yet when presented with the very same audio data alone, it was correctly decoded. As for container formats, it appears restricted to MP4/MOV, and Ogg (for Vorbis). AVI files are recognised as media files, but I was unable to find an AVI file which would play.

  With a device clearly capable of so much more, the poor multimedia support is nothing short of embarrassing.

  The Market

  Much of the hype surrounding Android revolves around the Market, Google’s virtual marketplace for app authors to sell or give away their creations. The thousands of available applications are broadly categorised, and a search function is available.

  The categorised lists are divided into free and paid sections, while search results, disappointingly, are not. To aid the decision, ratings and comments are displayed alongside the summary and screenshots of each application. Overall, the process of finding and installing an application is mostly painless. While it could certainly be improved, it could also have been much worse.

  The applications themselves are, as hinted above, beyond numerous. Sadly, quality does not quite match up to quantity. The vast majority of the apps are pointless, though occasionally mildly amusing, gimmicks of no practical value. The really good ones, and they do exist, are very hard to find unless one knows precisely what to look for.

  Battery

  Packing great performance into a pocket-size device comes with a price in battery life. The battery in the Nexus lasts considerably shorter time than that in my older, less feature-packed Nokia phone. To some extent this is probably a result of me actually using it a lot more, yet the end result is the same : more frequent recharging. I should probably get used to the idea of recharging the phone every other night.

  Verdict

  The Nexus One is a capable hardware platform running an OS with plenty of potential. The applications are still somewhat lacking (or very hard to find), although the basic features work reasonably well. Hopefully future Android updates will see more and better core applications integrated, and I imagine that over time, I will find third-party apps to solve my problems in a way I like. I am not putting this phone on the shelf just yet.