Comments

browj2 wrote on 8/29/2021, 9:14 PM

@bjtap

Hi,

Stick with VPX12 for now. We are constantly finding new bugs.

I have 12 on my desktop for production, 13 on laptop for playing.

John CB

John C.B.

VideoPro X(16); Movie Studio 2025 Platinum; Music Maker 2025 Premium Edition; Samplitude Pro X8 Suite; see About me for more.

Desktop System - Windows 10 Pro 22H2; MB ROG STRIX B560-A Gaming WiFi; Graphics Card Zotac Gaming NVIDIA GeForce RTX-3060, PS; Power supply EVGA 750W; Intel Core i7-10700K @ 3.80GHz (UHD Graphics 630); RAM 32 GB; OS on Kingston SSD 1TB; secondary WD 2TB; others 1.5TB, 3TB, 500GB, 4TB, 5TB, 6TB, 8TB, 12TB, 14TB; three monitors - HP 25" main, LG 4K 27" second, HP 27" third; Casio WK-225 piano keyboard; M-Audio M-Track USB mixer.

Notebook - Microsoft Surface Pro 4, i5-6300U, 8 GB RAM, 256 SSD, W10 Pro 20H2.

YouTube Channel: @JCBrownVideos

bjtap wrote on 8/31/2021, 7:25 AM

Thanks John CB. I will hangon with VPX12. This brings up a couple of other questions:

1) How will we 'know' when VPX13 is 'usable' or stable?

2) Why is Magix constantly pushing VPX13? I get update notices all the time via the program and online computer.

Barry

ProMagixUser wrote on 9/3/2021, 11:17 AM

I installed X13 version 19.0.1.117 and found many errors. The most important of these is the blurring problem in the post-render video. The program renders blurry. my system; i9 9700K nvidia RTX 2070 win10 and fully updated

johnebaker wrote on 9/3/2021, 12:34 PM

@ProMagixUser

Hi

. . . . The most important of these is the blurring problem in the post-render video. The program renders blurry. my system . . . .

  1. Do you mean the overall image is blurry?
     
  2. What is your source video resolution?
     
  3. Which export preset are you using and are you changing any of its parameters?
     
  4. What is the resolution of the device you are watching the exported video on?

John EB
Forum Moderator

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 24H2 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-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

johnebaker wrote on 9/3/2021, 12:41 PM

@bjtap

Hi Barry

See this Support article regarding the notifications/news software - if you do not use the Cloud options in VPX - uninstall the Update Notifier.

Also ensure you have the Hide news option checked in the program settings.

John EB

 

Last changed by johnebaker on 9/3/2021, 12:41 PM, changed a total of 1 times.

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 24H2 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-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

ProMagixUser wrote on 9/3/2021, 1:13 PM

@ProMagixUser

Hi

. . . . The most important of these is the blurring problem in the post-render video. The program renders blurry. my system . . . .

  1. Do you mean the overall image is blurry?
     
  2. What is your source video resolution?
     
  3. Which export preset are you using and are you changing any of its parameters?
     
  4. What is the resolution of the device you are watching the exported video on?

John EB
Forum Moderator

1 - Yes

2 - 1920x1080

3 - hevc or mpeg4 default settings

4 - 2K

note: this problem does not exist in X12 version