You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I do not know if this is a bug or a technical limitation.
I've been using ffmpeg-bar for a while without any issue via the Ubuntu bash on Windows 10.
I've just experienced the first hickup. The progression bar isn't being displayed when I use the concat format to merge multiple files of the same codec together.
The vidlist.txt file contains the path of the video files to be merged together.
The files are being processed and merged in the backend, but the frontend doesn't let you know about it. I first though my command wasn't working, until I realized that the ffmpeg command was working, but only the ffmpeg-bar wasn't displaying.
As I said, it might be technically impossible to have the progress bar in this situation, since multiple files, one after the other, are being joined together. But I though I should ask nonetheless. :)
Thanks,
Phil
The text was updated successfully, but these errors were encountered:
Hello,
I do not know if this is a bug or a technical limitation.
I've been using ffmpeg-bar for a while without any issue via the Ubuntu bash on Windows 10.
I've just experienced the first hickup. The progression bar isn't being displayed when I use the concat format to merge multiple files of the same codec together.
Here's the command I'm using:
ffmpeg-bar -f concat -i vidlist.txt -c copy outputfile.MP4
The vidlist.txt file contains the path of the video files to be merged together.
The files are being processed and merged in the backend, but the frontend doesn't let you know about it. I first though my command wasn't working, until I realized that the ffmpeg command was working, but only the ffmpeg-bar wasn't displaying.
As I said, it might be technically impossible to have the progress bar in this situation, since multiple files, one after the other, are being joined together. But I though I should ask nonetheless. :)
Thanks,
Phil
The text was updated successfully, but these errors were encountered: