What you describe is not happening here with the examples you provided.

May be a local player issue.

I'm seeing the issue in the 1080p stream in Firefox and Chrome. It's worse on the first video.

Do you see the problem when you put your rendered file back on the Vegas timeline, or only on YouTube?

You could try the Sony AVC/MVC encoder instead of the MainConcept encoder. You won't need much bit rate as it's a still image.

p.s. Go easy on the sharpening ;) ...that shouldn't cause this issue though.

What you describe is not happening here with the examples you provided.

May be a local player issue.

Check the video out in 720p or even lower, and use a screen with good quality, and you should see it pretty easily.
Happens in 1080p too, but it is even more noticeable in lower quality

 

I'm seeing the issue in the 1080p stream in Firefox and Chrome. It's worse on the first video.

Do you see the problem when you put your rendered file back on the Vegas timeline, or only on YouTube?

You could try the Sony AVC/MVC encoder instead of the MainConcept encoder. You won't need much bit rate as it's a still image.

p.s. Go easy on the sharpening ;) ...that shouldn't cause this issue though.

I cannot see the problem while rendering, only on the output file. This is both on YouTube, and the local file, although it is much easier to see on YouTube. Probably caused by the lack quality in comparison. About the sharpening, do you think 0.5 is too much? I use 0.5 on pictures, and 0.6 on the text. I would appreciate your opinion, as I am fairly new to video editing.

And yeah, I have tried both MainConcept and Sony AVC/MVC. It is not a computer issue, as it happens both on my computer and my brothers, which are fairly good CPU's. It has to be something I am doing wrong. And it seems to always happen rendering still images, and it is more noticeable when using transparent logos, as the one I am using in my videos, if that gives you a lead.

Best!

Also, I recently changed logos, which seems to have tuned down the problem.

My best video in terms of the issue. Almost not visible. If you cannot see it, look at the dirt in 720p

Easier to notice here, though it is much better than before.

I was looking at my old YT videos on different channels, and all of my footage rendering photos had the problem, whereas my video footage seems to work better. Also, does my video look shittier than normal in 720p? I feel like 720p should display better quality then I am getting.

Thanks for helping out!

I haven't been able to see "it" on Internet Explorer 11 or the iPad using Safari (both are held at 720p for youtube).

Edit:

I was able to see "it" using Chrome at 1080p.

Offering YouTube as evidence of an issue is ridiculous. YT is a black box, simply put.

YouTube must be removed from the equation because nobody here has any control over it

Upload, to a FILESHARE, an original file from your editor that shows "the problem," along with the ridiculously important MediaInfo properties for both source and render.

Then, others here can determine if the problem is indeed, a result of your Vegas workflow, or not. It's not that hard to arrive at definitive answers here, once extraneous influences have been ruled out.

About the sharpening, do you think 0.5 is too much? I use 0.5 on pictures, and 0.6 on the text...

At 1080p the image is over-sharpened for my taste.

But this leads on to a serious issue... In VP13 the amount of sharpening is affected by whether "GPU acceleration of video processing" (in Preferences > Video) is on or off (discussed here). GPU acceleration can do all sorts of other strange things and I wouldn't be surprised if it was also responsible for this "pulsing blur" problem. So try turning it off.

If that doesn't help then the best thing you could do would be to zip up these:

1. The project .veg file for the "Old Guitar" video that displays the problem
2. The still image
3. The logo(s)
4. Your rendered AVC file
    

Upload those to a fileshare service like Google Drive, Dropbox, wetransfer, mega.nz etc.. We don't need the music.

Also post screen grabs of your project settings and render settings windows.

https://www.dropbox.com/sh/yfp5h45k6q08ew9/AACFssjBgwhWk4RNJ80z3qwSa?dl=0

It happened with GPU acceleration turned off as well. Everything asked for should be included, if not just tell me. Oh, and the Old Guitar .veg file was not saved, but I made a reconstruction. Similar to the original file, just removed the music. It is edited in the exact same way.

The specs file is taken from the same project, just with another audio file, hence why it is 3m50. Both renders suffer the same problem.

Again, thanks for helping!

Download and review this file. (EDIT: Link removed to make use of dropbox.com resources.) If you're satisfied that it doesn't have the problem, I'll tell you how I did it.

When I play them in Vegas or VLC I'm not seeing the issue in your 2 AVC files nor in the 44.6MB 1080 MP4 file I download from YouTube (using YouTubeByClick), which suggests it's a problem with local playback of the YouTube file in the browser with the HTML5 player or Flash Player.

Not sure why this would be happening to your particular videos, as YouTube re-encodes everything. Perhaps the issue is more widespread but only apparent on videos with a still image. It might be related to the graphics card.

I can still see it in my local file. If you look closely, the pixels seems to change rapidly.in certain spots in the photo. Obviously if the video looked like that though, it would not really be a problem for me. I think the issue is prevalent in all my renders, but YouTube makes the quality drop, which makes the issue more visible. Hence why it is easier to spot in 720p and lower, and harder in 1080p. Just speculation, obviously.

Download and review this file. If you're satisfied that it doesn't have the problem, I'll tell you how I did it.

Still there. If you look at my blacks, which seems at least in this picture to be the easiest way to spot it, you can spot it. It seems like the picture has constantly moving pixels, which should not be the case for a still image. Thanks for helping out, though!

Not sure why this would be happening to your particular videos, as YouTube re-encodes everything. Perhaps the issue is more widespread but only apparent on videos with a still image. It might be related to the graphics card.

Yeah, it looks horrible on YouTube in comparison. Still images is pretty much what you use when uploading music to YouTube. When I look at the content of smaller channels, or channels my size, a lot of them struggle with the same thing. However, the big channels seem to have figured it out, as I cannot see the problem displayed on their videos. It might be a thing that a lot of people get with stills, but usually it is hard to notice if you are not aware of it. Most videos are not like the "Old Guitar" one, which is definitely my worst.

These files are all visually static for me when they play. What are your computer specs, in particular graphics card and driver and which browser and version?

AMD Radeon R9 200. There should not be anything wrong with my specs, i think. It might be my screen, but it happens with other screens as well, even my TV. With that said, it is really hard to see the movement. Or who knows? It might just be me playing mindgames on myself.

https://gyazo.com/92306782f547fac8451608039dfc2d4d

The area where it is most visible to my eyes. If you cannot see it, it might just be me.

One clarification. All the stills uploaded that I have seen more or less struggles with the issue. So yeah, it seems to be a widespread YouTube issue. It is just that some images struggles more with it than others, particularly images with a lot of blacks, and some blues. So I guess there might not be a solution when it comes to uploading. I just have to try to pick better images, I suppose.

These files are all visually static for me when they play. What are your computer specs, in particular graphics card and driver and which browser and version?

I also looked at John's file and see no pixel movement.

You could try rendering to an intraframe codec such as XAVC-I instead of long-GOP and see what the result looks like. File size will be bigger. I'm not sure if YouTube accepts it, but it probably does.

Also, if you're not sure what your eyes are seeing, use the video scopes to help you. I can see the pixels on the scopes moving when the I can't see the video image moving. Be sure preview quality is set to Best (full).

"I can see the pixels on the scopes moving when the I can't see the video image moving. Be sure preview quality is set to Best (full)."

[Techno-Philosophical Observation]

Anything less rigorous than All-Intra will show... I'll coin a new phrase... "scope squirm".

My project rendered uncompressed shows absolutely static scopes with a file size of 11.3 GB.

My project rendered using Quicktime to MJPEG A shows absolutely static scopes with a file size of 2.65 GB.

You can see it on YouTube here: (EDIT: Link removed to make better use of YouTube.com resources. I know they're free to me but society pays for all economic activity one way or another.)

My project rendered to XAVC-Intra shows static scopes to my eyes with a file size of 877 MB.

My project rendered to .mp4 shows a virtual waterfall of "scope squirm" at ~ 115 MB, even though James-Olick and I can't see the resultant artifacts when viewing full screen. In my case that's no great recommendation as I can't see anything, anyway.

My knee-jerk response to this situation:

It's asking a lot of a long group of pictures encoder to run through a complex algorithm hundreds of times, throw away 99.999% of the data and still represent the original with 100% accuracy and repeatability. After all, the MPEG and latter-day derivative encoders were developed for motion pictures.  

[/Techno-Philosophical Observation]

[Purely Philosophical Observation]

How many of the people listening to the music stare at the same picture on their mobile phone screens long enough to see the pixels crawl? 

[/Purely Philosophical Observation]

I plan to move this issue to my FFIWT file.

[Supplementary information with no real point]

The type of "pulsing blur" that I saw on the Old Guitar YouTube 1080 video would cause a major shift on the scopes, not just "scope squirm", if it also happened during playback in Vegas.

[/Supplementary information with no real point]

 

[Purely Philosophical Observation]

How many of the people listening to the music stare at the same picture on their mobile phone screens long enough to see the pixels crawl? 

Very few, which is probably the reason why no one has pointed it out.

I have also talked to the guys over at Creative COW to solve the issue, and they managed to identify it.

https://en.wikipedia.org/wiki/Compression_artifact

The picture with typing on it showcasing it perfectly. These project settings also helped with my last YT upload, and changing the file from .jpeg to .png, rendering progressive and deblock filter is also supposed to help. I have not tried it yet, as I do not have access to my computer today.

.
I might try changing the filetype, but I am satisfied with my newest uploads using MainConsept, hoping that the untested changes mentioned above will make it close to non-existant. If anyone is interested, I can link the CC thread.

https://forums.creativecow.net/thread/24/1018064

It seems to me that the posters there are dealing with general compression artifacts such a pixellation and not this specific, rhythmical blurring/pixellation that I see in the Old Guitar video.

Changing from jpeg to png shouldn't make a difference to that temporal issue. Once Vegas has decoded the image it's effectively in memory as a static uncompressed image.

Project render settings should always have been progressive, since interlacing isn't involved in the input or the output. Still shouldn't cause the issue though, even if you had an interlaced setting.

It seems to me that the posters there are dealing with general compression artifacts such a pixellation and not this specific, rhythmical blurring/pixellation that I see in the Old Guitar video.

Changing from jpeg to png shouldn't make a difference to that temporal issue. Once Vegas has decoded the image it's effectively in memory as a static bitmap image.

Project render settings should always have been progressive, since interlacing isn't involved in the input or the output. Still shouldn't cause the issue though, even if you had an interlaced setting.

Have a look at my newest post:

 

Is this more like the issue you see other posters deal with, or do think my issue differs? Old guitar might just be an extreme case of it. It is definitely the most prominent case I have had when uploading.

No issue with this one on YouTube in Firefox 53.0.3 at 1080 or 720. It looks fine. I think the HTML5 player is being used rather than Flash Player.

Just a slight pixel change at 0:11. Looks like sharpening kicked in at that time, then solid and no shifting.