Crash in psiparser.ax
|
2008-12-11, 04:55 PM
I use some tools in GB-PVR to fake the reception of your transport stream, so that I can do the scan and watch the channels here. I can then run it up in Visual Studio's debugger and analyse what happens if there is a crash.
2008-12-13, 04:03 PM
dennit Wrote:Here's the link to a 249MB full TS sample that crashes psiparser.ax. A quick question: Is psiparser.ax used during recording? I've only tried live - either through watching 1.3.7 PVRX2.exe guide or by scanning via config. Also - has anyone else tried 1.3.7 with emunation on 110 or 119 sats? I'm finding that more than 50% of the streams I test crash this way, but work fine under 1.2.13.
2008-12-13, 04:47 PM
dennit Wrote:A quick question: Is psiparser.ax used during recording?Yes, live and recording. Can you check your dont have 'Ignore PMT CRC errors always' ticked? This can certainly cause crashes in PsiParser.ax. Its in Config -> Capture Source -> Recording Source Settings -> BDA Advanced Settings.
2008-12-13, 04:53 PM
sub Wrote:Can you check your dont have 'Ignore PMT CRC errors always' ticked? This can certainly cause crashes in PsiParser.ax. Its in Config -> Capture Source -> Recording Source Settings -> BDA Advanced Settings. Yes, I do have 'Ignore PMT CRC errors always' ticked! Also 'Ignore PMT CRC errors during scan' is ticked. I take it I should uncheck both? I have no idea how or when they were checked. As far as I know, they've always been that way and I assumed they were the default whenever I looked at them. Next up - some testing - when the wife's Christmas movie ends recording!
2008-12-13, 04:56 PM
They always off by default, so you must have enabled them at some stage.
Ideally you'd have them both off, but some people have need to turning them on for a couple of reasons in the past.
2008-12-13, 06:18 PM
sub Wrote:They always off by default, so you must have enabled them at some stage. I must have turned them on for some reason that I can't recall (presumably related to my HVR1600 QAM installation). Turning these off has fixed my crashes! (The wife's recording got bumped until tonight) It's funny, but during testing to see if this fixed it, I managed to find the one channel with other problems, so of course I initially thought it was related to the 1.3.7 change. Switching back to 1.2.13 confirmed this channel has the same error. This is typical of how easily you get off track. Now, I want to use TS for multi-recording, but the playback of TS files has audio running at 1/2 speed (voices are deep and out of sync). The recorded TS files play OK in Media Player Classic. I guess I'm now off to figure this out with graphedit (unless anyone has any suggestions) Thanks for the help on the psiparser crash.
2008-12-13, 06:22 PM
Quote:Turning these off has fixed my crashes!Great. Quote:Now, I want to use TS for multi-recording, but the playback of TS files has audio running at 1/2 speed (voices are deep and out of sync). The recorded TS files play OK in Media Player ClassicMost people that have had this have resolved it by changing audio decoders, or fiddling AC3Filter settings.
2008-12-13, 07:28 PM
sub Wrote:Most people that have had this have resolved it by changing audio decoders, or fiddling AC3Filter settings. Thanks again! I had a note to myself from reading other posts that once I got 1.3.7 running, I wanted to install AC3Filter, but I hadn't done it yet. I tried searching on "slow audio" to fix my problem without success. Your post sent me to searching AC3Filter and all I needed was to install it and select it. (I set both rate and output to "no change"). I'm now off to test multi-record. |
|
|
