fordman
-
Posts
184 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by fordman
-
-
Nope. Australian money.
In US currency they are $4.40 each. Sucks huh?Yes, I wonder if it's a value added tax that Australia adds while the U.S. adds none, or perhaps there's just a greater market in the U.S. leading to a greater supply? I seem to recall Canadians complaining about the price of media in Canada because of the VAT, and wanting to come to the U.S. to get it instead. It's hard to find the ones in jewel cases any more in the U.S., and I mainly see spindles of 10 or 20. The 20 piece spindles are the ones that are $39.99 US about once a month.
At $2 US each, I stocked up and then gave up on DVD Shrink or like programs long ago...
-
$6 each in my money which is (checks currency market) UK?2.40 per disk.
Are those $US? If so, you can get them for $3 each in a spindle at Best Buy normal price, or $2 for the sales they have often.
-
I can't imagine sonic/prassi providing me with the specs for how to use it....so it's highly unlikely this will ever happen. Feel free to contact them on my behalf though!
Lots of apps use the burning sdk from sonic/prassi, that's why it seems widespread.
It's quite possible a version even comes built into windows.
Ahhh, OK. It sounds like one might need to purchase the SDK to be able to interface with it then.
Well, if other's haven't requested it, I certainly wouldn't make it a priority for ImgBurn!
I'll look for a workaround.
Thanks,
Ford Man
P.S. Version 1.3.0.0 seems to be firing on all cylinders for me!
-
I have "user only" access to computers that only have the Sonic (formerly Prassi) PX engine I/O installed, and in user mode access to Microsoft's SPTI is blocked, so no new programs, like ImgBurn, can use it. This was not an issue with Windows 2000, but apparently is with Windows XP.
I realize that there are other options, like ElbyCDIO and Patin-Couffin support, but like regular ASPI support, I don't have access to those either. Would it be difficult to add support for the PX engine? This seems like a very widespread interface....
Regards,
Ford Man
-
Err! It is not sufficient to overwrite the files in the ISO, because the files must be moved, by inserting some gaps between them. This is how the layer break cell is properly anigned with the start of an ECC bloc. Moving the files requires a full rebuild of the ISO image.
Anyway, even overwriting the files at the same position is not a piece of cake.
Sorry, r0lZ! I did not mean to minimize the effort this might take. I use your PGCEdit tool and love it. I think my analogy to what RecordNow Deluxe was a poor one, given that it modifies VIDEO_TS file collections on the fly, and not ISO images.
Now that I see your reponse, I see that it might be more than difficult - I agree that it is impracticle if not impossible!
The only reason that I was suggesting such a feature might be nice was for those images that require reauthoring, but I do not have the empty space to receive the extracted files. One other advantage would possibly be the ability to keep the file dates and times the same as in the original image. That was one of the best features of DVDD - the image looked the same, even the volume serial number!
In that vein - would it be possible to add a method in PGCEdit to stamp all files with a specific time and date when creating an ISO (or recording directly withing PGCEdit)? Programs like Nero or RecordNow provide a method to either keep original dates and times, or change them to a specific (or current) date and time. Currently I go through a rather convoluted methodology of launching PowerDesk (which supports changing file dates/times) right before selecting my layer break position, change all the file dates/times to the desired figures and then change my system clock to the same date and time (this ensures that even the . and .. directory entries as viewed from a command prompt match).
For single layers the method is easier. I use PGCEdit to fix up the files, then use PowerDesk to change the file dates and times (even the AUDIO_TS and VIDEO_TS directories themselves) and then make the ISO with ImgTool Classic. It manages to maintain the file dates and times even without changing my system clock.
Thanks,
FordMan
-
Good point, I forgot about that
Ok so you'll need to extract them.
Thanks for the confirmation, though I was hoping it was possible!
I imagine PGCEdit could likely be modified to compute the needed changes, write just the modified files to a temporary directory, and then insert those changed files into the image as it is being built... I think this is sort of how RecordNow Deluxe does it for recording on the fly while setting the layer break - it doesn't touch the source files.
-
You'll need to either extract the files from that MDS/ISO combo and rebuild it using PgcEdit, or do the same via mounting it within DAEMON Tools.
I saw this recommendation to mount the image via Daemon Tools before and tried it. It didn't work because PGCEdit needs to modify the source files (IFO/BUP anyway), and it cannot do that with a virtual DVD-ROM because it is read-only.
Am I missing something? Is there perhaps a way to have PGCEdit copy the needed modifications to the hard drive, and then make on-the-fly substitutions into the rebuilt image?
-
HEY,,THANKS ILL SEND SOME MAPLE SYRUP YOUR WAY TO,,EH,, CHEERS
P.S. i have changed to dvd rom from my LG recorder,what about my sony,,dosnt have a setting for that,,how can i change or make sure it burns as a bookrom,,cheersIt depends on what type of Sony you have. Check out this site:
If your Sony DVD Recorder is actually a re-badged LiteOn drive (Sony doesn't make any of their own recorders anymore), then you can flash it to the native LiteOn using the utilities you find at this web page, and the LiteOn drives allow book type setting! You can even keep the Sony drive ID while allowing book type setting. I belive if you do this, the omnipatcher utility autosets all media types to DVD-ROM, including DVD+R and DVD+RW. That's what it did on my girlfriends Sony drive. The drive (Equivalent to the LiteOn SOHW-832S) had the ability at first, then Sony disabled that ability in later firmware versions! Their official reason is that they didn't want to support this since it was not part of the DVD+R spec, but its more likely they didn't want to make it easy to copy DVDs, especially their DVDs, that would be playable in most any player....
I believe some of the later Sony drives are actually Benq drives, but these too allow book type setting, so if you can find a way to flash to that, you can use the Benq utilities to set the book type.
-
F6 is a hidden gem and no, it can't be enabled all the time. That's by design more than anything. These things are useful for debugging stuff and seeing what's going on without making the log all messy to 99% of the users.
I did email you earlier (to the email registered on this board) - incase you don't check it all that often
Yes, I enabled it for a routine burn of an .ISO/.MDS and there didn't seem to be much other than without debug on, so I expect that the detail is mainly seen when errors occur. I think I did notice that with debug on, the log showed exactly which VOB the layer break would occur during.
Yes, my e-mail server stuck your e-mail in my junk e-mail folder even though you had my address in the TO line! I've added you to the safe list, so that shouldn't happen again. I reponded affirmatively, by the way.
Thanks for everything,
Ford Man
-
Bugger!
Ok, it SHOULD have removed it and I just went to check my code so I could then explain when it wouldn't remove it.
Seems I did a bit of a copy + paste error and was comparing a value to the wrong value of something else. I've have now corrected this.
btw, if you enable program debug mode (F6), you can see more about what's going in. When that 'Potential Layer Break' (just via the 'Display IFO Layer break' option) window comes up, if you actually select an item, it will perform a logical update of the ifo - i.e. it won't actually write it back to the file but it'll show you what it would have changed if it had.
Try it, I'm sure you'll see what I mean
Great! I already got rid if the ISO, but I'll try your debug exercise on the next of this type I encounter. That could be awhile, as this was the first time I found this. Other PTP images have either had no valid break points and needed to be reauthored, or have had one at a cell that could directly correspond to a valid OTP one. This "behind the scenes" info looks like it would be great - is there a way to enable it all the time? I found the debug mode for I/O, but that's apparently not the same as the program I/O.
I decided to not re-author with PgcEdit as the old invalid flag at cell 33 occurred right at a "fade to black" scene change, so the momentary pause wouldn't be noticeable anyway.
Thanks for looking into it and not just assuming that I was doing something wrong. Your willingness to respond quickly and check your own code is very satisfying to the end user!
-
My opinion is that he shouldn't do that with any important data. If it's something important enough to archive you should do it on media you can trust.Here's a better idea - use them for backup up huge amounts of data from your hard drive. You can do this with any recording program (RecordNow, Nero, etc.) and burn in file mode as a data DVD! Computer drives don't seem to have a problem with layer switching when handling data files, at least for me. That's what I did with some Ritek Ridata discs...
More than a year ago when I got into dual layer burning, Verbatims were so expensive that I bought some Ritek RiData DVD+R DL discs. I encontered the same problems (Layer break hangs, pixelation) as grampaw when playing the DVD-VIDEO burns in my standalone DVD players, but there was never a problem when playing back on my PC drives. So, I started using them just for data, mainly large data files (MPG or AVI video captures) that wouldn't otherwise fit on a single layer disc.
Over a year later, they still verify fine and compare to the .sfv CRC files that I put on the discs (and copied to my HD).
My conclusion: Ritek DL discs have a problem with layer break transition on standalone DVD players, but are otherwise fine for PC drives....
-
Hi Here, Welcome to the forum. NO, NOT EVER. Imgburn will remain a image write program only. It will never be able to read just write. In saying this though, it is the best write program out there ............
I would agree it is the best writing program out there. If it won't ever support ISO creation. Could you recomend a good program that will, even if I need to use it in combination with AnyDVD, etc?
Thanks!!!
You could try IsoBuster. I'm not sure whether the freeware version supports extracting entire images (the Pro one does), but you can check it out at http://www.isobuster.com
-
OK, I burned it as is. ImgBurn 1.2.0.0 seccessfully inserted a flag at cell 29, but did not remove the original one that was at cell 33.
This was a simple one where there was only one flag in the whole VTS, so I figured if ImgBurn could do it, it would be successful on this. However, I'll reauthor with PGCEdit from now on to be sure.
Suggestion: if the ISO could be prepared by ImgBurn first, with the option of not continuing the burn after it is altered, one could mount it and examine the changes made before burning. This would be especially helpful since DVD+R DL media does not support test mode.
-
Yeah it'll try to.
Do remember there is no real flag for a layerbreak and the one we take to mean the layerbreak could actually mean other things.
As such, proceed with caution and keep an eye on the 'SPLIP' (or something like that!) column in the 'Potential Layer Break' window.
Thanks,
Yes, I realize it's really a non-seamless playback flag. I have one that has it in the main VTS of the image, and it was meant as the pause for the true layer switch, as it's the only one shown in the almost 2 hour VTS. Unfortunately it does not match the requirements for the OTP layer break (sector/16 calculation), and ImgBurn finds that a cell approximately 4 cells earlier DOES match the requirements. Further analysis shows that this was a PTP image, so I assume that is the cause of the difference. Anyway, I'd prefer to just burn the ISO (and toss the .MDS) instead of reauthoring to ensure I don't get two non-seamless flags. It sounds like ImgBurn will do the job! ImgBurn has already succesfully burned a few PTP images to OTP DVD+R DL media, but the original flags did meet the OTP requirements, so there was no worry.
-
ImgBurn analyzes and presents options for insertion of a layer break flag into ISO images that don't already have a flag. However, will it delete incorrect flags when it inserts a correct one?
For example, if there is a layer break flag that was OK for a PTP image in the main VTS within the ISO, and ImgBurn finds a valid cell for a layer break flag conforming to the OTP requirements, will it delete the original PTP flag when it inserts the one for the OTP burn?
Or, if I want to make sure the original one is deleted, should I re-author the DVD with PGCEdit, even if ImgBurn finds a valid LB point for OTP?
-
I've read enough stuff in this forum to convince me that Ritek DL +R media are potential coasters. I've burned maybe 3 DVDs out of my spindle of 20, all I suppose classified as "successful", however with funky stuff going on at the layer break (stutter, stopping, pixellation).
I switched to Verbatim DL +R media a while ago, and they seem to work perfectly. So now I have this spindle of blank Riteks I don't know what to do with.
So, it just occurred to me, why not burn them as DVD-5's, i.e. only use layer 0. Anybody have any experience at this? Should I do anything special using ImgBurn? Hate to just dump this spindle...
Here's a better idea - use them for backing up huge amounts of data from your hard drive. You can do this with any recording program (RecordNow, Nero, etc.) and burn in file mode as a data DVD! Computer drives don't seem to have a problem with layer switching when handling data files, at least for me. That's what I did with some Ritek Ridata discs...
-
I will test the latest beta tonight - I have to say that some of the posts here look f'in ungrateful to me
! LUK! works his socks off for this program and includes whatever features he can when asked to - as polo pointed out you don't get that kind of service for programs you buy !!!!Come on guys - chill out and show some patience.....
I hope we can all just turn down the emotion a notch here. I agree that LUK deserves nothing but praise for his programming. I think you are witnessing that some have developed a "dependency" on his ImgBurn program, and when it's not working on their machine because of a programming change, they panic.
I, for one, was not affected by this issue and am happily using 1.2.0.0 and it is working as desired. I think the frustrations of some users stem from that fact that they are having issues and LUK raised expectations that a 1.2.1.0 version would be released approximately two weeks ago after this particular fix went through one more night of testing. However, since then, it appears that the lack of sufficient beta testers (an argument offered by one beta tester) and/or LUK's desire to pack more features in before releasing the next version has led to a more noticeable delay. Sometimes packing too many changes into a release can cause original features to break, as was witnessed with this problem...
Like I said, I am not affected, though I admit I avoided it at first because the problem sounded pretty bad. I also don't use the queue feature, so I don't know if I would have an issue with that...
I appreciate the fact that LUK is a perfectionist who wants to improve things as much as possible!
-
I'm using a system restore program called RestoreIT which created a 1.5MB .ima file (to be buned to CD for emergency recovery use). However it appears that this format is unsupported; is that correct?
Any advice would be appreciated.
#39;(You need a program called WinImage to write this to a floppy for booting....
-
My NEC 4550a drive has the latest NEC 1.07 firmware installed, however there is another firmware available from outside NEC.
What would the advantages be to use the alternative?
Thanks
If you are referring to Liggy and Dee's firmware, you can get RPC1 (region free) functionality, bitsetting for DVD+R and DVD+RW in addition to the included support for DVD+R DL discs. Also, they have modified some write strategies to improve burn quality.
-
a dvd+r can only get up to 4.47gb i think.
That is the problem, it tells you the file is to big.
Many thanks, will try to use shrink instead
As killjoy and I noted, it has nothing to do with your use of CloneDVD2. It has to do with the target value for the shrunken disc. I do recall that some movies (when I was still compressing them - use DL discs now) with DVD shrink would not get under 4.37 GB on the first try, and you had to shrink the output a second time. If you didn't change the default target size in CloneDVD2, perhaps that is what is happening to you.
-
a dvd+r can only get up to 4.47gb i think.
That is the problem, it tells you the file is to big.
thought it was 4.7gb?
#39;(No, the problem is the misconception caused by the difference of whether you consider 1 GB to be be 1073741824 bytes (1024 x 1024 x 1024) as is used for RAM, or if it is 1000000000 bytes (1000 x 1000 x 1000) as is used for hard drives and other storage media such as DVDs.
The 4.7 GB that you are referring to is actually 4700 MB or 4700000 KB or 4700000000 bytes in storage media terms.
However windows treats all space (RAM or physical media) from the 1024 bytes per KB perspective, so when you float your mouse over a file that is truly 4700000000 bytes, you'll see that windows reports just less than 4.38 GB (4700000000 divided by 1024 three times).
So, you are truly oversized for the DVD media. Since the default for CloneDVD2 always worked for me, I assume you changed it to a custom figure? You'll have to go back to the default and clone again...
-
When burning an dual layer ISO that does not have any layer break flags already present (the type that 1.2.1.0 will fix the LB insertion), how does ImgBurn insert LB flags for PGCs with re-used cells?
For an explanation of what I'm talking about, see Blutach's dual layer tutorial for burning or creating an ISO with PGCedit here:
http://www.videohelp.com/~r0lZ/pgcedit/thi...ith_pgcedit.htm
Toward the bottom there is a section titled: "A note on DVD?s with re-used cells"
I ran into this situation with a collection of VIDEO_TS files. I decided ot write it with Sonic RecordNow Deluxe 7.3 and found that it did NOT follow the methodology described in the tutorial - this is the first failure that I've had with RecordNow Deluxe 7.3.
Bascially I had a PGC for which some cells (VOB/Cell ID the same) were shared in 2 other PGCs. Basically the other PGCs were highlights of the main PGC.
So, when I burned with RecordNow Deluxe - I looked at the burned disc and was shocked to find that there was no layer break flag inserted into the main PGC1 which was appxomitaly 3 hours long! The other PGC5 and PGC6 already had the flag set because of the discontinuity of jumping around the main title for highlights, and and the cell that was shared with PGC1 already had a flag set in PGC5 and PGC6.
I didn't think this seemed right, so I created (my first) dual layer ISO with PGCEdit/mkisofs and it offered 3 possible selections of the layer break, all the same cell and exact physical LBA, but in each PGC1, PGC5 and PGC6. PECEdit suggested that the cell in PGC5 was the optimal selection as it corresponded to cell 1 of the PGC (as in Blutach's example).
I created the ISO and burned it, and as Blutach states, the flag was repeated in PGC1, as one should expect! So, PGCEdit (with ImgBurn logic for LB selection?) ensures that every PGC that uses the first cell on the second layer has the LB flag inserted into it - Great!
However, RecordNow Deluxe 7.3 failed to do this - and apparently also decided that the PGC5 location was the best, and doesn't bother to look for instances of shared/re-used cells in other PGCs. Clearly this seems to be a bug in RecordNow Deluxe.
Now, if I had the same files compiled into an ISO with no LB flags in PGC1, will ImgBurn correctly insert the flag into PGC1? I ask because copied the RecordNow burned DVD to an ISO and looked for the LB location with the ImgBurn tool to find the best layer break and it presented the same the same 3 choices as PGCEdit did, though I didn't bother to burn it a second time to see if it would have inserted a LB flag into PCG1 since all 3 choices were really pointing to the same cell, but in other PGCs.
I'm curious whether ImgBurn would follow the same logic as Blutach's tutorial shows for re-used cells...?
fordman
-
Use the queue function with some images loaded...
Oh, so this only happens if you are burning images from the queue? I admit I don't do that - I only burn an image to one disc at a time, and don't find myself burning several different images consecutively in a short period.
However, if the source of the issues is the size of the data "chunks" being read from the hard disk, I don't see how using the queue would be any different than burning a single image...
However, I'll give it a try. Do I need to load several images, or will just one image in the queue be enough to test this?
-
For me, the 'Available' counter in the 'Physical Memory (K)' box on the 'Performance' tab showed a drop in value every second that matched the write speed of my burner.
Once I'd noticed this pattern I didn't bother to keep an eye on it right until the end. What I did see was that it took me down from about 1.2gb free to 400mb. I may have gone beyond that, I don't know.
Switched back to 64k transfers and it wasn't even noticable after that.
As it's not actually ImgBurn using the memory, memory for the ImgBurn.exe process stayed at 30 odd MB as normal.
Strange, I didn't seem to see ANY decrease during burning in the performance tab, and definitely not by that much even when the burn started! Hmmm, perhaps it depends on the version of Windows (I'm using XP Home SP2 with all critical updates), and possible differences in memory management?
Maybe so, I am wondering what amount of RAM you have?
I have 1.5 GB of RAM currently on a Medion (MSI motherboard) computer with a non-hyperthreading 2.66 Ghz P4.
Date Stamp support for ImgBurn V2?
in ImgBurn General
Posted · Edited by fordman
Any chance that V2 will have the option to stamp all files to a user-specified date and time, similar to Nero?
Currently I have to use a patched together approach of stamping date/time with Powerdesk after BEFORE telling PGCEdit to create an ISO, and then I have to temporarily change the system date and time right before creating the ISO to get the same date stamp on directory entries.
I do this for when I re-author DVD backups...