Vegas with .mov files

Lerc wrote on 6/16/2019, 1:55 AM

came on here just to say this program is absolute garbage when it comes to .mov files. Nothing but trouble for over 6 years. No update. No fix. No nothing. Every single time .mov files are used in quantity in Vegas it turns black. Doesn't matter what type of .mov. Doesn't matter if its on a different PC with a newer version of Vegas. Doesn't matter what QT is installed. Doesn't matter which .dll you delete. This lack luster performance of a company so large with a problem that effects a file type that is used by most modern smart phones and cameras, and ITS STILL NOT FIXED!!??? Developers just get more and more lazy. So glad to see an expensive and "respected" piece of software like this be spaghetti coded and stuff with garbage to try and produce a new version each time that introduced new gimmicks instead of just sitting down and fixing known problems. Remember there will only be a more successful competitor to a product only if that product allows it. I use both premier and Vegas on the daily and I see ABSOLUTELY ZERO reason to purchase Vegas or premier. Wasted money, wasted time, wasted developers, wasted brain power, but it seems not very much of that was used anyway. Make a better product and you'll make more money. Best marketing there is.

Comments

tripleflip18 wrote on 6/16/2019, 2:31 AM

came on here just to say this program is absolute garbage when it comes to .mov files. Nothing but trouble for over 6 years. No update. No fix. No nothing. Every single time .mov files are used in quantity in Vegas it turns black. Doesn't matter what type of .mov. Doesn't matter if its on a different PC with a newer version of Vegas. Doesn't matter what QT is installed. Doesn't matter which .dll you delete. This lack luster performance of a company so large with a problem that effects a file type that is used by most modern smart phones and cameras, and ITS STILL NOT FIXED!!??? Developers just get more and more lazy. So glad to see an expensive and "respected" piece of software like this be spaghetti coded and stuff with garbage to try and produce a new version each time that introduced new gimmicks instead of just sitting down and fixing known problems. Remember there will only be a more successful competitor to a product only if that product allows it. I use both premier and Vegas on the daily and I see ABSOLUTELY ZERO reason to purchase Vegas or premier. Wasted money, wasted time, wasted developers, wasted brain power, but it seems not very much of that was used anyway. Make a better product and you'll make more money. Best marketing there is.

i feel same frustration with you man, i work with lots of move files and i have to friggen render many Mov files into a single long file, then go ahead and split them... seems like it can handle no more then a dozen or 2 max...

Musicvid wrote on 6/16/2019, 8:10 AM

And neither of you have posted a shred of information. This is not a support request, and not a complaint, because it contains no information. So what is this?

Start here, otherwise you are shouting at the wind.

https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

 

Kinvermark wrote on 6/16/2019, 8:42 AM

I use both premier and Vegas on the daily and I see ABSOLUTELY ZERO reason to purchase Vegas or premier.

Sounds like a self- justification for theft.

This is a poorly written troll post and should be ignored.

 

klt wrote on 6/17/2019, 3:40 PM

@Lerc

You need Shotcut. Theoretically it supports mov, and there's absolutely zero reason to purchase, as it is FREE!

If you use Vegas daily you already purchased it. If you use Premier daily, you are paying a monthly fee for Adobe. If you use cracked (stolen) versions, stop complaining about anything. You can't be sure what code the "cracker" has overwritten, and/or what code that cracker (even malicious) has added, and that can introduce nasty thing to your system.

😝

 

klt wrote on 6/17/2019, 3:46 PM

@tripleflip18

You can rewrap (almost) any .mov to mp4 with ffmpeg.

The command line is so complex:

ffmpeg -i input.mov -vcodec copy -acodec copy output.mp4

If you have Vegas newer than V14, the codecs should just work.

With V13 (and probably before) there were not all codecs working after rewrap, some of them Vegas interpreted just as flat green.

Give it a try!

 

wwaag wrote on 6/18/2019, 8:35 PM

@klt

Please note that your command line does not work if your mov file contains pcm audio. You will have to transcode to aac or render a new wave file. Unfortunately, FFmpeg does not "allow" pcm audio within the mp4 container. In the newer versions of FFmpeg, you cannot even trim an mp4 file with pcm audio that typically comes from a Sony or Panasonic camera. There have been quite a few complaints on the forums, but the developers seem to be pretty adamant regarding the container specs. Too bad.

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

aboammar wrote on 6/18/2019, 8:59 PM

I use both premier and Vegas on the daily and I see ABSOLUTELY ZERO reason to purchase Vegas or premier.

Sounds like a self- justification for theft.

This is a poorly written troll post and should be ignored.

 

Agreed.. It's weird when a person use cracked (stolen) versions and have the face to complain 😲

HP Z1 AIO Workstation G3

OS: Windows 10 Pro 64bit

Display: 23.6" UHD 4K

CPU: Xeon E3-1270 v5  quad-core @ 3.60GHz, 8MB cache, up to 4GHz with Intel Turbo Boost Technology

GPU: nVidia Quadro M2000M 4GB

RAM: 32GB DDR4 2133MHz ECC memory

System Drive: 1TB M.2 (2500MB/s)

Working Drive: 1TB M.2 (2500MB/s)

Storage Drive: 3GB SSD (500MB/s)

Video: Vegas Pro 16 Suite / DaVinci Resolve 16 Studio

Audio: PreSonus Studio One Pro 5

Graphics: CorelDraw Technical Suite 2020 / Xara Designer Pro X365

Image Editing: Corel PhotoPaint 2020 / Corel PaintShop Pro X9 Ultimate / PHASEONE Capture One Pro 11

3D Graphics: Maxon Cinema 4D Studio 10

Camera: Sony A7S II / A7 III

Website: www.innoviahouse.com

Vimeo: vimeo.com/innoviahouse

Fresh wrote on 6/18/2019, 9:25 PM

I have paid for my copy of Sony Vegas Pro 16 and overall i'm satisfied and want to love it, but truth be told, it keeps giving me grief. I tend to agree with the notion of slick marketing and new gimmicks without addressing the core issues. I fell for it with Vegas 14 and the automatic audio 'synchronization' which ended up never working as advertised. I still don't understand why the little yellow render carats that designate the render boundaries in Sony Vegas Pro 16 don't get saved with the project. It's maddening to have to set those, especially after the program crashed during a render. Last week, after rendering, the entire project mysteriously disappeared from my hard drive. Fortunately, i had a backup on an external drive. Now, when i go to render that project, instead of being 830 Megabites like the file whose project went missing, it renders to some astronomical size, basically filling the hard drive (20 gigs free) and crashing the software. I am working around all of these issues, still, I hope the developers will stay on track and try to fix the core issues, many of which seem well documented by users.

Kinvermark wrote on 6/18/2019, 9:48 PM

Sorry @Fresh but all this sounds a lot like "pilot error." Project files don't mysteriously get deleted unless your system is broken. Render controls are all there for YOU to set - you must have done something you didn't intend.

And it is very easy to save a region: Hit the R key and give it a name (or not). Done.

If you want some help from the forum on other issues, then please make a new thread and post all the relevant technical details. Many here are happy to help!

 

klt wrote on 6/19/2019, 12:53 AM

Thanks @wwaag,

I knew certain codecs possible in mov don't work in mp4. That's why I wrote "almost" :)

But I wasn't aware of this audio issue... So thanks for the warning! 😉

john-baker wrote on 6/19/2019, 8:12 AM

@Fresh!

Hi

I agree with @Kinvermark about 'Project files don't mysteriously get deleted' however there is another possibility from your comment

. . . it renders to some astronomical size . . . filling the hard drive (20 gigs free) . . . .

Is this the actual free space before rendering the video and what size are the drive(s)?

John EB

Lateral thinking can get things done!

VP 21, DVD Architect 7 build 100, Video Pro X 16, Movie Studio 2025,

PC :Windows 11 23H2 Professional  on Intel i7-8700K 3.2 GHz, 16Gb RAM, RTX 2060 6GB 192-bit GDDR6, 1Tb + 2 x 2Tb internal HDD + 4 Tb internal SSD (work disc),

Laptop: Lenovo Legion 5i Phantom - running Windows 11 23H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53 Video camera, Osmo Action 3 and Sony HDR-AS30V Sports cams.