DoStudio has stopped working - help!

[TenementLady]

When attempting to multiplex the files (via the PureHD Corel multiplexer) an error appears:

"Error - cannot find a parser component (2) - Code error 0x80004002"

I know Sony deactivated their DoStudio servers, so I guess the software really is dead now.

Has anybody found a fix?

[videoAI]

If PureHD is no longer functional, consider these multiplexing tools:
- Clever FFmpeg-GUI
- DVDFab All-In-One
- HandBrake
- MakeMKV

[TenementLady]

The multiplexer in DoStudio must execute the compile.

[TAMVid 63]

[QUOTE=TenementLady;2786604]When attempting to multiplex the files (via the PureHD Corel multiplexer) an error appears:

"Error - cannot find a parser component (2) - Code error 0x80004002"

I just got the exact same error message, something has been globally updated.

[kklaus]

I can report the same thing. My old DoStudio installation also stopped multiplexing. I suspect that some certificate of the Corel Pure HD Multiplexer, which is called in the background during compiling, has expired. And if the Corel multiplexer doesn’t run, of course the Blu-ray compilation won’t run either.

However, I found a trick to get the multiplexer working again. For this, the system date has to be set back. For example, to May 1st, 2025. But this only works as follows:
1. Set the normal current date. Start the compile.
2. When the compiler window appears, immediately go into the system settings and manually set the date to May 1st, 2025. There isn’t much time for this, because within a few seconds the Corel multiplexer is launched.

If you manage to do it quickly enough, the compiler runs correctly. If you’re too late, the error message appears again. Unfortunately, it doesn’t work to set the date back first and then start compiling. DoStudio is very picky about the date. For me, this quick-switch method has been the only thing that has worked so far.

[TenementLady]

I'm hoping that a patch or modification to Corel's built-in expiration date can be figured out.

[krykmoon]

When attempting to multiplex the files (via the PureHD Corel multiplexer) an error appears:

"Error - cannot find a parser component (2) - Code error 0x80004002"

I know Sony deactivated their DoStudio servers, so I guess the software really is dead now.

This is the primary reason to start (continue) to ditch all this online commercial crap with servers and cloud shit.. and focus on opensource software that works on your pc (non theirs).

I hope opensource will get better and better.. but people have to realize that opensource needs money too to develop and improve.. and I think it's a lot better to donate what you can to amazing projects like Blender, Kdenlive, Krita, Gimp, Inkscape (the list is long : if it's opensource and you find it useful and you can.. donate!) than to pay for all the commercial crap that it's server based and that they can shut off (or change the conditions) when they want.

[TenementLady]

It would be great if the original NetBlender guys could re-start software development on it and keep it updated, and even make it 4K compatible, but I guess Sony had a clause in their buyout that meant they cannot do anything with it in the future.

[krykmoon]

It would be great if the original NetBlender guys could re-start software development on it and keep it updated, and even make it 4K compatible, but I guess Sony had a clause in their buyout that meant they cannot do anything with it in the future.

These <great corporations> prefer to destroy everything, to let everything they buy (but they are not more interested in) to die than to allow anyone to go on with the project.

That's the main reason to go opensource and support those many awesome software with donations. And if they die.. since they're opensource.. someone can take them over.. and - anyway - even if not updated anymore.. they will never expire.

[TenementLady]

Sadly I don't think there is too much interest in Blu-ray/UHD authoring software, which is the reason the software that is available is costly to develop and is so prohibitively expensive to buy.

[krykmoon]

Sadly I don't think there is too much interest in Blu-ray/UHD authoring software, which is the reason the software that is available is costly to develop and is so prohibitively expensive to buy.

Bluray was a nasty thing from its beginning: it was created to make everything difficult and painful (outside THE RULES they were trying to impose).

That's why there weren't too much interest in it (HEY: they broke the encryption.. and started to offer some tools to do a lot of things.. but it's already a dead media/format.. that's why there's so little interest in it nowadays)

[TenementLady]

I disagree, there's a very healthy collector's market for Blu-ray and UHD discs.

[krykmoon]

I disagree, there's a very healthy collector's market for Blu-ray and UHD discs.

There may be.
But the format itself is quite dead.
Due to those bad choices from the beginning (closing and imposing everything).

The present and the future is .. the streaming. Not something to be so happy with.. but that's how's going.

[TenementLady]

I preferred the HD-DVD format, it's a pity Sony won the battle with Blu-ray.

[TenementLady]

I don't suppose anybody out there knows how to access and change the date in the Corel Multipexer promgramming code? I remember doing it when a similar thing happened with the DTS Encoder. I opened the app in a special programme editor, searched for a specific string, replaced it with a new line of code, and voila, it worked again.

[TenementLady]

I can report the same thing. My old DoStudio installation also stopped multiplexing. I suspect that some certificate of the Corel Pure HD Multiplexer, which is called in the background during compiling, has expired. And if the Corel multiplexer doesn’t run, of course the Blu-ray compilation won’t run either.

However, I found a trick to get the multiplexer working again. For this, the system date has to be set back. For example, to May 1st, 2025. But this only works as follows:
1. Set the normal current date. Start the compile.
2. When the compiler window appears, immediately go into the system settings and manually set the date to May 1st, 2025. There isn’t much time for this, because within a few seconds the Corel multiplexer is launched.

If you manage to do it quickly enough, the compiler runs correctly. If you’re too late, the error message appears again. Unfortunately, it doesn’t work to set the date back first and then start compiling. DoStudio is very picky about the date. For me, this quick-switch method has been the only thing that has worked so far.

Do you know if this method time stamps an incorrect date on the multiplexed files? Does it affect the date of the CMF master files?

[kklaus]

Do you know if this method time stamps an incorrect date on the multiplexed files? Does it affect the date of the CMF master files?

No. Unfortunately I can’t say that. The last project was only intended for a small duplication. That’s also why I didn’t need to create a BDCMF. You could try opening the master with BluStreak Tracer and checking which date is set there:
https://rivergatesoftware.com/support.html

[TenementLady]

OK, thanks. I'm wondering if this app would work to quickly change the date?

https://en.softonic.com/download/systemdatechanger/windows/post-download?dt=internalDownload

[Mahar]

Hello,

I found a radical solution to stop getting this message.
You need to open the LdvdAdvCntScriptParser.dll file located in the "Drive:\Do_Studio\Authoring_Launch\SouthBay" directory with IDA Pro.

In the procedure : sub_10020E30

.text:10020E30 ; int __stdcall sub_10020E30(int, const WCHAR *lpString, const WCHAR *lpWideCharStr, int, int, int)
.text:10020E30 sub_10020E30 proc near ; DATA XREF: .rdata:10110DA8↓o
.text:10020E30 ; .rdata:10110FE4↓o
.text:10020E30
.text:10020E30 var_814 = byte ptr -814h
.text:10020E30 RootPathName = byte ptr -114h
.text:10020E30 var_10 = dword ptr -10h
.text:10020E30 var_C = dword ptr -0Ch
.text:10020E30 var_4 = dword ptr -4
.text:10020E30 arg_0 = dword ptr 8
.text:10020E30 lpString = dword ptr 0Ch
.text:10020E30 lpWideCharStr = dword ptr 10h
.text:10020E30 arg_C = dword ptr 14h
.text:10020E30 arg_10 = dword ptr 18h
.text:10020E30 arg_14 = dword ptr 1Ch
.text:10020E30

We find a test :
cmp byte_101A2F0C, 0
jz short loc_10020E95

.text:10020E80 loc_10020E80: ; CODE XREF: sub_10020E30+28↑j
.text:10020E80 cmp byte_101A2F0C, 0
.text:10020E87 jz short loc_10020E95
.text:10020E89 push offset aErrorCannotFin_0 ; "*Error : Cannot find a parser component"...
.text:10020E8E push 137Dh
.text:10020E93 jmp short loc_10020E64

The variable aErrorCannotFin_0 is equal to :
.rdata:10110A14 aErrorCannotFin_0 db '*Error : Cannot find a parser component (2).',0Ah,0

This corresponds exactly to the error that occurred when the multiplexing was started.

Simply change the instruction `jz short loc_10020E95`=> (75 0C) to `jnz short loc_10020E95` => (74 0C).

Wee see to the label loc_10020E64 the code error 80004002h

.text:10020E64 loc_10020E64: ; CODE XREF: sub_10020E30+63↓j
.text:10020E64 push offset aXauthscripteng ; ".\\XAuthScriptEngine.cpp"
.text:10020E69 push offset dword_101D8F0C ; int
.text:10020E6E call sub_10008760
.text:10020E73 add esp, 10h
.text:10020E76 mov eax, 80004002h
.text:10020E7B jmp loc_1002129E

And there you have it, the program is cracked and will no longer display the message => Error : Cannot find a parser component (2).

Best regards

[TenementLady]

My PC is away for repair at the moment, but THANK YOU!