Recherche avancée

Sur d’autres sites (8061)

• How to improve this Powershell script ?

  3 janvier 2023, par Joan Venge

  I wrote a powershell script that merges go pro video files if they have multiple files. It works when the videos are at the root drive i.e. C :, but otherwise not. The mergevideos.txt file is not created if I run the script from a different directory. Or the txt is created but it's empty. Not sure what's going on when run from a different directory.

  


  So is there a way to fix these issues and refactor this code to make it better ? Ideally I want the script to automatically look at the directory it's in or allows me to specify the directory it should work in so I can just call it from the same location but the videos can be anywhere.

  


  $path = "C:/NewVideos/"
$oldvids = Get-ChildItem -Path $path *.mp4
foreach ($oldvid in $oldvids) {
    $curpath = $oldvid.DirectoryName

    $name = [System.IO.Path]::GetFileNameWithoutExtension($oldvid)
    $ext = [System.IO.Path]::GetExtension($oldvid)
    if ($name.StartsWith("GX01") -and !($name.EndsWith("_merged")))
    {
        $newvid = $curpath + $name + "_merged" + $ext
        if ([System.IO.File]::Exists($newvid))
        {
            Write-Output "$name | ALREADY MERGED"
            continue
        }

        $count = 1

        for ($num = 2; $num -lt 10; $num++)
        {
            $nextpart = $name.Replace("GX01", "GX0" + $num)
            if ([System.IO.File]::Exists($curpath + "/" + $nextpart + $ext))
            {
                $count = $num
            }
        }

        if ($count -eq 1)
        {
            Write-Output "$name | SINGLE VIDEO"
            continue
        }

        $mergefile = $curpath + "mergevideos.txt"
        if (!(Test-Path $mergefile))
        {
            New-Item -path $curpath -name mergevideos.txt -type "file"
        }

        Clear-Content $mergefile

        for ($num = 1; $num -le $count; $num++)
        {
            $nextpart = $name.Replace("GX01", "GX0" + $num)
            $videofilename = "file '" + $nextpart + $ext + "'"
            Add-Content $mergefile $videofilename
        }

         Write-Output "$name | MERGING  $count VIDEOS"
         ffmpeg -f concat -safe 0 -i $mergefile -c copy $newvid
    }
}


  


• Wave64 (.w64) file format : question regarding chunk GUIDs

  24 janvier 2023, par pdu

  I am having trouble understanding the headers of the Wave64 (.w64) files generated by ffmpeg and especially the GUIDs.

  


  The specification

  


  I have found this document which describes the file format and the GUIDs. I have also found other websites (here and here) that (indirectly) point to the same document. So this document is the only thing I have.

  


  According to this document the GUIDs are 128bits/16bytes long and should start with the FourCC of the Wave file format, but in lowercase instead of uppercase (see page 3). It also says that the 64bits fields are stored in little-endian (see item 3 of the list page 1), but it does not say anything about 128bits fields (but it should be the same).
For example the GUID for the RIFF chunk is : 66666972-912E-11CF-A5D6-28DB04C10000.

  


  The problem

  


  When I open a .w64 file generated by ffmpeg with an hex editor, I get this : 72 69 66 66 2E 91 CF 11 A5 D6 28 DB 04 C1 00 00. At the beginning, 76 69 66 66 stands for riff in ASCII. We can see that 0x66666972 from the spec was indeed stored in little-endian order (so far, so good). If we continue, we have 2E 91 and CF 11, which are still little-endian for 0x912E and 0x11CF. But now it gets weird : the following group of bytes are : A5 D6 and 28 DB 04 C1 00 00 for 0xA5D6 and 0x28DB04C10000 in the spec. So it is in big-endian now ?

  


  For reference, the relevant ffmpeg source files are wavenc.c, w64.h and w64.c.
I have also found this thread where someone implemented a .wav to .w64 converter (see the .7z attachment in the first post) and the GUIDs are stored in the same way as ffmpeg.

  


  Conclusion

  


  Seeing that two different implementations are doing the same thing, it probably means that I am missing something. Do you have any explanation ?

  


• FFmpeg - Wave64 (.w64) file format : question regarding chunk GUIDs

  26 janvier 2023, par pdu

  I am having trouble understanding the headers of the Wave64 (.w64) files generated by ffmpeg and especially the GUIDs.

  


  The specification

  


  I have found this document which describes the file format and the GUIDs. I have also found other websites (here and here) that (indirectly) point to the same document. So this document is the only thing I have.

  


  According to this document the GUIDs are 128bits/16bytes long and should start with the FourCC of the Wave file format, but in lowercase instead of uppercase (see page 3). It also says that the 64bits fields are stored in little-endian (see item 3 of the list page 1), but it does not say anything about 128bits fields (but it should be the same).
For example the GUID for the RIFF chunk is : 66666972-912E-11CF-A5D6-28DB04C10000.

  


  The problem

  


  When I open a .w64 file generated by ffmpeg with an hex editor, I get this : 72 69 66 66 2E 91 CF 11 A5 D6 28 DB 04 C1 00 00. At the beginning, 76 69 66 66 stands for riff in ASCII. We can see that 0x66666972 from the spec was indeed stored in little-endian order (so far, so good). If we continue, we have 2E 91 and CF 11, which are still little-endian for 0x912E and 0x11CF. But now it gets weird : the following group of bytes are : A5 D6 and 28 DB 04 C1 00 00 for 0xA5D6 and 0x28DB04C10000 in the spec. So it is in big-endian now ?

  


  For reference, the relevant ffmpeg source files are wavenc.c, w64.h and w64.c.
I have also found this thread where someone implemented a .wav to .w64 converter (see the .7z attachment in the first post) and the GUIDs are stored in the same way as ffmpeg.

  


  Conclusion

  


  Seeing that two different implementations are doing the same thing, it probably means that I am missing something. Do you have any explanation ?