Comments

walter-i. wrote on 3/20/2020, 5:50 AM

Welcome to the forum!

As it says on the sign:
"Please describe, what you were doing in Vegas Pro, when the problem occured".
See also: https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/

Last changed by walter-i. on 3/20/2020, 5:51 AM, changed a total of 1 times.

Camcorder: Pana HDC SD909, Sony FDR-AX53
Hardware: CPU i9-9900KS 4GHz, 32 GB Ram, GTX 1660 SUPER, ASUS TUF Z390-PLUS Gaming, SSD 970 EVO Plus 500GB M.2, SSD 860 EVO Series 1TB, Toshiba 3TB SATA, WIN 10 Pro
NLE: Vegas Pro11-15+17, Heroglyph4, RespeedR

rakan-algahtani wrote on 3/20/2020, 6:05 AM

the problem occured when I put a footage in the timeline

Dexcon wrote on 3/20/2020, 6:13 AM

Please refer to the link provided by walter-i. re information that is useful to give the forum some clue as to what is happening. Please take special notice of point 1 in section C re MediaInfo. You say 'footage', but there is a huge range of types of 'footage' - so what are the specs for the footage that you are using?

rakan-algahtani wrote on 3/20/2020, 6:48 AM

I use :

VEGAS Pro 17

windows 10

64bit

 

the specs of my footages are :

JPG , mov , psd

the problem is associated with all files the I have tried.

 

Grazie wrote on 3/20/2020, 7:47 AM

You're using MOV files - yes? If these QuickTime files? You could try allowing QT files to be read in the Deprecated Tab:

"Enable the QuickTime plugin Activates the old QuickTime plugin for file compatibility with old .mov files"

Cheers - G

 

rakan-algahtani wrote on 3/20/2020, 2:46 PM

I face this problem with MOV and all other extensions.

rakan-algahtani wrote on 3/21/2020, 4:08 AM

I paid for VEGAS Pro 17 ,

I really need to use it today ,

 

help me

j-v wrote on 3/21/2020, 4:30 AM

Did you do what @Grazie asked you to do?
And still you cannot use those .mov files?
Where are all your used and unwilling files stored?
You have to give here also that MediaInfo of all used and unwilling files @walter-i.asked for, look here: https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10 home version 1909 build 18363.720, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti.
Laptop  :Asus ROG GL753VD, W10 home version 1909 build 18363.720, CPU i7 7700HQ, 8 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 16,17 and VMS PL 16,17 are installed, all latest builds
Both Nvidia GPU's have driver version 442.92 Studio Driver, desktop the Studio DHC driver
TV      :LG 4K 55EG960V

Dutch video tutorials for beginners

My slogan is: BE OR BECOME A STEMCELL DONOR !!!

Dexcon wrote on 3/21/2020, 4:36 AM

I face this problem with MOV and all other extensions.

But haven't said whether or not you have tried the 'Deprecated Features' suggestion put forward by Grazie? If you haven't, then you're not helping yourself by not doing so.

Otherwise, if you have successfully used VP17 build 421 before, what is different or new with the media you are now attempting to use as against the media you previously successfully used? Have there been any changes made to your computer recently? Or have you installed any new plugins/programs between the times when VP17 worked successfully and then unsuccessfully?

Despite the comment/request from walter-i. nearly 24 hours ago, the information you have provided so far is rather scant to say the least.

rakan-algahtani wrote on 3/21/2020, 4:40 AM

guys, I do NOT know how to (allowing QT files to be read in the Deprecated Tab)

Dexcon wrote on 3/21/2020, 4:45 AM

Deprecated Feature is accessed via Options/Preferences.

... then check the "Enable the QuickTime plugin" box. Voila!

rakan-algahtani wrote on 3/21/2020, 4:47 AM

these are from of the files that I'm using opened by MEDIAINFO ,

rakan-algahtani wrote on 3/21/2020, 4:51 AM

nothing changed even after shutting the program and run it again

vkmast wrote on 3/21/2020, 5:02 AM

See if this FAQ helps.

j-v wrote on 3/21/2020, 5:13 AM

I have no experience with mov files and for sure not if they are encoded with the h.263 mpeg4 codec, so there I can't say anything, but it should not might give any problem to use those .psd or .png stills in the program. For this maybe a complete reset of VPro 17 might help you.
Therefore you have to click the startbutton of the program with hold Ctrl +Shift buttons and choose to delete the cached files.

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10 home version 1909 build 18363.720, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti.
Laptop  :Asus ROG GL753VD, W10 home version 1909 build 18363.720, CPU i7 7700HQ, 8 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 16,17 and VMS PL 16,17 are installed, all latest builds
Both Nvidia GPU's have driver version 442.92 Studio Driver, desktop the Studio DHC driver
TV      :LG 4K 55EG960V

Dutch video tutorials for beginners

My slogan is: BE OR BECOME A STEMCELL DONOR !!!

Grazie wrote on 3/21/2020, 6:05 AM

@rakan-algahtani - Good. Deprecated is off the List.

rakan-algahtani wrote on 3/21/2020, 7:42 AM

I reinstalled Vegas Pro 17, the same problem 😔

Dexcon wrote on 3/21/2020, 7:55 AM

I reinstalled Vegas Pro 17, the same problem

That doesn't necessarily solve the problem unless you used a registry remover like CCleaner or the like before re-installing. Or reboot VP as j-v suggested.

You seem to be reluctant to provide anything other than minimum information about your problem with VP17. I go back to other relevant information I enquired abut earlier:

… if you have successfully used VP17 build 421 before, what is different or new with the media you are now attempting to use as against the media you previously successfully used? Have there been any changes made to your computer recently? Or have you installed any new plugins/programs between the times when VP17 worked successfully and then unsuccessfully?

There are many highly knowledgeable people on this forum about VP, but I respectively suggest that mind-reading is not one of those skills.

 

walter-i. wrote on 3/21/2020, 7:59 AM

There are many highly knowledgeable people on this forum about VP, but I respectively suggest that mind-reading is not one of those skills.

@Dexcon 👍😄

Camcorder: Pana HDC SD909, Sony FDR-AX53
Hardware: CPU i9-9900KS 4GHz, 32 GB Ram, GTX 1660 SUPER, ASUS TUF Z390-PLUS Gaming, SSD 970 EVO Plus 500GB M.2, SSD 860 EVO Series 1TB, Toshiba 3TB SATA, WIN 10 Pro
NLE: Vegas Pro11-15+17, Heroglyph4, RespeedR

rakan-algahtani wrote on 3/21/2020, 8:22 AM

actually I do NOT know what to give?

I shared everything I understand  

rakan-algahtani wrote on 3/21/2020, 8:29 AM

my Graphics Card Model

Dexcon wrote on 3/21/2020, 8:30 AM

actually I do NOT know what to give? I shared everything I understand  

Please show me anywhere in any of your responses where you have answered:

... if you have successfully used VP17 build 421 before, what is different or new with the media you are now attempting to use as against the media you previously successfully used? Have there been any changes made to your computer recently? Or have you installed any new plugins/programs between the times when VP17 worked successfully and then unsuccessfully?...

I give in.

rakan-algahtani wrote on 3/21/2020, 8:31 AM

Status of GPU acceleration of video processing

rakan-algahtani wrote on 3/21/2020, 8:34 AM

what else should I do ?