Recherche avancée

Sur d’autres sites (2833)

• Additional : BIC : allow digits 1-9 in second place of location

  28 janvier 2016, par stefanb

  Additional : BIC : allow digits 1-9 in second place of location
  It seems that the BIC specification https://en.wikipedia.org/wiki/ISO_9362
  
  was interpreted too strictly, only allowing digits 1 and 2 while those 2 just
  
  have a special meaning, but all 1-9 are allowed.
  Example : SSKNDE77XXX Sparkasse Nuernberg. Closes #1658.
  

• ffmpeg encode timestamp on a timelapse video

  20 avril 2023, par Kyeotic

  I have a video that is a timelapse (generated by a GoPro, if that matters) with images every 5 seconds. I want to encode a timestamp onto it. Previously I've used a command like this one to get a timestamp burned in

  


  # Convert the date to EPOCH. This will be used to set the time for the draw text
# method.
EPOCH=$(date --date="${STARTDATE}" +%s)

# we assume that the STARTDATE is in UTC 0000, Zulu time, GMT and that we want
# to convert it to the local time on the computer.
ffmpeg -i "${INPUT}" -vf drawtext="fontsize=30:fontcolor=yellow:text='%{pts\:localtime\:${EPOCH}}':x=(w-text_w) - 10:y=(h-text_h) - 10" -vcodec libx265 -crf 28 "${OUTPUT}"


  


  The issue is that the timestamps generated by this progress as if it is a normal video, stamping a 30 minute timelapse as if it were 25 seconds. What I want are timestamps that match the timelapse.

  


  I've looked at the drawtext docs. I thought rate might be the key, but 1/5 and 150 both produce errors like this one :

  


  Parsed_drawtext_0 @ 0x10c607370] Failed to parse expression: (h-text_h) - 10 r=1/5 


  


  I figure I might need to multiply the current frame value to get the correct time, but I don't know how to do that.

  


• How to make FFMPEG video grayscale ?

  15 octobre 2018, par Aang

  In my program I am using the subprocess Python module in my script to call on FFMPEG to turn a sequence of images into a video (grayscale). It works and a video is created, but upon further inspection I see that the video itself has encoded the different intensities incorrectly.

  Here is my code :

                  subprocess.call(['/usr/local/bin/ffmpeg', '-framerate', \
  
                               framerate, '-f', 'image2','-pattern_type', \
  
                               'glob', '-i', self.directory + '/orbit_*.png', \
  
                               '-r', '10', '-s', '620x380', '-flags', 'gray', self.directory + 
  
                               ".avi"])

  Here is a link to the video that’s created : https://drive.google.com/open?id=0Bxt1siua2KQma0JaMVBMcE9TOEE

  If you’ll look at the scale bar on the right in the video, which normally looks like this
  in color, you’ll see that the same color shows up twice on the scale bar. I think it’s because FFMPEG is reading colors with the same intensities (for example, yellow and blue) the same way and therefore when the photo is encoded into grayscale it looks like this.

  What can I do ? Is this a matter of changing the "-flags", "gray" parameters of my subprocess call ?