There is a new patch for VPX 17.0.2.44.
Not sure what is in it yet but it is only 15MB.
Peter
New patch VPX11 17.0.2.44
Scenestealer
wrote on 10/1/2019, 6:23 AM
Comments
browj2
wrote on 10/1/2019, 7:36 AM
Hi Peter,
Managed to get the list on the second computer.
Important changes in version 17.0.2.44
- Fixed: Crash occuring when switching to tab "Effects"
- Fixed: Crash if playing fullscreen in "VideoForWindows" mode
John CB
DugsBugs
wrote on 10/1/2019, 6:43 PM
Who has been having these problems?
I have never crashed with either of these functions.
Magix seems to address the minority but things that have been plaguing us for years stay the same.
I now do every update since I pay for the service and hope Magix haven't broken something in the process and hope that some day, they will come up with a stable reliable product before I die.
Doug.
browj2
wrote on 10/3/2019, 9:57 AM
New bug in patch 17.0.2.44:
30. Title with Blurry transition/fade incorrect title size: Apply Effect transitions basic/Blurry:Counter-clockwise or any other to beginning or end of a title. If in a fade in, the title size becomes very large and then jumps to the correct size from one frame to the next at the end of the fade. In the images below, the first one shows the title in the last frame of the fade in; the second shows the next frame.
Tested in 17.0.1.32 - no problem, so it's a new bug.
John CB
johnebaker
wrote on 10/3/2019, 1:30 PM
Hi John
Confirmed - I have the same issue with all the blur effects in both VPX 11 and MEP 2020.
As a counter check also tested in MEP 2016 - no issue.
John EB
browj2
wrote on 10/4/2019, 9:02 AM
Update on bug list
I received feedback from Magix about the updated bug list. They are reviewing it and adding to their bug entries anything that was not already there, etc. To paraphrase, a list this size needs a lot of time so that it can be presented correctly. Hmmm. Most of the points, with the exception of the last few, are quite old, have been submitted multiple times as the list was updated, commented upon by Magix saying that they were on the list, but very little has been done. I think that the community needs to raise more tickets about these to get their attention, or something.
I am also trying to prepare a reply. If anyone has suggestions about how to reply, please let me know.
Here is a link to the updated list, revision 8. Some of the items on the list were raised by others and I have not been able or taken the time to validate. If anyone sees anything that is on the list that has been resolved, please let me know.
MIDI Support
On another topic, I mentioned to Magix that on the Magix.com site, VPX, version comparison chart, under Audio Editing, it indicates that VPX has MIDI support. We brought this up once before and it was determined that VPX does not have MIDI support. Here is the reply and clarification from Magix. They admit that it is a bit misleading.
"MAGIX Video Pro X supports MIDI timecode (MTC). This allows MAGIX Video Pro X to be synchronized from external sources and lets it synchronize external sources. With a virtual MIDI cable (e.g. "LoopBe1") it is also possible to synchronize MAGIX Video Pro X with Samplitude or Sequoia. A requirement for this is that a virtual VIDI cable has been successfully installed."
I have used LoopBe1 to synchronize VPX with Samplitude and it works very well. This allows one to modify the video in VPX whilst creating a soundtrack in Samplitude. I think that Magix should add in a comment about this as I believe that people looking at it would assume that they could import a midi file to the timeline, which cannot be done. Comments?
John CB