Search results

Loading Google Results...
  1. vinste

    Final Cut Pro X (10.3.2) Crashes

    Yes. No need to reinsert your smbios. Just try it, fast and easy. Worst case: it does not work, and then you revert to your config.
  2. vinste

    Final Cut Pro X (10.3.2) Crashes

    You corrupted the smbios while removing personal info, no big deal. Did tou try the config.plist? It includes some changes that could help.
  3. vinste

    Final Cut Pro X (10.3.2) Crashes

    No major issue there; you can still give this config.plist a try. I reinitialized your smbios, as it was corrupted
  4. vinste

    Final Cut Pro X (10.3.2) Crashes

    Yes, FCPX still works in 10.13.1 If you use clover, you can post your EFI folder, I will have a look (and your clover version)
  5. vinste

    Radeon Compatibility Guide - ATI/AMD Graphics Cards

    In a correctly configured setup (and in standard macs), iGPU does indeed not appear in luxmark: it shall be configured as connectorless and is then used for video encoding/decoding acceleration, while the 560 is used for opencl acceleration. If iGPU appears in Luxmark, then some apps such as...
  6. vinste

    Final Cut Pro X 10.3 crash

    I think it is, and I would say it depends on the task that is assigned (decoding/encoding/which quality/which resolution). On my side, I can see the iGPU frequency varying from a few Mhz while decoding a youtube video to 1.15 Ghz while exporting a 4K FCPX timeline
  7. vinste

    Final Cut Pro X 10.3 crash

    By vanilla, I mean only original kexts in L/E and S/L/E, and no configuration change outside of clover. From what I understand, shikigva=1 should not be needed if you do not modify AppleGVA.framework to enforce offline rendering.
  8. vinste

    Final Cut Pro X 10.3 crash

    Did you modify any Kext or com.apple.AppleGVA or com.apple.coremedia? It should all be vanilla
  9. vinste

    Final Cut Pro X 10.3 crash

    You have the explanation here. Nothing strictly necessary for your concern, but it puts you hack closer to a real mac, which is never a bad thing for stability.
  10. vinste

    Final Cut Pro X 10.3 crash

    Quicksync is not for rendering, it is for transcoding (h264/h265). There is no transcoding in BruceX, only opencl rendering through your 580. Exporting a h264 video with quicksync is a magnitude faster than without. Quicksync accelerates video a bit everywhere in macos: it decodes video in...
  11. vinste

    Final Cut Pro X 10.3 crash

    7-8 seconds for BruceX is typically when the timeline is pre-rendered. I would say that even 13 seconds is too fast for a 580. It should rather be around 17 seconds. You might have some rendered files already in your project. Deactivate background rendering, quit FCP and erase rendered files...
  12. vinste

    Final Cut Pro X 10.3 crash

    Can you try this config.plist? iGPU needs to be enabled, 64M min RAM/Max maximum RAM, PCIe GPU as prime
  13. vinste

    Final Cut Pro X 10.3 crash

    Sure, it works, as stated in previous post...
  14. vinste

    Sapphire Radeon RX Vega 64 on macOS

    You should enable iGPU and use Shiki for this. Not sure Vega can wake properly if you disable iGPU. And with it, you would have hw accelerated video in Safari and iTunes.
  15. vinste

    High Sierra - RX Vega & Final Cut h.264 fix

    you could just try this config.plist
  16. vinste

    Sapphire Radeon RX Vega 64 on macOS

    You could try this one (changed some kexts and config.plist) Vega has to be prime in Bios (PCIe1 surely), and iGPU activated with 64M memory min.
  17. vinste

    Sapphire Radeon RX Vega 64 on macOS

    Can you attach you EFI? Sleep works fine for me.
  18. vinste

    High Sierra - RX Vega & Final Cut h.264 fix

    Well, it is quite off-topic, but if you attach your EFI folder, I can have a look. Our setups are quite alike, it should work the same.
  19. vinste

    High Sierra - RX Vega & Final Cut h.264 fix

    It seems acceleration works now ok in 10.13.2 beta 0. I had even +10-15% opencl performance boot for my Vega 64. Still, sleep/wake does not work anymore, and fan spins very fast to keep the GPU cool, and is then quite loud... reverted to 10.13.1.
  20. vinste

    Post macOS/OS X Geekbench Benchmarks

    Nice 15% opencl performance increase with Vega in 10.13.2 beta 0 (https://browser.geekbench.com/v4/compute/1325116 -> https://browser.geekbench.com/v4/compute/1326514), but fan spin fast and loud, and Lilu panics now, so no Whatevergreen, and hazardous sleep/wake.
Top