Recherche avancée

Sur d’autres sites (11462)

• Yet another ffmpeg/libx264 issue

  26 décembre 2013, par kerim yucel

  My current situation is ; ffmpeg and libx264 has been compiled for Android, as shared and static libraries respectively. Since I have libx264.a and libffmpeg.so with me, only thing that remains is to link them and obtain a ffmpeg library that would allow me to proceed with my application. However, some questions remain unanswered. I am using Ubuntu with a virtual machine under Windows 7. I am using x264's last version, ffmpeg 0.10.4 release and NDK 7.

  I have tried to adjust flags (extracf and extrald) in order to include libx264 to ffmpeg compilation process as well, however I keep failing. Below you may find my build script for ffmpeg and the errors I have encountered.

  NDK=~/Android_NDK_r7b 
  
  PLATFORM=$NDK/platforms/android-8/arch-arm/ 
  
  PREBUILT=$NDK/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86 
  
  x264=/usr/local 
  
  #x264v2=~/x264 
  
  function build_one 
  
  { 
  
  ./configure --target-os=linux \ 
  
      --prefix=$PREFIX \ 
  
      --enable-cross-compile \ 
  
      --extra-libs="-lgcc" \ 
  
      --arch=arm \ 
  
      --cc=$PREBUILT/bin/arm-linux-androideabi-gcc \ 
  
      --cross-prefix=$PREBUILT/bin/arm-linux-androideabi- \ 
  
      --nm=$PREBUILT/bin/arm-linux-androideabi-nm \ 
  
      --sysroot=$PLATFORM \ 
  
     # --extra-cflags=" -O3 -fpic -DANDROID -DHAVE_SYS_UIO_H=1 -Dipv6mr_interface=ipv6mr_ifindex -fasm -Wno-psabi -fno-short-enums -fno-strict-aliasing -finline-limit=300 $OPTIMIZE_CFLAGS " \ 
  
      --extra-cflags="-I$x264/include" \ 
  
      --enable-shared \ 
  
      --enable-static \ 
  
      #--extra-ldflags="-Wl,-rpath-link=$PLATFORM/usr/lib  -L$PLATFORM/usr/lib -nostdlib -lc -lm -ldl -llog" \ 
  
      --extra-ldflags="-L$x264/lib" \ 
  
     --disable-everything \ 
  
     # --enable-demuxer=mov \ 
  
     # --enable-demuxer=h264 \ 
  
     # --disable-ffplay \ 
  
      --enable-gpl \ 
  
      --enable-libx264 \ 
  
     # --enable-protocol=file \ 
  
     # --enable-avformat \ 
  
     # --enable-avcodec \ 
  
     # --enable-encoder=libx264 \ 
  
     # --enable-decoder=rawvideo \ 
  
     #--enable-decoder=mjpeg \ 
  
     # --enable-decoder=h263 \ 
  
     # --enable-decoder=mpeg4 \ 
  
     # --enable-encoder=h264 \ 
  
     # --disable-network \ 
  
      #--enable-zlib \ 
  
     # --disable-avfilter \ 
  
      #--disable-avdevice \ 
  
      $ADDITIONAL_CONFIGURE_FLAG 
  
  
  
  make clean 
  
  make  -j4 install 
  
  $PREBUILT/bin/arm-linux-androideabi-ar d libavcodec/libavcodec.a inverse.o 
  
  $PREBUILT/bin/arm-linux-androideabi-ld -rpath-link=$PLATFORM/usr/lib -L$PLATFORM/usr/lib  -soname libffmpeg.so -shared -nostdlib  -z,noexecstack -Bsymbolic --whole-archive --no-undefined -o $PREFIX/libffmpeg.so libavcodec/libavcodec.a libavformat/libavformat.a libavutil/libavutil.a libswscale/libswscale.a -lc -lm -lz -ldl -llog  --warn-once  --dynamic-linker=/system/bin/linker $PREBUILT/lib/gcc/arm-linux-androideabi/4.4.3/libgcc.a 
  
  } 
  
  
  
  #arm v7vfpv3 
  
  CPU=armv7-a 
  
  OPTIMIZE_CFLAGS="-mfloat-abi=softfp -mfpu=vfpv3-d16 -marm -march=$CPU " 
  
  PREFIX=./androidIncludeTrialsNDK7/$CPU 
  
  ADDITIONAL_CONFIGURE_FLAG= 
  
  build_one 

  If I basically delete the lines extracf and extrald flags and use other ones (commented outs), it works fine except libx264 not found error. Otherwise, I get the following erros.

  ./buildnew.sh: line 35: --extra-cflags=-I/usr/local/include: No such file or directory 
  
  ./buildnew.sh: line 38: --extra-ldflags=-L/usr/local/lib: No such file or directory 
  
  ./buildnew.sh: line 40: --disable-everything: command not found 
  
  ./buildnew.sh: line 44: --enable-gpl: command not found 

  The compilation process ends with the following.

  make: *** [libavdevice/v4l.o] Error 1 
  
  make: *** Waiting for unfinished jobs.... 
  
  /home/mehmet/Android_NDK_r7b/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-ar: creating libavcodec/libavcodec.a 
  
  /home/mehmet/Android_NDK_r7b/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-ld: cannot open output file ./androidIncludeTrialsNDK7/armv7-a/libffmpeg.so: No such file or directory 

  I have x264 installed in my directory /home/mehmet/x264 and I also check whereis x264.a, it shows me as /usr/local/lib. I have tried changing the path $x264 to point out to home/mehmet/x264 folder, but I get the same error.

  Lastly, if I enable both extracf and extrald flags ( both commented ones and the used ones) . I get the same error mentioned above. I am afraid I am doing a simple typo here, but can`t see it and it is driving me crazy. Thanks a lot for your help.

  Best.

  EDIT

  I have deleted the comments and now obtain the following.

  ./buildnew.sh: 4: ./buildnew.sh: function: not found
  
  ERROR: libx264 not found

  Above error is observed from the terminal when I run the script. It build upto some point and finishes the process with the following error.

  libavcodec/libavcodec.a(libx264.o): In function `X264_frame':
  
  /home/mehmet/ffmpeg-0.10.4/libavcodec/libx264.c:159: undefined reference to `x264_picture_init'
  
  /home/mehmet/ffmpeg-0.10.4/libavcodec/libx264.c:179: undefined reference to `x264_encoder_reconfig'
  
  /home/mehmet/ffmpeg-0.10.4/libavcodec/libx264.c:191: undefined reference to `x264_encoder_encode'
  
  /home/mehmet/ffmpeg-0.10.4/libavcodec/libx264.c:197: undefined reference to `x264_encoder_delayed_frames'
  
  libavcodec/libavcodec.a(libx264.o): In function `encode_nals':
  
  /home/mehmet/ffmpeg-0.10.4/libavcodec/libx264.c:196: undefined reference to `x264_bit_depth'
  
  libavcodec/libavcodec.a(libx264.o): In function `X264_close':
  
  /home/mehmet/ffmpeg-0.10.4/libavcodec/libx264.c:231: undefined reference to `x264_encoder_close'
  
  libavcodec/libavcodec.a(libx264.o): In function `X264_init':
  
  /home/mehmet/ffmpeg-0.10.4/libavcodec/libx264.c:284: undefined reference to `x264_param_default'
  
  /home/mehmet/ffmpeg-0.10.4/libavcodec/libx264.c:292: undefined reference to `x264_param_default_preset'
  
  /home/mehmet/ffmpeg-0.10.4/libavcodec/libx264.c:305: undefined reference to `x264_param_parse'
  
  /home/mehmet/ffmpeg-0.10.4/libavcodec/libx264.c:502: undefined reference to `x264_param_apply_fastfirstpass'
  
  /home/mehmet/ffmpeg-0.10.4/libavcodec/libx264.c:505: undefined reference to `x264_param_apply_profile'
  
  /home/mehmet/ffmpeg-0.10.4/libavcodec/libx264.c:544: undefined reference to `x264_encoder_open_125'
  
  /home/mehmet/ffmpeg-0.10.4/libavcodec/libx264.c:554: undefined reference to `x264_encoder_headers'
  
  ./buildnew.sh: 51: ./buildnew.sh: build_one: not found

• Yet another ffmpeg/libx264 issue

  26 décembre 2013, par kerim yucel

  My current situation is ; ffmpeg and libx264 has been compiled for Android, as shared and static libraries respectively. Since I have libx264.a and libffmpeg.so with me, only thing that remains is to link them and obtain a ffmpeg library that would allow me to proceed with my application. However, some questions remain unanswered. I am using Ubuntu with a virtual machine under Windows 7. I am using x264’s last version, ffmpeg 0.10.4 release and NDK 7.

  I have tried to adjust flags (extracf and extrald) in order to include libx264 to ffmpeg compilation process as well, however I keep failing. Below you may find my build script for ffmpeg and the errors I have encountered.

  NDK=~/Android_NDK_r7b 
  
  PLATFORM=$NDK/platforms/android-8/arch-arm/ 
  
  PREBUILT=$NDK/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86 
  
  x264=/usr/local 
  
  #x264v2=~/x264 
  
  function build_one 
  
  { 
  
  ./configure --target-os=linux \ 
  
      --prefix=$PREFIX \ 
  
      --enable-cross-compile \ 
  
      --extra-libs="-lgcc" \ 
  
      --arch=arm \ 
  
      --cc=$PREBUILT/bin/arm-linux-androideabi-gcc \ 
  
      --cross-prefix=$PREBUILT/bin/arm-linux-androideabi- \ 
  
      --nm=$PREBUILT/bin/arm-linux-androideabi-nm \ 
  
      --sysroot=$PLATFORM \ 
  
     # --extra-cflags=" -O3 -fpic -DANDROID -DHAVE_SYS_UIO_H=1 -Dipv6mr_interface=ipv6mr_ifindex -fasm -Wno-psabi -fno-short-enums -fno-strict-aliasing -finline-limit=300 $OPTIMIZE_CFLAGS " \ 
  
      --extra-cflags="-I$x264/include" \ 
  
      --enable-shared \ 
  
      --enable-static \ 
  
      #--extra-ldflags="-Wl,-rpath-link=$PLATFORM/usr/lib  -L$PLATFORM/usr/lib -nostdlib -lc -lm -ldl -llog" \ 
  
      --extra-ldflags="-L$x264/lib" \ 
  
     --disable-everything \ 
  
     # --enable-demuxer=mov \ 
  
     # --enable-demuxer=h264 \ 
  
     # --disable-ffplay \ 
  
      --enable-gpl \ 
  
      --enable-libx264 \ 
  
     # --enable-protocol=file \ 
  
     # --enable-avformat \ 
  
     # --enable-avcodec \ 
  
     # --enable-encoder=libx264 \ 
  
     # --enable-decoder=rawvideo \ 
  
     #--enable-decoder=mjpeg \ 
  
     # --enable-decoder=h263 \ 
  
     # --enable-decoder=mpeg4 \ 
  
     # --enable-encoder=h264 \ 
  
     # --disable-network \ 
  
      #--enable-zlib \ 
  
     # --disable-avfilter \ 
  
      #--disable-avdevice \ 
  
      $ADDITIONAL_CONFIGURE_FLAG 
  
  
  
  make clean 
  
  make  -j4 install 
  
  $PREBUILT/bin/arm-linux-androideabi-ar d libavcodec/libavcodec.a inverse.o 
  
  $PREBUILT/bin/arm-linux-androideabi-ld -rpath-link=$PLATFORM/usr/lib -L$PLATFORM/usr/lib  -soname libffmpeg.so -shared -nostdlib  -z,noexecstack -Bsymbolic --whole-archive --no-undefined -o $PREFIX/libffmpeg.so libavcodec/libavcodec.a libavformat/libavformat.a libavutil/libavutil.a libswscale/libswscale.a -lc -lm -lz -ldl -llog  --warn-once  --dynamic-linker=/system/bin/linker $PREBUILT/lib/gcc/arm-linux-androideabi/4.4.3/libgcc.a 
  
  } 
  
  
  
  #arm v7vfpv3 
  
  CPU=armv7-a 
  
  OPTIMIZE_CFLAGS="-mfloat-abi=softfp -mfpu=vfpv3-d16 -marm -march=$CPU " 
  
  PREFIX=./androidIncludeTrialsNDK7/$CPU 
  
  ADDITIONAL_CONFIGURE_FLAG= 
  
  build_one 

  If I basically delete the lines extracf and extrald flags and use other ones (commented outs), it works fine except libx264 not found error. Otherwise, I get the following erros.

  ./buildnew.sh: line 35: --extra-cflags=-I/usr/local/include: No such file or directory 
  
  ./buildnew.sh: line 38: --extra-ldflags=-L/usr/local/lib: No such file or directory 
  
  ./buildnew.sh: line 40: --disable-everything: command not found 
  
  ./buildnew.sh: line 44: --enable-gpl: command not found 

  The compilation process ends with the following.

  make: *** [libavdevice/v4l.o] Error 1 
  
  make: *** Waiting for unfinished jobs.... 
  
  /home/mehmet/Android_NDK_r7b/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-ar: creating libavcodec/libavcodec.a 
  
  /home/mehmet/Android_NDK_r7b/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-ld: cannot open output file ./androidIncludeTrialsNDK7/armv7-a/libffmpeg.so: No such file or directory 

  I have x264 installed in my directory /home/mehmet/x264 and I also check whereis x264.a, it shows me as /usr/local/lib. I have tried changing the path $x264 to point out to home/mehmet/x264 folder, but I get the same error.

  Lastly, if I enable both extracf and extrald flags ( both commented ones and the used ones) . I get the same error mentioned above. I am afraid I am doing a simple typo here, but can`t see it and it is driving me crazy. Thanks a lot for your help.

  Best.

  EDIT

  I have deleted the comments and now obtain the following.

  ./buildnew.sh: 4: ./buildnew.sh: function: not found
  
  ERROR: libx264 not found

  Above error is observed from the terminal when I run the script. It build upto some point and finishes the process with the following error.

  libavcodec/libavcodec.a(libx264.o): In function `X264_frame':
  
  /home/mehmet/ffmpeg-0.10.4/libavcodec/libx264.c:159: undefined reference to `x264_picture_init'
  
  /home/mehmet/ffmpeg-0.10.4/libavcodec/libx264.c:179: undefined reference to `x264_encoder_reconfig'
  
  /home/mehmet/ffmpeg-0.10.4/libavcodec/libx264.c:191: undefined reference to `x264_encoder_encode'
  
  /home/mehmet/ffmpeg-0.10.4/libavcodec/libx264.c:197: undefined reference to `x264_encoder_delayed_frames'
  
  libavcodec/libavcodec.a(libx264.o): In function `encode_nals':
  
  /home/mehmet/ffmpeg-0.10.4/libavcodec/libx264.c:196: undefined reference to `x264_bit_depth'
  
  libavcodec/libavcodec.a(libx264.o): In function `X264_close':
  
  /home/mehmet/ffmpeg-0.10.4/libavcodec/libx264.c:231: undefined reference to `x264_encoder_close'
  
  libavcodec/libavcodec.a(libx264.o): In function `X264_init':
  
  /home/mehmet/ffmpeg-0.10.4/libavcodec/libx264.c:284: undefined reference to `x264_param_default'
  
  /home/mehmet/ffmpeg-0.10.4/libavcodec/libx264.c:292: undefined reference to `x264_param_default_preset'
  
  /home/mehmet/ffmpeg-0.10.4/libavcodec/libx264.c:305: undefined reference to `x264_param_parse'
  
  /home/mehmet/ffmpeg-0.10.4/libavcodec/libx264.c:502: undefined reference to `x264_param_apply_fastfirstpass'
  
  /home/mehmet/ffmpeg-0.10.4/libavcodec/libx264.c:505: undefined reference to `x264_param_apply_profile'
  
  /home/mehmet/ffmpeg-0.10.4/libavcodec/libx264.c:544: undefined reference to `x264_encoder_open_125'
  
  /home/mehmet/ffmpeg-0.10.4/libavcodec/libx264.c:554: undefined reference to `x264_encoder_headers'
  
  ./buildnew.sh: 51: ./buildnew.sh: build_one: not found

• What is Audience Segmentation ? The 5 Main Types & Examples

  16 novembre 2023, par Erin — Analytics Tips

  The days of mass marketing with the same message for millions are long gone. Today, savvy marketers instead focus on delivering the most relevant message to the right person at the right time.

  They do this at scale by segmenting their audiences based on various data points. This isn’t an easy process because there are many types of audience segmentation. If you take the wrong approach, you risk delivering irrelevant messages to your audience — or breaking their trust with poor data management.

  In this article, we’ll break down the most common types of audience segmentation, share examples highlighting their usefulness and cover how you can segment campaigns without breaking data regulations.

  What is audience segmentation ?

  Audience segmentation is when you divide your audience into multiple smaller specific audiences based on various factors. The goal is to deliver a more targeted marketing message or to glean unique insights from analytics.

  It can be as broad as dividing a marketing campaign by location or as specific as separating audiences by their interests, hobbies and behaviour.

  

  Audience segmentation inherently makes a lot of sense. Consider this : an urban office worker and a rural farmer have vastly different needs. By targeting your marketing efforts towards agriculture workers in rural areas, you’re honing in on a group more likely to be interested in farm equipment. 

  Audience segmentation has existed since the beginning of marketing. Advertisers used to select magazines and placements based on who typically read them. They would run a golf club ad in a golf magazine, not in the national newspaper.

  How narrow you can make your audience segments by leveraging multiple data points has changed.

  Why audience segmentation matters

  In a survey by McKinsey, 71% of consumers said they expected personalisation, and 76% get frustrated when a vendor doesn’t deliver.

  

  These numbers reflect expectations from consumers who have actively engaged with a brand — created an account, signed up for an email list or purchased a product.

  They expect you to take that data and give them relevant product recommendations — like a shoe polishing kit if you bought nice leather loafers.

  If you don’t do any sort of audience segmentation, you’re likely to frustrate your customers with post-sale campaigns. If, for example, you just send the same follow-up email to all customers, you’d damage many relationships. Some might ask : “What ? Why would you think I need that ?” Then they’d promptly opt out of your email marketing campaigns.

  To avoid that, you need to segment your audience so you can deliver relevant content at all stages of the customer journey.

  5 key types of audience segmentation

  To help you deliver the right content to the right person or identify crucial insights in analytics, you can use five types of audience segmentation : demographic, behavioural, psychographic, technographic and transactional.

  

  Demographic segmentation 

  Demographic segmentation is when you segment a larger audience based on demographic data points like location, age or other factors.

  The most basic demographic segmentation factor is location, which is easy to leverage in marketing efforts. For example, geographic segmentation can use IP addresses and separate marketing efforts by country. 

  But more advanced demographic data points are becoming increasingly sensitive to handle. Especially in Europe, GDPR makes advanced demographics a more tentative subject. Using age, education level and employment to target marketing campaigns is possible. But you need to navigate this terrain thoughtfully and responsibly, ensuring meticulous adherence to privacy regulations.

  Potential data points :

  • Location
  • Age
  • Marital status
  • Income
  • Employment 
  • Education

  Example of effective demographic segmentation :

  A clothing brand targeting diverse locations needs to account for the varying weather conditions. In colder regions, showcasing winter collections or insulated clothing might resonate more with the audience. Conversely, in warmer climates, promoting lightweight or summer attire could be more effective. 

  Here are two ads run by North Face on Facebook and Instagram to different audiences to highlight different collections :

  

  Each collection is featured differently and uses a different approach with its copy and even the media. With social media ads, targeting people based on advanced demographics is simple enough — you can just single out the factors when making your campaign. But if you don’t want to rely on these data-mining companies, that doesn’t mean you have no options for segmentation.

  Consider allowing people to self-select their interests or preferences by incorporating a short survey within your email sign-up form. This simple addition can enhance engagement, decrease bounce rates, and ultimately improve conversion rates, offering valuable insights into audience preferences.

  This is a great way to segment ethically and without the need of data-mining companies.

  Behavioural segmentation

  Behavioural segmentation segments audiences based on their interaction with your website or app.

  You use various data points to segment your target audience based on their actions.

  Potential data points :

  • Page visits
  • Referral source
  • Clicks
  • Downloads
  • Video plays
  • Goal completion (e.g., signing up for a newsletter or purchasing a product)

  Example of using behavioural segmentation to improve campaign efficiency :

  One effective method involves using a web analytics tool such as Matomo to uncover patterns. By segmenting actions like specific clicks and downloads, pinpoint valuable trends—identifying actions that significantly enhance visitor conversions. 

  

  For instance, if a case study video substantially boosts conversion rates, elevate its prominence to capitalise on this success.

  Then, you can set up a conditional CTA within the video player. Make it pop up after the user has watched the entire video. Use a specific form and sign them up to a specific segment for each case study. This way, you know the prospect’s ideal use case without surveying them.

  This is an example of behavioural segmentation that doesn’t rely on third-party cookies.

  Psychographic segmentation

  Psychographic segmentation is when you segment audiences based on your interpretation of their personality or preferences.

  Potential data points :

  • Social media patterns
  • Follows
  • Hobbies
  • Interests

  Example of effective psychographic segmentation :

  Here, Adidas segments its audience based on whether they like cycling or rugby. It makes no sense to show a rugby ad to someone who’s into cycling and vice versa. But to rugby athletes, the ad is very relevant.

  

  If you want to avoid social platforms, you can use surveys about hobbies and interests to segment your target audience in an ethical way.

  Technographic segmentation

  Technographic segmentation is when you single out specific parts of your audience based on which hardware or software they use.

  Potential data points :

  • Type of device used
  • Device model or brand
  • Browser used

  Example of segmenting by device type to improve user experience :

  Upon noticing a considerable influx of tablet users accessing their platform, a leading news outlet decided to optimise their tablet browsing experience. They overhauled the website interface, focusing on smoother navigation and better readability for tablet users. These changes offered tablet users a seamless and enjoyable reading experience tailored precisely to their device.

  Transactional segmentation

  Transactional segmentation is when you use your customers’ purchase history to better target your marketing message to their needs.

  When consumers prefer personalisation, they typically mean based on their actual transactions, not their social media profiles.

  Potential data points :

  • Average order value
  • Product categories purchased within X months
  • X days since the last purchase of a consumable product

  Example of effective transactional segmentation :

  A pet supply store identifies a segment of customers consistently purchasing cat food but not other pet products. They create targeted email campaigns offering discounts or loyalty rewards specifically for cat-related items to encourage repeat purchases within this segment.

  If you want to improve customer loyalty and increase revenue, the last thing you should do is send generic marketing emails. Relevant product recommendations or coupons are the best way to use transactional segmentation.

  B2B-specific : Firmographic segmentation

  Beyond the five main segmentation types, B2B marketers often use “firmographic” factors when segmenting their campaigns. It’s a way to segment campaigns that go beyond the considerations of the individual.

  Potential data points :

  • Company size
  • Number of employees
  • Company industry
  • Geographic location (office)

  Example of effective firmographic segmentation :

  Companies of different sizes won’t need the same solution — so segmenting leads by company size is one of the most common and effective examples of B2B audience segmentation.

  The difference here is that B2B campaigns are often segmented through manual research. With an account-based marketing approach, you start by researching your potential customers. You then separate the target audience into smaller segments (or even a one-to-one campaign).

  Start segmenting and analysing your audience more deeply with Matomo

  Segmentation is a great place to start if you want to level up your marketing efforts. Modern consumers expect to get relevant content, and you must give it to them.

  But doing so in a privacy-sensitive way is not always easy. You need the right approach to segment your customer base without alienating them or breaking regulations.

  That’s where Matomo comes in. Matomo champions privacy compliance while offering comprehensive insights and segmentation capabilities. With robust privacy controls and cookieless configuration, it ensures GDPR and other regulations are met, empowering data-driven decisions without compromising user privacy.

  Take advantage of our 21-day free trial to get insights that can help you improve your marketing strategy and better reach your target audience. No credit card required.