Problem preparing imovie error code project too long

I am creating imovie which is only 16 minutes long and has still images and songs. Previous copy was copied using iDVD but now error message comes up saying project is too long. Please Help.

A DVD can actually hold up to 120 minutes, including titles etc.
Best Performance is for movies of up to 60 minutes.
Best Quality is for movies of 61 - 120 minutes.
In both cases the maximum length includes titles, transitions and effects etc. Allow about 15 minutes for these.
(And whilst checking these settings in iDVD Preferences, make sure that the settings for NTSC/PAL and DV/DV Widescreen are also what you want.)
An alternative, if your project can not be edited down to 120 minutes, is to use Toast for the burning, which has a setting 'compress to fit' for longer projects, albeit with a minimal quality loss.

Similar Messages

  • How to Update a clob column..it gives error string literal too long

    I am trying to update a clob column of a table but it gives error string literal too long plz tell me what's the issue
    ORA-01704: string literal too long

    Peeyush wrote:
    I am trying to update a clob column of a table but it gives error string literal too long plz tell me what's the issue
    ORA-01704: string literal too longThere's a problem with my car. It won't start. Why won't it start? Please tell me!
    Oh wait, you can't, because I haven't given you nearly enough information...
    In other words, if you would like help in trying to work out where you've gone wrong, you should provide a small enough example of your code that demonstrates the error. We might then actually stand a chance of being able to help you!

  • Large XML Publisher reports fail with client-error-request-value-too-long

    We are running BI Publisher 5.6.3 with Oracle Applications 11.5.10.2 (ATG.H RUP 5), and are having frequent failures with client-error-request-value-too-long messages on large PDF reports that cause the entire report to not print.
    The exact error message is as follows:
    lp: unable to print file: client-error-request-value-too-long
    Pasta: Error: Print failed. Command=lp -c -dPDX_B6_1LJ5200NEAST /logs/temp/pasta3262_0.tmp
    Pasta: Error: Check printCommand/ntPrintCommand in pasta.cfg
    Pasta: Error: Preprocess or Print command failed!!!
    APP-FND-00500: AFPPRN received a return code of failure from routine FDUPRN. Program exited with status 1
    Cause: AFPPRN received a return code of failure from the OSD routine FDUPRN. Program exited with status 1.
    Action: Review your concurrent request log file for more detailed information.
    I have Google'd client-error-request-value-too-long, and found it is a common CUPS issue on Linux. The popular solutions (having /var/spool/cups and /var/spool/cups/tmp) are already in place. Also, the temp files are nowhere near 2 GB (44MB).
    Has anyone had this issue with BI Publisher on Linux?

    Thanks for the link. It looks like the sysadmins have throttled cups to low to allow large bitmapped print jobs:
    grep MaxRequestSize cupsd.conf
    # MaxRequestSize: controls the maximum size of HTTP requests and print files.
    MaxRequestSize 10M
    I am trying to get a more reasonable size limit.

  • Large BI Publisher reports fail with client-error-request-value-too-long

    We are running BI Publisher 5.6.3 with Oracle Applications 11.5.10.2, and are having frequent failures with client-error-request-value-too-long messages on large PDF reports that cause the entire report to not print.
    The exact error message is as follows:
    lp: unable to print file: client-error-request-value-too-long
    Pasta: Error: Print failed. Command=lp -c -dPDX_B6_1LJ5200NEAST /logs/temp/pasta3262_0.tmp
    Pasta: Error: Check printCommand/ntPrintCommand in pasta.cfg
    Pasta: Error: Preprocess or Print command failed!!!
    APP-FND-00500: AFPPRN received a return code of failure from routine FDUPRN. Program exited with status 1
    Cause: AFPPRN received a return code of failure from the OSD routine FDUPRN. Program exited with status 1.
    Action: Review your concurrent request log file for more detailed information.
    I have Google'd client-error-request-value-too-long, and found it is a common CUPS issue on Linux. The popular solutions (having /var/spool/cups and /var/spool/cups/tmp) are already in place. Also, the temp files are nowhere near 2 GB (44MB).
    Has anyone had this issue with BI Publisher on Linux?

    The linux sysadmins set the cups max_request_size at 10 MB, which was causing this error. Once the restriction was lifted, the reports ran without error.

  • Client-error-request-value-too-long

    What is this error???? I am trying to add an Epson 1280 printer and I get this error. I have the most current driver and not sure why this isn't working.

    My flatmate had this "client-error-request-value-too-long" problem with her (powerpc) powerbook. Nearly everything I tried didn't work:
    1) Reinstalling drivers
    2) Permissions repair
    3) Resetting print system using Fixamac's Printer Setup Repair Utility
    4) Updating from 10.4.10 to 10.4.11
    5) Using the command line to try and recreate the directory: /var/spool/cups/tmp (which told me it already existed)
    6) Using Transmit (with show invisible files turned on) to browse to /var/spool/cups/ and try and recreate the tmp folder
    On the last point I couldn't change anything about the /var/spool/cups/ directory because the permissions were corrupted in some way. It keep telling me tmp already existed but I couldn't see it.
    In the end what did work was enabling and logging in as root, browsing to /var/spool/ using Transmit and deleting the cups folder and then recreating. It took a few tries to delete too, but in the end I managed to remove it.
    Of course I wouldn't actually recommend this. I'm no Unix geek so god knows what I might have broken in the process, so I'm going to reinstall her system with the Archive and Install options when I get a chance, which is what I'd recommend doing in the first place to anyone having this problem.

  • Error: "client-error-request-value-too-long" when trying to add printer

    After installing the 10.4.9 Combo update, my HP 1350 All-in-One printer was not recognized. I reinstalled the driver, but now I can't add the printer. I get the error message "client-error-request-value-too-long" when trying to add the printer. Has anyone else experienced a similar problem.
    Thanks in advance

    Well, I tried all of that and I'm still getting the error message. I've also repaired disk permissions and run Disk Warrior. When I repaired disk permissions, many HP printer items showed up in the list.

  • USB Printing - client-error-request-value-too-long

    A little while back, my iSight suddenly stopped working and so I did a full format and reinstall to 'fix' the problem. The problem wasn't 'fixed' through this action. Instead, I had to disconnect power and let the computer sit there for a bit and think about what it had done (naughty iMac). Anyway... Another USB-related problem just popped up - this time with my printer.
    The printer is a Canon IP4000 and I just installed the latest drivers to try to fix this error. The first error was something about not being able to write to the device. I thought that was stupid and would probably be fixed by deleting the printer and then reinstalling it. I have so far 'uninstalled' the printer (more or less just removed it from the printers list in the printer utility) and now I can't re-add it to the list to install it. The error reads as follows:
    An error occurred while trying to add the selected printer.
    client-error-request-value-too-long
    I have tried Google but I just don't have the time to sort through all kinds of explainations on how CUPS works on Linux (apparently, this error is related to CUPS in some way). I also tried searching the forum for the error message but found nothing. So here I am again asking for some help from those who might have seen this problem before.
    This is on a fresh install and I have tried it on newly created users to no avail.
    Thanks for any help! -Thomas

    I've recently had this error which came up because the spool folder was missing. In the terminal:
    sudo mkdir /private/var/spool
    sudo mkdir /private/var/spool/cups
    puts the proper folders in their place. Repair permissions afterwards.
    Through the cups web interface, the error is "Request entity too large"
    Panther has the same folders, but a different error comes up.
    The above cups folder has different permissions than the default. Probably the same for Tiger and Panther but just to be safe, repair permissions.

  • Error: Q15064 Lexeme too long

    We have installed Sun workshop6.0 which has c compiler included, in Testing machine to compile Grapheq testing programs which we wrote .When we compile schedule editor, we came across the error Error: Q15064 Lexeme too long, truncating. We checked the Grapheqref.pdf which gives this error description as "A token which was too long for the lexical analyzer was found. Shorten the token.".
    Please help me if u know what Configuration we need to change for c compiler.
    Thanks in advance,
    Regards,
    Prasanna

    This message is not coming from the C compiler It is coming from the application. You need to ask the supplier of the application.

  • Imovie error The project could not be prepared for publishing because an error occurred. (-50)

    I can't export my imovie project.
    Appears this message:
    "The project could not be prepared for publishing because an error occurred. (-50)"
    What can I do?

    Thanks for the details.  We have a similar problem (see my post below) and are in the process of adding back each clip and then testing for export.  My question is, once iMovie is unable to export the project, does it render the file "bad" and prevent exporting even if you remove the "poisned" clip(s)?
    ++++++++++++++++++++++++++++++++++++++++++++++++
    Hello,  We are having a similar problem running iMovie '09.  We get the exact same error as you reported. 
    "Unable to prepare project for publishing" The project could not be prepared for publishing because an error occurred (-50)
    We have a very similar situation were we have multiple repeated clips.  However, our clips are 2.4 's.  Like you, we took the finished project and started eliminating edits that we thought might be preventing it from exporting. The following actions still would not allow the project to export:
    removing title pages
    removing transitions
    removing imported music from iTunes
    removed another clip from another event
    closed all other programs
    closed iMovie, powered off computer, opened iMovie, tried to export
    reconfirmed the last project exported would still export - it did without issueThe only difference between the project that will export and the one that does not are these short (2.4's) repeating clips
    When we create the new project from the recorded event without making any edits (just as recorded), it exports without issue.  We have started the arduous task of adding back in each edit and testing it for export until we determine which edit is causing it to "not export".  This is a very inefficient way of troubleshooting.
    This is a science project for my son and we need to be able to save it as a QT or mpeg4 movie so that he can submit it to his teacher for viewing and a grade!
    Any ideas from any other users would be greatly appreciated.

  • Can't publish-project too long

    I will give more background later, but to put my issue shortly, I will give the following info:
    I have one video clip that I have trimmed (by taking a bit from the beginning and a bit from the end).  It is almost 2 hours long (1:56 to be exact).
    So, I have one clip in the project and no music.  A pretty simple project.  I say share with iDVD.  It says it will take about 2 hours or so... and it seems to be going through all the appropriate processing, then, as it approaches the end of the process, it pops up with an error message from iMovie:
    Unable to prepare project for publishing.
    The project could not be prepared for publishing because an error occurred. (Project is too long.)
    (I'd give the little illustration, but whenever I bring up "Grab", it hides the pop-up error.  Once I click on iMovie, the pop-up error returns.  Weird!-- But this is a moot point as this isn't the problem- I need to publish my project to iDVD.)
    Other facts:
    I have 11.4 GB available on my hard drive, so this is not the issue.  (I had cleared up space thinking that was the problem as this is the second or third time I've attempted)
    The original movie file that is in the project is about 2.29 GB in size.
    Oddly, it seems that an error pops up under my Aperture saying I don't have sufficient space for the library volume.  I was doing nothing on the MacBook while this project was publishing, so not sure why that is coming up... and not sure why it would say there isn't sufficient space for the library if I have tons of space on my hard drive.  And, why is it popping up each time I try to publish my iMovie project?  There aren't any photos from Aperture even in the project.
    This mp4 file that I am using is actually a file produced by Elgato Video Capture (This is a VHS to digital transfer), if this matters at all.
    Previously, I had imported some jpegs into iPhoto, (for another iMovie project that I needed photos for), but iMovie could not "see" them even though they were there plain as day.  So, I imported into Aperture those same photos, and iMovie was able to "see" those in Aperture (these 11 photos are all I have in Aperture as I have not ventured into Aperture much yet-- but needed a work around for some reason on this OTHER project).  I give this info in the instance that this Aperture to iMovie link could be causing any issue with this project despite no photos being included in this project.

    Even though it might seem like a lot of space those 11.4GB of space, you still might need a little more especially as iDVD can only just about handle 2hr. worth of video material to fit on one DVD-R. The target free space you might want to get closer to is something like 25GB of open free space (almost double what you have free now). Partially the reason is all that 2 hours needs to be converted from the format it's in now Apple Intermediate Codec (AIC) to full MPEG-2. That's where things really start to expand and inflate. Then iDVD takes that whole MPEG-2 encoded file and makes an equally large Disk Image out of it that can then be burned to DVD-R. So the space requirements balloon up very quickly.
    Sharing directly to iDVD can be full of surprises. Instead what you might want to try rather than Sharing to DVD is instead sharing it to the Media Browser from iMovie first (Large Size). Quit iMovie wants it completes the encoding. Open iDVD, go to the Media button down in the lower right hand corner of the Window and at the top of the Media Browser choose Movies. In the window you should see an iMovie Star icon with the project you shared immediately beneath that. Create a new project and drag that shared iMovie into the project window.

  • IMovie error code (-50) when exporting video

    iMovie 09 suddenly started to generate the following error when sharing/exporting video:
    The project could not be prepared for publishing because an error occurred. (-50)
    Exporting using Quick Time option from the Share menu works. The other options fail with the error.
    OS is 10.7.3.
    For what is worth, I have uninstalled DivX recently.
    Any idea how to troubleshoot this?
    Thank you!

    I am having the same problem i have osx 10.7.2 and i get the error code 50 and the error code 8003  what can be done. support treats you like your oblivious to computers and know nothing.  First macbook but not first download or computer.  When using Microsoft systems you download and play so what gives here if this platform is suppose to be the best

  • Consolidating Library Error: File Name Too Long, But What File?

    I am trying to consolidate my library to put all my music (very unorganized) in one spot so I can back it all up. When I try to consolidate, it takes a second to prepare, then immediately brings up an error window saying "Copying Music Failed. The file name was invalid or too long."
    How do I fix this? I really would like to back up my music!

    Hi, ZeroGravity107.
    This can be a tricky problem to figure out since iTunes doesn't specify what file name is "invalid or too long" and there's no documentation on what determines if a file name is "invalid or too long".
    We had one user report that he was able to use his/her keen eyesight to note the last file that appeared before the error message appeared and it turned out that file was the cause of his/her trouble.
    If your eyesight isn't that keen, I'd suggest concentrating on the file name being too long possibility.
    The entire directory path leading to the file is considered part of the file name so, as an example, iTunes' default settings might place a particular file at C:\Documents and Settings\ user name \My Documents\My Music\iTunes\iTunes Music\artist folder\album folder\whatever.m4a.
    Is the directory path leading to your consolidated location much longer than that?
    polydorus has suggested a way to look over your file names: Assuming your music is currently in the default location, make your way there with Windows Explorer and select List in the View menu menu and see if anything stands out as being unusual.

  • FTP Error: 550 Arguments too long

    I am getting "550 Arguments too long" error code with message while try to FTP list the files from solaris 9 by using NetComponents.jar. (remote folder has more than 16000 files) But I am able to FTP list greater than 30000 files properly from solaris 8. Does anyone have seen a similar problem?

    Hello,
    I have the same problem. I connect to FTP server (Version wu-2.6.2+Sun) on SunOS 5.9. There is already patch 114564-09 installed. I try type "ls <directory>" command, where directory includes about 20 thousand files and FTP server returns: "550 Arguments too long".
    When I try "ls /directory2" command, where directory2 is empty, FTP server returns:
    550 /directory2/*: No such file or directory.
    This behaviour is same as behaviour of unix "ls" command, if I had type "ls /directory2/*" in the command line on the empty directory and on the directory with too many files.
    My conclusion: FTP server on SunOS have a new bug. It takes file list with "ls" command and appends to directory name "*" (asterisk).
    Can anybody help me? Is there some patch to solve this problem?

  • IMovie error causes project to disappear

    To anyone who's out there reading this:
    I was working on a movie project in iMovie (which I spent weeks working on.)  Randomly, iMovie gave me an error, and suddenly closed.  Then, my project was gone forever!  I tried all types of forums, and support communities.  Nothing helped.  Apple geeks, if you've encountered this error, please add some fix for this in the future.  I am a HUGE Apple supporter.  I've basically coerced all of my employees and friends to buy Apple products because this sort of "error" issue doesn't happen.  Well, it did!  And I feel pretty sheepish about all the money I've spent on reliable hardware and software.  However, if anyone has any trick to recover my lost project, that would be helpful.  Other than that, Apple, Inc. please help your loyal customers not lose faith in you!  Windows 8 is sounding pretty good right now!  Just saying.  And I HATE Microsoft products.

    Hi
    No Computer is 100% secure - Apple/Mac HP IBM or Whatever !
    There are things that one Can not do when using iMovie. (Very common origin to this trouble)
    • DO NOT move or alter any folder named
    - iMovie Event's
    - iMovie Project's
    (or resembling to this)
    ON DESKTOP/FINDER
    If You do - then iMovie get lost - as You then breaks the link back to it.
    Medicine (that might help) : When iMovie is NOT RUNNING - Move them back to their original places.
    This can work - if they was not moved out to an external hard disk - NOT FORMATTED as Mac OS Extended.
    ( formatted as: UNIX / DOS / FAT32 / Mac OS Exchange - can not be used for Video ! )
    Else - there are zillions of things that can go wrong - see my long long list of notes:
    When iMovie doesn't work as intended this can be due to a lot of reasons
    • iMovie Pref files got corrupted - trash it/they and iMovie makes new and error free one's
    • Creating a new User-Account and log into this - forces iMovie to create all pref. files new and error free
    • Event or Project got corrupted - try to make a copy and repair
    • a codec is used that doesn't work
    • problem in iMovie Cache folder - trash Cache.mov and Cache.plist
    • version miss match of QuickTime Player / iMovie / iDVD
    • preferences are wrong - Repair Preferences
    • other hard disk problem - Repair Hard Disk (Disk Util tool - but start Mac from ext HD or DVD)
    • External hard disks - MUST BE - Mac OS Extended (hfs) formatted to work with Video
    ( UNIX/DOS/FAT32/Mac OS Exchange - works for most other things - but not for Video )
    • USB-flash-memories do not work
    • Net-work connected hard disks - do not work
    • iPhoto Library got problems - let iPhoto select another one or repair it. Re-build this first then try to re-start iMovie.
    This You do by
    _ close iPhoto
    _ on start up of iPhoto - Keep {cmd and alt-keys down}
    _ now select all five options presented
    _ WAIT a long long time
    • free space on Start-Up (Mac OS) hard disk to low (<1Gb) - I never go under 25Gb free space for SD-Video (4-5 times more for HD)
    • external devices interferes - turn off Mac - disconnect all of them and - Start up again and re-try
    • GarageBand fix - start GB - play a few notes - Close it again and now try iMovie
    • Screen must be set to million-colors
    • Third-party plug-ins doesn't work OK
    • Run "Cache Out X", clear out all caches and restarts the Mac
    • Let Your Mac be turned on during one night. At about midnight there is a set of maintenance programs that runs and tidying up. This might help
    • Turn off Your Mac - and disconnect Mains - for about 20-30 minutes - at least this resets the FireWire port.
    • In QuickTime - DivX, 3ivx codec, Flip4Mac, Perian etc - might be problematic - temporarily move them out and re-try
    (I deleted the file "3ivxVideoCodec.component" located in Mac HD/Library/Quicktime and this resolved my issue.)
    buenrodri wrote
    I solved the problem by removing the file: 3ivxVideoCodec.component. after that, up-dated iMovie runs ok.
    Last resort: Trash all of iMovie and re-install it
    Yours Bengt W

  • What is iMovie error code -49? I get when I try to share my edited video in 720p with i tunes.

    I edited a homevideo on my new mac Book pro 15-inch. When I tried to share in 720p with iTunes I get a message that says it can't prepare it and gives error code -49. Does anyone know what that means? I have abour 90 GB disc space, so that can't be the problem.

    Hey,
    A lot of times iMovie does that when you are trying to prepare a large file. Try to do the same thing in to iTunes as a Mobile or a Medium file and see if it exports fine?

Maybe you are looking for