SMM firmware observations.

Im sure a lot of this ground has been covered but I thought Id put my 'want list' together. I blogged at http://www.sammorganmoore.com/fs7-notes-on-firmware/ Here is the text.. (badly formatted) The FS7 is the finest camera I have ever owned – I want to be clear on that. Slog3 is a fantastic space and the LUTs to delog it are wonderful. This makes the camera pseudo raw at 1/4 of the data rate of a raw camera.. well done Sony. Audio pots, a self powered EVF, low power consumption and other features also make the camera a wonder.. well done Sony!Now I think the camera could be moved to another level with some concentration on the firmware. I know nothing of firmware but I have a sense of what is easy to do and things that will push the processor to a place that it may not want to go. Bugs  magenta shiftWell known – Custom mode kelvin dial is off presenting a magenta shift in the image as one moves away from 3200k. cache recordOn event coverage I like to use cache record , however if I engage S+Q, and shoot an offspeed clip cache record is no longer engaged when I return to normal speed. matrix unstableWhen using custom mode I like to record Slog3, Matrix Off – as matrix adds saturation that should not be there in a LOG image. Matrix appears to ‘randomly’ switch itself on. mlut unstableAn early observation but it seems like Mlut status can be lost on engagement/disengagement of S+Q general unstabilityI cant remember other examples but other settings seem to ‘randomly’ move too. For example my camera is now on shutter speed – Im sure I set it to angle – setting it to angle means less button twongling when engaging S+Q menu delaysWhen I change ISO using the HML switch the EVF only picks up the settings two seconds later – very confusing if you are used to a faster response – If lags are defined by processor speed then the EVF could display a ‘wheel or egg timer’ in the way that computers tell us ‘this is hard, bear with me’ record status lostIn S+Q one can shoot a short shot and then get the camera into a status where the camera is neither displaying the record button or the STBY status – leaving the operator at a loss if he wants to start rolling – hit the record button again or not? A side note to this is the record button on the op side is not as sensitive as most record buttons. colour balance failThis might be a function of using Slog3/Custom which does not present the system enough colour data – but often it is impossible to use the WB button. If the camera is pointed at a white card it will read ‘NG highlight’ if one stops down in 1/2 stop increments the reading then suddenly changes to “low light’ making a click WB impossible. it is called tint!Tint is called tint by everybody and even in Cat Browse. So why is it called Temp in the Sony colour menu? Simple upgrades  Red dot on display offThis would be a simple warning to add.With the EX1/3 Fs100/700 one is still presented with an in monitor red icon when recording – can we have that back please. Display on/off was elegantly done with the FS100 Titles of Luts etcWith the EX1 I had many picture profiles built – they may have had titles like ‘SMM_EXT_Daylight’.. but on screen was not this title but PP3. With the FS7 the same or worse is the case. Ideally we would see something like..Recording: “EI : Slog3″Monitor: “SMM_Golden_Lut :”And in Custom Recording: “SMM_Daylight_Warm”This is super important at the moment because I have a setup “SMM_Minus17Magenta_55k” – this must be on when shooting Custom at 5500k and must NOT be on when shooting at 3200K which needs “SMM_32_Standard”(ideally this would also be burned into the meta data esp in EI so the colourist could go to the selected LUT to recreate the on set experience)  Taking it furtherReally I think the complete firmware of the camera needs a complete revisit. Sony should forget their broadcast heritage menu set up and move towards offering a simple interface that aligns with both Professional Cinema cameras and professional DSLR stills cameras (1dx, nikon D4) LUTsLuts should be consistent both in playback and HFR and not kill the WFM – I will not use Mlut at all until this is the case. LUts in CustomMany shooters are desiring EI mode to be ‘upgraded’ to include sharpening NR et al. I feel this is wrong as keeping those facilities out of EI gives one a safe method of recording image. Custom mode should be expanded to offer LUTs and then one could shoot with Slog, Sharpening, NR and a LUT. SlogCustom, match SlogEIWhen Slog 3 is engaged, matrix and all colour controls (excluding temp and tint) should be turned off – so that  SlogCustom matches Slog EI.  ISO, Shutter Ctemp buttonsPressing the ISO button engages Auto ISO – this is wrongand can ruin shots – Sony should align ISO button to match cameras by everyone else..The ISO button should open the ISO menu, 500-1000-2000-4000-6000-8000-10000-AUTOSame for the other two base controls..Temp 3200-4000-…..1000k-AutoShutter – 360-270-180-90-45-… Auto  RGB WFMThe basic way of evaluating colour in a digital camera is to evaluate large RGB histogram or WFM – addition of this.. even only to evaluate a still or in status mode would add a critical functionality – a functionality that is available on $500 and up DSLR and compact cameras. Bleeps.audio bleeps or clicks could be a confidence booters in start stop and menu navigation (EX1 FS100) AssignableEvery button shold be assignable!LUT ON/Off (see Sony PMW-F3)

A little update from this weekend. I filmed a drama short. Overall the imagery from the camera and flex of the files is absolutely performing as expected. BUT Somehow the camera managed to perform a factory reset without me noticing (possibly on battery change - maybe I didnt leave the battery in long enough after turning off?). My mind is on story, and the 20odd crew and cast I'm concentrating on.  I faile to notice the factory reset - but was certainly noticing 'no synch' in my monitor! Bad lead? what has happened? Where is my WFM (on the EFV?) Rerig to lookat the EVF which the director had been watching mounted on the back of the cam (nice simple solution). Non happy director! At least the factory settings are Slog and 4k which is what I was shooting. So I lost my monitor (as 4k-1080 needs to be set up) and my WFM and also the camera went to 50p 360 shutter. So buried was I in trying to restore the monitor between takes that I failed to notice 50p/360 for about 10 takes - so they will need retiming in post. Nice images but it is super stressful to have to watch the camera like a hawk. I want the camera to by my friend not the little devil on my shoulder ruining my day whenever I take my eye off him.    

Similar Messages

  • My observation after E63 firmware upgrade

    Hi all,
    As per above subject, here I express my some observation just for your information.
    1. All equalizer sound effect became same in music player, even manual setting not responding.
    2. When playing a song, it's stop and reset when fast forward or rewind applied.
    3. RealPlayer became more laggy, it's take noticeable time for normal to fullscreen and vice versa and also for volume up down
    4. Newly added theme White (Business and Personal) had a major issue of digital clock misalignment and minor one is top bar color mismatch with bottom bar and wallpaper.
    5. Mostly all preinstalled themes are not cover contacts and calendar color scheme.
    6. In week view of calendar the column header and left border misaligned for Tuesday and Saturday only.
    7. Personally I prefer the Black Personal theme, but the font of digital clock are so rough and not smooth as all dark business themes. It's very funny why all light colored themes got ugly digital clock and which also fixed more upper (near operator logo) than dark ones? It ruins the elegance of Eseries.
    Note: The observation done on my Nokia E63-1 (27) RM-437. 200.21.012. 18/06/2009 APAC, Upgraged by Nokia Authorized Service (Kolkata, India). It may not be applicable on all E63 worldwide. Lastly I have no intention to find fault of GREAT Nokia. This is for just sharing only.
    Thanks, have a very pleasant day.
    Message Edited by saranan on 18-Sep-2009 09:54 AM

    It depends who the phone is branded with as to whether any upgrades are available. If the software updater says no then you should not try to upgrade it some other way. I would contact your SP and ask about it since like you say the latest version is 400....
    E71-1(241.04) RM-346 300.21.012

  • How to install OS 9.2.1 on G3 with no OS; says needs updated firmware, how?

    I am trying to install OS 9.2.1 in an old G3 which at present has no OS in it.
    The screen says it needs updated firmware to do so. When I try to follow instructions, it tells me the CD is locked, which is obvious since it is an installation CD. Other instructions seem to assume there is already an older OS in the machine to update. Anyone with an idea of how to break this log jam?
    [email protected]

    Hi wmarina !
    Welcome to the Discussions, and Happy Thanksgiving!
    The only G3 that will give you a Firmware Update warning when trying to install OS 9, is a Blue & White G3 tower.......
    If that's what you have, then getting OS 9 onto it is a bit of a Catch-22, Can o' Worms, P.I.T.A., or whatever other favorite sayings you may have for a difficult job........
    "Other instructions seem to assume there is already an older OS in the machine to update."
    Very astute observation, and 100% correct.
    The OS that is assumed to be on the B&W's drive is MINIMUM 8.5.1, and therein lies the Catch-22.....
    A BOOTABLE 8.5.1 Install CD is NOT available as a RETAIL CD........
    The Retail CD is 8.5 install, with the 8.5.1 UPDATER, which is also on the CD.......
    The 2nd part of this problem is that the Firmware Updater (which is on the OS9.1 CD) MUST be run from the booted Hard Drive with 8.5.1 on it.........
    Your options are:
    1. Find a set of the ORIGINAL SOFTWARE CDs that shipped with a Blue & White G3, and install the original OS from there.........
    2. Do what I had to do. Take out the Hard Drive and move it to an older Mac (i.e. Beige), and install OS 8.5 on it, and update it to 8.5.1, take the Hard Drive out and re-install it into the B&W again, boot to it, and do the Firmware update at that time.........
    Note that NO Mac can boot to an EARLIER version OS than it shipped with when new, which is why you will have to use a beige to install 8.5.1 to that hard drive........
    As a secondary note, to avoid more problems, get a new Pram battery (1/2 AA 3.6V).
    Available at any Radio Shack.
    Good Luck !
    Kevin
    G3 1.1Ghz B&W, Digital Audio G4 Dual 533,G3Beige,8600/G4-800, 7600/G3-300, 6200 Ret.   Mac OS X (10.4.3)   ATI RADEON MEs: 7000, 9200, 9800, nVidia ? 64MB

  • E3000 firmware update fixes.

    Hey all,
    I just wanted to know if anyone noticed that their E3000 has actually been working to its standards and price after the new firmware update (build 4). Just wanted to know the concensus, because I am getting flawless signal strength, no drops, burst speed is amazing, the heat problem has gone away (no joke..im hoping this isnt just mine). Anyone have an input on if the new firmware update has helped?

    Yes, that is what I am observing too (Auto 20 or 40 but no 40 only).  Most of my adapters are N 2.4.  It is a shame I cannot pull more than 130-150 Mbps on these as "Auto" does not seem to work properly to give me 40 (it is always stuck on channel 1 at 20 MHz).  This may seem insignificant, but not when you are trying to transfer large files within the network.  I am also unable to get my full ISP provisioned throughput (43 down/35 up) at 130-150 Mbps.
    With the wrt610n, I was able to get 270-300 easily by forcing 40 only.
    It is a shame that Cisco's top of the line router does not have the basic functionalities needed.
    You are right about 5 GHz.  It is very good.  But I only have one 5 Ghz adapter that I use for work VPN.

  • N97 V2.1 - Observations

    As all the other N97 V2.1 threads seem to have gotten off topic I thought I would start this post for people to add their observations on the new firmware update.
    My observations:
    * RAM - Up to 10 MB more free and better RAM management, unfortunately the internet based widgets and Nokia messaging still use a lot of RAM which I suspect has a negative effect on the stability of the device (shame that Nokia didn't put 256MB RAM in the device as it's not living up to the Nokia marketing of the N97 and it's not reasonable to be expected to not use these features).
    * Widget UI - The widgets seem to be more stable and refresh properly.
    * Kinetic Scrolling - I still have sticking but it occurs only initially when I navigate down into a folder with a lot of icons (I suspect this has to do with the underpowered CPU, another design fail by Nokia).
    * Web browser - Seems to be more responsive and stable.
    * Photo gallery - Seems to be more responsive but still has a little lag (again probably due to the poor choice of CPU).
    * Music player - Seems to be better but still slow (CPU again).
    * General system - Seems more stable but still slow and I have had to restart the phone three times in 12 hours.
    * Other observations
    Menu>Settings>Phone>Application sett. - has a bug that just drops you back to the Menu level.
    No option to turn off auto-rotation for phone calls.
    Bug with the caller image not being constrained within the proper area.
    Contacts still doesn't exit properly.
    No improvement on free space on c: (Nokia should have put at least double the NAND memory in).
    Music player back UI inconsistency.
    No virtual keyboard in landscape mode.
    Nokia messaging still not properly integrated into the phone.
    Useless, unremovable trial apps still included in the firmware (Nokia listen to your customers and get rid of these).
    These are just my first observations and I'm sure over time I will notice more things but at the moment I would say that this firmware update is an improvement.
    Unfortunately IMHO nothing will overcome the poor design choices in relation to the CPU, RAM & NAND memory. I guess we will just have to live with the major shortcomings of this device but Nokia could definitely make it easier by clearly informing N97 owners about the roadmap for the device.
    Nokia N97 (RM-507) v 22
    iPhone 4 (Coming Soon) - Lemon N97 - SE - Nokia 8210 - Nokia 7710 - Nokia 5100

    Updated today and i must say it seems to make the device run alot smoother One thing i noticed though was that when you go into applications it slows down alot though this is probaly due to the amount of stuff i have in there lol. We i can say for the mean time the update is one of the best
    have to give it a couple of days i guess and see if it turns bad or not lol

  • What are the chances of an N95 Classic Firmware Up...

    Guys,
    Do you think Nokia will continue to support the N95 now that the 8gb version is out? I'm stuck with the phone based on contract and I'm hoping that at least we'll get a hot new firmware.
    What are the chances that they'll release a significantly updated firmware that possibly will free more memory or add that dynamic memory handling of the new software so this thing can be a reliable Ngage gaming device?

    one can be optimistic, and one can be realistic. One can observe the history of Nokia support and draw a conclusion and that would not be an optimistic conclusion. There are plenty of people who have contracts for phones that got a single upgrade if they were lucky. N95 has already had more than that (3?) with the last one dated 5 months ago. The cell phones that get updated are usually not 6 months between updates so every day that passes is like a nail in the coffin. So Nokia has moved on to N95 8GB. Contract has nothing to do with getting Nokia to upgrade firmware however badly it may be needed, contract is about making money for the phone company. The N95 8GB can just as well be called an N95 "i" version, they just didn't name it that. that means N95 "Classic" very likely "left in the dust" as a previous post articulately stated. When I say the I think the chance is zero, it is based on Nokia support history which is woeful

  • PRS-T1 stuck in infinite reboot loop after failed firmware update

    Hi,
    I tried to update the firmware, but failed when updating to version 1.0.07.05070. Tried to 2 times. The first time it failed I simply tried again. The second time, it took a lot longer to reach the failed to update message, but it did cause the ereader to reboot.
    Now, it's stuck in an infinite reboot loop on the "Opening book" page. The progress bar on that page stays completely empty, lasts for about 30 seconds, and reboots again. This will go one until the battery is dead or indefinitely if plugged in. 
    I have tried pressing the Home + Menu buttons, but they seem to have no effect.
    Please advise if there is anything I can try to revive it?
    Thanks in advanced.
    David
    Solved!
    Go to Solution.

    Kiroken,
    Here is what I have observed:
    - After a hard boot (reset + power button during 3+ seconds), if I don't do anything, it will reboot every ~30seconds.
    - If I press and hold the Home and Menu buttons, no effect. The same as if I didn't press anything.
    - If I press the Forward + Back buttons (2 & 4), it does not reboot after 30 seconds. Instead, the orange light on the power button blink every ~2-3 seconds.
    - Any other key combinations that I have tried have no effect.
    I have tried with and without several rescue sdcard. No difference. No improvement. In every case, the computer never sees the reader. If plugged into the power outlet, it seems like the battery charges alright. It does not appear to charge if plugged into USB port.
    That's all I know. If I can't fix it, I might be forced to turn it into a coaster or maybe a cutting board for the kitchen.
    David

  • Clicking sound originating from Airport Express firmware 7.5.2 and later

    Hello,
    I have submitted a bug report through Apple Developer Connection (I am a registered developer). By posting this here I want to get support for our case: Make Apple fix the Airport Express firmware.
    Summary:
    The Airport Express device has a bug which appeared first in version 7.5.2. It produces a "clicking" sound when using AirPlay to transport music from an iPhone or a Mac, when certain frequencies are being played. This is not depending on the attached amplifier or headphones, digital or analog output, network settings (network created by Airport Express or not), Mac or iPhone used, audio cable or power supply involved or due to bad quality of the sound file played. The problems are not there when audio is played directly from a Mac or an iPhone through headphones or optical out. We and my colleagues (developers and audophiles) have ruled out all the other options. The problem boils down to a change in the Airports firmware starting with 7.5.2. In 7.4.2 the clicking sound is not there.
    Steps to Reproduce:
    Play the following song via AirPlay on an Airport Express device having firmware 7.5.2 or higher. The Airport Express being used in our tests is the model produced from March 2008 – June 2012. Attach high fidelity headphones (like Bowers & Wilkins P5, which we used) to Airport Express. Alternatively use a very good amplifier/loundspeaker setup. We also reproduced the bug for example on an Onkyo A-9070 amplifier with both optical and analog connection - there is no difference there. The loudspeakers we used are passive Dynaudio X12.
    Play track no. 6 from the "Songs without words" album: http://itunes.apple.com/de/album/lieder-ohne-worte-op.-67-no.-2/id209380163?i=20 9381206
    Listen to this solo piano piece carefully for at least 40 seconds. You will notice a clicking sound with high frequencies. This clicking is *not* there in firmwares 7.4.2 and earlier.
    Expected Results:
    Perfect audio quality as in firmware 7.4.2 and earlier.
    Actual Results:
    Reproducible clicking sounds in high frequencies.
    Regression:
    This problem appeared first in Airport Express firmware 7.5.2 and has not been fixed yet. It can also be observed in the current version of Apple TV (as of September 16th).
    Notes:
    This issue, while not being recognized by the casual listener, makes AirPlay unusable for critical listening - at least when using any firmware after 7.4.2. I would love to use the current firmware (which produces a much more stable connection), but I (and other audiophile AIrplay users) would love to see this issue fixed first.
    Here is a thread that concludes - as we did - that Airport firmware 7.5.2 and later is the source of the problem. It is not the hardware, neither Apple's, nor the connected devices:
    https://discussions.apple.com/message/17296916#17296916
    Hope this helps!
    Best,
    Gabriel

    I'm having the exact same problem. As a classical music lover, this is driving me nuts. It's especially noticable in soft passages in the music, when the volume is turned up high. When the dynamics increase, the little pops/clicks appear (they sound a bit like static noise, as someone stated earlier in this thread). It happens at irregular intervals. When you play pop music, the clicks will disappear (drown) in the music. But for true audiophiles who listen mainly to jazz and classical music this is a severe problem.
    I have checked everything and it's definitely an airplay issue. My apple lossless files are 100% okay and play without any problem, except when streamed via airplay. Also, it makes no difference whether you use the analogue or the optical ouptut from the airport express.
    I've created a sine frequency sweep myself in Adobe Audition, from 20 Hz up to 20000 Hz with a duration of 25 seconds and a level of -6 dB. 
    When played through airplay, the clicks always start to appear after 4 seconds in the sweep, only to disappear at 23 seconds.
    The clicks manifest themselves at different volume levels. To my ears, they make the same sound as when you change the volume in iTunes when streaming music through airplay. Only when you set the volume in iTunes extremely low, the clicks will disappear.
    Apple engineers should use a frequency sweep to recreate the problem, as this is very revealing.
    PS: file format isn't an issue here. I've converted the Apple Lossless file to MP3, and it makes no difference at all.

  • Link to download firmware s

    I understand i need to download these softwares before i can update my at&t Lumia 1520 to denim. Is there a link to download firmware : 02061.00074.14273.33019 and firmware 1028.3562.1407.1001
    Solved!
    Go to Solution.

    taritera wrote:
    my phone has never been updated and i understand updating is cumulative, that is i need to update with the older firmwares before I finally udtate with denim
    That is absolute nonsense, you will get directly the latest available firmware available for your handset. If you do it OTA and some other firmware bits are required for the latest one to install, they will get installed automatically before the latest firmware is applied. You will only observe several updates happening one after the other without any input required from you. If you use the tool via PC, it will wipe your phone and install directly the latest firmware.

  • N80 Firmware changelog?

    Is there a Nokia certified website or source where I can find a history of N80 firmwares and what changes took place in each one?
    A changelog would be absolutely fantastic to help verify that new firmewares really fix observed problems.
    Also, it could be used to check if I have the latest firmware (I know I could just hook my phone up and sync it, but I'd rather have a simpler method since I've seen the Nokia Software Updater program fail on me a lot hence I don't trust it).
    Currently I have an N80 running 4.0707.0.7, updated just yesterday from the previous version.

    Being a computer program and well familiar with embedded systems myself I was afraid the case would be that Nokia doesn't release the details of each firmware update. Honestly, I think that is a form of sort of "corporate programmer cowardice."
    Regardless, you bring up another good point: N80 users certainly should NOT load the new 4.0707.0.7 firmware as it has some severe problems.
    Just to help future searchers get this:
    Nokia N80 4.0707.0.7 firmware is broken and bad, do not upgrade or load this firmware.

  • 7.3.1 firmware breaks 6to4 IPv6 connectivity

    Can others confirm that the 7.3.1 firmware breaks connectivity to various 6to4 sites? I reverted to 7.2.1 and my connectivity is restored. I'm a Comcast customer in the USA, so the Airport "helpfully" prevents me from using a static tunnel with DHCP-assigned WAN addresses, thus I'm stuck with 6to4.
    It appears as though the 7.3.1 firmware drops inbound 6to4-encapsulated traffic if the IPv4 wrapper source address is not 192.88.99.1, the 6to4 relay anycast address per RFC 3068. Whilst it's correct to send to this address (and only a minor irritation that it can't be overriden) it's wrong to insist that return traffic come from this, since it's effectively a "virtual" address, by virtue of being anycast and advertised by any helpful IPv6 network operator. It's good practice for 6to4 relays returning traffic to use their "real" IPv4 address for accountability.
    Examples of broken sites:
    https://6to4.nro.net/ (so no reverse DNS registration possible)
    http://www.ja.net/
    http://www.exim.org/
    Return traffic goes via the 6to4 relay handling 2002::/16 which is nearest, IPv6-network-wise, to the node sending back the traffic; so traceroute6 starts showing "* * *" at the point where the remote side is using a 6to4 relay that believes in accountability and is thus rejected by 7.3.1 firmware.
    This is all by my observations, with the help of some IPv6 network operators and various looking-glass traceroutes. The lack of ability to sniff external traffic with an Airport somewhat hinders local diagnosis.
    Can anyone confirm or deny this? Or offer hope of this regression being fixed?
    Thanks,
    -Phil

    Hi Phil,
    I'm just confirming that I have noticed the same problem. With the help of a colleague, we setup two AEs (AirPort Extreme) at different sites. Each had a global IPv4 address so it could give its children "2002::/16" addresses (note, if the AE doesn't get a global IPv4 address on its WAN, it won't respond to router solicitations on the LAN). We then attempted to get a child from one network to contact a child in the other, but failed because the destination AE would return an ICMP "destination unreachable" message. If we downgrade the destination AE to 7.2.1, then communication works perfectly. The behaviour from version 7.2.1 seems like what's intended for a 6to4 tunnel, so I'm puzzled why the Apple engineers would take this out.
    Regards,
    Shaun

  • Nokia 5610 new firmware...

    can anyone tell me when will the new firmware of nokia 5610 going to be launched???? im talking about the version higher than 8:30........

    giobacco wrote:
    today, in Italy, the new 09.40 version is released through nokia software update. i have the 08.30 with no bugs so i'm waiting some feedbacks.
    On my own observation there are still some things that needs to be fixed. I'll list them one by one on this post:
    /discussions/board/message?board.id=swupdate&thread.id=45652

  • Some observations in power saver in E71

    I have observed the following:
    1. If the any power saver other than the blank screen is running, and the key pad is also locked, and then you press the D-pad central button, it shows the date, time and some other info in large font (as expected). But once the button is de-pressed, it does not return the power saver, but shows blank screen.
    2. Breathing light works only with blank screen as power saver, or if one reaches blank screen, as mentioned in the first point.
    Any comments on this? In my opinion, for point 1, it should have returned to the power saver set up originally, instaed of the blank screen. The second point seems ok though, though it woould be good to have breating light in all the power savers.
    Regards,
    BK76

    Yup, I concur with tobiasrieper. if you have breathing lights off, it will return to the power saver.
    Anyways, hopefully some consistency will be introduced in the future firmwares. Also, it may be a good idea to link the breathing light to the power saver option, rather than profile settings. However, this is more subjective, and depends on personal preference!!
    Regards,
    BK76.
    Message Edited by bk76 on 17-Jul-2008 01:28 PM

  • Back to firmware 1.0.2, please help!

    Hello everybody,
    two days ago I updated to firmware 1.0.3 .Before that I haven't had any problems with my iPod Classic 80Gb. Unfortunately after the mantioned update, I observed that the volume limit is a lot lower- maybe double.
    At the end of the day, I have no benefits from 1.0.3, but a volume limit!!! :(((
    Please, tell me that there is some way back to 1.0.2.
    Thank you in advance.
    rm

    Before down-revving your iPod from 1.0.3, did your iPod's "Soundcheck" get turned on somehow? Enabling soundcheck (Settings/Soundcheck) will typically drop the volume in order to level out the volume differences between songs.
    If that's not it, then you can try a simpler method to install 1.0.2, *but it requires that you already have 1.0.2 on your computer*. If your iPod did not come with 1.0.2 and you had previously updated to 1.0.2, then it should already be on your computer. If that's the case, then try these instructions*:
    "To downgrade to an earlier firmware version, simply connect the iPod, and then click the “Restore” button while holding down the SHIFT key (Windows) or OPT key (Mac), and iTunes will prompt you for which firmware package to use to restore the iPod. Select the v1.0.2 package which should still be located on your computer, and iTunes will erase and restore your iPod with the older firmware."
    *From this week's "Ask iLounge" column (www.ilounge.com)
    If you never installed 1.0.2 (e.g. your iPod came with that version) then you'll need to try to find a copy, which I can't seem to locate at the moment. Search around to see if anyone posted it ...

  • Mail crashes after MacBook Pro firmware 1.0 update

    Ever since installing the firmware 1.0 MacBook Pro update, Mail crashes doing everything except starting up and receiving emails. In other words, if I click on a message, it crashes. If I'm lucky enough to be able to view a message, then it crashes when I try to reply, or file the message in a folder, or compose a new message. Help....
    MacBook Pro   Mac OS X (10.4.6)  
    MacBook Pro   Mac OS X (10.4.6)  

    Brad,
    So many crashes for so many unrelated reasons indicate there is some corruption either in a file used by Mail (probably the preferences file) or in the filesystem itself. You should start by verifying/reparing your disk (not just permissions), as described here:
    The Repair functions of Disk Utility: what's it all about?
    If Mail keeps crashing erratically after having repaired any filesystem issues, then try this:
    1. Quit Mail.
    2. Make a backup copy of the HOME/Library/Mail folder, just in case something goes wrong. You can do this in the Finder by dragging the folder to the Desktop while holding the Option (Alt) key down, for example. This is where all your mail is stored.
    3. In the Finder, go to HOME/Library/Preferences/. Locate the file com.apple.mail.plist and move it to the Desktop (to be deleted if this fixes the problem).
    You'll have to set up your accounts from scratch all over again. If given the option to import existing mailboxes or something like that, don't. Just enter the account information and Mail will automagically rediscover the data in HOME/Library/Mail/ when done.
    You'll also have to re-configure most of your settings in Mail > Preferences. The first thing you should do is go to Preferences > Viewing and disable "Display remote images in HTML messages" if it's enabled.
    At this point, Mail may still crash for some reason, but it should be something more consistent and repeatable than the situation you've described. Post back with your observations.

Maybe you are looking for