vegas pro18 373

yoo-changyun wrote on 12/30/2020, 12:03 AM

I'm having trouble updating to vegas pro18 build 373. Importing and playing Canon Time Labs clips is an issue of flickering the screen, but the clip has a problem. The 334 version, which has not yet been updated, works fine without any problems. Are there any users with the same problem as me?

Comments

walter-i. wrote on 12/30/2020, 2:07 AM

The flickering of the screen indicates a driver problem with the graphics card.
Use the Vegas Pro 18 feature "Help / Search for Driver Updates" to update your drivers. If that doesn't help, provide details of your hardware and software environment and especially about your media files.

https://www.vegascreativesoftware.info/de/forum/important-information-required-to-help-you--110457/

yoo-changyun wrote on 12/30/2020, 3:20 AM

vegas pro 14,15,16,17,18 all play well, this is the only blinking vegas pro 18 (373)
It is not a problem with the graphics card

RogerS wrote on 12/30/2020, 4:05 AM

vegas pro 14,15,16,17,18 all play well, this is the only blinking vegas pro 18 (373)
It is not a problem with the graphics card

VP 18 uses the graphics card differently than previous versions of Vegas. There is more support for hardware decoding, for example. However this is very media-specific. Walter's advice to use the latest studio driver is a good one.

If you want more help, please provide MediaInfo for exactly what types of video you are using.

This isn't a common issue, though, I don't remember seeing it here or on the Facebook groups.

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with latest driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 2080 Super (8GB) with latest studio driver, 2TB Hynix P41 SSD, Windows 11 Pro 64 bit

Dell XPS 15 laptop (2017) 32GB ram, NVIDIA 1050 (4GB) with latest studio driver, Intel i7-7700HQ with Intel 630 iGPU (latest available driver), dual internal SSD (1TB; 1TB), Windows 10 64 bit

VEGAS Pro 19.651
VEGAS Pro 20.411
VEGAS Pro 21.208

Try the
VEGAS 4K "sample project" benchmark: https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark: https://forms.gle/eErJTR87K2bbJc4Q7

yoo-changyun wrote on 12/30/2020, 5:34 AM

The weird thing is that the same vegas pro18 plays fine on build334 and when only playing on vegas pro build 373 the flicker is all the same vegas pro18. The reason I have a problem with build373 is that the video clip is also a regular clip. The problem only occurs in vegas pro 18 build373.

.

 

walter-i. wrote on 12/30/2020, 6:33 AM

If you post your answers and pictures in an English-speaking forum in Chinese, you are depriving yourself of the possibility of international help.

But of course you have to decide that all by yourself .......

yoo-changyun wrote on 12/30/2020, 7:27 AM

There is no Chinese in my writing...
There is only English + Korean... All information in the media information is in English just by looking at the codec. Even now, I tested it on another computer. Only vegas pro18 build(373) has a replay error and in vegas pro18 build334 below that everything works fine..
The admin just needs to view this article.
Looking forward to the next build.

RogerS wrote on 12/30/2020, 7:37 AM

Thanks for adding your comment in English.

All the developers are away for the holidays I believe but hopefully they can take a look at your MediaInfo in the new year.

If you have a sample of the footage you could upload (just a few seconds is fine), that would help with confirming the problem.

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with latest driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 2080 Super (8GB) with latest studio driver, 2TB Hynix P41 SSD, Windows 11 Pro 64 bit

Dell XPS 15 laptop (2017) 32GB ram, NVIDIA 1050 (4GB) with latest studio driver, Intel i7-7700HQ with Intel 630 iGPU (latest available driver), dual internal SSD (1TB; 1TB), Windows 10 64 bit

VEGAS Pro 19.651
VEGAS Pro 20.411
VEGAS Pro 21.208

Try the
VEGAS 4K "sample project" benchmark: https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark: https://forms.gle/eErJTR87K2bbJc4Q7

j-v wrote on 12/30/2020, 8:21 AM

All the developers are away for the holidays I believe but hopefully they can take a look at your MediaInfo in the new year.

No problem for us to see that MediaInfo
most important things are
256 Mb AVC file with bitrate of 464 Mbps, framerate 29,970 with dimensions 3848x2160,
The only problem looks for me the pretty high constant bitrate and maybe OP is for such needing stronger hardware.

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.70 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.70 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)

 

RogerS wrote on 12/30/2020, 8:23 PM

@VEGASHeman Hi Heman, if you could take a look at this when you get back Yoo-changyun is reporting a playback issue caused in build 373 with footage described in the MediaInfo above.

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with latest driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 2080 Super (8GB) with latest studio driver, 2TB Hynix P41 SSD, Windows 11 Pro 64 bit

Dell XPS 15 laptop (2017) 32GB ram, NVIDIA 1050 (4GB) with latest studio driver, Intel i7-7700HQ with Intel 630 iGPU (latest available driver), dual internal SSD (1TB; 1TB), Windows 10 64 bit

VEGAS Pro 19.651
VEGAS Pro 20.411
VEGAS Pro 21.208

Try the
VEGAS 4K "sample project" benchmark: https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark: https://forms.gle/eErJTR87K2bbJc4Q7

yoo-changyun wrote on 12/30/2020, 9:00 PM

Thanks for your attention My hardware spec is intea (r) core (tm) i9 9900x cpu @ 3.50ghz
64.0 GB of RAM
is rtx2060
All graphics drivers are up to date
Once additional information is the same error in the time lapse clips of Canon mirrorless cameras eos r, eosr6, but all vegas pro18 has a problem, the only thing there is no import, vegas pro18 build373 says there is no import vegas pro18 build334 It works well on my friend's other computer I also checked the problem with build373 There is a problem with the computer hardware specification is lower than me The computer imports and plays smoothly
In vegas pro18 build373 or lower, the strange thing is that there is no problem in other programs. After effects, there are no problems in the premiere, and import and playback are not possible only in vegas pro build373.

RogerS wrote on 12/30/2020, 9:30 PM

@yoo-changyun Can you share the MediaInfo for other files you are having trouble with? It would be good to see if the R and R6 are creating the same type of time lapse file or not (please paste it MediaInfo as text if you can, so we can autotranslate the Korean).

If you can upload a sample (Google Drive, etc.) of a few seconds it might help with confirming the issue.

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with latest driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 2080 Super (8GB) with latest studio driver, 2TB Hynix P41 SSD, Windows 11 Pro 64 bit

Dell XPS 15 laptop (2017) 32GB ram, NVIDIA 1050 (4GB) with latest studio driver, Intel i7-7700HQ with Intel 630 iGPU (latest available driver), dual internal SSD (1TB; 1TB), Windows 10 64 bit

VEGAS Pro 19.651
VEGAS Pro 20.411
VEGAS Pro 21.208

Try the
VEGAS 4K "sample project" benchmark: https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark: https://forms.gle/eErJTR87K2bbJc4Q7

yoo-changyun wrote on 12/30/2020, 9:43 PM

 

RogerS  thank you

eos r and eos r6 deliver media information data that cannot be played only on vegas pro18 build373 both home computer and workroom computer. Thank you.

 

eos r

일반
전체 이름 : C : \ Users \ fkdla \ Desktop \ 128A6904.MP4
형식 : MPEG-4
형식 약력 : Base Media / Version 2
코덱 ID : mp42 (mp42 / avc1 / CAEP)
파일 크기 : 236 MiB
길이 : 4 초 271 미리 초
총 비트 레이트 모드 : 변동
총 비트 레이트 : 464 Mbps
인코딩 날짜 : UTC 2019-01-04 16:24:17
태깅 한 날짜 : UTC 2019-01-04 16:24:17

비디오
ID : 1
형식 : AVC
형식 / 정보 : 고급 비디오 코덱
형식 약력 : High@L6.1
형식 설정 : 1 Ref Frames 형식 설정,
CABAC : 형식 설정,
RefFrames : 1 프레임
형식 설정, GOP : N = 1
코덱 ID : avc1
코덱 ID / 정보 : Advanced Video Coding
길이 : 4 초 271 미리 초
비트 레이트 모드 :
변동 비트 레이트 : 464 Mbps
폭 : 3840 픽셀
높이 : 2160 픽셀
화면 종횡비 : 16 : 9
프레임 레이트 모드 : 고정
프레임 레이트 : 29.970 (30000/1001) fps
색 공간 : YUV
크로마 서브 샘플링 : 4 : 2 : 0
비트 심도 : 8 비트
스캔 방식 : 프로그레시브
비트 / (픽셀 * 프레임) : 1.867
스트림 크기 : 236 MiB (100 %)
언어 : 영어
인코딩 날짜 : UTC 2019-01-04 16:24:17
태깅 한 날짜 : UTC 2019-01-04 16:24:17
색상 범위 : 풀
컬러 원색 : BT.709
전송 특성 : BT.709
매트릭스 계수 : BT.709
코덱 구성 상자 : avcC

 

eos r6

일반
전체 이름                                    : C:\Users\fkdla\Desktop\259A7517.MP4
포맷                                       : MPEG-4
포맷 프로파일                                  : Base Media / Version 2
코덱 ID                                    : mp42 (mp42/avc1/CAEP)
파일 크기                                    : 82.8 MiB
길이                                       : 1초 768미리초
총 비트레이트 모드                               : 변동
총 비트레이트                                  : 393 Mbps
인코딩 날짜                                   : UTC 2020-12-31 02:37:39
태깅한 날짜                                   : UTC 2020-12-31 02:37:39

비디오
ID                                       : 1
포맷                                       : AVC
포맷/정보                                    : Advanced Video Codec
포맷 프로파일                                  : High@L6.1
포맷 설정                                    : 1 Ref Frames
포맷 설정, CABAC                             : 아니오
포맷 설정, RefFrames                         : 1 프레임
Format settings, GOP                     : N=1
코덱 ID                                    : avc1
코덱 ID/정보                                 : Advanced Video Coding
길이                                       : 1초 768미리초
비트레이트 모드                                 : 변동
비트레이트                                    : 392 Mbps
폭                                        : 3 840 픽셀
높이                                       : 2 160 픽셀
화면 종횡비                                   : 16:9
프레임레이트 모드                                : 고정
프레임레이트                                   : 29.970 (30000/1001) fps
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 비트
스캔 방식                                    : 프로그레시브
비트/(픽셀*프레임)                              : 1.577
스트림 크기                                   : 82.7 MiB (100%)
언어                                       : English
인코딩 날짜                                   : UTC 2020-12-31 02:37:39
태깅한 날짜                                   : UTC 2020-12-31 02:37:39
Color range                              : Full
Color primaries                          : BT.709
Transfer characteristics                 : BT.709
Matrix coefficients                      : BT.709
Codec configuration box                  : avcC

EricLNZ wrote on 12/30/2020, 10:15 PM

Google Translate

eos r

Normal
Full Name: C:\Users\fkdla\Desktop\128A6904.MP4
Format: MPEG-4
Format bio: Base Media / Version 2
Codec ID: mp42 (mp42 / avc1 / CAEP)
File size: 236 MiB
Length: 4 seconds 271 milliseconds
Total bit rate mode: variable
Total bit rate: 464 Mbps
Encoding Date: UTC 2019-01-04 16:24:17
Date tagged: UTC 2019-01-04 16:24:17

video
ID: 1
Format: AVC
Format / Information: Advanced video codec
Format bio: High@L6.1
Format setting: 1 Ref Frames format setting,
CABAC: format setting,
RefFrames: 1 frame
Format setting, GOP: N = 1
Codec ID: avc1
Codec ID/Information: Advanced Video Coding
Length: 4 seconds 271 milliseconds
Bit rate mode:
Variable bit rate: 464 Mbps
Width: 3840 pixels
Height: 2160 pixels
Screen aspect ratio: 16:9
Frame rate mode: fixed
Frame rate: 29.970 (30000/1001) fps
Color Space: YUV
Chroma subsampling: 4: 2: 0
Bit Depth: 8 bits
Scan Method: Progressive
Bit/(Pixel * Frame): 1.867
Stream Size: 236 MiB (100%)
Language: English
Encoding Date: UTC 2019-01-04 16:24:17
Date tagged: UTC 2019-01-04 16:24:17
Color range: full
Color Primary Color: BT.709
Transmission characteristics: BT.709
Matrix coefficient: BT.709
Codec configuration box: avcC


eos r6

Normal
Full name: C:\Users\fkdla\Desktop\259A7517.MP4
Format: MPEG-4
Format Profile: Base Media / Version 2
Codec ID: mp42 (mp42/avc1/CAEP)
File size: 82.8 MiB
Length: 1 second 768 milliseconds
Total bitrate mode: variable
Total bit rate: 393 Mbps
Encoding date: UTC 2020-12-31 02:37:39
Date tagged: UTC 2020-12-31 02:37:39

video
ID: 1
Format: AVC
Format/Information: Advanced Video Codec
Format Profile: High@L6.1
Format setting: 1 Ref Frames
Format setting, CABAC: no
Format setting, RefFrames: 1 frame
Format settings, GOP: N=1
Codec ID: avc1
Codec ID/Information: Advanced Video Coding
Length: 1 second 768 milliseconds
Bit rate mode: variable
Bit rate: 392 Mbps
Width: 3 840 pixels
Height: 2 160 pixels
Screen aspect ratio: 16:9
Frame rate mode: fixed
Frame rate: 29.970 (30000/1001) fps
Color space: YUV
Chroma subsampling: 4:2:0
Bit depth: 8 bits
Scan Method: Progressive
Bit/(Pixel*Frame): 1.577
Stream size: 82.7 MiB (100%)
Language: English
Encoding date: UTC 2020-12-31 02:37:39
Tagged date: UTC 2020-12-31 02:37:39
Color range: Full
Color primaries: BT.709
Transfer characteristics: BT.709
Matrix coefficients: BT.709
Codec configuration box: avcC

yoo-changyun wrote on 12/30/2020, 10:58 PM

 

@RogerS Clips that were originally imported from vegas pro18 well, uploaded some of the clips that are only problematic in build 373. These clips are for verification purposes only and should not be distributed

 

https://drive.google.com/file/d/1x9evyINHeWs_X-n4bUhCVZGgVOlm76DI/view?usp=sharing

RogerS wrote on 12/31/2020, 12:10 AM

Once additional information is the same error in the time lapse clips of Canon mirrorless cameras eos r, eosr6, but all vegas pro18 has a problem, the only thing there is no import, vegas pro18 build373 says there is no import vegas pro18 build334 It works well on my friend's other computer

Thanks for the clip. I noticed that if "legacy AVC decoding" is checked under File I/O, the clip will not import at all. Make sure this is not checked in Vegas 17 or 18.

That doesn't answer your flicker problem, though. I'm curious if others see flickering with this type of video.

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with latest driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 2080 Super (8GB) with latest studio driver, 2TB Hynix P41 SSD, Windows 11 Pro 64 bit

Dell XPS 15 laptop (2017) 32GB ram, NVIDIA 1050 (4GB) with latest studio driver, Intel i7-7700HQ with Intel 630 iGPU (latest available driver), dual internal SSD (1TB; 1TB), Windows 10 64 bit

VEGAS Pro 19.651
VEGAS Pro 20.411
VEGAS Pro 21.208

Try the
VEGAS 4K "sample project" benchmark: https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark: https://forms.gle/eErJTR87K2bbJc4Q7

yoo-changyun wrote on 12/31/2020, 12:37 AM

I got it from vegas pro16 now, but it works very well. The problem is that vegas pro18 does not import.

lan-mLMC wrote on 12/31/2020, 12:44 AM

 

@RogerS Clips that were originally imported from vegas pro18 well, uploaded some of the clips that are only problematic in build 373. These clips are for verification purposes only and should not be distributed

 

https://drive.google.com/file/d/1x9evyINHeWs_X-n4bUhCVZGgVOlm76DI/view?usp=sharing


@yoo-changyun It can be dragged to my VEGAS Pro 18.0.0.373 without flicking.

yoo-changyun wrote on 12/31/2020, 12:53 AM

It's been a wow import. Right now, 7 Korean users, including me, can't even import... What's the problem...

RogerS wrote on 12/31/2020, 12:57 AM

What is a "wow" import? Did you make sure legacy decoding is unchecked?
I suggest you reset File I/O to defaults (or reset all of Vegas- hold control + shift when you start the program).

I'm also getting this clip to work in Vegas and was able to render it without any problem.

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with latest driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 2080 Super (8GB) with latest studio driver, 2TB Hynix P41 SSD, Windows 11 Pro 64 bit

Dell XPS 15 laptop (2017) 32GB ram, NVIDIA 1050 (4GB) with latest studio driver, Intel i7-7700HQ with Intel 630 iGPU (latest available driver), dual internal SSD (1TB; 1TB), Windows 10 64 bit

VEGAS Pro 19.651
VEGAS Pro 20.411
VEGAS Pro 21.208

Try the
VEGAS 4K "sample project" benchmark: https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark: https://forms.gle/eErJTR87K2bbJc4Q7

yoo-changyun wrote on 12/31/2020, 1:10 AM

Because of this problem, I tried to format and reinstall Windows and update the driver to the latest, but in vegas pro16, in vegas pro18 without such a Pew, the review blinks as shown in the attached video below.

Dexcon wrote on 12/31/2020, 1:11 AM

Vegas Pro 18 b373 ... that video does not import for me either - checking File I/O and Deprecated Features didn't make any difference.

It does seem odd though that the Properties window for the video is largely empty - for example, no stream information is showing which would be expected with an mp4:

The most current Studio driver is installed.

 

UPDATE

Unchecking Enable Legacy AVC Decoding in File I/O and restarting VP18 did enable the example clip to load into VP18/373, but the result was heavy flickering with more black than image.

Changing the File I/O also enabled the Properties window to populate.

Last changed by Dexcon on 12/31/2020, 2:40 AM, changed a total of 1 times.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 16, 17, 18, 19, 20 & 21, HitFilm Pro 2021.3, DaVinci Resolve Studio 18.5, BCC 2023.5, Mocha Pro 2023, Ignite Pro, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX10 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

RogerS wrote on 12/31/2020, 1:20 AM

@yoo-changyun What do you have dynamic ram preview set to- the default of 200MB? If it's a higher amount, try setting to 200.

I'm trying to figure out what is different between us. Do either of you have so4compound disabled in internal settings? Do you have Intel processors to do hardware decoding of this file type (I have the Intel 630 GPU)?

In Vegs under properties I get:

General
  Name: 128A6904.MP4
  Folder: C:\Users\Roger\Desktop
  Type: AVC
  Size: 242.10 MB (247,910,320 bytes)
  Created: Thursday, December 31, 2020, 3:01:50 PM
  Modified: Thursday, December 31, 2020, 3:02:24 PM
  Accessed: Thursday, December 31, 2020, 3:02:24 PM
  Attributes: Archive

Streams
  Video: 00:00:04.271, 29.970 fps progressive, 3840x2160x32, AVC

Summary
  [TCFM]: 6

ACID information
  ACID chunk: no
  Stretch chunk: no
  Stretch list: no
  Stretch info2: no
  Beat markers: no
  Detected beats: no

Other metadata
  Regions/markers: no
  Command markers: no

Media manager
  Media tags: no

Plug-In
  Name: so4compoundplug.dll
  Folder: C:\Program Files\VEGAS\VEGAS Pro 18.0\FileIO Plug-Ins\so4compoundplug
  Format: AVC

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with latest driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 2080 Super (8GB) with latest studio driver, 2TB Hynix P41 SSD, Windows 11 Pro 64 bit

Dell XPS 15 laptop (2017) 32GB ram, NVIDIA 1050 (4GB) with latest studio driver, Intel i7-7700HQ with Intel 630 iGPU (latest available driver), dual internal SSD (1TB; 1TB), Windows 10 64 bit

VEGAS Pro 19.651
VEGAS Pro 20.411
VEGAS Pro 21.208

Try the
VEGAS 4K "sample project" benchmark: https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark: https://forms.gle/eErJTR87K2bbJc4Q7

yoo-changyun wrote on 12/31/2020, 1:33 AM

But curiously, vegas pro16 and vegaspro 18 build334 does not have this problem. The problem occurs only in build 373. geforce rtx 2060

 

  Video: 00:00:04.271, 29.970 fps progressive, 3840x2160x32, AVC

Summary
  [TCFM]: 6

ACID information
  ACID chunk: no
  Stretch chunk: no
  Stretch list: no
  Stretch info2: no
  Beat markers: no
  Detected beats: no

Other metadata
  Regions/markers: no
  Command markers: no

Media manager
  Media tags: no

Plug-In
  Name: so4compoundplug.dll
  Folder: C:\Program Files\VEGAS\VEGAS Pro 18.0\FileIO Plug-Ins\so4compoundplug
  Format: AVC
 

lenard wrote on 12/31/2020, 2:31 AM

Because of this problem, I tried to format and reinstall Windows and update the driver to the latest, but in vegas pro16, in vegas pro18 without such a Pew, the review blinks as shown in the attached video below.

Unfortunatly Vegas18 is very buggy it's one of the worse releases in Vegas history according to some. I had a look at your file and was able to get it to play with hardware decoding off. At 4k it will put a lot of stress on your cpu, but my 6core can play ok but it does use a lot of cpu