VPX12 New Version now out - New Features - Old bugs?

Comments

simmiv wrote on 8/2/2020, 8:15 AM

Hi CubeAce,

I've now tried a number of different images and they are all good, except the one it crashes on. I fired up my i5 laptop and also ran Video Pro X on that and it also crashes, only on this image! So it would appear it is fine with 300dpi images..

I also had some issues with green frames being inserted at regular time intervals.. With a video on the timeline which is 59,97 frames it was inserting two green frames with 40 normal frames between. Pretty strange. I fiddled with the configuration and when it didn't change I closed down the project and then opened it up again and the issue was gone.. It was a bit strange, but I was wondering if it related to the NTSC vs PAL settings. I use NTC on the GoPros, but when the program installs on my PC it defaults the program settings to PAL. Anyway it seems to be good now..

Rgds,

Simmi

64Bit Windows 10 Pro 1909, Intel i7-4770K CPU @ 3.50GHz, overcloced to 3.99GHZ, 16GB Ram, Up to date with all upgrades and patches.

Activated Intel 4600 graphics (part of i7-4770k cpu) w/1GB as main display on Asus VS278 27" LCD Monitor

AMD Radeon R9 280x 3GB DDR5 on secondary display Samsung SMBX2450 24" LCD monitor

C: drive is an SSD but Magix runs from a HDD I: drive.. Saving Exports on a separate SSD drive.

CubeAce wrote on 8/2/2020, 10:58 AM

@simmiv

Hi Simmiv.

As far as I'm aware, North America is the only country that is native to NTSC. So I would guess if uploaded anywhere else in the world, the program would default to a PAL format as that would be the native format. The PAL format is technically superior to NTSC which was developed in the states to be backwards compatible with black and white broadcasts of the day resulting in less horizontal lines per frame and cope with lower band broadcast frequencies. Apart from the frame rate difference the resulting image often had colour shift problems as well making American programs of the era a not so pleasant experience for other audiences around the world.

With digital TV this is really not a problem any more and it's possible only reason for being is if you are still dealing with analogue equipment in the chain, such as making video conversions from analogue tape.

So if you don't live in North America I guess the default setting is PAL when installing the program.

As for changing the dpi of an image which as I said is really an instruction set for printers, what you are doing is telling the printer how many dots to put down per inch from the pixels that occupy that portion of the frame.

How that is then interpreted by a video editing package I have no idea as in theory the image should still have the same amount of pixel information across the screen unless during the video encoding it is wrongly interpreted somehow.

The green frames I can't explain at all but glad the problem has gone.

Ray.

Windows 10 Enterprise. Version 2004 OS build 19041.450. Direct X 12. Bios version 1401 latest hardware updates for Western Digital hard drives. Page file space 4.75GB.

Asus ROG STRIX Z390-F Gaming motherboard Rev 1.xx with Supreme FX inboard audio using the S1220A code.

Intel i9900K Coffee Lake 3.6 to 5.1GHz CPU and Intel UHD Graphics 630 Vers 27.20.100.8681, with 32GB of 2133MHz Corsair DDR4 ram.

1000 watt EVGA modular power supply.

1 x 250GB SSD D: drive for current project. 1 x 320gig Toshiba M2.1 drive for Operating System. + x2 WD BLACK 2TB internal SATA 7,200rpm hard drives.I for internal backup and 1 for Library clips/sounds/music/stills. Total 8TB of three external WD drives for backup.

NVIDIA G Force GTX 1650 Super. DCH Driver version 27.21.14.5206 CUDA cores. Memory interface 128bit Memory bandwidth 192.03GB/s 4GB of dedicated GDDR6 video memory, shared system memory 16307MB PCi Express x16 Gen3.

Running MEP Premium 19.0.2.58. and VPX 17.0.3.68 (UDP3)

M Audio Axiom AIR Mini MIDI keyboard Ver 5.10.0.3507

johnebaker wrote on 8/2/2020, 1:05 PM

@simmiv

Hi

The green frames are possibly caused by a glitch in decoding the NTSC video - do the GoPros record in PAL 50fps, progressive?

John EB

Lateral thinking can get things done!

VPX 12, MEP Premium 2021, and earlier versions 2015 and 2016, Music Maker Premium 2021 and Music Maker 2020.

Running Windows 10 2004 64bit on Intel i7-8700K 3.2 GHz, 16Gb RAM, 3 x 2Tb internal HDD + 60Gb internal SSD, + 6 ext backup HDDs, Sony FDR-AX53 Video camera, Contour HD 1080 and Sony HDR-AS30V Sports cams.

simmiv wrote on 8/2/2020, 6:15 PM

Cubeace, yes I'm aware of the NTSC (Never The Same Color) issues with the US standard. US TV's used to have a Hue control because the color would go out of sync! That is why Europe chose the PAL system as it synchronizes the color automatically. I had to force the program setting to NTSC and even then it was whinging about the fact that it had detected itself here in OZ, and it should be PAL.

johnebaker, I know I should use PAL, but as I'm filming while driving I want to have the highest frame rate I could, for a smoother footage. Thus all my gopro footage is recorded in NTSC. For instance while driving 90 Km/Hour I'm moving 25 Meters/sec. With 25 Frames/Sec I've got a distance of 1 Meter between frames. With 60 Frames/Sec the distance is just over 0,4 Meters/sec which makes for a smoother video. I think what may have happened is the fact that I had already created and saved the project with the setting as NTSC. When re-installing Video X Pro it defaulted to PAL and when I loaded the existing project file it re-used all the cached objects and thus created these green frames. I then changed the program setting from PAL to NTSC and re-loaded the project. It would then have been happy and not created the green frames. At least it's happy now!

64Bit Windows 10 Pro 1909, Intel i7-4770K CPU @ 3.50GHz, overcloced to 3.99GHZ, 16GB Ram, Up to date with all upgrades and patches.

Activated Intel 4600 graphics (part of i7-4770k cpu) w/1GB as main display on Asus VS278 27" LCD Monitor

AMD Radeon R9 280x 3GB DDR5 on secondary display Samsung SMBX2450 24" LCD monitor

C: drive is an SSD but Magix runs from a HDD I: drive.. Saving Exports on a separate SSD drive.

CubeAce wrote on 8/3/2020, 3:05 AM

@simmiv

Hi Simmiv.

I don't feel personally that anyone gets smoother footage shooting more frames per second but you do get a sharper image if that is what you mean. The 50 fps I shoot at is not far short of the quality I get if I shoot at 60 fps as long as I remember to apply the 180 degree shutter rule. I do use other frame rates and resolutions though and normally old projects will load at the old recorded settings. The only thing that tends to remain the same is the export settings from the previous project which will often give rise to an export warning that the project and export settings do not match.

Ray.

Windows 10 Enterprise. Version 2004 OS build 19041.450. Direct X 12. Bios version 1401 latest hardware updates for Western Digital hard drives. Page file space 4.75GB.

Asus ROG STRIX Z390-F Gaming motherboard Rev 1.xx with Supreme FX inboard audio using the S1220A code.

Intel i9900K Coffee Lake 3.6 to 5.1GHz CPU and Intel UHD Graphics 630 Vers 27.20.100.8681, with 32GB of 2133MHz Corsair DDR4 ram.

1000 watt EVGA modular power supply.

1 x 250GB SSD D: drive for current project. 1 x 320gig Toshiba M2.1 drive for Operating System. + x2 WD BLACK 2TB internal SATA 7,200rpm hard drives.I for internal backup and 1 for Library clips/sounds/music/stills. Total 8TB of three external WD drives for backup.

NVIDIA G Force GTX 1650 Super. DCH Driver version 27.21.14.5206 CUDA cores. Memory interface 128bit Memory bandwidth 192.03GB/s 4GB of dedicated GDDR6 video memory, shared system memory 16307MB PCi Express x16 Gen3.

Running MEP Premium 19.0.2.58. and VPX 17.0.3.68 (UDP3)

M Audio Axiom AIR Mini MIDI keyboard Ver 5.10.0.3507

johnebaker wrote on 8/3/2020, 3:59 AM

@simmiv, @CubeAce

Hi Simmi

. . . . . I know I should use PAL, but as I'm filming while driving . . . . For instance while driving 90 Km/Hour . . . .

I can understand where you are combining from with this train of thought, however the difference between 50 and 60 fps is not, IMHO, that great - the eye cannot tell the difference as anything above about 18 fps is seen as continuous motion.

In my experience it is not forward motion that suffers, having experienced some of the Outback 'back roads', it is pan / slew shots that suffer from some jerkiness at specific pan/slew speed/frame rate combinations and the 'rock and roll' is no affected so much.

One 'fix' I have found in smoothing out some of the severe jerkiness that is a disadvantage of progressive video at 25/30 fps is to apply the Interpolate intermediate images option of the Speed effect to clips that do have jerkiness present.

HTH

John EB

Lateral thinking can get things done!

VPX 12, MEP Premium 2021, and earlier versions 2015 and 2016, Music Maker Premium 2021 and Music Maker 2020.

Running Windows 10 2004 64bit on Intel i7-8700K 3.2 GHz, 16Gb RAM, 3 x 2Tb internal HDD + 60Gb internal SSD, + 6 ext backup HDDs, Sony FDR-AX53 Video camera, Contour HD 1080 and Sony HDR-AS30V Sports cams.

CubeAce wrote on 8/3/2020, 8:44 AM

@simmiv @johnebaker

Hi John.

I have a slightly different approach which does depend on how the camera is used within the car and how good the isolation is between the inside of the car and the wheels.

If the camera can be securely mounted to the front windscreen with as much dampening applied as possible to prevent camera vibration, I find it better to deactivate any vibration reduction system in the camera that seems to make the image worse during turns. This may not be true of all cameras, a lot depends on the anti-vibration method used and smaller cameras with less mass seem to benefit more over larger heavier ones.

I will also try your suggestion but I'm not off road that often.

Ray.

Windows 10 Enterprise. Version 2004 OS build 19041.450. Direct X 12. Bios version 1401 latest hardware updates for Western Digital hard drives. Page file space 4.75GB.

Asus ROG STRIX Z390-F Gaming motherboard Rev 1.xx with Supreme FX inboard audio using the S1220A code.

Intel i9900K Coffee Lake 3.6 to 5.1GHz CPU and Intel UHD Graphics 630 Vers 27.20.100.8681, with 32GB of 2133MHz Corsair DDR4 ram.

1000 watt EVGA modular power supply.

1 x 250GB SSD D: drive for current project. 1 x 320gig Toshiba M2.1 drive for Operating System. + x2 WD BLACK 2TB internal SATA 7,200rpm hard drives.I for internal backup and 1 for Library clips/sounds/music/stills. Total 8TB of three external WD drives for backup.

NVIDIA G Force GTX 1650 Super. DCH Driver version 27.21.14.5206 CUDA cores. Memory interface 128bit Memory bandwidth 192.03GB/s 4GB of dedicated GDDR6 video memory, shared system memory 16307MB PCi Express x16 Gen3.

Running MEP Premium 19.0.2.58. and VPX 17.0.3.68 (UDP3)

M Audio Axiom AIR Mini MIDI keyboard Ver 5.10.0.3507

emmrecs wrote on 8/13/2020, 2:02 PM

@johnebaker @browj2 @simmiv @Scenestealer

Before I raise another bug report can anyone else with the new version 12 confirm, or otherwise, this very bizarre problem I have just encountered, and can reproduce?

On a project I'm currently working on I have a video file on tracks 3 and 4 (3 is video, 4 is associated audio). I wanted to change the overall level of the audio, along with one or two other "tweaks" so went into the mixer and added some Magix and external VSTs as Track Effects.

Making ANY change to the fader for track/channel 4 makes absolutely no difference to the audio output level. Whether the fader is at +6 or -inf. the audio level is exactly the same! Moving the video/audio object to, say, track 5 and 6, the fader on track 6 works exactly as expected. Moving the video object back to tracks 3 and 4, no change to the audio with any move of the track 4 fader. I removed all the track effects, both Magix and external, but that made no change to the fader non-operation.

All other fader channels that I have checked work entirely as expected; only channel/track 4 behaves as if the fader was not being touched at all.

I am quite prepared to believe this is something bizarre on my computer but I would be very interested to learn whether anyone else can reproduce this?

TIA

Jeff

Win 10 Pro 64 bit, Intel i7 Quad Core 6700K @ 4GHz, 32 GB RAM, AMD Radeon R7 360 and Intel HD530 Graphics, MOTU 8-Pre f/w audio interface, VPX, MEP, Music Maker, Photo Story Deluxe, Photo Manager Deluxe, Xara 3D Maker 7, Reaper, Adobe Audition CS6 and CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D

johnebaker wrote on 8/13/2020, 2:50 PM

@emmrecs

Hi Jeff

. . . . Making ANY change to the fader for track/channel 4 makes absolutely no difference to the audio output level. . . .

Cannot replicate this, all track mixer volume controls, including 4, behave as normal.

John EB

Lateral thinking can get things done!

VPX 12, MEP Premium 2021, and earlier versions 2015 and 2016, Music Maker Premium 2021 and Music Maker 2020.

Running Windows 10 2004 64bit on Intel i7-8700K 3.2 GHz, 16Gb RAM, 3 x 2Tb internal HDD + 60Gb internal SSD, + 6 ext backup HDDs, Sony FDR-AX53 Video camera, Contour HD 1080 and Sony HDR-AS30V Sports cams.

browj2 wrote on 8/13/2020, 3:15 PM

@emmrecs

Hi Jeff,

I just checked in VPX11; cannot replicate this.

Are you absolutely certain that you put the effects on the correct track and/or that you are using the correct fader?

I ask because I just put the effects on track 5 by mistake, then tried to figure out why the effects weren't working.

John CB

John C.B.

VideoPro X(12); MEP2021 Plus; MM2021 Premium; see About me for more.

Desktop System - Windows 10 Home 1903; 16Gb RAM; i7 CPU 860@2.80Gz; ATI Radeon HD5770 w1GB; SSD 500GB, HD 2TB; others 1.5TB, 3TB, 500GB, 4TB, 5TB, 6TB; dual monitors - 27" main, 25" secondary; Casio WK-225 piano keyboard; M-Audio M-Track USB mixer; Notebook - Microsoft Surface Pro 4, i5, 8 GB RAM, 256 SSD, W10 Pro 1903

emmrecs wrote on 8/14/2020, 3:31 AM

@johnebaker @browj2

Hi John and John.

If you cannot replicate this in VPX12 there is clearly something very strange going on in my computer! I will test it again this morning, with a different video clip this time. @browj2 the FX were definitely being applied to track 4 (I could hear them working, until I completely removed all of them) but whether they were present or not, the fader on track/channel 4 had no effect.

Another Magix mystery!

Jeff

UPDATE: So I tested it this morning, "new project" but same clip: no problem!!!! New clip, still worked! Opened the "old" project, same clip on same track as just worked, now doesn't! Track 4 fader has no effect!!

Conclusion: the "old" project has somehow become corrupted. Not a problem to create a new one, but....

Last changed by emmrecs on 8/14/2020, 4:31 AM, changed a total of 1 times.

Win 10 Pro 64 bit, Intel i7 Quad Core 6700K @ 4GHz, 32 GB RAM, AMD Radeon R7 360 and Intel HD530 Graphics, MOTU 8-Pre f/w audio interface, VPX, MEP, Music Maker, Photo Story Deluxe, Photo Manager Deluxe, Xara 3D Maker 7, Reaper, Adobe Audition CS6 and CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D

simmiv wrote on 8/17/2020, 6:17 PM

@johnebaker @browj2

Hi John and John.

If you cannot replicate this in VPX12 there is clearly something very strange going on in my computer! I will test it again this morning, with a different video clip this time. @browj2 the FX were definitely being applied to track 4 (I could hear them working, until I completely removed all of them) but whether they were present or not, the fader on track/channel 4 had no effect.

Another Magix mystery!

Jeff

UPDATE: So I tested it this morning, "new project" but same clip: no problem!!!! New clip, still worked! Opened the "old" project, same clip on same track as just worked, now doesn't! Track 4 fader has no effect!!

Conclusion: the "old" project has somehow become corrupted. Not a problem to create a new one, but....

I have not used VST in my videos, so haven't tried this, but I'm glad you have worked it out.. I have experienced this before i.e. whereby after an upgrade something strange happens to a particular project. Sometimes saving it again and reloading fixes it, sometimes more effort is required.

In regards to my "crashing jpg file", Magix support have come back to me and acknowledged that it is a bug in VPX12. i.e. the file shouldn't cause VPX12 to crash like that. The same project with the same jpg file works fine in VPX11. They promised a bug fix for this would be in the next patch! Case closed!

Simmi

 

64Bit Windows 10 Pro 1909, Intel i7-4770K CPU @ 3.50GHz, overcloced to 3.99GHZ, 16GB Ram, Up to date with all upgrades and patches.

Activated Intel 4600 graphics (part of i7-4770k cpu) w/1GB as main display on Asus VS278 27" LCD Monitor

AMD Radeon R9 280x 3GB DDR5 on secondary display Samsung SMBX2450 24" LCD monitor

C: drive is an SSD but Magix runs from a HDD I: drive.. Saving Exports on a separate SSD drive.

johnebaker wrote on 8/18/2020, 4:10 AM

@simmiv

Hi Simmi

. . . . Magix support have come back to me and acknowledged that it is a bug . . . . promised a bug fix for this would be in the next patch! . . . .

That is good news.

@emmrecs

Hi Jeff

. . . . the "old" project has somehow become corrupted . . . .

That too is good news.

John EB

Lateral thinking can get things done!

VPX 12, MEP Premium 2021, and earlier versions 2015 and 2016, Music Maker Premium 2021 and Music Maker 2020.

Running Windows 10 2004 64bit on Intel i7-8700K 3.2 GHz, 16Gb RAM, 3 x 2Tb internal HDD + 60Gb internal SSD, + 6 ext backup HDDs, Sony FDR-AX53 Video camera, Contour HD 1080 and Sony HDR-AS30V Sports cams.