VPX11 Patch 17.0.2.47

browj2 wrote on 10/21/2019, 8:14 AM

This popped up this morning. No bugs that were on my list were fixed.

Important changes in version 17.0.2.47

  • Improved VEGAS Video Stabilization plug-in
  • Misinterpretation of anamorphic source material when using OFX plugins solved

John CB

John C.B.

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

Comments

devil wrote on 10/21/2019, 10:17 AM

Installed the update but haven't a clue what improvements are on it. Am disappointed that there is no improvement in the 'ducking' feature, which is next to useless because it cannot use a WAV or other audio file, only on-line sound.

browj2 wrote on 10/21/2019, 6:20 PM

@devil

Hi,

The changes are in my first post.

I have no problem using the 'damping' feature, not ducking (same thing but VPX terminology) on a wave or ogg file. Right-click on it (or Alt+L) brings up the dialogue box for Automatic volume damping of other tracks.

'Ducking' is mentioned in the manual only as one of the parameters for audio recording.

Are you referring to something else?

John CB

John C.B.

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

devil wrote on 10/22/2019, 3:38 AM

Thanks muchly, John. I'm not too bothered about the terminology, ducks are usually damp, anyway! 😃 I admit that I was unaware of the 'damping' (Alt+L) feature; I looked at the manual and found only the 'ducking' one. This feature is also the final phase of 'ducking' and was surprised that the suppression was limited to 12 dB, sometimes barely sufficient in fortissimo passages. Maybe a choice of up to 15 or even 18 dB (halving the volume each time) could be judicious.

Please excuse my ignorance based on minimal instructions in the manual!

Brian (the devil 👹)

gmlotkow wrote on 10/22/2019, 6:17 AM

I wish they'd fix the object trimmer. I did find it works if you hold down the Alt key while adjusting the arrow icons...

Self built computer with:

Intel i7 K8700 Coffee Lake processor

Corsair RMX Series RMX750 750 Watt 80 Plus Gold Fully Modular ATX Power Supply

Microsoft Windows 10 Pro 64-bit - 1pk DSP OEM DVD

Corsair Hydro H115i Pro RGB Water Cooling Kit

ASUS 24x Internal DVDRW SATA Writer

2X - Corsair Vengeance LPX 32GB 2 x 16GB DDR4-2666 PC4-21300 C16 Quad Channel Desktop Memory Kit

Seagate Barracuda Pro 4TB 7,200RPM SATA III 6Gb/s 3.5" Internal Hard Drive

2x - Samsung 960 EVO 250GB V-NAND M.2 2280 PCIe NVMe Gen 3 x4 Internal Solid State Drive (on MB)

Samsung 860 EVO 500GB MLC V-NAND SATA III 6Gb/s 2.5" Internal Solid State Drive

with a Dell U3415W 34.08" UW-QHD 60Hz HDMI DP Curved LED Monitor

devil wrote on 10/22/2019, 7:35 AM

I'm coming back to my previous post. I have just tried the Alt+L feature it on a current project and found that it is not editable, making its use somewhat limited for the odd correction. I don't know the exact correct terms, but it works on the thick line at the top of the audio track (track?) curve, whereas I've been using the thin, editable, (volume?) curve. Crazy, I know, but in the cases where 12 dB suppression is insufficient, it is possible to manually override the fixed track curve suppression with the adjustable volume curve (see attachment if available).

https://www.magix.info/uk/forum/vpx11-patch-17-0-2-47--1232010/

browj2 wrote on 10/22/2019, 10:20 AM

@devil

You have to use the up-arrow button at the top of the post window to add an image to your post.

I have no problem adjusting the points on the volume curve after using the damping feature. The cursor changes to a hand. The thumb has to be over the point, then left button down and drag. To add points, double-click on the line when the hand (the thumb) is over it. Double-click on a point when the thumb is over it and it deletes the point.

BTW, what is created is a Track Volume Curve, not an Object Volume Curve. You can also edit the Track Volume Curve using Automation in the Mixer.

John CB

Last changed by browj2 on 10/22/2019, 10:23 AM, changed a total of 1 times.

John C.B.

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

devil wrote on 10/24/2019, 6:51 AM

Thanks, John. I'm beginning to see some light through the mist, with your help. I attach the graphic where I failed last time. However, thanks to your help, it is not quite so relevant here now, mainly because you have shown me about using the thumb; prior to that I've clicked on the hand with no result. Anyway, thanks, I feel I'm now in business with the ability to do what I should like to do, without the laborious manual method.

 

BTW, a question of semantics, totally irrelevant to the thread. 'Ducking', often used in broadcasting dialogues, is a time-honoured term for reducing sound volume to make way for other sound https://en.wikipedia.org/wiki/Ducking while 'damping' reduces the magnitude of oscillations over a period of time https://en.wikipedia.org/wiki/Damping_ratio although I agree that 'damping' is sometimes used to alter the sound (quality, not necessarily amplitude) of a musical instrument. Please excuse me for my presumption in suggesting a logical correction. In context, I believe the 'ducking' shown is the correct terminology.

browj2 wrote on 10/24/2019, 7:33 AM

@devil

Hi,

Yes, "ducking" is the correct term. I wish that Magix would change this in their manual. Each time I have searched I have looked for "ducking" not "damping."

For anyone else reading this and for completeness, there are more ways to adjust volume and other effects. I prefer to use object effects rather than track for ducking. Go to Effects, Audio effects, General. Select an audio object. You can adjust the Volume more precisely by using keyframes. The only problem is that you have to move the volume slider off of 100 to get Volume to show up in the keyframe area, set a kf, move along the timeline, set a kf at the desired volume, etc. Turn on the volume curve for the object beside Volume in the kf area to see it on the timeline. Just don't forget to go back to the first kf and set it back to 100.

The object volume points are easier to drag than track volume points. The cursor changes to an arrow when you're over the volume curve. However, track automation using the mixer is easy and quick. Just don't go moving anything afterwards.

John CB

John C.B.

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

Glenn-Woiler wrote on 10/25/2019, 8:57 AM

@devil

Hi,

Yes, "ducking" is the correct term. I wish that Magix would change this in their manual. Each time I have searched I have looked for "ducking" not "damping."

For anyone else reading this and for completeness, there are more ways to adjust volume and other effects. I prefer to use object effects rather than track for ducking. Go to Effects, Audio effects, General. Select an audio object. You can adjust the Volume more precisely by using keyframes. The only problem is that you have to move the volume slider off of 100 to get Volume to show up in the keyframe area, set a kf, move along the timeline, set a kf at the desired volume, etc. Turn on the volume curve for the object beside Volume in the kf area to see it on the timeline. Just don't forget to go back to the first kf and set it back to 100.

The object volume points are easier to drag than track volume points. The cursor changes to an arrow when you're over the volume curve. However, track automation using the mixer is easy and quick. Just don't go moving anything afterwards.

John CB

What advanced editors make you use key frames to adjust audio on a clip? Why can't Magix come up to speed and let an audio clip be adjusted as the track is adjusted? Seems a no brainer to me.

browj2 wrote on 10/25/2019, 9:21 AM

@Glenn-Woiler

Hi Glenn,

Could you please explain?

Right now there are object and track level volume adjustments.

How else would you implement ducking if you don't adjust the volume curve?

John CB

John C.B.

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

Glenn-Woiler wrote on 10/25/2019, 9:49 AM

Hi Glenn,

Could you please explain?

Right now there are object and track level volume adjustments.

How else would you implement ducking if you don't adjust the volume curve?

John CB

I am back with 16.0.2.322
Never saw an easy way to vary the volume across a clip in the timeline.

browj2 wrote on 10/25/2019, 9:55 AM

@Glenn-Woiler

Look at the image. In the Audio editor, you set a kf at the beginning and another one where you want. The volume varies between the 2. On the timeline volume curve, make any adjustments that you want - add points, drag points up and down, etc.

John CB

John C.B.

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

Glenn-Woiler wrote on 10/25/2019, 10:03 AM

@browj2

In other editors, I don't need to go in to an audio editor - I just click in the audio clip and each click assigns a node, or "key frame". Not sure why Magix is so far behind. Not wishing to be a pain... but... not sure I made the wise choice a few years ago to get this editor. Multicam worked in version 15 and so far it is broke and I am not paying any more $$

browj2 wrote on 10/25/2019, 10:24 AM

In other editors, I don't need to go in to an audio editor - I just click in the audio clip and each click assigns a node, or "key frame". Not sure why Magix is so far behind. Not wishing to be a pain... but... not sure I made the wise choice a few years ago to get this editor. Multicam worked in version 15 and so far it is broke and I am not paying any more $$

VPX is much more advanced. In audio, you can have curves for each of the following:

  • Volume
  • Panorama
  • AUX 1
  • AUX 2
  • Sharp filter
  • Smooth filter
  • Distortion

For volume in VPX you simply turn on the volume curve (Ctrl+Shift+V) for the object and then click on the green line to set points or keyframes.

I don't see how you can simply click somewhere on an audio object and it puts a volume point there. How can you even select an audio object without a volume point being placed on it?

As for multicam, it is still on the bug list as #15. Someone indicated that after a patch, multicam was now working, but I can't find it. I recall testing it and had no problem. Just to refresh this, what exactly is the problem with multicam?

John CB

Last changed by browj2 on 10/25/2019, 10:24 AM, changed a total of 1 times.

John C.B.

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

Glenn-Woiler wrote on 10/25/2019, 11:31 AM

@browj2 As for multicam, it is still on the bug list as #15. Someone indicated that after a patch, multicam was now working, but I can't find it. I recall testing it and had no problem. Just to refresh this, what exactly is the problem with multicam?

 

In version 15, multicam worked nicely with no hickups. You could stop and come back in and continue. In version 16, it is slow and buggy. Sometimes, in the source window, the separate cam windows do not highlight with red when you click on it. ...but it works however... sometimes. ...if you stop and try to resume, that is when it really falls apart. Audio clips will be messed up and require you to go fix each one. One audio clip will do a fade from the next clip after it - all the way to its start - and you can't get a hold of the little fade node unless you lengthen the clip a tad and then you can fix and put the start back where it should be. The program monitor will not update and show you the selected cam while live multicam switching - after you stop and try to go back in. I have tried all sorts of ways to re-engaging multicam editing if I had to stop somewhere in the middle. It just does not work like it did before. Many times I just go in and cut everything up manually so I am not having to troubleshoot and fix things. And the deal breaker is... It used to work while I had a subscription to VPX version 15. Then a laptop went belly up and I replaced it and when I went to get VPX on it, only the first version of 15 came through and they told me when your subscription lapses, if you go to download it, you only get the version available when you bought your subscription! What kind of nonsense is that??? I paid for a year and should be able to get what was current at the end of the year's subscription! But... this is company policy... - bad policy. So then another laptop dies and it is replaced with a Windows 10 machine and version 15 would not work so they gave me a free upgrade to 16 and no more multicam. If this company had good will, they would give me a version that works with multicam like it did when I bought it. I also edit on Devinci Resolve which is a one time $300 fee for life. They are breaking the Adobe model of pay for it up your nose month after month, year after year. Magix should pay attention. Resolve is tops in many areas but for quick turn around of some projects, VPX still wins for me. But possibly soon, Resolve will pass them by. Sorry to rant... I am just not a happy camper.

browj2 wrote on 10/29/2019, 11:58 AM

@Glenn-Woiler

Latest Version 17.0.2.47

I just tried multicam and the only problem that I have is stuttering during playback. I put this down to my computer not being able to keep up. I was using GoPro 1080p files.

No fades on the audio.

No problem changing cameras - the selected one has a red box around it except at the beginning where you have to select one and it's yellow. Same if you are not in play - move the playback marker, click a camera and it will have yellow around it and the scene change will be made.

Update Service. I suggest that you read what it means. If you are out of service and have to reinstall, it reverts to the version that you had when you last paid, exactly the same as if there was no update service. The update service just gives you updates and new versions in advance and you can keep them so long as you don't have to reinstall if you haven't paid to lock in the new stuff.

It would be helpful if others could validate this with the current version as I still have multicam on the bug list. If it works fine, then I'll remove it from the list.

John CB

John C.B.

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