The UI now supports other languages in the form of language files (*.lang). The app ships with English strings, but you can add other languages by adding the corresponding .lang files in the AppData folder (where the ini file is stored).
To create new language files, simply copy the English one, change the language code (use the ISO ID), and change all the strings. Then save it as a .lang file (the name does not really matter, it's the language ID that does). Strings that are missing from the language file will default to their English version.
RipIt4Me reads the available language files when it starts, and you have a setting in the preferences for which language to use in the UI.
If you create a language file, post it on the forum, and it will be included in the installer after verification. Thanks! For further information see section 3.1.7 of the guide.
Improved scanning for Buttons Over Video (BOVs). The first and last navpacks for every cell are always scanned. There is a new "Stride" setting which controls how many navpacks are skipped when scanning for BOVs. In other words, if Stride is 10, RipIt4Me inspects 1 navpack out of 10 for cells that are smaller than the limit you have selected. This makes the scan faster and allows scanning longer cells.
The stride parameter is in the preferences (default 30 VOBUs (navpacks)). A new default has been set for the maximum cell duration to allow a full scan (now 300s). For further information, see section 3.2.7 and 3.2.8 of the guide.
Titlesets that are completely unreferenced are now completely excluded from the rip (even the IFO/BUP files). This will avoid Decrypter error messages such as "IFO/BUP Patching failed", make the rip faster and make the cleanup process much simpler.
As well, if a Titleset is excluded from the rip, its individual files are no longer checked for validity since they're excluded anyway.
The option to run the "Jump to menu" function in 1-click mode is now recorded in the INI file (no preference item, but it will remember your last setting).
Sped up the start of the process by copying the already copied IFOs from the temporary directory into the target rip, rather than ripping them again from the disc. The IFOs are put into a temporary directory during Step 1. This makes things a lot faster when you have tons of VTS (e.g., Saw 3 or Flux DVDs).
If you skip Step 3b, the DVD is no longer reloaded (and scanned for BOVs). It will be though, if you select "Jump to main menu" in the next step.
Step 1 is now modal, and can be quickly closed using the ESCAPE key.
The code has been improved to handle huge IFOs found in game DVDs.
The UDF parsing code now makes sure that the number of VTS is less 100!
For DVDs with very larger numbers of buttons, an error could happen that wasn't caught by the new error catching code, which caused an analysis error in Deal Or No Deal.
Added small delay before sending the keystrokes for the PSL file path to accommodate Windows VISTA. Tests indicate that RipIt4Me now works well under VISTA.
Fixed a problem in the analysis, which caused all the VTS to be removed in some DVDs!!!
Removed some annoying messages (scanning for BOVs on titlesets that were not ripped) and added protection against crashes in cleanup phase.
Added display of maximum duration for BOV scan and stride at the top of the log, so we can more easily check what's going on.
Fixed a crash that was reported by several users, at the end of the cleanup phase. Thanks for posting the debug logs! That helped a lot.
Important NOTE: For those of you who are still having problems where the drive or the DVD isn't detected, please run the LBAExtract app that's on the RipIt4Me home page (http://www.ripit4me.org/LbaExtract.zip) and post your results. We need to get to the bottom of these problems, and we need your help for this! Thanks in advance!
Finally: RipIt4Me 1.6.4.0 was able to rip Saw III without any change to the code (although 1.6.5.0 will do it a bit nicer, avoiding the DVD Decrypter messages)!
That was a significant achievement! We thank all the beta testers and the users who've helped bring this app where it is. The only reward we want is your satisfaction with the program.
