flicker in late-2018 rendered projects

[lata]

The program does not like up scaling the 720 x 576 to 1920 x 1080 when converting Mpeg2 to MP4
I would think 10% is the first video clip on your project

Try choosing the MP4 setting 720 x 480 which is a similar frame size to the project.

[Davidk]

Hi Trevor,
Thanks for that. But there has to be more to it than "the 1st video clip", and I suspect that it's related to no of clips and vsp duration - and thus probably involves a memory issue. Reasoning as follows:
- I mentioned the render to mp4 method worked for 2 clips. Those were at the default 1920x1080 resolution for mp4. The 1st was the cooktown vsp - which had 12 video clips, and a duration of 5min30sec. That rendered to MP4 Ok. The second was a project which has 14 video clips in it, and a duration of 4minutes 37sec. That render to mp4 also worked OK.
- The vsp failing to render to mp4 has 35 clips in it, with a duration of 19minutes 55 sec. Render to mp4 failed at 10%, and assuming that is a time related measure, that fail occurred at the 2 minute mark, and 4 video clips done by that time.

I'll try the different resolution size on render and advise what happens.

Update.
Rendering the vsp to mp4, 720x480, 25p, 16:9 worked fine: no errors and no blinks. Re-rendering the result to normal 720x576 mpeg2 also worked fine. 'tis a mystery unsolved but at least worked around. We are getting good at work arounds - come the day when VS doesn't need that - we will all be in shock but less frustrated.

So, now all the elements of my project are blink free, and the disk composition and menu are done. Render to iso tomorrow.

[ZacharyStanley]

The most imperative scrape is that the VS is a video editorial manager not an energy factor, that recommends the substance material need some sort of video ordinary. In Davids video (Cooktown) there is for various minutes nothing what has some video homes.

[weaver]

It was also my opinion from the very beginning of this theme. I never came to the idea to do some video editing without a video content. The today technology can make miracles, but it does not mean that we need to force it into this direction.
I remember fourty years ago we needed a huge box Time Base Corrector just to synchronize two remote video source. Today we can mix together almost any formats of video and pictures, but the basic must be somehow respected, a video editor is designed to edit video contents and not other picture formats.

[lata]

I have been creating slide shows for nearly 20 years using Video Studio with no problems the only content being Jpeg images.
The timelines settings (Project Properties) reflect the video that is to be created, we do not require any video content on the timelines to make our projects.

I have never had this problem that David is experiencing, nor does he have the problem using an earlier version.

Adding a video clip to the beginning of Davids project did not correct the issue for me.
I simply replaced the first clip (the blue clip) with a video file, that made no difference to my project.

I assume David also tried replacing the first clip, although he has not commented on that.

Creating a slide show from scratch using 2018 and 2019 contain Images only has no problems.

Unfortunately we do seem to be experiencing different results, something that testing 2018 and 2019 seems to do,
That makes it difficult to pin down the culprit, very frustrating.

I no longer have 2019 installed till the next / first service patch, for me at the moment 2019 is not fit for purpose.

[weaver]

Hi Trevor

I also did not had similar problem yet, but ( maybe a professional illness. ) I always start every video project with a video file (intro). Today ( especially in VS2018) there are so many possibilities ( video formats) that I am sure most of the users are not even able to select the correct one. It is much easier and safer to place a well working video intro and let VS2018 to configure the final video format ( set as the first clip).

When you just replace the first clip I do not know how VS handles this issue, ( maybe ignores the fact because the rest has already some format). I used a different methode, created a new project, placed my own MPEG2 intro and imported rest from Davids vsp. Of course I have got the expected message to recalculate the preferences for the vsp. It is the same when you reformat your edited video ( F6/ preferences).
I fully agree with you, that we do not have enough information to find the conflict.
I had in the past similar issues with one many camera project ( over 10 different cameras and formats) few clips simple did not work as expected, especially that times from the new DSLR cameras. Every camera delivered a different format and speed. Where did I expect a conflict (60p) those clips were working fine in the 50i environment, while the originally 50i clips from several cameras created the problems. Interestingly in Pinnacle the same clips were working fine.

These are the mysteries of almost all NLE-s.

I did not even installed the VS2019, even the VS2018 fulfills not completely my expectations and accuracy. It is very frustrating when I purchase a new product, has perfect features and options, but the basic accuracy, speed or the GUI is a nightmare. While in VSX7 the splitscreen format ( two monitors) is stable and also the cutting is accurate in VS2018 the custom GUI layout jumps into different settings and also the clips lock not very exactly (I had in my recent project several splitscreen sections with up to 4 clips) and also exact timing issues. I just discovered that the clips does not lock perfectly on the overlay tracks. I very often had to go to the maximum zoom and adjust the clip position in this way. Something similar I never experienced in VS X7.

[lata]

David
I used your original project as a nested VSP which rendered ok with no flickers.
How
1 / Start a new project using the same settings
2 / import your vsp to the library
3 / drag the VSP to the timeline holding Shift will drop as a single clip
4 / render that to same as project

I ran a few tests to render a short section with good results
I am still having issues with the text being out of line, I cannot understand that?

[Davidk]

Summarizing 2 communications with Trevor
1. I said
I tried that with the whole vsp - three times, same result: set the output folder and filename in share, same as project settings ticked, and - render began, got to about 8% and then just . . . blink and dies. No error message, and no apparent residue in the nominated output folder either.
2. Trevor responded with
Yes indeed it does disappear at 8%, i was setting the preview range to test the image flicker up to the lighthouse
8% is further on?

And on a time basis, not much further on. The 8% (of 5min30sec = 26.4 sec) elapsed is the Cook crew memorial plaque, 2 photo images (6sec) later than the lighthouse.

Now, if Corel could just fix these sort of issues with an established product rather than fussing with extra bells and whistles in the new one, we would be happier. Altho, this issue afflicts 2019 too. I've mentioned that in the posts, but maybe no one noticed.

[Davidk]

I've tried this again with 2019HF - and it failed outright: would not render at all. Had to use the manual, render to mp4 720x480 to get any output at all. Then re-render to mpeg2. That double stage procedure is tedious and prone to loss of resolution thru several renderings to get a usable mpg file.