BR Disc Burning Problems with IMGBurn (no response on s/w website)

I use real (near professional x264 encoding) s/w when converting/compressing discs, i.e., MeGUI/MKV; the engine used in DVDFab is the Bluray equivalent of DVDClone, which 'back in the day' was the poor equivalent of DVDRebuilder/Cinema Craft Encoder (again, professional s/w).

I used to use DVDFab years ago, but they 'split' DVD and BluRay decrypters into two products (two revenue streams, right?) and that's when I switched to AnyDVD, which just about everybody else that I 'talk' to has as well. Also ran into way too many discs that wouldn't decrypt.

.... YES Success! and guess what... going back to a very earlier version of IMGBurn did the trick. '

In fact, I jumped all the way back to v2.5.1 (released Apr 2010), burned my ISO rip, and it worked just perfectly! I'm burning the file version (BDMV/Certificate) and will see what gives then, but I'll bet (maybe a penny at this point) it will work; I'll update this posting when/if.

So, at some point IMGBurn 'went off the tracks' as in, the programmer failed to test out their program fully. At what point this happened, is a good question. I think I'm like most folks, especially when it comes to 'PD' programs like this, 'if it works, why fix it?'.

I would have never 'upgraded' IMGBurn if my older Vista/32 machine hadn't taken a really big dump, and I hadn't had so much problems in the past getting any backup routine to work (after this, I did make a new concerted effort to see what if any decent things had come out of the woodwork since 3+ years ago when I last failed to find something that actually worked, and found a program/system called 'Image for Windows' that works across all Windows (back through Win/NT4! now that's programming!) so ran tests and it works on my W2K machines..! (which was still widely being widely installed back, although XP was gaining ground, when I retired!)

Anyway, at some point IMGBurn failed; now, I'm not going to go through all the versions back from the most recent (2.5.8.0) and figure out where it went off the tracks; I'm RETIRED, and if the folks at IMGBurn want to pay me what I made circa 2002 to figure out their mess (btw, ~$2500/day) they can sign a contract.

Anyway, continuing to test. Will add to this posting when I get more info!

UPDATE: The files rip (BDMV/Certificate) plays okay as well.

For those who don't understand what's going on with programmers (in general) today or over the past few years (at least 3-4 decades, really) read WIRED on the disaster in rolling out the ACA/Heath Care sites. I could have told them months/years ago that you can trust programmers to do a job just about as far as you can trust a certain political party not to try and crater the country to turn it over to fascist billionaires. In other words, about the length of your arm so you can punch their lights out when they get out of line.

The reply I got on the Imgburn website was 'typical', tail wagging the dog. Blame me for the Bluray burner I have (although I proved that the program previously worked 100% by re-installing the older version), and not upgrading to a newer 'kit' or installing new drive firmware. If your software worked in the first place, and I'm not trying to do something 'new' like a new type of burnable disc (more 'x' times speed or something), then the 'new' s/w should work. Period. But obviously they changed something in the code to make it NOT work.

I've been in development conferences at multi-billion dollar projects (both in the government and private industry) where programmers have been told we needed x to do y, and been flat out that x would have to go the z to get to y and that's just the way it was. Well, see you later, bring in the next company and have them get to work. I'm sure with the ACA problems now, nobody was apparently willing to do that. Kick ass and take names.

At least in my case here, I could go back to something that worked. I'll keep the 'newest' s/w on one machine, and update when I see a new version, and give it a try again. But I have the luxury of keeping the old s/w on another machine, and burn there when I need to, something I'm sure most folks don't have.

Quote:

---

Originally Posted by Beck38

For those who don't understand what's going on with programmers (in general) today or over the past few years (at least 3-4 decades, really) read WIRED on the disaster in rolling out the ACA/Heath Care sites. I could have told them months/years ago that you can trust programmers to do a job just about as far as you can trust a certain political party not to try and crater the country to turn it over to fascist billionaires. In other words, about the length of your arm so you can punch their lights out when they get out of line.

---

Bullshit.

In any given disaster involving programmers, it's more likely it's the result of poor management. It'll be bad specs, micro management to the point of impeding the progress of the project, overly optimistic project plans, vague specs, inaccurate specs, unrealistic specs or no specs at all. If something goes tits up, I'd start looking at middle management, people in marketing, project leaders or virtually anyone else who has a say in the planning, especially if they are bound to stack more things on or alter priorities on a whim, or anyone who tends to bypass proper channels to bring issues directly to people who're meant to focus on a specific task. Sometimes the customer will also exacerbate things by making unrealistic demands, or changing their minds midway. Virtually anyone in a position of power who doesn't get the technology, but thinks they're all right to make quick, uninformed calls can screw over a project easily.

And it's precisely that sort of attitude you're displaying that has them screwing things over.


And don't get me started on firms that start outsourcing to places like India or latvia and expect the project to run as efficiently as if it were done in-house. Which it won't. Not because it'll be done by worse programmers, but because of failures in communication, different standards or bad logistics.


Other than that, I'll be very surprised if there's a piece of software that'll work with every concievable combination of hardware possible today, especially when factoring in not only current configurations sold today, but anything that's been in play since five years back or so, whenever it became affordable for end users to start burning blurays. The issue here is probably related to that they've not been running any tests on configurations similar to yours for a bit. Which is probably understandable given time constraints and imgburn not being run by a huge operation.