Recherche avancée

Sur d’autres sites (5826)

• FFMPEG/tensorflow warping .mp4's with no observable pattern of correlation

  25 mai 2018, par ThePeskyWabbit

  The function that performs the processing is here :

  def ffwd_video(path_in, path_out, checkpoint_dir, device_t='/gpu:0', batch_size=4):
  
  video_clip = VideoFileClip(path_in, audio=False)
  
  video_writer = ffmpeg_writer.FFMPEG_VideoWriter(path_out, video_clip.size, video_clip.fps, codec="libx264",
  
                                                  preset="slow", bitrate="3000k",
  
                                                  audiofile=path_in, def ffwd_video(path_in, path_out, checkpoint_dir, device_t='/gpu:0', batch_size=2):threads=None,
  
                                                  ffmpeg_params=None)
  
  
  
  g = tf.Graph()
  
  soft_config = tf.ConfigProto(allow_soft_placement=True)
  
  soft_config.gpu_options.allow_growth = True
  
  with g.as_default(), g.device(device_t), \
  
          tf.Session(config=soft_config) as sess:
  
  
  
      batch_shape = (batch_size, video_clip.size[1], video_clip.size[0], 3)
  
      print(batch_shape)
  
      img_placeholder = tf.placeholder(tf.float32, shape=batch_shape,
  
                                       name='img_placeholder')
  
  
  
      preds = transform.net(img_placeholder)
  
      print(preds)
  
      saver = tf.train.Saver()
  
      if os.path.isdir(checkpoint_dir):
  
          ckpt = tf.train.get_checkpoint_state(checkpoint_dir)
  
          if ckpt and ckpt.model_checkpoint_path:
  
              saver.restore(sess, ckpt.model_checkpoint_path)
  
          else:
  
              raise Exception("No checkpoint found...")
  
      else:
  
          saver.restore(sess, checkpoint_dir)
  
  
  
      X = np.zeros(batch_shape, dtype=np.float32)
  
  
  
      def style_and_write(count):
  
          for i in range(count, batch_size):
  
              X[i] = X[count]  # Use last frame to fill X
  
          _preds = sess.run(preds, feed_dict={img_placeholder: X})
  
          for i in range(0, count):
  
              video_writer.write_frame(np.clip(_preds[i], 0, 255).astype(np.uint8))
  
  
  
      frame_count = 0  # The frame count that written to X
  
      for frame in video_clip.iter_frames():
  
          X[frame_count] = frame
  
          frame_count += 1
  
          if frame_count == batch_size:
  
              style_and_write(frame_count)
  
              frame_count = 0
  
  
  
      if frame_count != 0:
  
          style_and_write(frame_count)
  
  
  
      video_writer.close()

  I do not expect this to be a repeatable sample as it requires gigabytes of models/checkpoints/etc. to do so.

  Anyways, I am converting .gif’s to .mp4’s using this line of code :

  os.system('echo "y"| ffmpeg -i temp.gif -movflags faststart -pix_fmt yuv420p -vf "scale=trunc(iw/2)*2:trunc(ih/2)*2" temp.mp4')

  and when I run a subsequent .mp4 through the video rendering function, this will sometimes happen :

  original : https://i.imgur.com/WrBa6yw.gifv

  result : https://giphy.com/gifs/dream-bot-BzqB8XILJuVTJcgJnn

  It will happen on certain .mp4’s 100% of the time and on others, 0% of the time. It either happens to a clip or it does not happen to that clip. It is not a case of a single clip sometimes having this problem. If it is good, it is always good but if it’s bad, that clip will never work.

  After this output data from when the clips are processed :

  good gifs
  
  Stream #0:0: Video: h264 (libx264) ([33][0][0][0] / 0x0021), yuv420p, 728x728, q=-1--1, 30 fps, 15360 tbn, 30 tbc
  
  frame=  450 fps= 78 q=-1.0 Lsize=    7570kB time=00:00:14.93 bitrate=4152.6kbits/s
  
  
  
  Stream #0:0: Video: gif, bgra, 800x450, 25 fps, 25 tbr, 100 tbn, 100 tbc
  
  Stream #0:0: Video: h264 (libx264) ([33][0][0][0] / 0x0021), yuv420p, 728x408, q=-1--1, 23.98 fps, 24k tbn, 23.98 tbc
  
  frame=  360 fps=198 q=-1.0 Lsize=    2568kB time=00:00:14.93 bitrate=1408.8kbits/s 
  
  
  
  Stream #0:0: Video: gif, bgra, 728x408, 23.92 fps, 23.98 tbr, 100 tbn, 100 tbc
  
  Stream #0:0: Video: h264 (libx264) ([33][0][0][0] / 0x0021), yuv420p, 728x408, q=-1--1, 23.98 fps, 24k tbn, 23.98 tbc
  
  frame=  360 fps=198 q=-1.0 Lsize=    2568kB time=00:00:14.93 bitrate=1408.8kbits/s 
  
  
  
  bad gifs
  
  Stream #0:0: Video: h264 (libx264) ([33][0][0][0] / 0x0021), yuv420p, 800x450, q=-1--1, 25 fps, 12800 tbn, 25 tbc
  
  frame=  150 fps= 87 q=-1.0 Lsize=    1840kB time=00:00:05.92 bitrate=2545.8kbits/s
  
  
  
  Stream #0:0: Video: gif, bgra, 378x275, 25 fps, 25 tbr, 100 tbn, 100 tbc
  
  Stream #0:0: Video: h264 (libx264) ([33][0][0][0] / 0x0021), yuv420p, 378x274, q=-1--1, 25 fps, 12800 tbn, 25 tbc
  
  frame=  115 fps=0.0 q=-1.0 Lsize=     253kB time=00:00:04.52 bitrate= 459.4kbits/s

  I have noticed that the frame= value is exactly 15x larger than the .gif fps value while for the bad .gifs, it is not. I believe this is the cause but do not know how to change these values. does anybody know how I can process/convert the gif to .mp4 so that the frame= value is 15x the gif fps ?

• We are hiring engineers to build an awesome product and platform used by millions of people

  16 février 2016, par Piwik Core Team — Jobs

  Are you ready for a new challenge ? Or maybe you know someone who is looking for a change ? We have some exciting problems to solve and are looking for senior developers to work with us and our community on our open source Piwik Analytics platform. Piwik is used by more than one million websites all over the world. It is deployed on more than 300.000 servers and some users track more than 1 billion actions per month.

  What is it like to work on Piwik ?

  We develop this software using modern PHP, MySQL, Redis, AngularJS and more. We provide several kind of APIs and a plugin architecture to allow developers to extend and change Piwik to their needs. However, we would not be Piwik if we stopped at this point ! We want to turn Piwik into an even more awesome product and platform.
  You can imagine there is a lot to do and many challenges to face !

  While one part is to always make Piwik scale better and to improve UI and UX, we also want to provide simple APIs to make the life of developers as pleasant as possible. We aim to solve things the right way and our thousands of unit, integration, system, JavaScript and screenshot tests help us to innovate and to not be afraid of change. We like clean code and constant improvements.

  The Piwik team lives in New Zealand, Europe (Poland, Germany) and in the U.S. We do the vast majority of our collaboration online. Our values include being open, transparent and sharing knowledge. For this we use tools like GitHub and Slack to communicate and Quake servers to take our minds off complex challenges. We are a small, flexible team, so when you come aboard, you will play an integral part in engineering and have a big impact on the product loved by so many people. You’ll help to create a welcoming environment for new contributors and set an example with your development practices and communications skills.

  Apply now, or spread the word !

  If you have strong skills in PHP send us an email with your CV and tell us a little about yourself and your experience in engineering complex applications.

  Apply for a job here http://piwik.org/jobs/ and if you’re maybe not the right candidate, contribute to the project by sharing this blog post and by sending it to your friends !

• We are hiring engineers to build an awesome product and platform used by millions of people

  16 février 2016, par Piwik Core Team — Uncategorized

  Are you ready for a new challenge ? Or maybe you know someone who is looking for a change ? We have some exciting problems to solve and are looking for senior developers to work with us and our community on our open source Piwik Analytics platform. Piwik is used by more than one million websites all over the world. It is deployed on more than 300.000 servers and some users track more than 1 billion actions per month.

  What is it like to work on Piwik ?

  We develop this software using modern PHP, MySQL, Redis, AngularJS and more. We provide several kind of APIs and a plugin architecture to allow developers to extend and change Piwik to their needs. However, we would not be Piwik if we stopped at this point ! We want to turn Piwik into an even more awesome product and platform.
  You can imagine there is a lot to do and many challenges to face !

  While one part is to always make Piwik scale better and to improve UI and UX, we also want to provide simple APIs to make the life of developers as pleasant as possible. We aim to solve things the right way and our thousands of unit, integration, system, JavaScript and screenshot tests help us to innovate and to not be afraid of change. We like clean code and constant improvements.

  The Piwik team lives in New Zealand and Europe (Germany). We do the vast majority of our collaboration online. Our values include being open, transparent and sharing knowledge. For this we use tools like GitHub and Slack to communicate and Quake servers to take our minds off complex challenges. We are a small, flexible team, so when you come aboard, you will play an integral part in engineering and have a big impact on the product loved by so many people. You’ll help to create a welcoming environment for new contributors and set an example with your development practices and communications skills.

  Apply now, or spread the word !

  If you have strong skills in PHP send us an email with your CV and tell us a little about yourself and your experience in engineering complex applications.

  Apply for a job here http://piwik.org/jobs/ and if you’re maybe not the right candidate, contribute to the project by sharing this blog post and by sending it to your friends !