Quote
PepsiMan has a point that this is getting complicated again. Even though I also went to (only) public schools, I'm just trying to see this thing through
2bskyhi, one thing I can't tell from your screen captures is whether or not those black bars are permanently present, or are simply the result of playing a 2.4:1 video on a 16:9 monitor. The way to tell is to take the player out of full screen mode and drag one of the corners towards the middle.
If you're doing that with either of my finished clips, you should be able to get the window frame in contact with all 4 edges of the media, just like my earlier screenshot showed.
If you try to do that with the clip you've produced in PD16, you'll see that the upper and lower black bars are always present, and will even force black bars along the left and right edges if you squeeze the vertical dimension too far. That's because PD always produces to the project's fixed aspect ratio setting, even when the pixel sizes in the producing profile do not match that.
If PD could produce a 500x25 or 5184x2160 strip of video directly, we wouldn't need to use VDub2 for a post pass.
However, you'll notice that the Intermediate profile I created is 5184x2900, which is both axes desqueezed into a 16:9 frame. Since the profile's horizontal size exactly matches the clip size, PD creates the empty, black bars along the top and bottom to fill in the missing areas.
In order to remove the black bars, we need to run the clip through the post pass in VDub2 to actually crop the unwanted 370 lines of pixels above and below the clip so we end up with a video that's truly 5184x2160 (instead of what PD gave us, which is 5184x2160 content inside a 5184x2900 video frame).
Does this whole process make more sense now? I hope so, and I'll post the updated steps in the next post for clarity
2bskyhi, one thing I can't tell from your screen captures is whether or not those black bars are permanently present, or are simply the result of playing a 2.4:1 video on a 16:9 monitor. The way to tell is to take the player out of full screen mode and drag one of the corners towards the middle.
If you're doing that with either of my finished clips, you should be able to get the window frame in contact with all 4 edges of the media, just like my earlier screenshot showed.
If you try to do that with the clip you've produced in PD16, you'll see that the upper and lower black bars are always present, and will even force black bars along the left and right edges if you squeeze the vertical dimension too far. That's because PD always produces to the project's fixed aspect ratio setting, even when the pixel sizes in the producing profile do not match that.
If PD could produce a 500x25 or 5184x2160 strip of video directly, we wouldn't need to use VDub2 for a post pass.
However, you'll notice that the Intermediate profile I created is 5184x2900, which is both axes desqueezed into a 16:9 frame. Since the profile's horizontal size exactly matches the clip size, PD creates the empty, black bars along the top and bottom to fill in the missing areas.
In order to remove the black bars, we need to run the clip through the post pass in VDub2 to actually crop the unwanted 370 lines of pixels above and below the clip so we end up with a video that's truly 5184x2160 (instead of what PD gave us, which is 5184x2160 content inside a 5184x2900 video frame).
Does this whole process make more sense now? I hope so, and I'll post the updated steps in the next post for clarity
Thank you both so much AGAIN.
So regarding Optodata's first question re. format & Tomasc's expanded description to check it, I suspect this format issue is likely as good as it needs to be--all I hoped for.... Following Tomasc's instructions with the same "DroneX" video he used to test, I am able to eliminate all black bars in VLC, WMP & WIN Movies & TV, but I never ran it thru the post project in VDub2. Anyway, that clip is NOT the "Final" one that I produced with Optodat's last instructions. That clip is here: https://my.pcloud.com/publink/show?code=XZlk3MkZC7xwC3WiYvmOdbVaHRXBebmDtT67
So for one more func check, I decided to load the last 3 versions of my test videos(DroneX, DroneY, and Final) into my Galaxy S8. (I know I feel your eyes rolling now--justifiably so). But what I found was, that the only clip that played without stuttering, was the "Final" version. Since cell phones are a likely share platform for my productions, I think I'll quit while I'm ahead & before you all get sick of me...
I just shot a new test video & ran it thru Optodata's LATEST instructions including the post in VDub2 and it worked perfect for all 3 players & on my phone!!!!!!!!!!!!
So I can finally give you all a break. Tomasc, PepsiMan(Happy Happy, Joy Joy) & Optodata you're all rock stars. I can get pretty OCD & persistent when I need to learn something, but I don't often find other's who are so willing to tolerate this many rookie questions about such technical minutia...
THANK YOU ALL AGAIN! 2bskyhi
Well, it figures... I spoke too soon... I discovered that the Custom profile I used for step 4 of your latest instructions, was in fact the first one you sent me--with the 4096x2160 default res that is just above the 5184x2900 Intermediate.ini you sent me. When I try to use the correct profile w/ 5184x2900, I get this error in PD: https://my.pcloud.com/publink/show?code=XZJrGMkZE35IQrhP6KpsNBSYR6jdoRuvGwp7
When I examined the .ini file, I noticed several differences, but I don't know how to enterpet them....
I'll understand if you want to surrender...
Thank You, 2bskyhi
This message was edited 2 times. Last update was at Mar 29. 2020 17:49