[GH-ISSUE #333] Video downloads cannot be imported into Vegas Pro #9027

New Issue

GiteaMirror · 2026-04-24T15:05:10-05:00

GiteaMirror commented

2026-04-24 15:05:10 -05:00

Originally created by @INNERLMNT on GitHub (Jan 25, 2024).
Original GitHub issue: https://github.com/imputnet/cobalt/issues/333

bug description
I'm a video editor and my issue is that whenever I download a video using cobalt, I'm able to import it into Adobe Premiere Pro with no problems, but I'm unable to import it into MAGIX Vegas Pro (I am using version 14.0; I'm aware the latest stable release is version 21, I'm using 14 for reverse compatibility purposes). I do not have this problem with audio, as it imports just fine.

reproduction steps

download video (settings: 1080p max, h264/mp4, progressive)
open Vegas Pro 14
start a new project
drag file into the project only to see my cursor turn into the "no" symbol (🚫) as it doesn't allow me to import the file

platform

OS: Windows 11 (version 10.0.22621)
browser: Google Chrome
Chrome version 120.0.6099.227 (Official Build) (64-bit)
Vegas Pro version 14, build number 161

Originally created by @INNERLMNT on GitHub (Jan 25, 2024). Original GitHub issue: https://github.com/imputnet/cobalt/issues/333 **bug description** I'm a video editor and my issue is that whenever I download a video using cobalt, I'm able to import it into Adobe Premiere Pro with no problems, but I'm unable to import it into MAGIX Vegas Pro (I am using version 14.0; I'm aware the latest stable release is version 21, I'm using 14 for reverse compatibility purposes). I do not have this problem with audio, as it imports just fine. **reproduction steps** 1. download video (settings: 1080p max, h264/mp4, progressive) 2. open Vegas Pro 14 3. start a new project 4. drag file into the project only to see my cursor turn into the "no" symbol (🚫) as it doesn't allow me to import the file **platform** - OS: Windows 11 (version 10.0.22621) - browser: Google Chrome - Chrome version 120.0.6099.227 (Official Build) (64-bit) - Vegas Pro version 14, build number 161

GiteaMirror added the bug label 2026-04-24 15:05:10 -05:00

GiteaMirror closed this issue

2026-04-24 15:05:11 -05:00

GiteaMirror commented

2026-04-24 15:05:12 -05:00

@lostdusty commented on GitHub (Jan 26, 2024):

Could you try remuxing the video file? Use this command: ffmpeg -i videonamehere.mp4 -c copy outvideohere.mp4.

(ffmpeg is needed)

@lostdusty commented on GitHub (Jan 26, 2024): Could you try remuxing the video file? Use this command: `ffmpeg -i videonamehere.mp4 -c copy outvideohere.mp4`. (ffmpeg is needed)

GiteaMirror commented

2026-04-24 15:05:13 -05:00

@INNERLMNT commented on GitHub (Jan 26, 2024):

Remuxing would only be a patch to the problem, but so would downloading
videos from y2mate - no remuxing necessary. Does cobalt do a certain type
of muxing that messes with the usability of the footage?

On Fri, Jan 26, 2024, 13:49 Princess Mortix @.***>
wrote:

Could you try remuxing the video file? Use this command: ffmpeg -i
videonamehere.mp4 -c copy outvideohere.mp4.

(ffmpeg is needed)

—
Reply to this email directly, view it on GitHub
https://github.com/wukko/cobalt/issues/333#issuecomment-1912020947, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BFTUYIWQZDNNQ23MCOGRJMTYQOQ7PAVCNFSM6AAAAABCLKWFCGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJSGAZDAOJUG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

@INNERLMNT commented on GitHub (Jan 26, 2024): Remuxing would only be a patch to the problem, but so would downloading videos from y2mate - no remuxing necessary. Does cobalt do a certain type of muxing that messes with the usability of the footage? On Fri, Jan 26, 2024, 13:49 Princess Mortix ***@***.***> wrote: > Could you try remuxing the video file? Use this command: ffmpeg -i > videonamehere.mp4 -c copy outvideohere.mp4. > > (ffmpeg is needed) > > — > Reply to this email directly, view it on GitHub > <https://github.com/wukko/cobalt/issues/333#issuecomment-1912020947>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/BFTUYIWQZDNNQ23MCOGRJMTYQOQ7PAVCNFSM6AAAAABCLKWFCGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJSGAZDAOJUG4> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

GiteaMirror commented

2026-04-24 15:05:13 -05:00

@wukko commented on GitHub (Jan 26, 2024):

vegas pro is severely outdated and doesn't accept modern file types, i suggest you use up-to-date software such as premiere like you mentioned

@wukko commented on GitHub (Jan 26, 2024): vegas pro is severely outdated and doesn't accept modern file types, i suggest you use up-to-date software such as premiere like you mentioned

GiteaMirror commented

2026-04-24 15:05:14 -05:00

@wukko commented on GitHub (Jan 26, 2024):

this happens because cobalt merges video and audio files together on-fly, making it impossible to predict final file length, so the length info is missing from file headers (that are obviously sent before the end).

all modern software doesn't have issues with that, but vegas pro hasn't been majorly updated since early 2010s with incremental updates not fixing core problems.

updating to latest vegas version might fix the issue, but it's just a guess based off release date.

@wukko commented on GitHub (Jan 26, 2024): this happens because cobalt merges video and audio files together on-fly, making it impossible to predict final file length, so the length info is missing from file headers (that are obviously sent before the end). all modern software doesn't have issues with that, but vegas pro hasn't been majorly updated since early 2010s with incremental updates not fixing core problems. updating to latest vegas version might fix the issue, but it's just a guess based off release date.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/cobalt#9027