Mercalli acting weird on save

[mikeandm]

Hi,
I am having a problem saving edited clips in Videostudio 2018 both before and after installing SP4.
I have edited a series of clips, using Mercalli on some of them, as usual. I then go to "share" to save it. It takes the expected time to save as if it was rendering using Mercalli, but when I play it I am getting the message that "the video analysis must be executed again."
If I go back from "share" to "edit" and run the clips again they are clear of the message. If I open a clip and reselect Mercalli without changing the settings it just closes again showing that it has already carried out the operation. Hope this makes the problem clear. I should add I have been using the programmes for many years with no problems before.
I have tried this on a couple of different projects and unfortunately I am getting the same result.
Can any one suggest a fix please.
Thanks
Mike

[RobertOZ]

This problem has been raised before, for many versions of VS, search the forum for Mercalli related issues

Updating the graphics card driver has resolved the problem for some users

[lata]

Hi,
I should add I have been using the programmes for many years with no problems before.
Thanks
Mike

Have you changed your editing techniques
Have you added other FX filters or used Speed Timelapse in addition to Mercalli
Changing the Project Properties especially the frame rate may affect Mercalli.
Changing / cutting the clip after applying Mercalli will require a rescan.

[mikeandm]

Hi,
unfortunately I have not changed any editing, all the points you mention I am aware about.
At the moment The one I am trying is to make sure the project properties match on all the clips, the only problem is the video is about 1 hour and I am having to go through each clip and redo the mercalli effect.
The other very strange thing is that I have 2 video's that have this problem, but I have just recorded a third one which worked fine. I do not understand but will not complain.
Thanks

[Ken Berry]

My own theory about Mercalli is that you can avoid that rescan msg if you output the video in progressive/frame based format. I use AVCHD .m2ts quite a bit, but mp4 using the H.264 codec should also work. See my post at viewtopic.php?p=346379#p346379 and the link contained in it.

[Scubbie]

I've found a few issues with Mercalli over time. The tips above do work.

There are a few potential causes I've identified:

1. Using Mercalli to stabilise multiple clips
2. Using Mercalli on the same clip in a different way later
3. Rendering in a different way to your project's properties

The first is really annoying. I'm not sure of the threshold figure, but let's say that you've sorted out 6 clips and you're now on number 7. One of the others will lose its information and you can either get into a loop restabilising them all for eternity or putting them into a separate mini-project and rendering each individual clip to a new video file clip. You can then use that stabilised clip in your project instead of the original.

The second one could be that you have a long clip which you'd like to split and use a few times, stabilising each slightly differently. Once more you'll get a conflict and using the technique mentioned above is perhaps the best way around this. Personally, I'd create two clips, each with the stabilising options I wanted for each clip in the first place.

The third one is a real meany at times. If your project is set to 1080 25p and you render at 1080 30p, for example, then you'll get the error message asking you to analyse the clip once more. You could also get it if you rendered the same project as an AVI file 720 x 576 @25fps.

I've found that the sound settings or compression ration don't influence the results in this instance.

The obvious solution to the rendering issue is to ensure that you chose the right options and match them. If you change the project's properties, then you'll need to reanalyse each clip that Mercalli is used with.

Generally, the only time I see this one myself is when I've set the project properties to 50p and carelessly forget to chose the 50p option when I render a project as the default is 1080 25p. One I spot it, the solution is to correctly render the project once more.

Of course, sometimes it's nice to produce a video in multiple resolution options. The answer there would be to produce one at the highest resolution, check it over for any issues and then to import that onto the timeline and render it out in multiple resolutions. Otherwise, you'll have to change the project properties, then resample each clip prior to producing each video at different resolutions.