2005-04-14, 11:05 PM
so no ideas on why the scheduling doesn't update? i mena the timing apears to be right it makes the folder about 30sec before it should be recording
2005-04-14, 11:05 PM
so no ideas on why the scheduling doesn't update? i mena the timing apears to be right it makes the folder about 30sec before it should be recording
2005-04-15, 12:26 AM
i tried un installing and getting rid of the folder aswell but nothing helps i vcant even get video but does that card in my previous post look like it will work?
AMD 64 3200+ Winchester, DFI Lanparty Ultra D
EVGA 7800 256,2 GiG PC 3500, 1 WD SATA 36 GiG, 1 WD 250 GiG, WinTv PVR 150 , Dell 2005FPW LCD
2005-04-15, 12:31 AM
does the fact that the database can't automaticly compress matter i just noticed that in the log file
2005-04-15, 10:59 AM
contra: not nativly with gb-pvr, it might work with the software recorder, but i can't really say as there's been no testing with that card.
2005-04-15, 11:00 AM
conta: if you want a card that will work out of the box with gb-pvr then get one of the cards listed on the gb-pvr home page. Basically you're looking for a card that supports Hardware based MPEG compression.
2005-04-15, 04:01 PM
k thanks
AMD 64 3200+ Winchester, DFI Lanparty Ultra D
EVGA 7800 256,2 GiG PC 3500, 1 WD SATA 36 GiG, 1 WD 250 GiG, WinTv PVR 150 , Dell 2005FPW LCD
2005-04-17, 09:50 PM
Well, I managed to pick up a WinTV-GO for dirt cheap last week, so I decided to see if I could get a little dual-tuner action with GBPVR to tide me over until I can afford a PVR-500.
Accidentally screwing up my Windows partition has forced me to re-install from scratch, so I've decided to take this opportunity to retire my PVR-250 a bit in order to play with my new old WinTV-GO and to perhaps help out this software recorder project a bit. Anyways, LiveTV works great with sound and video and everything, but the moment I try to record or timeshift, I get a Could not connect to the recording device error (paraphrasing, not in front of my HTPC right now). Wondering what log files to post. Running a WinTV-GO (by itself for now) with an 878 chipset using the latest BTWincap drivers and the Moonlight MPEG-2 Encoders on the system in my signature.
GB-PVR v1.1.5, 1x Hauppauge PVR-150 (v.2.0.48.25037), 2x Hauppuage PVR-500MCE (v.2.0.48.25037), Athlon XP 2500+@3200+, 1GB DDR RAM, Diamond AMD Radeon HD2600 Pro 512MB DDR2 AGP (v7.7), NVIDIA nforce2 Ultra 400 Chipset (v5.10), Chaintech AV-710 (v500b), Windows XP Home w/SP2, Microsoft .NET 2.0, DirectX 9.0c (Aug '07), NVIDIA PureVideo decoders (v.1.02-223), SchedulesDirect, Dell 2405FPW; DVI
My DVD Collection
2005-04-17, 10:14 PM
make sure you've restarted the recording service, then attempt to record or timeshift, then just post the files that have been updated since you re-started the service. (i assume you did install the moonlight encoder pack - you must have it or you can't record)
2005-04-17, 11:03 PM
Yup, I've got that encoder pack.
Anyways, here are my log files. I think I got all the relevant ones, but if there's any missing, I'll post them too. Since I've got nothing mission critical to record for the next few days and I've still got to rebuild my system to before when it crashed, I'm happy to be a guinea pig for a while.
GB-PVR v1.1.5, 1x Hauppauge PVR-150 (v.2.0.48.25037), 2x Hauppuage PVR-500MCE (v.2.0.48.25037), Athlon XP 2500+@3200+, 1GB DDR RAM, Diamond AMD Radeon HD2600 Pro 512MB DDR2 AGP (v7.7), NVIDIA nforce2 Ultra 400 Chipset (v5.10), Chaintech AV-710 (v500b), Windows XP Home w/SP2, Microsoft .NET 2.0, DirectX 9.0c (Aug '07), NVIDIA PureVideo decoders (v.1.02-223), SchedulesDirect, Dell 2405FPW; DVI
My DVD Collection
2005-04-18, 08:31 AM
there are two bugs, the one should have been fixed in 0.14, but looks like it's still there. (it's picking the wrong mixer to mute/unmute).
I'm guessing the other error: 'Horizontal size is greater than permitted in specified Level' is because the default size of your WinTV-GO is larger than the Moonlight encoder will support. Can you check what size this is using GraphEdit (search the forum for a link to d/l). If you could also manually hook things up in GraphEdit to play with sizes etc, that would help confirm that this is the problem, and that changing the size makes it work. |
|