Recherche avancée

Sur d’autres sites (6609)

• Invalid data found when processing input on ffmpeg m4s to mp4 transfer

  1er mars 2020, par keith scott

  The result of the power shell window

  I saw a post on here about converting m4s to mp4 and I have followed the steps of concatenating all the files into another m4s file that I called all.m4s and when I use the command ffmpeg -i allm4s.m4s -c copy video.mp4. I made the combined m4s file by coding an exe to add all the m4s files that have the word video in them to the m4s file. Here is the source code written in c# if you compile the code then that is the code I have used to make the m4s

  using System;
  
  using System.Collections.Generic;
  
  using System.Linq;
  
  using System.Text;
  
  using System.Threading.Tasks;
  
  using System.IO;
  
  
  
  namespace files
  
  {
  
      class Program
  
      {
  
          static void Main(string[] args)
  
          {
  
              string dir = Directory.GetCurrentDirectory();
  
              string[] info = Directory.GetFiles(dir);
  
              Console.WriteLine(dir + "\\allm4s.m4s");
  
              Console.ReadKey();
  
              foreach (string name in info)
  
              {
  
                  if (Path.GetFileName(name).Contains(".m4s") && Path.GetFileName(name).Contains("video"))
  
                  {
  
                      using (Stream srcStream = File.OpenRead(name))
  
                      {
  
                          using (Stream destStream = File.OpenWrite(dir+"\\allm4s.m4s"))
  
                          {
  
                              srcStream.CopyTo(destStream);
  
                              Console.WriteLine(destStream+name);
  
                          }
  
                      }
  
                  }
  
              }
  
              Console.ReadKey();
  
          }
  
      }
  
  }

  I think if there is to be an issue it is to do with this allm4s.m4s file as the file size is about 1.5mb even though each segment m4s is about 750kb each and there are quite a lot.If anyone has a way of adding concatenating lots of files together through a program/application that would be useful.

• pip path : anaconda vs. native python (on macOS)

  26 juin 2020, par Hubert Schölnast

  I am using macOS X and I installed native Python 3.8 in April, and the packages of this version are stored in :

  


  /Users/hubert/Library/Python/3.8/lib/python/site-packages/


  


  Some weeks later, in May, I installed Anaconda, but it uses a different path for it's packages :

  


  /Users/hubert/opt/anaconda3/lib/python3.7/site-packages/


  


  Today I needed to install a new package to be used in a native Python script. I typed :

  


  pip install ffmpeg


  


  I've got a success-message. But when I wanted to run my script, it couldn't find ffmpeg. I rebooted my Mac, but the script still couldn't find it. So I again tried pip install ffmpeg. Now I did get this message :

  


  Requirement already satisfied: ffmpeg in ./opt/anaconda3/lib/python3.7/site-packages (1.4)


  


  But obviously native Pythons wants to have it in the other path.

  


  My questions :

  


  

  1. Is it save to just copy the directories ffmpeg and ffmpeg-1.4.dist-info from the anaconda directory to the native directory ?

  


  2. How can I tell pip to use the native Python directory to install new packages ?

  


  3. Is it a good idea to merge the two site-packages directories ? And if it's a good idea : What is the best way to let native Python 3.8 and Anaconda (which obviously uses Python 3.7) use the same site-packages directory ?

  


  


• lavd : deprecate the bktr device

  28 janvier 2024, par Anton Khirnov

  lavd : deprecate the bktr device
  It implements BSD-specific support for very old analog capture cards,
  
  which are highly unlikely to be useful today. After being added in 2005,
  
  there were never any commits to it beyond compilation fixes and generic
  
  maintenance. There have also been zero trac tickets for this device, and
  
  the only related web search result I found concludes that it does not
  
  work.
  The code also does some unacceptable things, like messing with signal
  
  handlers and storing its state in global variables.
  

  • [DH] doc/indevs.texi
  • [DH] libavdevice/bktr.c
  • [DH] libavdevice/version_major.h