links
if applicable, add links that cause the issue. more = better.
platform
Windows 11 21H2
Chrome
version 123.0.6312.106, stable
additional context
Cobalt issue or VEGAS issue? I've tried other downloaders and the video output seems to work fine in VEGAS, but not with Cobalt.
Originally created by @cysjunk on GitHub (Apr 6, 2024).
Original GitHub issue: https://github.com/imputnet/cobalt/issues/420
**bug description**
VEGAS Pro reads any YouTube videos I download in Cobalt at an extremely high frame rate which makes it so that I can't edit the video.
**reproduction steps**
steps to reproduce the behavior:
1. go to cobalt.tools
2. click on the URL bar and paste the video link
3. download this video: https://www.youtube.com/watch?v=x-ENzR_bD6M
4. open VEGAS Pro
5. import video
**screenshots**
**links**
if applicable, add links that cause the issue. more = better.
**platform**
- Windows 11 21H2
- Chrome
- version 123.0.6312.106, stable
**additional context**
Cobalt issue or VEGAS issue? I've tried other downloaders and the video output seems to work fine in VEGAS, but not with Cobalt.
The downloaded webm video is missing the duration in it's metadata so media player will not be able to calculate the time duration, my current solution was just do stream copy locally with ffmpeg or something, with Linux we can quickly fixed this problem by running these simple command:
ffmpeg -i video.webm -c copy fixed-video.webm
I'm not sure why cobalt not post-processing downloaded video yet.
<!-- gh-comment-id:2041208778 -->
@bramaudi commented on GitHub (Apr 6, 2024):
Is your downloaded video are in **webm** format?
The downloaded webm video is missing the duration in it's metadata so media player will not be able to calculate the time duration, my current solution was just do stream copy locally with ffmpeg or something, with Linux we can quickly fixed this problem by running these simple command:
```bash
ffmpeg -i video.webm -c copy fixed-video.webm
```
I'm not sure why **cobalt** not post-processing downloaded video yet.
vegas, just like all outdated software, can't calculate file length based on actual media data. this is why it gets confused.
this can be fixed by:
using newer software
ffmpeg -i filehere.mp4 -c copy outfilehere.mp4
<!-- gh-comment-id:2041289124 -->
@wukko commented on GitHub (Apr 7, 2024):
vegas, just like all outdated software, can't calculate file length based on actual media data. this is why it gets confused.
this can be fixed by:
1. using newer software
2. `ffmpeg -i filehere.mp4 -c copy outfilehere.mp4`
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @cysjunk on GitHub (Apr 6, 2024).
Original GitHub issue: https://github.com/imputnet/cobalt/issues/420
bug description
VEGAS Pro reads any YouTube videos I download in Cobalt at an extremely high frame rate which makes it so that I can't edit the video.
reproduction steps
steps to reproduce the behavior:
screenshots
links
if applicable, add links that cause the issue. more = better.
platform
additional context
Cobalt issue or VEGAS issue? I've tried other downloaders and the video output seems to work fine in VEGAS, but not with Cobalt.
@bramaudi commented on GitHub (Apr 6, 2024):
Is your downloaded video are in webm format?
The downloaded webm video is missing the duration in it's metadata so media player will not be able to calculate the time duration, my current solution was just do stream copy locally with ffmpeg or something, with Linux we can quickly fixed this problem by running these simple command:
I'm not sure why cobalt not post-processing downloaded video yet.
@cysjunk commented on GitHub (Apr 6, 2024):
VEGAS doesn't support webm so I use mp4 format.
@wukko commented on GitHub (Apr 7, 2024):
vegas, just like all outdated software, can't calculate file length based on actual media data. this is why it gets confused.
this can be fixed by:
ffmpeg -i filehere.mp4 -c copy outfilehere.mp4