VEGAS Pro 17 Update 1 (build 321) - General Discussion

Comments

BobMoyer wrote on 10/5/2019, 9:52 AM

@Ralf, you are not alone on this forum, either with your use of Win7 or the voiced opinion "upgrade" your OS. I honestly did not notice when purchasing VP17 that Win10 was required, mostly because Win7 is still in wide use and until January still supported by MS. My fault totally but for various reasons I cannot change OS now and I cannot afford to purchase another system just for VP17. And actually, I purchased VP16 with a free upgrade to VP17 when released. No where on that offer did it mention that Win10 was required.

j-v wrote on 10/5/2019, 10:10 AM

Windows 7 users are more than once offered to update for free to W10.
I used the very latest offer and never has regretted it.
Even with the latest builds you can switch automatic update off and after 1 month use I was completely boss again over my own hardware in spite of how Windows tries to retake that task. Simply by ignoring all the so called " Safety Warnings" of Windows.
I am able to use all my Vegas versions from version 10 till VP 17 b 321, simply by installing them in the comptability mode for the Windows version they were made for.

 

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 23H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
560.81 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2127
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 560.81 and Intel UHD Graphics 630 with driver 31.0.101.2127
Vegas software: VP 10 to 21 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

Rich Parry wrote on 10/5/2019, 5:35 PM

I'm not refuting BobMeyer comment. I didn't know W10 was required either. Magix now clearly states W10 is required. I loved W7 but when VP17 was released I reluctantly moved to W10. I paid full price $199.

https://www.vegascreativesoftware.com/us/vegas-pro/specifications/

Rich

CPU Intel i9-13900K Raptor Lake

Heat Sink Noctua  NH-D15 chromas, Black

MB ASUS ProArt Z790 Creator WiFi

OS Drive Samsung 990 PRO  NVME M.2 SSD 1TB

Data Drive Samsung 870 EVO SATA 4TB

Backup Drive Samsung 870 EVO SATA 4TB

RAM Corsair Vengeance DDR5 64GB

GPU ASUS NVDIA GeForce GTX 1080 Ti

Case Fractal Torrent Black E-ATX

PSU Corsair HX1000i 80 Plus Platinum

OS MicroSoft Windows 11 Pro

Rich in San Diego, CA

crofter wrote on 10/6/2019, 4:04 AM

For those wishing to upgrade,the upgrade from Win 7,8 is still free,just download the update assistant and off you go.well worth it in my estimation.

BobMoyer wrote on 10/6/2019, 8:22 AM

Would you have a link to this download?

crofter wrote on 10/6/2019, 8:27 AM

https://www.microsoft.com/en-gb/software-download/windows10

Click "download tool now",Plenty of stuff on the net about doing the upgrade.

BobMoyer wrote on 10/6/2019, 8:46 AM

Thank you.

AlesCZ wrote on 10/6/2019, 11:07 AM

4K 60fps video cannot be edited in this version. Within seconds, the preview will be slow down from 60fp to almost 0fps.
4K 30fps(or slow down 60fps footages to 0,5 playback rate) works fine, stable 30fps preview.

j-v wrote on 10/6/2019, 11:54 AM

4K 60fps video cannot be edited in this version. Within seconds, the preview will be slow down from 60fp to almost 0fps.
4K 30fps(or slow down 60fps footages to 0,5 playback rate) works fine, stable 30fps preview.

4k 50p HEVC can with me in VP 17 b 321 in full preview

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 23H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
560.81 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2127
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 560.81 and Intel UHD Graphics 630 with driver 31.0.101.2127
Vegas software: VP 10 to 21 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

joost-berk wrote on 10/6/2019, 12:42 PM

Not new codecs for exportation video ! I'm sad !


@KaraUSA What different codec do you need that is not yet available in Vegas Pro 17 (build 321)?

Vegas Pro user since version 1.2

OS: Windows 10 Pro (Latest version)

CPU: AMD Ryzen 7 3800X

RAM: 32GB DDR4 3200MHz

GPU: Nvidia GeForce RTX 2080 Super 8GB GDDR (Latest Studio Driver)

Monitoring: Black Magic Design DeckLink SDI 4K (or Nvidia HDMI for 4K HDR)

Audio: M-Audio M-Track Eight ASIO

Controller: Behringer X-Touch

Kinvermark wrote on 10/6/2019, 12:46 PM

@AlesCZ

You should post a detailed MEDIAINFO report of your problem media to make it easier for the developers to reproduce the issue. And open a tech support ticket if you can spare the time.

Ralf wrote on 10/6/2019, 1:02 PM

@Ralf, you are not alone on this forum, either with your use of Win7 or the voiced opinion "upgrade" your OS. I honestly did not notice when purchasing VP17 that Win10 was required, mostly because Win7 is still in wide use and until January still supported by MS. My fault totally but for various reasons I cannot change OS now and I cannot afford to purchase another system just for VP17. And actually, I purchased VP16 with a free upgrade to VP17 when released. No where on that offer did it mention that Win10 was required.

Thank you Bob. I'll apologize for my rather blunt response to @Dexcon, it's just that that I've been harangued for an inestimable time regarding W7 and it's tiresome to have to have that thrust in one's face continually. I was tired, hadn't had coffee and reacted badly. I'm sorry.

I too fell into purchasing VP17 (suite) and only discovered the support issue afterwards. I'm not inclined to switch to W10 until absolutely forced to. I have deep reservations as to the QA, privacy, and frankly... angry with the shenanigans that MS foisted on us to try and "upgrade". Even now, they're obfuscating local logins in order to try and funnel every one to accept an online login for their OS. Unconscionable, IMHO.

I will ultimately need to bend as, well, Internet and "bad things". I just wish MS would treat users with some modicum of respect.

As I said, I bought Vegas without realizing initially that support wouldn't be offered for W7. I didn't come here looking for support from Magix. I came here looking for support from the excellent community surrounding the product -- which I feel is the best, deepest, I have ever had the privilege to make use of.

I do think, speaking as someone with a background of some training in programming and electronic engineering, that the shut down behaviour as currently exhibited in W7 (not correctly terminating) is something that may point to issues occurring in W10 as well. After all, W10 isn't a complete re-write and much still harkens to W7.

As to direct support for the program (VP17), I'm not overly concerned. My system isn't about to bow to this or any other program. That's how I built it.

AlesCZ wrote on 10/6/2019, 1:05 PM

Format                                   : MPEG-4
Format profile                           : JVT
Codec ID                                 : avc1 (avc1/isom)
File size                                : 203 MiB
Duration                                 : 12 s 29 ms
Overall bit rate mode                    : Variable
Overall bit rate                         : 142 Mb/s
 

It is strange if only I have this problem.

Kinvermark wrote on 10/6/2019, 1:08 PM

"Incorrect termination" however defined is still an issue in Windows 10 - for some users. Developers are completely aware of it and have been trying to solve it on-and-off for many versions. Must be a tough one - as are many other old Vegas bugs. Fortunately it is more irritant than roadblock.

Kinvermark wrote on 10/6/2019, 1:10 PM

@AlesCZ

Thats not a MEDIAINFO report. Free utility. Google it. Need more detail - as per Fiola's thread.

I ask you same question as him: can you cause a crash with just one small piece of this media?

AlesCZ wrote on 10/6/2019, 1:25 PM

@AlesCZ

Thats not a MEDIAINFO report. Free utility. Google it. Need more detail - as per Fiola's thread.

I ask you same question as him: can you cause a crash with just one small piece of this media?

This is from the Mediainfo software. No crash yet. But after the update I have not edited any project yet. I just tried the performance.
It looks like the disk read bit rate is failing. But I tried files from several drives and I use SSD. Strangely, if I try to slow down the video, the preview plays stable 30fps (project set to 30fps). If I play a video that is recorded at 60fps in a project set to 30fps without slowing down, it happens that the video runs out very quickly. If I slow down the video to 30fps, there's no problem.
My setup:
i7 4790k, GTX 1080, GTX 1070, 16GB RAM, Win10 64bit
Yes, the 4790k is an older processor, but I create 3D animations, VFX, create graphics, create music, sometimes I play flight simulators. No problem. It is still a good CPU.

EDIT.: Davinci Resolve has a similar problem. That means I have a problem in the system, maybe :/
OK, so far I'll try it resolving myself.
Thanks!

Kinvermark wrote on 10/6/2019, 4:06 PM

Well, that's a bit of a turnaround @AlesCZ . You first claimed absolutely that -

4K 60fps video cannot be edited in this version

Which is a very broad statement, that you now say is not true.

And the info you provided about your media was very minimal - too minimal to be useful for troubleshooting.

If you revisit this issue in future , please provide a FULL LISTING from MEDIAINFO and preferably a test file if possible.

j-v wrote on 10/6/2019, 4:18 PM

😁

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 23H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
560.81 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2127
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 560.81 and Intel UHD Graphics 630 with driver 31.0.101.2127
Vegas software: VP 10 to 21 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

Former user wrote on 10/6/2019, 7:23 PM


It looks like the disk read bit rate is failing. But I tried files from several drives and I use SSD. Strangely, if I try to slow down the video, the preview plays stable 30fps (project set to 30fps). If I play a video that is recorded at 60fps in a project set to 30fps without slowing down, it happens that the video runs out very quickly. If I slow down the video to 30fps, there's no problem.
 

I've always had that problem, not being able to playback anything above 4k30p. So slow it's unusable 1fps etc. I had hoped upgrade to vp17 would fix that with the hardware decoding. I have a similarly old I7 but mine is much slower, I would have thought a 4-4.4ghz(factory) chip would be ok. I get near 100% CPU on playback, do you also?

I also have the same situation with the video playing fine briefly then unusable. If I then pause and playback a few times from that point the video will play fine again for brief period. This is a similar situation to when vegas stutters at transitions, if you playback a few times it becomes smooth, so likely your computer can't playback 60fps, it's the cache it can playback

Kinvermark wrote on 10/6/2019, 9:47 PM

@Former user

Yes, likley it is cached playback. You can increase the period of "good" playback a little by increasing dynamic RAM amount in preferences, even if you don't make a SHIFT-B preview. Best, however, is to let Vegas make a proxy, then it should playback OK (It does on my low spec machine - see signature.)

AlesCZ wrote on 10/7/2019, 12:07 AM


It looks like the disk read bit rate is failing. But I tried files from several drives and I use SSD. Strangely, if I try to slow down the video, the preview plays stable 30fps (project set to 30fps). If I play a video that is recorded at 60fps in a project set to 30fps without slowing down, it happens that the video runs out very quickly. If I slow down the video to 30fps, there's no problem.
 

I've always had that problem, not being able to playback anything above 4k30p. So slow it's unusable 1fps etc. I had hoped upgrade to vp17 would fix that with the hardware decoding. I have a similarly old I7 but mine is much slower, I would have thought a 4-4.4ghz(factory) chip would be ok. I get near 100% CPU on playback, do you also?

I also have the same situation with the video playing fine briefly then unusable. If I then pause and playback a few times from that point the video will play fine again for brief period. This is a similar situation to when vegas stutters at transitions, if you playback a few times it becomes smooth, so likely your computer can't playback 60fps, it's the cache it can playback

Yes, that's exactly the situation.

AlesCZ wrote on 10/7/2019, 12:29 AM

Well, that's a bit of a turnaround @AlesCZ . You first claimed absolutely that -

4K 60fps video cannot be edited in this version

 

I thought it was caused by an update. I guess I have a cache problem. The quality of the preview has no effect at all.

Kinvermark wrote on 10/7/2019, 9:44 AM

Let Vegas make an internal proxy. That help?

AlesCZ wrote on 10/7/2019, 9:54 AM

This is strange:

Here is the sample download: http://leteckaposta.cz/912397968