[Oki Pienandoro]

If you use 2 track (and one is act as matte), then use Track Matte Key
Image Matte was used if you want to matte the footage directly into the footage (there is an option to load the image matte)

——————————————
Sorry for the english, not native speaker.

[Oki Pienandoro]

Follow up for my previous reply.
If you’re not convenient to share the files publicly, perhaps we can use this workaround.

Download the image template below that i made for you, it’s a frame template ranging from 4K through 720.
10169_frametemplate.png.zip

Now make a new sequence based on that frame, which mean you will have a 4K sequence.

Now drop the problematic file on top of that image.
Make sure the frame is on 4K sequence don’t resize the files, or your footage.

Post your result (screen cap the program panel).
This way we can actually see the border (including the “fake” black border) if there’s any, in that problematic files.

This is the only way i can think of, to detect your frame border without you sharing the file itself.

——————————————
Sorry for the english, not native speaker.

[Oki Pienandoro]

Maybe because it’s a fake 1920×1080. The image is 1280×720 but the camera export them (with black bar) as compensation to 1920×1080.
We can’t know for sure unless you share the problematic file..

——————————————
Sorry for the english, not native speaker.

[Oki Pienandoro]

From the looks of it, looks like you rotate the image 270 degree, is that correct ?
You didn’t give us info what the original source files frame size (before you rotate to landscape).

So i’m assuming the source files doesn’t conform with 16:9 ratio or 9:16 ratio when you record it on portrait mode.
No matter what you do it will still have the black bar since it doesn’t conform with that ratio.
So you either need to enlarge/shrink the video manually using effects tabs (Don’t use “Scale Frame to Frame Size),
which means a portion of your image will be lost due cropping.

Are you really sure the black bar still exits, even after you enlarge/shrink the video?
Because there’s a chance your VLC didn’t properly show the video (let say, you inadvertently set the VLC to render a 50% frame size).
In other word, the black bar is not exist, but because VLC wrongly configured it scaled down the video, so it may look like you still have a black bar.

The only way to test this is to re-import the output to premiere again.

——————————————
Sorry for the english, not native speaker.

[Oki Pienandoro]

First of all, don’t panic, there always a workaround (somehow). Believe me, many editor (including me) been through even worse.

Let’s start from the very beginning,
The start screen. It could be the “Preferences | General | At Start Up” was somehow not set into “Show Start Screen”
So it may/may not related to the problem you have.

2nd, when you said you reinstalled Adobe, did you use Adobe Cleaner, and delete any preferences. Also, did it import your preferences from cloud ?

I don’t quite get it how the “re-image” (restore image ???) from PC has anything to do with Mac.
Also, if you restore image from a broken installation, it’s pointless. Better start from scratch (manual clean install).

How many days left to deadline ?
You never mentioned your footage container and codec, sequence, and did you use any 3rd party plugin ?
Any dynamic link ?

What kind of edit ? Multicam ?

Have you tried to delete the cache and the database ?

If i were you, seeing the problem still arise even after changing platform, i would do :
1. Transcode to format you trust (ProRes, DNxHD, Cineform), and don’t mixed it, and make sure the audio is also conformed, so Premiere didn’t have to reconformed.
2. If it still fails, i will switch back to Win 7, CC 2014.
Which mean you need to export/import your sequence in XML, since most likely Premiere CC 2014 can’t open CC2015 project files.

Honestly i just installed CC2015 last week (just for the sake of learning new feature), because i’ve seen so many report about bug on initial release..
I’m still using CC 2014 on Win 7 for my work.

——————————————
Sorry for the english, not native speaker.

[Oki Pienandoro]

Yeah, you can’t do that in AME, however, in AE, it will generate subfolder for each comp/footage if you encode to image sequence.
You didn’t need to put them in comp, just load the footage into project then add them into render Queue (Ctrl+Shift+/) AE will generate the comp automatically.

——————————————
Sorry for the english, not native speaker.

[Oki Pienandoro]

Your vimeo example is on private/password protected.

——————————————
Sorry for the english, not native speaker.

[Oki Pienandoro]

Currently only manual, but next release will be native feature:
https://blogs.adobe.com/creativecloud/whats-coming-next-in-adobe-premiere-pro-cc-and-media-encoder-cc/

https://www.youtube.com/watch?v=G8a1G1YkNDg

——————————————
Sorry for the english, not native speaker.

Some contents or functionalities here are not available due to your cookie preferences!

This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.

[Oki Pienandoro]

Can you elaborate more ?
I’m interested what the difference.

I’m taking a wild guess here (based on this OP experience):

Is it in “Non database driven” NLE (Premiere), when we opened the timeline, all of the assets in the timeline was load into RAM ?
While in “Database driven” NLE (AVID), the timeline was just a reference ? It only load to RAM when the playhead is on top of the assets ?

——————————————
Sorry for the english, not native speaker.

[Oki Pienandoro]

Since you’re only edit a 1920×1080 H.264 from canon DSLR, and from the tech specs here:
https://support.apple.com/kb/SP703?locale=en_US

Assuming the graphic card were not supported (thus you only edit in Software Mode, not GPU accelerated mode)
Also,i never own Mac or any MacBook Pro (but i do use them if i’m editing with 3rd party)

In personal use/project, i only use PC,
A 10 years old PC if i have to say. And i can edit in realtime on native H.264.
Based on that, since my PC specs is lower than your spec (or anyone really)
It’s safe to say your machine it’s more than enough.

Also, Adobe comes with trial you know, you can use it for 30 days. See if it can hold well.
The only limitation is the output format (i think), since some of them is licensed.

You might as well check your performance by using a benchmark project file here :
https://ppbm7.com/index.php/homepage/instructions

But don’t take this as a real workflow benchmark, this more aiming at GPU performance.

For understanding about GPU advantages, read here :
Yes, it was webpage with an old school layout, but it’s really worth it to read IMO.
https://www.studio1productions.com/Articles/Premiere-Benchmark.htm

In conclusion, if your workflow never or rarely use a GPU accelerated effects etc, you will not get advantages at all by upgrading your machine/graphic card.

See the result here :
(look for GPU VS Software only)
https://ppbm7.com/index.php/results/mpe-performance

But it only applies IF your workflow depend on GPU assisted feature (they use a heavily GPU project files in this benchmark)

——————————————
Sorry for the english, not native speaker.