Compressor doesn't work

after some problem and restarting Copressor (FCP 6) seems to stop working... Progress bar shows, but doesn't run... What do i have to do?

try these instructions. Worked for me after all else failed, and did not have to reinstall all of FCP.
Good luck
http://www.scottsimmons.tv/blog/2008/01/11/compressor-hatred-resolved

Similar Messages

  • HT4664 compressor doesn t work till maverick is install

    till i install marverick, compressor doesn t work, what should i do, i can t open it to install update... it say to old version... it does t appear on the app strode cause it was furnish with tha IMac

    I'm afraid you will need to contact Apple to get this straightened out.
    Russ

  • Compressor doesn't work/won't install after FCP5 install

    We recently "upgraded" one of the G5s in our lab to Final Cut Pro 5 from FCP HD 4.5 (these were both Academic versions if that matters, so it's not really an upgrade, you buy a new license at academic pricing). I don't remember which we did first, but we also upgraded this machine to Tiger at the same time.
    The guy that does most of the video work on this machine reported to me that compressor wasn't working. That it would launch and crash, and sure enough it does. So I did some investigating, and the version of Compressor that appears to be installed on the system is 1.2.1, but doesn't Compressor 2 come with Final Cut Pro 5 (or is it just Studio)? I tried to reinstall from the disk and and on the install screen where it lists the packages to install (the 'Custom Install on "Macintosh HD"' screen), Compressor shows up as unchecked, greyed out and with "Skip" in the Action column. I've even tried removing Compressor from the Applications folder and that doesn't seem to make a difference. Is there any way for me to force the installer to install the version of Compressor on the Final Cut Pro 5 disk?
    Something seems to be messed up. Any help would be greatly appreciated. Thanks!
    PowerMac G5   Mac OS X (10.4.3)  

    OK, it took some fiddling, but I got Compressor to install correctly. First I tried the instructions Apple has here:
    http://docs.info.apple.com/article.html?artnum=93234
    but that didn't help.
    So then I found this page with a brief article on "Tricks to install Compressor 2 on G3 Mac":
    http://www.xlr8yourmac.com/archives/jun05/060305.html
    Not very descriptive, but I basically had to make a local copy of the Compressor package from the Final Cut Pro Install disk, then go in and remove the InstallerCheck and VolumeCheck files and then manually install that package by itself.
    I did a reinstall of FCP5 from the disk for good measure after that, and then a software update. It still says "Skip" for Compressor vs. "Update" for everything else when you are in the FCP installer. Everything seems to be working fine now though.
    This seems like a serious problem in Apple's Final Cut Pro 5 installation package (at least for the academic version and whatever sequence of steps got us into this state).

  • FCP 4.0 COMPRESSOR DOESN'T WORK AFTER UPDATING TO 10.11.4

    CAN'T SELECT COMPRESSOR IN MY FCP 4.0 SINCE I UPDATED TO 10.11.4

    Sounds like they did an Archive & Install, which leaves you with non-functioning Pro Apps (and Adobe apps, if you have any).
    Try removing Final Cut Pro and Compressor and reinstall.
    Instructions for reinstalling Final Cut Pro: http://support.apple.com/kb/TS1846
    Instructions for reinstalling Compressor: http://support.apple.com/kb/TS1888
    There is an application called FCS Remover, but I am not sure if it works with Final Cut Pro 4.
    If it is still not working, I would try what David suggests.
    Here is a list Jon Chappell has compiled about what versions of OS X, QuickTime and FCP works best together: http://www.digitalrebellion.com/blog/posts/recommendedquicktime_and_mac_os_configurations_for_final_cutpro.html
    If you live close to an AppleStore you could try to bring it back and ask them to help you.
    Best of luck!

  • Compressor doesn't work anymore....

    Hello,
    I got a really strange bug,
    I can not use Compressor anymore...
    I can't see the "project" window where there is all my video-sequence...
    I can only see these windows :
    • "Settings / Destinations"
    • "Inspector"
    • "Preview" (but the preview window looks very buggy, i think...
    • "History"
    So I can't add any new video to compress/export... and I can add any setting to export the videos...
    I try 2 times, to errase all the Compressor Applications and application support and prefs..
    and try to reinstall from the original DVD.
    but it don't work again and again....
    PLEASE HELP !!!
    now, I don't know what to do...
    Perhaps I didn't erase & re-install the applications and compressor files properly,
    but, CAN ANYONE HELP ME PLEASE ?!!
    Thanks in advance.

    keyman: Try following the steps Compressor Zealot links to. Read the instructions carefully, and make sure you remove all the Compressor/Qmaster files before reinstalling.
    Eyebite wrote:
    don't plan on using Virtual Clustering. As far as I can determine, no one has that working yet.
    Uhmmm... Virtual Clustering works fine, but you can not use virtual clustering when sending your sequence directly from FCP to Compressor.
    Compressor: Don't export from Final Cut Pro using a Virtual Cluster
    To transcode your FCP-sequence using Virtual Clustering with Compressor 3, you can export your sequence as a self-contained ProRes file, and then bring that file into Compressor.
    Keep in mind that job segmenting is not always good for compression.
    Job Segmenting and Two-Pass (or Multi-Pass) Encoding
    If you choose the two-pass or the multi-pass mode, and you have distributed processing enabled, you may have to make a choice between speedier processing and ensuring the highest possible quality.
    The Apple Qmaster distributed processing system speeds up processing by distributing work to multiple processing nodes (computers). One way it does this is by dividing up the total amount of frames in a job into smaller segments. Each of the processing computers then works on a different segment. Since the nodes are working in parallel, the job is finished sooner than it would have been on a single computer. But with two-pass VBR and multi-pass encoding, each segment is treated individually so the bit-rate allocation generated in the first pass for any one segment does not include information from the segments processed on other computers. First, evaluate the encoding difficulty (complexity) of your source media. Then, decide whether or not to allow job segmenting (with the “Allow Job Segmenting” checkbox at the top of the Encoder pane). If the distribution of simple and complex areas of the media is similar throughout the whole source media file, then you can get the same quality whether segmenting is turned on or not. In that case, it makes sense to allow segmenting to speed up the processing time.
    However, you may have a source media file with an uneven distribution of complex scenes. For example, suppose you have a 2-hour sports program in which the first hour is the pregame show with relatively static talking heads, and the second hour is high-action sports footage. If this source media were evenly split into 2 segments, the bit rate allocation plan for the first segment would not be able to “donate” some of its bits to the second segment because the segments would be processed on separate computers. The quality of the more complex action footage in the second segment would suffer. In this case, if your goal were ensuring the highest possible quality over the entire 2-hour program, it would make sense to not allow job segmenting by deselecting the checkbox at the top of the Encoder pane. This forces the job (and therefore, the bit-rate allocation) to be processed on a single computer.
    Note: The “Allow Job Segmenting” checkbox only affects the segmenting of individual jobs (source files). If you are submitting batches with multiple jobs, the distributed processing system will continue to speed up processing by distributing (unsegmented) jobs, even with job segmenting turned off.
    From the Compressor User Manual

  • Compressor doesn't work after migrating

    I just bought a new MacPro 2.66 Quad Core and migrated everything from my old Mac Pro (Dual). I had to re-enter my FCP serial - FCP works fine. Compressor does open but when I want to submit a job it tells me "unable to submit to queue", make sure compressor is installed correct. Any clue? Since I hace compressor 3.0.5 installed I hate to go back to the DVD's.

    ProApps work better with a fresh install. Migrating has been known to cause problems. But since you're already there, try this: http://www.digitalrebellion.com/compressor_repair.htm
    -DH

  • Why exporing with compressor doesn't work

    Hi friends and ..... merry xmas
    a little and silly question but important for me now....
    I've a little movie about 15' and try to export with compressor, but when I submit I get an error:
    Status: Failed - 3x error: NewMovieFromFile failed -50
    Everything is at the right place, but I can't export with compressor why???
    Thanks 4 your support

    15 minutes is a REALLY long file in Motion. You should try breaking it up into more manageable segments, maybe 5 min apiece.
    Also, it's been noted that Exporting via Compressor is buggy from Motion. Try exporting a QT and then taking that into Compressor.
    Andy

  • Compressor 4 doesn't work since I installed Mavericks and I can't export a video normally on FCPX either.

    Compressor 4 doesn't work since I installed Mavericks and I can't export a video normally on FCPX either.
    Can someone help me?
    Thank you!

    Got the phone direct from the Apple website, so I assume it was unlocked, and it had been on giffgaff ever since but I don't see why that's a problem?
    The carrier was automatically selected as Free and is up to date.
    There seemed to be no problem that the SIM was being used in an iPhone 4 and my friends in exactly the same situation (e.g. arriving in France and moving over to the Free network with iPhone 4's) have had zero problems with their 3G network; it just seems to be me.
    The Free Mobile Network is included on this list which I guess means that they are Apple-approved? iPhone: Wireless carrier support and features
    How do I find out whether or not I would need to manually configure an APN? I'm not even sure I know what that is.

  • H264.mov , Flash 9 - QT pro works, Compressor Doesn't???

    Creating h.264 movies with QT Pro. Change extension, to .flv, they play fine in Flash 9 player. Use Compressor to make similar movie, change extension to .flv, it doesn't work.
    I need to batch hundreds of movies as we update our websites, so repeatable, preset driven work flow is a must. Any idea why QT Pro works and Compressor doesn't?
    Thank in advance for your time.
    Frank

    You need a mpeg4 compresson that's is set for h.264. The mpeg4 in Compressor doesn't have the setting. Here read this: http://discussions.apple.com/message.jspa?messageID=8779452#8779452

  • Compressor doesn't open and show windows properly

    Haven't used Compressor for a while and when I open it I don't get the windows, just the bar at the top. Choosing a windows layout doesn't work and although you can switch on the inspector, settings/destination and history windows I can't display the window that you drag the files, settings and destinations into. I've tried re-installing, no good. All other FCS programs work fine, before and after re-install, anyone know what's going on?

    Tried all the above suggestions, just had to properly uninstall FCS with FCS Remover then re-install. Window display is fine now but I'm not sure if it's actually doing anything, submit a job but nothing seems to be produced ...looking into that.

  • [Solved] Network doesn't work after hibernate?

    Hello!  This is my first legit Linux install so excuse me if I'm a bit slow.  I installed Arch last night and everything went smoothly.  However, after I tested out hibernate on my machine, the network doesn't seem to work.  Just prior to the hibernate, I installed Pidgin and Skype but they worked alright, so I think that the hibernate caused a problem on eth0.
    I have an Asus P8Z68-V Pro motherboard with an Intel 82579V Gigabit Ethernet Controller that's using the e1000e driver.  Running "dmesg | grep e1000e" says that it is up.
    I'm not entirely clear here, but from reading, I think that I have several ways of connecting to the network, including network, dhcpcd, networkmanager, and wicd.  I am using wicd so I did the following (or at least I think I am only using wicd):
    #rc.d stop network
    #rc.d stop dhcpcd
    #rc.d stop networkmanager
    Similarly, I put a ! in front of network in rc.conf:
    # /etc/rc.conf - Main Configuration for Arch Linux
    # LOCALIZATION
    # LOCALE: available languages can be listed with the 'locale -a' command
    # DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
    # startup and during the boot process. If set to 'no', the C locale is used.
    # HARDWARECLOCK: set to "", "UTC" or "localtime", any other value will result
    # in the hardware clock being left untouched (useful for virtualization)
    # Note: Using "localtime" is discouraged, using "" makes hwclock fall back
    # to the value in /var/lib/hwclock/adjfile
    # TIMEZONE: timezones are found in /usr/share/zoneinfo
    # Note: if unset, the value in /etc/localtime is used unchanged
    # KEYMAP: keymaps are found in /usr/share/kbd/keymaps
    # CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
    # CONSOLEMAP: found in /usr/share/kbd/consoletrans
    # USECOLOR: use ANSI color sequences in startup messages
    LOCALE="en_US.UTF-8"
    DAEMON_LOCALE="no"
    HARDWARECLOCK="UTC"
    TIMEZONE="America/New_York"
    KEYMAP="us"
    CONSOLEFONT=
    CONSOLEMAP=
    USECOLOR="yes"
    # HARDWARE
    # MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
    # Replace every !module by an entry as on the following line in a file in
    # /etc/modprobe.d:
    # blacklist module
    # See "man modprobe.conf" for details.
    MODULES=()
    # Udev settle timeout (default to 30)
    UDEV_TIMEOUT=30
    # Scan for FakeRAID (dmraid) Volumes at startup
    USEDMRAID="no"
    # Scan for BTRFS volumes at startup
    USEBTRFS="no"
    # Scan for LVM volume groups at startup, required if you use LVM
    USELVM="no"
    # NETWORKING
    # HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
    HOSTNAME="Vicious"
    # Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
    # Wired network setup
    # - interface: name of device (required)
    # - address: IP address (leave blank for DHCP)
    # - netmask: subnet mask (ignored for DHCP) (optional, defaults to 255.255.255.0)
    # - broadcast: broadcast address (ignored for DHCP) (optional)
    # - gateway: default route (ignored for DHCP)
    # Static IP example
    # interface=eth0
    # address=192.168.0.2
    # netmask=255.255.255.0
    # broadcast=192.168.0.255
    # gateway=192.168.0.1
    # DHCP example
    # interface=eth0
    # address=
    # netmask=
    # gateway=
    interface=eth0
    address=
    netmask=
    broadcast=
    gateway=
    # Setting this to "yes" will skip network shutdown.
    # This is required if your root device is on NFS.
    NETWORK_PERSIST="no"
    # Enable these netcfg profiles at boot-up. These are useful if you happen to
    # need more advanced network features than the simple network service
    # supports, such as multiple network configurations (ie, laptop users)
    # - set to 'menu' to present a menu during boot-up (dialog package required)
    # - prefix an entry with a ! to disable it
    # Network profiles are found in /etc/network.d
    # This requires the netcfg package
    #NETWORKS=(main)
    # DAEMONS
    # Daemons to start at boot-up (in this order)
    # - prefix a daemon with a ! to disable it
    # - prefix a daemon with a @ to start it up in the background
    # If something other takes care of your hardware clock (ntpd, dual-boot...)
    # you should disable 'hwclock' here.
    DAEMONS=(hwclock syslog-ng dbus !network netfs crond wicd)
    Restarting eth0 through wicd-cli still did not work.  I also tried resuscitating the network via instructions on the configure network page before trying to focus solely on wicd.
    I found a few similar problems on the forums by searching "wicd hibernate" and tried several solutions but they did not work.  Several problems seem to be that the network doesn't work after a suspend because I guess the stuff in RAM did not get saved?  But people were able to restart the network by running "/usr/lib/wicd/autoconnect.py" and I wasn't able to get this to work.  As a final effort, I added "resume" into mkinitcpio.conf and placed the machine into sleep again to see if it may magically reset something but of course this did not happen .
    mkinitcpio.conf:
    # vim:set ft=sh
    # MODULES
    # The following modules are loaded before any boot hooks are
    # run. Advanced users may wish to specify all system modules
    # in this array. For instance:
    # MODULES="piix ide_disk reiserfs"
    MODULES=""
    # BINARIES
    # This setting includes any additional binaries a given user may
    # wish into the CPIO image. This is run first, so it may be used to
    # override the actual binaries used in a given hook.
    # (Existing files are NOT overwritten if already added)
    # BINARIES are dependency parsed, so you may safely ignore libraries
    BINARIES=""
    # FILES
    # This setting is similar to BINARIES above, however, files are added
    # as-is and are not parsed in any way. This is useful for config files.
    # Some users may wish to include modprobe.conf for custom module options
    # like so:
    # FILES="/etc/modprobe.d/modprobe.conf"
    FILES=""
    # HOOKS
    # This is the most important setting in this file. The HOOKS control the
    # modules and scripts added to the image, and what happens at boot time.
    # Order is important, and it is recommended that you do not change the
    # order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
    # help on a given hook.
    # 'base' is _required_ unless you know precisely what you are doing.
    # 'udev' is _required_ in order to automatically load modules
    # 'filesystems' is _required_ unless you specify your fs modules in MODULES
    # Examples:
    ## This setup specifies all modules in the MODULES setting above.
    ## No raid, lvm2, or encrypted root is needed.
    # HOOKS="base"
    ## This setup will autodetect all modules for your system and should
    ## work as a sane default
    # HOOKS="base udev autodetect pata scsi sata filesystems"
    ## This is identical to the above, except the old ide subsystem is
    ## used for IDE devices instead of the new pata subsystem.
    # HOOKS="base udev autodetect ide scsi sata filesystems"
    ## This setup will generate a 'full' image which supports most systems.
    ## No autodetection is done.
    # HOOKS="base udev pata scsi sata usb filesystems"
    ## This setup assembles a pata mdadm array with an encrypted root FS.
    ## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
    # HOOKS="base udev pata mdadm encrypt filesystems"
    ## This setup loads an lvm2 volume group on a usb device.
    # HOOKS="base udev usb lvm2 filesystems"
    HOOKS="base udev autodetect pata scsi sata resume filesystems usbinput"
    # COMPRESSION
    # Use this to compress the initramfs image. With kernels earlier than
    # 2.6.30, only gzip is supported, which is also the default. Newer kernels
    # support gzip, bzip2 and lzma. Kernels 2.6.38 and later support xz
    # compression.
    #COMPRESSION="gzip"
    #COMPRESSION="bzip2"
    #COMPRESSION="lzma"
    #COMPRESSION="xz"
    #COMPRESSION="lzop"
    # COMPRESSION_OPTIONS
    # Additional options for the compressor
    #COMPRESSION_OPTIONS=""
    Not sure if my fstab.conf is useful but if this has something to do with settings getting "lost" in swap, here it is.  Linux is on an SSD and HDD (sda and sdc) and Windows 7 is on a HDD (sdb).
    fstab.conf:
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    none /tmp tmpfs nodev,nosuid,noatime,size=2000M,mode=1777 0 0
    /dev/sda1 / ext4 defaults,noatime,discard 0 1
    /dev/sda2 /home ext4 defaults,noatime,discard 0 2
    /dev/sdc1 /boot ext4 defaults 0 1
    /dev/sdc2 /var ext4 defaults 0 0
    /dev/sdc3 swap swap defaults 0 0
    /dev/sdc4 /media/data ext4 defaults 0 0
    shm /dev/shm tmpfs nodev,nosuid,size=10G 0 0
    Is wicd causing these problems or did I configure something else improperly?  Would appreciate any help to get eth0 up again!
    Last edited by TheBigCow7 (2011-09-13 17:57:20)

    Ok, I think I've made some progress!  Hibernate definitely affects my network connection.  Could this be a kernel 3.0 problem?
    I noticed that ifconfig showed eth0 without an inet addr, just an inet6 addr for the longest time.  e1000e seemed to be loading up ok.  I'm not certain here, but I think that meant the dhcp settings didn't stick, or something along those lines.
    Trying to use dhcpcd like the instructions here did not work.  By some chance, one attempt did work and while it did, I downloaded and installed dhclient.  After that one successful attempt, renewing the DHCP lease via dhcpcd did not work again.
    Luckily though, I found that running "dhclient eth0" worked.  My DHCP settings seemed to have somehow gotten messed up after my initial, problematic hibernate to the point where none would stick, even after a reboot.  Manually typing in "dhclient eth0" would get eth0 working, so I decided to add it to the bottom of /etc/rc.local, like in the example on the networking page.
    Now, eth0 works after a boot.  However, after the daemons load up during the boot process, my computer takes a long time to get to the login prompt (this is relatively speaking, since I am on a SSD and the boot process used to be blazing fast before).  I'm pretty sure it's because I added "dhclient eth0" to /etc/rc.local.
    I should say that even with these changes, after a hibernate, my eth0 still does not work and if it weren't for the edit to /etc/rc.local, eth0's inet settings would still not stick after a reboot (that is to say, the hibernate does do something to my network settings). 
    Is this the correct/most efficient way to fix my DHCP problem?  Can I fix my "eth0 after hibernate" issue?  Also, can I make my DHCP settings boot up without changes to /etc/rc.local so that I can get a fast boot again (still not sure how it was able to work before without my edit)?

  • SUBMIT FUNCTION ON COMPRESSOR IS NOT WORKING

    Hi Everybody!
    I was overseas for a while and when I came back to work, my workstation was updated I guess.
    I'm using the FINAL CUT STUDIO 3, I did not any updates yet.
    My issue is when I'm trying to send a sequence, from the timiline in final cut (SEND TO/COMPRESSOR) everything seems to be normal. Once I do all the settings and destinations on COMPRESSOR, and I'm ready to start the render, I'm able to see the SUBMIT button, but it seems to be inactive...
    Probably u have already figured out the way to fix this issue...
    please help guys, this is delaying my overall process so much!
    Thanks!

    Hi everybody!
    Compressor don't works! I can't use the submit function because it doesn't work. Help me!
    I removed compressor and Qmaster and re-installed them: in this way the submit function works and I can save the job on "this computer", but when I download the compressor's upgrade the submit function stops to work.
    I'm sorry, I'm italian and my english is very bad!

  • Plymouth doesn't work [SOLVED]

    Hello!
    Plymouth doesn't work.
    I installed plymouth, added plymouth to HOOKS array in /etc/mkinitcpio.conf file, added "quiet splash" to /etc/default/grub file and ran "sudo grub-mkconfig -o /boot/grub/grub.cfg" followed by "sudo plymouth-set-default-theme -R solar".
    File /etc/mkinitcpio.conf
    # vim:set ft=sh
    # MODULES
    # The following modules are loaded before any boot hooks are
    # run. Advanced users may wish to specify all system modules
    # in this array. For instance:
    # MODULES="piix ide_disk reiserfs"
    MODULES=""
    # BINARIES
    # This setting includes any additional binaries a given user may
    # wish into the CPIO image. This is run last, so it may be used to
    # override the actual binaries included by a given hook
    # BINARIES are dependency parsed, so you may safely ignore libraries
    BINARIES=""
    # FILES
    # This setting is similar to BINARIES above, however, files are added
    # as-is and are not parsed in any way. This is useful for config files.
    FILES=""
    # HOOKS
    # This is the most important setting in this file. The HOOKS control the
    # modules and scripts added to the image, and what happens at boot time.
    # Order is important, and it is recommended that you do not change the
    # order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
    # help on a given hook.
    # 'base' is _required_ unless you know precisely what you are doing.
    # 'udev' is _required_ in order to automatically load modules
    # 'filesystems' is _required_ unless you specify your fs modules in MODULES
    # Examples:
    ## This setup specifies all modules in the MODULES setting above.
    ## No raid, lvm2, or encrypted root is needed.
    # HOOKS="base"
    ## This setup will autodetect all modules for your system and should
    ## work as a sane default
    # HOOKS="base udev autodetect block filesystems"
    ## This setup will generate a 'full' image which supports most systems.
    ## No autodetection is done.
    # HOOKS="base udev block filesystems"
    ## This setup assembles a pata mdadm array with an encrypted root FS.
    ## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
    # HOOKS="base udev block mdadm encrypt filesystems"
    ## This setup loads an lvm2 volume group on a usb device.
    # HOOKS="base udev block lvm2 filesystems"
    ## NOTE: If you have /usr on a separate partition, you MUST include the
    # usr, fsck and shutdown hooks.
    HOOKS="base udev plymouth autodetect modconf block filesystems keyboard fsck nvidia"
    # COMPRESSION
    # Use this to compress the initramfs image. By default, gzip compression
    # is used. Use 'cat' to create an uncompressed image.
    #COMPRESSION="gzip"
    #COMPRESSION="bzip2"
    #COMPRESSION="lzma"
    #COMPRESSION="xz"
    #COMPRESSION="lzop"
    #COMPRESSION="lz4"
    # COMPRESSION_OPTIONS
    # Additional options for the compressor
    #COMPRESSION_OPTIONS=""
    File /etc/default/grub
    GRUB_DEFAULT=0
    GRUB_TIMEOUT=5
    GRUB_DISTRIBUTOR="Arch"
    GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
    GRUB_CMDLINE_LINUX=""
    # Preload both GPT and MBR modules so that they are not missed
    GRUB_PRELOAD_MODULES="part_gpt part_msdos"
    # Uncomment to enable Hidden Menu, and optionally hide the timeout count
    #GRUB_HIDDEN_TIMEOUT=5
    #GRUB_HIDDEN_TIMEOUT_QUIET=true
    # Uncomment to use basic console
    GRUB_TERMINAL_INPUT=console
    # Uncomment to disable graphical terminal
    #GRUB_TERMINAL_OUTPUT=console
    # The resolution used on graphical terminal
    # note that you can use only modes which your graphic card supports via VBE
    # you can see them in real GRUB with the command `vbeinfo'
    GRUB_GFXMODE=auto
    # Uncomment to allow the kernel use the same resolution used by grub
    GRUB_GFXPAYLOAD_LINUX=keep
    # Uncomment if you want GRUB to pass to the Linux kernel the old parameter
    # format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
    #GRUB_DISABLE_LINUX_UUID=true
    # Uncomment to disable generation of recovery mode menu entries
    GRUB_DISABLE_RECOVERY=true
    # Uncomment and set to the desired menu colors. Used by normal and wallpaper
    # modes only. Entries specified as foreground/background.
    #GRUB_COLOR_NORMAL="light-blue/black"
    #GRUB_COLOR_HIGHLIGHT="light-cyan/blue"
    # Uncomment one of them for the gfx desired, a image background or a gfxtheme
    #GRUB_BACKGROUND="/path/to/wallpaper"
    #GRUB_THEME="/path/to/gfxtheme"
    # Uncomment to get a beep at GRUB start
    #GRUB_INIT_TUNE="480 440 1"
    #GRUB_SAVEDEFAULT="true"
    No sucess. Any help?
    Last edited by joseribeiro (2014-06-11 12:15:30)

    I disagree.
    I don't need to run mkinitcpio -p linux if I ran plymouth-set-default-theme -R solar.
    See the following terminal output:
    # mkinitcpio -p linux
    ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
    -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
    ==> Starting build: 3.14.6-1-ARCH
    -> Running build hook: [base]
    -> Running build hook: [udev]
    -> Running build hook: [plymouth]
    -> Running build hook: [autodetect]
    -> Running build hook: [modconf]
    -> Running build hook: [block]
    -> Running build hook: [filesystems]
    -> Running build hook: [keyboard]
    -> Running build hook: [fsck]
    -> Running build hook: [nvidia]
    Building nvidia modules for 3.14.6-1-ARCH kernel...
    Module nvidia/337.25 already installed on kernel 3.14.6-1-ARCH/x86_64
    Ok.
    ==> Generating module dependencies
    ==> Creating gzip initcpio image: /boot/initramfs-linux.img
    ==> Image generation successful
    ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
    -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
    ==> Starting build: 3.14.6-1-ARCH
    -> Running build hook: [base]
    -> Running build hook: [udev]
    -> Running build hook: [plymouth]
    -> Running build hook: [modconf]
    -> Running build hook: [block]
    ==> WARNING: Possibly missing firmware for module: aic94xx
    ==> WARNING: Possibly missing firmware for module: smsmdtv
    -> Running build hook: [filesystems]
    -> Running build hook: [keyboard]
    -> Running build hook: [fsck]
    -> Running build hook: [nvidia]
    Building nvidia modules for 3.14.6-1-ARCH kernel...
    Module nvidia/337.25 already installed on kernel 3.14.6-1-ARCH/x86_64
    Ok.
    ==> Generating module dependencies
    ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
    ==> Image generation successful
    # plymouth-set-default-theme -R solar
    ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
    -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
    ==> Starting build: 3.14.6-1-ARCH
    -> Running build hook: [base]
    -> Running build hook: [udev]
    -> Running build hook: [plymouth]
    -> Running build hook: [autodetect]
    -> Running build hook: [modconf]
    -> Running build hook: [block]
    -> Running build hook: [filesystems]
    -> Running build hook: [keyboard]
    -> Running build hook: [fsck]
    -> Running build hook: [nvidia]
    Building nvidia modules for 3.14.6-1-ARCH kernel...
    Module nvidia/337.25 already installed on kernel 3.14.6-1-ARCH/x86_64
    Ok.
    ==> Generating module dependencies
    ==> Creating gzip initcpio image: /boot/initramfs-linux.img
    ==> Image generation successful
    ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
    -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
    ==> Starting build: 3.14.6-1-ARCH
    -> Running build hook: [base]
    -> Running build hook: [udev]
    -> Running build hook: [plymouth]
    -> Running build hook: [modconf]
    -> Running build hook: [block]
    ==> WARNING: Possibly missing firmware for module: aic94xx
    ==> WARNING: Possibly missing firmware for module: smsmdtv
    -> Running build hook: [filesystems]
    -> Running build hook: [keyboard]
    -> Running build hook: [fsck]
    -> Running build hook: [nvidia]
    Building nvidia modules for 3.14.6-1-ARCH kernel...
    Module nvidia/337.25 already installed on kernel 3.14.6-1-ARCH/x86_64
    Ok.
    ==> Generating module dependencies
    ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
    ==> Image generation successful
    They are equivalents.
    Last edited by joseribeiro (2014-06-10 18:37:29)

  • Mic/Remote on headset doesn't work correctly with my iPhones iPod

    Currently I'm using a third party headset because my original apple headset broke.. Sometimes when I first plug in the headset it'll automatically start playing music, fast forward songs, skip tracks, and randomly stop and start again. I usually solve this by unplugging the headset and plugging it back in. Once it has stopped doing all that mumbo jumbo with the iPod I can listen to music just fine but the mic/remote function doesn't work at all.. The mic doesn't work forsure because when I get called they cannot hear me.
    I troubleshooted with my boss's iPhone 3GS and tried my third party headset on her phone and it worked just fine mic/remote and all. So I took her original headset and plugged it into my iPhone to see if it was a problem with my phone and it worked just fine.. I hear about people saying lint may be the problem in the jack but I took an air compressor and cleared it out and vacuumed it and no lint was found..
    Anyone got any idea what could be the problem?? I really liked using my mic/remote so if anyone can help me out that would be great..

    Hi J&M,
    See these posts for suggested fixes:
    http://discussions.apple.com/thread.jspa?messageID=894936&#894936
    AND
    http://discussions.apple.com/thread.jspa?threadID=361771
    Good luck,
    Maz

  • Just upgraded to Yosemite, now Final Cut Pro doesn't work

    Hi I just upgraded to Yosemite 10.10 on a 2010 MacBook Pro, and the only major tool I use on there now doesn't work.... Final Cut Pro 10.0.9.
    The icon in the tray has a line through it and when you click on it, a panel opens advising that I can't use it because I have the wrong version. It doesn't advise what I should do. How can I get Final Cut Pro working again..... urgently!  I've seen a temporary fix somewhere on a forum which involves going in to applications and launching from somewhere deep in there, but not ideal. Whats the proper fix please and why would Apple allow something like this to happen without covering it? Its an apple product on an apple machine and Im a video producer and I have been let down with this...

    Thanks to all your lovely help, advice and support I have now found the purchases section of my App Store account and in the Purchases section is the offending NOT PIRATE! copy of FCPX and next to is a button which says INSTALL. I can only image that is the upgrade route - it doesnt say. I have now hit the install button and hopefully that will be it. Would I be correct in saying that Compressor also needs a similar upgrade or am I going to get abuse for asking that as well?

Maybe you are looking for