Changing pixel density metadata in JPEG
Hello:
Does anybody know of a way/utility to batch mode change the pixel density metadata in JPEG files? I have this Phillips digital frame which won't display images properly when the JPEG DPI information is 72, regardless of the real pixel width and height of the images.
Editing it in Photoshop works, but it also rewrites the data of the image, recompressing the JPEG a second time, cumulating artifacts.
Thank you for your suggestions,
Yann
All other applications do what they're supposed to with Windows font settings, so I'm not going to set it to 100% and mess them up because Firefox is weird.
Similar Messages
-
Include Develop settings in metadata inside JPEG, TIFF, and PSD files ignored when unchecked
In the Catalog Settings under the Metadata tab, I have unchecked the option 'Include Develop settings in metadata inside JPEG, TIFF and PSD files'.
I then selected a JPEG photograph in the Library module and chose Metadata/Save Metatdata to File. I wanted to save the metadata that I had added (keywords, IPTC, rating, etc), but not the develop settings.
I then imported the jpeg back into another catalog. The metadata I had added was there as expected, but so are the develop settings. This I did not expect or want.
Have I got something wrong here? My understanding is that turning off the 'Include Develop settings in metadata inside JPEG, TIFF and PSD files' option means that develop settings are not written to the xmp area in non raw files such as jpegs.
Looks like a bug to me.
TonyHello all,
I have investigated this problem further and now have the answer. It is not that the option "Include Develop settings in metadata inside JPEG, TIFF, and PSD files" is ignored, but it appears that the LR catalog is not properly updated when this option is turned off.
Here are steps to test and illustrate the problem:
1. Create a new folder and place a copy of an original jpeg image (original from camera) in the new folder. Make sure you keep the original safe and only work on copies.
2. Create a new catalog in Lightroom 2.3.
3. Import the jpeg image from the new folder.
4. Add some metadata (keywords, ratings, title, caption, IPTC data, etc).
5. Make some Develop adjustments to the image.
6. Open "Catalogue Settings" from the Edit menu and check (enable) the option "Include Develop settings in metadata inside JPEG, TIFF, and PSD files". Uncheck (disable) the "Automatically write changes into XMP" option.
7. Select "Save Metadata to File".
8. Delete the jpeg image from the Library module, then re-import it.
9. Copy the original image back to the new folder, replacing the updated jpeg (once again, the jpeg image now contains no metadata from Lightroom). At this stage, Lightroom fails to recognize that the metadata in the LR catalog doesn’t match the metadata content in the jpeg file. I would have though that it should.
10. Open "Catalogue Settings" from the Edit menu and uncheck (turn off) the option "Include Develop settings in metadata inside JPEG, TIFF, and PSD files".
11. Reset the Develop settings.
12. You now need to make a change to the metadata like increase or decrease the rating (otherwise LR won’t save any metadata to the jpeg file - LR is being too smart and thinks it’s already up to date, so does nothing when you do the next step).
12. Select "Save Metadata to File".
13. Delete the jpeg image from the Library module again, then re-import it again.
14. Look at the develop settings (that you specifically did not want saved within the jpeg file in step 10).
Although the Develop settings were Reset in step 11, you have ended up with the original Develop settings from step 5. It is true that LR has not saved the reset develop settings, but it also hasn’t removed the old develop settings that are still stored in the catalog. This must be considered a bug (oversight). Note that it has also saved an Import snapshot as well.
For the more technically minded (and the LR developers if you are listening), the field "xmp" in the table "Adobe_AdditionalMetadata" is not updated (old camera raw settings and snapshot settings are left behind) when the "Include Develop settings in metadata inside JPEG, TIFF, and PSD files" option is unchecked (disabled) and it seems that this is the data that is written to the jpeg file when you select "Save Metadata to File". Note that the state of "Automatically write changes into XMP" has not effect on this process - I tried it on and off.
Hope that this might be of some help to others one day.
Tony -
What does "Include develop settings metadata inside JPEG, TIFF, and PSD files" do?
I am wondering what the option "Include develop settings metadata inside JPEG, TIFF, and PSD files" found in catalog settings/metadata does? what happens if you uncheck it?
Bob12312321 wrote:
also when this is unchecked will lightroom still save keyword changes to raw(nef) files? thank you!
Metadata ("real" metadata like keyowords nor develop adjustments) are never saved into non-DNG Raw files (like .nef, .cr2) directly. With these files, there is always a so called sidecar file (with the extension .xmp) created to hold the XMP information.
And yes, if the option is unchecked, LR will save the keywords to the XMP sidecars, when you perform "Write Metadata to File" or have the autowrite option active.
Beat -
Laserjet CP1025nw color, unable to change Print density
Hi,
I need to raise the "Print Density" to 5 (for pcb toner transfer) on my Laserjet
CP1025nw color, but when I open the printer properties I do not have that option
in the device settings tab, despite what is said on the help page of that model.
OS: Windows XP
The printer is on the USB port.
The pilot is: HP LaserJet Professional CP1020 Series + last update
How can I change that setting ?
Please help !!!
Thank you in advance for any help you can bring !
All the best,
This question was solved.
View Solution.From what you describe you want to increase your toner density on your subsequent print jobs. First of all, if you have not, you should uninstall this printer and make sure that the drivers are the most up to date using the website I will link below :
http://h10025.www1.hp.com/ewfrf/wc/softwareCategory?cc=us&lc=en&dlc=en&product=4052972
Here you should also check for your firmware to be sure that it is up to date.
I would also, both before and after, check under "Printer Preferences" (not properties) and see if there is a way to change the density under the Paper/Quality tab.
Let me know if this helps you out!
-Spencer -
[SOLVED] Rapidly changing pixels in X (Intel 945GME)
Hi,
A few days ago I managed to install Arch Linux on my EEE Box B202 (thanks, devs), containing an Intel 945GME chipset. Everything looks fine, but when I start X, the screen goes black for a few moments (monitor complains 'no sync') and when it is back on, I sometimes notice some screen glitches: a few times a minute there is a little flicker somewhere (especially when something on the screen changes) and pictures are not 'steady', i.e. there are pixels that rapidly change colour (e.g., in the Google logo). On smooth surfaces I don't notice those glitches (or they are less noticeable).
My monitor is connected using a DVI-cable (so, without the DVI-to-VGA-adaptor). In WinXP there are no glitches, so it couldn't be due to the cable or the 945GME chipset that can't handle this resolution... I tried using xf86-video-intel 2.4.3-1 and libdrm 2.3.1-2 as well as xf86-video-intel-newest 2.6.1-2 and libdrm-newest 2.4.4-2 from AUR. On another box (with a i82915G/GV/910GL graphics chip) there are no problems with these drivers (well, connecting using the VGA-port, that is).
I already searched the forums for this (also the Ubuntu- and EEE-users forum), but nothing helps. My xorg.conf reads
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "ServerFlags"
Option "AutoAddDevices" "False"
EndSection
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/Type1"
EndSection
Section "Module"
Load "xtrap"
Load "extmod"
Load "glx"
Load "dri"
Load "dbe"
Load "freetype"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2" # IntelliMouse PS/2
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "LVDS"
Option "Ignore" "True"
EndSection
Section "Monitor"
Identifier "VGA"
Option "Ignore" "True"
EndSection
Section "Monitor"
Identifier "TMDS-1"
Option "Ignore" "False"
EndSection
Section "Monitor"
Identifier "Neovo F-419"
HorizSync 31.5 - 64.3
VertRefresh 50-70
DisplaySize 336 269
EndSection
Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
#Option "NoAccel" # [<bool>]
#Option "SWcursor" # [<bool>]
#Option "ColorKey" # <i>
#Option "CacheLines" # <i>
#Option "Dac6Bit" # [<bool>]
Option "DRI" # [<bool>]
#Option "NoDDC" # [<bool>]
#Option "ShowCache" # [<bool>]
#Option "XvMCSurfaces" # <i>
#Option "PageFlip" # [<bool>]
Option "monitor-LVDS" "LVDS"
Option "monitor-VGA" "VGA"
Option "monitor-TMDS-1" "TMDS-1"
Identifier "Card0"
Driver "intel"
VendorName "Intel Corporation"
BoardName "Mobile 945GME Express Integrated Graphics Controller"
BusID "PCI:0:2:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Neovo F-419"
DefaultDepth 24
Subsection "Display"
Depth 8
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
EndSection
When adding @60 to the Mode "1280x1024", my monitor complains about the signal being out of range (despite displaying a somewhat unsharp picture). Uncommenting the "NoAccel" option and commenting out "DRI" didn't solve this problem (only slows down graphics drawing a lot).
This is my last Xorg.0.log (using 2.4.3-1):
X.Org X Server 1.5.3
Release Date: 5 November 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.27-ARCH i686
Current Operating System: Linux brogain 2.6.28-ARCH #1 SMP PREEMPT Sun Jan 25 10:13:11 UTC 2009 i686
Build Date: 17 December 2008 08:20:05PM
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Feb 1 13:07:19 2009
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "X.org Configured"
(**) |-->Screen "Screen0" (0)
(**) | |-->Monitor "Neovo F-419"
(**) | |-->Device "Card0"
(**) |-->Input Device "Mouse0"
(**) |-->Input Device "Keyboard0"
(**) Option "AutoAddDevices" "False"
(**) Not automatically adding devices
(==) Automatically enabling devices
(==) Including the default font path /usr/share/fonts/misc,/usr/share/fonts/100dpi:unscaled,/usr/share/fonts/75dpi:unscaled,/usr/share/fonts/TTF,/usr/share/fonts/Type1.
(**) FontPath set to:
/usr/share/fonts/misc,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/TTF,
/usr/share/fonts/Type1,
/usr/share/fonts/misc,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/TTF,
/usr/share/fonts/Type1
(**) ModulePath set to "/usr/lib/xorg/modules"
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) Loader magic: 0x81d5fe0
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 4.1
X.Org XInput driver : 2.1
X.Org Server Extension : 1.1
X.Org Font Renderer : 0.6
(II) Loader running on linux
(--) using VT number 7
(--) PCI:*(0@0:2:0) Intel Corporation Mobile 945GME Express Integrated Graphics Controller rev 3, Mem @ 0xfeb80000/0, 0xd0000000/0, 0xfeb40000/0, I/O @ 0x0000ec80/0
(--) PCI: (0@0:2:1) Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller rev 3, Mem @ 0xfea80000/0
(II) System resource ranges:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
(II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
(II) "glx" will be loaded. This was enabled by default and also specified in the config file.
(II) "freetype" will be loaded. This was enabled by default and also specified in the config file.
(II) "dri" will be loaded. This was enabled by default and also specified in the config file.
(II) LoadModule: "xtrap"
(II) Loading /usr/lib/xorg/modules/extensions//libxtrap.so
(II) Module xtrap: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension DEC-XTRAP
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
ABI class: X.Org Server Extension, version 1.1
(==) AIGLX enabled
(==) Exporting typical set of GLX visuals
(II) Loading extension GLX
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension XFree86-DRI
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "freetype"
(II) Loading /usr/lib/xorg/modules/fonts//libfreetype.so
(II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
compiled for 1.5.3, module version = 2.1.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.6
(II) Loading font FreeType
(II) LoadModule: "intel"
(II) Loading /usr/lib/xorg/modules/drivers//intel_drv.so
(II) Module intel: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 2.4.3
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 4.1
(II) LoadModule: "mouse"
(II) Loading /usr/lib/xorg/modules/input//mouse_drv.so
(II) Module mouse: vendor="X.Org Foundation"
compiled for 1.4.2, module version = 1.3.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 2.0
(II) LoadModule: "kbd"
(II) Loading /usr/lib/xorg/modules/input//kbd_drv.so
(II) Module kbd: vendor="X.Org Foundation"
compiled for 1.4.2, module version = 1.3.1
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 2.0
(II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G,
E7221 (i915), 915GM, 945G, 945GM, 945GME, 965G, G35, 965Q, 946GZ,
965GM, 965GME/GLE, G33, Q35, Q33,
Mobile Intel® GM45 Express Chipset,
Intel Integrated Graphics Device, G45/G43, Q45/Q43
(II) Primary Device is: PCI 00@00:02:0
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(II) resource ranges after probing:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b]
[5] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b]
[6] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b]
[7] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[8] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[9] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b]
[10] 0 0 0x000003c0 - 0x000003df (0x20) IS[b]
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Loading /usr/lib/xorg/modules//libint10.so
(II) Module int10: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
ABI class: X.Org Video Driver, version 4.1
(II) Loading sub module "vbe"
(II) LoadModule: "vbe"
(II) Loading /usr/lib/xorg/modules//libvbe.so
(II) Module vbe: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.1.0
ABI class: X.Org Video Driver, version 4.1
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/lib/xorg/modules//libvgahw.so
(II) Module vgahw: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 0.1.0
ABI class: X.Org Video Driver, version 4.1
(**) intel(0): Depth 24, (--) framebuffer bpp 32
(==) intel(0): RGB weight 888
(==) intel(0): Default visual is TrueColor
(**) intel(0): Option "DRI"
(II) intel(0): Integrated Graphics Chipset: Intel(R) 945GME
(--) intel(0): Chipset: "945GME"
(--) intel(0): Linear framebuffer at 0xD0000000
(--) intel(0): IO registers at addr 0xFEB80000
(II) intel(0): 2 display pipes available.
(==) intel(0): Using EXA for acceleration
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Reloading /usr/lib/xorg/modules//libint10.so
(II) intel(0): initializing int10
(WW) intel(0): Bad V_BIOS checksum
(II) intel(0): Primary V_BIOS segment is: 0xc000
(II) intel(0): VESA BIOS detected
(II) intel(0): VESA VBE Version 3.0
(II) intel(0): VESA VBE Total Mem: 7872 kB
(II) intel(0): VESA VBE OEM: Intel(r) 82945GM Chipset Family Graphics Chip Accelerated VGA BIOS
(II) intel(0): VESA VBE OEM Software Rev: 1.0
(II) intel(0): VESA VBE OEM Vendor: Intel Corporation
(II) intel(0): VESA VBE OEM Product: Intel(r) 82945GM Chipset Family Graphics Controller
(II) intel(0): VESA VBE OEM Product Rev: Hardware Version 0.0
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Module "ddc" already built-in
(II) Loading sub module "i2c"
(II) LoadModule: "i2c"
(II) Module "i2c" already built-in
(II) intel(0): Output VGA using monitor section VGA
(**) intel(0): Option "Ignore" "True"
(II) intel(0): I2C bus "SDVOCTRL_E for SDVOB" initialized.
(II) intel(0): I2C device "SDVOCTRL_E for SDVOB:SDVO Controller B" registered at address 0x70.
(II) intel(0): I2C bus "SDVOB DDC Bus" initialized.
(II) intel(0): Output TMDS-1 using monitor section TMDS-1
(**) intel(0): Option "Ignore" "False"
(II) intel(0): SDVOB: device VID/DID: 02:47.02, clock range 25.0MHz - 165.0MHz
(II) intel(0): SDVOB: 1 input channel
(II) intel(0): SDVOB: TMDS0 output reported
(II) intel(0): Current clock rate multiplier: 2
(II) intel(0): I2C device "SDVOB DDC Bus:ddc2" registered at address 0xA0.
(II) intel(0): EDID vendor "AIC", prod id 37968
(II) intel(0): Using hsync ranges from config file
(II) intel(0): Using vrefresh ranges from config file
(II) intel(0): Printing DDC gathered Modelines:
(II) intel(0): Modeline "1280x1024"x0.0 135.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
(II) intel(0): Modeline "640x350"x0.0 25.18 640 656 752 800 350 387 389 449 +hsync -vsync (31.5 kHz)
(II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
(II) intel(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
(II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
(II) intel(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz)
(II) intel(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz)
(II) intel(0): Modeline "640x480"x0.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
(II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
(II) intel(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
(II) intel(0): Modeline "1024x768"x0.0 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz)
(II) intel(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz)
(II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
(II) intel(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz)
(II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
(II) intel(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz)
(II) intel(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz)
(II) intel(0): Modeline "1280x1024"x60.0 108.88 1280 1360 1496 1712 1024 1025 1028 1060 -hsync +vsync (63.6 kHz)
(II) intel(0): Modeline "1280x1024"x70.0 128.94 1280 1368 1504 1728 1024 1025 1028 1066 -hsync +vsync (74.6 kHz)
(II) intel(0): Modeline "1280x1024"x72.0 132.75 1280 1368 1504 1728 1024 1025 1028 1067 -hsync +vsync (76.8 kHz)
(II) intel(0): EDID vendor "AIC", prod id 37968
(II) intel(0): Output TMDS-1 connected
(II) intel(0): Using user preference for initial modes
(II) intel(0): Output TMDS-1 using initial mode 1280x1024
(II) intel(0): Monitoring connected displays enabled
(II) intel(0): detected 256 kB GTT.
(II) intel(0): detected 7932 kB stolen memory.
(==) intel(0): video overlay key set to 0x101fe
(==) intel(0): Will not try to enable page flipping
(==) intel(0): Triple buffering disabled
(==) intel(0): Intel XvMC decoder disabled
(==) intel(0): Using gamma correction (1.0, 1.0, 1.0)
(**) intel(0): Display dimensions: (336, 269) mm
(WW) intel(0): Probed monitor is 370x300 mm, using Displaysize 336x269 mm
(**) intel(0): DPI set to (120, 151)
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "exa"
(II) LoadModule: "exa"
(II) Loading /usr/lib/xorg/modules//libexa.so
(II) Module exa: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 2.4.0
ABI class: X.Org Video Driver, version 4.1
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(II) intel(0): Comparing regs from server start up to After PreInit
(WW) intel(0): Register 0x70024 (PIPEASTAT) changed from 0x00020203 to 0x00020000
(WW) intel(0): PIPEASTAT before: status: VBLANK_INT_ENABLE VSYNC_INT_STATUS VBLANK_INT_STATUS OREG_UPDATE_STATUS
(WW) intel(0): PIPEASTAT after: status: VBLANK_INT_ENABLE
(II) Loading sub module "dri"
(II) LoadModule: "dri"
(II) Reloading /usr/lib/xorg/modules/extensions//libdri.so
(==) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b](OprD)
[5] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b](OprD)
[6] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b](OprD)
[7] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[8] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[9] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b](OprU)
[10] 0 0 0x000003c0 - 0x000003df (0x20) IS[b](OprU)
(II) intel(0): Kernel reported 238848 total, 1 used
(II) intel(0): I830CheckAvailableMemory: 955388 kB available
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 10, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 10, (OK)
drmOpenByBusid: Searching for BusID pci:0000:00:02.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 10, (OK)
drmOpenByBusid: drmOpenMinor returns 10
drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
(II) [drm] DRM interface version 1.3
(II) [drm] DRM open master succeeded.
(II) intel(0): [drm] Using the DRM lock SAREA also for drawables.
(II) intel(0): [drm] framebuffer mapped by ddx driver
(II) intel(0): [drm] added 1 reserved context for kernel
(II) intel(0): X context handle = 0x1
(II) intel(0): [drm] installed DRM signal handler
(**) intel(0): Framebuffer compression enabled
(**) intel(0): Tiling enabled
(==) intel(0): VideoRam: 262144 KB
(II) intel(0): Attempting memory allocation with tiled buffers.
(II) intel(0): Tiled allocation successful.
(II) intel(0): [drm] Registers = 0xfeb80000
(II) intel(0): [drm] ring buffer = 0xd0000000
(II) intel(0): [drm] mapped front buffer at 0xd1000000, handle = 0xd1000000
(II) intel(0): [drm] mapped back buffer at 0xd5000000, handle = 0xd5000000
(II) intel(0): [drm] mapped depth buffer at 0xd6000000, handle = 0xd6000000
(II) intel(0): [drm] mapped classic textures at 0xd7000000, handle = 0xd7000000
(II) intel(0): [drm] Initialized kernel agp heap manager, 33554432
(II) intel(0): [dri] visual configs initialized
(II) intel(0): Page Flipping disabled
(II) intel(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(II) EXA(0): Offscreen pixmap area of 39321600 bytes
(II) EXA(0): Driver registered support for the following operations:
(II) Solid
(II) Copy
(II) Composite (RENDER acceleration)
(==) intel(0): Backing store disabled
(==) intel(0): Silken mouse enabled
(II) intel(0): Initializing HW Cursor
(II) intel(0): [DRI] installation complete
(II) intel(0): Current clock rate multiplier: 2
(II) intel(0): xf86BindGARTMemory: bind key 0 at 0x01000000 (pgoffset 4096)
(II) intel(0): xf86BindGARTMemory: bind key 1 at 0x02000000 (pgoffset 8192)
(II) intel(0): xf86BindGARTMemory: bind key 2 at 0x05000000 (pgoffset 20480)
(II) intel(0): xf86BindGARTMemory: bind key 3 at 0x06000000 (pgoffset 24576)
(II) intel(0): xf86BindGARTMemory: bind key 4 at 0x07000000 (pgoffset 28672)
(II) intel(0): Fixed memory allocation layout:
(II) intel(0): 0x00000000-0x0001ffff: ring buffer (128 kB)
(II) intel(0): 0x00020000-0x0061ffff: compressed frame buffer (6144 kB, 0x000000003f820000 physical
(II) intel(0): 0x00620000-0x00620fff: compressed ll buffer (4 kB, 0x000000003fe20000 physical
(II) intel(0): 0x00621000-0x0062afff: HW cursors (40 kB, 0x000000003fe21000 physical
(II) intel(0): 0x0062b000-0x00632fff: logical 3D context (32 kB)
(II) intel(0): 0x00633000-0x00633fff: overlay registers (4 kB, 0x000000003fe33000 physical
(II) intel(0): 0x007bf000: end of stolen memory
(II) intel(0): 0x01000000-0x01ffffff: front buffer (12800 kB) X tiled
(II) intel(0): 0x02000000-0x0457ffff: exa offscreen (38400 kB)
(II) intel(0): 0x05000000-0x05ffffff: back buffer (12800 kB) X tiled
(II) intel(0): 0x06000000-0x06ffffff: depth buffer (12800 kB) X tiled
(II) intel(0): 0x07000000-0x08ffffff: classic textures (32768 kB)
(II) intel(0): 0x10000000: end of aperture
(WW) intel(0): ESR is 0x00000010, page table error
(WW) intel(0): PGTBL_ER is 0x00000010, display A pte
(WW) intel(0): Existing errors found in hardware state.
(II) intel(0): Output configuration:
(II) intel(0): Pipe A is on
(II) intel(0): Display plane A is now enabled and connected to pipe A.
(II) intel(0): Pipe B is off
(II) intel(0): Display plane B is now disabled and connected to pipe B.
(II) intel(0): Output TMDS-1 is connected to pipe A
(II) intel(0): [drm] dma control initialized, using IRQ 16
(II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
(II) intel(0): DPMS enabled
(II) intel(0): Set up textured video
(II) intel(0): Set up overlay video
(II) intel(0): direct rendering: Enabled
(WW) intel(0): Option "monitor-LVDS" is not used
(--) RandR disabled
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 11, (OK)
drmOpenByBusid: Searching for BusID pci:0000:00:02.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 11, (OK)
drmOpenByBusid: drmOpenMinor returns 11
drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
(II) AIGLX: enabled GLX_MESA_copy_sub_buffer
(II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
(II) AIGLX: enabled GLX_texture_from_pixmap with driver support
(II) AIGLX: Loaded and initialized /usr/lib/xorg/modules/dri/i915_dri.so
(II) GLX: Initialized DRI GL provider for screen 0
(II) intel(0): Setting screen physical size to 376 x 301
(**) Option "Protocol" "IMPS/2"
(**) Mouse0: Device: "/dev/input/mice"
(**) Mouse0: Protocol: "IMPS/2"
(**) Option "CorePointer"
(**) Mouse0: always reports core events
(**) Option "Device" "/dev/input/mice"
(==) Mouse0: Emulate3Buttons, Emulate3Timeout: 50
(**) Option "ZAxisMapping" "4 5 6 7"
(**) Mouse0: ZAxisMapping: buttons 4, 5, 6 and 7
(**) Mouse0: Buttons: 11
(**) Mouse0: Sensitivity: 1
(**) Option "CoreKeyboard"
(**) Keyboard0: always reports core events
(**) Option "Protocol" "standard"
(**) Keyboard0: Protocol: standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xorg"
(**) Keyboard0: XkbRules: "xorg"
(**) Option "XkbModel" "pc105"
(**) Keyboard0: XkbModel: "pc105"
(**) Option "XkbLayout" "us"
(**) Keyboard0: XkbLayout: "us"
(**) Option "CustomKeycodes" "off"
(**) Keyboard0: CustomKeycodes disabled
(II) evaluating device (Mouse0)
(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
(II) evaluating device (Keyboard0)
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(II) Mouse0: ps2EnableDataReporting: succeeded
(II) UnloadModule: "mouse"
(II) UnloadModule: "kbd"
(II) intel(0): xf86UnbindGARTMemory: unbind key 0
(II) intel(0): xf86UnbindGARTMemory: unbind key 1
(II) intel(0): xf86UnbindGARTMemory: unbind key 2
(II) intel(0): xf86UnbindGARTMemory: unbind key 3
(II) intel(0): xf86UnbindGARTMemory: unbind key 4
(II) intel(0): [drm] removed 1 reserved context for kernel
(II) intel(0): [drm] unmapping 8192 bytes of SAREA 0xf8264000 at 0xb7a3f000
(II) intel(0): [drm] Closed DRM master.
Thanks in advance!
Last edited by Marcel- (2010-02-16 02:06:08)Sorry for bumping this old topic, but I managed to workaround this problem (still the same hardware).
The last year I used xf86-video-vesa, as the mentioned problem didn't show up using this driver (and screen rendering in X wasn't slow, so I was fine with that). After getting disturbed by some random screen flickering after KMS was enabled by default (while still adding video=791 and using xf86-video-vesa), I decided to try xf86-video-intel again combined with KMS.
After fixing the above misconfigurations I rebooted and my screen was dropped in a console using 1280x1024@75Hz. Using several consoles for a few hours worked flawlessly. But when starting X (with an xorg.conf generated via X -configure and disabling input hotplugging) things got worse.
At first, I didn't notice anything using black-on-white xterms. But after running Chromium I saw these flickering pixels again, a horizontal line (the bottom of the back button) showed pixels that changed colors rapidly. The problem appeared to be dependent on the contents of the screen: dark, patterned surfaces like several of these pictures acquired a lot of green pixels moving fast (I hope this is comprehensible), the "Floating Diamond" also got some rapidly changing pixels. Moreover, I got a small black line flashing every now and then.
I thought that the refresh rate might be too high for the Intel GPU to cope with (the monitor should be able to handle this). After way too much searching, I discovered how to set a refresh rate in KMS: I added
kernel /vmlinuz26 root=[...] ro video=1280x1024@60
^^^^^^^^^^^^^^^^^^
to /boot/grub/menu.lst.
After a reboot the refresh rate indeed dropped to 60 Hz. X stubbornly refused to stick to this (I thought it merely used the graphical mode KMS set). A bit more googling resulted in the following adjustments to xorg.conf:
Section "Monitor"
Identifier "Neovo F-419"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
HorizSync 31.5-64.3
VertRefresh 50-70
EndSection
Section "Device"
Identifier "Card0"
Driver "intel"
Option "monitor-DVI1" "Neovo F-419"
VendorName "Intel Corporation"
BoardName "Mobile 945GME Express Integrated Graphics Controller"
BusID "PCI:0:2:0"
EndSection
Now my X runs at 60 Hz and... the rapidly changing pixels seem to be gone (for half an hour at the moment).
Only question that remains is: why didn't I have these glitches outside of X? Is it because text screens have relatively large areas with the same color? After all, this 'noise' was best visible on heavily patterned areas.
And one last question: should I mention this somewhere upstream (e.g. at the xf86-video-intel people or at LKML)? -
External displays with similar pixel density to 17" MBP display?
I've got a 17" MacBook Pro, native resolution 1920x1200, which is quite high in terms of pixel density. I have a 24" external Samsung display, also 1920x1200, which means the pixel density is lower. It works fine, but (as you might expect), screen items increase in size rather noticeably when I drag from the laptop display to the external display. (The 24" LCD Apple Cinema Display is also 1920x1200, so the same thing would happen). I've been looking all over the place, and I can't seem to find an external display in the 20-24" range that has a resolution higher than 1920x1200. Ideally I'd like to find a display with the same amazing pixel density, so everything is the same size on both my laptop display and on the external display. I don't know what that would be--probably something like 2048x1152 on a 20" or 22", and 2560x1600 for a 24". Even Apple's 30" Cinema Display at 2560x1600 (or what I imagine will be the new 27" LCD coming out later this summer, probably at 2560x1600) would suffer from this problem, because while the resolution is great, the screen size is so large that the pixel density is lower and once again screen items would increase in size when moved from the laptop monitor to the external monitor. I don't really care about screen size or cost. I'd buy a 20" display, or a 30" display, at pretty much any price, if the pixel density were identical to my MacBook Pro. Anybody know where I can find something like this?
The pixel densities of the 15" hi-res MBP at 1680 x 1050 and the 17" at 1920 x 1200 are really quite extreme — the 17" slightly more so than the 15". To read the "fine print" on those screens without a resolution-independent user interface (which the Mac OS doesn't yet offer), most users have to sit closer to those displays than they'd want to be to a 27" or 30" display, simply because for a viewer sitting that close to it, the bigger display would extend outward beyond the central field of sharply focused vision. One would constantly be leaning forward and back: in to read the menus or palettes and then out to see the whole screen. That would be pretty tiring. Thus I think it's quite unlikely that we'll ever see 30", 27" or maybe even 24" displays from Apple or anyone else at the same pixel density as the highest-resolution MBPs: 133.2 pixels per inch for the 17" and 128.6 for the 15", compared with 108.8 for the 27" iMac and 97.7 for the 30" Cinema Display). The current standard-resolution 15" MBP at 110.3 actually has a lower pixel density than the 13", at 113.5.
Interestingly, the current 24" Apple LED-backlit display at 113.2 has almost exactly the same pixel density as the 13" MacBook Pro screen. For someone who wanted things to stay the same size when moving from screen to screen, that would be an ideal pairing. But the 13" MBP sure wouldn't be any match for the 17" in terms of screen real estate when each was being used as a stand-alone portable. -
i want to import massively metadata to jpeg files.
Can you help me to import metadata such as keywords.
I have already tried with xmp toolkit of Adobe but the metadata
is not readable from file info in Adobe Photoshop CS2
What seems to be the problem ?
I 'm using windows xpI can probably help with this.
I have a script called TagFromFilename that can apply fill in the details that can be extracted from the file path if the .wavs are stored in the layout <Album Artist>\<Album>\[D-]## <Name>[ - <Artist>].<Ext> where D is an optional leading disc number and <Artist> is an optional trailing artist (otherwise both artist and album artist are set to the grandparent folder). You just need to make sure that before you add the tracks to iTunes, that it won't rename the files. You can do this by turning off the Keep option if the files are inside the media folder, or the copy option if the tracks are located outside.
Alternatively I have another script called ExportImport which allows for almost any editable to be adjusted, as long as you can export the internal track IDs of each track and then marry them up with the data you want to import. See Batch Add Comments Tag Solution? for a previous example of how if might be done. I'll gladly go into more detail if you tell me what fields you already have and what identifying information is present.
tt2 -
Hi,
Is there a way of changing pixel colours in (say) a Graphics (or image) object? I want to be able to create a Graphics object, and then change pixel colours, as determined by the results of a numerical simulation, as results are generated.
Any help appreciated!You can use the drawLine to draw a one-pixel line in the right place.
Alternatively (and probably better) use an int array to contain your image data and use a MemoryImageSource to generate an Image for display from that. -
DNG file modification date not changed by writing metadata?
I use LR 2.7 on Windows XP. To my surprise, I just noticed that writing metadata updates (e.g., new keywords) from LR to the DNG files does NOT appear to update the file modification date, which suggests obvious issues for backup strategies (yes, I understand that a changed modification date introduces other backup issues). I have verfifed that the metatdata does indeed change in the DNG files, so I am mystified. Can someone shed some light on this? Thanks.
js
www.johnshorephoto.comYes, I explicitely invoke "save metadata to file". Furthemore, I have checked the behavior by (a) modifying DNGs in LR; (b) saving the metatdata to the DNG; (c) creating a new LR catalog and importing the revised DNGs. The metadata changes do show up in the re-imported DNGs (and the metadata field "Metadata Date" correctly shows the recent change). Morevover, the file sizes do change (wth the metadata changes) even though the modification dates shown in windows explorer do not change.
However, I just redid the experiment to double check, and discovered an important clue - the mysterious behavior occurs when the DNG files are on a NAS device (in particular a Netgear ReadyNAS Duo. To summarize:
- When the DNG files are on a local hard drive, the file modification dates change as expected
- When the DNG files are non local (i.e., on the network but on a NAS device), the file modification dates do not change even though the file sizes do change;
What's more, I see the same behavior when accessing the DNGs via Adobe Bridge (CS5) - i.e., if I change the metadata, I'm asked if I want to apply the metadata changes to the DNG, and I say yes (and confirm by looking via Bridge at a copy of the changed file). On a local disk, the file modificaiton dates change (as do the modification date displayed in Bridge), but if the files are on the NAS, the modification dates do not.
Any additional thoughts?
js -
I am trying to change pixels to 1920x1920 in iphoto. I used crop, custom and it change. When I looked at my photo information it was 2000x2000. I have tried numerious times to no avail.....! I need the 1920 specific size for art show jurying. Love the ease of the iphoto, am new to mac, used adobe before, but seems it is better. So, any advice???? Thanks
crop to any square ratio (1x1 -- 1920x1920 -- any square) and then export the photo using a custom size with the maximum dimension of 1920 - cropping is actually by default just a ratio not a size - the size is set during export
LN -
How do I change the raw image to jpeg with element 6
How do I change the raw image to jpeg using element 6? I am using a canon 10D camera.
From the Editor choose:
File >> Open
Then navigate to your raw file
When the image appears in the converter use the sliders to make your raw adjustments, then click open image.
From the Editor use:
File >> Save As >> jpeg
-
How do I change ipage document into a jpeg document to email?
How do IU change ipage document into a jpeg document to email?
Pages documents can be exported to these formats:
PDF, Word, RTF, Plain Text, or ePub
Not JPG or JPEG.
From the Pages menu bar click File > Export -
How do I change pixel size?
Technically, you can't change the size of an image screen pixel. You can use resampling to change the number of pixels representing a current screen pixel (upsample means more pixels are used to represent a pixel, downsample means fewer).
You can change the size of an image pixel when it's printed by modifying the DPI (dots per inch). The bigger a pixel is, the fewer will fit in an inch, and vice versa. -
I often have requests for images to be sent within certain parameters: such as "no longer than 1200 pixels on longest side + jpeg format + file size no less than 5 mb." Images will be viewed on a large stand up screen. My original image sizes are usually around 22 mb. When I use Export and specify 1200 pixels (quality setting is all the way over to 12), Save the file to a folder on the desktop, and then open the image in Preview, Inspector shows that the file size is now 233 KB. How do I meet all specifications without reducing the image size so drastically?
Thank you.. Pardon, it reduced it down to 833 KB, not 233 (I mixed it up with another image) from the Original image of 22 MB, RAW. Should it reduce it down that much??
That will depend on the amount of of detail in your jpeg. Given a certain pixels size and level of quality, a jpeg with many details will require a larger filesize than a jpeg with large plain regions of constant color.
Is 833 KB a big enough file size to view on a big screen?
The file size is really unimportant for the quality. What will count is the pixel size and jpeg quality you set. What is the pixel size of the large screen? That should match the pixel size you are using in your export preset. 1200 longest dimension is extremely unlikely for a large screen. Even the 17" display of my MacBook Pro has a larger pixelsize of 1920x1200.
I am sharing William Lloyd's doubts, that the specifications you were given are correct. I'd try to export with a larger pixelsize and a high jpeg quality - perhaps 10.
If you export with 10 Megapixel and a good jpeg quality, you will probably get a 5MB file, not that the size should matter. -
Revision: 13840
Revision: 13840
Author: [email protected]
Date: 2010-01-27 21:20:12 -0800 (Wed, 27 Jan 2010)
Log Message:
Changed the plugin metadata media factory key to an ObjectIdentifier per Brian's request.
Modified Paths:
osmf/trunk/framework/OSMF/org/osmf/metadata/MetadataNamespaces.as
osmf/trunk/plugins/SMILPlugin/org/osmf/smil/loader/SMILLoader.asRemember that Arch Arm is a different distribution, but we try to bend the rules and provide limited support for them. This may or may not be unique to Arch Arm, so you might try asking on their forums as well.
Maybe you are looking for
-
Filename of inbound CSV in UDF
Hello, I would like to insert the filename of an inbound (CSV) file into a UDF in B1. Scenario: F.AnySystem to B1. All the field mapping of the fields inside the file is done and works perfectly. But how can i get the filename? Does anybody have a hi
-
HT4623 Is there virus protection for the iPad? Where would I find it? Thankd
Is there virus protection for the iPad available? Where would I find it please? Thanks CathyJ248
-
How can i use ipad after erasing it
I cannot access my ipad after I erased it, I don't have access to the old email and the pass word and security questions aren't working, what can I do so that I can set it up again?
-
Firefox crashes when using adobe reader retriving pdf files
For instance when I tried to get a pdf file from the IRS web site using adobe reader firefox crashes it also does the same thing on other sites with pdf files what would be the problem and how could I resolve this issue.
-
How to create an animation that rotates in response to the mouse position?
Hey guys, I'm designing a home page that is centered around a logo. I need the logo to rotate around 360 degrees as the mouse explores the area around it. I'm attaching a quick sketch explaining the type of motion I need, a mockup of what th