DTS-HD MAS encoder has stopped working....why?

[jpsdr]

Hard to say...
I would think of maybe "no", because it's not something allowing you to run it without a license, but allowing you to just run it when you have license, because without, you can't (despite having a lifetime non-stop license).
But it's just a two cents thought, i'm not law expert.
And even more, it could be different according countries, the "right" to modify legitimate bought programs to allow it to run on your system when the seller/support is unable fo provide a solution, still staying in your license use.

[filler56789]

Originally Posted by richardpl

It this equivalence of cracking?

I am not a lawyer but I think the answer is «no».
Changing one byte to disable a time-bomb in a software that was assumed to not have a time-bomb is very-different from a dongle crack or a keygen, for example.
-------
P.S.: Several years ago Patrakov gave us a free open-sourced DCA encoder, maybe it is time for someone else to develop an open-source DTS-Express encoder and a pure lossless DTS encoder as well

[EMR]

Originally Posted by filler56789

Just confirming that the trick also works for the ancient version 2.00.24.
All one has to do is: open the original DtsJobQueue.exe in a hex editor,
look for the byte-sequence "BF D0 2B FA 79", replace "79" with "EB", save.

That is a terrific solution for all users of the Windows version of DTS-HD MAS. Is there a similar solution for the Mac OS X version? I would need either a patched version of the DtsJobQueue Unix executable or the relevant instructions to hex-edit said executable, or a patched DTSEncoder.app.

[filler56789]

Originally Posted by EMR

Is there a similar solution for the Mac OS X version?
I would need either a patched version of the DtsJobQueue Unix executable or the relevant instructions to hex-edit said executable,

Probably there is, but I have no idea of what it would be :-/

I have just opened the DTSJobQueue for Mac with a hex editor, but only because of, let's say, my "morbid curiosity", since I cannot imagine what I should be looking for in it...

or a patched DTSEncoder.app.

Are you sure of that?
I mean, that the time-bomb in the Mac edition of the Master Audio Suite is in that file :-/

[EMR]

Originally Posted by filler56789

[COLOR="Blue"]Are you sure of that?
I mean, that the time-bomb in the Mac edition of the Master Audio Suite is in that file :-/

A Mac "app" is, in reality, a folder with or without an icon. Because of that, the DtsJobQueue Unix executable is included in DTSEncoder.app, which is the folder that you double-click to do the encoding. It will run the relevant executable Unix file(s) as needed. So, it is possible to edit an app, usually meaning (hex-)editing one or more Unix executable files and one or more "plist" configuration files or the like.

As for the specific location of the time bomb in the OS X version, my hunch is that it's there because that's where the Windows version included said time bomb. More likely than not, both the Windows and the OS X versions include the same source code. I would assume the developers only adapted minor portions of their code to make it run on both platforms doing exactly the same thing. After adapting whatever they needed to change, compiling the code for both platforms would have been straightforward. If my hunch is correct, then that's where the OS X time bomb should be.

[filler56789]

Originally Posted by EMR

A Mac "app" is, in reality, a folder with or without an icon. Because of that, the DtsJobQueue Unix executable is included in DTSEncoder.app, which is the folder that you double-click to do the encoding. It will run the relevant executable Unix file(s) as needed. So, it is possible to edit an app, usually meaning (hex-)editing one or more Unix executable files and one or more "plist" configuration files or the like.

As for the specific location of the time bomb in the OS X version, my hunch is that it's there because that's where the Windows version included said time bomb. More likely than not, both the Windows and the OS X versions include the same source code. I would assume the developers only adapted minor portions of their code to make it run on both platforms doing exactly the same thing. After adapting whatever they needed to change, compiling the code for both platforms would have been straightforward. If my hunch is correct, then that's where the OS X time bomb should be.

Thanks for the information, because I really know almost-nothing about the Mac operating system.

[Overdrive80]

Originally Posted by neil wilkes

Someone please help?
My legally purchased and supposedly perpetually licensed DTS-HD MAS encoder suite has stopped working, and I am not the only person this is happening to.
Error log attached, and it is saying there is a 'configuration file error'.
NOTHING has changed except the calendar year - Windows 7 Pro, same version of Java.
A friend has the same issue on Windows 10 so it is not the OS.

Anyone got any ideas, please?

Are you testing with jre-6u45-windows-i586 version? In my case, it was one solution.

[badflame]

Originally Posted by filler56789

Just confirming that the trick also works for the ancient version 2.00.24.
All one has to do is: open the original DtsJobQueue.exe in a hex editor,
look for the byte-sequence "BF D0 2B FA 79", replace "79" with "EB", save.

Great!!!

[Lyris]

Originally Posted by filler56789

Just confirming that the trick also works for the ancient version 2.00.24.
All one has to do is: open the original DtsJobQueue.exe in a hex editor,
look for the byte-sequence "BF D0 2B FA 79", replace "79" with "EB", save.

How did you figure this out?

[filler56789]

Originally Posted by Lyris

How did you figure this out?

By looking at the original patched .EXE shared by rik1138:

Originally Posted by rik1138

Here's a fix I'm using for DTS-HD Master Audio Suite ver 2.60.22. Replace the DtsJobQueue.exe in the install folder with this one.

There's only a one-byte difference between this file and the original one on my install, so if you have a newer (or older) version, maybe see if they compare or not.
(The change is byte 418E5 from 79 (in the original file) to EB.
I didn't fix this, I found it on another forum...

Then I checked whether the bytes that appeared before the "evil 79" in the 2.60.22 executable also appeared in the 2.00.24 executable... and the answer was *YES*.

So I edited the older .EXE, tested it, and saw that the modification worked.

[Lyris]

Aha, so DTS themselves released a version that doesn't have this "booby trap" in it. Essentially we're just reverting part of it back to an older version.