"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?

Similar Messages

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.

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?

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.

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

Writing to DLT problem

I'm trying to create a DLT from DVD Studio Pro 4.2 (running under Snow Leopard) and it recognizes that the drive is there however when I come to output it gets to the formatting stage, writing lead-in and does nothing! Has anyone else encountered this at all?
Thanks in advance for any help

Welcome to the Boards
Have not seen any issues about Snow Leopard and DLT drives yet, though there have been some issues from time to time in the past.
Some details on the set up (card, DLT drive, Computer, which version of DVD SP 4.2.x) may help, but Snow Leopard is still fairly new. Have you checked to see if there are new drivers for the card for Snow Leopard? How much room is on your hard drives? (Sometimes a drive may be full and can cause problems writing out...)
If you are on deadline and find yourself hitting a wall, something to check into while troubleshooting is whether the replication plant can take DDP off a hard drive (or DVD-R, though those are more risky.)
Some places will also write out projects to DLT for you and do some premastering checks, like dvdverification.com

Idvd ejects the disk during the "multiplexing and burning" / "writing lead-in" portion. When I check, there's nothing on the disk

idvd ejects the disk during the "multiplexing and burning" / "writing lead-in" portion. When I check, there's nothing on the disk.

What brand and type of disk are you using? What speed are you burning at? Are you able to create a disk image of the project?
Try this basic troubleshooting fix:
1 - delete the IDVD preference file, com.apple.iDVD.plist, that resides in your
User/Home/Library/ Preferences folder.
2 - delete IDVD'S cache file, Cache.db, that is located in your
User/Home/Library/Caches/com.apple.iDVD folder.
3 - launch IDVD and try again.
NOTE: In Lion and Mountain Lion the Home/Library folder is now invisible. To make it permanently visible enter the following in the Terminal application window: chflags nohidden ~/Library and hit the Enter button - 10.7: Un-hide the User Library folder.

"The even-numbered length of the DEC field I_DFZ_EX can lead to problems"

Hi All,
I am getting the following warning message while activating the PP datasources,
2LIS_04_P_MATNR
2LIS_04_P_ARBPL
Warning Message: "The even-numbered length of the DEC field I_DFZ_EX can lead to problems"
                               "The even-numbered length of the DEC field I_DLZ_EX can lead to problems"
                               "The even-numbered length of the DEC field S_DFZ_EX can lead to problems"
                               "The even-numbered length of the DEC field S_DLZ_EX can lead to problems"
Checked in SDN, but no answer.
Need your expert solution, to resolve.
With Regards,
Sekhar

Thank you Des, for immediate response.
But i have already gone through the Note.
As we are using ghe standard datasources, can you suggest which option should i use to resolve.
Solution
If the field is not manipulated in the customer exit or elsewhere, no
processing is required.
If you change the field, the following possible solutions are available:
1. You can make sure that the number of the characters does not
increase after the manipulation.
2. If you can change the extract structure of the DataSource without
affecting other scenarios (for example, if it was generated in
transaction RSO2), you can increase the length of the DEC field (or
CURR, QUAN) there to the next odd character (in the example above:
from DEC 4 on DEC 5).
3. If neither of these solutions are possible, you can use a customer
append that contains a relevant DEC field (or CURR, QUAN) with the
next highest odd length. This can be used for the result of the
calculations. This means that you do not have to manipulate the
previous field.
With Regards,
Sekhar

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

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

"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

TOC (table of contents) Formatting/Leader Tab Problems

BACKGROUND
I have found it impossible to format TOCs with leader tabs as I've seen the procedure outlined in numerous forum posts, books, and elswehere. I am an intermediate FrameMaker user running FM 9 on Windows XP Pro. I run the same setup on a home and office machine with the same problem.
I am in the process of migrating very large volumes of our company's documentation from LaTek to FM and this issue is proving to be insurmountable.I need to have complete control over this process, instead of "making do" with the default TOC.
I have spent three days studying every nuance of the issue, which usually leads me to some insight or pattern that lets me solve the problem, or at least share some clue on the forums. However, in this case, FM either doesn't work as its supposed to or it implements my changes in a seemingly arbitrary manner. So I'm not sure if this is a bug or a user error. I've also experienced the occasional crash of FM during all this work, oftentimes this is preceded by the Paragraph Designer window freezing up and refusing to change views within the window (i.e. basic, default font, etc.).
THE PROBLEM
More specifically, I've learned to manage general formatting with the building blocks on the "reference page", but the leader tabs I use for the page numbers almost never propogate, unless I use the sample TOC included with FM.
I am certain they are properly formatted, I've even copied examples directly from files that I know work (FM sample files).
When I implement the process manually, I insert the tab between the building blocks (no spaces), set a right flush tab, double click and choose tab leader option. Then I go to "body page" view, save the document, and regenerate the TOC. Usually nothing happens. Ocassionally, after regenerating several times or creating a fresh TOC, some of the changes magically propogate.
I have even tried importing the format of another TOC, which only seems to work randomly. Mostly not.
Any help is appreciated.
Thanks,
Douglas

Thanks for your quick responses, as well as your other suggestions for my project.
I am running FM 9.0p230. I tried upgrading to 9.0.3 when I began encountering this problem, but received an error message telling me I was running the wrong version of FM. If any one is familiar with this error message and can mention the fix before I delive into that problem, it is also appreciated.
I have attached the TOC. I'm not sure how/if this can be used to help me troubleshoot, so please let me know. I am new to the forums and the development side of FM.
I did "update all" on the paragraphs tags in question. If you look in the body view of this page with text symbols turned on, you can see the symbols for the second tab stops I have placed between the text and page number. That informatoin also appears in the Paragraph Designer. Both of those things add to my confusion on this matter, because that would seem to indicate I have globally applied the paragraph tags correctly, right?
If you go to the reference page, you will see my treatment of the building blocks.
Thanks again in advance for help,
Douglas

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!

Can create 52 publication, but creating 53rd leads to problems

Hello,
My apologies in advance for a long post, but I was really trying to make sure I do my due diligence before turning to the community for help, so here it goes.
I am working on a proof of concept with the purpose of using transactional replication to maintain a "reporting" copy of our databases.
The setup will include a "Publisher" server and a separate "Subscriber" server. The replication will be a "Pull" transactional replication with a distributor running on the Subscriber server. Once again: Publisher =>
pull => (Distributor + Subscriber)
We expect to have a lot of databases on each of our servers, so, in order to mimic this scenario, I restored 100 databases (about 1 GB each) on
the publisher. All of the databases are identical.
I wrote a script, which enables me to setup replication in an automated fashion (since obviously I don't want to do it manually dozens of times).
The script performs the following steps:
1. Enable replication for a database (if not enabled already):
2. Create logreader agent for a database
3. Create publication for a database (if doesn't exist)
4. Create snapshot agent for a database (don't run it yet)
5. Add articles to the publication
6. Run snapshot agent job (and wait for it to finish)
7. Create subscription database (if it doesn't exist)
8. Add subscription in the subscription database (if it doesn't exist)
9. Create distribution agent
I am able to successfully setup replication for about 52 of my databases and everything is running fine.
When I get to #53 things start to go wrong. The snapshot creation is successful, but the logreader and the distribution agents fail. Moving on to #54 everything is now completely broken. The snapshot does not get created and none of the agents
are running. I have carefully reviewed replication monitor and SQL Agent jobs looking for error messages, but didn't find anything helpful. The replication monitor simply says: "Agent Shutdown.
For more information see the SQL Server Agent job history for job ‘….correct job name here…’".
In the details it says: "The replication agent encountered a failure.
See the previous job step history message or Replication Monitor for more information".
Next I go to the SQL Agent Jobs and review the output.
In the job history the failed step says: "Message : The replication agent encountered a failure. See the previous job step history message or Replication Monitor for more information".
In turn, the previous step has no info at all.
Just the word “Message” with nothing after that. I have also reviewed the windows application log for any errors, but it simply repeats the same messages I see in the replication monitor and agent job history.
I added “–output” parameter to the agent command (in the job step properties) hoping that the output file would provide me with more information, but no output file gets created, which leads me to believe that the agents don’t even start.
I was thinking that I might have hit some hardware limit, so I checked the disk space and there is plenty of it available. I have also checked RAM and it's not even 50%
used.
Finally, what really gets me is that I am able to run all of the agents manually from the command line.
For example, I can copy paste parameters from the SQL Agent snapshot job and run snapshot.exe from the command line with these parameters – the snapshot gets created successfully.
The same goes for logreader and distribution agents.
I am completely confused here and appreciate any pointers in the right direction.
Final note (and maybe the only silver lining): The problem is fully re-producible.
I can successfully setup my 50+ subscription and then the issues will always start around subscription number 52-53.
Thank you!

Answering my own question here. The solution was given to me by Brandon Williams of http://www.sqlrepl.com. I was hitting a Windows limitation related to the use of "desktop heap". The problem is described here: http://support.microsoft.com/kb/949296
and the work-around is given here: support.microsoft.com/kb/824422.
Note that while the KB articles refers to WindowsNT and SQL Server 7.0/2000, it certainly applies to the latest versions as well. In my case I am running Windows 2008R2 Server and SQL Server 2012

Writing to DVD problem

Hi all,
I have a problem writing to my new LG DVD/CD r/w, i have solaris 10 on my x86 pc.
i can write to CDs normally with the same device on solaris, but only DVDs causing me a problem.
bash-3.00# cdrw -iv root.iso
Looking for CD devices...
Initializing device...done.
Preparing to write DVD
Writing track 1...failed.
done.
Finalizing (Can take several minutes)...done.
PLease help.

Tried cdrecord and got this :(
bash-3.00# ./cdrecord \-v speed=16 dev=0,0 /export/home/root.iso
./cdrecord: No write mode specified.
./cdrecord: Asuming -tao mode.
./cdrecord: Future versions of cdrecord may have different drive dependent defaults.
./cdrecord: Continuing in 5 seconds...
Cdrecord-Clone 2.01 (i386-pc-solaris2.10) Copyright (C) 1995-2004 J�rg Schilling
TOC Type: 1 = CD-ROM
scsidev: '0,0'
scsibus: 0 target: 0 lun: 0
Warning: Using USCSI interface.
Using libscg version 'schily-0.8'.
SCSI buffer size: 57344
atapi: 1
Device type : Removable CD-ROM
Version : 0
Response Format: 2
Capabilities :
Vendor_info : 'HL-DT-ST'
Identifikation : 'DVDRAM GSA-4167B'
Revision : 'DL12'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: 0x0011
Profile: 0x0012
Profile: 0x0011 (current)
Profile: 0x0015
Profile: 0x0016
Profile: 0x0014
Profile: 0x0013
Profile: 0x001A
Profile: 0x001B
Profile: 0x002B
Profile: 0x0010
Profile: 0x0009
Profile: 0x000A
Profile: 0x0008
Profile: 0x0002
./cdrecord: Found DVD media but DVD-R/DVD-RW support code is missing.
./cdrecord: If you need DVD-R/DVD-RW support, ask the Author for cdrecord-ProDVD.
./cdrecord: Free test versions and free keys for personal use are at ftp://ftp.berlios.de/pub/cdrecord/ProDVD/
./cdrecord: This version of cdrecord does not include DVD-R/DVD-RW support code.
./cdrecord: If you need DVD-R/DVD-RW support, ask the Author for cdrecord-ProDVD.
./cdrecord: Free test versions and free keys for personal use are at ftp://ftp.berlios.de/pub/cdrecord/ProDVD/
Using generic SCSI-3/mmc CD/DVD driver (checks media) (mmc_cd_dvd).
Driver flags : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
Drive buf size : 1114112 = 1088 KB
Drive DMA Speed: 3227 kB/s 18x CD 2x DVD
FIFO size : 4194304 = 4096 KB
Track 01: data 2971 MB
Total size: 3412 MB (338:05.24) = 1521393 sectors
Lout start: 3412 MB (338:07/18) = 1521393 sectors
Current Secsize: 2048
./cdrecord: Unspecified command not implemented for this drive.
./cdrecord: Data will not fit on any disk.
./cdrecord: Cannot write more than remaining DVD capacity.
bash-3.00#
I will try to search for cdrecord-ProDVD

"writing lead-in" problem

Similar Messages

Maybe you are looking for