Opened 12 years ago
Closed 12 years ago
#2630 closed defect (fixed)
Log output is blocking
| Reported by: | bjartnes | Owned by: | |
|---|---|---|---|
| Priority: | normal | Component: | ffplay |
| Version: | git-master | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Reproduced by developer: | no | |
| Analyzed by developer: | no |
Description (last modified by )
Not sure if this is labelled a bug or more a new feature/feature change but it was mentioned that it might should be raised with ffmpeg.
The issue is that when I pipe video in node.js to a ffplay child-process the log output is blocking. This means that after a while playing the video will halt because the output buffer from stdout fills up with progress information. It's easy to work around, but it was claimed that it seems unnescessary to block on log output. I myself have no strong opinions on the issue, but I thought I should bring it up.
Change History (5)
comment:1 by , 12 years ago
comment:2 by , 12 years ago
| Keywords: | log output blocking removed |
|---|---|
| Priority: | minor → normal |
| Type: | enhancement → defect |
| Version: | 1.1.5 → git-master |
Command line and complete, uncut console output missing.
I wanted to write "aren't you searching for -loglevel 0 ?" but there appears to be a bug in ffplay iiuc.
comment:3 by , 12 years ago
I may misunderstand the ticket, but you could test this patch with -loglevel 30 (or smaller):
http://thread.gmane.org/gmane.comp.video.ffmpeg.devel/164562
comment:4 by , 12 years ago
| Description: | modified (diff) |
|---|
comment:5 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
I believe this bug should be fixed since 3b491c5 but as said I may misunderstand, please reopen this ticket if the problem is still reproducible with git head.
blog=>block. Could not find edit button.