Jump to content

Driftwood

Members
  • Posts

    457
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by Driftwood

  1. Download Hackintools and use it's calculator or use a hex to decimal converter. Enter each of your hex values and convert to Decimal in this calc, then copy and paste each decimal value into each added child entries which you 'Add' (0 to 18) under mmiowhitelist in config.plist. You find your hex numbers on each line of MMiO section (19 lines of MMIO 0xnnnnnnnnn values) in your opencore debug txt boot log using search. Child 0 to 14 will be Boolean value = Yes. The last four (15 to 18) = No, or you can actually forget about adding the last four child's as they are Negative values (not used)
  2. Did you check your other DP/hdmi port for picture? Sometimes when it goes black, its booted! Maybe upgrade to latest OC build to help too
  3. It's Apple who keep dropping the hardware support. The last great bastion is encoding HEVC PQ Rec2020 420 10-bit for HDR TV/Netflix style delivery. I haven't seen any NLE that can beat x265 CPU encoding. And that's the way I do it and using Handbrake GUI. Threadripper with 32 cores64 threads beats them all at software CPU encodes. Ridiculously fast! At 8-bit HEVC or h264 Media Encoder and fcpx etc... work well. It's 10-bit and now 12-bit HEVC that is the problem as it is so mathematically challenging. Davinci resolve gives me around 8fps in 10 bit. They're all slow outside x265. True 10-bit HEVC hardware support will need to be sorted out in Mac. And Apple are directly responsible for stopping AMD and Nvidia in their tracks - certainly for 'prosumer' level cards. We need encode, not just decode! We wait with baited breath to see support returned.
  4. No its all good. Methinks I don't need any Device Properties I guess. Thanks so much for letting me try. Of course on Air, I don't wanna damage these babies! But I think you gave me a rather safe power table. I get the drift, we're all good in Metal and that's what matters.
  5. @iGPU Gave it a whirl in Catalina: No real performance increase (slight decrease). Im getting 98fps avg on BS without DevProp, but will try it over on BS shortly. Here's OC debug text DevProp rip which I assume success means the DevProps were loaded ok.
  6. @iGPU After trying the DSDT, and looking at comparable builds I am at a losss to explain your 149 fps? There must be something else you are doing or can you get down to the nitty gritty of the DSDT to find out the cause of this graphics performance in CB15? I have to O/c to 4Ghz just to get over 100fps! I really need to understand how. You are not o/c GPU's etc..?. I know u have a decent water block setup but 50% greater than most of us is really quite stunning.
  7. Im definitely getting mediocre results when looking at other TRX40 / Asrock board owners (rocket88). Im going to have to fine tune things...
  8. Thanks @iGPU couldn't see a great deal of difference in BS on benchmark tests. Slight improvement on Apple Compressor rendering! Big Sur BM Tests - NO XMP(Above 4G Enabled, Macpro7,1)
  9. @iGPU Here's the Asrock TRX40 Creator (Above 4G, CSM Disabled BIOS, standard settings) DSDT file to add to your database. Asrock Creator Above 4G no csm DSDT.zip
  10. @iGPU @meina222 Can u rip out all the common essentials for TRX40 and create SSDTs out of them? Be interesting to see.
  11. This sounds like... amazing. Must try it out. What are our common MMIO addresses referencing? Do you know? UPDATE: Like @fabiosun same, an error at start. Hung there and rebooted.
  12. HEVC Encode Test on AMD Threadripper. Adobe Media Encoder Metal Works on AMD Hackintosh - Apple's Compressor doesn't seem to be able to use Metal with AMD Hackintosh. In 5 minutes, Adobe ME Beta had finished transcoding a 10 minute long 12-bit 4444 UHD video file to a HEVC 420 10-bit mp4, in the same time Apple Compressor had barely started - clearly its not making use of Metal and is Software/CPU only. Handbrake is quicker than Compressor using CPU software encoding doing same file 20% quicker than Compressor. Compressor would have taken over an hour to complete so I stopped it! UPDATE: After much reading it appears the following:- HEVC is hardware-accelerated only in single-pass, 8-bit mode. This is reasonably fast, but not as fast as compressing media into H.264. 10-bit HEVC, which is required for HDR media, is compressed in software – and, that takes forever! If you are going to do any form of HEVC encoding, use ffmpeg or Handbrake GUI because they implemented tried and test, fast and efficient encoders developed over many years, AND they fully implement the use of the hardware where it can.
  13. Ok Ive just done a latest commit build using Pavo's OCBuilder to bring my efi's and kexts etc BANG! up-to-date. Here's the latest Big Sur EFI folder complete for Asrock'ers or anyone who needs to analyze for their board. Driftwood Big Sur Bare Metal EFI - Asrock TRX40 Creator EFI.zip
  14. LOL! Its amazing the trouble we go through and all it is is something simple. I guess certain USB hardware is safe and others not. I use a Editors Keys Mac keyboard and is seen by OSX as Mac and works without problems. I guess PC keyboards may be providing the error.
  15. Latest OC061 Commits Config manuals and differences pdfs. Release version should be tomorrow (Pavo). OC061 Latest Commits manual and Differences.zip
  16. @fabiosun and anyone else who wants to see or use my working EFI folders together with config.plists. If you try, simply edit the Platforminfo UUIDs as usual. Also please check if you receive relinked errors either way (ie your Library/Extensions folder has matching kexts or older kexts in these EFIs match L/E - as you may have to update your kextcache kernel cache properly to get these working. For Proxmox you will need to sort out your MMIO, vm.conf, vfio.conf and bl'cklists. Here's the EFI folders:- Proxmox Catalina Driftwood Proxmox - Catalina EFI FOlder.zip Proxmox Big Sur (last used on beta 2) Driftwood Proxmox - Big Sur EFI Folder.zip Bare Metal Catalina Driftwood Catalina Bare Metal EFI Folder.zip Bare Metal Big Sur (works on beta 6) Driftwood Big Sur Bare Metal EFI Folder.zip
  17. The only problem with going virtualized is the clock and timings. This is critical for audio and video apps. This is why I still run both, and BM is of course best for timing. For Penryn compatability and using all intel_memset.A compiled stuff, Proxmox is best. The patches (or rather layer removers) for Photoshop and Davinci in BM are okay but not so ideal a workaround. Personally, I would like lilu to be improved more with patches to do intel compiled spoofing to use intel_memset.V etc... this is what u pay for either side 🙂
  18. Okayish... This is Big Sur beta 6 (Prox to come) Im running on standard BIOS RAM setups not Performance if that matters...!? Plus I had a few apps running inc safari 🙂
  19. I can't seem to get CB15 working still in BS. Only 20 works for me unless someone has a reliable CB15 link which works for them?
  20. VIDEO ENCODING BigSur Tests 35000 bitrate HEVC 10-bit Encode from 10-bit Apple Pro Res Raw 4444 Just been going thru all the available video encoding on Big Sur and it appears that Adobe Media Encoder is the fastest encoder of them all - encoding twice the speed of frame rate. Apple's Compressor for some reason is not making use of Metal and CPU only but it was very slow and I need to look into that as Im sure it should work. Handbrake only uses CPU for HEVC 265 10-bit and processed footage in slightly above realtime fps. @fabiosun Ill do some new bench tests for your question.
  21. So Ive been looking at the problem of certain programs not working under AMD because of the old Intel_memset.A compiler problem. Intel tuned compilation. Ive tried in Camtasia and looked at some Waves plugins to see if a way would be implemented to make the call(} routines edited and changed to go to intel_memset.V but to no avail. Also there's some good stuff out there like the dispatchpatches in the attached zip. Has anyone tried using these for cpu spoofing or maybe a way of getting Lilu patched so that the intel_memset compile is redirected? Read the reader inside and see Mac patches) inteldispatchpatch.zip For Waves, I see that some of the Hackintosh guys recommend an MKL CPU debug (like stuff found in above) when attempting to debug run Logic with Waves AU plugins. In terminal, use MKL_DEBUG_CPU_TYPE=5 /Applications/Logic\ Pro\ X.app/Contents/MacOS/Logic\ Pro\ X
  22. You basically program the stand alone mode by copying your input/ouput setup into firmware of the RME FF800. Then you detach it from computer and use it live on the road or studio and it will retain those settings for Input/Output path as standalone. See manual. If you are switching it between computers all settings are retained. The RME FF800 drivers which work both in Catalina and Big Sur are here: driver_fw_mac_339.zip The same driver works under Proxmox with non-abridged firewire card like mine! Though, it is not as 'reliable' as bare metal. I use two RMEFF800s. They're stilll top quality! However, I am about to buy the newly announced AIO Pro (RMEs new AIO card version which is clean (no headphone noise) and better pathways in the digital process. For me (who uses predominantly plugins inside Logic and Avid Pro Tools) the AIO card is just as good as an MADI FX card which is a little bit more expensive but if you require a ton of inputs /outputs would be better option. The AIO Pro card is released within the next two weeks Synthax tell me - Price around 560 - 650 EUs/dollars/GBPs
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.