Live type - artifacts some times

I have a half dozen live type titles all developed from the same basic set of elements- only differeing in the language on the titlesThe first set i place weeks ago they are all fine, this week i simply copied them and pasted them in another area of the video i am working on and 2 out of 6 of them when rendered showed interlacing lines.
I deleted them and readded them directly - still interlace lines - anyone have any ideas about this?

When I upgraded to LiveType 2, I thought I could skip installing the LT media discs, after all the files are already installed, right. Afraid not -all my LT media was deleted. I dragged a few folders from my backup across, to find that they did not work in LT 2.
My conclusion:
The .afp files are only compatible with version 1.x of LiveType.
Version 2 must use the .ltlf files.
As to why some of your afp files work yet others don't, I'm am not sure.
Are you familiar with FontMaker (in LiveType's "File" menu)? Maybe that could be used to convert the afp files.

Similar Messages

Live Type crashes every time I try to use the "Place" function.

Everytime I try to use the Place command and import a graphic, Live Type just shuts down. How do I fix this?
Todd

That's interesting Todd. You're on 10.4.5, and "Place" selection crashes Live Type. I'm getting the same thing on 10.4.3, so upgrading the OS may not solve my problem. Plus I don't want to upgrade the OS in the middle of a project. Bad Idea!
However I have a second system with 10.4.5, and the "Place" and "Place movie" work fine. So for the time being I'm going to build th graphics there. A workaround, but it's a little cumbersome.
I tried rebooting, reparing permissions, deleting preferences for LT, but those didn't help.
My next step is to re-install LT only, but I don't want to do this until I output the project I'm working on. (It's two months in the making, and I don't want to mess anything up.) I know it's overly cautious, but there's too much at stake.
Mac G5 Mac OS X (10.4.3) 2Gig RAM, Kona 2, AttoUL3D
Mac G5 Mac OS X (10.4.3) 2Gig RAM, Kona 2, AttoUL3D
Mac G5 Mac OS X (10.4.3)

When I create billing some time it calls condtion type KOFI or KOFK

Hi Friends,
I need your help in case of FI-SD flow.
When I create billing document for same category
1) Material type
2) Sale org.
3) Plant
4) Division
5) Revenue cost element
Some time it calls condition type KOFI and in some material it calls KOFK. I don't why when the above category are same two different condition type are coming in different - 2 material.
Both condition types are assigned in our customization.
Basic question is that there is any configuration in material master or sd . who calls the condition type at the time of creating billing.
Regards
Kailash

Hi,
The use of Kofi or Kofk is dependant on the master data.
If a Cost assignment exists (eg WBS - element) KOFK is used.
If no assignment exists - KOFI is used.
Kind regards

While playing auiod/video in my hp pavillion some times rubbing type noise is coming.

HP PAVILION DM4 NOTE BOOK PC
S.NO.CNU0511DPQ
while playing auiod/video in my hp pavillion some times rubbing type noise is coming.
my system is getting restarted while restarting hard disk fail error is coming pl do the needful
Regards
Rajesh kumar
09676401400

Hi @vs93 ,
Thank you for visiting the HP Support Forums. I needed to edit your post and remove the Serial Number. In accordance with our Rules of Participation:
Protect privacy - yours and others'. Don't share anything about yourself that you would not want to see on a road-side billboard. Don't post contact or other personal information-your own or anyone else's-or any content that you receive in one-to-one communications without the author's consent. For example, don’t post your computer’s serial # or contact information publicly, and do not allow someone you don’t know to remotely take control of your computer.
If you need people to contact you directly, either ask them to send you a private message or subscribe to the thread so you will be notified when there are replies. You may also click on your name anywhere in the forum and you will be taken to your profile page, where you can find a list of threads you have participated in.
Sharing personal email addresses, telephone numbers, and last names is not allowed for your safety. If you have any questions feel free to send me a private message in reply.
Thank you
George
I work for HP

My mother buy one ipod for me,and now she give to me. Can i replace an ipod for an iphone locked to use only of United States? I'm from Brazil and i go to United States(Orlando) in November to live there some time.can i change the ipod to iphone so you c

My mother buy one ipod for me,and now she give to me.
Can i replace an ipod for an iphone locked to use only of United States?
I'm from Brazil and i go to United States(Orlando) in November to live there some time.can i change the ipod to iphone so you can use in the United States.

No.
There are no trade ins at all.
You would ahve to buy a new iphone if you want one.

Media Missing in Live Type File Error Message

So I just upgraded to FCE 3.5 and have been playing around with LIve Type.
Yesterday I succeeded in making some titles with textured backgrounds etc. and getting them into FC. Today, I can still make the titles in Live Type, but when I import them into FC I get this message, in front of a purplish background, on the icon in the FC browser and when I drag the thumbnail into the viewer.
Media Missing in LIve Type File.
I have gone into project properties in Live Type and checked the "render background" box. I have also moved my media sequences above the background divider in the time line.
Nothing shows up in FCE, not even my text. But if I do a title with only text it shows up. If I include a texture and some effects, it does not show up. I just tried it with effects only and they show up. So it appears that it is a texture media problem. As soon as I open the text/effect title and add a texture, it comes up with this error in FCE.
My files for live type are on an external hard drive. it mounts fine. I can see all my titles fine in Live Type. They render fine. But don't show up in FCE.
I am working on a MacBook.
Any help?

When I Render it it shows up, but only for a few seconds then it goes black for a few more seconds. This happens when I have my in and out points set in LT and check, render only between in and out points, it also happens when this box is not checked. So I don't get the full time of my title effect.
My problem is that I didn't have to render before, why do I have to go to the trouble to render now?
I don't have to render on my iMac, it just works there. No rendering or exporting required. ?
Dan

How to import layouts with live type and vectors?

I seem to have run into a stumper on basic AE workflow. I want to set up a workflow where I can lay out designs in one app, and then bring them into AE to animate, and fly the camera around. My intent is to do infographics like this: http://vimeo.com/25123730 (OK, well, not nearly that slick...yet)
The difficulty is, if I lay out my design in Photoshop, after I import it, it will let me convert the type to live type, but the vector shapes are all rasterized, and I can't get them as vectors. If I lay out in Illustrator, the shapes are all crisp vectors, but my type is rasterized! I'm thinking that there's something I have to be missing here.
What's the solution?

There's actually a very simple solution that I use all the time. You simply convert your type to outlines in illustrator. I do this kind of stuff at least once a month. That's the only way to go. A side benefit is that you get to work with much smaller file sizes and much faster rendering times when you're doing really big 3-D moves on a really big piece of artwork.
The only catch is that some typefaces do not convert to outlines very well. You just need to make sure by carefully examining the conversion.
Another trick is to duplicate the type layers before you convert them. I move all of the duplicated type to a separate layer that I keep at the bottom of the stack in case the client wants, and they always want, changes. That bottom layer is simply kept hidden.
If I really need to use a text animator on one of the lines, I will use the illustrator layer as a placeholder and just simply type in the word or words. Most of my designs do not involve heavy use of text animators. These tricks will work until After Effects has the ability to import LiveType from Illustrator or vector shapes from Photoshop.

Why does my rendered Live Type movie look bad

I created some lower thirds using Live Type, then I imported them into FCP. When I edit them onto my timeline it looks really bad (not sharp)...why?

njs21 wrote:
I did not realize the canvas shows a low res image. that is not too comforting though.
You're new, obviously. We all were at one time or another. Your Canvas is a small window inside the interface of your editing application running on a computer screen. You can think of it like the page preview function in Photoshop, it's an approximation; you won't really know what your page is going to look like till you print it. But with lots of experience, you begin to be able to predict what various filters and effects will look like on different types of paper stocks on different printers.
njs21 wrote:
When it is all done rendering and exporting it will be high res?
Maybe. Depends on how you've got your rendering settings sets set up. Generally, yes, if you read that part of the manual carefully and follow the steps. But you won't know till you've gone all the way to your output format and evaluated your work on your final media's display.
bogiesan

DVDSP and Live Type

I have a Menu Background created in Live Type that has some text effects and a texture background. I imported the Live Type file (.ipr) to DVDSP, set it as my menu background and added a "Play Video" button. In Live Type when you "play" the file its sharp, clear and fonts are smooth. When I play the Menu created with this file in DVDSP, the fonts are all "jiggy-jaggy" in both the viewer and the simulator.
Live Type file was created with NTSC 4:3 as the preference preset
DVDSP is set at NTSC and 4:3 display mode
I am at a loss as to how to correct this so the menu will display the same in both apps. I am new to FCSPro - so bear with me if this is something simple and stupid!
iMac 24 Intel Core 2 Duo Mac OS X (10.4.8)

Neither simple nor stupid...
Try exporting the footage out of live type as a .mov file and using that as your menu background. You can then add the 'Play' button and when the disc is built it should all get encoded to MPEG2.
I think the issue is how the live type file is being read - I have certainly been in the same position before and found that by using .mov from LT it all seemed much better.
You could also add the 'Play Video' text to the background in LT, then use a simple overlay made in photoshop to give you a button highlight (a single button on a menu will be selected by default as the menu plays, so the highlight would always show). If you do this then you can use QT to encode the background footage to MPEG2 and then use that as your menu... don't add any other items from the palette though, or else the background footage will get encoded a second time by DVDSP and look pretty bad.

Apply Style or Favorites options in Live Type?

Hello, just trying to figure out live type, and I have a question.
I am using it to create info graphics on a dvd presentation, and I am wondering:
Do I have to manually format each different line of text, or is there a way that I can save a set of formatting parameters (font, size, drop shadow settings, color) and apply a style to given text, or do I have to format each line every time. I looked in the manual, and searched this forum and didn't find anything helpful.
I can't believe there isn't a way to do it, but I can't find it. Maybe saving it as a LiveType (even though there is no motion or effects)?
Let me know what you think.
Thanks,
Ken

You've got a couple choices here.
You can always copy a text track...paste it on a new track and then change your text.
If you have a more involved and layered graphics you could also create a template.
To save your project as a template:
1 Place the project file (.ipr) in a folder in this location: /Library/Application Support/
LiveType/Templates.
2 Generate a short QuickTime movie of the project (with the same name but an
appropriate movie extension, such as .mov or .mp4).
Once you do this, the template will appear in the preview window of the
Template Browser.

I have two iPhones, one is a 4s and the other is a 3g. I have not used my 3g in some time now. I recently restored it but I cannot use it without a sim card, it says i have to "activate it."

I have two iPhones, one is a 4s and the other is a 3g. I have not used my 3g in some time now. I recently restored it but I cannot use it without a sim card, it says i have to "activate it." I cannot place my iPhone 4s sim card in it (too small), and i do not want to get a new contract or sim card for an iPhone that i do not ues very much.

Thanks for your help, but i cannot borrow a noral sim card now, my family has all up graded to iPhone 4s's, i have done this before, but one of my family had the same type of iphone so i could use theirs. Now i am the only one who still holds on to their old phone... I am not sure about buying an adapter...

[SOLVED] Getting freezes after using dwm for some time and exiting it

Hello, I have an Asus Ux51, with a fresh (less than a month) arch installation. If I recall correctly I had a couple of freezes in other occasions but I don't remember much about those so I rather focus on the only freeze I can more or less reproduce and I've been having lately. After using dwm for some time with a couple of programs opened (rTorrent, browser, and some terminals for instance), if I close dwm or just press the power button to shut down, it starts closing everything and either stays with a black screen, or hangs while X prints the log information. It's not always though, for example, if I just boot it, open dwm and close it without giving it much use it usually closes fine.
Tried googling a bit to see the usual ways to troubleshoot this but didn't get really far.
This is my /var/log/Xorg.0.log
[ 7.573]
X.Org X Server 1.14.2
Release Date: 2013-06-25
[ 7.573] X Protocol Version 11, Revision 0
[ 7.573] Build Operating System: Linux 3.9.7-1-ARCH x86_64
[ 7.574] Current Operating System: Linux arch 3.10.3-1-ARCH #1 SMP PREEMPT Fri Jul 26 11:26:59 CEST 2013 x86_64
[ 7.574] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=74e92d67-41b6-4911-8ceb-009ae8c9cdab ro quiet add_efi_memmap i915.i915_enable_rc6=1 pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 "acpi_osi=!Windows 2012"
[ 7.574] Build Date: 01 July 2013 10:48:42AM
[ 7.574]
[ 7.574] Current version of pixman: 0.30.0
[ 7.574] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 7.574] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 7.574] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Aug 10 19:08:34 2013
[ 7.574] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 7.575] (==) No Layout section. Using the first Screen section.
[ 7.575] (==) No screen section available. Using defaults.
[ 7.575] (**) |-->Screen "Default Screen Section" (0)
[ 7.575] (**) | |-->Monitor "<default monitor>"
[ 7.575] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 7.575] (==) Automatically adding devices
[ 7.575] (==) Automatically enabling devices
[ 7.575] (==) Automatically adding GPU devices
[ 7.578] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 7.578] Entry deleted from font path.
[ 7.578] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 7.578] Entry deleted from font path.
[ 7.578] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 7.578] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 7.578] Entry deleted from font path.
[ 7.578] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 7.578] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/
[ 7.578] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 7.578] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 7.578] (II) Loader magic: 0x7fdc20
[ 7.578] (II) Module ABI versions:
[ 7.578] X.Org ANSI C Emulation: 0.4
[ 7.578] X.Org Video Driver: 14.1
[ 7.578] X.Org XInput driver : 19.1
[ 7.578] X.Org Server Extension : 7.0
[ 7.578] (II) xfree86: Adding drm device (/dev/dri/card1)
[ 7.579] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 7.580] (--) PCI:*(0:0:2:0) 8086:0166:1043:15a7 rev 9, Mem @ 0xf7400000/4194304, 0xd0000000/268435456, I/O @ 0x0000f000/64
[ 7.580] (--) PCI: (0:1:0:0) 10de:0fd1:1043:15a7 rev 161, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 7.580] Initializing built-in extension Generic Event Extension
[ 7.580] Initializing built-in extension SHAPE
[ 7.580] Initializing built-in extension MIT-SHM
[ 7.580] Initializing built-in extension XInputExtension
[ 7.580] Initializing built-in extension XTEST
[ 7.580] Initializing built-in extension BIG-REQUESTS
[ 7.580] Initializing built-in extension SYNC
[ 7.580] Initializing built-in extension XKEYBOARD
[ 7.580] Initializing built-in extension XC-MISC
[ 7.580] Initializing built-in extension SECURITY
[ 7.580] Initializing built-in extension XINERAMA
[ 7.580] Initializing built-in extension XFIXES
[ 7.580] Initializing built-in extension RENDER
[ 7.581] Initializing built-in extension RANDR
[ 7.581] Initializing built-in extension COMPOSITE
[ 7.581] Initializing built-in extension DAMAGE
[ 7.581] Initializing built-in extension MIT-SCREEN-SAVER
[ 7.581] Initializing built-in extension DOUBLE-BUFFER
[ 7.581] Initializing built-in extension RECORD
[ 7.581] Initializing built-in extension DPMS
[ 7.581] Initializing built-in extension X-Resource
[ 7.581] Initializing built-in extension XVideo
[ 7.581] Initializing built-in extension XVideo-MotionCompensation
[ 7.582] Initializing built-in extension XFree86-VidModeExtension
[ 7.583] Initializing built-in extension XFree86-DGA
[ 7.583] Initializing built-in extension XFree86-DRI
[ 7.584] Initializing built-in extension DRI2
[ 7.584] (II) LoadModule: "glx"
[ 7.585] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 7.586] (II) Module glx: vendor="X.Org Foundation"
[ 7.586] compiled for 1.14.2, module version = 1.0.0
[ 7.586] ABI class: X.Org Server Extension, version 7.0
[ 7.586] (==) AIGLX enabled
[ 7.587] Loading extension GLX
[ 7.587] (==) Matched intel as autoconfigured driver 0
[ 7.587] (==) Matched nouveau as autoconfigured driver 1
[ 7.587] (==) Matched nvidia as autoconfigured driver 2
[ 7.587] (==) Matched nv as autoconfigured driver 3
[ 7.587] (==) Matched intel as autoconfigured driver 4
[ 7.587] (==) Matched vesa as autoconfigured driver 5
[ 7.587] (==) Matched modesetting as autoconfigured driver 6
[ 7.587] (==) Matched fbdev as autoconfigured driver 7
[ 7.587] (==) Assigned the driver to the xf86ConfigLayout
[ 7.587] (II) LoadModule: "intel"
[ 7.588] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 7.592] (II) Module intel: vendor="X.Org Foundation"
[ 7.592] compiled for 1.14.2, module version = 2.21.12
[ 7.592] Module class: X.Org Video Driver
[ 7.592] ABI class: X.Org Video Driver, version 14.1
[ 7.592] (II) LoadModule: "nouveau"
[ 7.592] (WW) Warning, couldn't open module nouveau
[ 7.592] (II) UnloadModule: "nouveau"
[ 7.592] (II) Unloading nouveau
[ 7.592] (EE) Failed to load module "nouveau" (module does not exist, 0)
[ 7.592] (II) LoadModule: "nvidia"
[ 7.592] (WW) Warning, couldn't open module nvidia
[ 7.592] (II) UnloadModule: "nvidia"
[ 7.592] (II) Unloading nvidia
[ 7.592] (EE) Failed to load module "nvidia" (module does not exist, 0)
[ 7.592] (II) LoadModule: "nv"
[ 7.592] (WW) Warning, couldn't open module nv
[ 7.592] (II) UnloadModule: "nv"
[ 7.592] (II) Unloading nv
[ 7.592] (EE) Failed to load module "nv" (module does not exist, 0)
[ 7.592] (II) LoadModule: "vesa"
[ 7.593] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 7.593] (II) Module vesa: vendor="X.Org Foundation"
[ 7.593] compiled for 1.14.0, module version = 2.3.2
[ 7.593] Module class: X.Org Video Driver
[ 7.593] ABI class: X.Org Video Driver, version 14.1
[ 7.593] (II) LoadModule: "modesetting"
[ 7.593] (WW) Warning, couldn't open module modesetting
[ 7.593] (II) UnloadModule: "modesetting"
[ 7.593] (II) Unloading modesetting
[ 7.593] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 7.593] (II) LoadModule: "fbdev"
[ 7.593] (WW) Warning, couldn't open module fbdev
[ 7.593] (II) UnloadModule: "fbdev"
[ 7.593] (II) Unloading fbdev
[ 7.593] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 7.593] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server,
Ivybridge Server (GT2), HD Graphics, HD Graphics 4600,
Haswell Desktop (GT3), HD Graphics, HD Graphics 4600,
Haswell Mobile (GT3), HD Graphics, HD Graphics P4600/P4700,
Haswell Server (GT3), Haswell (GT1), Haswell (GT2), Haswell (GT3),
HD Graphics, Haswell (GT2), Haswell (GT3), Haswell SDV Desktop (GT1),
Haswell SDV Desktop (GT2), Haswell SDV Desktop (GT3),
Haswell SDV Mobile (GT1), Haswell SDV Mobile (GT2),
Haswell SDV Mobile (GT3), Haswell SDV Server (GT1),
Haswell SDV Server (GT2), Haswell SDV Server (GT3),
Haswell SDV (GT1), Haswell SDV (GT2), Haswell SDV (GT3),
Haswell SDV (GT1), Haswell SDV (GT2), Haswell SDV (GT3),
Haswell ULT Desktop (GT1), Haswell ULT Desktop (GT2),
Iris(TM) Graphics 5100, HD Graphics, HD Graphics 4400,
HD Graphics 5000, Haswell ULT Server (GT1), Haswell ULT Server (GT2),
Iris(TM) Graphics 5100, Haswell ULT (GT1), Haswell ULT (GT2),
Iris(TM) Graphics 5100, HD Graphics, HD Graphics 4200,
Iris(TM) Graphics 5100, Haswell CRW Desktop (GT1), HD Graphics 4600,
Iris(TM) Pro Graphics 5200, Haswell CRW Mobile (GT1),
HD Graphics 4600, Iris(TM) Pro Graphics 5200,
Haswell CRW Server (GT1), Haswell CRW Server (GT2),
Iris(TM) Pro Graphics 5200, Haswell CRW (GT1), Haswell CRW (GT2),
Iris(TM) Pro Graphics 5200, Haswell CRW (GT1), Haswell CRW (GT2),
Iris(TM) Pro Graphics 5200, ValleyView PO board
[ 7.594] (II) VESA: driver for VESA chipsets: vesa
[ 7.594] (++) using VT number 1
[ 7.594] (WW) Falling back to old probe method for vesa
[ 7.594] (II) intel(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 7.594] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[ 7.594] (==) intel(0): RGB weight 888
[ 7.594] (==) intel(0): Default visual is TrueColor
[ 7.594] (--) intel(0): Integrated Graphics Chipset: Intel(R) Ivybridge Mobile (GT2)
[ 7.594] (**) intel(0): Relaxed fencing enabled
[ 7.594] (**) intel(0): Wait on SwapBuffers? enabled
[ 7.594] (**) intel(0): Triple buffering? enabled
[ 7.594] (**) intel(0): Framebuffer tiled
[ 7.594] (**) intel(0): Pixmaps tiled
[ 7.594] (**) intel(0): 3D buffers tiled
[ 7.594] (**) intel(0): SwapBuffers wait enabled
[ 7.594] (==) intel(0): video overlay key set to 0x101fe
[ 7.594] (II) intel(0): Output eDP1 has no monitor section
[ 7.595] (--) intel(0): found backlight control interface /sys/class/backlight/acpi_video1
[ 7.596] (II) intel(0): Output VGA1 has no monitor section
[ 7.596] (II) intel(0): EDID for output eDP1
[ 7.596] (II) intel(0): Manufacturer: LGD Model: 323 Serial#: 0
[ 7.596] (II) intel(0): Year: 2012 Week: 0
[ 7.596] (II) intel(0): EDID Version: 1.4
[ 7.596] (II) intel(0): Digital Display Input
[ 7.596] (II) intel(0): 6 bits per channel
[ 7.596] (II) intel(0): Digital interface is DisplayPort
[ 7.596] (II) intel(0): Max Image Size [cm]: horiz.: 35 vert.: 19
[ 7.596] (II) intel(0): Gamma: 2.20
[ 7.596] (II) intel(0): No DPMS capabilities specified
[ 7.596] (II) intel(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
[ 7.596] (II) intel(0): First detailed timing is preferred mode
[ 7.596] (II) intel(0): Preferred mode is native pixel format and refresh rate
[ 7.596] (II) intel(0): redX: 0.629 redY: 0.350 greenX: 0.349 greenY: 0.614
[ 7.596] (II) intel(0): blueX: 0.154 blueY: 0.112 whiteX: 0.313 whiteY: 0.329
[ 7.596] (II) intel(0): Manufacturer's mask: 0
[ 7.596] (II) intel(0): Supported detailed timing:
[ 7.596] (II) intel(0): clock: 138.0 MHz Image Size: 345 x 194 mm
[ 7.596] (II) intel(0): h_active: 1920 h_sync: 1952 h_sync_end 1988 h_blank_end 2088 h_border: 0
[ 7.596] (II) intel(0): v_active: 1080 v_sync: 1085 v_sync_end 1090 v_blanking: 1102 v_border: 0
[ 7.596] (II) intel(0): LG Display
[ 7.596] (II) intel(0): LP156WF4-SPB1
[ 7.596] (II) intel(0): EDID (in hex):
[ 7.596] (II) intel(0): 00ffffffffffff0030e4230300000000
[ 7.596] (II) intel(0): 00160104952313780a25b5a159599d27
[ 7.596] (II) intel(0): 1c505400000001010101010101010101
[ 7.596] (II) intel(0): 010101010101e83580a8703816402024
[ 7.596] (II) intel(0): 550059c2100000180000000000000000
[ 7.596] (II) intel(0): 00000000000000000000000000fe004c
[ 7.596] (II) intel(0): 4720446973706c61790a2020000000fe
[ 7.596] (II) intel(0): 004c503135365746342d535042310069
[ 7.596] (II) intel(0): Not using default mode "320x240" (doublescan mode not supported)
[ 7.597] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
[ 7.597] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
[ 7.597] (II) intel(0): Not using default mode "512x384" (doublescan mode not supported)
[ 7.597] (II) intel(0): Not using default mode "640x480" (doublescan mode not supported)
[ 7.597] (II) intel(0): Not using default mode "640x512" (doublescan mode not supported)
[ 7.597] (II) intel(0): Not using default mode "800x600" (doublescan mode not supported)
[ 7.597] (II) intel(0): Not using default mode "896x672" (doublescan mode not supported)
[ 7.597] (II) intel(0): Not using default mode "928x696" (doublescan mode not supported)
[ 7.597] (II) intel(0): Not using default mode "960x720" (doublescan mode not supported)
[ 7.597] (II) intel(0): Not using default mode "700x525" (doublescan mode not supported)
[ 7.597] (II) intel(0): Not using default mode "1024x768" (doublescan mode not supported)
[ 7.597] (II) intel(0): Printing probed modes for output eDP1
[ 7.597] (II) intel(0): Modeline "1920x1080"x60.0 138.00 1920 1952 1988 2088 1080 1085 1090 1102 -hsync -vsync (66.1 kHz eP)
[ 7.597] (II) intel(0): Modeline "1400x1050"x60.0 122.00 1400 1488 1640 1880 1050 1052 1064 1082 +hsync +vsync (64.9 kHz d)
[ 7.597] (II) intel(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz d)
[ 7.597] (II) intel(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz d)
[ 7.597] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz d)
[ 7.597] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz d)
[ 7.597] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz d)
[ 7.597] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz d)
[ 7.598] (II) intel(0): EDID for output VGA1
[ 7.598] (II) intel(0): Output eDP1 connected
[ 7.598] (II) intel(0): Output VGA1 disconnected
[ 7.598] (II) intel(0): Using exact sizes for initial modes
[ 7.598] (II) intel(0): Output eDP1 using initial mode 1920x1080
[ 7.598] (II) intel(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 7.598] (II) intel(0): Kernel page flipping support detected, enabling
[ 7.598] (==) intel(0): DPI set to (96, 96)
[ 7.598] (II) Loading sub module "fb"
[ 7.598] (II) LoadModule: "fb"
[ 7.598] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 7.599] (II) Module fb: vendor="X.Org Foundation"
[ 7.599] compiled for 1.14.2, module version = 1.0.0
[ 7.599] ABI class: X.Org ANSI C Emulation, version 0.4
[ 7.599] (II) Loading sub module "dri2"
[ 7.599] (II) LoadModule: "dri2"
[ 7.599] (II) Module "dri2" already built-in
[ 7.599] (II) UnloadModule: "vesa"
[ 7.599] (II) Unloading vesa
[ 7.599] (==) Depth 24 pixmap format is 32 bpp
[ 7.599] (II) intel(0): [DRI2] Setup complete
[ 7.599] (II) intel(0): [DRI2] DRI driver: i965
[ 7.599] (II) intel(0): Allocated new frame buffer 1920x1080 stride 7680, tiled
[ 7.599] (II) UXA(0): Driver registered support for the following operations:
[ 7.599] (II) solid
[ 7.599] (II) copy
[ 7.599] (II) composite (RENDER acceleration)
[ 7.599] (II) put_image
[ 7.599] (II) get_image
[ 7.599] (==) intel(0): Backing store disabled
[ 7.599] (==) intel(0): Silken mouse enabled
[ 7.600] (II) intel(0): Initializing HW Cursor
[ 7.600] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 7.600] (==) intel(0): DPMS enabled
[ 7.600] (==) intel(0): Intel XvMC decoder enabled
[ 7.600] (II) intel(0): Set up textured video
[ 7.600] (II) intel(0): [XvMC] xvmc_vld driver initialized.
[ 7.600] (II) intel(0): direct rendering: DRI2 Enabled
[ 7.600] (==) intel(0): hotplug detection: "enabled"
[ 7.613] (--) RandR disabled
[ 7.634] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 7.634] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 7.634] (II) AIGLX: enabled GLX_ARB_create_context
[ 7.634] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 7.634] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
[ 7.634] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[ 7.634] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 7.634] (II) AIGLX: Loaded and initialized i965
[ 7.634] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 7.634] (II) intel(0): Setting screen physical size to 508 x 285
[ 7.669] (II) config/udev: Adding input device Video Bus (/dev/input/event9)
[ 7.669] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 7.669] (II) LoadModule: "evdev"
[ 7.669] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 7.670] (II) Module evdev: vendor="X.Org Foundation"
[ 7.670] compiled for 1.14.2, module version = 2.8.1
[ 7.670] Module class: X.Org XInput Driver
[ 7.670] ABI class: X.Org XInput driver, version 19.1
[ 7.670] (II) Using input driver 'evdev' for 'Video Bus'
[ 7.670] (**) Video Bus: always reports core events
[ 7.670] (**) evdev: Video Bus: Device: "/dev/input/event9"
[ 7.670] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 7.670] (--) evdev: Video Bus: Found keys
[ 7.670] (II) evdev: Video Bus: Configuring as keyboard
[ 7.670] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:01/input/input10/event9"
[ 7.670] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 6)
[ 7.670] (**) Option "xkb_rules" "evdev"
[ 7.670] (**) Option "xkb_model" "pc104"
[ 7.670] (**) Option "xkb_layout" "us"
[ 7.684] (II) config/udev: Adding input device Video Bus (/dev/input/event8)
[ 7.684] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 7.684] (II) Using input driver 'evdev' for 'Video Bus'
[ 7.684] (**) Video Bus: always reports core events
[ 7.684] (**) evdev: Video Bus: Device: "/dev/input/event8"
[ 7.684] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 7.684] (--) evdev: Video Bus: Found keys
[ 7.684] (II) evdev: Video Bus: Configuring as keyboard
[ 7.684] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:03/LNXVIDEO:00/input/input9/event8"
[ 7.684] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[ 7.684] (**) Option "xkb_rules" "evdev"
[ 7.684] (**) Option "xkb_model" "pc104"
[ 7.684] (**) Option "xkb_layout" "us"
[ 7.684] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[ 7.685] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 7.685] (II) Using input driver 'evdev' for 'Power Button'
[ 7.685] (**) Power Button: always reports core events
[ 7.685] (**) evdev: Power Button: Device: "/dev/input/event2"
[ 7.685] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 7.685] (--) evdev: Power Button: Found keys
[ 7.685] (II) evdev: Power Button: Configuring as keyboard
[ 7.685] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input2/event2"
[ 7.685] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
[ 7.685] (**) Option "xkb_rules" "evdev"
[ 7.685] (**) Option "xkb_model" "pc104"
[ 7.685] (**) Option "xkb_layout" "us"
[ 7.685] (II) config/udev: Adding input device Lid Switch (/dev/input/event1)
[ 7.685] (II) No input driver specified, ignoring this device.
[ 7.685] (II) This device may have been added with another device file.
[ 7.685] (II) config/udev: Adding input device Sleep Button (/dev/input/event3)
[ 7.685] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 7.685] (II) Using input driver 'evdev' for 'Sleep Button'
[ 7.685] (**) Sleep Button: always reports core events
[ 7.685] (**) evdev: Sleep Button: Device: "/dev/input/event3"
[ 7.685] (--) evdev: Sleep Button: Vendor 0 Product 0x3
[ 7.685] (--) evdev: Sleep Button: Found keys
[ 7.685] (II) evdev: Sleep Button: Configuring as keyboard
[ 7.685] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input3/event3"
[ 7.685] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 9)
[ 7.685] (**) Option "xkb_rules" "evdev"
[ 7.685] (**) Option "xkb_model" "pc104"
[ 7.685] (**) Option "xkb_layout" "us"
[ 7.685] (II) config/udev: Adding drm device (/dev/dri/card1)
[ 7.685] (II) config/udev: Adding drm device (/dev/dri/card0)
[ 7.686] (II) config/udev: Adding input device USB2.0 HD UVC WebCam (/dev/input/event6)
[ 7.686] (**) USB2.0 HD UVC WebCam: Applying InputClass "evdev keyboard catchall"
[ 7.686] (II) Using input driver 'evdev' for 'USB2.0 HD UVC WebCam'
[ 7.686] (**) USB2.0 HD UVC WebCam: always reports core events
[ 7.686] (**) evdev: USB2.0 HD UVC WebCam: Device: "/dev/input/event6"
[ 7.686] (--) evdev: USB2.0 HD UVC WebCam: Vendor 0x4f2 Product 0xb36e
[ 7.686] (--) evdev: USB2.0 HD UVC WebCam: Found keys
[ 7.686] (II) evdev: USB2.0 HD UVC WebCam: Configuring as keyboard
[ 7.686] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.3/3-1.3:1.0/input/input6/event6"
[ 7.686] (II) XINPUT: Adding extended input device "USB2.0 HD UVC WebCam" (type: KEYBOARD, id 10)
[ 7.686] (**) Option "xkb_rules" "evdev"
[ 7.686] (**) Option "xkb_model" "pc104"
[ 7.686] (**) Option "xkb_layout" "us"
[ 7.686] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event5)
[ 7.686] (II) No input driver specified, ignoring this device.
[ 7.686] (II) This device may have been added with another device file.
[ 7.686] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 7.686] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 7.686] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 7.686] (**) AT Translated Set 2 keyboard: always reports core events
[ 7.686] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 7.686] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 7.686] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 7.686] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 7.686] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 7.686] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 11)
[ 7.686] (**) Option "xkb_rules" "evdev"
[ 7.686] (**) Option "xkb_model" "pc104"
[ 7.686] (**) Option "xkb_layout" "us"
[ 7.686] (II) config/udev: Adding input device ETPS/2 Elantech Touchpad (/dev/input/event7)
[ 7.686] (**) ETPS/2 Elantech Touchpad: Applying InputClass "evdev touchpad catchall"
[ 7.686] (**) ETPS/2 Elantech Touchpad: Applying InputClass "touchpad catchall"
[ 7.687] (**) ETPS/2 Elantech Touchpad: Applying InputClass "Default clickpad buttons"
[ 7.687] (II) LoadModule: "synaptics"
[ 7.687] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 7.687] (II) Module synaptics: vendor="X.Org Foundation"
[ 7.687] compiled for 1.14.1, module version = 1.7.1
[ 7.687] Module class: X.Org XInput Driver
[ 7.687] ABI class: X.Org XInput driver, version 19.1
[ 7.687] (II) Using input driver 'synaptics' for 'ETPS/2 Elantech Touchpad'
[ 7.687] (**) ETPS/2 Elantech Touchpad: always reports core events
[ 7.687] (**) Option "Device" "/dev/input/event7"
[ 7.810] (II) synaptics: ETPS/2 Elantech Touchpad: found clickpad property
[ 7.810] (--) synaptics: ETPS/2 Elantech Touchpad: x-axis range 0 - 3260 (res 32)
[ 7.810] (--) synaptics: ETPS/2 Elantech Touchpad: y-axis range 0 - 2119 (res 32)
[ 7.810] (--) synaptics: ETPS/2 Elantech Touchpad: pressure range 0 - 255
[ 7.810] (--) synaptics: ETPS/2 Elantech Touchpad: finger width range 0 - 15
[ 7.810] (--) synaptics: ETPS/2 Elantech Touchpad: buttons: left double triple
[ 7.810] (--) synaptics: ETPS/2 Elantech Touchpad: Vendor 0x2 Product 0xe
[ 7.810] (**) Option "TapButton1" "1"
[ 7.810] (**) Option "TapButton2" "2"
[ 7.810] (**) Option "TapButton3" "3"
[ 7.810] (**) Option "SoftButtonAreas" "50% 0 82% 0 0 0 0 0"
[ 7.810] (--) synaptics: ETPS/2 Elantech Touchpad: touchpad found
[ 7.810] (**) ETPS/2 Elantech Touchpad: always reports core events
[ 7.853] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio4/input/input8/event7"
[ 7.853] (II) XINPUT: Adding extended input device "ETPS/2 Elantech Touchpad" (type: TOUCHPAD, id 12)
[ 7.853] (**) synaptics: ETPS/2 Elantech Touchpad: (accel) MinSpeed is now constant deceleration 2.5
[ 7.853] (**) synaptics: ETPS/2 Elantech Touchpad: (accel) MaxSpeed is now 1.75
[ 7.853] (**) synaptics: ETPS/2 Elantech Touchpad: (accel) AccelFactor is now 0.051
[ 7.853] (**) ETPS/2 Elantech Touchpad: (accel) keeping acceleration scheme 1
[ 7.853] (**) ETPS/2 Elantech Touchpad: (accel) acceleration profile 1
[ 7.853] (**) ETPS/2 Elantech Touchpad: (accel) acceleration factor: 2.000
[ 7.853] (**) ETPS/2 Elantech Touchpad: (accel) acceleration threshold: 4
[ 7.853] (--) synaptics: ETPS/2 Elantech Touchpad: touchpad found
[ 7.853] (II) config/udev: Adding input device ETPS/2 Elantech Touchpad (/dev/input/mouse0)
[ 7.853] (**) ETPS/2 Elantech Touchpad: Ignoring device from InputClass "touchpad ignore duplicates"
[ 7.853] (II) config/udev: Adding input device PC Speaker (/dev/input/event4)
[ 7.853] (II) No input driver specified, ignoring this device.
[ 7.853] (II) This device may have been added with another device file.
Found this recent thread in the forums, I'll give REISUB a try late, but the times it freezed I remember trying to blindly reboot it, or switching off virtual console and couldn't.
In case it's of any use, this is my # uname -a
Linux arch 3.10.3-1-ARCH #1 SMP PREEMPT Fri Jul 26 11:26:59 CEST 2013 x86_64 GNU/Linux
Could it have something to do with the nvidia optimus setup that this laptop has? When installing arch I found out that there was no support yet for it so I'm just using the intel drivers (following what the arch wiki said).
Any ideas or advice to point me in the right direction would be very much appreciated.
Thanks in advance.
Last edited by contiver (2013-08-16 20:25:34)

I don't start st in my .xinitrc. I launch it from dmenu and usually everything is fine. If I launch it from dwm's internal command using Alt-Shf-Return, X freezes 100% of the time. A workaround was suggested by st's main developer to call st like this:
static const char *termcmd[] = { "/bin/sh", "-c", "st", NULL };
but it didn't work for me.
Very rarely X will freeze anyway. I haven't been able to pin it down. When X fails, my journal returns this:
BUG: unable to handle kernel paging request at ffffc90014ce8000
IP: [<ffffffff812bfe7f>] bitfill_aligned+0x8f/0x140
PGD 7c00b067 PUD 7c018067 PMD 7b3eb067 PTE 0
Oops: 0002 [#1] PREEMPT SMP
Modules linked in: nls_cp437 vfat fat snd_usb_audio snd_usbmidi_lib snd_hwdep snd_rawmidi snd_seq_device snd_pcm snd_page_alloc snd_timer
CPU: 1 PID: 7520 Comm: X Not tainted 3.10.5-1-ck #1
Hardware name: /D410PT, BIOS MOPNV10N.86A.0155.2009.1106.0430 11/06/2009
task: ffff88007aa786b0 ti: ffff8800797ee000 task.ti: ffff8800797ee000
RIP: 0010:[<ffffffff812bfe7f>] [<ffffffff812bfe7f>] bitfill_aligned+0x8f/0x140
RSP: 0018:ffff8800797efaa8 EFLAGS: 00010212
RAX: 0000000003ffff5c RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000003ffff5c RSI: ffffc90014901520 RDI: ffffc90014ce7fe0
RBP: ffff8800797efab8 R08: 00000000ffffd700 R09: 0000000003f83204
R10: 0000000000000000 R11: ffffc90014ce7fd8 R12: ffffffffffffffff
R13: ffffc90014901520 R14: ffffffff812bfdf0 R15: 0000000000000320
FS: 00007fb350033880(0000) GS:ffff88007ea80000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: ffffc90014ce8000 CR3: 000000007b104000 CR4: 00000000000007e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Stack:
0000000000000000 ffff88007a4d3000 ffff8800797efb28 ffffffff812bfbb9
ffffffff00000000 ffff88007c00c000 0000000000000000 ffffffff8186f240
0000000000000000 ffffffff00000006 ffffd700797efb58 ffff88007a4d3000
Call Trace:
[<ffffffff812bfbb9>] cfb_fillrect+0x1c9/0x400
[<ffffffff812ba2e5>] bit_clear_margins+0x165/0x190
[<ffffffff812b3633>] fbcon_clear_margins+0x63/0x90
[<ffffffff812b7a9f>] fbcon_switch+0x3df/0x570
[<ffffffff813200bd>] redraw_screen+0x17d/0x240
[<ffffffff812b6eeb>] fbcon_blank+0x20b/0x2d0
[<ffffffff81320767>] do_unblank_screen+0xa7/0x1b0
[<ffffffff813175d1>] vt_ioctl+0x10d1/0x1170
[<ffffffff8130b407>] tty_ioctl+0x277/0xb90
[<ffffffff8118fb21>] ? mntput_no_expire+0x41/0x150
[<ffffffff81183a3e>] do_vfs_ioctl+0x2de/0x4c0
[<ffffffff8117328e>] ? ____fput+0xe/0x10
[<ffffffff8107766c>] ? task_work_run+0x9c/0xe0
[<ffffffff81183ca3>] SyS_ioctl+0x83/0xa0
[<ffffffff814bab9d>] system_call_fastpath+0x1a/0x1f
Code: 08 45 01 d8 31 d2 44 89 c0 41 f7 f1 83 f8 07 89 c2 76 4f 44 8d 08 48 8d 3e 0f 1f 00 4c 89 17 4c 89 57 08 4c 89 57 10 4c 89 57 18 <4
RIP [<ffffffff812bfe7f>] bitfill_aligned+0x8f/0x140
RSP <ffff8800797efaa8>
CR2: ffffc90014ce8000
---[ end trace aff6cb5ad5097aef ]---

When I external edit an aperture photo using Photoshop Elements 9 and then get out, the changes are not reflected in Aperture when I return - this used to work for me but doesn't seem to have for some time - help please?

Have used Aperture for some time - at some point this stopped working - not sure when
workflow:
click photo and elect to use the external editor (Photoshop Elements 9)
Copy of the photo is created in Aperture with the "O" badge and I am rolled out to Photoshop
Have to change the type to 8-bit in Photoshop to start making changes
When done and I exit I am prompted to save the photo
On returning to Aperture however the "O" badged photo does not get updated/reflect my changes
Other Things:
I can find a changed photo sitting in the Aperture Library using finder or Photoshop itself - so I know changes have been made a new file saved (TIFF).
I am wondering if I am missing some (new) preference such that the changes are not proerly being saved for re-display/storage in the Aperture Library
I am running Lion OSX at the moment but the behaviour was the same under Snow Lepoard versions.
Current version of Aperture is 3.1.3, Elements is 9.0
Any help/suggestions greatfully received

Try using psd. Some rerports indicate some confustion between the apps with TIFF. See:
https://discussions.apple.com/message/15921933#15921933
I cannot confirm, nor test, since I use PS CS5, and not Elements.
Ernie

Condition Types appearing two times in a Purchase Order

Hi,
The condition types are same in supplementary schema (for Info Record) and Purchase Order Calculation Schema. When I put some value against a condition type under conditions in Info Record then that condition type appears 2 times in the purchase order. It seems the condition type appears 1st time (with value from Info Record) because it is picked from Info Record and 2nd time (with no value) from the Purchase Order Calculation Schema.
The requirement is condition type should appear only single time in PO (by default) with or without value in spite of having info record. In case some value is maintained in Info Record then the condition type should appear with value but in a single line in PO which can be edited if required. There should not be second line of same condition type by default in PO.
Can anyone provide some idea to resolve this?
Thanks in advance

There is only 1 condition line (apart from PB00), which comes 2 times in PO by default, in MEK2 and also one condition line (one line was deleted and then saved) in last PO (from the Info Record). But the condition type still comes 2 times while creating a new PO.
Please provide some more answer to resolve this issue.
Thanks in advance

Drive won't read any dvd-ejects it automatically after spinning some time

The SuperDrive on my MBP has stopped recognizing/reading any blank DVD media (and many recorded DVDs, including movie discs). It spins for some time with a noise and then ejects it out. The same media works fine in my wife's Sony Vaio laptop.
There was a thread on this previously, but Apple has closed it:
http://discussions.apple.com/thread.jspa?threadID=1295681
I know Apple won't own up to the problem, so has anyone found a solution?
Drive details:
HL-DT-ST DVDRW GSA-S10N:
Model: HL-DT-ST DVDRW GSA-S10N
Revision: AP09
Serial Number: K0077R40928
Detachable Drive: No
Protocol: ATAPI
Unit Number: 0
Socket Type: Internal
Low Power Polling: Yes
Power Off: Yes

Got exactly the same problem a few days ago (still there, las time I checked):
http://discussions.apple.com/thread.jspa?threadID=1914325&tstart=0
Dunno why, but I think this has something to do with the Security Update 2009-001 Apple posted on its download platform a few days ago. Must have wrecked my SuperDrive somehow--and maybe yours, too--and I agree with Ryan when he says Apple hasn't been up to its reputation, lately. Maybe the market pressure got too much, and they started buying cheaper components...
Makes me wonder; imagine, you buy the brand new MacBook/MacBook Pro, with its encased battery and other fancy stuff, and something breaks down in the beast's belly. What do you do, then, bring it back to that some so-called Genius tells you to send it in to AppleCare.
Naughty, naughty, Apple...

Live type - artifacts some times

Similar Messages

Maybe you are looking for