@browj2

To get the eyes, you first have to add a kf, then it turns on.

Ah, I would if I could, but most of the time the add keyframe icon is greyed out as in my screenshot! And when it does appear, clicking it usually has no obvious effect, and still no eyes!

Sev.

@browj2, @MAGIX_Redaktion

Hi John

The Size position does take a little getting used to and some mental gymnastics, or save the settings as presets, with 0,0 being the centre of the screen rather than top left.

I would have preferred an option, either in the program settings or the Size, position, rotation effect, to select which reference point system you want to work with.

Like you busy during the day to check will do for the other issues ASAP.

John EB

@SevCardy, @MAGIX_Redaktion

Hi

The issue appearing with a black image or space, would suggest this may be a problem with the use of the NV shaders in that, in a sense, they have nothing to work with - ie all data in/out is 0.

John EB

@johnebaker @SevCardy

What if you made a 'black' jpg or bmp with the value of 1.1.1.?

Ray.

@SevCardy

Hi Sev,

Ah, I would if I could, but most of the time the add keyframe icon is greyed out as in my screenshot! And when it does appear, clicking it usually has no obvious effect, and still no eyes!

Sev.

Select the offset XY - either should turn on both, then you can kf. Or you can select X or Y scale or both with Shift select. You can select all using select X scale, shift select last item.

John CB

@CubeAce

What if you made a 'black' jpg or bmp with the value of 1.1.1.?

That sounded like a brilliant idea! Then I tried it and it doesn't work. In fact it appears to be a problem with any image of a single colour. Put just a few lines of a different colour on the image, and it works!

Sev

@SevCardy

Hi Sev.

Second suggestion.

Use a normal video file trimmed to length but pull the transparency down to the last two available sections of the slider. This appears black on my screen on the finished export (Not using VXP13 unfortunately) but when I export it I don't get the 'no image' warning before exporting.

Ray.

@CubeAce

Good suggestion. Works well on playback within VPX13. Exports without error, but the resulting video file shows the video clip with no transparency! Game, set, and match to Magix I feel....

Sev.

Problem that started today, with vid file that had been working OK, is that when I start to play it the vid screen goes blank in under 1sec.

Dond

I seem to have found the problem. When I set my Radeon 500 series graphics card for processing hardware acceleration it causes the video loss.

Put this back to intel UHD it does seem to work OK

Dond

@SevCardy

Hi Sev.

You said.

Good suggestion. Works well on playback within VPX13. Exports without error, but the resulting video file shows the video clip with no transparency! Game, set, and match to Magix I feel....

If the start section is now blank (black) but then the video shows, then am I missing something in what you want in your requirements.

Ray.

@dond10

Hi Dond

There are some inconsistencies with using a AMD or Nvidia setting for the Processing option.

I have several issues when testing with HEVC, Variable Frame Rate video from a mobile phone:

1. some clips play fully others the screen goes blank after a some seconds. I have to change the processing GPU setting to Intel
    
2. when a portrait version is imported into a landscape project, it is stretched to fill the screen instead of the previous behaviour where it was pillar boxed with black bars left and right.
    
3. VFR video is still not handled correctly resulting in glitches in the Aspect Ratio on play back and exports irrespective of the GPU settings.

John EB

@dond10

Hi Dond

There are some inconsistencies with using a AMD or Nvidia setting for the Processing option.

I have several issues when testing with HEVC, Variable Frame Rate video from a mobile phone:

1. some clips play fully others the screen goes blank after a some seconds. I have to change the processing GPU setting to Intel
    
2. when a portrait version is imported into a landscape project, it is stretched to fill the screen instead of the previous behaviour where it was pillar boxed with black bars left and right.
    
3. VFR video is still not handled correctly resulting in glitches in the Aspect Ratio on play back and exports irrespective of the GPU settings.

John EB

Hi John EB

It looks like I will have to leave the settings with Intel until things are sorted

Dond

@CubeAce

Sorry, it was my imprecise description. If I include a video clip with the transparency turned right down as the first clip in the project per your suggestion, then playback from the timeline in VPX shows exactly what you would expect: that first clip appears black and the following video clips are shown normally. However, when I export the project and play back the exported file with VLC, the first clip shows as a normal video clip (i.e. not black).

This is using display settings of NV, NV, NV of course. A black image or a blank title will work fine with the display settings set to Intel, Intel, Intel so in that case this work-around is unnecessary. It seems that all roads lead to having to use Intel, Intel, Intel as the display settings until the issues with NV are sorted.

Sev.

@SevCardy

Hi Sev. No problem.

It doesn't help when Magix doesn't state if there are any conditions to how it works. In the past most of the export hardware encoding was done using an Intel GPU as far as I can tell with the nvidia card taking care of most of the 3D work. I wish they would state which GPU is capable of what it can do rather than letting us endlessly looking for a setup that may give bit more performance. Then again we don't know what percentage Windows has a say in this or why a driver can do one thing supposedly in one application but seemingly incapable of the same action in another program. I don't even pretend to know what is going on. In VPX 11 all I can say is both of my suggestions worked so it's not the GPUs or Windows drivers or Windows.

So as you said.

Game, set, and match to Magix I feel....

😞😞😞

Ray.

@CubeAce

On reflection, I'm not surprised that the "transparent" video clip trick didn't work. In fact, I've found it doesn't work in VPX13 with any display settings using GPUs (the "software" options for display settings do work). That's because the transparency is an adjustment of the video level and, as I've already reported, fades to/from black (adjustments of video level) do not work with any GPU settings in VPX13.

Sev.

Has anyone at Magix ever heard of the phrase 'if it ain't broke, don't fix it'? I cannot believe how buggy 13 is and I've just effectively spent £109 to break my previously working system. I cannot use titles without massive loop-around other functions, plus other meaningless alterations which just slow me down. What happened to keyframes for size/position of titles? I want to move some according to the video content (as I could in the previous version) but now I can't. Why? WHY??? I have jobs to do which I have promised and now I can't finish them. You'd better wake up, Magix, or you'll find you have an exodus on your hands. And I might well be at the head of the queue. TEST THE BLASTED STUFF PROPERLY BEFORE YOU RELEASE IT, YOU NUMPTIES!!!

@dond10 @johnebaker

It looks like I will have to leave the settings with Intel until things are sorted

I have done a LOT of testing of VPX13 over the last few days, mainly on exporting, but I must now get on with other work. However, in summary, my findings are:

• With 1920x1080i AVCHD source material and exporting to mp4 AVCHD transport stream (m2ts file): using display settings of Intel, Intel, Intel is the most stable.
• With 1920x1080i AVCHD source material and burning a BD with the preset "1920x1080i PAL (Default)": using display settings of Intel, Intel, Intel cause the output to be abandoned with an error (bizarre considering export to .m2ts works!). I haven't found a GPU setting that works without a crash or multiple errors reported in the log.
• With 1920x1080i AVCHD source material and burning a BD with the preset "1920x1080p24fps": the only stable option is to use display settings of Intel, Intel, Intel.
• With 4K source and exporting to HEVC ("MP4 FullHD 1920x1080 25"): display settings of Intel, Intel, Intel cause the output to be abandoned with an error. Display settings of NVIDIA, NVIDIA, NVIDIA appear to work perfectly and it is very fast (about one third of real time on my system).
• Regardless of GPU settings (Intel or NVIDIA) or video format, all fades to/from black throughout the project are ignored on export. Cross-fades (technically they are cross-dissolves) work fine though. Using a display setting of Microsoft WARP for export resolves this issue, but it is of course very slow.
• A black or blank clip at the beginning of a video with AVCHD source material (and only at the beginning!) causes the export to crash when using a display setting of export=NVIDIA.

Your mileage may, of course, differ. It seems like a case of "choose the display settings to match your project".

Sev.

I really feel for he newcomers to VPX using it for the first time.
I contacted the support desk and they supplied me with current patch 18.0.1.95 so I can stay with 12 and easily reinstall it if needed down the track.
I think they need to remove 13 from the website until they have sorted the problems out.
As mentioned, 12 is the best version they have had in a long time even though there are some of you have issues with 12, which will always be the case with any editing software.
Stick with 12 and keep enjoying what you do.
Doug.

Hi Everyone

New patch 19.0.1.105released - see here.

Section, Title and Export range issues are fixed , Display audio channels for Surround Sound now working - still get loss of audio waveform when extracting the channels.

John EB

@johnebaker

Hi John.

What's left to fix?

Ray.

@CubeAce

Hi Ray

. . . . What's left to fix? . . . .

So far in testing:-

1. The manual.
    
2. De-interlacing option in Program settings, Device options not available for Standard Renderer (Direct 3D) only available when using Alternative mode 2. Manual says the option should be available.
    
3. Import/Export tab - no options for HWA, this may be a case of it is not needed as under the Device options there is the option to use Microsoft WARP.
   
   and as previously commented
    
4. loss of audio waveform when extracting the channels from Surround Sound.

John EB