@Scenestealer @johnebaker

This is a "real" project of about 76 minutes duration containing multiple clips in the same video format. Many are cross-faded and there are a few simple titles to break sections. As far as I recall there are no other effects used (it was a simple "quick and dirty" rough edit of footage shot on a wildlife holiday). All the screen shots were taken within the first few minutes of export so roughly in the same place in the video.

I stated in an earlier post that setting Export=NVIDIA always resulted in a crash; that was true at the time because I was only testing H.264 export and the crash happened regardless of the other display settings. Eg, for settings NV, NV, NV an export to H.264 hangs for about 5 seconds and then gives this message:

And the log shows:

[FATAL]   [MPEGIntel]: MuxDataError |muxer type=AVCHD |DP4 errno=0x04010BC0: Error 3008: not enough data to multiplex |where=DP4MetaMuxer::MuxData called MuxData |input buffer address=0x000000006AD73060, size=118066 |stream=AVC
2021/06/28 08:27:24 [FATAL]   [MPEGIntel]: AVCHDFilePipeline::EncodeVideo frame 56: HardwareEncodeError
2021/06/28 08:27:24 [FATAL]   [MPEGIntel]: MuxDataError |muxer type=AVCHD |DP4 errno=0x04010BC0: Error 3008: not enough data to multiplex |where=DP4MetaMuxer::MuxData called MuxData |input buffer address=0x000000006AD73060, size=100727 |stream=AVC
2021/06/28 08:27:24 [FATAL]   [Export - Engine]: Bounce: CInfoException: 0x8004002b - export->WriteVideoFrame

However, it does not crash when exporting to HEVC (the following is with settings NV, NV, NV):

As an aside, using a setting of Import=NVIDIA on my system always causes a handful of occurrences of the following pair of error messages in the log when opening the project:

[FATAL]   [MXMPEG2 frame request]: GetMXVideoFrame: decode error 0x85008002 means <MXMPEG2 Error 0002: common decode error>
[ERROR]   [Import]: VideoReader_GetFrame: FAILED to get video frame

(but it is not given for every clip!). There are no such errors if Import=iGPU.

But, MEP has also always had issues with my graphics card, so I'm not entirely surprised at the results with VPX; I find display settings of iGPU, iGPU, iGPU the most stable.

Sev.

@ScreenBytes @dond10

I am not able to successfully render and save my mp3 audio file from my movie export as I was able to do prior to accepting and installing the Version 13 of Video Pro X.

Interesting that the specification foot note for .mp3 Import states that it can only be achieved as a standalone audio file and not as part of a V/A container:-

"(4) MP3 audio import – can only be imported as an individual .mp3 file, not as part of a video/audio container such as MKV"

It does however state it can be exported but I assume this is again only as an audio file.

Peter

 

Hi Peter

I says in help under export as mp3

"Note: MP3 export requires Windows Media Player version 10 and up.
The MP3 encoder cannot be used as a codec for the AVI audio file audio tracks."

So the only thing you can do is export as .wav and convert with 3rd party software like Audacity.

In some editions of Windows 10 windows media player is included as an optional feature that you can enable. ... To do that, select the Start button, then select Settings > Apps > Apps & features > Manage optional features > Add a feature > Windows Media Player, and select Install.

Dond

Hi friends, although this is a small error in writing, but it is very disturbing 😀

@lukmanhh

HI,

I already pointed that out on page 2 of this thread - the hint is also in German.

@johnebaker

Hi John EB,

Further to my post about the Orientation and Size/Position/Rotation problems, I just noticed that clicking on the reset of the latter resets the everything except the selection box.

As pointed out by @Beardeboss in another thread, the Center button has disappeared. How could Magix do this? I use that button often.

Whatever happened to Magix' beta testers? Surely they couldn't have missed these problems; they're too obvious.

John CB

@browj2

Hi John

. . . . the Center button has disappeared. How could Magix do this?  . . . .

Because it is not needed, by default when you resize an object it is centred, I believe the Section should also move the Centre point however as we know it is buggy. If it was working correctly then if you move that object to for example a corner and then use the >< on the Anchor point, horizontal or vertical values - which are missing once section is applied, the object becomes centred appropriately as shown below

John EB

@SevCardy @johnebaker

Hi

Thanks Sev for your additional information. Sorry I did no take into account your point in your earlier post about the NVidia Export selection failing.

I think the error mesages may relate to the "Non Standard" Codec ID 27 reported in Media Info of you source files. Can you tell us the source of these files and perhaps copy the full MI analysis of the files you are using?

Also are you running the very latest Intel and Nvidia graphics drivers on your system. You should make sure to use the Nvidia Studio drivers (not the gaming drivers) installed via a clean install option in the driver installer (or after using DDU = Display Driver Uninstaller utility).

Your HEVC exports do not appear to be using Nvidia NVENC HWA at all because this should show up as a graph on the right TM saying "Video Encode" - as ( I think? ) you can see in one of John EB's screenshots elsewhere.

@dond10

Thanks for the additional info about the .mp3 files and Widows media player. MEP / VPX have always relied on WMP's installation for use of the .mp3 codec.

Peter

@SevCardy @johnebaker

Hi

Thanks Sev for your additional information. Sorry I did no take into account your point in your earlier post about the NVidia Export selection failing.

I think the error mesages may relate to the "Non Standard" Codec ID 27 reported in Media Info of you source files. Can you tell us the source of these files and perhaps copy the full MI analysis of the files you are using?

Also are you running the very latest Intel and Nvidia graphics drivers on your system. You should make sure to use the Nvidia Studio drivers (not the gaming drivers) installed via a clean install option in the driver installer (or after using DDU = Display Driver Uninstaller utility).

Your HEVC exports do not appear to be using Nvidia NVENC HWA at all because this should show up as a graph on the right TM saying "Video Encode" - as ( I think? ) you can see in one of John EB's screenshots elsewhere.

@dond10

Thanks for the additional info about the .mp3 files and Widows media player. MEP / VPX have always relied on WMP's installation for use of the .mp3 codec.

Peter

Hi Peter

I'm afraid the info on mp3 is a bit of a red herring for me as I have MEP installed but can't export to mp3.

Dond

@SevCardy, @Scenestealer

Hi Sev, Peter

Sev, is the video file with codec id 27 from a digital TV receiver recording?

A quick search of the Internet produces many results of issues with this codec id.

When posting MediaInfo data please include all the data - there should be more information which may help identify the issue quicker.

John EB

@dond10

Hi Dond

Can you clarify which programs you, have installed, and which you are having issues with, from previous posts you upgraded from VPX 12 to VPX 13, in your last post you mention MEP.

If you have an issue with MEP please create a new topic, this one is about VPX 13.

John EB

@Scenestealer @johnebaker

That's interesting about problems with codec id 27, I hadn't seen anything about that before. All the files in that project were shot on a Panasonic HC-V770 camera. The files are straight from the camera, i.e. have not had any other processing before use (the project was, however, created in MEP, but I am getting the same issues with small test projects created with VPX13). A typical file gives the following MediaInfo (in full):

General
ID                                       : 0 (0x0)
Complete name                            : D:\My Videos\2020\2020 Uganda\20200111-090718.MTS
Format                                   : BDAV
Format/Info                              : Blu-ray Video
File size                                : 41.3 MiB
Duration                                 : 21 s 551 ms
Overall bit rate mode                    : Variable
Overall bit rate                         : 16.1 Mb/s
Maximum Overall bit rate                 : 18.0 Mb/s
Recorded date                            : 2020-01-11 09:06:56+02:00
Writing application                      : Panasonic

Video
ID                                       : 4113 (0x1011)
Menu ID                                  : 1 (0x1)
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : High@L4
Format settings                          : CABAC / 2 Ref Frames
Format settings, CABAC                   : Yes
Format settings, Reference frames        : 2 frames
Format settings, GOP                     : M=3, N=12
Codec ID                                 : 27
Duration                                 : 21 s 640 ms
Bit rate mode                            : Variable
Bit rate                                 : 15.0 Mb/s
Maximum bit rate                         : 16.8 Mb/s
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate                               : 25.000 FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Interlaced
Scan type, store method                  : Separated fields
Scan order                               : Top Field First
Bits/(Pixel*Frame)                       : 0.290
Stream size                              : 38.8 MiB (94%)

Audio
ID                                       : 4352 (0x1100)
Menu ID                                  : 1 (0x1)
Format                                   : AC-3
Format/Info                              : Audio Coding 3
Commercial name                          : Dolby Digital
Codec ID                                 : 129
Duration                                 : 21 s 664 ms
Bit rate mode                            : Constant
Bit rate                                 : 384 kb/s
Channel(s)                               : 6 channels
Channel layout                           : L R C LFE Ls Rs
Sampling rate                            : 48.0 kHz
Frame rate                               : 31.250 FPS (1536 SPF)
Compression mode                         : Lossy
Stream size                              : 1 016 KiB (2%)
Service kind                             : Complete Main

Text
ID                                       : 4608 (0x1200)
Menu ID                                  : 1 (0x1)
Format                                   : PGS
Codec ID                                 : 144
Duration                                 : 21 s 176 ms

@dond10

Hi Dond

Can you clarify which programs you, have installed, and which you are having issues with, from previous posts you upgraded from VPX 12 to VPX 13, in your last post you mention MEP.

If you have an issue with MEP please create a new topic, this one is about VPX 13.

John EB

Hi John EB

Sorry I meant to put WMP not MEP.

Dond

@SevCardy, @MAGIX_Redaktion

Hi Sev

. . . . Panasonic HC-V770 . . . .

That is the Panasonic version of my old Sony camera, there should be no issues at all importing that video format.

I was also surprised to find that the codec id for my Sony MTS clips is also 27.

However I did find 2 bugs:

Objects on timeline:

1. displaying the sound channels does not work correctly - the video clip(s) disappear from the timeline leaving the audio as shown below, playing the timeline does show the clips in the Program monitor correctly
   
   
    
2. extracting the sound channels there is an inconsistency in how the extracted channels waveforms are displayed (or not) and those that are blank, as shown below, have no audio on playback
   
   

John EB

@johnebaker

I am beginning to suspect that it is the file format that is the problem. I've never used Panasonic's software to import the video clips to the PC, I just copy them. I'm guessing their software does something more than just copy the files - possibly conforming them to a standard format. As just copying them worked fine when editing/exporting with MEP and iGPU, I'd just continued to do the same. But carrying the files over to VPX (which can use the NVIDIA card) is now showing up the problems.

When I get some time, I'll download the Panasonic software and import some clips to see if that makes a difference.

Sev.

@johnebaker

Hi John EB

. . . . the Center button has disappeared. How could Magix do this?  . . . .

Because it is not needed, by default when you resize an object it is centred, I believe the Section should also move the Centre point however as we know it is buggy. If it was working correctly then if you move that object to for example a corner and then use the >< on the Anchor point, horizontal or vertical values - which are missing once section is applied, the object becomes centred appropriately as shown below

I disagree with the "by default when you resize an object it is centred" and I would not want this to happen - when I resize, I usually don't want it centred, and especially automatically. You had to reset the horizontal and vertical positions to get that. So, pressing 2 buttons instead of 1 is progress?

Try keyframing a video clip starting a couple of seconds in with size/position changed - smaller, upper right, zoom factor now unknown. The keyframe button does not turn on as it did before and you have to expand the Size/Position/Rotation kf and select something. Try it out. Afterwards, try dragging the playback marker along the keyframe area. KF's keep getting added. Go to close to the beginning of the keyframe area, press playback, give it a second, press the stop button. Does it stop? Mine does not (it did once) until the entire clip has been played back.

We now have X and Y scale in the keyframe area instead of width and height as in the area above. Click on X-scale, it turns on. You have to hold down shift to also turn on Y-scale. Then you can keyframe what used to be zoom. Another step backwards.

Click on Offset:X (what was wrong with X and Y - Offset threw me) and both Offsets turn on by default. In the area above, why not X and Y instead of Horizontal and Vertical so that at least a new user could relate the titles in the kf area with the main area?

To do what I suggested above, you have to turn on X and Y scale and Offset X and Y. How does one do that?

I tried turning all on, moved along the timeline, moved the object, and ended up with a rotation kf with the image upside down.

Basically, the whole thing is a lot more complicated than before and does not work correctly.

I did manage to find the magic sauce to kf properly, but it definitely is not obvious and requires additional work.

Would any previous project that has Size/Position keyframes work properly in this version? I doubt it.

John CB

@SevCardy

Hi

. . . . I've never used Panasonic's software to import the video clips to the PC, I just copy them. I'm guessing their software does something more than just copy the files - possibly conforming them to a standard format.  . . . .

I also just copy them from the camera, VPX 13 imports them with no issues. I normally do not use the Sony software as it is another step that is not needed, the only time I have used it, is for quick GPS tracking overlays for my Sony sportscam video.

John EB

Hi

Just installed latest patch and the size/position/rotation even using KF seems to be work OK. Titles still no good

Dond

@johnebaker @SevCardy @dond10

It looks like my observation that HEVC export is not using Nvidia NVENC HWA has been fixed with the latest patch .103

Fixed: Hardware acceleration during HEVC Encoding with NVIDIA graphic cards

I wonder if this will enable the apparent absence of H.264 HWA export on the Nvidia GPU - can someone test both of these scenarios please.

@MAGIX_Redaktion

Thanks to the team for the swift patches and your notification Stefan.

Peter

@johnebaker

I also just copy them from the camera, VPX 13 imports them with no issues. I normally do not use the Sony software as it is another step that is not needed, the only time I have used it, is for quick GPS tracking overlays for my Sony sportscam video.

Yes, I downloaded the Panasonic software yesterday and all it seems to do is copy the MTS files from the camera, rename them with an m2ts extension, and add a load of other files to the directory which I assume assists their software with editing and export. The only good thing it does is name the video files sensibly with date and time, but I generally do that using the "Advanced Renamer" software. Otherwise the files seem to be identical to the MTS files on the camera's memory card.

Later yesterday I discovered something that may explain the crashes I was getting when exporting H.264 using the setting export=NVIDIA, but I need to do more testing to make sure it wasn't a red herring, and also to test if the latest update fixes the problem.

Sev.

@johnebaker

<sigh> It is as I expected. The crashes with the NVIDIA card are caused by one simple issue. I tend to put a few seconds of "blank" video at the start of each project, and I do this by a quick-and-dirty trick of inserting a title containing just a single space. I even have a user-defined title template to do this, so it is really quick to do and I do it almost automatically, even when setting up test projects.

That simple two-second "title" is what has been causing the problem all along; VPX13 crashes with the usual error message with the tip about updating the Intel CPU graphics driver (sic) or deactivating hardware acceleration. Interestingly this happens at exactly the start of the next video clip (even if there is a "real" title following the blank one). Removing that "blank" title, enables the project to export to conclusion - even though there are "blank" titles (marking the ends of chapters) elsewhere in the project.

The odd thing is, setting the display options to iGPU, iGPU, iGPU gives no problems with these blank titles at all.

@Scenestealer

Export to H.264 (on my test project which is 76 mins long) shows NVIDIA use of 3d, Encode and Decode in PerfMon. Total use of the card is averaging around 25%. The export took about 28 mins. The iGPU is showing around 3% use of 3D and zero for everything else. I think that answers one of your questions.

Sev

@SevCardy @johnebaker

Export to H.264 (on my test project which is 76 mins long) shows NVIDIA use of 3d, Encode and Decode in PerfMon. Total use of the card is averaging around 25%. The export took about 28 mins. The iGPU is showing around 3% use of 3D and zero for everything else. I think that answers one of your questions.

Yay! At last it is working. This is a big step forward for Magix.

Hopefully users without Intel iGPU's who use Nvidia or AMD GPU's can now use HWA for export of H.264 & HEVC material!

Peter

@johnebaker

Sorry to keep beating on this, but I am not pleased with the Size/Position changes and keep finding problems.

I created a project in MEP2021 with size/position keyframing and turned on the X curve. It opened and played correctly in VPX13. At least there is that.

However, in VPX13 (19.0.1.103), turning on the eye in the kf area does not turn on the curve. Can you confirm?

As soon as I tried moving a point on the curve of the object where it worked (done in MEP), the curve disappeared.

Next without using the PiP buttons, reduce the size of a video clip to 50%. You have to calculate. It should be in the middle of the screen. Now put it at the upper left corner. For me this is home, but home is now the anchor point. How do you get the image to be aligned with the left or top edge? Before, just give X or Y a 0. Now, you have to do some serious calculations. X = -460, Y = 270; this is the position of the anchor point, not the left and top edge of the image.

Now trying doing the same thing but with a 50% size and aligning with the bottom right of the screen. Before, one could calculate from the origin minus the width or height of the image. Now, you have to do some fancier calculations to get this.

Now you can try the PiP effects. This will throw off the location of the handles box.

Now try some keyframing by moving along the timeline and dragging and resizing the image. Ooops! Did you forget to turn on XY keyframing? And how do you also turn on size keyframing at the same time? Everything? Before, we could just move along the timeline, resize/position and the kf's were created, move along.

Articles/tutorials have been published with the coordinates for images sizes/positions for video walls or PiP. They now go in the toilet.

The only way out that I can see would be to move the anchor point to one of the nodes. Thus buttons to place the anchor point on a node would be most helpful or at the very least, have the anchor point snap to a node when dragged over one.

I still find this whole change convoluted and there are too many problems to be able to coherently suggest solutions.

I still want the zoom slider and zoom factor box and the Centre button (even though I can reset X and Y of the anchor point with 2 clicks instead of 1). I want automatic keyframing of whatever graphical changes I make when moving along the timeline and changing something.

And, of course, the bugs should be fixed.

I have not yet tried out any previous saved effects or saving and loading new effects.

Sorry, but my time is limited - have to keep working on the new old house.

John CB

@johnebaker

An update to my earlier post: leaving blank space at the start of the project causes the same crash. So does adding an image that is all black. But adding a "real" image works! Something weird going on here. Can anyone else reproduce the same issue?

Sev.