Here are the changes/improvements:

Changes in version 15.0.5.195:

• NEW: Image border effects
• NEW: Start dialog with new design (easier to understand and use)
• NEW: 360° effects categories (now contains all 360° effects)
• NEW: 360° scene rotation
• NEW: Automatic recognition for 360° material and switching (Ricoh Theta m15, S, SC, Samsung Gear 360 and 360° files exported with programs)
• NEW: Automatic stitching for some camera models (Ricoh Theta, Samsung Gear)
• NEW: Track enhancements (track header, insert new track)
• NEW: 5K/6K support for Lumix GH5 (movie settings)
• Improved algorithms for rotate, zoom and 3D distortion (CPU performance improvements, deep color enabled, fixed artifacts)
• Simplified selection of an object’s background (selection of background color moved from the Title Editor to the “Background design” title context menu)
• GPU acceleration for Open FX effects (e.g. all HitFilm effects)
• Virtually all effects can now be used in full screen mode
• Fixed many crashes that occurred when using the program or upon program end
• Fixed error which prevented export to network drives
• Fixed various errors in Effects section (shot match, contour, lookup tables, titles

First comments:

1. Startup screen - presumably made for those with a touch-screen
2. Left track header - "+" button added to insert track above
3. New icons for effects
4. For me, Video mode - Standard mode now works again, the video clips are no longer black
5. New Image Border Effects are under Effects, Design elements. Not obvious what they do. There is a folder called "Cover." Selecting this messes up the menu list and it is difficult to get it back to normal. I used Alt+Shift+H to restore it.
6. NB OFX (Essential 3 and 4) - not fixed, still turn the image black
7. Still no "Share" command in top menu

John CB

I was so hoping my overlay problem would be fixed in this however it is all the same for me.

Support are working on it but so far no answers.

Really strange because the previous updates work until 15.0.4.176.

Seems like one would only need to see what changes were made in that update that would effect the Chromakey or overlay process.

Anyway I do like the new Welcome and open file screen and I'm sure others things will be better.

Just noticed that when I play anything on the timeline, it will play for 3 secs then stop while the play button is still pressed.

When I touch the stop button then play again, it will go another 3 secs and so on.

Not sure if this is just me or not. But it is since the new patch.

EDIT: Closed it down, re-opened and that 3 sec stop had gone. :-) All good except my Overlay prob.

I'm really not game to do this update.
Am I going to turn a pig into a bigger pig?.
I have never had so many issues with VPX as I have with this one.

I find I am having to mix the edit down to a WMV or MP4 to then create a DVD because there are so many issues with the DVD function.
My main hope is they will fix the crashing issues that have been around since VPX began.
Fix the problems before bringing out new functions.
 

I'm really not game to do this update.
Am I going to turn a pig into a bigger pig?.
I have never had so many issues with VPX as I have with this one.

I find I am having to mix the edit down to a WMV or MP4 to then create a DVD because there are so many issues with the DVD function.
My main hope is they will fix the crashing issues that have been around since VPX began.
Fix the problems before bringing out new functions.
 

 

Hi

Compressing to WMV or MP4 and later creating VPX DVD will not hurt you. U me on the laptop is the same problem and on the computer this problem does not exist. So I had version 15.0.4.176 and so I have version 15.0.5.195. The laptop has Win10 Pro and the Win7 Pro computer. Some time ago I had a problem with the Timeline sound, the difference came to 11 second, and I do not know how and why it was repaired.
Greetings Tomek

Kompresja do WMV lub MP4 i później tworzenie VPX DVD  nic ci nie da.U mnie na laptopie jest ten sam problem a na komputerze ten problem nie istnieje.Tak miałem w wersji 15.0.4.176 i tak mam w wersji 15.0.5.195. Laptop ma Win10 Pro, a komputer Win7 Pro.Jakiś czas temu miałem problem z dźwiękiem na Timeline,różnica dochodziła do 11 second,a nie wiem jak i dlaczego sam się naprawił.
Pozdrawiam Tomek

I find mixing down direct to DVD, all the fades go stupid and I am getting error messages. That's why I do WMV first.
It's a double process but the result works.

I find mixing down direct to DVD, all the fades go stupid and I am getting error messages. That's why I do WMV first.
It's a double process but the result works.

Hi DB,

Sounds like an odd problem. I sometimes write direct to dvd from the timeline without any problems, but if a project has a lot of effects I will frequently create one or more mp4s which seem to be quicker to render than dvd files. I then take the mp4s into a new project and render a dvd from that. Dvds from mp4s are very much quicker than dvds direct from the original timeline, but I don't have a problem with either in VPX7 or VPX.

What do you mean by 'all the fades go stupid' and what error messages do you get?

Roger

Hi,

I use Magix mxv format as an intermediate format when I have a lot of effects, especially Neat Video. Then I create a copy of the project, select and delete all and import the mxv file. This is the same as doing a mixdown which is documented in the manual. Magix advises that this be done if your computer start to reach its limits. If I have created chapter markers, they will still be there. I can then easily review the file from within VPX. If problems, I go back, make corrections and redo the mixdown.

Then when I create the DVD or BD, the process goes very fast. I encode to disk and then use speed BurnR to create the disk.

The only thing about the mixdown, is that if I have a long movie, I export to mxv in sections, check each when it is done, otherwise it can take a long time to find out that something was wrong.

John CB

Further to my first post above, I found an interesting "fix" of VPX on my Surface Pro 4. VPX with patch 176 gave me a 0 days remaining under About, but continued working. I put this in a ticket. When I had this problem before, I had to uninstall VPX and the patch using a Microsoft special uninstall program and then re-install; Magix told me to use the same procedure. Since VPX was still working, I left it alone. However, with this new patch, I simply tried installing the it and it worked, but not only that, it re-instated my serial number on the About screen. That was a simple fix.

John CB

Further to my first post above, I found an interesting "fix" of VPX on my Surface Pro 4. VPX with patch 176 gave me a 0 days remaining under About, but continued working. I put this in a ticket. When I had this problem before, I had to uninstall VPX and the patch using a Microsoft special uninstall program and then re-install; Magix told me to use the same procedure. Since VPX was still working, I left it alone. However, with this new patch, I simply tried installing the it and it worked, but not only that, it re-instated my serial number on the About screen. That was a simple fix.

John CB

Hey
I had the same after installing VPX on a long device where I had 0 days instead of serial number and I remembered your problem and so it was until yesterday. After installing patch 15.0.5.195 everything went back to normal.
I have the impression that you need to change the device once every 30 days in case of a problem because then the VPX connects to the server Magix to correct the serial number.
Hello Tomek

Cześć
Miałem to samo po zainstalowaniu VPX na dugim urządzeniu gdzie zostało mi 0 dni zamiast nr.seryjnego i przypomniałem sobie o twoim problemie i tak zostało do wczoraj .Po instalacji patch'a 15.0.5.195 wszystko wróciło do normy.
Mam wrażenie że trzeba zmieniać urządzenie raz na 30 dni w razie problemu bo wtedy VPX łączy się z serverem Magix w celu poprawności nr.seryjnego.
Cześć Tomek

Hi,

I use Magix mxv format as an intermediate format when I have a lot of effects, especially Neat Video. Then I create a copy of the project, select and delete all and import the mxv file. This is the same as doing a mixdown which is documented in the manual. Magix advises that this be done if your computer start to reach its limits. If I have created chapter markers, they will still be there. I can then easily review the file from within VPX. If problems, I go back, make corrections and redo the mixdown.

Then when I create the DVD or BD, the process goes very fast. I encode to disk and then use speed BurnR to create the disk.

The only thing about the mixdown, is that if I have a long movie, I export to mxv in sections, check each when it is done, otherwise it can take a long time to find out that something was wrong.

John CB

Hi John,

It sounds like we work virtually the came way except I mix down to MP4. In that way, I can save each MP4 section as a seperate file on USB for my wedding clients so that they can view in HD quality rather than the SD quality of a DVD.

Roger

Had another problem today that I haven't seen before.

I had been editing a wedding for a few hours and saving regularly, then whilst checking the previous few minutes of editing, I noticed that two of the clips seemed to be still images rather than 7 second moving images. I also found that two moving clips with different clip numbers were also showing as stills, but were both showing the same still even though they were different clips. As I actually had no stills from these clips, I decided to save the project and shut down the PC. The moment it had saved, the programme disappeared without warning and a message appeared saying that Magix was restarting. It restarted with a new project screen with no attempt to automatically recover or reopen the project I had been working on. I then looked at the backups of the project and found that the previous auto save had been 45 minutes before the crash. That in itself is odd as it is set to auto save every 10 minutes in case I forget.

I shut the computer down and rebooted, loading the project I had saved immediately before it had crashed. It now ran normally and fortunately I had lost nothing. Very odd and something I have not experienced before.

Roger

@RogerGunkel
I have always found the opposite .
DVD from the timeline has always been quicker for me.
As mentioned by John CB, Effects such as neat video slow the process down a lot and make preview impossible.
Since I often give my clients a USB copy, then I need to do the WMV anyway
My original question is still whether to update or not if my problems haven't been fixed in this update but end up with other problems.
Doug

Hi Doug,

I used to find it quicker to write to DVD than MP4, but since ditching my graphics card and using the Intel i7 graphics, the reverse has been true.

Might be a bit early to see what problems may be in the new update, but hopefully folks will report them.

Roger

@RogerGunkel
I agree Roger.
I am putting up with what I have at the moment and changing some of my practices.
I lust want to get to the stage where it doesn't freeze or crash.
I have i7 with 16gig ram and 2.9gig processor well above what Magix recommend.
Lets hope they can produce a reliable product soon.
Doug.

Well I was forced to do the update because every time I tried to open a project, it just sat there doing nothing with an empty project. I would then have to go to file and open project to get it to open.
This only started happening today.
"Way to go Magix".
Anyway, everything seems to be working fine so far and DVD direct from timeline seems to be working ok.
I don't like that there is no box to tick to "not show" the start dialogue box every time I start a project.
Obviously, if I am opening Magix a new project, then I am starting a new project. I don't need to be asked every time what I want to do. Just a minor complaint.
It all updated fine and I still have the serial showing.
Give it a go.
Doug

 

I've just tried to write a 1hr 57min dvd, something I have done many times over the years, however with VPX after the new update I am getting the same problem that I had before the update. The programme should resize the file to fit the dvd when selected, however it just gives an error message when prior to writing the dvd to say that the file won't fit on the dvd and I should shorten the programme.When I go into the advanced menu and click on the adapt bit rate button, it tells me that the file will fit. This must be a bug as I never had this problem with VPX7

Roger

@1940

Just noticed that when I play anything on the timeline, it will play for 3 secs then stop while the play button is still pressed.

When I touch the stop button then play again, it will go another 3 secs and so on.

Not sure if this is just me or not. But it is since the new patch.

I thought it was just me as well but it has been doing this since the early patches - very annoying and IIRC someone else reported the same behaviour a few months back. With me it is more like 10 secs before it stops.

Peter

@RogerGunkel

I used to find it quicker to write to DVD than MP4, but since ditching my graphics card and using the Intel i7 graphics, the reverse has been true.

This would make sense because the Intel Quicksync block in the iGPU is optimised for HW encoding/decoding of the H264 (MP4) codec.

BTW I see the latest Win 10 1709 version has added some graphs in Task manager that show several real time parameters of GPU performance - a bit like the GPU-Z utility. It shows info about my Intel GPU and my discreet Nvidia GPU.

Peter

@RogerGunkel

Hi

. . . . I've just tried to write a 1hr 57min dvd, something I have done many times over the years, however with VPX after the new update I am getting the same problem that I had before the update. The programme should resize the file to fit the dvd when selected, however it just gives an error message when prior to writing the dvd to say that the file won't fit on the dvd and I should shorten the programme. . . . .

Just completed a 1h 59min movie writing to DVD-RW, space required 5769MB / 4489 MB, auto adjusted ie clicked Adjust, to fit to disc and burned OK - file size on disc 4.17GB with VPX version 15.0.5.195

The Encoder settings, Adapt bitrate button, also functions correctly reducing the bitrate from 6224 down to 4843

In the Burn dialog, what does the space indicator show the disc space required before you click the Adjust button?

John EB

@RogerGunkel

Hi

. . . . I've just tried to write a 1hr 57min dvd, something I have done many times over the years, however with VPX after the new update I am getting the same problem that I had before the update. The programme should resize the file to fit the dvd when selected, however it just gives an error message when prior to writing the dvd to say that the file won't fit on the dvd and I should shorten the programme. . . . .

Just completed a 1h 59min movie writing to DVD-RW, space required 5769MB / 4489 MB, auto adjusted ie clicked Adjust, to fit to disc and burned OK - file size on disc 4.17GB with VPX version 15.0.5.195

The Encoder settings, Adapt bitrate button, also functions correctly reducing the bitrate from 6224 down to 4843

In the Burn dialog, what does the space indicator show the disc space required before you click the Adjust button?

John EB

In the burn dialog it shows me similar to your figures above about 5.4Gb, then asking me if I want to split or make it fit (or words to that effect) I select fit and it goes into the usual steps until just prior to writing the dvd, when the error message appears. If I go into the Encoder settings and select the adapt bitrate button, it tells me that the file is correct for the dvd. When I looked at the files produced in the dvd image file I found that the folder size was 8.2Gb ?? That was obviously why it wouldn't write the dvd. A short while ago I compared it with a dvd of shorter length that had written fine and found that in the failed folder there were 4 identical files showing the menu picture all of 29 minutes each, whereas the same file for the shorter dvd showed a length of 0 mins. Both menus had the the 'Still from the video' option in the menu editing screen, however, the failed one had written the file 4 times at 29 minutes each. I tried changing the menu background option to 10 seconds of moving image from a clip and this time the write was successful.

As I have used both still and moving images from the video files as backgrounds many times, I can't see any reason why I am now getting this problem on longer menus in VPX. It could be that there is a problem with the particular menu that I use for weddings in VPX compared with the same menu in VPX7

Roger

I have found most of my error messages while encoding have had something to do with the menus or chapter markers.
Don't ask me why.
That's why I have changed to mixing down to wmv then starting a new project just for the DVD.
Seems to work. It is double time but I usually do a wmv for better quality anyway. DVD is rubbish quality.
Doug