v 1.3.11 zero file sizes

[newyankee]

I am back, I don't really know what fixed it yesterday. But with the patches applied, PVRX2 dies after a few seconds. There's nothing in the logs.

Do you want me to record to full ts?

Guido

[sub]

If its crashing, yes try capturing that c:\temp\full.ts as mentioned above.

[newyankee]

I don't get a full.ts file with that reg key. I captured a regular *.ts file through the config setting. Hope that works for you. It's from a channel that causes pvrx2 to crash within seconds. If I roll back to psiparser from the 1.311 install all is good.

Load the ts from http://www.zshare.net/download/55351992e99d3f89/

Guido

[sub]

I don't get a full.ts file with that reg key. I captured a regular *.ts file through the config setting. Hope that works for you. It's from a channel that causes pvrx2 to crash within seconds. If I roll back to psiparser from the 1.311 install all is good.

Load the ts from http://www.zshare.net/download/55351992e99d3f89/

Guido

Unfortunately that file scans fine for me, and correctly identifies all the channels.

----
Can you try the utility from here: http://support.microsoft.com/kb/286350. The relevent section on how to use this seems to be:

ADPlus -crash -pn myapp.exe
This command runs ADPlus in crash mode for the process named Myapp.exe. ADPlus waits for an exception to occur, or for a user to press CTRL+C in the minimized debugger window, to generate a memory dump file and to detach the debugger.

Of course substituting myapp.exe with pvrx2.exe. This should generate a minidump which will give me more info to go on.
Initially I'll just want the text file it generates, but may also want the minidump itself.

[BigMoose]

Annoyingly, with the RecordFullTS key set I cant get it to crash!! However when I set it to 0 it crashed quite happily. I'll keep playing and see if I can get a stream recorded that does crash but there's only so many Gb that I have a hope of uploading anywhere... For now I'll prob have to roll the problem file back so I dont cause the wife problems tomorrow. But given enough people here seem to have the problem I hope someone captures a troublesome stream sooner or later. I'll post if I succeed.

[soccerdad]

Hi Sub,

For what it is worth. I have not been seeing any crashes.

[sub]

Annoyingly, with the RecordFullTS key set I cant get it to crash!! However when I set it to 0 it crashed quite happily.

The other option is to try the adplus recommendation in my previous post.

[UncleJohnsBand]

Sorry, I was targetting that reply at kayfam, with his crash.

Yours is probably a case of ffmpeg not liking something about your broadcasters encoding parameters. You might need to find one of those recordings that fail to transcode, then manually run ffmpeg on it and see what error it reports. You may not be able to do anything about it though (other than trying different ffmpeg versions).

Do you still have these timestamp problems if you leave the files as .ts files? There have been a lot of improvements in recent months in this area. If you've been doing your transcode for a while, you may not need to any more.

I'll give a .ts file a try and see what happens.

[kayfam]

Just a tip for those that may not feel comfortable digging around the registy. Create the following by opening notepad and paste this text in:

Code:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Devnz]
"RecordFullTS"=dword:00000001

Select the all files option and save as RecordFullTS.reg or you can use the attached file. Double click the .reg key and it will be set.
This is for testing purposes only and you will have to manually remove the key after creating the .TS file.

[crlorentzen]

If I roll back to psiparser from the 1.311 install all is good.

Same here, the patched psiparser causes issues, rolling back fixes the issue. It crashed config when scanning. I can attach logs, but they don't show much. Unfortunately I don't have the time to do the testing with the Microsoft tool, sorry.