IDVD crashing when attempting to change font in Theme

Hi, all:
I'm writing on behalf of my 13-year-old daughter, who with a friend used iMovie HD to make a movie for a school project, and then used iDVD '08 to burn that project to a disc. She's had to edit the movie a bit, and has shared the edited version with iDVD, but is now having a problem. Here's her exact e-mail to me (I'm in Europe right now; she's at home in the US)...
"hey i had to do a few touch ups to the movie that me and jill made, and every time a tried 2 share it 2 idvd, it worked, but when i tried 2 change the font on the themes thingy, it always said, "idvd has to close unexpectedly. we apologize for the inconvenience." or something like that that made me have 2 force quit it more than once. dont panic, the new version of the movie is still saved on imovie, but i dont know whats wrong with the other thing. please email me back ASAP! xoxo"
TIA for your help & suggestions!
Bill from CT (but in France)

Just an additional thought to add to Glo H's excellent recommendation.....if your daughter sends her movie to iDVD and then needs to change anything in the movie, iDVD will recognize that something has changed and ask if it should update. And you think, nice, all is well. But, if you have chapter markers in the movie, iDVD will not 'update' properly. If you don't know this, you will see iDVD going ahead and encoding and burning, but the DVD disk will not play correctly. From the chapter marker nearest the change, all further chapter selections will default to that one.
I have had this happen three times now, and it has been with iDVD8. The previous version made the changes appropriately. The last time the only change I made was to change the spelling in a title! The other changes were to delete one song in an audio track and add another.
The only way to fix it was to create a new iDVD project and drop the movie in again.
I am using iMovie 6. Maybe iMovie 8 or 9 would be different. I just wanted to caution you. I know how difficult it can be to provide your kids with assistance from a distance. Mine used to call from college and it took at least 20 minutes just to figure out what they were doing......then I had to find the answer!

Similar Messages

  • Muse crashes when attempting to change font

    Hi,
    Just tested Muse from Creative Cloud and can't past changing fonts. Each time I try, the app crashes.
    Removed all duplicate and corrupt fonts with Font Book, restarted, but crashing persists.
    Any advice on font management using Muse would be appreciated.
    Thanks,
    Chris
    Macbook Pro, OSX 10.8.4, 2.8GHz, 8GB RAM
    Muse v4.1, Build 8, CL 77415
    AIR Runtime:3.6.05970

    Unrelated.
    LolliMotion has an old version of AIR with a bug that causes Muse to crash.
    Topelovely, please delete the two "tk" folders within the AdobeMusePrelease folder structure in Preferences (on Mac) or (%localappdata% on Windows).
    <from my phone>

  • CS4 Crashes when attempting to change color of characters in story

    Below is a function that we have been using since forever. It changes the color of a specified number of characters in a story starting at a specific position in the textmodel.<br /><br />The crash happens when processing the command (immediately after "11" is displayed).<br /><br />classID is kTextAttrColorBoss.<br /><br />Any help would be greatly appreciated.<br /><br />ErrorCode ApplyTextAttributes(ITextModel * pTextModel, int32 position, int32 length, UID swatchUID, ClassID classID)<br />{<br />     ErrorCode rc = kFailure;<br />     do<br />     {<br />          InterfacePtr<ITextAttrUID> textAttrUID_Color(::CreateObject2<ITextAttrUID>(classID));<br />          if (textAttrUID_Color == nil)<br />          {<br />//               ASSERT_FAIL("TSCore::CreateCharStyle: color invalid");<br />//               CAlert::ErrorAlert("textAttrUID obj is nuil");<br />               break;<br />          }<br /><br />          if (swatchUID == kInvalidUID)<br />          {<br />               ASSERT_FAIL("TSCore::CreateCharStyle: ResolveRGBColorSwatch failed");<br />//               CAlert::ErrorAlert("Invalid color UID");<br />               break;<br />          }<br />          <br />          // Set our color attribute and store it:<br />          textAttrUID_Color->SetUIDData(swatchUID);<br />          <br />          InterfacePtr<ICommand> pApplyTextAttrCmd ( Utils<ITextAttrUtils>()->BuildApplyTextAttrCmd(pTextModel, position,  length, textAttrUID_Color, kCharAttrStrandBoss) );<br />          //pApplyTextAttrCmd->SetUndoability(ICommand::kUndoNotRequired);     <br />CAlert::WarningAlert("11");<br />          rc = CmdUtils::ProcessCommand(pApplyTextAttrCmd);<br />CAlert::WarningAlert("12");<br />          if (rc != kSuccess)<br />               CAlert::WarningAlert("Error on ApplyTextAttrCmd");<br />     }while(false);<br />     <br />     return rc;               <br />}

    Hi Rick,
    I've just been chasing a crash in the Debug version of CS4 InDsign which was asserting with Protective shutdown.
    Like you the manifestation was on a call to ProcessCommand.
    I don't know if it's the same, but on the off chance I'll detail what I discovered.
    I traced back the cause of the crash to an earlier call through our ASB-CSB using the function template and macros, Process and make_functor.
    The function template Process which is in the SelectionASBTemplates.tpp sets up a abortable command sequence on the stack.
    If the result from the CSB function wasn't kSuccess then the sequence was aborted.
    Unfortunately in our CS2 version of the ASB/CSB's we were rather naughtily using the return to pass  a value and not an ErrorCode.
    the result was that our call was forcing an abort everytime.
    I've duplicated and renamed the Process function at the top of our ASB code and missed out the command sequence and it works fine.
    This isn't really the best solution and I'll have to investigate further but at least it solves the crash.
    Below is the new version of Process. I hope it helps you (or someone else out).
    All the best
    Caerwyn  Pearce
    #if (CREATIVE_SUITE_VERSION == CS2)
    // Use standard function template from SelectionASBTemplates.tpp for CS2.
    // It doesn't seem to cause problems, and I'd prefer not to fix it if it's working.
    #define ATLASB_Process        Process
    #else
    //    DESCR:        Call each CSB suite to process the request, wrapping the entire call in a sequence.
    //                Compare this with the one in SelectionASBTemplates.tpp.   
    //                Essentially I've removed the command sequence, and the possibility of an abort.
    //                For some reason this was causing a Protective shutdown in CS4.
    //                Also note the abort takes place if the return value from Process is not kSuccess(aka 0).
    //                For GetSelection we are returning ATLCSB::SelectionType which has a value of -1, -2 or -3
    //                which is most definitely not kSuccess and which was provoking an abort.
    //                However that's not the end of the problem, and the line ErrorUtils::PMSetGlobalErrorCode
    //                seems to be causing problems else where outside of the Process function template.
    //                It may be that our code is not resilient to aborting command sequences.
    //    NOTE:        Most definitely doesn't abort the sequence regardless of errors.
    //    RETURNS:    Error Code.
    template <typename Functor>
    typename Functor::result_type ATLASB_Process (Functor& f, typename Functor::argument_type object, PMIID iid)
        InterfacePtr<const IIntegratorTarget>                     iIntegratorTarget (object, UseDefaultIID ());
        std::auto_ptr<IIntegratorTarget::TargetSuiteCollection> selectionSuites (iIntegratorTarget->GetTarget (iid));
        ErrorCode                                                errorCode = kSuccess;
        if (!selectionSuites->empty())
            for (int32 i = selectionSuites->size () - 1; i >= 0 && errorCode == kSuccess; i--)
                typename Functor::argument_type        iUnknown = static_cast<typename Functor::argument_type>(static_cast<IPMUnknown*>((*selectionSuites) [i]));
                errorCode = f(iUnknown);
        return (errorCode);
    template <typename Functor>
    typename Functor::result_type ATLASB_Process (Functor& f, typename Functor::argument_type object)
        return (ATLASB_Process (f, object, GetDefaultIID (object)));
    #endif

  • Application Crashes/Quits when attempting to change sequence settings

    Application (Final Cut Pro 4) suddenly quits/crashes when attempting to changwe sequence settings. How can this be fixed.
    Also changes made in "user preferences", "timeline options" are not saved.
    Also, audio wave forms no longer show up in "timeline".

    Welcome to the discussions, Streetart.
    This was a bug in 4.0 - you need to upgrade to at least 4.1 to fix it - you can go all the way to 4.5 for free...
    Patrick

  • Have downloaded new Lightroom 5.4 from CC. When trying to launch am getting following error message and then Lightroom crashes: "an error occurred when attempting to change modules". Can't find a thread which relates to this error message.

    Have downloaded new Lightroom 5.4 from CC. When trying to launch am getting following error message and then Lightroom crashes: "an error occurred when attempting to change modules". Can't find a thread which relates to this error message.

    Hi 99jon,
    Many thanks for that. Had been going through this list yesterday and now again today:
    Ref  Solution 1: Lightroom is at its latest update
    Ref  Solution 2: It's interesting how I cannot find the Preferences file anywhere on my mac. (new mac pro, OS 10/9.2) . . .
    Ref  Solution 3: Lightroom doesn't allow me to do anything after the error message appears
    Ref  Solution 4: don't have any Nik Software plug-ins
    Ref  Solution 5: checked permissions and changed all to "Read & Write" - makes no difference
    Ref  Solution 6: I don't have a different user account on my mac.
    Not sure what else to do.

  • Purchased Light Room 5, installed, registered .. but keep getting this screen "An error occurred when attempting to change modules. ... OK" ?? WTF? ?

    Installed Light Room 5.2 from Disc on my mac os x (latest, updated version)
    But keep getting this "An error occurred when attempting to change modules.. OK" no other options/selection and of course if I click OK ... it crashed out ...
    Can anyone help?
    For such a big company .. there isn't any chat option to get to someone to talk to  !!!

    Just because you are the only user on the computer doesn't mean you are the administrator.
    Also, the fact that you are being asked to re-enter your serial number each time you start means that it is not being remembered because something is either preventing it from being written to you disk or (less likely) something is erasing it. This does suggest that you lack certain permissions to make changes to your computer. Not only to save your serial number, but to have access to the Lightroom files needed to change modules (they are just plug-ins within Lightroom).
    Try creating a new user account and run Lightroom from there (making sure that it is part of the Administrator group).
    To get to chat support, you have to choose the options:

  • Another "An error occurred when attempting to change modules" error

    Hello all:
    After using Adobe Photoshop Lightroom on Mac OSX trouble free for the past 6 months, I opened up Lightroom today and received the following error: "An error occurred when attempting to change modules." I had not made any changes in between when it worked normally and when the error started to occur. I beleive the last thing I did before this error occurred was to go into the Print Module.
    Other information--I keep all my RAW .NEF files on an external Firewire (800) 750 GB drive. This is on Mac OS X 10.5 running Adobe Photoshop Lightroom 1.3 and also with 1.4.1. I'm running an iMac 20" with dual-core 2.2 Ghz Intel processors and 4 GB of RAM. I have around 25k images total.
    When I noticed this problem, I was on Lightroom 1.3. I immediately upgraded to 1.4.1, which did not solve the problem. I have also tried many suggestions in the forums including uninstalling the application and removing the .plist file.
    I thought I had come up with a solution by creating a new catalog, then importing the former into it. While this seems to work immediately after the import process, as soon as I close it, the problem manifests itself again.
    More details that may or (likely) may not help:
    - Going to the Develop and Print Modules gives me no problems. However, when I click on Library, Slideshow, or Web, I see the error.
    - I upgraded my Mac to the latest patch level after observing this error to no avail.
    So it looks like my choices are to create a new file and reimport every single time, or lose all of the work I've done for the past 6 months on thousands of images.
    Can anyone please help???? I promise to post the solution when we fix this darn thing so others may benefit. I'd be happy to run through any troubleshooting that y'all would suggest outside of switching to a Canon.
    Thanks!!!!
    Matt

    I'd first check for the existence of a file ending in .lock, which should be present when LR is in use, but if it exists when LR is quit, it can cause problems, and should be deleted.
    Please post back your results.

  • I have Lightroom 5 installed on my MacBook Air but when I try to open the program I receive the message "An error occurred when attempting to change modules".  I uninstalled, emptied trash and re-installed but I continue to get the same message.

    I have Lightroom 5 installed on my iMac which I downloaded (uploaded?) to my MacBook Air (via wi-fi) but unlike the iMac, I'm unable to use the program on the MacBook Air.  When I open the program on the iMac and click 'file', (as people using the program would know) there are 21 options - import pics, export, etc, etc - however, in the version on the MacBook Air, opening 'file' gives me four options - New Catalogue, Open Catalogue, Page Setup and Printer - and with that comes the pop-up message "An error occurred when attempting to change modules".  Any ideas please?

    A forum thread from 3 years ago talking about LR 1.x which had this problem seems to need permissions fixed or new folders created with the corrected permissions.  You might try doing a repair permissions for your user and/or run LR as an administrator user.  I am a PC person so cannot tell you exactly how to do that.
    https://forums.adobe.com/message/1457020

  • An error occurred when attempting to change modules.--when i log in as a guest program works fine but when i log in onb my account that pops up

    An error occurred when attempting to change modules. this comes up on my account on my mac but not when guest account  ?

    I fixed the problem myself, no response in chat nor phone (1 hour in hold an no answer) here's the link, step # 5 saved me! Here's the link seems to be a very common problem, hope it works for you! Error changing modules | Lightroom

  • Lightroom 4: An error occurred when attempting to change modules.

    I downloaded Lightroom 4 a few days ago and installed it on my MacBook Pro. Everything worked great. I thought it would overwrite Lightroom 3, but it didn't. So Lightroom 3 is still installed, but I haven't opened it since I installed Lightroom 4.
    I downloaded Lightroom 4.3 this morning and installed it on the same MacBook Pro.  Using my MacBook Pro and a second monitor, I opened Lightroom 4.3 and worked on some photos. Everything worked great.
    Then I began watching a slideshow in the Lightroom 4.3 slideshow module on the second monitor with my MacBook Pro in the library module. During the slideshow I clicked on the slideshow module on my MacBook Pro and got this error message:
    An error occurred when attempting to change modules.
    Now I can’t get into the slideshow module. I just get the error message.
    I moved the preferences file to the trash and reopened Lightroom 4 but lost color labels, so I put it back in the preferences folder.
    Thanks for your help

    I called Adobe and let them fiddle online with Lightroom on my MacBook Pro. The Adobe tech claims I have a corrupt permissions file. He told me to contact Apple and have them rebuild my permissions file.
    When I contacted Apple, the tech said to startup my MackBook Pro with the option key held down until the first screen appears. Then click on: Recovery HD, arrow, Language, Disk Utility, Macintosh HD, Repair Disk Permissions.
    I did this three times, but some permissions were not repaired. Another Apple tech then suggested I bring my MackBook Pro to a Macintosh authorized repair shop, and have them repair my permissions file. I asked if I can buy Norton Utilities or a similar program and do it myself. The Apple tech said yes, but an authorized repair person will know which permissions to repair and which ones not to touch.
    Unless someone on this forum can tell me how to do this repair myself, I’ll get it repaired next week. And, I’ll post the results as soon as I can.

  • An error occurred when attempting to change modules Lightroom 5 CC

    I've seen other users pose this question but haven't seen any solutions that work for me.  I get the error: "An error occurred when attempting to change modules" when I open up Lightroom 5 on one user, but on another user it opens up fine.  I've tried moving and trashing preferences, uninstalling and reinstalling the program.  It's the same whether I open an existing catalog or try to open Lightroom while creating a new project.  Any help would be greatly appreciated.  This occured after updating to Mavericks on a 2011 iMac.  All other Creative Cloud apps seem to have installed just fine.

    Hi 99jon,
    Many thanks for that. Had been going through this list yesterday and now again today:
    Ref  Solution 1: Lightroom is at its latest update
    Ref  Solution 2: It's interesting how I cannot find the Preferences file anywhere on my mac. (new mac pro, OS 10/9.2) . . .
    Ref  Solution 3: Lightroom doesn't allow me to do anything after the error message appears
    Ref  Solution 4: don't have any Nik Software plug-ins
    Ref  Solution 5: checked permissions and changed all to "Read & Write" - makes no difference
    Ref  Solution 6: I don't have a different user account on my mac.
    Not sure what else to do.

  • An error occurred when attempting to change modules.

    Loaded LR on my iMac, tried to copy & use a catalogue from W7 P/C. Now get "An error occurred when attempting to change modules."  when opening LR. Tried a variety of on-line suggestions, HELP. NB too much hassle with all the other apps to start a new user with such as Adobe and Microsoft.
    George

    Hi, I¹ve been through it again to ensure I¹ve not forgot things. Completely
    removed Lightroom and all files I can find, etc and reloaded. Some tedious
    result. Step 6 is too time consuming at the moment for me, too many things
    on the go since I¹m about to go on holiday and on return I shall need
    Lightroom on this iMac. Any clues? This iMac had Mavericks from new,
    uploaded to Yosemite and then loaded Photoshop CC, Lightroom etc and get
    this damned problem.
    Reading around the web I¹m not the only one with this issue, to suggest a
    new user a/c is a soft option without resolving the issue.
    I hope an expert from Adobe can resolve this,
    Regards, George (retired IT Manager and IT Systems Project Manager)

  • An error occurred when attempting to change modules. message after my regist numb?

    after I put my regist number appears this message= An error occurred when attempting to change modules.
    and I cannot use my lightroom
    What to do?

    http://helpx.adobe.com/lightroom/kb/error-changing-modules-lightroom.html

  • I have a mac, and am trying to install lightroom 3.6, everything says it has installed ok, but when trying to open I get this message...An error occurred when attempting to change modules.

    anybody have any idea?

    https://forums.adobe.com/search.jspa?q=error+occurred+when+attempting+to+change+modules&pl ace=%2Fplaces%2F1383621&depth=…

  • ???  I just installed Lightroom 5 from Amazon for my Mac with 10.10.1 software.  When I open it I get: "An error occurred when attempting to change modules".  It won't import photos and has no side panels under Library.  What should I do?

    I just installed Lightroom 5 from Amazon for my Mac with 10.10.1 software.  When I open it I get: "An error occurred when attempting to change modules".  It won't import photos and has no side panels under Library.  What should I do?

    I Nearly bought from Amazon too but I found a thread from Adobe stating that the only recognized outlet for lightoom is themselves and other outlets serial numbers will not be guaranteed.
    THat at was sufficient for me to buy direct from Adobe, hope you get it sorted.

Maybe you are looking for

  • Cross references are just unusable

    As stated in several other discussions (with NO answers), using cross references in a multi-document book is ridiculous. Every single change made in the document cause a slow-down that is just absurd -- it's taking me 10 minutes to change a SINGLE WO

  • When charging iPhone

    When I was in the office charging my iPhone using my computer there is a sudden power failure that causes my computer force to shut down and now my Phone can't charge at all

  • COMPARISON_PROBLEM

    I created many comparisons, but now will not let me create any comparison and I'm using the same script. Oracle do not give any error, just takes a long time and never ends. while the process runs, I check the view dba_comparison but does not return

  • GR to be created between 14th and 20th of every month as per planng calndr

    Hi Freinds, I have a requirement that PR or PO should be created only betwen 14th and 20th of every month. How can i configure the planning calendar and lot size for this requireent. Thanks in advance Shailesh.

  • Two finger "right click" no longer works!

    This morning using the two-finger click on my MBP 13-inch stopped working. It acts the same way as the one-finger left-click. I have rebooted the computer twice, reset the preferences twice, cleaned the trackpad surface... Nothing. To say the least,