Dear DVDFab Users, For decades, DVDFab has been the cornerstone of your digital media collection. Your loyalty is the bedrock of our innovation, and as we head into 2026, we want to ensure our technical precision meets your highest expectations. We are currently refining our development roadmap and invite you to vote for the features you need most from our new list, such as Video Colorization, Audio Quality Enhancement, and DVD to UHD Upscaling, as well as many more to choose from. If you have other brilliant ideas or specific technical features not listed here that you’d love us to support, please share them with us in the comments! Your insights will define our engineering priorities for the coming year. Let’s make DVDFab even better together!

Radeonのグラボにももっと対応してほしいです

This is a feature request for the logging to help dealing with disc read errors and whether they actually matter that much or not. My specific use case is doing full copies of discs. This is for large NAS (80TB) and playback via a device (DuneHD) which can play the disc from folder / ISO over network. Having said that, I have also done rips of specific episodes to mkv, which of course can be constructed with multiple files on disc (e.g. extended cuts, etc.). I've ripped about 20TB of stuff so far, fighting my way through Game of Thrones 4K box set (known for defects). - When a read error occurs, the log file provides very basic info, e.g. "read error filling 0: 11 22773760 22781370 22777280 24" ~~- it would be very helpful if the error log could flag the specific file (e.g. 00123.m2ts) that will be filled with 0 so I can then go look at it in the output folders.~~ [EDIT - I just figured out the # of the .m2ts file is at the end of the read error line] - I can sort of guess at what that read error is (looks like a block with start and end address, then position of the error, not sure after that). Would be nice to have a legend for that somewhere. I've spent a bunch of time doing multiple rips of full discs and doing diffs (e.g. WinMerge) between the multiple different output folders looking for any files that mismatch, which is a strong indicator that those files are actually the ones that had errors because the errors will probably be slightly different on each run. Many times, the file with errors are the little 20 second long (~15MB) m2ts files with the copyright warning in many different languages. I may not have a perfect copy of the disc, but those files do not really matter. ~~What I want to know - upon error - is what files the errors are in.~~ [EDIT See above] Then I can determine what I need to do about it. Also, if there is any more info about the error that can be provided, that would be helpful. I'm not sure this is completely possible or not, but it would be great to know what layer and the radius from the center of the disc so that I can hunt for the offending dirt, scratch, or defect. I'm assuming that based on the disc "type" (e.g., BD100) and the sector, that information should be fairly straight forward to calculate. Is there good spot for little UI/UX or other reports for little (some very minor) usability comments / suggestions? Thanks! [EDIT - adding items] - It would be incredibly useful to have a log spit out for each disc separately, that way I can compare the logs to see where the errors were on multiple runs. - BUG? I left a rip going for hours that I already knew would have issues. I wanted the smallest amount of 0 fill possible, so I set the "skip sectors after a reading error" to 0. Looks like that ended up never moving forward to the next sector, so it sat for hours and hours try to read the same error sector. I assumed that "0" would mean the number of sectors after the error to skip and assumed the error condition would just cause it to move to the next sector. Maybe I am not understanding this?

I wish the Blu-Ray Creator module gave users better control over creating custom menu settings, without the templates, and allowing them to add buttons and chapters from a JPG image. The program is good, but the option to create menu settings is very weak.

I wished their was a linux version as having to move from windows to Linux as not replacing working pc just because some components are not supported with windows now .

Mein Wunsch wäre Magenta TV bei den Stream Fab

**+ 1000 on the Linux version!** I think it would be much faster. Or, a windows version which works under wine or similar so I do not have to keep maintaining a windows boot drive. Also it would be great to have a media catalog generator media organizer. I have a lot of DVDs and CDs and having to manually update a spreadsheet every time I buy more is a real pain. Software which would add to a database I could export to a spreadsheet when I rip/add a new movie/album/ebook to a set of folders.

I would like to see a stand alone captioning option to be used when working with home videos.

Mit den vorgeschlagenen Funktionen kann ich persönlich nichts anfangen. Lieber als neue Funktionen wäre mir, dass bereits vorhandene Funktionen laufen bzw. Problemmeldungen nicht monatelang "in Bearbeitung" sind oder "auf der Warteschleife" landen :)

[Official Vote] Which New DVDFab Features Matter Most to You?

djbwells

Ive just bought the Mac Version… UHD Creator doesnt work at all… just hangs when its supposed to start encoding, and the Disc Copy function works but crashes the app when finished. So would be nice if you charge for an app please make sure it works first.

flavien9

Suppression des filigranes

accountisfake

I would love to have DVDFab not continuously crash. After each “upgrade”, I always revert back to 13.0.4.9, what I consider the last stable version.
First, if I start DVDFab and then insert a disc, the system & DVDFab don’t see the disc. I have to insert the disc first, let the system read it, THEN start DVDFab. Now, ALL versions after 13.0.4.9 after ripping the disc, I insert a new disc and it refuses to read it. I would have to shut down DVDFab, and go through the 10 minute startup procedure again.

Another feature, stop defaulting to “Copy Disc”. It took me awhile to figure out that is the default and when ripping a disc, I would get an error that there was no writable disc available.

Another fix that needs to be made, is the 10 minute startup. After starting DVDFab, and it has read the disc, it “locks up” and is unresponsive. If I click anywhere in the interface, I get a system error, “The program is non-responsive, select what you want to do”. This stays up for 90-120 seconds before DVDFab becomes responsive again. This really needs to be fixed.

Can you please remove the “weekly limit” on the number if discs that can be done in a week?

« Previous Page