OmniPatcher for LiteOn DVD-Writers (v1.4.3) (OLD)

So, you don't have to select a strategy? Cool. That's the only thing that was confusing me. I just used the crossflash exe firmware before.

i have a 451@832 litey, using firmware vsoa, ran it through the omnipatcher with appropriate speed hacks. is there a way to check what options i may have enabled in the current firmware? in other words, my burns with both ricoh jpn r01 and cmc mag e01 have been spectacular, especially when i burn at 4x instead of 8x (pi less than 9 max, pif 0). if i upgrade firmware to vso8, i want to achieve the same results as i get now ( i know i should leave it alone, but i love to test the limits ). i can't remember if i did fallback, etc.
advice codeguys?

If you load your patched firmware into OP (if you don't have your firmware, you can dump it from your drive), OP will tell you what patches (see the checkboxes) and what strat switches (look for the exclamation marks) you have applied. The exception is the reading-speed patch; if you have applied the RS patch, then the box should be grayed out instead of checked if you open the patched firmware in OP.

---

Last edited by code65536; 09-11-2004 at 05:32. Reason: Typo

thanks code!

js2020 what strategy your use for cmc mag e01 this DVD+R failed to me, please post a msg with your strategy and what speed your used, click in the glasses for save strategy

Great works code65536 and C0deking

Thanks
Vacio

A few people had success with the CMC MAG R01 strategy. From js2020's post, I'd say he was using 4x burn speed.

does force fallback only work for 8x burns because i burn T01 at 4x only and i get high error rates at the end of the scan.

Yes. All it does is drop the burn speed from 8x, to 6x or 4x near the end of the disc.

I see you have posted in the CGxx thread but have you actually tried CG3E yet. This might help or cure your problem.

hey Codeking sorry about the stupid mistakes i made on the forums i got my post deleted from another thread. sorry. well ill jus say what i gotta say. im gonna upgrade to the CG3E firmware and ill also get omnipatcher with it. below is the type of media i will be using. does anyone know some good write strategies for the type im using with CG3E firmware? i mostly want quality, low pif and pi. thanks, and sorry for all my mistakes and questions

The default write strategy should be fine. CG3E will up the speed on those to 8x, at which speed they should produce excellent burns.

No, the recommended tweaks need to be applied to CG3E, to up the burning speed to 8x. The default for both T01 versions is 4x.

how come i need to speed hack it to 8x? does it improve the burn quality better than burning it at 4x? i just want good quality. like do you know any recommended tweaks with omnipatcher for the type of media i have?

Some media burns better at 4x then 8x and some the other way round. I'm not sure if T01 burn better at 4x or 8x. Maybe someone else can tell us that.

I'd suggest you start off by using CG3E stock (no changes). Then show us the results of your T01, in the CGxx thread.

Thanks Code
I changes my sony 710A to liton 1653S
and Chenges Sony D11 ( 8X+) strategy to Sony D21 (16X) and Burn at 16X
It take 5min 55secondsfor 4.12 G data and the Pe.PF value is good

For my 832S, my T01s burn about the same at 4x or at 8x. The OP recommended tweaks button should set both of the T01 types to 8x for all drive types.

I recently had someone play back a wedding video I burned on a 1633 Lite-On using the current version of Nero at 4x. The video froze up on a stand-alone player at some point (I didn't observe this, someone else did). I used Omnipatcher to convert a DVD+R to a DVD-ROM, but I'm not sure if that's the problem or not. I used a Fuji DVD+R (actually made by Ricoh according to KProbe). I'm planning on experimenting to see if the same problems occur. I turned off bitsetting in the drive's firmware on one disk (same video as the first one that had the freezing problem). I then burned the same video on my Sony DVD burner - again using a DVD+R - with no bitsetting (Sony drives don't support bitsetting). I want to see if the same freezing problem occurs. My next experiment is to burn using Nero at 2x using the same video and try bitsetting and without bitsetting and see if the problem occurs. I might end up going back to DVD-Lab to do the burning to see if Nero was the problem.

@harpert It sounds to me more like a media problem than a program or bitset problem. The disc was recognized by the player. Try posting some Kprobe 2.4.2 scans done @4x speed. after scan, save(while disc is still in the drive) as .png using diskette icon at the upper right. Attach by 'manage attachment' button in the 'go advanced' reply window.

Thanks for the reply. I'll do a Kprobe scan tonight as you recommend. I thought Fuji (Ricoh) disks were ok, but based on your comment that it's a media problem, I'm beginning to wonder. My clients encountered freeze problems with DVDs I purchased from my local PC Club (http://www.pcclub.com) and I made the mistake thinking I could get by using those (the last batch I bought was priced at $.40 each). I was trying to avoid the freeze issues I encountered with cheap, no-name brand DVD media, and purchased (what I thought were quality) Fuji DVD+Rs. I recall seeing Fuji DVDs on a list of recommended DVD brands. What brand media do you recommend? I saw Ritek (can't recall the special coating on them) on that recommended list. Would you agree or recommend another brand? I'm also wondering if the parameters I used (such as a compression rate of 4 mb/sec) on TMPGenc to convert from an AVI file to MPEG-2 were a problem.

Tom

@ harpert My personal favorite are RICOHJPNR01 for backing up stuff. However, for commercial purposes I would probably go with what is supposed to be THE best, Taiyo Yuden +R discs. You can do a search around here for others' comments or google for them.

I'd be really surprised if the problem was with the media itself.

Fuji 4x DVD+Rs (media code RICOHJPNR01) are excellent discs in my experience. Out of the several hundred that I've burned, I've encountered one problem, and that may well have been related to the source, rather than the media.

I prefer using Nero CD/DVD Speed to Kprobe, as I've found Kprobe's results to be all over the board, when going from one drive to the next, plus the nero utility can be used on any DVD drive. Burn a couple test discs on the media, and test them on any DVD-drive you can get a hold of, as well as on your stand-alone player(s).

I have never seen this speed drop on 1213s@1633s or 1653s.
My drive is always speeding up from 60% or 70% up to end so the actual speed near end is 7.8 or 7.9.
Further finishing disc burn in lead out speed is 8x sharp.
I don't see any speed fallback even I always check that option in Omni.
Please explain?

The speed drop CK was talking about applies only for 51S and 2S drives. OP keeps the box disabled for 3S drives so you shouldn't be able to check it...

New version: 1.3.16

This is a minor release. Unless you have a slimtype drive, there is really no reason to upgrade to 1.3.16. This version basically contains some of the little things that I had wanted to do for 1.3.15 but did not do because I didn't want to delay it even more.

The first post has been updated accordingly.

Future directions...

Unless there are important bugs/problems that need addressing, this should also be the last of the 1.3.x series of OmniPatcher. Tentative plans for the next version, 1.4.0, include possible interface layout changes, a media code rename feature (in the meantime, if you happen to be one of the few people who have a need for this, use ala42's tool), and the ability to select what reading speed to use for the reading-speed patch.

We don't have an ETA for this version, but, at the moment, it is not a high-priority item, especially now that ala42 has released something to address the media renaming thing.

---

Last edited by code65536; 12-11-2004 at 05:19. Reason: Typo fix and wording adjustment.

I haven't had tried any KProbe or Nero scans yet - been busy with finishing a video and doing home stuff. I did try out the Fuji DVD+R (converted to DVD-ROM using Omnipatcher) on another DVD player (Panasonic DVD-S25, about a year old) and it played back fine. I tried the DVD again on my 2 year old Panasonic player/recorder (can't recall model number) and it played back fine at the point that froze on a Sony player/recorder (don't know the model number or how old). My problem may be player dependent with different results obtained on various makes and models - too many variables to have to consider. I feel somewhat more confident now about Fuji DVD+Rs. I'll try to convince the video guys in my building that the DVD+R bitsetting to a DVD-ROM was not the problem. It could be that some players are more compatible with certain DVD brands than others. I'll recommend they try out that DVD on other DVD players in the building to obtain a better sample of data.

Can I finally start speedhacking for the slimdrives...