Compressor 4 to img to disk

Compressor 4 allows you to "burn" a disk image to your hard drive.  How do I burn a blu-ray disk image and then make a Blu-Ray disk?

Right click (control click) on the .img file and select "burn ... to disc"

Similar Messages

  • .dmg vs. .img--can't burn .img in Disk Utilities

    I know I've created .dmg files using iDVD before, but for some reason my last project created a .img file, an NDIF disk image, which I cannot use to burn DVDs from Disk Utiliity.
    Is this because I'm using an archived DVD project? When I go to File/Save as Disk Image, it defaults to a .img file. TIA.

    A .dmg file is created when you use a previously burned DVD disk to create the new image.
    A .img file is create when iDVD creates a disk image file from an iDVD project.
    You can use either one to burn to a DVD disk with Disk Utility. I have many saved disk images from both projects and disks and have burned each to a DVD disk without any problem.
    Have you tried doing a burn to disk in DU? Did you use a good brand of DVD-R disk like Verbatim or Maxell?
    And did you use a slow burn speed of 4x or less?
    You should be able to do this easily.

  • HT4775 I made a DVD in compressor and even though the disk is finished, I still see the active job.  How do I clear the job off the active jobs list?

    A few weeks ago, I launched compressor via FCPX to make a DVD.  Everything went fine.  The disc burned and ejected from my DVD burner, but the job is still listed under Active Jobs.  Nothing I've tried will make it go away.  Is there any way to clear that list?

    Go into your Home library and open Application Support and then Compressor. Open the History sub folder and within that, open V4. Scroll down to find the job and drag it to the trash.
    Russ

  • Hard Disk Repair Help!

    Good evening,
    Just wondering if you guys can give me any help with regards to my Mid 2010 Mac Mini running Mountain Lion.
    I only use the computer for internet browsing and iTunes, I've upgraded the RAM to 8GB myself which was straight forward.
    Yesterday I get home from work and the Mac is turned off (I usually leave it on Stand-By). Upon turning it on by the button on the back I get the Apple Logo and the rotating circle, followed by this screen;
    [IMG]http://i117.photobucket.com/albums/o78/Jonny2modified/6E058BF7-C5CC-4725-BB6E-64 D53168DAD8-11438-00000B443DCDE4DC_zps4a055f0a.jpg[/IMG]
    If I click on Disk Utility I've got these options on the left;
    [img]http://i117.photobucket.com/albums/o78/Jonny2modified/B1377C74-71DB-45B0-B700-11 77B06FC73D-11438-00000B4442D9F747_zps5208f360.jpg[/img]
    I've a 160GB external hard drive which has stuff on it now but could transfer that stuff over to a very old and slow laptop if I need the extra space for backing up.
    Verify Disk on the top drive gives me this, which looks fine?;
    [IMG]http://i117.photobucket.com/albums/o78/Jonny2modified/777713AF-708F-4723-B947-2B 9337725A74-11438-00000B444825DEFF_zps957f56f9.jpg[/IMG]
    But Disk Repair on the greyed out drive gives me this;
    [IMG]http://i117.photobucket.com/albums/o78/Jonny2modified/5A6FC9F4-79E9-44DB-ACF3-96 44F9631AEB-11438-00000B444DBBA0CE_zps46e5ea78.jpg[/IMG]
    Which doesn't sound good?
    The bad bit.. I've not backed up anything since I got the computer, I've got pictures/music on my computer I'd like to keep if possible.. But I don't know anything about backing things up, or how I'd go about it. Sounds pretty terminal from that pop-up message from Apple!
    I've got installation disks if I need them.
    So you helpful people - What do I need to do first?
    Thanks in advance!
    (Apologies about the bad pictures, thought it'd be better than nothing though!)

    Thanks so far, Viking.
    Tried to do the Shift or S key on boot up after/on the chime but nothing.
    Will try a wired keyboard tomorrow, will any USB keyboard work to you know? Can borrow one from work if so..
    EDIT;
    I appear to have got it into Single User Mode. Tried the fsck command, this is what I got back from that;
    http://i117.photobucket.com/albums/o78/Jonny2modified/19CDDA7A-43CF-4F3C-A4B7-22 BAA013BB53-12042-00000B863A4EDB71_zps64426d37.jpg
    Still started up in Disk Utility..
    If I try and install Lion again I get this;
    http://i117.photobucket.com/albums/o78/Jonny2modified/C2691425-5AA3-43B7-B354-58 F1F9AA199B-12042-00000B863E72ED34_zpsc5118a5e.jpg
    So, I guess it's dead?

  • Wrong colors on iDVD burned disk after FCut Pro installation

    Hi there:
    For some reason, after burning a DVD using the iDVD 5.0.1 software all I get is wrong colors when playing it in ANY DVD player. If I watch the very same disk on my G5 Mac, everything turns out ok!
    Is it a codec problem?? This problems sudenly began AFTER I installed the Final Cut Pro on my disk.
    How can this be explained by the Final Cut installation? And how can I get it right again?
    Any help on this would be highly apreciated, please!
    Thanks in advance!
    Rui.

    The images are pictured ok, but the colors are wrong. I have two DVD players at home:
    - When I play the DVD on an expensive Pionner DVD player, the reds turned into some sort of green, and the overall color range seems more «cold» (ie, more blue and greenish)
    - When I play the DVD on a cheap 20 dolars players, everything turns out black and white.
    It happens this way no matter if I use the NTSC or PAL preferences when burning.
    I also tryed to asve a .img to disk and burn it using the Disk Utility. Didnt work also.
    Ok, I'll try what you say about the external monitor
    Thanks for being around.
    Rui.

  • Compressor and Install Problems:

    I recently bought the lastest Macbook Pro with Lion. The Apple Store recommended I migrate my Applications rather than clean install as the installer for FCS wouldn't work with Lion.
    Compressor now has the greyed out submit button problem. I ran Compressor Repair, at some point it recognised my computer as a cluster, but then the actual batches would fail. Then it went back to not having my computer as a cluster again, and I can't refind it.
    Everything is greyed out within QMaster on System Prefs as well.
    The advice that I have read is to selectively trash Compressor and reinstall from the disks. But I see that I need something like Rosetta to install from the original FCS disks. And my old computer is on Leopard, 10.5.8 which I don't think I have the disk for anyhow, I think my basic Mac disk would be Tiger or whichever was before that. How do I get Compressor off and back onto my machine, and is there any fix to sort this out without having to go through all this? The issues I've had with FCS since getting this new system have really started to affect my work.
    With thanks in advance.

    Classic ignorance from the Apple Store.  Migrating applications is not a good idea and it can lead to these sorts of problems.
    First thing to try is deleting compressor preferences
    You can use Preference Manager to do this
    https://discussions.apple.com/docs/DOC-2491
    If you have the disks that came with your computer, you've got the OS install disks which will allow you to install Rosetta. 
    You could also try installing Rosetta off the Tiger Disk.

  • Does Motion Filtering setting affect Export Using Compressor?

    Hello!
    Can anyone tell me if my Motion Filtering setting in the video processing tab of my sequence settings has any effect on the ultimate quality of my export when using the "Export Using Compressor" command? I know it certainly would when exporting to Quicktime, but I'm wondering if it matters if I'm going directly to Compressor. I am sending a completely unrendered sequence.
    Thanks!
    Cameron

    Don't feel too bad. None of us can match what the big guys do with our software encoders and burners.
    They have the advantage of very expensive encoding hardware/software. They have tons of technical expertise (the so called black art of encoding). And they are working with source material that is expertly lighted, shot and graded. Then they physically stamp their disks, rather than relying on dyes.
    It's not a fair fight.
    But we can do a very decent job using FCP and/or Compressor and/or DVD Studio Pro and/or iDVD.  (I've seen – and made myself – some great looking DVDs by simply taking a ProRes 422 file into iDVD and choosing Professional Quality.)
    I always start with a Pro Res master file – either 422 or HQ, depending on the original material. When possible the frame rate and size are the same as what was shot.
    A Compressor>Create DVD or Compressor >DVD Studio Pro can produce superior results because you have more control over the process. Starting with the DVD stock preset, you adjust as necessary – bit rate and sometimes Frame Controls. So, for example, using Frame Controls you could reduce the chances of introducing artifacts in the down-convert from HD to SD by turning on the Resize Filter.
    Open up the Preview window. Set in and out points to encode a manageable length test file with he stock settings. Burn a test DVD directly from Compressor using a DVD-RW disk. If you like it, great. Make a disk image (select HD as output device in Job Actions) and burn. Or if you want better menus, use Toast,
    We're seeing less and less interlaced footage these days, but if working with a video intended for the Web or computer display, the video should be de-interlaced – again, in Frame Controls.
    Finally, buy good media like Verbatim.
    Good luck.
    Russ

  • FCP 10.0.1 update now crashes every time I launch it!

    FCP update now crashes every time I launch it! Won't even open a project I started last week with version 10.0.0.
    I have a deadline at work so I've now got a big problem! I'm trying to give the new and supposedly improved FCPX a shot but this app is turning out to be a real hack. What other professional video editing software do you guys use? Anyone use Premier Pro? I have Premier pro and think I should probably start my new projects in it. As I said....this app is a real mess.
    FYI: Same problem for my 1 year old MacBook Pro (8G ram, i7 processor) AND my Mac Pro (16G ram, 2 x 3GHz quad core processors, 4-1TB hardrives.

    I don't know who these friends are, but they're certainly misinformed and they don't appear to be doing you any favours.
    There are a great number of professional editors who have used Final Cut Pro since version 4 - but took the trouble to
    a.     Find out the system and install requirements for FCP X
    b.     Watch professional tutorials such as Ripple Training and actually LEARN how to use this ground breaking new application.
    They (and I) are having very few issues with FCP X - especially since the update.
    If you're getting crashes, autosave problems etc, there is more than likely some conflict on your system drive.
    Create a new (admin) user on your Mac system and try FCP X from there.
    I did this, and FCP X worked perfectly on the new account, meaning there was definitely a conflict on my existing system.
    To be absolutely certain my MacPro's system was squeaky clean, I then did a clean reinstall (not TimeMachine) and FCP X has worked reliably ever since.
    FCP X application should be in your Applications folder and ideally, your project and events should all be on an external HD and not on your Mac system drive.
    I have around 4000 clips distributed between six events at the moment and FCP X is coping very well most of the time.
    It helps to work without the waveforms displayed as these slow things down considerably.
    Do you have FC Studio or a version of FCP on the same drive partition as FCP X?
    This is what Apple say on their current web page on installation practice:
    "It is strongly recommended that you install Final Cut Pro X, Motion 5, and Compressor 4 on a startup disk that does not have Final Cut Studio (2009) already installed. Use Apple's preferred installation procedure when upgrading one version of Final Cut Pro or Final Cut Studio to the next. This procedure is not unique to Final Cut Pro X."
    They do go on to say "if you must" have the two on the same partition, FCS must be located in a different folder - but I would have thought the words "strongly recommended" and "if you must" speak for themselves.
    Andy

  • KVM VGA-Passthrough using the new vfio-vga support in kernel = 3.9

    This is intented for people who wish to pass-through a GPU to a virtual machine using the KVM hypervisor, QEMU and vfio-pci
    NOTE: AMD RADEON 5xxx, 6xxx, 7xxx, 2xx and NVIDIA GEFORCE 7, 8, 4xx, 5xx, 6xx, 7xx 9xx have been reported working with this, passing though an intel IGD is not supported YET
    NOTE: THIS IS EXPERIMENTAL SO IT MIGHT NOT WORK ON YOUR SYSTEM
    This is the result on my radeon 6950:
    This is the result on my geforce 470 gtx:
    Recommended reads
    Alex Williamson's blog and FAQ for detailed technical information
    OVMF whitepaper.
    GPU passthrough database by noctavian
    At this moment there are two ways to achieve this using KVM: legacy VGA via Seabios or non-VGA (UEFI) via OVMF
    The main practical advantage of using OVMF is that on intel systems you no longer need the i915 VGA arbiter patch which also disables DRI on the host
    Requirements
    AMD-VI/VT-D enabled and working (On intel systems both your MB and you CPU must support it, to find out if you CPU has VT-D support go here: http://ark.intel.com/, you also need to boot with intel_iommu=on to enable it)
    At least 2 GPU's, one primary boot device and the card you wish to pass-through
    Qemu=>2.0
    Aditional kernel patches might be required if you're using an Intel CPU: ACS override patch and i915 VGA arbiter patch, you can find a kernel package with these patches included on AUR: linux-vfio
    Aditional requirements for OVMF:
    An UEFI compatible GPU (Most modern gpus support this, SEE: Does my graphics card ROM support EFI?
    An UEFI compatible GUEST (ex: Windows 7 and up)
    OVMF:  Gerd Hoffmann's rpms or OVMF-svn from AUR
    If you're building your kernel manually this option is required:
    CONFIG_VFIO_PCI_VGA=y
    Preparing your System
    On intel system the i915 VGA arbiter patch is required if:
    You're using the IGD on your host
    You're doing VGA assignment
    NOTE: Enabling this will disable DRI!
    If you wish to avoid this, then then you should try OVMF
    To enable it add this kernel parameter to your bootloader:
    i915.enable_hd_vgaarb=1
    Next, we need to prepare the GPU for vfio:
    Blacklist radeon or nouveau or nvidia or fglrx on /etc/modprobe.d/blacklist.conf
    Example, blacklisting the opensource radeon module:
    echo "blacklist radeon" >> /etc/modprobe.d/blacklist.conf
    Use pci-stub
    In my case since i have 2 radeon cards blacklisting the radeon module is not an option, so i use pci-stub
    NOTE: If pci-stub was built as a module, you'll need to modify /etc/mkinitcpio.conf and add pci-stub in the MODULES section, after that you need to update your initramfs like this
    mkinitcpio -p linux-mainline
    lspci
    07:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cayman PRO [Radeon HD 6950] <-- radeon 6950
    07:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cayman/Antilles HDMI Audio [Radeon HD 6900 Series] <-- radeon 6950 audio
    lspci -n
    07:00.0 0300: 1002:6719 <-- radeon 6950
    07:00.1 0403: 1002:aa80 <-- radeon 6950 audio
    Now add this kernel parameter to your bootloader:
    pci-stub.ids=1002:6719,1002:aa80
    dmesg | grep pci-stub
    [ 2.096151] pci-stub: add 1002:6719 sub=FFFFFFFF:FFFFFFFF cls=00000000/00000000
    [ 2.096160] pci-stub 0000:07:00.0: claimed by stub
    [ 2.096165] pci-stub: add 1002:AA80 sub=FFFFFFFF:FFFFFFFF cls=00000000/00000000
    [ 2.096174] pci-stub 0000:07:00.1: claimed by stub
    [ 2.096178] pci-stub: add 1B21:1042 sub=FFFFFFFF:FFFFFFFF cls=00000000/00000000
    Setting up vfio and kvm modules
    This is only required if you get this message:
    vfio_iommu_type1_attach_group: No interrupt remapping support. Use the module param "allow_unsafe_interrupts" to enable VFIO IOMMU support on this platform
    If your board doesn't enable interrupt remapping, you need to add this to your bootloader:
    vfio_iommu_type1.allow_unsafe_interrupts=1
    Or if vfio-pci was built as a module ( default on arch )
    echo "options vfio_iommu_type1 allow_unsafe_interrupts=1" > /etc/modprobe.d/vfio_iommu_type1.conf
    Some applications like Passmark Performance Test and SiSoftware Sandra crash the VM without this:
    echo "options kvm ignore_msrs=1" >> /etc/modprobe.d/kvm.conf
    Binding a device to vfio-pci
    We'll use this script to make life easier:
    #!/bin/bash
    modprobe vfio-pci
    for dev in "$@"; do
    vendor=$(cat /sys/bus/pci/devices/$dev/vendor)
    device=$(cat /sys/bus/pci/devices/$dev/device)
    if [ -e /sys/bus/pci/devices/$dev/driver ]; then
    echo $dev > /sys/bus/pci/devices/$dev/driver/unbind
    fi
    echo $vendor $device > /sys/bus/pci/drivers/vfio-pci/new_id
    done
    Save it as /usr/bin/vfio-bind
    chmod 755 /usr/bin/vfio-bind
    Bind the GPU and GPU audio:
    vfio-bind 0000:07:00.0 0000:07:00.1
    Systemd service:
    [Unit]
    Description=Binds devices to vfio-pci
    After=syslog.target
    [Service]
    EnvironmentFile=-/etc/vfio-pci.cfg
    Type=oneshot
    RemainAfterExit=yes
    ExecStart=-/usr/bin/vfio-bind $DEVICES
    [Install]
    WantedBy=multi-user.target
    cat /etc/vfio-pci.cfg
    DEVICES="0000:00:11.0 0000:04:00.0 0000:05:00.0 0000:06:00.0 0000:07:00.0 000:07:00.1"
    Testing if its working out
    Seabios:
    qemu-system-x86_64 -enable-kvm -m 1024 -cpu host,kvm=off \
    -smp 4,sockets=1,cores=4,threads=1 \
    -device vfio-pci,host=07:00.0,x-vga=on -device vfio-pci,host=07:00.1 \
    -vga none
    OVMF:
    qemu-system-x86_64 -enable-kvm -m 1024 -cpu host,kvm=off  \
    -smp 4,sockets=1,cores=4,threads=1 \
    -drive if=pflash,format=raw,readonly,file=/usr/share/ovmf/x64/ovmf_code_x64.bin \
    -drive if=pflash,format=raw,file=/usr/share/ovmf/x64/ovmf_vars_x64.bin \
    -device vfio-pci,host=07:00.0 -device vfio-pci,host=07:00.1 \
    -vga none
    Note:
    kvm=off will hide the kvm hypervisor signature, this is required for NVIDIA cards, since its driver will refuse to work on an hypervisor and result in Code 43 on windows (unless you're using a QUADRO)
    x-vga=on is required for vga assignment
    -vga none disables the default vga device on QEMU, it is also required for vga assignment
    You should see a black qemu window on your main display, and seabios/ovmf ouput on your monitor from your passthru'd card saying it cant find anything to boot
    If you're using an intel cpu and nothing happens try this:
    modprobe -r kvm_intel
    modprobe kvm_intel emulate_invalid_guest_state=0
    NOTE: There might be some problems using nvidia/fglrx/nouveau drivers on the host gpu, see the ISSUES section below on how to solve this
    At this point you're ready to create your vm, you could use libvirt + virt-manager to create your vm using a nice graphical interface, there are
    also some interesting examples in this thread, otherwise if you prefer to use the command line continue reading
    DISK:
    Creating a disk image:
    Create a 30Gb raw image:
    dd if=/dev/zero of=windows.img bs=1M seek=30000 count=0
    Using a VIRTIO controller:
    We create our virtio controller for qemu:
    -device virtio-scsi-pci,id=scsi
    Attaching our hdd:
    -drive file=/home/nbhs/windows.img,id=disk,format=raw,if=none -device scsi-hd,drive=disk
    Attaching a cdrom:
    -drive file=/home/nbhs/windows.iso,id=isocd,if=none -device scsi-cd,drive=isocd
    To install windows, you'll need to download the virtio drivers iso from here
    Attaching the virtio iso:
    -drive file=/home/nbhs/virtio.iso,id=virtiocd,if=none -device ide-cd,bus=ide.1,drive=virtiocd
    Windows will complain it cant find a disk to install to, just click browse, find the folder for your os/arch, select "RED HAT VirtIO pass-through controller" then click next.
    For more info check out the Archlinux wiki's QEMU section
    Using a physical disk or partition:
    -drive file=/dev/sdb,id=disk,format=raw,if=none -device scsi-hd,drive=disk
    You might need to change the bus depending on the controller you use
    If you wish to use a physical partition and be able to read its contents later on, you can follow these guides:
    http://fds-team.de/cms/articles/2013-12 … yer-u.html
    https://wiki.archlinux.org/index.php/QE … disk_image
    Passing a sata disk controller to qemu:
    If you dual boot like me you can pass an entire sata controller (in ahci mode) and all the drives attached, and seabios will boot from them.
    lspci
    00:11.0 SATA controller: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] (rev 40)
    Make sure all volumes are unmounted, then bind the controller to vfio:
    vfio-bind 0000:00:11.0
    Now we pass the controller to the vm:
    -device vfio-pci,host=00:11.0
    USB:
    Its also possible to passthrough a usb controller, in my case an ASMEDIA USB3 Controller:
    lspci
    04:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller
    05:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller
    06:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller
    Bind them to vfio:
    vfio-bind 0000:04:00.0 0000:05:00.0 0000:06:00.0
    Pass them to the vm:
    -device vfio-pci,host=04:00.0 \
    -device vfio-pci,host=05:00.0 \
    -device vfio-pci,host=06:00.0
    Or a specific device:
    lsusb
    Bus 004 Device 010: ID 045e:00e1 Microsoft Corp. Wireless Laser Mouse 6000 Reciever <-- mouse
    Bus 004 Device 011: ID 045e:074b Microsoft Corp. <-- keyboard
    We pass them to the vm:
    -usb -usbdevice host:045e:00e1 -usbdevice host:045e:074b
    NETWORK:
    Please see https://wiki.archlinux.org/index.php/QEMU#Networking
    AUDIO EMULATION:
    To hear the sound from the vm on your host speakers you'll need to add this lines:
    -soundhw hda
    You might need to start qemu like this:
    QEMU_PA_SAMPLES=128 QEMU_AUDIO_DRV=pa qemu-system-x86_64...
    alsa:
    QEMU_ALSA_DAC_BUFFER_SIZE=512 QEMU_ALSA_DAC_PERIOD_SIZE=170 QEMU_AUDIO_DRV=alsa qemu-system-x86_64...
    Note: these are the settings i found that work great on my system, if you get crackling/skipping audio you might want to try different settings
    To see the available drivers and audio options:
    qemu-system-x86_64 -audio-help
    LOADING YOUR CARD ROM FROM A DUMP/FILE:
    modify this line:
    -device vfio-pci,host=07:00.0,...... \
    change it to this:
    -device vfio-pci,host=07:00.0,......,romfile=/path/to/your/gpu/bios.bin \
    ISSUES:
    Using the latest NVIDIA drivers on the guest will result in code 43, but there's a workarround
    Using the latest NVIDIA drivers on the guest using hv enlightenments will result in code 43, see: https://forums.geforce.com/default/topi … 8/#4314318
    Using AMD proprieraty drivers on the host, see: https://bbs.archlinux.org/viewtopic.php … 2#p1273412 the only solution atm is using the opensource radeon driver
    PERFORMANCE IMPROVEMENTS:
    SEE: https://bbs.archlinux.org/viewtopic.php … 1#p1270311
    Pin vcpu to pcpu, see http://www.linux-kvm.com/content/tip-ru … cific-cpus
    Use cgroups, specifically cpuset, see https://access.redhat.com/site/document … puset.html
    Use Hugepages, see http://pic.dhe.ibm.com/infocenter/lnxin … ttunhp.htm
    Use Hyper-V enlightenments, see: http://blog.wikichoon.com/2014/07/enabl … h-kvm.html
    Last edited by nbhs (2015-04-05 20:01:18)

    nbhs wrote:
    apoapo wrote:
    I finally got some progress.
    After trying mainline kernel and with vbios, I went to bios/uefi and turned the Primary VGA card from onboard to pci-express ...
    Now I see the seabios in passthroughed screen, but with blinking cursor in it, so i will try some things .
    NIce! have you tried running windows with it yet? does it work if you dont load the rom file by hand?
    Hi,
    I tried it again and I captured this error message if I use the PCI-e card es Primary Card:
    qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: VFIO 0000:01:00.0 BAR 0 mmap unsupported. Performance may be slow
    This was, when I got some seabios picture.
    After some reboots I wanted to try it again, I was spammed with errors . Dont have them to show you now...  will look for it.
    Now I'm With the onboard as primary Card and I found this in dmesg:
    [ 0.401391] DMAR: No ATSR found
    [ 0.401412] IOMMU 0 0xfed90000: using Queued invalidation
    [ 0.401413] IOMMU 1 0xfed91000: using Queued invalidation
    [ 0.401415] IOMMU: Setting RMRR:
    [ 0.401422] IOMMU: Setting identity map for device 0000:00:02.0 [0xbf800000 - 0xcf9fffff]
    [ 0.402590] IOMMU: Setting identity map for device 0000:00:1d.0 [0xbd568000 - 0xbd59afff]
    [ 0.402606] IOMMU: Setting identity map for device 0000:00:1a.0 [0xbd568000 - 0xbd59afff]
    [ 0.402619] IOMMU: Setting identity map for device 0000:00:14.0 [0xbd568000 - 0xbd59afff]
    [ 0.402628] IOMMU: Prepare 0-16MiB unity mapping for LPC
    [ 0.402635] IOMMU: Setting identity map for device 0000:00:1f.0 [0x0 - 0xffffff]
    [ 0.402717] PCI-DMA: Intel(R) Virtualization Technology for Directed I/O
    [ 0.402782] ------------[ cut here ]------------
    [ 0.402786] WARNING: at drivers/pci/search.c:46 pci_find_upstream_pcie_bridge+0x83/0x90()
    [ 0.402787] Hardware name: To Be Filled By O.E.M.
    [ 0.402788] Modules linked in:
    [ 0.402790] Pid: 1, comm: swapper/0 Not tainted 3.9.2-1-mainline #1
    [ 0.402791] Call Trace:
    [ 0.402796] [<ffffffff81058090>] warn_slowpath_common+0x70/0xa0
    [ 0.402797] [<ffffffff8105817a>] warn_slowpath_null+0x1a/0x20
    [ 0.402799] [<ffffffff8129ea43>] pci_find_upstream_pcie_bridge+0x83/0x90
    [ 0.402802] [<ffffffff813b3c7b>] intel_iommu_add_device+0x4b/0x1f0
    [ 0.402805] [<ffffffff813ab630>] ? bus_set_iommu+0x50/0x50
    [ 0.402806] [<ffffffff813ab65a>] add_iommu_group+0x2a/0x50
    [ 0.402809] [<ffffffff8135bf63>] bus_for_each_dev+0x63/0xa0
    [ 0.402811] [<ffffffff813ab622>] bus_set_iommu+0x42/0x50
    [ 0.402814] [<ffffffff819130b6>] intel_iommu_init+0xa83/0xb7b
    [ 0.402816] [<ffffffff818dd10b>] ? memblock_find_dma_reserve+0x124/0x124
    [ 0.402818] [<ffffffff818dd11d>] pci_iommu_init+0x12/0x3c
    [ 0.402820] [<ffffffff8100210a>] do_one_initcall+0x10a/0x160
    [ 0.402823] [<ffffffff818d5037>] kernel_init_freeable+0x15b/0x1dc
    [ 0.402824] [<ffffffff818d4881>] ? do_early_param+0x88/0x88
    [ 0.402827] [<ffffffff814b55f0>] ? rest_init+0x90/0x90
    [ 0.402828] [<ffffffff814b55fe>] kernel_init+0xe/0x190
    [ 0.402830] [<ffffffff814dad6c>] ret_from_fork+0x7c/0xb0
    [ 0.402832] [<ffffffff814b55f0>] ? rest_init+0x90/0x9

  • Transparency in png image not showing

    Hello,
    I have a Region, which needs a background and an image 'on top' of it.
    I can set the background using
    setStyle("-fx-background-color: #" + 123456 + ";");
    Or I can just use a Rectangle of that colour.
    Then I have an ImageView...   spiralImgView = new ImageView(new Image("images/spiral2.png"));
    The png image itself has some transparency in it.
    So when I add them to the region...
    this.getChildren().addAll(rect, spiralImgView);
    I just get a white background showing behind the image.
    Can anyone help me fix this?
    Thanks

    I didn't do any coding.  This will tell you if it is your image:
    1)  Download and start JavaFX Scene Builder
    2)  Without making any changes paste "-fx-background-color: #1d1d1d;" into the "Style" box of the "Properties" window
    3)  Drag and drop an Image View into the scene from the "Library" window.
    4)  Click on the ImageView in the "Hierarchy" window.
    5)  In the "Properties" window Use the "Image" selector to find your img on disk
    If your image is mostly transparent it's background will not be white but #1d1d1d

  • [Solved] Kernel failed to re-read the partition for Udisk

    re-produce procedure
    * plug a udisk
    * use `fidsk` to partition the disk `fdisk /dev/sdb`
    * save the partition. Error will raise.
    Here is the error raised by fdisk
    Disk /dev/sdb: 3.7 GiB, 3974103040 bytes, 7761920 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: dos
    Disk identifier: 0x2dfbdb2a
    Command (m for help): n
    Partition type
    p primary (0 primary, 0 extended, 4 free)
    e extended (container for logical partitions)
    Select (default p): p
    Partition number (1-4, default 1):
    First sector (2048-7761919, default 2048):
    Last sector, +sectors or +size{K,M,G,T,P} (2048-7761919, default 7761919):
    Created a new partition 1 of type 'Linux' and of size 3.7 GiB.
    Command (m for help): w
    The partition table has been altered.
    Calling ioctl() to re-read partition table.
    Re-reading the partition table failed.: Success
    The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8).
    Syncing disks.
    When use the kpartx to re-read the partition, it still raise error
    # sudo kpartx -a -s /dev/sdb
    device-mapper: reload ioctl on sdb1 failed: Invalid argument
    create/reload failed on sdb1
    following is the error message when run strace
    # sudo strace kpartx -a -s /dev/sdb
    open("/etc/udev/udev.conf", O_RDONLY|O_CLOEXEC) = 4
    fstat(4, {st_mode=S_IFREG|0644, st_size=49, ...}) = 0
    mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f2f5cff0000
    read(4, "# see udev.conf(5) for details\n\n"..., 4096) = 49
    read(4, "", 4096) = 0
    close(4) = 0
    munmap(0x7f2f5cff0000, 4096) = 0
    access("/run/udev/control", F_OK) = 0
    open("/dev/urandom", O_RDONLY) = 4
    read(4, "\v~", 2) = 2
    semget(0xd4d7e0b, 1, IPC_CREAT|IPC_EXCL|0600) = 1179649
    semctl(1179649, 0, SETVAL, 0x1) = 0
    semctl(1179649, 0, GETVAL, 0xffffffffffffffff) = 1
    close(4) = 0
    semop(1179649, {{0, 1, 0}}, 1) = 0
    semctl(1179649, 0, GETVAL, 0xffffffffffffffff) = 2
    ioctl(3, DM_DEV_CREATE, 0xf4ff30) = 0
    ioctl(3, DM_TABLE_LOAD, 0xf4ff10) = -1 EINVAL (Invalid argument)
    write(2, "device-mapper: reload ioctl on s"..., 60device-mapper: reload ioctl on sdb1 failed: Invalid argument) = 60
    write(2, "\n", 1
    But if you unplug the disk and plug the disk again. The partition is re-read and I can see the sdb1.
    My system is the latest ( 2015-4-14 ).
    Did anybody meet this error and tell me how to fix it ? Thanks a lot.
    Last edited by Jeffrey4l (2015-04-30 02:01:35)

    alphaniner wrote:
    Jeffrey4l wrote:
    Actually, I first meet this issue by following step.
    * qemu-img create disk 10G
    * qemu-nbd -c /dev/nbd0 disk
    * fdisk /dev/nbd0
    write the partition table and raise the above error.
    I don't get any error when writing the table to an nbd.
    It's probably not relevant, but I load the nbd module manually with "modprobe nbd nbds_max=2 max_part=4"
    I really load that module.
    I also tried losetup file, it also raised error when write the partition info.
    So i think whether i forget some module or service which is used by hot re-partition.

  • Creating a blu-ray

    I am looking into purchasing an external blu-ray burner. One thing the company told me whose product I am interested in is If I want
    the Blu-ray to play back on a normal Blu-ray player connected to a TV, like a typical commercial film on a Blu-ray disc, special Blu-ray
    authoring software is required. (They referenced the Compressor app is able to do this.)
    Is there a difference between burning to Blu-ray directly from Final Cut vs. exporting from Final Cut and using Compressor? Just trying to understand the difference, if any.
    Thank you.

    Parm4u wrote:
    Is there a difference between burning to Blu-ray directly from Final Cut vs. exporting from Final Cut and using Compressor? Just trying to understand the difference, if any.
    The difference is that in Compressor you have more control over the settings – adjusting bit rates, Frame Controls, fiilters, etc.
    They both use Compressor to encode and Create DIsk to make the disk. In the case of FCPX, Compressor and Create Disk are embedded apps.
    Russ

  • Can't update fcp 5.1 to 5.1.4

    final cut pro (5.1.4) stopped working on my office mac (dual 1.25 g4 running 10.5.6) so i deleted the fcs apps, the plists and receipts and reinstalled fcs and compressor from our original fcs disks. ran software update and it installed everything successfully except the fcp 5.1.4 update. if i repeat the process for just the 514 update it downloads the file but stalls at the 'checking packages' step then i get an error which reads "the update final cut pro update can't be installed. sorry an unexpected error occurred'.
    so i downloaded the 5.1.4 update from the apple site but launching that i hit an issue where i can't click on the install button after agreeing to the eula. if i click on the install location and reselect my boot drive i still see the install button greyed out.
    any suggestions?

    fixed it by downloading the excellent fcs remover application, running it then reinstalling everything.

  • How do I uninstall FCP X Trial (I want to purchase and re-install "properly")?

    I installed the FCP X Trial app and have decided to purchase and go forward with FCP X, but have some questions:
    I see from the Apple FCP installation best practices document (HT4722) that it's not advisable to install along with Studio (instructions I did not follow in my hasty installation the Trial version) and I know Larry Jordan has some alternative views on FCP X installation which sound good to me, so I think I'd really like to carefully remove (unistall) the Trial version without damaging my current Studio installation (which I want to retain). I will then proceed with a carful installation fo the purchased X apps (and have not yet completely decided on which path I will take with that.
    So how do I uninstall?
    And does anyone here have any thoughts on the best way to install X given that:
    1. I will continue using both X and Studio (but of course won't run them at the same time). I simply cannot divorce myself from Studio completely, but want to start using X in certain projects that are conducive to it.
    2. I do NOT wish to do any partitioning (hate partitions).
    Thanks!
    -Dave

    Unlike the old FCP 7 there is no mystery about uninstalling FCP X.
    Simply drag the application to the trash and delete it.
    To install FCP X and FCS on the same disk (and partition) read the last 2 sections of this Apple Fact Sheet. (You didn't read far enough through it).
    http://support.apple.com/kb/HT4722
    Which method you use depends on which item you wish to have put in its own folder.
    Both methods work perfectly.
    Just to avoid any misunderstanding these are the titles of the 2 pertinent sections:-
    Install Final Cut Pro X, Motion 5, or Compressor 4 on the same disk as Final Cut Studio (2009)
    Restore the Final Cut Studio (2009) applications to their original location
    Message was edited by: Ian R. Brown

  • Error in encoding then.....

    hi. i made my project in iDVD with an apple theme. upon trying to burn however it says there is an error during encoding with menus/slideshows. so i followed the advice i found in another post saying to save as a disk image and burn using the img with disk utility, however! when i did that, my dvd was really diminished in quality and a few of the slideshows didnt even work. ?? even though they work fine in the preview in iDVD.

    You did not say if your slide shows were made within iDVD slideshow pane or made from iMovie or iPhoto into a QT file.
    I have had many problems as well with QT slide show.
    I have discovered that iDVD5 did not like the QT slideshow. So I ended up burning with iDVD4.
    you can read the following links relating to my problems.
    http://discussions.apple.com/thread.jspa?threadID=688655&tstart=0
    and to isolate the problem files that iDVD5 hangs up on, read my reply to Jack in this trhead
    http://discussions.apple.com/message.jspa?messageID=3378713#3378713
    it did quit during encoding the "menus slideshows"
    When you isolate the problem file, you might have to re-import it into iMovie and re-export it. or re-export from iPHoto, if it was the case
    read on
    michel

Maybe you are looking for

  • Mini-DVI to Video adapter + Widescreen CRT Television problem...

    The problem is that in the resolution list in Display-tab for the second display, which is PAL TV, have no resolutions for WIDESCREEN TV. Only resolutions are 640x480, 720x480, 720x576, 800x600 and 1024x768. Is this a OS related or is there different

  • All Purchase made from Apple TV will not transfer back to iTunes

    After I had purchase movies, and TV shows, they just stay on the Apple TV. I was not able to transfer them into the iTunes. I tried to transfer these movie or TV shows purchase by Selecting from iTunes File->Transfer Files from Apple TV, but it faile

  • ITunes Refuses to Add Certain Songs

    I've been reluctantly using iTunes ever since I got an iPod and have been having a number of problems. The most recent is that iTunes will simply refuse to add certain songs. My entire 35 gig library is unprotected MP3's and in this case, I have a fo

  • Disable partner item pop-up screen

    Hi all, I do have a requirement for Transaction VA01 and VA02. When a Sales Order is created, and I opened that Sales Order via VA02, I wish to grey-off the entire fields of partner's address screen. The partner's screen can be reached via VA02 -> He

  • Problems when i try to run a WebI query on top of a BW query

    Hi, people, All the time i try to run a query in WebIntelligence on top of a BW Query it raises the error message "A database error ocurred. The database error text is: Unable to create a cube. The connection is not connected to a cube (WIS 10901)".