Hi Mathias,

Good of you to ask. Below is the list of problems that I put in my thread about the new version and it contains those mentioned by Jon and more. I have also included some problems that have been outstanding.

VPX 16.0.1.242

Bugs (1 to 7 are new problems):

1. Import tab: Link to the Movie Templates along with the various lengths is missing..
2. Import tab: Link to the folder under MAGIX Tools for XAR is missing.
3. Import tab: Cloud Import opens a German interface for me.
4. Templates tab: Image Objects - ColorFields and Pictures - the preview icons do not show. They are in the folder under Program Data, but they do not show up on the screen.
5. Templates tab: Transitions: Missing Movie transitions.
6. Templates tab: The vertical scroll bar cannot be dragged up and down, only sideways to expand/contract the listing window. The mouse indicator changes to a left/right arrow. This may just be a problem on my hi-resolution Surface Pro 4. I haven't installed the new version on my desktop yet.
7. J/L-cut command: Hold down Alt and drag the end of a trimmed clip, either the video part or the audio part to do this. However, holding down Alt and dragging on the audio or video part away from the end moves it independently, thus getting audio and video out of sync. Was this intentional to be used in cases where the A/V is slightly out of sync and one wants to slightly move the audio?
8. There should be a warning somehow that users should not install the new content and try to update from 236 to 242 at the same time. One user had a fatal crash, requiring uninstall, reinstall.
9. On-going problem: Right-click on the audio part of a video track, no command for "Edit in external editor." This has been an intermittent problem, sometimes it's there, sometimes not. This gets linked to the next problem if one wants to export to Samplitude (to EDL) and include all objects. Each audio part of a video clip has to be mixed down, but the right-click Edit in external editor is not always there.
10. On-going problem: Exporting from Samplitude Pro X3 to Video Pro X (see under the export options in Samplitude), mixes down the audio, saves the file, opens Video Pro X but the audio file does not show up in VPX. If VPX is open before exporting, Samplitude tries to open a second instance; it should not. Going from MusicMaker to MEP (both ways) is simple and effective. Going from Samplitude to VPX (both ways) is almost impossible.
11. There should be a Share menu in VPX (like in MEP) and it should be possible to go back and forth to MusicMaker and Samplitude as can be done with Movie Edit Pro.
12. Major annoyance: page 19 of the VPX10 manual states: "The Media Pool has been completely redesigned. It now features direct access to the MAGIX Store, where you can buy additional content and functions for direct use. If you have already purchased content with other MAGIX programs, this can also be used in MAGIX Video Pro X." This is not true as anything purchased through the in-app Store of MusicMaker cannot be used in VPX or MEP, and vice versa.

I have screen captures and videos of the above if you would like to see any of them to understand better. Please let me know.

Resolved:

1. Object and Edit Trimmer: the bug that I raised recently of not moving all objects when a clip was lengthened has been fixed - thank you, but I still have a problem with the right button of the Object Content. It may move 1 frame but no more (usually) but I can hold down Alt+Shift and click and it moves 5 frames; go back several frames with the left arrow, go forward with the right arrow and it only does 1 frame. There are ways to get it to work, like clicking on the Move transition buttons which seems to turn on the right button for the Object Content. I will submit a video with my ticket on this.
2. The OFX screen: the sliders and buttons now all fit in the width of the default window (almost, as there is just a small amount missing, but it may be the Surface Pro 4 problem). No longer any need to scroll to the right.

Puzzling new feature:

I can't figure out what is meant on the Magix.com web site or where this is in the program:

"Object extraction Exactly like you'd imagine. Video Pro X's new object extraction algorithm makes it possible to recognize and extract objects from videos."

It looks like the program identifies a moving object and masks the background. If so, it would be a major feat, but I could not find anywhere as to how to apply this.

However, if it is just the anti-spill improvement, then the text should be reworded to says.

Can you explain what this means? Or did the feature not make it into the final version?

Other than all of that, it seems to work well. I will now put it on my desktop.

Thanks,

John CB

New icons are very annoying. As you can see the icon is obscured and it is hard to "catch" it to drag it onto the video.

The old connections were better. Even if the icons are small, we can easily drag them onto the video clip.

I have now installed the new version on my desktop. I copied over my Video_Pro_X.ini file and the .pmly (window setups) files over to the new version and everything worked fine.

I can confirm that for Bugs point 6 in my previous post and Resolved point 2, the problems are only with my Surface Pro and must be related to the resolution.

Also for Resolved point 1, I mentioned an on-going problem with the right button of the Object Content feature (does the same as the new Move Object Content feature). I found a new problem. The counter in the Edit Trimmer shows 0 when the head of the clip has been trimmed; the Object Trimmer shows the correct value. So, I'll call these Bug 13.

For my Bugs 10 and 11, I tried going from MusicMaker to VPX using the Share feature in MusicMaker. VPX was open and the playback marker partway along the timeline. MusicMaker mixed down the audio, sent it to VPX and placed it on the timeline at the location of the playback marker. This is exactly what Samplitude should do. I don't know if the problem is with VPX or Samplitude, but there is a problem.

I don't have an NVidia graphics card, so I can't test that new feature, HEVC/H.265 video export with NVENC support from NVIDIA. It would be interesting to hear from those who do.

Other than that, everything that I have tried so far, works fine.

John CB

I don't have an NVidia graphics card, so I can't test that new feature, HEVC/H.265 video export with NVENC support from NVIDIA. It would be interesting to hear from those who do.

@Michal-MST

Wow! Looks like NVidia owners should be pleased.

Re your post about the icons, I just noticed that there is a dropdown menu to change the size of the icons from very small, to small, normal and big. Did you try this?

John CB

I'm on version 16.0.1.236. When I follow the update path, it says I have the latest version. If I go to the 'Patches and FAQs' section of my online account, there's no mention of 16.0.1.242. How do I get that patch?

I still have the problem of VPX10 producing very juddery (unusable) playback as soon as I select 'Video Output'. As I mentioned in a previous post, my VPX6 version plays 'Video Output' buttery smooth.

Further testing VPX10, when 'Video Output' is not selected I play back at half resolution (720p). Very smooth. But if I change to Full Screen (1080p), the playback is as juddery as if 'Video Output' was selected. So that's the problem! My Decklink Mini Monitor (when 'Video Output' is selected) always plays back at Full HD 1080p. So VPX10 can't handle Full HD Playback using my NVIDIA Quadro 4000, even though VPX6 can. And so can Davinci Resolve 12.5. Buttery smooth!!

Please, please Magix solve this unnecessary problem!

@discburn

Hi Seamus,

In the program, under Help, Update on-line, you should get a message for the patch, unless you just fell outside of the 365 update plan. Check in your account to see when the expiry date is.

John CB

Hi John,

Yes, I'm within the year. I'll keep an eye on the updates.

Seamus

I am finding it harder to mix down WMV files. It will get to a random point in the mix and stop processing. Sometimes it will re start but mostly it will freeze the program and needs to be force shutdown. When trying to move wmv objects, it is very slow and often freezes when trying to make basic adjustments. I have been using this process for years and now it’s getting harder. Not sure if this is a 242 issue.

Doug

Update on a couple of the bugs that I mentioned.

1. Import tab: Link to the Movie Templates - In Movie Edit Pro, latest version, I see that this has been moved to the Templates tab. Looks like Magix forgot to put them there.

5. Templates tab: Transitions: missing Movie transitions - it seems that Magix has dropped this. The files are still in Program Data and I have a workaround.

@DugsBugs

I did a few tests on a project, exporting a range of 58s:10f, that includes 3 full HD clips and 1 transition that was one of the missing Movie transitions, a short mxv file. Nothing fancy, no effects.

1. Export range to mxv file, import to timeline, no problems
2. Export same range to wmv file, stopped mixing down at 2 seconds, after a while crashed my computer with the blue screen of death
3. Same project, after reboot, exported same range to mxv - 1m21s, size 377,834kB
4. Exported same range to wmv - 3:58, size 127,951kB

No ill effects in the last 15 minutes, and no trouble moving the wmv around on the timeline.

I suggest that you try mxv (export as Magix video) for your intermediates.

Have you had any more problems with wmv?

John CB

@MAGIX_Redaktion

Mathias - this is a major bug requiring an urgent fix. Please have this taken care of.

New potential bug. Could someone please try this?

13. Nested sequences no longer work. I have tried on both computers. The nested sequence that I did in X9 showed up okay in X10, but I could not add any again, no existing ones or new ones. I tried in a new projects as well, unsuccessfully.

A nested sequence is simply dragging a second movie onto the timeline of the first from the project folder.

Edit: I just created a project with a nested sequence in X7 then opened the project in X10. The following message popped up. I clicked on Continue and the project opened with the nested sequence correctly on the timeline. There is a problem somewhere with X10.

It gets worse. Editing the movie of the nested sequence in X10 from the project done with X7, like increasing gamma, causes the preview monitor to go blank. Restarting the project worked. But I did it a second time and X10 froze when I went back to the main movie. Not good.

Reopened it, and when I made changes to the nested sequence movie, back to main movie, preview monitor black, toggling the Video mode from Standard to Compatible and back brought back the video on the preview monitor.

John CB

@browj2

Wouldn't it be better for them to fix the problem.
I have been doing it this way forever. I mix to wmv so I can give that as a secondary video to the customer or to post on Facebook and because DVD is poor quality. A lot of people just want to watch on a computer.
I have had so much trouble over the years of crashing and losing complete projects,that I mix sections down so I have a complete video to stitch together.
This has always worked for me until now.
I just want a reliable version without having to change the way I do things too much.
MXV probably works for what you do but not for me.
I couldn't get a MXV file to play. "Is that Possible"
Thanks.
Doug
 

@DugsBugs

I agree that Magix should fix this wmv problem, if we and they can consistently show that there is a problem.

The mxv file only works in a Magix program (MEP, VPX, PhotoStory, MusicMaker, Samplitude); you can't run it with anything outside of the program. As I said, use it as the intermediate, not the final product. I mix down parts that get difficult effects on them, like Neat Video, then I import that into the timeline, usually a separate project, in order to keep editing efficiently. I had the misfortune of exporting to DVD a 1h20m project that had a lot of Neat Video effects on it. It took 60 hours and the result was disastrous. I then exported sections to mxv, imported into a project that would be the final one. When I got to the final export, it went very fast, as the effects had already been taken care of by the intermediate.

Magix created the mxv format specifically for this purpose. Although the file size is larger than wmv, it exports faster and works better on the timeline.

I suggest that you make a test. Export 5 or 10 minutes of a project that has a lot of effects. Reimport the mxv into a new movie or project, and you will see that it works the same as a wmv, but probably better.

John CB

@browj2
Thanks for the clarification.
Still wouldn't solve my issue because there are still times when I just want to edit WMV files I have created in the past as well.
For some reason, MP4 files seem to be a bit jittery on playback.
If I can solve this issue then maybe MP4 will work for me. Especially for customers using that horrible Apple.
I will still have a play with mxv.
Doug.
By the way. Has anyone on the forum found a way to stay signed in to the topic.
I tick the box every time to remember me but it does nothing.
 

@DugsBugs

You can use the mxv files the same as mp4 and wmv, just not for the final product. I keep all of my projects, so if I need to edit final result, I would go back to the original project.

Strange that you find mp4 files jittery on playback. I never use wmv, only mp4 for export and distribution. My video tutorials on YT are all mp4, as are my other exports to Vimeo and on-line album. I also use mp4 files uploaded to YT in some websites. The videos are unlisted, so the link is in the website. I haven't noticed any problems with playback.

When you see a jittery playback of an mp4 file, what are you using to play it back? Are you going through the internet, like YT, FB or Vimeo?

Staying logged in is a problem. We keep raising it with Magix but nothing gets done. Most annoying!

John CB

@browj2
Generally play with Windows Media Player or VLC for some files.
Playback on FB or YT is usually fine but when I turn a MP4 file into a DVD, that's where I notice a problem as well.
I am only using these double handling methods because VPX has been so unstable over the years.
There needs to be less attention put on useless functions no one uses and just get all the bugs fixed.
Every time they release another version, they stuff something else.
The mxv file seems to be very stable when working on the object so I may try this on a larger scale thanks.
Doug

@browj2

Re your post about the icons, I just noticed that there is a dropdown menu to change the size of the icons from very small, to small, normal and big. Did you try this?

Yes. I tried, however, for me these new buttons are too big. Fortunately, it goes live with it though it used to be better :)

@DugsBugs

What are you using to burn DVD's?

I use the one that comes with VPX, first (DVD or BD) encoding to a folder, checking the files, and then burning a DVD using Magix speed burn'r. To speed up encoding, if my project contains a lot of effects, I'll export to mxv, import to a new project, create the chapters and DVD menu, then encode. It's very fast. I would never use mp4 or wmv as the intermediate.

I think that we have gotten way off-topic here.

John CB

@browj2
I use much the same process as you except for the mxv which I am about to try. Thanks for the tip.
I tested a mxv with a raw camera file and it was much faster than wmv and once imported into a project , it was much more stable. My main trouble is when I try to drag the end of an object, it is very slow and not a smooth action.This sometimes causes a freeze but it seems to be good with mxv.
I guess it goes back to double handling and converting all footage first like other programs need to.
wmv works fine for me for dvd. I never burn with speed burn. usually Nero. Just easier when I need to go back and burn another copy. The choppy MP4 in dvd has nothing to do with the burn process. It's in the encoding process.
I never encode the original project to dvd. Like you, I make a new project with the wmv.
Had my first freeze last night with the new patch so all is not good.
We all live in hope.
Doug.

Well,just when I thought the 242 patch had solved most of my problems, back to the freezing and spontaneous shutting down.
I can not believe we are up to version 10 of VPX with endless patches and we are no better off than VPX 6 the pig of all pigs.
@MAGIX_Redaktion
Is there anyone at Magix who can get us out of this nightmare.
This is not a hobby to me and I rely on it to work for my life.
Unfortunately we are forced to do these updates and no way of rolling back.
Everything was going fine until this major update and current patch.
I can not identify when the crashing occurs because it can happen with the most basic of moves and reproducing it is impossible.
I find I am having to change things I have been doing for years just to get through a project. Mixing down a wmv may make it to the end or just stop when it feels like it. If it does make it through, it is almost impossible to re work the wmv in another project. I have never had that problem before.
PLEASE find someone who can end this horror movie so we can all return to enjoy doing what we love doing.
Doug.
 

Hi everybody,

I talked to the developers and they read the posts (including this one) at magix.info. They reproduced some bugs you have mentioned and put them on their ToDoList.

We are really sorry that some of you have trouble with this version! We are working as fast and as hard as we can to prepare everything for a new patch – no target date, yet.

I'll let you know more as soon as I have more information to share.

Hi everybody,

I talked to the developers and they read the posts (including this one) at magix.info. They reproduced some bugs you have mentioned and put them on their ToDoList.

We are really sorry that some of you have trouble with this version! We are working as fast and as hard as we can to prepare everything for a new patch – no target date, yet.

I'll let you know more as soon as I have more information to share.

Thanks! It's cool to hear that the devs are looking at the bugs people are noting here (and not just in support requests) and working towards fixes.

I'm really impressed with the speed that the original patch came out and can't wait to see the next update/patch.

I've been playing around with Vegas 15 Pro too recently, and I still slightly prefer the VPX interface and feature set (although I really wish the Vegas Pro OFX integration could be ported across to VPX so it would work with FXHome Ignite as I'd love some FXHome compositing tools available above the basics included in the VPX install).

All in all, good job so far Magix team - just keep plugging away at the bugs :-).