Jump to content

All Activity

This stream auto-updates

  1. Yesterday
  2. Help me please I'm desperate looking for M-Disc DVD 4.7GB spindle of 10 or 15 units to buy but I can't find it at a good price for Brazil, here I don't sell it but on amazon, ebay, newegg the freight and rates are too high someone can you help me?
  3. Last week
  4. I would think to contact the M-Disc Verbatim DVD manufacturer but I don't know the actual manufacturer of this disc in 2016 i have stored two asus internal sata dvd drives model DRW-24F1MT/BLK/B/AS and i wanted to keep them for future use
  5. Before I was told about the evils of CMC, I spent about $2,000 in discs, new burners, and new DVD video recorders trying to figure out why my discs that had worked fine for so long stopped working. The answer was Optodisc switched to CMC and I never used an Optodisc product again. And now, Optodisc is out of the optical disc business; good riddance! I've only burned a few M-Discs so I don't know from experience. Plus, my M-Disc are nowhere near as old as they need to be to prove any of the claims the manufacturer makes. However, the theory behind M-Discs versus organic dye is that M-Disc is basically akin to a process of chipping pits in stone versus burning ink. So, theoretically, M-Disc should be able to back up its claims. And as long as they make hardware that supports DVD+R reading, M-Disc will never go obsolete.
  6. thank you for the explanation I had CMC discs in 2013 but today I have M-Disc DVD Verbatim and I burned files on it in your opinion M-Disc has more resistance than other discs in glue and polycarbonate?
  7. I've been burning optical discs since 2000, the early days of CD-R. I've never cared a jot about PIE, PIF, and jitter values. As long as they pass Verify/Read tests, that's good enough for me. And if they're DVD Video discs, a play of all contents on a standalone DVD player. The PIE/PIF/jitter values probably don't really come into play in terms of how long a disc will last before it's not readable. A disc will simply become unreadable based on the quality of its dye/metallic oxide. And it's an all or nothing situation, usually. Cheap media will become completely unreadable after like a year or so. Some media will have just a few sectors become unreadable, but if you're not using CMC discs, you generally don't have to worry about discs dying unless your burner doesn't like the dye on that particular disc. Which you'll generally know if it doesn't the minute Write or Verify fails for a particular brand.
  8. Will it survive even without me knowing the PIE, PIF and jitter values after burning the M-Disc DVD?
  9. M-Disc will, most likely, long outlive the user.
  10. i thought M-Disc DVD was marketing for a living decades the truth is i just ran the read test but i know that PIF, PIE and jitter secretly increase
  11. As they’re meant to last for hundreds of years, I doubt it makes much difference to you if you used a simple ‘read’ operation to check the disc or if you look at pif type levels. If it passes a read operation now, it’ll still do so in 50 years time. That said, if you have the ability to scan for such info, why risk the long term archiving of important data on a disc that is of immediately questionable readability?
  12. i store files on mdisc dvd for a few years but the only test i ran was read test 100% good but i don't know if it's recommended to do these pie, pif and jitter tests before storing m-discs for the long term?
  13. Yes, I believe every single burn has some amount of PIE/PIF/jitter. If it's low, it can generally be ignored. If it's high, then you start to worry.
  14. Of course, nothing is perfect. Like I said, the ‘amount’ of errors depends on your drive and how well it can burn them. Some will be better at burning them than others. Btw, if you just ask the same question over and over again, I’ll simply ban this new account you’ve made too.
  15. M-Disc DVD Verbatim have PIE, PIF and jitter errors after burning?
  16. That would depend on how well your drive can burn them. I doubt usage has any effect on the speed at which a disc deteriorates. Plus, if you're talking about M-Disc, they're designed to last for ages.
  17. M-Disc DVD produces many PIE, PIF, jitter errors after burning files? on DVD M-Disc discs stored for long periods without use do PIE, PIF, jitter errors increase more compared to moderately used discs?
  18. You haven’t included/enabled cd-text info when creating the cue.
  19. I am trying to create a music cd from a group of mp3 files in directory I:\FILES\MUSIC\FAVORITES I have created a CUE file that looks good. I have tried both methods described in the guides section with the same results. When I play the cd the names displayed are Track1, Track2, etc. I have gotten this to work properly before but do not know what has changed. Any suggestions would be appreciated.MUSICCD.cue ImgBurn.log
  20. I know I’m treading into territory that has been brought up on this forum by various requesters multiple times in the past. But I still want to bring it up, if anything for an insight into the current and future of burning media on disc (I may have limited knowledge). Lightning UK has said that the BD-R and/or UDF 2.50 standard specifies that there is no logical layer break. While this might be true for data discs, BDMV puts a lot of effort into seamless streaming, PTS layer breaks are those that happen within one stream at a chapter for instance or an arbitrary presentation time. I have tried to find information on what an image such as ISO consists of, if the UDF filesystem is intricate enough to say which order files should be in, their start and end sectors, or if burning an image results in a file structure of alphabetical order. This has the risk that on DL and TL discs index.bdmv, the first file supposed to be accessed, is on L1 or L2. Is all this really up to the hardware? Can a virtual UDF filesystem be more specific? Can I manually edit a UDF filesystem, to change the blocks and sectors? I only found the single tool, udftools, on Github and it’s for creating new filesystems. Here is an example of a CMF FAI file. It’s an XML that very concretely outlines the BDMV disc layout, with start sectors and file sizes. If only I could find a way to make use of this when creating an image or burning to disc. <?xml version="1.0" encoding="UTF-8"?> <CMFFilesInfo xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="FAIschema.xsd"> <FileAddressInfo> <FileAddress Path="/BDMV/index.bdmv" Size="264" Access="EXTENT"> <Extent Start="4320" Size="264" /> </FileAddress> <FileAddress Path="/BDMV/MovieObject.bdmv" Size="470" Access="EXTENT"> <Extent Start="4321" Size="470" /> </FileAddress> <FileAddress Path="/BDMV/PLAYLIST/00001.mpls" Size="790" Access="EXTENT"> <Extent Start="4323" Size="790" /> </FileAddress> <FileAddress Path="/BDMV/CLIPINF/00001.clpi" Size="11640" Access="EXTENT"> <Extent Start="4344" Size="11640" /> </FileAddress> <FileAddress Path="/BDMV/STREAM/00001.m2ts" Size="10275858432" Access="EXTENT"> <Extent Start="275232" Size="1073676288" /> <Extent Start="799488" Size="1073676288" /> <Extent Start="1323744" Size="1073676288" /> <Extent Start="1848000" Size="1073676288" /> <Extent Start="2372256" Size="1073676288" /> <Extent Start="2896512" Size="1073676288" /> <Extent Start="3420768" Size="1073676288" /> <Extent Start="3945024" Size="1073676288" /> <Extent Start="4469280" Size="1073676288" /> <Extent Start="4993536" Size="612771840" /> </FileAddress> <FileAddress Path="/BDMV/BACKUP/PLAYLIST/00001.mpls" Size="214" Access="EXTENT"> <Extent Start="16127906" Size="214" /> </FileAddress> ........ </FileAddressInfo> </CMFFilesInfo> After searching a week for any solution to layout my disc when burning, I gave up and fed Imgburn the image in hope for the best. As expected, no layer breaks were honored and what’s worse, break L0 had bad sectors and the video is corrupted for 12 frames or so. L1 break was fine though. The only hack I can think of, besides if the possibility to edit the UDF FS exists, is to insert useless blank clips around the layer breaks. And if PTS breaks are needed, chop the stream into several parts while inserting these fillers. I appreciate if anyone has an opinion on this problem, and I hope that someone agrees that it’s not an issue without merit.
  21. What were the CD images of? Audio CD's or data discs like some kind of software installers or game discs? If they're Audio CD's or game discs, you probably won't have much luck copying their contents. You can't do it without special ripping software for Audio CD's. And some game CD's require the actual disc to run. And if they're some like Playstation or other console hardware discs, you'd need the images themselves as copying the contents won't necessarily copy all the contents. (Long story.) If they're just plain old data CD's, you can copy the contents to another location and put all the copied contents to an ISO in Build mode. If you have the space on a DVD, copy the CD ISO's to the image, too, as archive copies. If they're not just plain data CD's, you can do like LUK said and archive the ISO's. Then, you can use some kind of virtual drive software to load each CD ISO as a virtual drive for accessing. Even if they are plain old data CD's, you can still archive them to one disc and mount each CD as a virtual drive each time you want to access the files on the discs. You said the CD's are ISO's, which indicates they probably aren't Audio CD's or console game discs.
  22. You can't. You'd need to extract the contents from each one, merge them (contents of each ISO into its own folder or something) and then burn the entire thing. If you just want to archive the ISO's on 1 disc (as in, back them up), use build mode.
  23. I am dealing with "old stuff" here. I have multiple small iso's that were originally supposed to be burned to cd's, 630Mb. I want to burn them to a single DVD, could someone point me in the right direction please. All help appreciated.
  24. It seems there is a newer firmware released for you drive https://www.firmwarehq.com/Samsung/SH-S223C/files.html Try update the drive with the SB07 (now it's on SB04), it may help or not. Remove the disc from the drive when flashing it.
  25. That's probably a drive or disc issue. Try another drive. Preferably, get a USB one you can easily hook up and disconnect afterwards. TSSTCorp drives have been known to be problematic sometimes. Or the drive may simply be at a point where it's getting old. If a different drive can't read the disc, the issue is most likely the disc has gone bad. The PS2 is almost 21 years old since initial release, so it wouldn't surprise me if a disc has become unreadable, particularly if it was well played.
  26. Earlier
  27. I tried the method, and it very very slowly came up with this. I 20:26:21 Operation Started! I 20:26:21 Source Device: [0:0:0] TSSTcorp CDDVDW SH-S223C SB04 (D:) (SATA) I 20:26:21 Source Media Type: DVD-ROM (Book Type: DVD-ROM) I 20:26:21 Source Media Supported Read Speeds: 6x I 20:26:21 Source Media Sectors: 2,089,296 (Track Path: PTP) I 20:26:21 Source Media Size: 4,278,878,208 bytes I 20:26:21 Source Media File System(s): None I 20:26:21 Read Speed (Data/Audio): MAX / MAX I 20:26:21 Destination File: F:\Desktop Files\Project Overlord\Legal RIps\Socom US Navy Seals.iso I 20:26:21 Destination Free Space: 450,203,250,688 Bytes (439,651,612.00 KiB) (429,347.28 MiB) (419.28 GiB) I 20:26:21 Destination File System: NTFS I 20:26:21 File Splitting: Auto I 20:26:22 Read Speed - Effective: 2.4x - 6x I 20:31:56 Reading Session 1 of 1... (1 Track, LBA: 0 - 2089295) I 20:31:57 Reading Track 1 of 1... (MODE1/2048, LBA: 0 - 2089295) W 20:33:35 Failed to Read Sectors 0 - 31 - Reason: No Seek Complete W 20:34:10 Failed to Read Sector 0 - Reason: Unrecovered Read Error W 20:36:00 Retrying (1 of 20)... W 20:36:12 Retry Failed - Reason: No Seek Complete W 20:36:12 Retrying (2 of 20)... W 20:36:18 Retry Failed - Reason: No Seek Complete W 20:36:18 Retrying (3 of 20)... W 20:36:24 Retry Failed - Reason: No Seek Complete W 20:36:24 Retrying (4 of 20)... W 20:36:29 Retry Failed - Reason: No Seek Complete W 20:36:29 Retrying (5 of 20)... W 20:36:35 Retry Failed - Reason: No Seek Complete W 20:36:35 Retrying (6 of 20)... W 20:36:40 Retry Failed - Reason: No Seek Complete W 20:36:40 Retrying (7 of 20)... W 20:36:46 Retry Failed - Reason: No Seek Complete W 20:36:46 Retrying (8 of 20)... W 20:36:52 Retry Failed - Reason: No Seek Complete W 20:36:52 Retrying (9 of 20)... W 20:36:57 Retry Failed - Reason: No Seek Complete W 20:36:57 Retrying (10 of 20)... W 20:37:03 Retry Failed - Reason: No Seek Complete W 20:37:03 Retrying (11 of 20)... W 20:37:08 Retry Failed - Reason: No Seek Complete W 20:37:08 Retrying (12 of 20)... W 20:37:14 Retry Failed - Reason: No Seek Complete W 20:37:14 Retrying (13 of 20)... W 20:37:19 Retry Failed - Reason: No Seek Complete W 20:37:42 Retrying (14 of 20)... W 20:38:53 Retry Failed - Reason: No Seek Complete W 20:38:59 Retrying (15 of 20)... W 20:39:04 Retry Failed - Reason: No Seek Complete W 20:39:04 Retrying (16 of 20)... W 20:39:10 Retry Failed - Reason: No Seek Complete W 20:39:10 Retrying (17 of 20)... W 20:39:16 Retry Failed - Reason: No Seek Complete W 20:39:16 Retrying (18 of 20)... W 20:39:22 Retry Failed - Reason: No Seek Complete W 20:39:22 Retrying (19 of 20)... W 20:39:27 Retry Failed - Reason: No Seek Complete W 20:39:27 Retrying (20 of 20)... W 20:39:32 Retry Failed - Reason: No Seek Complete W 20:45:15 Retrying (21)... W 20:45:21 Retry Failed - Reason: No Seek Complete W 20:45:24 Failed to Read Sector 0 - Reason: No Seek Complete W 20:45:29 Failed to Read Sector 1 - Reason: No Seek Complete
  28. Load the program without a disc in the drive. Go into Read mode Put the disc in the drive and keep an eye on the status bar of the main window. If the drive goes through the motions of trying to initialise the disc and then just ends up saying medium not present, it means your drive can't read the disc (at all). This is not an ImgBurn issue. Another drive may have more luck reading the disc.
  1. Load more activity
  • Create New...

Important Information

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