Jump to content

rcubed

Members
  • Posts

    33
  • Joined

  • Last visited

Everything posted by rcubed

  1. UK, I have two possible suggestions for ImgBurn 1) Is it possible to add the Book Type data to the log file when the verify is being done? It's possible to check using DVDInfoPro, but it might be convenient to have it in the log. My Plextor 716SA allows setting Book Type DVD-ROM for both +R and +R DL's 2) It is reasonable and possible to add the verify speed to the graph data? Perfect record with Verbatim DLs(@6x) and TY +Rs (8X)with ImgBurn to date no coasters. Thanks,
  2. UK, Was the %V option implemented in the 1.1.0.0 version or is it pending for the next release? Thanks again for a great piece of software! Cuber Thanks, I look forward to the next release
  3. UK, Was the %V option implemented in the 1.1.0.0 version or is it pending for the next release? Thanks again for a great piece of software! Cuber
  4. Shamus, Thanks, I suspected that would be the case.
  5. LUK, Is there a benefit to having the cycle tray before verify option selected as the default? Does this remove cached items from the OS and guarantee the data is verfified against the DVD data? What is the risk of deselecting it? LUK thanks again for a great program. I have yet to burn a coaster with ImgBurn especially DL DVDs. I rarely use Nero anymore. :P Rcubed
  6. No takers on the question? I just burned another two disks one at 4x and one at 6x and no spike in the jitter plot at the layer switch. After much appreciated advice from UK and others I switched to letting PgcEdit pass the layer break information using the "Calculate Optimal" option in ImgBurn. I looked back at the previous logs when I had been copying the info into the layer break using user specified. I noted the PgcEdit log indicated the absolute layer break as "Layer break is at absolute sector 2039968. (Offset in L0 is 1.)" I used a value of 2039968 when I think the value entered should have been 2039968-1 or 2039967. Would that have led to the spike in the jitter at the layer break? Moral of story let PgcEdit and ImgBurn do it automatically. Thanks for any insight. Again thanks to UK and rOIZ for some terrific software! rcubed
  7. Ipew, On my Sony standalone there is a menu option that allows an on screen display of the dynamic bit rate and the layer that is currently playing. It's a picture of the disk with a pointer and number indicating the layer and position (approximately) where the player is playing. I just pop the disk in, select that option and by using the scene selection zero in on the layer break. Don't know how may other player have that option. r*3
  8. Hi, Since this my 1st post, first let me say thanks to Lightning and rOIz fo their two programs (donations forthcoming). After reading several forums on the topic of layer breaks I decided to "go with the pros" and use PgcEdit to build an ISO image and decide the layer break point and ImgBurn to generate the final DVD. Works like a champ no coasters yet. Also I beg forgiveness if this is off topic. It's really good to see Lightning has found a project to focus his considerable talents on following the demise of DVDD. #39;( I was heart broken when he was forced to stop work on the project. I especially enjoyed the DVDD form topics and the exchanges of humor. My question concerns this. I have only done 3 burns of DL disks. I am using the Verbatim +R DL disks that supposedly can be burned from 2.4x to 6x. I am burning using a Plextor 716SA and checking the burns with Plextools XL. My system is an Asus A7N8X Deluxe mobo with 1G ram, an Athlon 2800+ and am running Win XP Pro (latest change levels). The first burn I did at 2.4x and for that burn the jitter shows a step to a slightly higher level at the DL switch point. For the next two burns I did them at 6x and on those scans there is a single spike to the top of the Jitter graph at the DL switch point followed by a drop back to what I would consider the normal jitter level (i.e. similar to the 2.4x burn). In all other respects the PI levels and TA checks on the burns indicate they are very good if not excellent. Is there an explanation for this? Is it normal or abnormal. Is it going to cause any problems? All three disks play ok on my PC and with my Sony standalone DVD player and my daughter's player. I would be willing to post jpgs of the beta/jitter plots. However I don't appear to be priviledged to do attachements. Any enlightenment would be appreciated. I suspect it may be an artifact of the burner and chosen speed, but don't understand why it only seems to occur at the 6x burn level (sample of 1@2.4x 2@6x). I haven't had the opportunity to try one at 4x yet. And yes I've had my share of problems getting the 716SA to work with my mobo. However that is another whole story. Things seem to have normalized. Thanks in advance R.R.Richardson (rcubed) BTW One other quick question. In ImgBurn should the Calculate Optimal option be used when burning using ImgBurn from inside PgcEdit or is it better to note the break point selected by PgcEdit and enter using the User Specified option? Some guides imply the one generated by PgcEdit will be used, but it didn't seem to be completely clear to me. Does this still hold true if the burn is done at a later date using ImgBurn in stand alone mode? I've also been using the 32K separation option in PgcEdit.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.