Recherche avancée

Sur d’autres sites (6133)

• Why do my Windows filenames keep getting converted in FFMPEG ?

  14 avril 2024, par GeneralTully

  I'm running a script that walks through a large library of .flac music, making a mirror library with the same structure but converted to .opus. I'm doing this on Windows 11, so I believe the source filenames are all in UTF-16. The script calls FFMPEG to do the converting.

  


  For some reason, uncommon characters keep getting converted to different but similar characters when the script runs, for example :

  


  06 xXXi_wud_nvrstøp_ÜXXx.flac


  


  gets converted to :

  


  06 xXXi_wud_nvrstøp_ÜXXx.opus


  


  They look almost identical, but the Ü and I believe also the ø are technically slightly different characters before and after the conversion.

  


  The function which calls FFMPEG for the conversion looks like this :

  


  def convert_file(pool, top, file):
    fullPath = os.path.join(top, file)
    # Pass count=1 to str.replace() just in case .flac is in the song
    # title or something.
    newPath = fullPath.replace(src_dir, dest_dir, 1)
    newPath = newPath.replace(".flac", ".opus", 1)

    if os.path.isfile(newPath):
        return None
    else:
        print("{} does not exist".format(newPath))
   
        cvt = [
            "Ffmpeg", "-v", "debug", "-i", fullPath, "-c:a", "libopus", "-b:a", "96k", newPath]
        print(cvt)

        return (
            fullPath,
            pool.apply_async(subprocess.run, kwds={
                "args": cvt,
                "check": True,
                "stdin": subprocess.DEVNULL}))


  


  The arguments are being supplied by os.walk with no special parameters.

  


  Given that the script is comparing filenames to check if a conversion needs to happen, and the filenames keep getting changed, it keeps destroying and recreating the same files every time the script runs.

  


  Why might this be happening ?

  


  edit : I have confirmed that if I manually execute the FFMPEG command in CMD, bypassing Python completely, it converts the original Unicode 0125 + 01410 to 0334 (U with umlaut), so this doesn't seem to be a Python problem.

  


• lavf : Use wchar functions for filenames on windows for mkdir/rmdir/rename/unlink

  17 novembre 2014, par Martin Storsjö

  lavf : Use wchar functions for filenames on windows for mkdir/rmdir/rename/unlink
  This makes sure that the internal utf8 path names are handled
  
  properly - the normal file handling functions assume path names
  
  are in the native codepage, which isn’t utf8.
  This assumes that the tools outside of lavf don’t use the mkdir
  
  definition. (The tools don’t do the same reading of command line
  
  parameters as wchar either - they probably won’t handle all possible
  
  unicode file parameters properly, but at least work more predictably
  
  if no utf8/wchar conversion is involved.)
  This is moved further down in os_support.h, since windows.h shouldn’t
  
  be included before winsock2.h, while io.h needs to be included before
  
  the manual defines for lseek functions.
  Signed-off-by : Martin Storsjö <martin@martin.st>
  

  • [DH] libavformat/internal.h
  • [DH] libavformat/os_support.h

• Revision 34657 : lister les plugins non utilises (le glob() est pourri, qui fait mieux)

  23 janvier 2010, par fil@… — Log

  lister les plugins non utilises (le glob() est pourri, qui fait mieux)