Recherche avancée

Sur d’autres sites (4623)

• The Guide to an Ethical Web : With Big Data Comes Big Responsibility

  13 mars, par Alex Carmona

  Roughly two-thirds of Earth’s 8 billion people use the internet for communication, education, entertainment, business and more. We are connected globally in ways previous generations could’ve never dreamed of. It’s been a wild ride, and we’re just starting.

  Many users have learned that experiences online can be a mix of good and bad. Sometimes, the bad can feel like it outweighs the good, particularly when large tech companies use our data shadily, cut corners on accessibility or act in any other way that devalues the human being behind the screen.

  As fellow internet citizens, what responsibility do we have to create a more ethical web for our customers ?

  In this article, we’ll look at ethical principles online and how to act (and not act) to build trust, reach customers regardless of ability, safeguard privacy and stay compliant while improving business outcomes.

  

  What is an “ethical web” ?

  When we talk about the ethical web, we’re talking about the use of the internet in an ethical way. Among other values, it involves transparency, consent and restraint. It applies the Golden Rule to the internet : Treat others (and their data and user experience) how you’d want yourself (and yours) to be treated. 

  With limited oversight, the internet has evolved in ways that often prioritise profit over user rights. While selling data or pushing cookies might seem logical in this context, they can undermine trust and reputation. And the tide is slowly but surely shifting as consumers and legislators push back.

  Consumers no longer want to buy from companies that will use their data in ways they don’t agree to. In 2022, 75% of UK and US consumers surveyed said they were uncomfortable purchasing from businesses with weak data ethics.

  Legislators worldwide have been taking part in this effort for nearly a decade, with laws like GDPR in the EU and LGPD in Brazil, as well as the various state laws in the US, like California’s CCPA and Virginia’s VCDPA. 

  Even tech giants are no longer above the law, like Meta, which was fined over a billion Euros for GDPR violations in 2023.

  

  These changes may make the internet feel less business-friendly at first glance, but ethical choices ultimately build a stronger digital ecosystem for both companies and consumers. 

  Likewise, all internet users alike can make this happen by shunning short-term profit and convenience for healthier, long-term choices and behaviour.

  As we dig into what it takes to build an ethical web, remember that no company or individual is free from mistakes in these areas nor is it an overnight fix. Progress is made one click at a time.

  Ethical SEO : Optimising your content and your ethics

  Content creation and search engine optimisation (SEO) require so much work that it’s hard to fault creators for not always abiding by search engine guidelines and seeking shortcuts – especially when there’s a sea of LinkedIn posts about how copying/pasting ChatGPT responses helped someone rank #1 for several keywords in one week.

  However, users turn to Google and other search engines for something of substance that will guide or entertain them.

  Content meets customer needs and is more likely to lead to sales when it’s well-written, original and optimised just enough to make it easier to find on the first page of results. This doesn’t happen when content teams dilute quality and waste a reader or viewer’s time on posts that will only yield a higher bounce rate.

  Some SEO pros do find success by building backlinks through private blog networks or crafting a million unedited posts with generative AI, but it’s short-lived. Google and other search engines always catch up, and their content plummets or gets penalised and delisted with every new update.

  Content teams can still rank at the top while sticking to ethical SEO principles. Here’s a sample list of dos and don’ts to get started :

  • Do put content quality above all else. Make content that serves the audience, not just a brand or partner ad network.
  • Do apply the E-E-A-T framework. Search engines value content written by authors who bring expertise, experience, authority and trust (E-E-A-T).
  • Don’t keyword stuff. This might have worked in the early days of SEO, but it hurts readability and now harms article performance.
  • Do use alt text as intended. While it can still help SEO, alt text should prioritise accessibility for users with screen readers.

  • Don’t steal content. Whether it’s violating copyright, copying/pasting other people’s content or simply paraphrasing without citation, companies should never steal content.
  • Don’t steal ideas. It’s okay to join in on a current conversation or trends in an industry, but content creators should be sure they have something valuable to add.
  • Do use AI tools as partners, not creators. AI can be an incredible aid in crafting content, but it should never be posted without a human’s touch.

  When we follow ethical SEO guidelines and get more clients with our content, how do we best handle their data ?

  Ethical data governance : Important principles and how to avoid data misuse

  Data governance comprises every aspect of how a company manages data, including storage, security, privacy, lifecycle management, setting policies and maintaining compliance with laws like GDPR and HIPAA.

  Applying data ethics to governance is doing it all in a transparent, restrained way that acknowledges an individual’s right to ownership over their data. 

  For organisations, this translates to getting consent to collect data and clearly spelling out how it will be stored and used — and sticking to it.

  If a user’s birth date is needed for legal reasons, it cannot be sold to a third party or later used for something else without explicit permission. Reusing data in ways that stray from its original purpose is a form of commingling, one of the data misuses that is easy for even well-intentioned teams to do accidentally.

  Ethical data governance also includes the vigilant safeguarding of users’ data and minimising potential privacy issues.

  Failing to implement and adhere to strong security measures leads to situations like the National Public Data (NPD) breach, where cyber criminals expose the addresses, phone numbers and social security numbers of hundreds of millions of people. This was due in large part to a weakness in storing login credentials and a lack of password policy enforcement.

  No one at NPD wanted this to happen, but security likely took a backseat to other business concerns, leading to the company’s filing for bankruptcy.

  More importantly, as a data broker that aggregates information from other sources, the people affected likely had no clue this organisation had been buying and selling their data. The companies originally entrusted with their information helped provide the leaked data, showing a lack of care for privacy.

  Situations like this reinforce the need for strict data protection laws and for companies to refine their data governance approach. 

  Businesses can improve their data governance posturing with managers and other higher-ups setting the right tone at the top. If leadership takes a firm and disciplined approach by setting and adhering to strong policies, the rest of the team will follow and minimise the chances of data misuse and security incidents.

  One way to start is by using tools that make the principles of data ethics easier to follow.

  Ethical web analytics : Drawing insights while respecting privacy

  Web analytics tools are designed to gather data about users and what they do while visiting a site.
  The most popular tool worldwide is Google Analytics (GA). Its brand name and feature set carry a lot of weight, but many former users have switched to alternatives due to dissatisfaction with the changes made in GA4 and reservations about the way Google handles data.

  

  Google is another tech giant that has been slapped with massive GDPR fines for issues over its data processing practices. It has run so afoul of compliance that it was banned in France and Austria for a while. Additionally, in the US Department of Justice’s ongoing antitrust lawsuit against Google, the company’s data tracking has been targeted for both how it affects users and potential rivals.

  Unlike GA, ethical web analytics tools allow websites to get the data they need while respecting user privacy.

  Matomo offers privacy protections like :

  • Providing data anonymisation and IP anonymisation
  • Allowing users the ability to not process personally identifiable information (PII)
  • Disabling the ability to track users across websites by default to make compliance easier
  • Giving users full control over their customer data without the risk of it getting into the hands of third parties
  • Much more

  We’re also fully transparent about how we handle your data on the web and in the Matomo Cloud and in how we build Matomo as an open-source tool. Our openness allows you to be more open with your customers and how you ethically use their data.

  There are other GDPR-compliant tools on the market, but some of them, like Adobe Analytics, require more setup from users for compliance, don’t grant full control over data and don’t offer on-premise options or consent-free tracking.

  Beyond tracking, there are other ways to make a user’s experience more enjoyable and ethical.

  Ethical user experience : User-friendliness, not user-hostility

  When designing a website or application, creating a positive user experience (UX) always comes first. 

  The UI should be simple to navigate, data and privacy policy information should be easy to find and customers should feel welcomed. They must never be tricked into consenting or installing. 

  When businesses resort to user-hostile tactics, the UX becomes a battle between the user and them. What may seem like a clever tactic to increase sign-ups can alienate potential customers and ruin a brand’s image. 

  Here are some best practices for creating a more ethical UX :

  Avoid dark patterns

  Dark patterns are UI designs and strategies that mislead users into paying for, agreeing to or doing something they don’t actually want. These designs are unethical because they’re manipulative and remove transparency and consent from the interaction. 

  In some cases, they’re illegal and can bring lawsuits. 

  In 2023, Italy’s Data Protection Authority (DPA) fined a digital marketing company €300,000 for alleged GDPR violations. They employed dark patterns by asking customers to accept cookies again after rejecting them and placing the option to reject cookies outside the cookie banner. 

  Despite their legality and 56% of surveyed customers losing trust in platforms that employ dark patterns, a review by the Organisation for Economic Co-operation and Development (OECD) found that 76% of the websites examined contained at least one dark pattern.

  

  If a company is worried that they may be relying on dark patterns, here are some examples of what to avoid :

  • Pre-ticking boxes to have users agree to third-party cookies, sign up for a newsletter, etc.
  • Complicated cookie banners without a one-click way to reject all unnecessary cookies
  • Hiding important text with text colour, under drop-down menus or requiring hovering over something with a mouse 
  • “Confirm shaming” users with emotionally manipulative language to delay subscription cancellations or opt out of tracking 

  Improve trust centres

  Trust centres are the sections of a website that outline how a company approaches topics like data governance, user privacy and security. 

  They should be easy to find and understand. If a user has a question about a company’s data policy, it should be one click away with language that doesn’t require a law degree to comprehend.

  Additionally, trust centres must cover all relevant details, including where data is stored and who does the subprocessing. This is an area where even some of the best-intentioned companies may miss the mark, but it’s also an easy fix and a great place to start creating a more ethical web.

  Embrace inclusivity

  People want to feel welcomed to the party — and deserve to be — regardless of their race, ethnicity, religion, gender identity, orientation or ability. 

  Inclusivity is great for customers and companies alike. 

  A study by the Unstereotype Alliance found that progressive marketing drove up short- and long-term sales, customer loyalty and purchase consideration. A Kantar study reported that 75% of surveyed customers around the world consider a company’s diversity and inclusivity when making a purchasing decision.

  An easy place to start embracing inclusivity is with a website’s blog images. The people in photos and cartoons should reflect a variety of different backgrounds.

  Another area to improve inclusivity is by making your site or app more accessible.

  Accessibility ethics : An internet for everyone

  Accessibility is designing your product in a way that everyone can enjoy or take part in, regardless of ability. Digital accessibility is applying this design to the web and applications by making accommodations like adding descriptive alt text to images for users with visual impairments.

  Just because someone has a hearing, vision, speech, mobility, neurological or other impairment doesn’t mean they have any less of a right to shop online, read silly listicles or get into arguments with strangers in the comment section.

  Beyond being the right thing to do, the Fable team shows there’s a strong business case for accessibility. People with disabilities have money to spend, and the accommodations businesses make for them often benefit people without disabilities, too – as anyone who streams with subtitles can attest.

  Despite being a win-win for greater inclusivity and business, much of the web is still inaccessible. WebAIM, a leader in web accessibility, studied a million web pages and found an average of over 55 accessibility errors per page.

  We must all play a more active role in improving the experience of our users with disabilities, and we can start with accessibility auditing and testing.

  An accessibility audit is an evaluation of how usable a site is for people with disabilities. It may be done in-house by an expert on a company’s team or, for better results, a third-party consultant who can give a fully objective audit.

  Auditing might consist of running an automated tool or manually checking your site, PDFs, emails and other materials for compliance with the Web Content Accessibility Guidelines list.

  Accessibility testing is narrower than auditing. It checks how accessibility or its absence looks in action. It can be done after a site, app, email or product is released, but it ideally starts in the development process.

  Testing should be done manually and with automated tools. Manual checks put developers in the position of their users, allowing them to get a better idea of what users are dealing with firsthand. Automated tools can save time and money, but there should always be manual testing in the process.

  Auditing gives teams an idea of where to start with improving accessibility, and testing helps make sure accommodations work as intended.

  Conclusion

  At Matomo, we strive to make the ethical web a reality, starting with web analytics.

  For our users, it means full compliance with stringent policies like GDPR and providing 100% accurate data. For their customers, it’s collecting only the data required to do the job and enabling cookieless configurations to get rid of annoying banners. 

  For both parties, it’s knowing that respect for privacy is one of our foundational values, whether it’s the ability to look under Matomo’s hood and read our open-source code, the option to store data on-premise to minimise the chances of it falling into the wrong hands or one of the other ways that we protect privacy.

  If you weren’t 100% ethical before, it’s never too late to change. You can even bring your Google Analytics data with you.

  Join us in our mission to improve the web. We can’t do it alone ! 

  Try Matomo free for 21 days

  no credit card required

• IOException : Error running exec() Command, When calling FFmpeg method

  21 avril 2016, par kc ochibili

  i am trying to create a slide show mp4 using this ffmpeg method but i keep getting this IOException Error running exec(). Command when i click the button.

  here is my call

  ffmpegController = new FfmpegController(getTempDirectory(), new File(""));
  
  ffmpegController.createSlideshowFromImagesAndAudio(slideFrames, getAudioPath(), getOutPath(), 500, mCallbackResponse);

  Here is the source code of the small project.
  Here is the apk

  And here is my Error message

     Error running exec(). Command: [ffmpeg, -y, -i, /storage/emulated/0/TestFFmpeg/frame1.png, /storage/emulated/0/TestFFmpeg/temp/image-000.jpg]
  
  
  
   Working Directory: lib Environment: [VIBE_PIPE_PATH=/dev/pipes, ANDROID_ROOT=/system, EMULATED_STORAGE_SOURCE=/mnt/shell/emulated, LOOP_MOUNTPOINT=/mnt/obb, EMULATED_STORAGE_TARGET=/storage/emulated, ANDROID_BOOTLOGO=1, LD_LIBRARY_PATH=/vendor/lib:/system/lib, EXTERNAL_STORAGE=/storage/emulated/legacy, ANDROID_SOCKET_zygote=9, ANDROID_DATA=/data, PATH=/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin, ANDROID_ASSETS=/system/app, ASEC_MOUNTPOINT=/mnt/asec, BOOTCLASSPATH=/system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/framework2.jar:/system/framework/telephony-common.jar:/system/framework/voip-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/sec_edm.jar:/system/framework/seccamera.jar:/system/framework/secocsp.jar:/system/framework/sc.jar:/system/framework/scrollpause.jar:/system/framework/stayrotation.jar:/system/framework/smartfaceservice.jar:/system/framework/sws.jar:/system/framework/WfdCommon.jar, ANDROID_PROPERTY_WORKSPACE=8,66560, SECONDARY_STORAGE=/storage/extSdCard:/storage/UsbDriveA:/storage/UsbDriveB:/storage/UsbDriveC:/storage/UsbDriveD:/storage/UsbDriveE:/storage/UsbDriveF, ANDROID_STORAGE=/storage]

  Here is my Activity code :

  public class MainActivity extends Activity {
  
  
  
  Button testButton;
  
  EditText errorLogView;
  
  
  
  TinyDB tinydb;// sharedPreference Wrapper
  
  static Context context;
  
  @Override
  
  protected void onCreate(Bundle savedInstanceState) {
  
      super.onCreate(savedInstanceState);
  
      setContentView(R.layout.activity_main);
  
      context = getApplicationContext();
  
      tinydb = new TinyDB(context); // sharedPreference Wrapper
  
      testButton = (Button) findViewById(R.id.test_Image_View);
  
      errorLogView = (EditText) findViewById(R.id.errorlog);
  
      setListeners();
  
  }
  
  
  
  public void setListeners(){
  
      testButton.setOnClickListener(new OnClickListener() {
  
  
  
          @Override
  
          public void onClick(View v) {
  
              // TODO Auto-generated method stub
  
              Bitmap frame1Bitmap = BitmapFactory.decodeResource(getResources(), R.drawable.ic_launcher);
  
              //Saves the image to the file system an returns the path
  
              String firstFrame = tinydb.putImagePNG("TestFFmpeg", "frame1.png", frame1Bitmap);
  
              String secondFrame = tinydb.putImagePNG("TestFFmpeg", "frame2.png", frame1Bitmap);
  
              String thirdFrame = tinydb.putImagePNG("TestFFmpeg", "frame3.png", frame1Bitmap);
  
  
  
  
  
              ArrayList<clip> slideFrames = new ArrayList<clip>();
  
              slideFrames.add(new Clip(firstFrame));
  
              slideFrames.add(new Clip(secondFrame));
  
              slideFrames.add(new Clip(thirdFrame));
  
  
  
              copyResourceSoundToSDCard();
  
  
  
              FfmpegController ffmpegController = null;
  
              try {
  
  
  
                  ffmpegController = new FfmpegController(getTempDirectory(), new File(""));
  
                  ffmpegController.createSlideshowFromImagesAndAudio(slideFrames, getAudioPath(), getOutPath(), 500, mCallbackResponse);
  
  
  
              } catch (FileNotFoundException e) {
  
                  // TODO Auto-generated catch block
  
                  e.printStackTrace();
  
                  toast("FileNotFoundException");
  
                  toast(e.getLocalizedMessage());
  
              } catch (IOException e) {
  
                  // TODO Auto-generated catch block
  
                  toast("IOException");
  
                  toast(e.getLocalizedMessage());
  
                  errorLogView.setText(e.getLocalizedMessage());
  
                  e.printStackTrace();
  
              } catch (Exception e) {
  
                  // TODO Auto-generated catch block
  
                  e.printStackTrace();
  
                  toast("Exception ");
  
                  toast(e.getLocalizedMessage());
  
              }           
  
          }
  
      });
  
  
  
  
  
  }
  
  
  
  public Clip getAudioPath(){
  
      Clip mAudPath = null;
  
      try {
  
          mAudPath = new Clip(new File(tinydb.getString("audpath")).getCanonicalPath());
  
      } catch (IOException e1) {
  
          // TODO Auto-generated catch block
  
          e1.printStackTrace();
  
      }
  
      return mAudPath;
  
  }
  
  
  
  public Clip getOutPath(){
  
      String videoName = ("myTestVideo.mp4");
  
      String saveFolder = ("TestFFmpeg/videos");
  
      String movieFullPath = setupAudioFolder(saveFolder, videoName);
  
  
  
      Clip outPath = null;
  
      try {
  
          outPath = new Clip(new File(movieFullPath).getCanonicalPath());
  
      } catch (IOException e1) {
  
          // TODO Auto-generated catch block
  
          e1.printStackTrace();
  
      }
  
      tinydb.putString("outhPath", outPath.path);
  
  
  
      return outPath;
  
  }
  
  
  
  public void copyResourceSoundToSDCard(){
  
      try {
  
          copyRawFile(context, R.raw.screens_shot_sound, getResaveDirectory(), "755");
  
      } catch (IOException e) {
  
          // TODO Auto-generated catch block
  
          e.printStackTrace();
  
      } catch (InterruptedException e) {
  
          // TODO Auto-generated catch block
  
          e.printStackTrace();
  
      }
  
  }
  
  
  
   private File getResaveDirectory(){
  
  
  
      String audioName = ("ShotSound.wav");
  
      String saveFolder = ("TestFFmpeg");
  
      File appRootFile;
  
      String path = setupAudioFolder(saveFolder, audioName);
  
      tinydb.putString("audpath",  path);
  
      appRootFile = new File(path);
  
      return appRootFile;
  
    }
  
  
  
  public String setupAudioFolder(String theFolder, String theImageName){
  
      File sdcard_path = Environment.getExternalStorageDirectory();
  
      File mFolder = new File(sdcard_path, theFolder);
  
      if (!mFolder.exists()) {
  
          if (!mFolder.mkdirs()) {
  
              Log.e("While creatingsave path",
  
                      "Default Save Path Creation Error");
  
              // Toast("Default Save Path Creation Error");
  
          }
  
      }
  
      String mFullPath = mFolder.getPath() + '/' + theImageName;
  
  
  
      return mFullPath;
  
  }
  
  private static void copyRawFile(Context ctx, int resid, File file, String mode) throws IOException, InterruptedException
  
  {
  
      final String abspath = file.getAbsolutePath();
  
      // Write the iptables binary
  
      final FileOutputStream out = new FileOutputStream(file);
  
      final InputStream is = ctx.getResources().openRawResource(resid);
  
      byte buf[] = new byte[1024];
  
      int len;
  
      while ((len = is.read(buf)) > 0) {
  
          out.write(buf, 0, len);
  
      }
  
      out.close();
  
      is.close();
  
      // Change the permissions
  
      Runtime.getRuntime().exec("chmod "+mode+" "+abspath).waitFor();
  
  }       
  
  ShellCallback mCallbackResponse = new ShellUtils.ShellCallback() {
  
  
  
      @Override
  
      public void shellOut(String shellLine) {
  
          // TODO Auto-generated method stub
  
  
  
      }
  
  
  
      @Override
  
      public void processComplete(int exitValue) {
  
          // TODO Auto-generated method stub
  
          toast("process done");
  
  
  
      }
  
  };
  
  
  
  public File getTempDirectory(){
  
      String saveFolder = ("TestFFmpeg/temp");
  
      File appRootFile = setupCustomFile(saveFolder);
  
  
  
  
  
      return appRootFile;
  
   }
  
  
  
  public File setupCustomFile(String theFolder){
  
      File sdcard_path = Environment.getExternalStorageDirectory();
  
      File mFolder = new File(sdcard_path, theFolder);
  
      if (!mFolder.exists()) {
  
          if (!mFolder.mkdirs()) {
  
              Log.e("While creatingsave path",
  
                      "Default Save Path Creation Error");
  
              // Toast("Default Save Path Creation Error");
  
          }
  
      }
  
  
  
      return mFolder;
  
  }
  
  
  
  
  
  
  
  public static void toast(String thetext) {
  
      Toast.makeText(context, thetext, Toast.LENGTH_LONG).show();
  
  }
  
  </clip></clip>

  any help would be appreciated

• Building my JAVA parameter array for FFMPEG

  29 janvier 2016, par user3541092

  FFmpeg Version : N-63893-gc69defd Copyright (c) 2000-2014 the FFmpeg developers
  built on Jul 16 2014 05:38:01 with gcc 4.6 (Debian 4.6.3-1)

  Machine : Amazon Linux t2.micro (free tier)

  Sample File : sample_iTunes.mov
  Sample File URL : https://support.apple.com/en-us/HT201549

  I’m trying to replicate the following FFmpeg command, using a string array and then pass this array into the Runtime.getRuntime().exec().

  ffmpeg -i file:/var/local/ffmpegtest/media_input/sample_iTunes.mov -pix_fmt yuv420p -c:v libx264 -vtag mp42 -metadata major_brand="mp42" -b:v 8000k -minrate 8000k -maxrate 10000k -ac 2 -strict experimental -c:a aac -b:a 256k -metadata:s:a:0 handler="Stereo" /var/local/ffmpegtest/media_output/sample_iTunes.mp4 -y

  NOTE : This works when I pass the full command, as a single string into Runtime.getRuntime().exec().

      String _cmd = "ffmpeg -i %s -pix_fmt yuv420p -c:v libx264 -vtag mp42 -metadata major_brand=\"mp42\" "
  
              + "-b:v 8000k -minrate 8000k -maxrate 10000k -ac 2 -strict experimental -c:a aac -b:a 256k -metadata:s:a:0 handler=\"Stereo\" %s -y";
  
      String _ffmpegCommand = String.format(_cmd, _inputFile, _outPutFile);
  
      p = Runtime.getRuntime().exec(_ffmpegCommand);
  
      BufferedReader _reader = new BufferedReader(new InputStreamReader(p.getErrorStream()));
  
  
  
      String _line = null;
  
  
  
      while((_line = _reader.readLine()) != null) {
  
          lw.writeLine(_logPath + _logName, _line);
  
          System.out.println(_line);
  
      }

  I started out with just a basic parameter list. As I add add each additional parameter, I re-build the JAR file and upload it to my EC2 instance to test for any errors.

  The following string array works :

  try
  
          {
  
              String[] _params = {"ffmpeg",
  
                         "-i",
  
                         String.format("%s", _inputFile),
  
                         "-pix_fmt",
  
                         "yuv420p",
  
                         "-c:v",
  
                         "libx264",
  
                         String.format("%s", _outPutFile),
  
                         "-y"};
  
  
  
              p = Runtime.getRuntime().exec(_params);
  
  
  
              BufferedReader _reader = new BufferedReader(new InputStreamReader(p.getErrorStream()));
  
  
  
              String _line = null;
  
  
  
              while((_line = _reader.readLine()) != null) {
  
                  lw.writeLine(_logPath + _logName, _line);
  
                  System.out.println(_line);
  
              }
  
          }
  
          catch (Exception e) {
  
              BufferedReader _reader = new BufferedReader(new InputStreamReader(p.getErrorStream()));
  
  
  
              String _line = null;
  
  
  
              while((_line = _reader.readLine()) != null) {
  
                  lw.writeLine(_logPath + _logName, _line);
  
                  System.out.println(_line);
  
              }
  
  
  
          }

  However, when I continue to build the array with additional parameters, I begin to experience problems (lets add -vtag mp42) :

  try
  
          {
  
              String[] _params = {"ffmpeg",
  
                         "-i",
  
                         String.format("%s", _inputFile),
  
                         "-pix_fmt",
  
                         "yuv420p",
  
                         "-c:v",
  
                         "libx264",
  
                         "-vtag", // <---- New
  
                         "mp42", // <---  New
  
                         String.format("%s", _outPutFile),
  
                         "-y"};
  
  
  
              p = Runtime.getRuntime().exec(_params);
  
  
  
              BufferedReader _reader = new BufferedReader(new InputStreamReader(p.getErrorStream()));
  
  
  
              String _line = null;
  
  
  
              while((_line = _reader.readLine()) != null) {
  
                  lw.writeLine(_logPath + _logName, _line);
  
                  System.out.println(_line);
  
              }
  
          }
  
          catch (Exception e) {
  
              BufferedReader _reader = new BufferedReader(new InputStreamReader(p.getErrorStream()));
  
  
  
              String _line = null;
  
  
  
              while((_line = _reader.readLine()) != null) {
  
                  lw.writeLine(_logPath + _logName, _line);
  
                  System.out.println(_line);
  
              }
  
  
  
          }

  Error Message : Could not write header for output file #0 (incorrect codec parameters ?) : Invalid data found when processing input

  Full Log output for errant trail run :

  29 Jan 2016 03:45:09 UTC - Running FFMpeg...
  
  29 Jan 2016 03:45:09 UTC -  Input file: /var/local/ffmpegtest/media_input/sample_iTunes.mov
  
  29 Jan 2016 03:45:09 UTC -  Output file: /var/local/ffmpegtest/media_output/sample_iTunes.mp4
  
  29 Jan 2016 03:45:09 UTC - ffmpeg version N-63893-gc69defd Copyright (c) 2000-2014 the FFmpeg developers
  
  29 Jan 2016 03:45:09 UTC -   built on Jul 16 2014 05:38:01 with gcc 4.6 (Debian 4.6.3-1)
  
  29 Jan 2016 03:45:09 UTC -   configuration: --prefix=/root/ffmpeg-static/64bit --extra-cflags='-I/root/ffmpeg-static/64bit/include -static' --extra-ldflags='-L/root/ffmpeg-static/64bit/lib -static' --extra-libs='-lxml2 -lexpat -lfreetype' --enable-static --disable-shared --disable-ffserver --disable-doc --enable-bzlib --enable-zlib --enable-postproc --enable-runtime-cpudetect --enable-libx264 --enable-gpl --enable-libtheora --enable-libvorbis --enable-libmp3lame --enable-gray --enable-libass --enable-libfreetype --enable-libopenjpeg --enable-libspeex --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-version3 --enable-libvpx
  
  29 Jan 2016 03:45:09 UTC -   libavutil      52. 89.100 / 52. 89.100
  
  29 Jan 2016 03:45:09 UTC -   libavcodec     55. 66.101 / 55. 66.101
  
  29 Jan 2016 03:45:09 UTC -   libavformat    55. 43.100 / 55. 43.100
  
  29 Jan 2016 03:45:09 UTC -   libavdevice    55. 13.101 / 55. 13.101
  
  29 Jan 2016 03:45:09 UTC -   libavfilter     4.  8.100 /  4.  8.100
  
  29 Jan 2016 03:45:09 UTC -   libswscale      2.  6.100 /  2.  6.100
  
  29 Jan 2016 03:45:09 UTC -   libswresample   0. 19.100 /  0. 19.100
  
  29 Jan 2016 03:45:09 UTC -   libpostproc    52.  3.100 / 52.  3.100
  
  29 Jan 2016 03:45:09 UTC - Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/var/local/ffmpegtest/media_input/sample_iTunes.mov':
  
  29 Jan 2016 03:45:09 UTC -   Metadata:
  
  29 Jan 2016 03:45:09 UTC -     major_brand     : qt  
  
  29 Jan 2016 03:45:09 UTC -     minor_version   : 537199360
  
  29 Jan 2016 03:45:09 UTC -     compatible_brands: qt  
  
  29 Jan 2016 03:45:09 UTC -     creation_time   : 2005-10-17 22:54:32
  
  29 Jan 2016 03:45:09 UTC -   Duration: 00:01:25.50, start: 0.000000, bitrate: 307 kb/s
  
  29 Jan 2016 03:45:09 UTC -     Stream #0:0(eng): Video: mpeg4 (Simple Profile) (mp4v / 0x7634706D), yuv420p, 640x480 [SAR 1:1 DAR 4:3], 261 kb/s, 10 fps, 10 tbr, 3k tbn, 25 tbc (default)
  
  29 Jan 2016 03:45:09 UTC -     Metadata:
  
  29 Jan 2016 03:45:09 UTC -       creation_time   : 2005-10-17 22:54:33
  
  29 Jan 2016 03:45:09 UTC -       handler_name    : Apple Video Media Handler
  
  29 Jan 2016 03:45:09 UTC -       encoder         : 3ivx D4 4.5.1
  
  29 Jan 2016 03:45:09 UTC -     Stream #0:1(eng): Audio: aac (mp4a / 0x6134706D), 32000 Hz, mono, fltp, 43 kb/s (default)
  
  29 Jan 2016 03:45:09 UTC -     Metadata:
  
  29 Jan 2016 03:45:09 UTC -       creation_time   : 2005-10-17 22:54:34
  
  29 Jan 2016 03:45:09 UTC -       handler_name    : Apple Sound Media Handler
  
  29 Jan 2016 03:45:09 UTC - [libx264 @ 0x30c2c00] using SAR=1/1
  
  29 Jan 2016 03:45:09 UTC - [libx264 @ 0x30c2c00] using cpu capabilities: MMX2 SSE2Fast SSSE3 FastShuffle SSE4.2 AVX AVX2 FMA3 BMI1 BMI2
  
  29 Jan 2016 03:45:09 UTC - [libx264 @ 0x30c2c00] profile High, level 2.2
  
  29 Jan 2016 03:45:09 UTC - [libx264 @ 0x30c2c00] 264 - core 129 r2230 1cffe9f - H.264/MPEG-4 AVC codec - Copyleft 2003-2012 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=1 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=10 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
  
  29 Jan 2016 03:45:09 UTC - [mp4 @ 0x30c21a0] Tag mp42/0x3234706d incompatible with output codec id '28' ([33][0][0][0])
  
  29 Jan 2016 03:45:09 UTC - Output #0, mp4, to '/var/local/ffmpegtest/media_output/sample_iTunes.mp4':
  
  29 Jan 2016 03:45:09 UTC -   Metadata:
  
  29 Jan 2016 03:45:09 UTC -     major_brand     : qt  
  
  29 Jan 2016 03:45:09 UTC -     minor_version   : 537199360
  
  29 Jan 2016 03:45:09 UTC -     compatible_brands: qt  
  
  29 Jan 2016 03:45:09 UTC -     Stream #0:0(eng): Video: h264 (libx264) (mp42 / 0x3234706D), yuv420p, 640x480 [SAR 1:1 DAR 4:3], q=-1--1, 10 fps, 90k tbn, 10 tbc (default)
  
  29 Jan 2016 03:45:09 UTC -     Metadata:
  
  29 Jan 2016 03:45:09 UTC -       creation_time   : 2005-10-17 22:54:33
  
  29 Jan 2016 03:45:09 UTC -       handler_name    : Apple Video Media Handler
  
  29 Jan 2016 03:45:09 UTC -       encoder         : Lavc55.66.101 libx264
  
  29 Jan 2016 03:45:09 UTC -     Stream #0:1(eng): Audio: aac (libvo_aacenc), 32000 Hz, mono, s16, 128 kb/s (default)
  
  29 Jan 2016 03:45:09 UTC -     Metadata:
  
  29 Jan 2016 03:45:09 UTC -       creation_time   : 2005-10-17 22:54:34
  
  29 Jan 2016 03:45:09 UTC -       handler_name    : Apple Sound Media Handler
  
  29 Jan 2016 03:45:09 UTC -       encoder         : Lavc55.66.101 libvo_aacenc
  
  29 Jan 2016 03:45:09 UTC - Stream mapping:
  
  29 Jan 2016 03:45:09 UTC -   Stream #0:0 -> #0:0 (mpeg4 (native) -> h264 (libx264))
  
  29 Jan 2016 03:45:09 UTC -   Stream #0:1 -> #0:1 (aac (native) -> aac (libvo_aacenc))
  
  29 Jan 2016 03:45:09 UTC - Could not write header for output file #0 (incorrect codec parameters ?): Invalid data found when processing input