0kb recordings

[sub]

One you problems stems from you having configured your PVR250 as a PVR150. Check the card type in the config app.

[Cosworth]

One you problems stems from you having configured your PVR250 as a PVR150. Check the card type in the config app.

50% of the problem solved already!!

This happened when I had to change the order of the capture cards (to set the capture preference) and deleted the old capture settings for the PVR-250.

This reduces the problem to a normal BDA 0kb one. Seeing as 0kb really can mean "wrong settings" somewhere along the line I guess each filter in the graph should be checked.

I had to define the BDA.ini settings myself like this:

Code:

[TerraTec Cinergy 1200 DVB-C] TUNING_TYPE=DVB-C FILTER_TUNER=Cinergy 1200 DVB-C Tuner (BDA) FILTER_CAPTURE=Cinergy 1200 DVB-C Capture (BDA) PIN_TUNER_IN=Input0 PIN_TUNER_OUT=MPEG2 Transport PIN_CAPTURE_IN=MPEG2 Transport PIN_CAPTURE_OUT=MPEG2 Transport

Seems ok and live tv is working.

Next step would be to find out why the card doesn't lock to the station - Or at least reports that. I'm just not sure where to look for clues....

Edit: Noticed that the capture preference has changed back to the PVR 250 as being the first capture device, even though it's listed underneath the BDA device in the config screen. Wasn't that supposed to be the way to set the preference?

[sub]

Your zero byte recording on the DVB-C device is probably caused by you mux filter. Do a recording, then zip and attach your GB-PVR Recording Service.exe.log and GBPVRRecordingService.exe-native.log and I'll take a look.

It'll look for available captures sources from the top of the list down. The rules change slightly for back to back recordings.

[Cosworth]

Here they are. Scheduled a recording for this morning at 0700. It failed like before.

Setting the misc-BDA multiplexer to transport stream crashes GB-PVR with this message in the log:

Code:

09-01-2006 17:20:48.065 VERBOSE [35] Changing to channel (GBPVR.Backend.Common.NullTunerController): 37 09-01-2006 17:20:48.065 VERBOSE [35] Requesting IRecordingSource to start recording: F:\Video\TV\Droopy i Alaska_20060109_17201730.mpg 09-01-2006 17:20:48.080 VERBOSE [35] BDARecordingSource about to start recording oid:4 channel:T:C,578000,6875,QAM64,8~P:440~V:440~A:441~L:000~PMT:32~TXT:442~N:>DR1_43 09-01-2006 17:21:01.552 ERROR [35] Error starting recording: Object reference not set to an instance of an object. 09-01-2006 17:21:01.567 ERROR [35] Error starting recording: at NativeUtilities.BDARecorder.StartRecording(String cardType, Int32 board, String filename, IntPtr hwnd, String tuningRequest, Int32 lnbLOF1, Int32 lnbSwitch, Int32 lnbLOF2, Int32 diseqc, Boolean powered, Boolean previewMode) at NativeUtilities.BDARecorder.StartRecording(String cardType, Int32 board, String filename, IntPtr hwnd, String tuningRequest, Int32 lnbLOF1, Int32 lnbSwitch, Int32 lnbLOF2, Int32 diseqc, Boolean powered) at GBPVR.Backend.Common.BDARecordingSource.startRecording(IRecordingSourceConfiguration xa7c7ceed38e3bee4, Int32 x16b01fbd4b998cfc, String x8b1d9e3189e6e73d, ChannelTuning x14c8abe66009b164, Int32 xeef1d8e9d81064fa, Boolean x3a83f6e9e3779d99) at GBPVR.RecordingService.RecordingManager.WorkerThread() 09-01-2006 17:21:01.771 VERBOSE [35] RecordingStatus is now RecordingStatus.RECORDING_IN_PROGRESS 09-01-2006 17:21:01.787 VERBOSE [35] RecordingFactory.save() 09-01-2006 17:21:01.787 VERBOSE [35] Save(): Updated existing scheduled recording

DVR-MS yields a 6kb file.

So none of the multiplexors available gives a change to the lock problem.

I noticed that compared to live preview I don't see an actual tuning request in the logs, but that may mean nothing. The function
SetTuningRequest(T:C,538000,6875,QAM64,8~P:1860~V:480~A:481~L:000~PMT:35~TXT:482~N:>TV2)
Is only called in live preview mode.

[the_it_bloke]

I have the zero file length issue too.

I have a new Hauppauge 1300 (non MCE) using the latest drivers from the Hauppauge website. I have the latest gbpvr software and a brand new build. I dont have access issues with the HDD (or I wouldnt have been able to get even a 0MB file) and dont have a HDD space issue.
I have tried;

InterVideo Multiplexer
FILE: C:\Program Files\InterVideo\Common\Bin\Ivimux.ax
VERSION: 3.0.22.0

CyberLink MPEG Muxer
FILE: C:\WINDOWS\system32\MpgMux.ax
VERSION: 5.0.0727

and the DVR-MS mux

If i set up a number of recordings (sequential or not) I get the first recording ok and the rest are 0MB. If during a failed recording, I restart the recording services from the tray icon, a new file is created and the recording starts correctly. The next recording will always fail....

Love the product, but really boored with this. Wife is close to murder....

Help?

[sub]

I've had a couple of HVR owners report similar things recently. I'm not sure why it is behaving differently that other devices, but you could try the patch from http://forums.nextpvr.com/showthread.php?t=17820. Even though its talking about live tv, it seems to have solved a recording problem for another couple of users, much like the one you describe.

[the_it_bloke]

Hi Sub

Thank you for the very fast response, particularly on a Sunday evening!

I have applied the replacement DLL and early testing indicate that I am now consistently recording, at least with manual recording settings.

Fingers crossed and thanks again for a top product.

[sub]

Thank you for the very fast response, particularly on a Sunday evening!

Monday morning here.

[the_it_bloke]

Hey sub, where in the world are you? obviously East os me!

Tried the patch, it seemed to record manual recordings ok, but when I started using the EPG it has become intermittent, it may record each of a sequence of programs or just return a 0mb file randomly.
During a failed recording I attempted to watch Live TV and kept getting a message like "the device is actively refusing a connection".

Restarting the recording services still starts a new correct recording, but the whole thing is very intermittent now, rather than not working.

Have downloaded and installed the CyberLink MPEG Muxer V 5.0.2022 and removed the older version (V 5.0.0727 I think).

Just set up 4 recordings from EPG and they all seem to have recorded!
Have left it with a schedule of recordings today, if it remains stable I will report back.

[the_it_bloke]

Finally a fully working PVR

So to recap:
Windows XP SP2 All patches installed
2GHz AMD-MSI MoBo-512MB RAM-80GB ATA100 HDD-ATI AGP Graphics
Hauppauge HVR-1300 Card (only set up for DVB by choice)
Latest GB-PVR Release
GB-PVR Patch as recommended by SUB for HVR-1300
CyberLink MPEG Muxer V 5.0.2022

10 successful recordings later, not saying it's purfect, but it's never managed that before! Can't stop smiling. Even wife has forgiven me

Processor running between 2% and 7% when recording and not watching TV