Jump to content
Sign in to follow this  
Followers 0
writyper

mp4 files QuickLook got broken

2 posts in this topic

Recommended Posts

Posted (edited)

I had an (almost) perfectly working hack, but then at some point I found mp4 files preview in Finder no longer works. It just rolls a circle but won't start. Other file types are not affected.

Last changes I made before it broke were installing FCPX + Compressor + Pro Video Formats and then Xcode.

 

I tried different troubleshooting tips but nothing worked. My backup 10.13 system still work just fine with the same EFI.

 

This is an output I get in terminal:

 

 qlmanage -p /Volumes/RAID/Video/_Export/video.mp4 

 

Testing Quick Look preview with files:
    /Volumes/RAID/Video/_Export/video.mp4
objc[821]: Class QLMediaTranscoding is implemented in both /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuickLookUI.framework/Versions/A/PlugIns/Music.qldisplay/Contents/MacOS/Music (0x10e0c80c0) and /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuickLookUI.framework/Versions/A/PlugIns/Movie.qldisplay/Contents/MacOS/Movie (0x10e0fa110). One of the two will be used. Which one is undefined.

 

objc[821]: Class QLMediaExportWindowController is implemented in both /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuickLookUI.framework/Versions/A/PlugIns/Music.qldisplay/Contents/MacOS/Music (0x10e0c8110) and /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuickLookUI.framework/Versions/A/PlugIns/Movie.qldisplay/Contents/MacOS/Movie (0x10e0fa250). One of the two will be used. Which one is undefined.

 

Anyone knows how to fix that ?

Edited by writyper

Share this post


Link to post
Share on other sites
Advertisement

...and this is how I fixed this:

 

How to rebuild the LaunchServices database 
If your "Open With" menu shows applications that are no longer installed, or shows some of them as duplicates, you can use the following Terminal command to rebuild your LaunchServices database:
/System/Library/Frameworks/ApplicationServices.framework/\
Frameworks/LaunchServices.framework/Support/lsregister \
-kill -r -domain local -domain system -domain user

 

source: http://hints.macworld.com/article.php?story=20031215144430486 

 

case closed.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.

Announcements

  • Similar Content

    • By arsradu
      Hi guys,
       
      So, this little tutorial is meant to help people fix a new issue with Mojave: opening jpg files (looks like it happens with larger files, not so much with smaller ones) using Quick Look (on spacebar key pressed) or Preview app, using the dedicated GPUs.
      The issue is that, when trying to open jpg files (for some reason, it doesn't occur with pngs), the pop-up window would remain in an endless loop. And from that point forward, any other app trying to open the same file will either become unresponsive (in the case of the Preview app) or just stay in endless loop (in case of Quick Look)
       
      As a workaround, in case the tutorial below doesn't work for you, you can use Grab (built-in app in MacOS) to open said files.
       
      This issue DOES NOT occur using the iGPU. So...if you're comfortable using the iGPU, just switch to that and you should be good to go. You don't need this tutorial.
       
      This tutorial is based on @Cyberdevs' research and testing on this topic (especially useful if you're using an RX series AMD video card), and my own very limited time testing this on my rig. I just thought it would be useful to create a new thread for it so that people can discuss this particular issue here.

       
      With that being said, I'll just move on to the actual tutorial.
       
      New (probably better) method.
       
      Switch your SMBIOS in Clover config in regards to the dedicated GPU you're using, instead of the CPU. Take a look here and choose the corresponding SMBIOS closest to your hardware.
      Yeah, that's it.
       
      In case you lose CPU PM with this method, there are multiple ways to fix that, and they do not make the object of this thread.  It worked perfectly fine for me though and I didn't need to change anything else.
       
      Alternatively, you can also try one of the MacPro SMBIOSes, such as MacPro5,1 or MacPro6,1. It was tested multiple times and it showed good results. 
      Keep in mind that choosing these will most likely not show you an iGPU in System Report, since those machines generally (probably all of them) use Xeon CPUs with no iGPUs either.
       
      /!\NOTE: There have been reports saying that using this method (switching SMBIOS to a MacPro one) with newer versions of MacOS may cause iTunes to crash.
      So...keep that in mind and better try some of the other methods mentioned here.
       
      A simple Lilu plugin
       
      Thanks to vulgo for the plugin and @Matgen84 for sharing and testing it, we now have yet another possible solution to this issue. It's a Lilu plugin (which means that it requires Lilu.kext in order to work) it's called NoVPAJpeg, and it can be downloaded from here.
      You use it as a regular kext, alongside Lilu. I prefer (and recommend) using it within the EFI folder, in Clover/kexts/Other. But if you want to use it in S/L/E, that should work just fine.
       
      More info can be found in this post here.
       
      UPDATE:
       
      According to Vulgo, NoVPAJpeg.kext is now deprecated.
      In case its functionality is needed, use WhateverGreen.kext (alongside Lilu.kext) and add the following boot arguments:
      shikigva=32 shiki-id=Mac-7BA5B2D9E42DDD94 In case you wanna try alternative medicine  ...
       
      The main thing we need to do is actually very simple: we need to enable the iGPU (integrated GPU) by default, in BIOS, while actually being connected to the dedicated GPU.
       
      For ATI GPUs (curtesy of @Cyberdevs' post here).
       
      The discreet GPU should be set as primary in BIOS and your displays should be connected to your discreet GPU
      The iGD/iGPU/iGFX must be enabled in BIOS/UEFI as the secondary GPU.
       
      I removed the DSDT Reconfigured the config.plist to and removed some flags which weren't needed because of the DSDT added the InjectATI + Ornioco Framebuffer (I removed the Orinoco framebuffer because of some weird glitches but it might be useful for other AMD GPUs if you inject the correct framebuffer according to your GPU. No need to inject anything for nVidia GPUs unless your GPU needs it) Added the InjectIntel + ig-platform-id for my intel HD530 (for intel HD 530 I use the 0x19120001 ig-platform-id)  
      Steps 5 to 7 might not be necessary I just did them anyway, if anyone succeeded to get quicklook working without those steps let me know so I can exclude those steps.

           Also confirmed to work with AMD R9 270X on a SandyBridge rig (without an iGPU) using WhateverGreen + Lilu kexts, which also helped to solve the transparency issue along with the Quick Look problem, it also resolved the buggy Screen Capture (Command+Shift+5) issue as well. 
       
          Also, do:
      nvram cleanup kextcache & prelinked kernel rebuild reboot  More info on that here.
       
       
      For NVIDIA GPUs (tested on my old MSi GTX 650)
       
      This is what I needed for my NVIDIA GPU and the MSI motherboard in the signature (*since then, I upgraded my GPU to my current RX 580). Your milage may vary, depending on your hardware. But, the idea should be the same regardless.
       
         For MSi motherboads (check out my motherboard details in the signature)
       
      Set your BIOS to use PEG (dedicated GPU) so you can boot.
      Since you're reading this, chances are that you're already connected to the dedicated GPU and the BIOS is set to PEG. So just go into BIOS and see if you're using the iGPU or the dedicated (PEG) graphics device by default.
      If you're already using this, skip to Step 3 (the part AFTER Reboot). Reboot (I think you don't necessarily need to boot into the OS...but you do need to reboot at least until Clover UI) Reboot back into BIOS and set it from PEG to IGD (integrated graphics) WITHOUT removing the cable. Save Reboot again.  
         The result should be that the OS is tricked into thinking you're booting with the IGPU when in fact you're using the dedicated GPU.
       
         For Gigabyte motherboards
       
         Set:
      Peripherals -> Initial Display Output -> iGFX Chipset -> Internal Graphics -> Enabled
           DVMT Pre-Allocation -> default 64M.
           DVMT Total Gfx Mem -> default 256M Save Reboot  
         You should do this with the cable connected to the dedicated GPU.
       
      You will also need to patch the iGPU from Clover config.
      1. Graphics -> Inject Intel (UNCHECK Inject Nvidia or ATI if it's checked).
      2. ig-platform-id (in my case for Intel HD 4600 Desktop) it was: 0x0d220003
       
      And use IntelGraphicsFixup.kext (now included into WhateverGreen.kext) in Clover/kexts/Other. In my particular case, without the kext, I would get freezes in Safari.
       
      Another way to activate the iGPU while having the dGPU set as primary is by going into BIOS/SAG/Graphics Configuration/iGPU and setting Multi-Monitor to [Enabled], all the rest remains on [Auto], and set Inject/Intel to [True] in Clover config.*.
       
      Thanks to @gjw for the tip.
       
      *Motherboard dependent. But the multi-monitor option might be the same regardless of manufacturer.
       
       
      This might be a bug with Mojave and it could be fixed by Apple in the future. but in the meantime, feel free to use this if it helps you fix the issue.
       
      For HP motherboards (including laptops), so far no solution, unless the BIOS somehow allows to switch from dGPU to iGPU and vice-versa.
       
      Cheers!
    • By d123c
      When I do some change or annotation in my Preview program, It automatically changes the color of my pictures.
      Does anyone have this problem? Here you have an example.
       

      The following image is the original one:

       
      My Preview software is the 8.0 (859.7) version and my Osx is the 10.10.2 (Yosemite). I would be glad if someone could help me in this problem.
       
      Yours,
       
      Dino 
       
    • By shape5
      Hi all, I was originally trying this with Automator, but if someone can guide me to accomplishing this easier with Applescript then feel free, though i haven't worked with it before.  I am trying to get specific actions within a workflow looped. I just need the workflow to process a single image file continuously so the selected edits repeat within the 1 file until i stop the loop. Here are some basic actions i'm trying to get started with:

      1 - get specified finder items
      2 - copy finder items
      3 - scale images
      4 - crop images
      5 - loop

      The problem is that i want to loop only actions 3 & 4, but the loop starts over at 1 and creates a new file each time it loops. Can i create 2 workflows where the 2nd one (containing actions 3/4/5) starts when the first (containing 1/2) ends so only the 2nd workflow is looped? I'm not sure how to tell the 2nd one to start when the first ends though. Do i just set the input of the 2nd to use the 1st workflow file?
       
      or if it's possible to run this as a service from within Preview that's fine too.  Originally i had this setup as WMD (watch me do) actions but Automator won't record the selection tool. if i can get the selection tool recorded then i can keep it as a WMD based workflow.  Acorn (for crop/scale i believe) & Extra Suites (Applescript app for recording the mouse click & draw) were apps i saw mentioned on other posts that came up on google searches which might be able to help accomplish this workflow or script.

      Any help would be greatly appreciated.

      thanks
    • By YorkiesWorld
      Hi guys,
       
      So I've got my system working somewhat well with Niresh's Mavericks 10.9.0 apart from my GPU. Everything works fine and I do get 1080p resolution, however the Preview App crashes when I use it to view pictures, and I've heard that this could be caused by the driver for the card? I've heard it has something to do with OpenGL or CUDA which I honestly don't know that much about, and was wondering if there's a way to fix the problem by any chance?
       
      Everything else works great so far and there's just this tiny thing left that I need to fix the issue!
    • By justinreyesv
      Recently upgraded to the Yosemite Public Beta and everything is working beautifully, as expected but playing videos causes my hackintosh to crash.
       
      Now I know it's not a Yosemite-specific issue because I had this same issue when I was using Mavericks and installing the NVIDIA Web Drivers fixed it for me (along with the pink-stutter frame issues in Flash Player) but the NVIDIA Web Drivers do not work with Yosemite yet for some reason (don't see why not other than version checking) and they disable themselves on startup.
       
      Is there any way around this? 
       
      My current config is Clover UEFI (latest one)
       
      Intel i5 4670k @ 4.3GHz
      Gigabyte G1 Sniper m5
      16GB DDR3 2200MHz
      EVGA GeForce GTX 760 SC 2GB GDDR5
       
      Hope this is not just something I'm experiencing myself, tried to do a bit more googling and can't find any references (love all the info going around, almost seems like I never have to post anymore and I really try to avoid doing so but I'm completely stumped with this issue)
×