Slow transitions in 4.3.1

Since I upgraded the firmware on my iphone 4 from 4.1 to 4.3.1 I noticed that is slower and is very noticeable. I have restored 10,000 times and I think that is a problem of Ios. I hope Apple fix this soon because the new devices that are providing (just opened) and have lag. Do not understand how can this be happening. Thanks for your answers.

Not clear what you are trying to accomplish. There is no FTP in the BT profiles on the iPhone so you cannot exchange data via iOS and BT. There are some apps that allow 2 iPhones to play games against each other or swap photos but they handle the handshake between devices within the app.

Similar Messages

Slow transition from Screen Recording back to Captivate Tool

I am new to captivate so excuse me if I do not know all the training/tool jargon yet.
I am trying to do a screen capture of a web based tool to train a client. I have done a few of these, and they worked pretty well, but longer recording seem to bog down. Obviously this makes sense, but the current recording is taking forever and I can not tell if the software is locked up or working. I just get the spinning ball on the mac when I try to bring up Captivate.
It seems like in the past if I hit Command Return, it started closing the recording. In the past when it acted like it was hanging up, I would just click to open Captive and it would show me a that it was working. Currently I am not getting that when I bring up the captivate software. I still see the red outline for the recording area and this has been 30 minutes or so. Is it possible that it is still working or do you think there is a problem?
The screen recording was long, but this seems really long to transition.
So I guess I need to know if this is common. And second what I should do now? Should I let things run over night or is the tool still recording? If so this could just keep recording and fill up the hard drive (I guess).
Any ways to cancel the recording if it is still recording? Is there any way to check this? Is there a realistic (or estimated timeframe) to wait for this transition? For every minute you can expect to wit 2 minutes to finalize and move the recording over to captivate (or similar). Is there another way to end things or know what is going on?
Any advice would be greatly appreciated.
Thanks.
Maybe I should do screen recordings with quick time and then add audio in captivate. Thoughts?

What are you upload/download speeds at each location?

Slow Transition on the ipad

Greetings,
I've been writing an app in AIR 2.7 for the ipad. I've run into a performance problem when transitioning from one view to another. It takes about 4 seconds before the animation start. The target view has about 15 elements (a mix if list/images and textareas). I believe the problem is in the creation of the elements before the animation starts.
Has anyone else run into this situation? If so...suggestings?
--Klee

Shongruden,
So here is the bulk of the mxml. I didnt paste the contents of the script tag because I dont think it is relevant at this point. If you think it is, let me know and I'll post it as well. This is really a prototype with static data.
<s:states>
<s:State name="landscape"/>
<s:State name="portrait"/>
</s:states>
<fx:Declarations>

<fx:XML id="body" xmlns="">
<body>Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum. It is a long established fact that a reader will be distracted by the readable content of a page when looking at its layout. The point of using Lorem Ipsum is that it has a more-or-less normal distribution of letters, as opposed to using 'Content here, content here', making it look like readable English. Many desktop publishing packages and web page editors now use Lorem Ipsum as their default model text, and a search for 'lorem ipsum' will uncover many web sites still in their infancy. Various versions have evolved over the years, sometimes by accident, sometimes on purpose (injected humour and the like). Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots in a piece of classical Latin literature from 45 BC, making it over 2000 years old. Richard McClintock, a Latin professor at Hampden-Sydney College in Virginia, looked up one of the more obscure Latin words, consectetur, from a Lorem Ipsum passage, and going through the cites of the word in classical literature, discovered the undoubtable source. Lorem Ipsum comes from sections 1.10.32 and 1.10.33 of "de Finibus Bonorum et Malorum" (The Extremes of Good and Evil) by Cicero, written in 45 BC. This book is a treatise on the theory of ethics, very popular during the Renaissance. The first line of Lorem Ipsum, "Lorem ipsum dolor sit amet..", comes from a line in section 1.10.32. The standard chunk of Lorem Ipsum used since the 1500s is reproduced below for those interested. Sections 1.10.32 and 1.10.33 from "de Finibus Bonorum et Malorum" by Cicero are also reproduced in their exact original form, accompanied by English versions from the 1914 translation by H. Rackham.</body>
</fx:XML>
<fx:Array id="articles">
<fx:Object label="This is the title" icon="@Embed('/assets/article_icon.png')" shortDescription="Lorem Ipsum is simply dummy text of the printing and typesetting industry."/>
<fx:Object label="This is the title" icon="@Embed('/assets/article_icon.png')" shortDescription="Lorem Ipsum is simply dummy text of the printing and typesetting industry."/>
<fx:Object label="This is the title" icon="@Embed('/assets/article_icon.png')" shortDescription="Lorem Ipsum is simply dummy text of the printing and typesetting industry."/>
<fx:Object label="This is the title" icon="@Embed('/assets/article_icon.png')" shortDescription="Lorem Ipsum is simply dummy text of the printing and typesetting industry."/>
<fx:Object label="This is the title" icon="@Embed('/assets/article_icon.png')" shortDescription="Lorem Ipsum is simply dummy text of the printing and typesetting industry."/>
<fx:Object label="This is the title" icon="@Embed('/assets/article_icon.png')" shortDescription="Lorem Ipsum is simply dummy text of the printing and typesetting industry."/>
<fx:Object label="This is the title" icon="@Embed('/assets/article_icon.png')" shortDescription="Lorem Ipsum is simply dummy text of the printing and typesetting industry."/>
<fx:Object label="This is the title" icon="@Embed('/assets/article_icon.png')" shortDescription="Lorem Ipsum is simply dummy text of the printing and typesetting industry."/>
<fx:Object label="This is the title" icon="@Embed('/assets/article_icon.png')" shortDescription="Lorem Ipsum is simply dummy text of the printing and typesetting industry."/>
<fx:Object label="This is the title" icon="@Embed('/assets/article_icon.png')" shortDescription="Lorem Ipsum is simply dummy text of the printing and typesetting industry."/>
<fx:Object label="This is the title" icon="@Embed('/assets/article_icon.png')" shortDescription="Lorem Ipsum is simply dummy text of the printing and typesetting industry."/>
<fx:Object label="This is the title" icon="@Embed('/assets/article_icon.png')" shortDescription="Lorem Ipsum is simply dummy text of the printing and typesetting industry."/>
<fx:Object label="This is the title" icon="@Embed('/assets/article_icon.png')" shortDescription="Lorem Ipsum is simply dummy text of the printing and typesetting industry."/>
<fx:Object label="This is the title" icon="@Embed('/assets/article_icon.png')" shortDescription="Lorem Ipsum is simply dummy text of the printing and typesetting industry."/>
<fx:Object label="This is the title" icon="@Embed('/assets/article_icon.png')" shortDescription="Lorem Ipsum is simply dummy text of the printing and typesetting industry."/>
<fx:Object label="This is the title" icon="@Embed('/assets/article_icon.png')" shortDescription="Lorem Ipsum is simply dummy text of the printing and typesetting industry."/>
<fx:Object label="This is the title" icon="@Embed('/assets/article_icon.png')" shortDescription="Lorem Ipsum is simply dummy text of the printing and typesetting industry."/>
<fx:Object label="This is the title" icon="@Embed('/assets/article_icon.png')" shortDescription="Lorem Ipsum is simply dummy text of the printing and typesetting industry."/>
<fx:Object label="This is the title" icon="@Embed('/assets/article_icon.png')" shortDescription="Lorem Ipsum is simply dummy text of the printing and typesetting industry."/>
</fx:Array>
</fx:Declarations>
<fx:Style>
@namespace s "library://ns.adobe.com/flex/spark";
.labelStyle {
color: #0000ff;
alpha:.4
.messageStyle {
color: #000000;
alpha:.4;
fontSize:10;
#articleHeader{
fontSize:30;
color:black;
borderVisible:false;
contentBackgroundColor:white;
editable:false;
#articleBody{
fontSize:16;
color:black;
borderVisible:false;
contentBackgroundColor:white;
editable:false;
#categoryName{
paddingTop:10;
fontSize:25;
paddingLeft:5;
backgroundColor:#cecece;
</fx:Style>
<s:List id="categoryList" left="0" top="95" width="320" height="647" click="list1_clickHandler(event)" includeIn="landscape">
<s:itemRenderer>
 <fx:Component>
 <s:IconItemRenderer labelField="label" messageStyleName="messageStyle" messageField="shortDescription" iconField="icon" />
 </fx:Component>
</s:itemRenderer>
</s:List>
<s:TextArea id="articleHeader" x="328" y="43" width="528" height="127" editable="false" selectable="false" text="Title" x.landscape="328" y.landscape="53" width.landscape="516" x.portrait="5" y.portrait="52"/>
<s:Line x="0" y="199" width="687" xFrom="330" xTo="400" yFrom="10" yTo="10" x.landscape="0" y.landscape="224" x.portrait="-323" y.portrait="208">
<s:stroke>
 <s:SolidColorStroke color="0x000000" weight="1"/>
</s:stroke>
</s:Line>
<s:Line includeIn="portrait" x="135" y="42" xFrom="400" xTo="400" yFrom="10" yTo="170">
<s:stroke>
 <s:SolidColorStroke color="0x000000" weight="1"/>
 </s:stroke>
</s:Line>
<s:Line x="-80" y="38" height="694" xFrom="400" xTo="400" yFrom="10" yTo="724" includeIn="landscape">
<s:stroke>
 <s:SolidColorStroke color="0x000000" weight="1"/>
</s:stroke>
</s:Line>
<s:Image includeIn="portrait" x="541" y="52" width="50" cacheAsBitmap="true" source="@Embed('/assets/my headshot.png')"/>
<s:Image includeIn="portrait" x="589" y="162" width="40" cacheAsBitmap="true" source="@Embed('/assets/Google-icon.png')"/
<s:Image includeIn="portrait" x="541" y="114" width="40" cacheAsBitmap="true" source="@Embed('/assets/Facebook-icon.png')"/>
<s:Image includeIn="portrait" x="589" y="114" width="40" cacheAsBitmap="true" source="@Embed('/assets/Digg-icon.png')"/>
<s:Image includeIn="portrait" x="633" y="114" width="40" cacheAsBitmap="true" source="@Embed('/assets/Linked-In-icon.png')"/>
<s:Image includeIn="portrait" x="541" y="162" width="40" cacheAsBitmap="true" source="@Embed('/assets/Google-icon.png')"/>
<s:Image includeIn="portrait" x="634" y="162" width="40" cacheAsBitmap="true" source="@Embed('/assets/Share-icon.png')"/>
<s:Image x="810" y="180" width="39" height="22" cacheAsBitmap="true" source="@Embed('/assets/Actions-bookmark-new-icon.png')" x.landscape="323" y.landscape="203" x.portrait="487" y.portrait="189"/>

<s:Image x="474" y="178" width="20" height="20" cacheAsBitmap="true" source="@Embed('/assets/star_gold.png')" x.portrait="151" y.portrait="187"/>
<s:Image x="527" y="178" width="20" height="20" cacheAsBitmap="true" source="@Embed('/assets/star_gold.png')" x.portrait="204" y.portrait="187"/>
<s:Image x="500" y="178" width="20" height="20" cacheAsBitmap="true" source="@Embed('/assets/star_gold.png')" x.portrait="177" y.portrait="187"/>
<s:TextArea id="articleBody" right="0" bottom="42" width="696" height="486" editable="false" selectable="false" text="" right.landscape="0" bottom.landscape="42" height.landscape="469" right.portrait="10" bottom.portrait="50" width.portrait="753" height.portrait="739"/>
<s:Label includeIn="portrait" x="597" y="60" width="94" text="Don Reisinger"/>
<s:Label x="332" y="183" width="183" fontSize="12" text="Publish Date: 7/27/2011"
x.portrait="9" y.portrait="192"/>
<components:actionBar id="header" x="0" y="0" cacheAsBitmap="true"/>
<components:CategorySelector id="cats" visible="false" x="452" y="39"/>
<s:Label id="categoryName" x="0" y="50" width="320" height="46" color="#08254C" fontWeight="bold" text="Security" includeIn="landscape"/>
<components:MyStuffSelector id="myStuff" visible="false" x="578" y="40"/>
<s:Button x="857" y="714" width="75" height="30" label="ad" click="showAd()" x.portrait="683" y.portrait="962"/>
<s:Rect id="layover" visible="true" left="0" right="0" top="0" bottom="0" left.portrait="0" right.portrait="0" top.portrait="0" bottom.portrait="0">
<s:stroke>
 <s:SolidColorStroke color="0x000000" weight="1"/>
</s:stroke>
<s:fill>
 <s:SolidColor color="0x000000" alpha=".5"/>
</s:fill>
</s:Rect>
<s:Image id="large_ad" visible="true" cacheAsBitmap="true" click="hideAd()" horizontalCenter.landscape="0" source="/assets/layover_ad.png"
verticalCenter.landscape="0" horizontalCenter.portrait="0" verticalCenter.portrait="0"/>
<components:publishShareBlock includeIn="landscape" x="852" y="51">
</components:publishShareBlock>

Transitions slow on some clips

I am having a problem with slow transitions on some clips.
Seems like on a clip I bring in from my Sony HVR-A1U it is fine.
But on clips I have converted from 8mm film to MiniDV then pulled in from the same camera they are like 10 times slower.
Can anyone tell me why?
And is there a fix for this?

.. Clarification..
a clear discription of the problem sometimes help to find an answer..
so, you do mean, that little red bar in the clip, indicating the 'rendering' of an effect, moves signficant slower...?
usually, all these process makes widely use of socalled temp-files, whcih are located onto the internal drive (or, that part of your HDD, where your System is located, if you partioned the drive...)
if you go under 10 - 20 GB of free disk space, iM slows down 'til freeze...
to speed up all processes, be sure, your Mac can 'breath'... ;))

Problem with unstable and slow SWFs

Good evening,
Some of my users are reporting problems with the SWF output of my intensive Captive file which includes significant software simulation. I knew that these files were going to be resource intensive due to the nature of the project, but I felt comfortable with system requirements of at least 2 gb RAM and a mid-range processor.
Unfortunately, some of my users who meet this criteria are reporting problems including text animations not playing in full and slow slide transitions. I cannot replicate this problem on any of my machines.
I have been playing around trying to compress images as much as possible and otherwise reduce file size. What else can be done? What are the top five things I can do to remedy this problem?
My presentation is about 50 slides and the SWF output is about 4.5 mb.
Thanks

I've seen this type of thing many times, especially in corporate environments.
My top suggestions:
If you've taken all reasonable steps to make your project as web-friendly as possible by this time, don't make any more changes to your project until you've exhausted the possibilities below. It is most likely NOT your project that is at fault.
Find out more details from the users that are complaining. If at all possible, actually go and sit with them to watch the behaviour they're talking about. Don't believe everything you hear.
Check that users are on the correct version of Flash Player. For example, Flash Player 10 can play significantly better than Flash 9.
Ask the user to check defragmentation on their PC. Most users DON'T know how to do this and never defragment. As a result, I have seen PCs in corporate IT environments that had not been defragmented in years. Their hard drive showed up mostly red when the fragmentation analysis was done. This lack of PC housekeeping can contribute to many issues, especially with Flash or multimedia playback. Ask the user to defragment 2 or 3 times to be on the safe side.
Watch the CPU on Task Manager while the PC is playing the Captivate presentation. The performance monitor should tell you if the CPU is struggling and unable to decode the content fast enough.
Try to have another user log onto the same machine using a different profile and see if they experience the same issues. This can tell you whether the issue is due to a corrupted user profile. Conversely, have the same user log onto a different machine, creating a new profile for themselves on that PC to see if they experience the same issue. If it seems to be their profile at fault, they may need to get some IT dude to blow away their profile and set it up afresh.
Check whether or not the issue could be due to server latency. This is especially the case where LMSs are involved. Users will often experience latency issues such as slow transitions from one quiz slide to the next because the course module has to wait for the LMS to respond before it can move forward. If this is occurring for a significant number of users, you can try using the optional SCORM template that only sends tracking data at the end of the module instead of all the way through.
In my experience, if 95% of your user base is playing the content without issue, you don't need to change anything. Chances are that whatever is going wrong for the few that are complaining about poor playback wouldn't necessarily improve no matter what you did to your project. In the vast majority of cases, you need to isolate what exactly is causing the issue for these users and correct it ON THEIR END.
Rod Ward
www.infosemantics.com.au
UPDATE: I just realised that a lot of this information would probably help others, so I created a blog post documenting these steps: http://www.infosemantics.com.au/debug_slow_playback

Creating a small transition video 100px

Hi,
I'm not sure if this is the appropriate flash thread to start
here but since it's listed under Media I thought I'd stick it under
this subcategory.
What I'm trying to do is make a 100 x 100 pixels (small)
video for a sig. I wanted to take 3 different clips, put them
together and make a slow transitional video where the scenes go
slow and gradually change. I'm very new to Flash so I'm not sure
what I'm doing. First I attempted to import one wmv file to the
library and dragged it to the white box. I then attempted to cut
down the video by deleting the frames but all that did was move the
video to start at later frames instead of editing it down so I
could shorten it. I also tried doing a tween but that didn't do
anything at all (not that I know what it's for anyway, lol). I
tried using the Flash Help but all it did was confuse me with the
instructions to cut and clip video where they don't even tell me
where to find this tool to do just that.
Can anyone help me please? I would really appreciate your
suggestions! :)
-Ceara519

Okay.....
I had hoped someone could give me some suggestions about how
to create the effect I wanted. I tried to do this on my own but
unfortunately it still didn't have the effect I wanted. How can I
get the scenes to gradually transition and integrate into another
scene smoothly without white in white out? Also, is there a way I
can prolong them so the effect lasts longer? I tried the transition
effects but all it did was create the fade in fade out effect not
prolong it. What can I do?
Another frustrating difficulty I've been having is that
somehow when I try to add the transition effects and move them so
they all occur closely with the layers (1 movie clip for each
layer), they don't finish the scene? It gets cut off? Each of the
clips I have on here that you see aren't showing the complete shot
just gets cuts off before each scene finishes. Why is it doing
this?
I also had problems uploading to swf. file so I had no choice
but to try gif.
http://i142.photobucket.com/albums/r109/Sorcha25/hopethisworks.gif

How do I transition a photo from B&W to color?

I have seen a video that has photo stills that gradually change from black and white to color. Does FCP have a way to do this? Or do slow transitions between effects or other video settings?

unfortunaely, color-corrections are not keyframe-able.
But in this case, the trick is simple:
• split your photo in the timeline
• color-correct #1 to b/w
• apply a sloooow dissolve

Slow Select - AI on MacBook Pro OS 10.5.8

ISSUE: Using Direct or Indirect Selection tool on any object in Illustrator CS3 or CS4 is slow (usually presents beach ball). It is an irritation not feature failure. To reproduce, create a new Illustrator file on MacBookPro5,4, (effects RGB or CMYK, all preview and non preview modes), create a line segment, create a square (or any other closed shape), or create some text. Grab the direct selection tool and click on any of the objects. You may not see the slowness on first selection. Now click on any of the other objects. The machine will pause. The existing selection will not disappear. The beach ball will appear and spin. After roughly 2 seconds, the existing selection will disappear, and the new selection will be made as expected. It's the expected behavior but very slow transition from one selection to another.
NOTE: strangely, if you do a drag selection (marquee drag) rather than clicking on the object with the selection tool, the delay does NOT occur!
Any help much appreciated. Had posted this Issue to Apple MBP forum, was asked by a user there to post it here first, BUT believe the issue is related to graphics hardware on new MBP. Have tried exact same test on an older MBP using same version of CS4 Illustrator without encountering problem. Have also tested CS3 on this with same problem. Thanks, James.

SOLVED - see great work done by users here
http://forums.adobe.com/message/2423029#2423029

FB Burrito pushView/popView Animation vs Android's Transition Animation

This question is directed towards the Flash Builder Burrito Development Team:
When I select "No Animations" on my Android phone, the transition animations within the apps on my phone are all disabled, which is expected. I've noticed two things regarding "view" transitions within apps developed with FB Burrito (tested on my Android phone: HTC Evo 4G):
1. When "No Animations" is selected, the pushView/popView animations still occur, indicating that apps developed with FBB operate independently from Android's transition animation system.
2. The frame rate of the view animations within the FBB-developed app is much slower than the phone's frame rate (47-50 fps), even when the frame rate is set to 50 fps within the app; whereas, non-FBB-developed apps' transition animations operate at the phone's frame rate (in this case, 47-50 fps).
From usability and aesthetic standpoints, this may be problematic:
1. If users choose to turn off their phones' animations, they will have to deal with the independently-operated transtion animations with FBB-developed apps (usability issue).
2. If users keep their phones' animations on, they will have to deal with the aesthetically unplesant slow transition frame rate of FBB-developed apps (aesthetic issue).
My question is: Within the final build of FBB, will view transitions operate off of Android's animation system, or will they remain independent?
PS-LOVE the progress you guys at Adobe are making constantly to make muti-screen development more efficient! Adobe FTW!

AIR does not currently have an API to read this particular Android setting. To answer your question, Flex view transitions are independent of the Android system settings.
Jason San Jose
Software Engineer, Flex Mobile

Lion Mail slow

I just upgraded and find Lion mail to be slow to the point of seeing a hesitation when I click Reply and then a very slow transition of theh window to the Reply screen. Any ideas why? Thanks.

I have experienced the same problem on two computers with Mail. When I hit reply or forward, the entire computer just comes to a halt.

What every developer should know about bitmaps

This isn't everything, but it is a good place to start if you are about to use bitmaps in your program. Original article (with bitmaps & nicer formatting) at Moderator edit: link removed
Virtually every developer will use bitmaps at times in their programming. Or if not in their programming, then in a website, blog, or family photos. Yet many of us don't know the trade-offs between a GIF, JPEG, or PNG file – and there are some major differences there. This is a short post on the basics which will be sufficient for most, and a good start for the rest. Most of this I learned as a game developer (inc. Enemy Nations) where you do need a deep understanding of graphics.
Bitmaps fundamentally store the color of each pixel. But there are three key components to this:
1.Storing the color value itself. Most of us are familiar with RGB where it stores the Red, Green, & Blue component of each color. This is actually the least effective method as the human eye can see subtle differences on some parts of the color spectrum more than others. It's also inefficient for many common operations on a color such as brightening it. But it is the simplest for the most common programming tasks and so has become the standard.
2.The transparency of each pixel. This is critical for the edge of non-rectangular images. A diagonal line, to render best, will be a combination of the color from the line and the color of the underlying pixel. Each pixel needs to have its level of transparency (or actually opacity) set from 0% (show the underlying pixel) to 100% (show just the pixel from the image).
3.The bitmap metadata. This is informat about the image which can range from color tables and resolution to the owner of the image.
Compression
Bitmaps take a lot of data. Or to be more exact, they can take up a lot of bytes. Compression has been the main driver of new bitmap formats over the years. Compression comes in three flavors, palette reduction, lossy & lossless.
In the early days palette reduction was the most common approach. Some programs used bitmaps that were black & white, so 1 bit per pixel. Now that's squeezing it out. And into the days of Windows 3.1 16 color images (4 bits/pixel) were still in widespread use. But the major use was the case of 8-bits/256 colors for a bitmap. These 256 colors would map to a palette that was part of the bitmap and that palette held a 24-bit color for each entry. This let a program select the 256 colors out of the full spectrum that best displayed the picture.
This approach was pretty good and mostly failed for flat surfaces that had a very slow transition across the surface. It also hit a major problem early on with the web and windowed operating systems – because the video cards were also 8-bit systems with a single palette for the entire screen. That was fine for a game that owned the entire screen, but not for when images from different sources shared the screen. The solution to this is a standard web palette was created and most browsers, etc. used that palette if there was palette contention.
Finally, there were some intermediate solutions such as 16-bits/pixel which did provide the entire spectrum, but with a coarse level of granularity where the human eye could see jumps in shade changes. This found little usage because memory prices dropped and video cards jumped quickly from 8-bit to 24-bit in a year.
Next is lossy compression. Compression is finding patterns that repeat in a file and then in the second case just point back to the first run. What if you have a run of 20 pixels where the only difference in the second run is two of the pixels are redder by a value of 1? The human eye can't see that difference. So you change the second run to match the first and voila, you can compress it. Most lossy compression schemes let you set the level of lossiness.
This approach does have one serious problem when you use a single color to designate transparency. If that color is shifted by a single bit, it is no longer transparent. This is why lossy formats were used almost exclusively for pictures and never in games.
Finally comes lossless. This is where the program compresses the snot out of the image with no loss of information. I'm not going to dive into what/how of this except to bring up the point that compressing the images takes substantially more time than decompressing them. So displaying compressed images – fast. Compressing images – not so fast. This can lead to situations where for performance reasons you do not want to store in a lossless format on the fly.
Transparency
Transparency comes in three flavors. (If you know an artist who creates web content – have them read this section. It's amazing the number who are clueless on this issue.) The first flavor is none – the bitmap is a rectangle and will obscure every pixel below it.
The second is a bitmap where a designated color value (most use magenta but it can be any color) means transparent. So other colors are drawn and the magenta pixels are not drawn so the underlying pixel is displayed. This requires rendering the image on a selected background color and the edge pixels that should be partially the image and partially the background pixel then are partially the background color. You see this in practice with 256 color icons where they have perfect edges on a white background yet have a weird white halo effect on their edges on a black background.
The third flavor is 8 bits of transparency (i.e. 256 values from 0 – 100%) for each pixel. This is what is meant by a 32-bit bitmap, it is 24-bits of color and 8 bits of transparency. This provides an image that has finer graduations than the human eye can discern. One word of warning when talking to artists – they can all produce "32-bit bitmaps." But 95% of them produce ones where every pixel is set to 100% opacity and are clueless about the entire process and the need for transparency. (Game artists are a notable exception – they have been doing this forever.) For a good example of how to do this right take a look at Icon Experience – I think their bitmaps are superb (we use them in AutoTag).
Resolution
Many formats have a resolution, normally described as DPI (Dots Per Inch). When viewing a photograph this generally is not an issue. But take the example of a chart rendered as a bitmap. You want the text in the chart to be readable, and you may want it to print cleanly on a 600 DPI printer, but on the screen you want the 600 dots that take up an inch to display using just 96 pixels. The resolution provides this ability. The DPI does not exist in some formats and is optional in others (note: it is not required in any format, but it is unusual for it to be missing in PNG).
The important issue of DPI is that when rendering a bitmap the user may want the ability to zoom in on and/or to print at the printer's resolution but display at a lower resolution – you need to provide the ability for the calling program to set the DPI. There's a very powerful charting program that is useless except for standard viewing on a monitor – because it renders at 96 DPI and that's it. Don't limit your uses.
File formats
Ok, so what file formats should you use? Let's go from most to least useful.
PNG – 32-bit (or less), lossless compression, small file sizes – what's not to like. Older versions of some browsers (like Internet Explorer) would display the transparent pixels with an off-white color but the newer versions handle it properly. Use this (in 32-bit mode using 8 bits for transparency) for everything.
ICO – This is the icon file used to represent applications on the desktop, etc. It is a collection of bitmaps which can each be of any resolution and bit depth. For these build it using just 32-bit png files from 16x16 up to 256x256. If your O/S or an application needs a lesser bit depth, it will reduce on the fly – and keep the 8 bits of transparency.
JPEG – 24-bit only (i.e. no transparency), lossy, small file sizes. There is no reason to use this format unless you have significant numbers of people using old browsers. It's not a bad format, but it is inferior to PNG with no advantages.
GIF – 8-bit, lossy, very small file sizes. GIF has two unique features. First, you can place multiple GIF bitmaps in a single file with a delay set between each. It will then play through those giving you an animated bitmap. This works on every browser back to the 0.9 versions and it's a smaller file size than a flash file. On the flip side it is only 8 bits and in today's world that tends to look poor (although some artists can do amazing things with just 8 bits). It also has a set color as transparent so it natively supports transparency (of the on/off variety). This is useful if you want animated bitmaps without the overhead of flash or if bandwidth is a major issue.
BMP (also called DIB) – from 1 up to 32-bit, lossless, large file sizes. There is one case to use this – when speed is the paramount issue. Many 2-D game programs, especially before the graphics cards available today, would store all bitmaps as a BMP/DIB because no decompression was required and that time saving is critical when you are trying to display 60 frames/second for a game.
TIFF – 32-bit (or less), lossless compression, small file sizes – and no better than PNG. Basically the government and some large companies decided they needed a "standard" so that software in the future could still read these old files. This whole argument makes no sense as PNG fits the bill. But for some customers (like the federal government), it's TIFF instead of PNG. Use this when the customer requests it (but otherwise use PNG).
Everything Else – Obsolete. If you are creating a bitmap editor then by all means support reading/writing every format around. But for other uses – stick to the 2+4 formats above.
Edited by: 418479 on Dec 3, 2010 9:54 AM
Edited by: Darryl Burke -- irrelevant blog link removed

I don't think the comment about jpeg being inferior to png and having no advantages is fair. The advantage is precisely the smaller file sizes because of lossy compression. Saving an image at 80-90% quality is virtually indistinguishable from a corresponding png image and can be significantly smaller in file size. Case in point, the rocket picture in that blog post is a jpeg, as is the picture of the blogger.
The statements about the TIFF format is slightly wrong. TIFF is sort of an all encompassing format that's not actually associated with any specific compression. It can be lossless, lossy, or raw. You can have jpeg, jpeg2000, lzw, packbits, or deflate (png) compressed tiff files. There's also a few compressions that specialize in binary images (used alot for faxes). In fact, the tiff format has a mechanism that allows you to use your own undefined compression. This flexibility comes at a price: not all image viewers can open a tiff file, and those that do may not be able to open all tiff files.
Ultimately though, the main reason people use TIFF is because of its multipage support (like a pdf file), because of those binary compressions (for faxes), and because of its ability include virtually any metadata about the image you want (ex: geographical information in a "GeoTIFF").

What is the keyboard shortcut for symbols?

Somehow when wiping off my keyboard the buttons got pushed into a particular sequence that has changed my English keyboard into all symbols. Going to system preference/keyboard doesn't work because that says my keyboard is English. The other interesting thing is that the screen does a slow fade now when transitioning between say launch pad and then desktop.
Any one have a clue what I am talking about?

The symbols by be tied to the option key being stuck down, and the slow transition may be tied to the Shift key being stuck down.
If you open Language & Text System prefs, select Input source, and add the keyboard viewer to the input sources, you can select that from the Input menu and see if it shows the option and shift keys stuck down.

How do I fade one frame into another?

In Flash pro 4 how do I fade out of one keyframe and fade into the next one with a slow transition? thanks.

Try this set alpha to 0. Move ahead 20 frames or how fast or slow you want it.Change the alpha to 100%.Then create motion tween in the button symbol and place the movie clip in the over state.
Then it should fade as the movie plays.You can implement it the way you want it.
Hope this helps
Good Luck!

I have two videos and I would like to use parts of both videos with one audio track what is the best way to edit this?, I have two videos and I would like to use parts of both videos with one audio track what is the best way to edit this?

In Final Cut Express I have two videos I'd like to merge parts of each video into a final film. What is the best way to do this in FCE?

Hi
I use a slightly different way than Alchroma.
Same
• One video on track 1 and the other on Video.track 2
• Resize to 25% and move one to the left and the other to the right
Diff
• I don't use the blade tool
• I use the Pen tool and change the transparency - then I get fast or slow transitions in same stroke and easy to fine-tune later if needed. (But this can be done with the Roll-tool if Blade is used - so it might be as easy)
Final
• Resize to 100% and Center
Video is done
Audio - very close to this by changing the level so that best audio will dominate
• Pen tool here too
But that's me - the Alchroma way is as good as this or may be better for some
Yours Bengt W

Grid in Spaces gone (dark; no blue rectangles)

Please see attached link to screenshot of my Spaces grid, or to be more precise: lack thereof (grid that is). I have 16 spaces, but the grid has disappeared. The grid appears as is in the screenshot, regardless of how many spaces I use. How do I get the proper grid back? I see no settings to control this, so I figure something is off.
Screenshot: http://cl.ly/2GZ2

Just to illustrate: when doing a slow transition to Spaces (using Shift+F8 to slow down the process), one clearly can clearly see that the grid is present during the transition. But as Spaces completes it's "loading process", it fades to black, eliminating the grid. When reverting, you can also clearly see the grid during the fade out. I'm not sure if it matters, but I have my 32" Samsung hooked up as well. Used to work before doing a clean install of OS X due to unrelated issues.
Proper order for the screenshots is as follows:
1. http://cl.ly/2HPg (Spaces during transition)
2. http://cl.ly/2GZ2 (Spaces fully loaded)
Hopefully someone will pick up on this. Crossing my fingers!
Thanks!

Slow transitions in 4.3.1

Similar Messages

Maybe you are looking for