@browj2

Hi John

Item 50 - To modify the parameters, we used to be able to use the Size/Position effect.

AFAICS SP&R and Camera Zoom are 2 independent 'effects', I am getting the same behaviour testing in MEP 2021 and MEP 2016.

John EB

@CubeAce

Hi Ray,

Camera/Zoom always uses Size/Position and creates keyframes. This is just a simple semi-automated way to use Size/Position to do the same thing. You can't see the keyframes in your image because your keyframe area is too small.

Open it up (make the area higer by dragging the Media Pool upwards from the kf area:

Now you'll see the keyframes. Before MEP2022 and VPX13, you could simply use Camera/Zoom, switch to Size/Position and modify the keyframes. Now you can't.

After doing the above, select SPR and Apply Effect. A new keyframe subject is entered and you cannot modify the Image Size/Position items or keyframes.

This is what you'll see. Make sure that your kf area is high enough to see this.

John CB

Hi John

Oops!

OK. Re-opened the project. I only used the camera zoom to alter positions and size and I didn't touch size position rotation although those changes I made are recorded there.

And they kept their settings.

Am I missing something? Does it matter is you can't use size position rotation? The movement seems to be recorded in that effect even if you use the camera zoom function.I didn't try to rotate the image.

Now I have tried to rotate the image and save it.

It seems to have worked OK.

Ray.

@CubeAce

Hi Ray,

I will post a video shortly.

Try this. Afer doing the Camera/Zoom, switch to SPR. Make sure that the playback marker is in an area that was the original size, and drag a handle to make the image smaller, thus creating a Zoom out or PiP effect of the image. Now play it back. The image should stay the same size and the content should do the Camera Zoom. It doesn't. So something is wrong with this. I think that Magix forget to change Camera/Zoom to use the new SPR, or the new SPR doesn't quite work right with Camera/Zoom.

John CB

And, here is the video:

Comments/improvements?

John CB

@browj2

Hi John

I can see what you are getting at, I can replicate it once, if you reset the effects and try again I get different weird effects happening, depending on how many times I do the steps shown, not only is there something wrong between the 2 items you are showing, resetting the effects does not work correctly either.

Only a restart of VPX fixes the reset issue until you go for a reset again then you are back in the loop again.

Hope this makes sense.

John EB

@browj2

Hi John.

OK.

I just witnessed all the key frames disappear as I switched from one effect to the other.

Maybe not exactly what you get but very odd.

Ray.

@johnebaker

Hi John EB,

Thanks for taking a look. Yes, trying again can give strange and different results. In making up the video, I had to reboot VPX several times just to be able to get a clean run at the effects. I didn't include that as it was already complicated enough.

@CubeAce

Hi Ray,

I haven't seen the keyframes disappear. Can you replicate that?

John CB

@browj2 @johnebaker

Hi John.

I just tried for you but all I did was crash the program.

Here is the crash log.

----------------------------------------------------------------------
MAGIX Movie Edit Pro Premium  03.06.2022  23:29
----------------------------------------------------------------------
CrashDump 20220603_232949_v21.0.2.138.dmp successfully written

Error in module "Qt5GuiMx64Qt5.15.1.dll" (Load address: 0x00007FF92BF40000) to address 0x00007FF92BFCFDD1 (Exception 0xc0000005 "ACCESS_VIOLATION")

Main Thread   (ThreadID: 0000326c)
  00007ff92bfcfdc9   13 48 8b f8 44 8b 42 04
  00007ff92bfcfdd1 > 44 89 40 04 4c 8b 0b 49
  00007ff92bfcfdd9   8b 49 10 4d 63 41 04 49

videodeluxe.exe    30.03.2022  22:34      5774b97b

Memory Allocation
Base:        1.080
PE:        176
Pages:        65.536

PI:        45.920
PI_TEMP_DATA:    41.312
SI:        387.040
SI_TEMP_DATA:    48.000
FSI:        0

Blocks:        0
Temporary:    0
BE:        0
PLE:        688.000
BE Pool:        288
PLE Pool:        0
wHdr/inst:    0
Image Cache:    186.015.981
Video:        185.381.127(0/0)
Bitmap:        0

Thumbnail Cache:    1.119.981
SI Display Cache:    1.059.600
PLE Display Cache:    238.596

Buffer:        0
Pointer:        0

Title:        0
Memory GF:        0
Memory GF Zero:        0
Memory GF Zero_Dyn:        0
Memory GF Dyn:        0
Memory TT:        0
Audio Effect:        216
PPE:        40.000

Video Monitor:    0
malloc/free:    0
DIB:        5.032

VP: admin:        0
VP+Trans: privateData:        0
Transitions::        0

Frame Cache:    0
EXIF:        0
VSW:        0
DVDMAKER:    0
global UI (malloc):    0
global UI (valloc):    0
NOWAGGLE:    0
ReaderFrame:    0
MP3 Reader:    0
JPEG buffer:    0

Private Bytes:    4868 MByte

TLS:        975
MXGUI:        98.438.636
Sum:        473.728.409

Processor [46]  3600MHz  4 Core(s)
Microsoft Windows NT 10.0 (Build 19044)
Used Memory: 4015 MB             Max Used Memory: 6062 MB
Free Virtual Memory: 25352 MB     Total Virtual Memory: 131072 GB

 Call stack:
Address   Frame
00007FF92BFCFDD1  000000000014B770  MxQt::qt_xForm_helper+8B1
00007FF92C1D57CE  000000000014B7C0  MxQt::QDashedStrokeProcessor::setInvScale+379E
00007FF92C1E0ADA  000000000014B8F0  MxQt::qTriangulate+2ECA
00007FF92C1DD739  000000000014B9B0  MxQt::qTriangulate+89
00007FF9331FB4E5  000000000014B9B8  0000:00000000

Ray.

Additional bugs:

53.       Keyframe area details expansion does not stay collapsed – Same problem in VPX14 and Movie Edit Pro/Movie Studio 2022. Adding an effect, like Size/Position/Rotation (SPR) shows the collapsed effect in the keyframe area. Click on the popdown to expand the effect to the details. Click again to close the details. Select another object, select the first object, and the effect details is expanded. Close the details. Select another clip, apply the SPR effect, and the effect details are shown in the keyframe area instead of being collapsed. The collapsed effect should always be shown in the keyframe area the first time that the effect has been used. When collapsed and navigating away and coming back to the object, the effect in the keyframe area should remain collapsed. The same thing occurs with other effects. Upon reopening the Program, the effects in the keyframe area are collapsed until one expands them.

If the effect has been collapsed, it should stay collapsed unless expanded. For the same effect on another object, it should start collapsed, not expanded just because the same effect was expanded on another clip.

See the video:

See this thread on the forum:

            MEP(MS)2022 and another annoying bug I've just found (magix.info)

            [Ticket#XXXX]

54.       Attach to picture position – First raised by John E. Baker – with two tickets and nothing resolved.

An issue with the Attach to picture position effect appears to have been introduced with MEP 2022 and VPX 13 and is also in VPX 14, as a result of the Anchor point being made movable and defaulting to the centre of the screen instead of the old way referencing the top left corner (0,0).

Leaving the anchor point in the centre, the object being attached is offset after running the effect analysis.  Setting the Anchor point to top left corner - the old 0,0 reference point, and the object tracks correctly.

Looks like maths for calculating the position of the object are not taking into account the anchor point not being at centre of the object.

Nothing shows up in the keyframe area. In previous versions, the effect Pin object x/y would show up in the keyframe area. As well, the curves of keyframed effects could be turned on for the timeline in previous versions.

John CB

@browj2

Hi John.

Since the last Windows 10 update MEP 2022 on my machine is no longer creating a project folder when selecting Create a New Project. It will remember where I place project files but only after a project folder is created. Otherwise it just goes to the default drive selected in the program setup section.

Ray.

@CubeAce

Hi Ray,

When you start a new project and give it a name, nothing is actually saved. Note that the folder is greyed out. When you save for the first time, MEP will use the default name or the name that you indicated, but you have to indicate the path and if not already created, create the folder. It is not done automatically.

However, if you check "Copy media to project folder" on the New Project screen, you get access to the folder box and you can indicate where you want it created. The folder will be created automatically using the project name the next time that you do this for a new project, because MEP remembers that the "Copy media to project folder" box was checked.

Currently, the box is unchecked.

John CB

@browj2

Hi John

Item 54 - Attach to picture position - I have had further feedback on this and it is being worked on.

@CubeAce

Hi Ray

. . . . Since the last Windows 10 update MEP 2022 on my machine is no longer creating a project folder  . . . .

Which Windows 10 update was this?

Works fine on my laptop - last update for me was KB5015807 (July 12 2022).

Is Antivirus blocking the drive ?

John EB

@johnebaker

Hi John.

Same update patch. Was working before the update. MEP will save an MVP file to the correct location once a folder is made and retain the memory but the program itself is not creating project folders as seen in the video clip.

The drive is not being blocked by my antivirus. Other programs can create folders there.

At present my workaround is to create project folders in Windows and then point the program to the already created folder. It's more annoying than an actual problem.

I haven't tried the same with VPX 12 yet.

Ray.

@browj2

Hi John.

Sorry.

Missed your reply above John EBs.

You could well be (and probably are) correct. In the past that has been checked but I thought I would try projects not containing the source files.

It never occurred to me the program would behave differently.

Thank you for the clarification although if I do have objects in the timeline and press save, there is still no project folder created. The MVP file just gets dumped directly onto the J drive.

[Edit] Is this because some people would put all such created projects into one folder?

Ray.

@CubeAce

Hi Ray

Some users prefer to have all their source media in different locations and then bring what is used in the project into the project folder so all is in one place.

When using the Copy into project folder option, MEP/VPX renames the media to avoid name clashes eg C0661.MP4 to C0661_75F8D842.MP4

Personally I prefer an organised project folder structure for each project. I use a master folder (Blank) with subfolders which I copy and paste, rename, before downloading the first recorded media from the cameras.

The Image and Video folders are further subdivided by camera.

John EB

@johnebaker

Hi John.

I do understand that people will have their own way of working and setups for folder paths and contents may vary.

It just caught me out not producing a folder automatically as normally I would import the files into a project.

Ray.

@CubeAce

Hi Ray,

Thank you for the clarification although if I do have objects in the timeline and press save, there is still no project folder created. The MVP file just gets dumped directly onto the J drive.

Having objects on the timeline has nothing to do with it. It is a workflow activity.

The MVP does not "just gets dumped directly onto the J drive." You are the one who does this. You are given the option to decide where you want to put the project file when you first save the project. See below.

With "Copy media to project folder" unchecked, no folder is created for the project.

The default is whatever you have indicated in the Program Settings, Folders:

unless you saved to another location the last time that you saved. VPX/MEP remembers the last location.

When you press on the Save button (orr File, Save) the first after starting a new project, you will get the following Explorer screen where you can change the project name and the location:

If you don't change the location/path, then it "just gets dumped directly onto the J drive."

The only bug seems to be that the default location has, on occasion, been changed to the last export location or something like that.

When you save for the first time in this mode, the explorer will always open and always has, to allow you to choose/change the project name and location. At this time, you can select or create a folder for the MVP file and its backups. Many users forget to give a project a name in the startup screen and would be stuck with the default name - the date. As part of the work flow for a new project, one should always give the project a name before doing anything else, and immediately upon starting that project, do a save so that baks and temporary files go to the correct location.

With "Copy media to project folder" checked, you get access to the folder folder field:

where you now decide if you want the proposed folder - the default or last location with the project name as the folder name, or something else. As soon as you click on OK, the folder will be created and used, but nothing will be in it until you do a save or add material to the timeline. Do a save to make sure that it is locked in. If you don't do a save at all and decide to exit the project, you will be asked if you want to save. If you don't want to save, you will be asked if you want to delete the folder that was created.

John CB

@browj2

Hi John.

I do understand what you are saying but I don't see why the option for where to save it should be greyed out in one option but available in another. Easy enough to fix as I make a folder beforehand now and then save the MVP to that folder.

I just find it odd to have options removed unless it is trying to stop something happening that may be unhelpful or destructive in some way. but for the life of me I can't think of a reason.

Ray.

@CubeAce

Hi Ray,

I added some information and an image to the previous post. Take another look.

The folder is greyed out because you may not want a folder created and no new folder is required. You get the opportunity to do what you want when you first save.

John CB

@browj2

you may not want a folder created and no new folder is required.

This is where we differ (Different work flows) but I now understand that in some instances for some people this would be an undesirable action.

Thank you for your clarification.

Ray.

Patch for Video Pro X 14: 20.0.3.169

Downloading it now (1 GB file).

Unfortunately, most of the bugs that I have raised with Magix do not appear to have been fixed.

As nice as it is to have the following bugs fixed, there are still many more. Given the large amount of time that Magix has had, they could have and should have done more. Not amused.

Fixed: Bugs with effects based on size/position/rotation, including:

• Title positioning
• Object tracking
• Section
• Camera/zoom shot
• 3D morph
• Captions/title templates
• Image objects

Fixed: Error that occurred during resetting the window layout

Fixed: Preview error when working in multicam mode

Fixed: Program settings for stereo 3D projects now set correctly

Fixed: Error when pausing the loading process for preview pictures in Explorer

Fixed: Color conversion error

Fixed: Error relating to message 'Internal Error - Page used in WriteAllPagesForSI'

Fixed: Flickering and display of wrong frames for dynamic titles, timecodes and X3D

Optimized: Effect overview 

• Effect parameters display
• Color palette for effect curves (requires resetting the program settings)
• Effect parameter remains selected
• Fixed: Error that occurred when working with keyframes
• Fixed: Keyframes for colors do not include all color channels
• Fixed: Button for creating keyframes occasionally inactive

John CB