Writing lead out lasts forever

I have a 2.5 minute movie from Fianl Cut Express, that encodes and burns quickly, then takes 15-17 minutes to "write the lead out."
Is that normal?

The important question is, does it burn correctly despite how long it takes?
If so, don't worry about the length. I have burned movies that were totally video only, about 1hr 50min that took over 24 hours to encode and burn. And, I have burned movies that were mostly photos and a few video clips to a total of say 25min. and it took about 10 hours to encode and burn. I think my system is less powerful than yours, but if you get a successful burn however you do it, that is the goal!

Similar Messages

Writing Lead-out takes forever

Well, this did not use to happen but now whenever I try to burn a DVD in my MBP using Toast Titanium 7 - data or video DVD, about 4G worth of material - the programme takes forever to write the lead out. Also, the burning itself is very slow (I'm not talking compressing here. Just burning). I've tried different brands (the same brands I've been using for ages) - Sony, Maxell, Benq - but it's been slow with all of them.
I don't think this is an issue with Toast since I can burn DVDs as usual using Toast in my good ol' iMac.
Has anyone experienced something similar? Does anyone know what's happening?
TIA
Dan

I have been having the same problems with the lead-out, but it is inconsistent. It took forever for me to finish a burn in DVD Studio Pro, then I used popcorn to rip a couple of copies of it and the first copy burned as usual, the second took for bloody ever to finish out. Not sure what the deal is. I never had this problem with my 2.16 MBP CoreDuo, they are new to my Core2Duo machine. This was not the first DVD burning I have done, but the first time I have encountered the problem. Had burned from iTunes and Popcorn previously without problems over the past week. Not sure what the problem is, but if anyone figures it out, I would love to know!

DSP hangs on writing lead out

Has anyone else experienced this? I'm simply burning a disc with a :30 clip as the sole title and it's the first play. The encoding seems to go along fine, but the writing lead-out takes forever. When I force quit the app, I can't eject the disc without rebooting. When I test the disc, it plays fine.
Am I doing something wrong or is this a software issue?

Has anyone else had trouble with certain brands of media?
You can find here info * about quality media *. You can use Toast to read the manufacturer ID in your media to double check its not a fake one. Try to use allways first quality media.
Besides that, you must find your best combination of madia brand + burner. In my personal case, I found the best results using Sony DVD-R . . . the ones that don't work for you !
You can try * Creating Disc Image in DVDSP * and burning with Toastand/or Disk Utility.
Hope that helps !
Alberto

Writing lead-out never finishes

Weird problem.
Project burns correctly, but iDVD 5 will sit on "Writing lead-out" forever. The first time this happened, I forced-quit iDVD 5, but could not eject the disk. I waited about 30 minutes before I forced-quit, then rebooted the system. I was able to eject the disk than, and it worked perfectly in my set top DVD player, as well as in the DVD player app.
Tried to burn again, this time let iDVD run overnight. Woke up this morning to see it still "writing lead-out". As before, the disk worked perfectly, but it required a force-quit/reboot in order for me to eject.
What's going on, and how do I fix it? This is a new clean install of 10.4, just wiped the system last week.

'Writing lead-out' can take a long time - especially on 'short' discs - but overnight is too long.
I suppose you could have a media problem or write speed problem (either of which can produce lots of burn errors).
Have you tried creating a disk image instead of writing directly to writable media?

Writing Lead-out

"Writing lead-out" seems to take forever - ten minutes anyway. Why? Is there a way to speed this up? I had a two minute DVD that I can burn quickly but then writing lead-out goes on and on.
Thanks

and it will go on and on.
What is surprising, is that the longer the DVD, the shorter the write out.
But writing the lead out on really short DVDs takes a bunch of time. No way to speed it up.
best wishes
David
Remember to mark a response helpful or solved

IDVD 09' Freezes when writing lead-out.

Everything seems to work fine until it gets to "writing lead-out" it then seems to freeze up, after about 15-20 minutes it will eject my dvd disc, the screen stays the same as if it's still writing the lead-out. When i play back the dvd disc it stops playing about 1 minute into the movie. but if i play the copy on my hard drive (the one i'm trying to burn to disc) it works fine. Any ideas? Thanks for your time.
Model Name: MacBook Pro
Model Identifier: MacBookPro4,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.5 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 6 MB
Memory: 2 GB
Bus Speed: 800 MHz
Boot ROM Version: MBP41.00C1.B03

Hi DJHYPE
Welcome to apple discussions. Sorry to hear you are having troubles burning to Dvd-R.
Suggestion: Let's narrow things down a bit. Try burning a disc image first to the desktop. You can do that from the file menu within iDvd. Next I'd like you to test the disc image with apple's dvd player app. Assuming it plays as expected, then burn to Verbatim, Maxell, or Tiaiyo Yuden at 4x. Please avoid Memorex while trobleshooting. Thereafter / once we have the issue resolved, feel free to burn to whatever media works best for you and your mac.
http://support.apple.com/kb/HT1583?viewlocale=en_US
Hope this helps but if not just come on back.
Message was edited by: SDMacuser

Writing lead-out problem ...?

Howdy All,
I am using iDVD6 to burn a project to RIDATA DVD+R DL discs. The burn in iDVD6 90% of the time fails at the end (no error logs). However, after playing the DVD on a number of players (computer and dedicated) the DVD seems to be fine (all aspects - movie, slides, finish etc).
A hint at the problem may be that when I use Toast to burn data to the same discs it fails at writing the "Lead-Out" with Mac OS Error -5001. Searching the Internet hasn't really told me much about either of those (Lead-Out) or Mac OS Error -5001.
Burns have worked fine on the Samsung TSSTcorp CD/DVDW SH-S182D DVD Burner before, with other media (Imation DVD+R DL). However, writing the lead-out also failed on an Imation disc when retrying it after it failed on a RIDATA disc. DVD burns the Imation succeed.
Would anyone have any idea of what is happening? Can I just ignore the problem? Is there any easy way I can do a bitwise compare of the DVD and, say, a disk image? Does iDVD do a verify of the burn (although having it tell me the burn failed isn't a good sign if it does)?
If this is a media issue, which I assume it is (although the Imation failing is a problem), what has it go to do with writing the lead-out?
Thanks in advance for any suggestions, experience, comments.
Cheers,
Ashley Aitken.

Hi Klaus,
Thanks for that, I kind-of guessed what "lead out" was about but thanks for giving all the details.
You don't provide any information on what Mac you
have, what OS, how much RAM (example: see my profile
at the bottom of this post), which would help a lot
in diagnosing your problem.
Power Mac G5 - original single CPU model (can't recall the speed) with 2GB RAM etc.
New Samsung DVD Burner (as indicated in previous post), original drive didn't burn dual layer disks.
I've since found that my "backup" with Toast (spanning multiple DVD+R DLs) that failed the Lead Out actually bit-compares with the original.
As the DVDs which failed also seem to work fine in DVD players and on the computer, I wonder if this is really a significant error.
Many here find that Verbatim DVD-R, as well as Fuji
DVD-R, give the fewest problems, even more so when
they are burned at only 2x or 4x.
Thanks that info - its unfortunate we have to burn at slower speeds than the drive is rated - kind of beats the purpose ...
I've previously had pretty good results with Imation DVD+R DL but wanted something that was inkjet printable (DL).
I could only find RiData locally. I now know that they are though of as second tier media, so perhaps the media is the problem.
Cheers,
Ashley.

IDVD (and Toast) never complete writing lead-outs

Hi,
I've noticed occasionally that when using Toast 7 and iDVD 6 that during the writing process, the application in question persists on writing the lead-out. I understand what the correlation between lead-out and DVD playing length are. However, the drive just spins and spins for hours if left to do so. It is a Pioneer DVR-109 (not Apple blessed). The media is Memorex DVD-R 16x and I frankly haven't spent time trying other media yet.
I'm unable to halt the spinning by any means other than rebooting the computer. Usually, the result is fine. Sometimes the DVD doesn't conclude viewing properly.
Any thoughts? Thanks!

Yup, the Memorex disks have been a bit problematic. I was able to burn to an image with iDVD.
I happened to have some TEON DVD-R 8x media a friend gave for another project, and that worked fine. The Memorex 16x media burned at 8x had the same issue.
I had had poor experiences with Verbatim media in the past. But co-workers have raved about the DL disks and the single-layer ones lately. Perhaps I will give them a try.
Thanks!

Long Lead Out Times!!!!! Help

Anyone know how to cut down on writing lead-out times with dvd-studio pro 4
Took about 7 min for a 30 sec clip

The reason that the shorter the clip is, the longer the lead out is because of what I posted earlier. The dvd spec requires a gig minimum of data/content. Not all burners/burning applications will hold true to that spec, so some might not experience the longer lead out times (which is the burning application adding dummy padding data to fill the gig up). If you are using media, then that type is 'approved' by the dvd consortium; and typically is the type of media that will result in the long lead out times (complying to spec). Depending on the speed of the media and burner, 7 minutes would be about right for 1 gig (since the 30 sec clip wouldn't take up much by itself).
If you use media (not 'officially approved by the dvd forum), then it's basically looked at as a data disc, and generally don't end up having the padding data added on; and hence they burn quicker.
Jim

DVD Burning Freezes @ writing the lead out !

Has anyone experienced this? I burn disc all the time with no problem i have used all types of media, Apple disc are the best. but now it freeze at the lead out in DVDSP, Can any one help?

I can't help, but want to add my thoughts: mine used to work fine, now, when I get to the end, I get error messages; I've tried both native burning to the G5 and Toast. Since this is your thread, I'm going to post a separate one, so as not to detract from those who may know your specific difficulty, but boy they sound alike and I wanted to just say -- it's seems to be not exactly an uncommon problem. These are my error messages, I'm curious if they are the same as yours:
Toast:
The drive reported an error:
Sense Key = ILLEGAL REQUEST
Sense Code = 0x72, 0x03
SESSION FIXATION ERROR - INCOMPLETE TRACK IN SESSION
G5:
This disc did not verify correctly and is unreliable. Because this disc is unreliable, discard it and try again using a new, blank disc. (Error code 0x80020063)

IDVD fails at "writing lead in"

I'm trying to create a DVD in iMovie and burn in iDVD. The source file is a DVD that was made from a straight video transfer that my friend made of a low budget movie. That DVD is not encoded with anything.
I ripped in Handbrake and threw it into iMovie, made clips and chapters, yadda yadda. Exported to iDVD. In iDVD I selected one of the 6.0 themes, created backgrounds with still frames I modified in Comic Life and using music I ripped from the audio. Looks great, works fine in iDVD. Then I try to burn.
It takes hours to encode and when I get to Step 5 "burn", it quits after "writing lead in" and says there were problems with the burn process, but doesn't specify anything. It ejects the disk, which is still blank and usable.
As far as trouble shooting goes, I have 53 gigs of free space and have repaired preferences and disk in disk utility. I made a test DVD of some photos using the same theme and media (HP, not sure + or -) and it came out fine. So what gives?
Message was edited by: petehnek

Thanks for the reply. I created a disk image last night but didn't have the time this morning to burn it. I tried a quick and dirty in disk utility but I didn't see a "burn" option. Is that in the pulldown menu? The image did play in DVD.
Message was edited by: petehnek

After the last Yosemite update on my MacBook pro I turned the FileVault on, now my Mac is freezing all the time and encrypting the drive looks like going to last forever and I am unable to use my MacBook pro what must I do???!!!

after the last Yosemite update on my MacBook pro I turned the FileVault on, now my Mac is freezing all the time and encrypting the drive looks like going to last forever and I am unable to use my MacBook pro what must I do???!!!

1. This procedure is a diagnostic test. It changes nothing, for better or worse, and therefore will not, in itself, solve the problem. But with the aid of the test results, the solution may take a few minutes, instead of hours or days.
Don't be put off by the complexity of these instructions. The process is much less complicated than the description. You do harder tasks with the computer all the time.
2. If you don't already have a current backup, back up all data before doing anything else. The backup is necessary on general principle, not because of anything in the test procedure. Backup is always a must, and when you're having any kind of trouble with the computer, you may be at higher than usual risk of losing data, whether you follow these instructions or not.
There are ways to back up a computer that isn't fully functional. Ask if you need guidance.
3. Below are instructions to run a UNIX shell script, a type of program. As I wrote above, it changes nothing. It doesn't send or receive any data on the network. All it does is to generate a human-readable report on the state of the computer. That report goes nowhere unless you choose to share it. If you prefer, you can act on it yourself without disclosing the contents to me or anyone else.
You should be wondering whether you can believe me, and whether it's safe to run a program at the behest of a stranger. In general, no, it's not safe and I don't encourage it.
In this case, however, there are a couple of ways for you to decide whether the program is safe without having to trust me. First, you can read it. Unlike an application that you download and click to run, it's transparent, so anyone with the necessary skill can verify what it does.
You may not be able to understand the script yourself. But variations of the script have been posted on this website thousands of times over a period of years. The site is hosted by Apple, which does not allow it to be used to distribute harmful software. Any one of the millions of registered users could have read the script and raised the alarm if it was harmful. Then I would not be here now and you would not be reading this message.
Nevertheless, if you can't satisfy yourself that these instructions are safe, don't follow them. Ask for other options.
4. Here's a summary of what you need to do, if you choose to proceed:
☞ Copy a line of text in this window to the Clipboard.
☞ Paste into the window of another application.
☞ Wait for the test to run. It usually takes a few minutes.
☞ Paste the results, which will have been copied automatically, back into a reply on this page.
The sequence is: copy, paste, wait, paste again. You don't need to copy a second time. Details follow.
5. You may have started the computer in "safe" mode. Preferably, these steps should be taken in “normal” mode, under the conditions in which the problem is reproduced. If the system is now in safe mode and works well enough in normal mode to run the test, restart as usual. If you can only test in safe mode, do that.
6. If you have more than one user, and the one affected by the problem is not an administrator, then please run the test twice: once while logged in as the affected user, and once as an administrator. The results may be different. The user that is created automatically on a new computer when you start it for the first time is an administrator. If you can't log in as an administrator, test as the affected user. Most personal Macs have only one user, and in that case this section doesn’t apply. Don't log in as root.
7. The script is a single long line, all of which must be selected. You can accomplish this easily by triple-clicking anywhere in the line. The whole line will highlight, though you may not see all of it in the browser window, and you can then copy it. If you try to select the line by dragging across the part you can see, you won't get all of it.
Triple-click anywhere in the line of text below on this page to select it:
PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/libexec;clear;cd;p=(Software Hardware Memory Diagnostics Power FireWire Thunderbolt USB Fonts SerialATA 4 1000 25 5120 KiB/s 1024 85 \\b%% 20480 1 MB/s 25000 ports ' com.clark.\* \*dropbox \*genieo\* \*GoogleDr\* \*k.AutoCAD\* \*k.Maya\* vidinst\* ' DYLD_INSERT_LIBRARIES\ DYLD_LIBRARY_PATH -86 "` route -n get default|awk '/e:/{print $2}' `" 25 N\\/A down up 102400 25600 recvfrom sendto CFBundleIdentifier 25 25 25 1000 MB ' com.adobe.AAM.Updater-1.0 com.adobe.AAM.Updater-1.0 com.adobe.AdobeCreativeCloud com.adobe.CS4ServiceManager com.adobe.CS5ServiceManager com.adobe.fpsaud com.adobe.SwitchBoard com.adobe.SwitchBoard com.apple.aelwriter com.apple.AirPortBaseStationAgent com.apple.FolderActions.enabled com.apple.installer.osmessagetracing com.apple.mrt.uiagent com.apple.ReportCrash.Self com.apple.rpmuxd com.apple.SafariNotificationAgent com.apple.usbmuxd com.citrixonline.GoToMeeting.G2MUpdate com.google.keystone.agent com.google.keystone.daemon com.microsoft.office.licensing.helper com.oracle.java.Helper-Tool com.oracle.java.JavaUpdateHelper com.oracle.java.JavaUpdateHelper org.macosforge.xquartz.privileged_startx org.macosforge.xquartz.startx ' ' 879294308 4071182229 461455494 3627668074 1083382502 1274181950 1855907737 2758863019 1848501757 464843899 3694147963 1233118628 2456546649 2806998573 2778718105 2636415542 842973933 2051385900 3301885676 891055588 998894468 695903914 1443423563 4136085286 523110921 3873345487 ' 51 5120 files );N5=${#p[@]};p[N5]=` networksetup -listnetworkserviceorder|awk ' NR>1 { sub(/^$[0-9]+$ /,"");n=$0;getline;} $NF=="'${p[26]}')" { sub(/.$/,"",$NF);print n;exit;} ' `;f=('\n%s: %s\n' '\n%s\n\n%s\n' '\nRAM details\n%s\n' %s\ %s '%s\n-\t%s\n' );S0() { echo ' { q=$NF+0;$NF="";u=$(NF-1);$(NF-1)="";gsub(/^ +| +$/,"");if(q>='${p[$1]}') printf("%s (UID %s) is using %s '${p[$2]}'",$0,u,q);} ';};s=(' s/[0-9A-Za-z._]+@[0-9A-Za-z.]+\.[0-9A-Za-z]{2,4}/EMAIL/g;/faceb/s/(at\.)[^.]+/\1NAME/g;/\/Shared/!s/(\/Users\/)[^ /]+/\1USER/g;s/[-0-9A-Fa-f]{22,}/UUID/g;' ' s/^ +//;/de: S|[nst]:/p;' ' {sub(/^ +/,"")};/er:/;/y:/&&$2<'${p[10]} ' 1s/://;3,6d;/[my].+:/d;s/^ {4}//;H;${ g;s/\n$//;/s: (E[^m]|[^EO])|x([^08]|02[^F]|8[^0])/p;} ' ' 5h;6{ H;g;/P/!p;} ' ' ($1~/^Cy/&&$3>'${p[11]}')||($1~/^Cond/&&$2!~/^N/) ' ' /:$/{ N;/:.+:/d;s/ *://;b0'$'\n'' };/^ *(V.+ [0N]|Man).+ /{ s/ 0x.... //;s/[()]//g;s/(.+: )(.+)/ (\2)/;H;};$b0'$'\n'' d;:0'$'\n'' x;s/\n\n//;/Apple[ ,]|Genesy|Intel|SMSC/d;s/\n.*//;/\)$/p;' ' s/^.*C/C/;H;${ g;/No th|pms/!p;} ' '/= [^GO]/p' '{$1=""};1' ' /Of/!{ s/^.+is |\.//g;p;} ' ' $0&&!/ / { n++;print;} END { if(n<10) print "com.apple.";} ' ' { sub(/ :/,"");print|"tail -n'${p[12]}'";} ' ' NR==2&&$4<='${p[13]}' { print $4;} ' ' END { $2/=256;if($2>='${p[15]}') print int($2) } ' ' NR!=13{next};{sub(/[+-]$/,"",$NF)};'"`S0 21 22`" 'NR!=2{next}'"`S0 37 17`" ' NR!=5||$8!~/[RW]/{next};{ $(NF-1)=$1;$NF=int($NF/10000000);for(i=1;i<=3;i++){$i="";$(NF-1-i)="";};};'"`S0 19 20`" 's:^:/:p' '/\.kext\/(Contents\/)?Info\.plist$/p' 's/^.{52}(.+) <.+/\1/p' ' /Launch[AD].+\.plist$/ { n++;print;} END { if(n<200) print "/System/";} ' '/\.xpc\/(Contents\/)?Info\.plist$/p' ' NR>1&&!/0x|\.[0-9]+$|com\.apple\.launchctl\.(Aqua|Background|System)$/ { print $3;} ' ' /\.(framew|lproj)|\):/d;/plist:|:.+(Mach|scrip)/s/:[^:]+//p ' '/^root$/p' ' !/\/Contents\/.+\/Contents|Applic|Autom|Frameworks/&&/Lib.+\/Info.plist$/ { n++;print;} END { if(n<1100) print "/System/";} ' '/^\/usr\/lib\/.+dylib$/p' ' /Temp|emac/{next};/(etc|Preferences|Launch[AD].+)\// { sub(".(/private)?","");n++;print;} END { split("'"${p[41]}"'",b);split("'"${p[42]}"'",c);for(i in b) print b[i]".plist\t"c[i];if(n<500) print "Launch";} ' ' /\/(Contents\/.+\/Contents|Frameworks)\/|\.wdgt\/.+\.([bw]|plu)/d;p;' 's/\/(Contents\/)?Info.plist$//;p' ' { gsub("^| |\n","\\|\\|kMDItem'${p[35]}'=");sub("^...."," ") };1 ' p '{print $3"\t"$1}' 's/\'$'\t''.+//p' 's/1/On/p' '/Prox.+: [^0]/p' '$2>'${p[43]}'{$2=$2-1;print}' ' BEGIN { i="'${p[26]}'";M1='${p[16]}';M2='${p[18]}';M3='${p[31]}';M4='${p[32]}';} !/^A/{next};/%/ { getline;if($5<M1) a="user "$2"%, system "$4"%";} /disk0/&&$4>M2 { b=$3" ops/s, "$4" blocks/s";} $2==i { if(c) { d=$3+$4+$5+$6;next;};if($4>M3||$6>M4) c=int($4/1024)" in, "int($6/1024)" out";} END { if(a) print "CPU: "a;if(b) print "I/O: "b;if(c) print "Net: "c" (KiB/s)";if(d) print "Net errors: "d" packets/s";} ' ' /r\[0\] /&&$NF!~/^1(0|72\.(1[6-9]|2[0-9]|3[0-1])|92\.168)\./ { print $NF;exit;} ' ' !/^T/ { printf "(static)";exit;} ' '/apsd|BKAg|OpenD/!s/:.+//p' ' (/k:/&&$3!~/(255\.){3}0/ )||(/v6:/&&$2!~/A/ ) ' ' $1~"lR"&&$2<='${p[25]}';$1~"li"&&$3!~"wpa2";' ' BEGIN { FS=":";p="uniq -c|sed -E '"'s/ +\$[0-9]+\$\$.+\$/\\\2 x\\\1/;s/x1$//'"'";} { n=split($3,a,".");sub(/_2[01].+/,"",$3);print $2" "$3" "a[n]$1|p;b=b$1;} END { close(p);if(b) print("\n\t* Code injection");} ' ' NR!=4{next} {$NF/=10240} '"`S0 27 14`" ' END { if($3~/[0-9]/)print$3;} ' ' BEGIN { L='${p[36]}';} !/^[[:space:]]*(#.*)?$/ { l++;if(l<=L) f=f"\n "$0;} END { F=FILENAME;if(!F) exit;if(!f) f="\n [N/A]";"cksum "F|getline C;split(C, A);C="checksum "A[1];"file -b "F|getline T;if(T!~/^(AS.+ (En.+ )?text(, with v.+)?$|(Bo|PO).+ sh.+ text ex|XM)/) F=F" ("T", "C")";else F=F" ("C")";printf("\nContents of %s\n%s\n",F,f);if(l>L) printf("\n ...and %s more line(s)\n",l-L);} ' ' s/^ ?n...://p;s/^ ?p...:/-'$'\t''/p;' 's/0/Off/p' ' END{print NR} ' ' /id: N|te: Y/{i++} END{print i} ' ' / / { print "'"${p[28]}"'";exit;};1;' '/ en/!s/\.//p' ' NR!=13{next};{sub(/[+-M]$/,"",$NF)};'"`S0 39 40`" ' $10~/$L/&&$9!~"localhost" { sub(/.+:/,"",$9);print $1": "$9|"sort|uniq";} ' '/^ +r/s/.+"(.+)".+/\1/p' 's/(.+\.wdgt)\/(Contents\/)?Info\.plist$/\1/p' 's/^.+\/(.+)\.wdgt$/\1/p' ' /l: /{ /DVD/d;s/.+: //;b0'$'\n'' };/s: /{ /V/d;s/^ */- /;H;};$b0'$'\n'' d;:0'$'\n'' x;/APPLE [^:]+$/d;p;' ' /^find: /d;p;' "`S0 44 45`" ' BEGIN{FS="= "} /Path/{print $2} ' ' /^ *$/d;s/^ */ /;' ' s/^.+ |\(.+$$//g;p ' '/\.(appex|pluginkit)\/Contents\/Info\.plist$/p' ' /2/{print "WARN"};/4/{print "CRITICAL"};' ' /EVHF|MACR/d;s/^.+: //p;' );c1=(system_profiler pmset\ -g nvram fdesetup find syslog df vm_stat sar ps crontab iotop top pkgutil 'PlistBuddy 2>&1 -c "Print' whoami cksum kextstat launchctl smcDiagnose sysctl\ -n defaults\ read stat lsbom mdfind ' for i in ${p[24]};do ${c1[18]} ${c2[27]} $i;done;' pluginkit scutil dtrace profiles sed\ -En awk /S*/*/P*/*/*/C*/*/airport networksetup mdutil lsof test osascript\ -e );c2=(com.apple.loginwindow\ LoginHook '" /L*/P*/loginw*' "'tell app \"System Events\" to get properties of login items'|tr , \\\n" 'L*/Ca*/com.ap*.Saf*/E*/* -d 1 -name In*t -exec '"${c1[14]}"' :CFBundleDisplayName" {} \;|sort|uniq' '~ $TMPDIR.. $ -flags +sappnd,schg,uappnd,uchg -o ! -user $UID -o ! -perm -600 $' '.??* -path .Trash -prune -o -type d -name *.app -print -prune' :${p[35]}\" :Label\" '{/,}L*/{Con,Pref}* -type f ! -size 0 -name *.plist -exec plutil -s {} \;' "-f'%N: %l' Desktop L*/Keyc*" therm sysload boot-args status " -F '\$Time \$(RefProc): \$Message' -k Sender Req 'fsev|kern|launchd' -k RefProc Rne 'Aq|WebK' -k Message Rne 'Goog|ksadm|probe|Roame|SMC:|smcD|sserti|suhel| VALI|ver-r|xpma' -k Message Req 'abn|bad |Beac|caug|corru|dead[^bl]|FAIL|fail|GPU |hfs: Ru|inval|jnl:|last value [1-9]|NVDA$|pagin|proc: t|Roamed|rror|SL|TCON|Throttli|tim(ed? ?|ing )o|WARN' " '-du -n DEV -n EDEV 1 10' 'acrx -o comm,ruid,%cpu' '-t1 10 1' '-f -pfc /var/db/r*/com.apple.*.{BS,Bas,Es,J,OSXU,Rem,up}*.bom' '{/,}L*/Lo*/Diag* -type f -regex .\*[cght] ! -name .?\* ! -name \*ag \( -exec grep -lq "^Thread c" {} \; -exec printf \* \; -o -true $ -execdir stat -f:%Sc:%N -t%F {} \;|sort -t: -k2 |tail -n'${p[38]} '/S*/*/Ca*/*xpc* >&- ||echo No' '-L /{S*/,}L*/StartupItems -type f -exec file {} +' '-L /S*/L*/{C*/Sec*A,Ex}* {/,}L*/{A*d,Ca*/*/Ex,Co{mpon,reM},Ex,In{p,ter},iTu*/*P,Keyb,Mail/B,Pr*P,Qu*T,Scripti,Sec,Servi,Spo,Widg}* -path \\*s/Resources -prune -o -type f -name Info.plist' '/usr/lib -type f -name *.dylib' `awk "${s[31]}"<<<${p[23]}` "/e*/{auto,{cron,fs}tab,hosts,{[lp],sy}*.conf,mach_i*/*,pam.d/*,ssh{,d}_config,*.local} {,/usr/local}/etc/periodic/*/* /L*/P*{,/*}/com.a*.{Bo,sec*.ap}*t {/S*/,/,}L*/Lau*/*t .launchd.conf" list getenv /Library/Preferences/com.apple.alf\ globalstate --proxy '-n get default' -I --dns -getdnsservers\ "${p[N5]}" -getinfo\ "${p[N5]}" -P -m\ / '' -n1 '-R -l1 -n1 -o prt -stats command,uid,prt' '--regexp --only-files --files com.apple.pkg.*|sort|uniq' -kl -l -s\ / '-R -l1 -n1 -o mem -stats command,uid,mem' '+c0 -i4TCP:0-1023' com.apple.dashboard\ layer-gadgets '-d /L*/Mana*/$USER&&echo On' '-app Safari WebKitDNSPrefetchingEnabled' "+c0 -l|awk '{print(\$1,\$3)}'|sort|uniq -c|sort -n|tail -1|awk '{print(\$2,\$3,\$1)}'" -m 'L*/{Con*/*/Data/L*/,}Pref* -type f -size 0c -name *.plist.???????|wc -l' kern.memorystatus_vm_pressure_level '3>&1 >&- 2>&3' " -F '\$Time \$Message' -k Sender kernel -k Message CSeq 'n Cause: -' " );N1=${#c2[@]};for j in {0..9};do c2[N1+j]=SP${p[j]}DataType;done;N2=${#c2[@]};for j in 0 1;do c2[N2+j]="-n ' syscall::'${p[33+j]}':return { @out[execname,uid]=sum(arg0) } tick-10sec { trunc(@out,1);exit(0);} '";done;l=(Restricted\ files Hidden\ apps 'Elapsed time (s)' POST Battery Safari\ extensions Bad\ plists 'High file counts' User Heat System\ load boot\ args FileVault Diagnostic\ reports Log 'Free space (MiB)' 'Swap (MiB)' Activity 'CPU per process' Login\ hook 'I/O per process' Mach\ ports kexts Daemons Agents XPC\ cache Startup\ items Admin\ access Root\ access Bundles dylibs Apps Font\ issues Inserted\ dylibs Firewall Proxies DNS TCP/IP Wi-Fi Profiles Root\ crontab User\ crontab 'Global login items' 'User login items' Spotlight Memory Listeners Widgets Parental\ Controls Prefetching SATA Descriptors App\ extensions Lockfiles Memory\ pressure SMC Shutdowns );N3=${#l[@]};for i in 0 1 2;do l[N3+i]=${p[5+i]};done;N4=${#l[@]};for j in 0 1;do l[N4+j]="Current ${p[29+j]}stream data";done;A0() { id -G|grep -qw 80;v[1]=$?;((v[1]==0))&&sudo true;v[2]=$?;v[3]=`date +%s`;clear >&-;date '+Start time: %T %D%n';};for i in 0 1;do eval ' A'$((1+i))'() { v=` eval "${c1[$1]} ${c2[$2]}"|'${c1[30+i]}' "${s[$3]}" `;[[ "$v" ]];};A'$((3+i))'() { v=` while read i;do [[ "$i" ]]&&eval "${c1[$1]} ${c2[$2]}" \"$i\"|'${c1[30+i]}' "${s[$3]}";done<<<"${v[$4]}" `;[[ "$v" ]];};A'$((5+i))'() { v=` while read i;do '${c1[30+i]}' "${s[$1]}" "$i";done<<<"${v[$2]}" `;[[ "$v" ]];};A'$((7+i))'() { v=` eval sudo "${c1[$1]} ${c2[$2]}"|'${c1[30+i]}' "${s[$3]}" `;[[ "$v" ]];};';done;A9(){ v=$((`date +%s`-v[3]));};B2(){ v[$1]="$v";};for i in 0 1;do eval ' B'$i'() { v=;((v['$((i+1))']==0))||{ v=No;false;};};B'$((3+i))'() { v[$2]=`'${c1[30+i]}' "${s[$3]}"<<<"${v[$1]}"`;} ';done;B5(){ v[$1]="${v[$1]}"$'\n'"${v[$2]}";};B6() { v=` paste -d: <(printf "${v[$1]}") <(printf "${v[$2]}")|awk -F: ' {printf("'"${f[$3]}"'",$1,$2)} ' `;};B7(){ v=`grep -Fv "${v[$1]}"<<<"$v"`;};C0() { [[ "$v" ]]&&sed -E "$s"<<<"$v";};C1() { [[ "$v" ]]&&printf "${f[$1]}" "${l[$2]}" "$v"|sed -E "$s";};C2() { v=`echo $v`;[[ "$v" != 0 ]]&&C1 0 $1;};C3() { v=`sed -E "${s[63]}"<<<"$v"`&&C1 1 $1;};for i in 1 2 7 8;do for j in 0 2 3;do eval D$i$j'(){ A'$i' $1 $2 $3; C'$j' $4;};';done;done;{ A0;D20 0 $((N1+1)) 2;D10 0 $N1 1;B0;C2 27;B0&&! B1&&C2 28;D12 15 37 25 8;A1 0 $((N1+2)) 3;C0;D13 0 $((N1+3)) 4 3;D23 0 $((N1+4)) 5 4;D13 0 $((N1+9)) 59 50;for i in 0 1 2;do D13 0 $((N1+5+i)) 6 $((N3+i));done;D13 1 10 7 9;D13 1 11 8 10;B1&&D73 19 53 67 55;D22 2 12 9 11;D12 3 13 10 12;D23 4 19 44 13;D23 5 54 12 56;D23 5 14 12 14;D22 6 36 13 15;D22 20 52 66 54;D22 7 37 14 16;D23 8 15 38 17;D22 9 16 16 18;B1&&{ D82 35 49 61 51;D82 11 17 17 20;for i in 0 1;do D82 28 $((N2+i)) 45 $((N4+i));done;};D22 12 44 54 45;D22 12 39 15 21;A1 13 40 18;B2 4;B3 4 0 19;A3 14 6 32 0;B4 0 5 11;A1 17 41 20;B7 5;C3 22;B4 4 6 21;A3 14 7 32 6;B4 0 7 11;B3 4 0 22;A3 14 6 32 0;B4 0 8 11;B5 7 8;B1&&{ A8 18 26 23;B7 7;C3 23;};A2 18 26 23;B7 7;C3 24;D13 4 21 24 26;B4 4 12 26;B3 4 13 27;A1 4 22 29;B7 12;B2 14;A4 14 6 52 14;B2 15;B6 14 15 4;B3 0 0 30;C3 29;A1 4 23 27;B7 13;C3 30;B3 4 0 65;A3 14 6 32 0;B4 0 16 11;A1 26 50 64;B7 16;C3 52;D13 24 24 32 31;D13 25 37 32 33;A2 23 18 28;B2 16;A2 16 25 33;B7 16;B3 0 0 34;B2 21;A6 47 21&&C0;B1&&{ D73 21 0 32 19;D73 10 42 32 40;D82 29 35 46 39;};D23 14 1 62 42;D12 34 43 53 44;D12 22 20 32 25;D22 0 $((N1+8)) 51 32;D13 4 8 41 6;D12 21 28 35 34;D13 27 29 36 35;A2 27 32 39&&{ B2 19;A2 33 33 40;B2 20;B6 19 20 3;};C2 36;D23 33 34 42 37;B1&&D83 35 45 55 46;D23 32 31 43 38;D12 36 47 32 48;D13 10 42 32 41;D13 37 2 48 43;D13 4 5 32 1;D13 4 3 60 5;D12 21 48 49 49;B3 4 22 57;A1 21 46 56;B7 22;B3 0 0 58;C3 47;D22 4 4 50 0;D12 4 51 32 53;D23 22 9 37 7;A9;C2 2;} 2>/dev/null|pbcopy;exit 2>&-
Copy the selected text to the Clipboard by pressing the key combination command-C.
8. Launch the built-in Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Click anywhere in the Terminal window and paste by pressing command-V. The text you pasted should vanish immediately. If it doesn't, press the return key.
9. If you see an error message in the Terminal window such as "Syntax error" or "Event not found," enter
exec bash
and press return. Then paste the script again.
10. If you're logged in as an administrator, you'll be prompted for your login password. Nothing will be displayed when you type it. You will not see the usual dots in place of typed characters. Make sure caps lock is off. Type carefully and then press return. You may get a one-time warning to be careful. If you make three failed attempts to enter the password, the test will run anyway, but it will produce less information. In most cases, the difference is not important. If you don't know the password, or if you prefer not to enter it, press the key combination control-C or just press return three times at the password prompt. Again, the script will still run.
If you're not logged in as an administrator, you won't be prompted for a password. The test will still run. It just won't do anything that requires administrator privileges.
11. The test may take a few minutes to run, depending on how many files you have and the speed of the computer. A computer that's abnormally slow may take longer to run the test. While it's running, there will be nothing in the Terminal window and no indication of progress. Wait for the line
[Process completed]
to appear. If you don't see it within half an hour or so, the test probably won't complete in a reasonable time. In that case, close the Terminal window and report what happened. No harm will be done.
12. When the test is complete, quit Terminal. The results will have been copied to the Clipboard automatically. They are not shown in the Terminal window. Please don't copy anything from there. All you have to do is start a reply to this comment and then paste by pressing command-V again.
At the top of the results, there will be a line that begins with the words "Start time." If you don't see that, but instead see a mass of gibberish, you didn't wait for the "Process completed" message to appear in the Terminal window. Please wait for it and try again.
If any private information, such as your name or email address, appears in the results, anonymize it before posting. Usually that won't be necessary.
13. When you post the results, you might see an error message on the web page: "You have included content in your post that is not permitted," or "You are not authorized to post." That's a bug in the forum software. Please post the test results on Pastebin, then post a link here to the page you created.
14. This is a public forum, and others may give you advice based on the results of the test. They speak only for themselves, and I don't necessarily agree with them.
Copyright © 2014 by Linc Davis. As the sole author of this work, I reserve all rights to it except as provided in the Use Agreement for the Apple Support Communities website ("ASC"). Readers of ASC may copy it for their own personal use. Neither the whole nor any part may be redistributed.

"writing lead-in" problem

hello
we are experiencing an very frustrating problem. we are burning a Dual Layer disk with a one hour video, and a slide show. We have followed all of the pointers listed here about compatible file types and audio files. When we go to burn the disk it goes through all the processes until we get to "Burn" and then it simply ejects our disk (we have tried several different blank disks) and it gives the following message, "Current operation: Writing lead-in..." . the progress bar keeps going but nothing happens. Even if we put the disk back in this message remains.
We have tried the same process on the imac internal DVD burner as well as an external Sony DVD burner with the same result.
Does anyone know what "Writing lead-in" means and can you guess what might be causing idvd to eject our disk at this point?
Thanks in advance.
Bruce Trono

Hi Bruce!
For what it is worth, 'Lead In':
Marks the start of each session on the disc.
The process of writing a lead-in and lead-out is called disc fixation and it generates a new disc session.
On CD media it is the area that contains the TOC data and precedes each program area. The main channel in the Lead-in area contains audio or data null information. This area is coded as track zero. The Q Sub-channel in this area is coded with the Table of Contents information.
The DVD Lead-in area is the area comprising physical sectors 1.2 mm wide or more adjacent to the inside of the Data area. The area contains the Control data and precedes the Data area.
Which helps not a lot in diagnosing your problem!
Like F Shippey asked, what media are you using, and are you sure you have a superdrive that can burn dual layer disks?
Indeed, why are using dual layer disks when the project is only one hour long?

IDVD quits while writing lead in showing 3 minutes left

Start to burn disk and audio and video starts but as soon as it gets to "writing lead-in" it shows 3 minutes remaing. Progress bar stops moving. Drive ejects disk before it's done burning.
Using iDVD 7.1.2
Doing a Share to iDVD from iMovie 11.
Used Memorex dvd-r and Verbatim dvd-r with same results.
Made disk image that appears to be ok.
Is this proving to be bad DVD disk or is this something internal?

Thanks for the info.
I set burn to 4 x and best quality. Also used a more generic brand of DVD.
Combined it seemed to work.
I found out through an outside source that the coating on maxells wont work with older super drives.
The Verbatim didn't work either. It may have not worked because I bought the ones that are printed to look like vintage super 8 film reel. That extra layer of ink and coating may be part of the problem.
I got some generic office max dvd's. Worked fine.

Toast 7 Not writting lead out!

Hello,
I'm having some issues with Toast 7 stalling while writting the lead out. I've tried getting an answer from Roxio but the online help always says that there are no agents available.
I'll be trying to write a DivX file or make my own dvd from those avi files. It will write all the way to the end where it says that it's writting the lead-out, then it just stays there. I've been told to not try cheap media which i've gone against and bought the good stuff (sony and imation) and it still stalls! Even when the disk is only half full it stalls on the lead out. So it's not the disk space. My external dvd writter has worked many times in the past. It seems that since my last update & wipe I did it's started doing this again? I pray that there's a patch or something out there for it. or somthing, it's pretty frustrating.
I need some help as soon as possible. Please help me.

DOES NOBODY HAVE ANY HELP FOR ME??!!
I've attempted to contact Roxio and i've looked and posted on the Roxio board. Their online support chat never works, i've updated my firmware and still the issue continues on good media (not cheap).

Writing lead out lasts forever

Similar Messages

Maybe you are looking for