It's because of quality, but what the FAQ is saying, is that slowing the burn speed down will probably make no difference, or it could make it worse. You should find some better media, that will produce better quality burns, at the speeds your drive supports.

Alright king, do you know why I can't enable auto bitset on a 1613s to 1653s?
I'm confused so any help is greatly appreciated. I've tried 1633s firm as well as 1653s both cf and stock.
Thanks

It would be fine if you could be more specific. I would guess you wanted to say that omnipatcher does not allow you to enable auto bitssetting anymore. That would be the case with the latest liteon firmwares for 16x3 drives, because there is a new booktype tool available on the liteon site, version number should be 1.33, which stores to choosen booktype inside the drive as default booktype.

Sorry. just a bit frustrated at the time. So will the new utility work permanently or will I have to use it every time I burn a disc? Just got a _3s drive and I have always had a _1s@_2s drive so I have always used the auto bitset. When I could not enable with the _3s drive, I was a bit ticked. I'll try the tool. Thanks

Check the omnipatcher history file for the details. Auto bitsetting to DVD-ROM was disabled for some firmwares because this firmwares can handle it better now on their own (permanently, but selectable) with the new booktype tool.

@unkdunk
Also see this post.

If OP doesn't show the code for the media I have, there is nothing I can do, right?

I have some FUJI (ProDiscF01) that say "up to 8X" but will only burn at 2X maximum (and only shows up to 4X in thd identifier program). The ID is as follows:


---------------------------------------------------------------------------
Unique Disc Identifier : [DVD-R:ProdiscF01]
---------------------------------------------------------------------------
Disc & Book Type : [DVD-R] - [DVD-R]
Manufacturer Name : [Prodisc Technology Inc.]
Manufacturer ID : [ProdiscF01]
Blank Disc Capacity : [2,298,496 Sectors = 4,489.3MB = 4.38GB (4.71GB)]
Recording Speeds : [1x , 2x , 4x]
[6x And Higher Might Not Always Be Detectable]
-------------------------------------------------------------------------

I'm not looking to get 8X from -R blanks, but I'd like to at least get the 4X I'm used to on my 411s@811s. The OP list doesn't show this code, so until a new firmware is released, I'm stuck at 2X, right?

Thanks

Wrong . Follow the link in my signature and add any media code you want.

Thanks, but I can't figure out how to use that program. I load the firmware, but I can't get the IMPORT button to become functional unless I highlight one of the codes already listed in the window. Then when I paste the code in the open window, I don't know what to do after that. If I try to SET, it asks if I want to replace whatever is highlighted. Why can't I add to an empty line? It seems that it only allows me to replace one of the already listed ones with my new code. Am I having a "stupid" day?

No, you have got it right, but missed the second sentence in the thread:

I didn't miss that sentence, but I didn't realize it was the ONLY way to add a new code. I guess I understand somewhat now -- there must be only a limited amount of bytes of firmware space, and to add an unlimited number of new codes would go beyond that limit, right? :-)

So, let me see if I get it now --

1) If I want to add one, I must replace one -- and I just choose one to replace that I probably won't need to use?

2) Can I add higher speeds to codes already there?

Thanks.

Close . Even adding a limited number, e.g. just one code to the tables is too complex. The only way would be patching the code search function, as omnipatcher does when changing the write strategies.

Right.
Yes, but keep in mind that your x11 drive can not burn -R faster than 4x.
You probably have to swap the strategy a few tries with omnipatcher until you find a strategy which works fine. Check the Changing write strategies thread for details.

Great, thanks for the quick feedback. As for the -R, I had seen that many times (not being able to burn faster than 4X) but then I saw some posts on various threads where people indeed were able to burn higher. That's why I said earlier "I'm not looking to get 8X from -R blanks" but then I found these FUJI -R that say "up to 8X". I did add that code and checked the 8X box, but it only now shows a maximum of 4X (see my post in your MediaCodeSpeed thread) so I guess that's the limitation you refer to for the x11 drives. As said there, I'll be quite happy to get 4x from them...it's much better than 2x. :-)

Thanks again.

hello Ala

As posted before, i did as you said and indeed the only available speed was 2x. Whatever else i change in the media code, however, is ignored and the discs cannot be written at over 4x. do you have a solution for this or a reason because this does not work?

thank you.

I fear a bit that the 852 does not write -R media faster than 4x. At least PS01 does not burn TYG02 faster than 4x, it should burn at 8x. To verify this you could use MCSE to overwrite the your original FUJIFILM03 media code and replace one of the 8x capable media codes, e.g. TYG02, with FUJIFILM03 to check if your disks allow 8x burning now.

hey, would it be wise to use the OmniPatcher for my LiteOn 1653?
i burnt a movie at 8x(using tdk cmc media) and the movie itself lagged and skipped, now would this OmniPatcher fix this up? i also recnonised my burner reads discs a bit slower hmm, this looks promising.

thanks in advance.



-elementz

just give it a try...

Welcome to CDFreaks

You may have a burning problem with the TDK media. It may improve after a couple of burns, as the drive learns. If not, read the announcement at the top of the forum and these two FAQs:
http://club.cdfreaks.com/showthread.php?t=109986
http://club.cdfreaks.com/showthread.php?t=118794

Start a new thread and post a Nero or Kprobe scan of the disc that skips and all of the information about your drive, media and system.

VERBATIM MKM001 DVD+R DL scan
Burn speed: 4x
scan speed: 4x

Burn time ~26 min including leadin/leadout.


Here's a DL burn using a dru-710a flashed with the sony BYx2 firmware. Modified with omnipatch 1.3.18 for autobitsetting and riplock disabled. No other changes.

The 2nd layer appears slightly on the highside as far as # of PIF failures (though overall PIF max value is low.

Any other comments?

thanks

I do not know if this is a bug or a feature.

I have a bunch of DVD-R without any Media ID. I used MediaCodeSpeedEdit to replace one of the existing DVD-R codes with a blank MID. It disappeared from the display.

I saved the file.

I opened it using omnipatcher but now all DVD-R codes are gone. Is this what's supposed to happen? I flashed using the file and the Blank-MID media was recognized by the drive.

It's a limitation. Each of the media tables contain at least one blank media code (which is why it's not a very good idea to blank out a media code). Blank entries are filtered out. For older, pre-3S firmwares, because of how the codes are extracted, a misplaced blank entry can disrupt the reading of the codes (this would not be disruptive with the newer 3S firmwares and should just result in a single disappearing entry).

thanks! Is there any special reason why the blank mids are filtered out? Can this limitation be fixed on ere-3s FW? I'm using 812s @ 832s

so now that it all seems to have settled down, could i remind of my little suggestion? what about saving all changes you do in gui, to .conf file, which can be loaded again? as it is now, it's quite painful to upgrade to new firmwares, and have all your changes saved (unless you want to create .conf manually, which could get tricky for the inexperencied

trying to load 1653S.CS0C.stock.exe in OmniPatcher v1.3.18 i've got an error message:
"OmniPatcher expected to find 10 media tables in this firmware, however, only 3 tables were recognized.
There will likely be some media codes in this firmware that are present but are not being reported by OmniPatcher."
Is that means: firmware is bad or it can not be used with OmniPatcher v1.3.18?

CS0C is not yet supported by omnipatcher, look here.