[NEED HELP] Adobe Media Encoder not encoding Premiere sequences

[MSTRKKRFT]

Hello!

I'm facing an issue with AME 2019/2020 (everything is fine with AME 2018) : when I queue a sequence from Premiere the encoding just wont start (no error code). (see screenshot here : https://drive.google.com/file/d/1itxWVhDXGAqIvHCSJL_JjdRoevkgk9uT/view?usp=sharing)

I've tried to do that with new project made in PP2020 and with existing projects as well (made in PP2018), same issue.
However, if i directly use a video file to transcode in AME (H264 MOV file) with exact same preset as the Premiere Sequence (H264, VBR8, tried with HW acceleration and with Software only) there is no problem, encoding starts directly.
Tried to export to ProRes as well, same issue with Premiere sequences, no issue with transcoding video file.
Tried with Metal/OpenGL/Software Only : same issue
Also deleting Cache, reseting AME, and every common practice to solve issues in general didn't helped with my problem.

I've managed to export a sequence from Premiere a few times, this is how I did it : 

1- Create new PP2020 project (Test2020.prproj)
2- Imported a H264 1080p (50 fps) footage from my GH4
3- Create a new sequence from this clip
4- Queue the sequence in AME
5- Nothing happens, AME stuck on "Ready" like explained
6- Went to this folder where - I guess - AME creates a temp project file for the export "/var/folders/d2/v4h7x_fn4d7gfdvxz8ychjym0000gn/T/"
7- Opened "Test2020.prproj" from this folder in Premiere
8- Queue the sequence in AME
9- AME encoded the sequence properly, I've tried different format and everything was working

This solution is not working all the time, didn't really find a pattern yet. 

One more information : I just upgraded from High Sierra to Mojave, the problem was there in High Sierra and is still there in Mojave (I did a clean install, no update)

I also realised that in AME 2018 Preferences, in the "Media" tab, the option "Enable hardware accelerated decoding" is grayed out, but in AME2019/AME2020 this option is available, weird right ?

Because everything is working with AME2018 and not AME2019/2020 maybe it's a permission issue ? I mean Adobe made some changes in the software which my hackintosh configuration is not handling well. I did a test on my MacBook (13" i7 2015) and no problem at all with the same version of Adobe softwares and same version of Mojave. 

I've also just switched to VirtualSMC ans tried to install all hackintosh Kext in /L/E (with Hackintool Kext installer) instead of using clover injection, but same problem. 

Here is the send me file : https://drive.google.com/open?id=1EHRUTi9V4vGF6J5sj-bhy8-yPB1FUa_M

Here is my config (HW acceleration working):
- MacOs Mojave 10.14.6 (18G3020)
- i5-3570K
- GA-Z77-D3H
- 16Go RAM 2400Mhz DDR3
- Sapphire Radeon RX 580 4Go
- Kingston SSD 256 Go (system)
- Toshiba SSD 128 Go (cache)
- 2* WD HDD 1To (backup)
- 2* Toshiba USB 3.0 HDD 2To (working files)

Thanks for your help!
MSTRKKRFT

[MaLd0n]

disable igpu and try with smbios iMacPro1,1

[MSTRKKRFT]

1 hour ago, MaLd0n said:

disable igpu and try with smbios iMacPro1,1

Thanks for your help, just tried that (disabled iGPU in BIOS, removed "InjectIntel" and changed to iMacPro1,1 SMBIOS in Clover) and the problem is still there. I did let iGFX as primary option in BIOS, maybe I should use PEG instead ? 
But on the other hand I now have full HW acceleration (H264+HEVC), instead of H264 only before that, so that's definitely a good start  

Here is the new Send Me file : https://drive.google.com/open?id=1z-ZJ6LMu1o5LR_6fPgdShV66QrqK0FKW

[MaLd0n]

TRY

https://filebin.net/tvfa35n6ijccdhnm/CLOVER.zip?t=88ugg9me

[MSTRKKRFT]

I've installed your Clover folder, then I reinstalled Media Encoder (just to be sure everything is clean), and I think it's working now! 
I still can't export converted Premiere Pro 2018 projects in PPro 2019 via Media Encoder (which works without any problem on my MacBook Pro) but for a new sequence made directly into PPro 2019 it seems that everything is working now. 
Will keep you updated about that in this thread, but the problem seems to be solved!! 

I've noticed you added AirportBrcmFixup.kext in Kext folder, is it really needed ? Because I don't have wifi. 

And one last question, do you suggest installing kexts in /L/E or injecting them from Clover ? I've seen so many different point of view among forums.

Thanks again for your help @MaLd0n !! 😁

[MaLd0n]

9 hours ago, MSTRKKRFT said:

you added AirportBrcmFixup.kext

don't need, but no difference with or without