Comments

Howard-Vigorita wrote on 7/7/2019, 10:07 AM

@JN_ agreed that converting the original red car footage to 4k probably isn't representative of footage coming out of a 4k camera. But I have to disagree on using fixed frame rate unless no one can play vfr. The original red car bench was designed to make Sony's XDCAM format shine on encoding but it produced overly large mp4 files which is probably why it never caught on. I only quote its numbers for comparison over the years which obviously cannot apply to 4k performance so we should probably forget about it for that. Looks like the default amd/vce template was used for clip #2 and it plays and runs fine on all my systems. In my PCs I have run Vegas 16 with a Radeon VII and RX580. I also tried it on a NUC with an AMD Vega-M (Vegas 16) and a Microsoft Surface laptop (Vegas 13) which has a combo Intel HD 520 plus Nvidia GeForce but I select the Intel GPU in Vegas. Wonder if it's amd gpu sensitive. That might put a crimp in deliverables using that encoder.

Laptop: Dell XPS15-9570; i7-8750h 32gb (integrated Intel UHD-630 & Nvidia GTX-1050Ti)
Road: Intel NUC i7 8809g 32gb (integrated AMD VegaM 4gb graphics and Intel HD630)
Workstation: i9 9900k 32 gb (Sapphire AMD Radeon VII 16gb graphics and integrated Intel UHD630)
Workstation2: e5 1650v4 128 gb (Sapphire Nitro+ RX580 8gb graphics)
Workstation3: i7-980X 24gb (Sapphire RX480 4gb graphics)
currently Vegas 16, testing Vegas 17

JN_ wrote on 7/7/2019, 12:27 PM

@Howard-Vigorita “it plays and runs fine on all my systems”,

Ok good for you. But you know, the 4K benchmark isn't just for your system.

Ive lost count of the number of users that come on this forum with a playback issue that is sometimes down to variable frame rate media. I’ve never participated in solutions of this type, but the gurus here, once mediainfo shows it as vfr, often suggest to convert to an intermediary fixed frame rate, and then for the users to proceed from there. VP is getting better at vfr to be sure, but its still an issue, but not on your systems.

None of the 3 main original source media was vfr, so why convert one of them to vfr?

The 4K benchmark is for all users, not just those that don’t have an issue with vfr.

Thanks for going to the trouble of putting it together and making it available for download.

Good luck with the takeup.

 

Desktop and Laptop basic specs ...

Both run Win 10, has latest updates ...

Running latest ver. of Vegas Pro with latest updates.

VP13 B453 also.

Vegaseur and Pluraleyes installed on both ...

Quicktime 7.79.80.95

PC ...

i9 9900K, Intel Graphics 630. Nov 2018.

Mem. 32gb DDR4

Graphics card .. Nvidia Rtx 2080 Ti

Nvidia Graphics driver .. latest Studio driver.

Latest Intel Graphics driver

 

Laptop ... (Acer Predator G9-793-77AC)

CPU .. i7-6700HQ Skylake-H

Memory ..16GB DDR4 

Graphics card .. Nvidia GTX 1070, latest Studio driver.

Kinvermark wrote on 7/7/2019, 12:47 PM

I agree that using variable frame rate media is not ideal for a test standard. It's just a little too non-standard.

Honestly, while I absolutely applaud the effort of various forum members to get this project off the ground, I think we will need some leadership from Magix here, otherwise we will never all agree, and there needs to be some way to host the large 4k test project anyway.

I will add "test project" as a feature requests thread.

Grazie wrote on 7/7/2019, 1:40 PM

O...K.... Will somebody please pour some logic lotion onto Region 5? What is in that R5 that is choking my brand new PC? My PC Builder-Agent has no idea why this is happening. My PC is fast and sensationally strong. We both watched the Task Manger Graphs as the PC did NOT break into a sweat. Oh yes, switching off GPU made for a judder-dummy.

Grazie

PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti

PC 10 64-bit 64gb * Intel® Core™i9 - 3.3GHz * 40Gb NVIDIA  GeForce RTX 2070

Cameras: Canon XF300 + PowerShot SX60HS Bridge

Kinvermark wrote on 7/7/2019, 1:52 PM

Region 5 media has 0.632 playback rate and some PNG titles with a chroma keyer effect.

You could try turning FX off and/or playback set back to 1.0.

If it were me, I would borrow another graphics card. Might be an NVIDIA thing. Or not. :)

 

 

Howard-Vigorita wrote on 7/7/2019, 2:47 PM

@Howard-Vigorita “it plays and runs fine on all my systems”,

Ok good for you. But you know, the 4K benchmark isn't just for your system.

@JN_ Well I guess I was wrong about the usefulness of the 4k red car bench. It highlighted a limitation of your system. I think posting your results with notice of what you had to do to run it is fine for now. All the clips are vbr, btw, so you're way off base about that. Even the clip#3 which looks like ProRes_KS and resembles the native format of certain Canon cameras like the 5DS I'm looking at. I didn't know anyone still did anything with fixed bit rate in a compression format anymore because it kind of defeats the purpose. An easier workaround for anyone else that cannot process clip#2 (AMD VCE) would be to just copy clip#1 (MainConcept h.264) over clip#2... they are all the same clip just in different compression formats. Another possibility is to copy clip#3 over both clip#1 and clip#2... that clip is the very large low compression ProRes for the 4K version as compared to Sony MXF in the original.

Last changed by Howard-Vigorita on 7/7/2019, 2:51 PM, changed a total of 1 times.

Laptop: Dell XPS15-9570; i7-8750h 32gb (integrated Intel UHD-630 & Nvidia GTX-1050Ti)
Road: Intel NUC i7 8809g 32gb (integrated AMD VegaM 4gb graphics and Intel HD630)
Workstation: i9 9900k 32 gb (Sapphire AMD Radeon VII 16gb graphics and integrated Intel UHD630)
Workstation2: e5 1650v4 128 gb (Sapphire Nitro+ RX580 8gb graphics)
Workstation3: i7-980X 24gb (Sapphire RX480 4gb graphics)
currently Vegas 16, testing Vegas 17

Grazie wrote on 7/7/2019, 2:54 PM

Region 5 media has 0.632 playback rate and some PNG titles with a chroma keyer effect.

@Kinvermark - Yup, I noticed that.

You could try turning FX off and/or playback set back to 1.0.

@Kinvermark - This doesn't get to the nub of the issue.

If it were me, I would borrow another graphics card. Might be an NVIDIA thing. Or not. :)

@Kinvermark - I know you wish to help, but this is niether an option nor plausible

The Techs are going into a huddle about this tomorrow. I hope they come up withsomething.

Region 5 plays fine on Preview half.

 

Grazie

PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti

PC 10 64-bit 64gb * Intel® Core™i9 - 3.3GHz * 40Gb NVIDIA  GeForce RTX 2070

Cameras: Canon XF300 + PowerShot SX60HS Bridge

Howard-Vigorita wrote on 7/7/2019, 3:12 PM

@Grazie Have you narrowed down the issue to track 5 or track 6? If you mute one of them and try again you'll find out which is blowing you up. Track 5 has the png file and track 6 is a color gradient. Don't know that'll solve it but it'll tell you what to look more closely at. Maybe the png media file is damaged or zero-length. Try and view it without Vegas.

Laptop: Dell XPS15-9570; i7-8750h 32gb (integrated Intel UHD-630 & Nvidia GTX-1050Ti)
Road: Intel NUC i7 8809g 32gb (integrated AMD VegaM 4gb graphics and Intel HD630)
Workstation: i9 9900k 32 gb (Sapphire AMD Radeon VII 16gb graphics and integrated Intel UHD630)
Workstation2: e5 1650v4 128 gb (Sapphire Nitro+ RX580 8gb graphics)
Workstation3: i7-980X 24gb (Sapphire RX480 4gb graphics)
currently Vegas 16, testing Vegas 17

Grazie wrote on 7/7/2019, 3:36 PM

@Grazie Have you narrowed down the issue to track 5 or track 6? If you mute one of them and try again you'll find out which is blowing you up. Track 5 has the png file and track 6 is a color gradient. Don't know that'll solve it but it'll tell you what to look more closely at. Maybe the png media file is damaged or zero-length. Try and view it without Vegas.

Something in that Region 5. Cut that Region5 out, and all is fine. I’ve even got a separate Region 5 Veg purely to see if it is messing with me.

Bottom line, “others” don’t have an issue with Region 5.

Grazie

PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti

PC 10 64-bit 64gb * Intel® Core™i9 - 3.3GHz * 40Gb NVIDIA  GeForce RTX 2070

Cameras: Canon XF300 + PowerShot SX60HS Bridge

JN_ wrote on 7/7/2019, 3:51 PM

@Howard-Vigorita “it plays and runs fine on all my systems”,

Ok good for you. But you know, the 4K benchmark isn't just for your system.

@JN_ Well I guess I was wrong about the usefulness of the 4k red car bench. It highlighted a limitation of your system. I think posting your results with notice of what you had to do to run it is fine for now. All the clips are vbr, btw, so you're way off base about that. Even the clip#3 which looks like ProRes_KS and resembles the native format of certain Canon cameras like the 5DS I'm looking at. I didn't know anyone still did anything with fixed bit rate in a compression format anymore because it kind of defeats the purpose. An easier workaround for anyone else that cannot process clip#2 (AMD VCE) would be to just copy clip#1 (MainConcept h.264) over clip#2... they are all the same clip just in different compression formats. Another possibility is to copy clip#3 over both clip#1 and clip#2... that clip is the very large low compression ProRes for the 4K version as compared to Sony MXF in the original.

@Howard-Vigorita  ... “All the clips are vbr, btw, so you're way off base about that.”

 

Now you’re confusing fixed bit rate with fixed frame rate.

The issue with one of your converted clips is that its a variable frame rate, I never said anything about variable bit rate.

Last changed by JN_ on 7/7/2019, 4:00 PM, changed a total of 1 times.

 

Desktop and Laptop basic specs ...

Both run Win 10, has latest updates ...

Running latest ver. of Vegas Pro with latest updates.

VP13 B453 also.

Vegaseur and Pluraleyes installed on both ...

Quicktime 7.79.80.95

PC ...

i9 9900K, Intel Graphics 630. Nov 2018.

Mem. 32gb DDR4

Graphics card .. Nvidia Rtx 2080 Ti

Nvidia Graphics driver .. latest Studio driver.

Latest Intel Graphics driver

 

Laptop ... (Acer Predator G9-793-77AC)

CPU .. i7-6700HQ Skylake-H

Memory ..16GB DDR4 

Graphics card .. Nvidia GTX 1070, latest Studio driver.

Kinvermark wrote on 7/7/2019, 4:42 PM

@Grazie

Turning off FX or resetting clip timing are intended to isolate & identify the scope of the problem. Then you can decise wether or not you want to live with it.

Seems to me there are only two real options: 1) ignore the "problem" as relatively unimportant and hope that it does not affect your own projects. 2) Try something to fix it. Either one may be valid.

I would think a relatively likely and easy thing to change is the GPU, so that's where I would start. You could temporarily scavenge one from your old system, or get your PC Builders to give you one to try - seems like they would do this just as customer support, given that they likely have spare parts lying around anyway.

 

Kinvermark wrote on 7/7/2019, 4:44 PM

@JN_

FYI, I started a thread re: 4k Test project, in case you want to comment there.

Howard-Vigorita wrote on 7/7/2019, 4:49 PM

@JN_ Sorry, I assumed you meant variable bit rate because none of the files are supposed to be variable frame rate. I know who made the file and I'll see if I can recreate a file with the (VFR) notation in the Vegas properties screen... odd that none of the other video info tools I have say that (ffprobe, mpc-hc,vlc, etc)

Laptop: Dell XPS15-9570; i7-8750h 32gb (integrated Intel UHD-630 & Nvidia GTX-1050Ti)
Road: Intel NUC i7 8809g 32gb (integrated AMD VegaM 4gb graphics and Intel HD630)
Workstation: i9 9900k 32 gb (Sapphire AMD Radeon VII 16gb graphics and integrated Intel UHD630)
Workstation2: e5 1650v4 128 gb (Sapphire Nitro+ RX580 8gb graphics)
Workstation3: i7-980X 24gb (Sapphire RX480 4gb graphics)
currently Vegas 16, testing Vegas 17

JN_ wrote on 7/7/2019, 5:10 PM

@Howard-Vigorita

I used the tool mediainfo.

If the original file "Mercedes Clip 2 MPEG-2 XDCAM EX 1080p30.mp4" is rendered out to a 4K version using Nvenc then it'll automatically become VFR.  I don't have VCE, maybe the same happens.

To overcome this Nvenc bug I had to render it out using Mainconcept, CPU only encoding, not HW encoding, then its output as CFR.

I then did some tests, with my near 8GB project, posted earlier.

Last changed by JN_ on 7/7/2019, 5:25 PM, changed a total of 4 times.

 

Desktop and Laptop basic specs ...

Both run Win 10, has latest updates ...

Running latest ver. of Vegas Pro with latest updates.

VP13 B453 also.

Vegaseur and Pluraleyes installed on both ...

Quicktime 7.79.80.95

PC ...

i9 9900K, Intel Graphics 630. Nov 2018.

Mem. 32gb DDR4

Graphics card .. Nvidia Rtx 2080 Ti

Nvidia Graphics driver .. latest Studio driver.

Latest Intel Graphics driver

 

Laptop ... (Acer Predator G9-793-77AC)

CPU .. i7-6700HQ Skylake-H

Memory ..16GB DDR4 

Graphics card .. Nvidia GTX 1070, latest Studio driver.

Howard-Vigorita wrote on 7/7/2019, 5:40 PM

That's interesting... varying between 29.97 and 30. I've been doing various render tests and cannot get anything to come up with (VFR) in the Vegas properties screen no matter what I do. Thought it might be one of those boxes to let the source control the frame rate but nope. Wonder if a Vegas update changed something with the the AMD VCE encoder. Did you just re-render it with the standard Magix AVC - 4K 2160p 29.97 fps (AMD VCE) preset?

Laptop: Dell XPS15-9570; i7-8750h 32gb (integrated Intel UHD-630 & Nvidia GTX-1050Ti)
Road: Intel NUC i7 8809g 32gb (integrated AMD VegaM 4gb graphics and Intel HD630)
Workstation: i9 9900k 32 gb (Sapphire AMD Radeon VII 16gb graphics and integrated Intel UHD630)
Workstation2: e5 1650v4 128 gb (Sapphire Nitro+ RX580 8gb graphics)
Workstation3: i7-980X 24gb (Sapphire RX480 4gb graphics)
currently Vegas 16, testing Vegas 17

JN_ wrote on 7/7/2019, 6:01 PM

@Howard-Vigorita With all due respect, I don’t know whether its a language barrier or you simply didn’t bother reading the details of my last post. To repeat, I don’t have VCE capability. Please read my previous post.

 

Desktop and Laptop basic specs ...

Both run Win 10, has latest updates ...

Running latest ver. of Vegas Pro with latest updates.

VP13 B453 also.

Vegaseur and Pluraleyes installed on both ...

Quicktime 7.79.80.95

PC ...

i9 9900K, Intel Graphics 630. Nov 2018.

Mem. 32gb DDR4

Graphics card .. Nvidia Rtx 2080 Ti

Nvidia Graphics driver .. latest Studio driver.

Latest Intel Graphics driver

 

Laptop ... (Acer Predator G9-793-77AC)

CPU .. i7-6700HQ Skylake-H

Memory ..16GB DDR4 

Graphics card .. Nvidia GTX 1070, latest Studio driver.

Howard-Vigorita wrote on 7/7/2019, 6:12 PM

@JN_ Sorry, I thought you had something to contribute. In any event you have identified a possible issue that might effect someone other than yourself so I'll see what I can do about getting rid of that vfr jitter bug.

Last changed by Howard-Vigorita on 7/7/2019, 6:15 PM, changed a total of 1 times.

Laptop: Dell XPS15-9570; i7-8750h 32gb (integrated Intel UHD-630 & Nvidia GTX-1050Ti)
Road: Intel NUC i7 8809g 32gb (integrated AMD VegaM 4gb graphics and Intel HD630)
Workstation: i9 9900k 32 gb (Sapphire AMD Radeon VII 16gb graphics and integrated Intel UHD630)
Workstation2: e5 1650v4 128 gb (Sapphire Nitro+ RX580 8gb graphics)
Workstation3: i7-980X 24gb (Sapphire RX480 4gb graphics)
currently Vegas 16, testing Vegas 17

JN_ wrote on 7/7/2019, 6:28 PM

@Howard-Vigorita Its simple really @Kinvermark brought up the idea again of say a 4K version of the Red Car test. This has been an on again off again idea, maybe this time it might fly, but not on one wing.

You offered your storage space and upload time to host your modified version to other users, well done. I checked it out and found it has a problem, its not fit for purpose, so fix it. If you’re going to make something for other users to use you have a responsibility to get it right.

 

Desktop and Laptop basic specs ...

Both run Win 10, has latest updates ...

Running latest ver. of Vegas Pro with latest updates.

VP13 B453 also.

Vegaseur and Pluraleyes installed on both ...

Quicktime 7.79.80.95

PC ...

i9 9900K, Intel Graphics 630. Nov 2018.

Mem. 32gb DDR4

Graphics card .. Nvidia Rtx 2080 Ti

Nvidia Graphics driver .. latest Studio driver.

Latest Intel Graphics driver

 

Laptop ... (Acer Predator G9-793-77AC)

CPU .. i7-6700HQ Skylake-H

Memory ..16GB DDR4 

Graphics card .. Nvidia GTX 1070, latest Studio driver.

Howard-Vigorita wrote on 7/7/2019, 7:34 PM

@JN_ Do me a favor and pull down a re-rendered clip#2 and let me know if swapping it into the project lets it run on your system. It's in a zip in the same place as the big one you already pulled in.

Laptop: Dell XPS15-9570; i7-8750h 32gb (integrated Intel UHD-630 & Nvidia GTX-1050Ti)
Road: Intel NUC i7 8809g 32gb (integrated AMD VegaM 4gb graphics and Intel HD630)
Workstation: i9 9900k 32 gb (Sapphire AMD Radeon VII 16gb graphics and integrated Intel UHD630)
Workstation2: e5 1650v4 128 gb (Sapphire Nitro+ RX580 8gb graphics)
Workstation3: i7-980X 24gb (Sapphire RX480 4gb graphics)
currently Vegas 16, testing Vegas 17

JN_ wrote on 7/7/2019, 8:05 PM

@Howard-Vigorita Aok, playback fine on laptop, 0.753 fps. (VP freezes after finishing playback, Laptop hardware may not be up to the task). Rendered out to a FHD nvenc encoded file aok. Mediainfo shows it as CFR. 👍.

Now i’m going back to bed, it’s 2:04 AM here in Dublin, goodnight.

 

Last changed by JN_ on 7/8/2019, 3:36 AM, changed a total of 1 times.

 

Desktop and Laptop basic specs ...

Both run Win 10, has latest updates ...

Running latest ver. of Vegas Pro with latest updates.

VP13 B453 also.

Vegaseur and Pluraleyes installed on both ...

Quicktime 7.79.80.95

PC ...

i9 9900K, Intel Graphics 630. Nov 2018.

Mem. 32gb DDR4

Graphics card .. Nvidia Rtx 2080 Ti

Nvidia Graphics driver .. latest Studio driver.

Latest Intel Graphics driver

 

Laptop ... (Acer Predator G9-793-77AC)

CPU .. i7-6700HQ Skylake-H

Memory ..16GB DDR4 

Graphics card .. Nvidia GTX 1070, latest Studio driver.

Grazie wrote on 7/7/2019, 10:44 PM

@Kinvermark - I know your suggestions are well meant, and you wish the best for me. For that I thank you - thank you.

Turning off FX or resetting clip timing are intended to isolate & identify the scope of the problem. Then you can decise wether or not you want to live with it.

@Kinvermark - Yes, of course. This has become more of a campaign to ascertain just what is going on. I’ve been reading the dialogue between @Howard-Vigorita and @JN_ which strongly indicates some evidence-based results whereby Variable Framerates are at the crux of the issues in that “Region 5”.

Seems to me there are only two real options: 1) ignore the "problem" as relatively unimportant and hope that it does not affect your own projects. 2) Try something to fix it. Either one may be valid.

@Kinvermark - Sure, I can, and have lived with many, many things, but I’d rather know just what the Dickens is going on! Wouldn’t you? So:

1) No, it’s not unimportant to me? It’s very important to me. I’ve just spent, for me, much money on a new MONSTA! that I want to nail just what is going on in this Red Car Test. And, as I said the @Howard-Vigorita and @JN_ is indicating a logic-hiatus that somewhere along the way a Variable Framerate has been introduce, and, as we know, Variable is not something that VP processes well with certain Hardware, and can lead to choking.

2) Sure, a “fix” is oft what we do in VP. IMHO, I’m guessing it’s the price we pay for using such a intuitive NLE. And this convergence of “Workflow” and “Choking” has been a stress test using The Red Car sample has done just that. Somehow for “others” this has not been an issue. Good.

I would think a relatively likely and easy thing to change is the GPU, so that's where I would start.

Well, yes, it would. However, this doesn’t present crucial/critical/systematic evidenced-based results for you/me/MAGIX to make a difference. And again, that dialogue, pointing towards “Variable”, for my Card and not others, in my opinion, gives my Builders and MAGIX a way forward to get convergence of development for all concerned.

You could temporarily scavenge one from your old system, or get your PC Builders to give you one to try - seems like they would do this just as customer support, given that they likely have spare parts lying around anyway.

Ah, and here’s the thing.... My old PC’s GPU was a cul-de-sac in terms of functionality with regard to Variable-ness. As to going, “Cap-in-Hand”, my term and not yours, to my Builders for an alternative GPU could be viewed as being desperate, at best and putting the cart before the horse and may result in confusion and unsubstantiated lack of evidenced-based results pointing towards convergence for a a solution.

As I said, I know all your comments are well meant and you wish the best for me, for that I thank you. However, 😉, this whole process has revealed, in my opinion, a far more fundamental issue. Me, fiddling about with Hardware that attempts to “fits” my NLE, over just this, if it’s correct, the Variable issue, is not assisting both MAGIX and, in my case, nVidia and Builders to move forward.

Here is a novel thought: My System is just so fast now that neither VP nor the nVidia Card can keep-up with needing to do the Math with variable frame rate. A slower processing would deal with the variable-ness better?! Sure, this sounds ludicrous, and I’m no IT engineer, but sometimes product development does require comments made by individuals on the other side of the Fence line 😉.

Grazie

PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti

PC 10 64-bit 64gb * Intel® Core™i9 - 3.3GHz * 40Gb NVIDIA  GeForce RTX 2070

Cameras: Canon XF300 + PowerShot SX60HS Bridge

Howard-Vigorita wrote on 7/7/2019, 10:57 PM

@JN_ Carman be banished! I'll see about getting the big zip updated tomorrow when I'll have access to more bandwidth.

Laptop: Dell XPS15-9570; i7-8750h 32gb (integrated Intel UHD-630 & Nvidia GTX-1050Ti)
Road: Intel NUC i7 8809g 32gb (integrated AMD VegaM 4gb graphics and Intel HD630)
Workstation: i9 9900k 32 gb (Sapphire AMD Radeon VII 16gb graphics and integrated Intel UHD630)
Workstation2: e5 1650v4 128 gb (Sapphire Nitro+ RX580 8gb graphics)
Workstation3: i7-980X 24gb (Sapphire RX480 4gb graphics)
currently Vegas 16, testing Vegas 17

Grazie wrote on 7/7/2019, 11:01 PM

@JN_ Carman be banished!

@Howard-Vigorita - Please explain? I’m all ears 😎

What do you think of my analysis and then going forward?

 

Grazie

PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti

PC 10 64-bit 64gb * Intel® Core™i9 - 3.3GHz * 40Gb NVIDIA  GeForce RTX 2070

Cameras: Canon XF300 + PowerShot SX60HS Bridge

JN_ wrote on 7/8/2019, 3:43 AM

@Grazie If you’re testing using the original 2k Red Car project? then there is no VFR issue. It's now only in @Howard-Vigorita's present 4K download which he is going to update when he can.

Just wondering, not at PC now to check, is there any Quicktime media in the project @Grazie, and if so would changing your Quicktime driver do anything? Or since its a new build is there ANY Quicktime driver installed?

Last changed by JN_ on 7/8/2019, 4:10 AM, changed a total of 2 times.

 

Desktop and Laptop basic specs ...

Both run Win 10, has latest updates ...

Running latest ver. of Vegas Pro with latest updates.

VP13 B453 also.

Vegaseur and Pluraleyes installed on both ...

Quicktime 7.79.80.95

PC ...

i9 9900K, Intel Graphics 630. Nov 2018.

Mem. 32gb DDR4

Graphics card .. Nvidia Rtx 2080 Ti

Nvidia Graphics driver .. latest Studio driver.

Latest Intel Graphics driver

 

Laptop ... (Acer Predator G9-793-77AC)

CPU .. i7-6700HQ Skylake-H

Memory ..16GB DDR4 

Graphics card .. Nvidia GTX 1070, latest Studio driver.