Recherche avancée

Sur d’autres sites (10184)

• Realtime removal of carriage return in shell

  1er mai 2013, par Seth

  For context, I'm attempting to create a shell script that simplifies the realtime console output of ffmpeg, only displaying the current frame being encoded. My end goal is to use this information in some sort of progress indicator for batch processing.

  For those unfamiliar with ffmpeg's output, it outputs encoded video information to stdout and console information to stderr. Also, when it actually gets to displaying encode information, it uses carriage returns to keep the console screen from filling up. This makes it impossible to simply use grep and awk to capture the appropriate line and frame information.

  The first thing I've tried is replacing the carriage returns using tr :

  $ ffmpeg -i "ScreeningSchedule-1.mov" -y "test.mp4" 2>&1 | tr '\r' '\n'

  This works in that it displays realtime output to the console. However, if I then pipe that information to grep or awk or anything else, tr's output is buffered and is no longer realtime. For example : $ ffmpeg -i "ScreeningSchedule-1.mov" -y "test.mp4" 2>&1 | tr '\r' '\n'>log.txt results in a file that is immediately filled with some information, then 5-10 secs later, more lines get dropped into the log file.

  At first I thought sed would be great for this : $ # ffmpeg -i "ScreeningSchedule-1.mov" -y "test.mp4" 2>&1 | sed 's/\\r/\\n/', but it gets to the line with all the carriage returns and waits until the processing has finished before it attempts to do anything. I assume this is because sed works on a line-by-line basis and needs the whole line to have completed before it does anything else, and then it doesn't replace the carriage returns anyway. I've tried various different regex's for the carriage return and new line, and have yet to find a solution that replaces the carriage return. I'm running OSX 10.6.8, so I am using BSD sed, which might account for that.

  I have also attempted to write the information to a log file and use tail -f to read it back, but I still run into the issue of replacing carriage returns in realtime.

  I have seen that there are solutions for this in python and perl, however, I'm reluctant to go that route immediately. First, I don't know python or perl. Second, I have a completely functional batch processing shell application that I would need to either port or figure out how to integrate with python/perl. Probably not hard, but not what I want to get into unless I absolutely have to. So I'm looking for a shell solution, preferably bash, but any of the OSX shells would be fine.

  And if what I want is simply not doable, well I guess I'll cross that bridge when I get there.

• How to tell ffmpeg to encode only the latest frames from input pipe (live streaming) ?

  12 mars 2018, par Valdir

  Similar question on another language : How to get the latest frames in ffmpeg, not the next frame

  Well, basically I receive a vp8 webm chunks through sockets and send it to ffmpeg stdin. My problem is that when the network slows down or temporarily stops, ffmpeg output freezes until the expected chunks arrives. When that happens I can see the output "as expected".

  The real problem is that for every glitch, ffmpeg starts to transcoding from the point it stopped, so let’s say I’m streaming my webcam and at 01:01 I have a network glitch. My chunks are still sent from browser, but never received. At this point the video live streaming (on client’s browser) is at let’s say 01:10, and after the network starts to work as expected, ffmpeg starts receiving all chunks at once since 01:01 and encodes it from that point.

  What I want is ffmpeg to encode only the latest chunks in order to keep in sync with the original video being broadcasted. So I want it to discard that part that lagged.

  It seems like the original problem comes from the socket connection, which sends packets in order and can delay depending on the connection.

• Started Programming Young

  6 septembre 2011, par Multimedia Mike — Programming

  I have some of the strangest memories of my struggles to jump into computer programming.

  Back To BASIC
  I remember doing some Logo programming on Apple II computers at school in 5th grade (1987 timeframe). But that was mostly driving turtle graphics. Then I remember doing some TRS-80 BASIC in 7th grade, circa 1989. Emboldened by what very little I had learned in perhaps the week or 2 we took in a science class to do this, I tried a little GW-BASIC on my family’s “IBM-PC compatible” computer (they were still called that back then). I still remember what my first program consisted of. Even back then I was interested in manipulating graphics and color on a computer screen. Thus :

  10 color 1
  20 print "This is color 1"
  30 color 2
  40 print "This is color 2"
  ...
  

  And so on through 15 colors. Hey, it did the job– it demonstrated the 15 different colors you could set in text mode.

  What’s FOR For ?
  That 7th grade computer unit in science class wasn’t very thick on computer science details. I recall working with a lab partner to transcribe code listings into a computer (and also saving my work to a storage cassette). We also developed form processing programs that would print instructions to input text followed by an “INPUT I$” statement to obtain the user’s output.

  I remember there was some situation where we needed a brief delay between input and printing. The teacher told us to use a construct of the form :

  10 FOR I = 1 TO 20000
  20 NEXT I
  

  We had to calibrate the number based on our empirical assessment of how long it lasted but I recall that the number couldn’t be much higher than about 32000, for reasons that would become clearer much later.

  Imagine my confusion when I would read and try to comprehend BASIC program code I would find in magazines. I would of course see that FOR..NEXT construct all over the place but obviously not in the context of introducing deliberate execution delays. Indeed, my understanding of one of the fundamental building blocks of computer programming — iteration — was completely skewed because of this early lesson.

  Refactoring
  Somewhere along the line, I figured out that the FOR..NEXT could be used to do the same thing a bunch of times, possibly with different values. A few years after I had written that color program, I found it again and realized that I could write it as :

  10 for I = 1 to 15
  20 color I
  30 print I
  40 next I
  

  It still took me a few more years to sort out the meaning of WHILE..WEND, though.