Capture source definitions, where?
|
2010-01-28, 11:40 PM
Where are the capture source definitions stored? Please don't say that they are in the same database as the epg and schedule....
BTW: Sub, did you read my suggestion in whishlist (http://forums.nextpvr.com/showthread.php?t=45629)? "I'd rather have a bottle in front of me than a frontal lobotomy"
2010-01-29, 12:07 AM
Reddwarf Wrote:Where are the capture source definitions stored? Please don't say that they are in the same database as the epg and schedule....Yes, they're in the gbpvr.db3 database. Quote:BTW: Sub, did you read my suggestion in whishlist (http://forums.nextpvr.com/showthread.php?t=45629)?No, I'd missed this post. Quote:Sub, is there any chance you can delay the next release until these changes are implemented?To be honest, its unlikely I could do this (at least not right not). Multidec support itself is very complicated and I'm sure this would be a large complicated project, and consume quite a bit of time. The next release is a huge release, with a large number of changes, and I've already created too much work for myself for that next release. That said, I do share the same desire for this. I have hoped to add direct multidec plugin support for quite a while now. Its just a matter of finding the time...
2010-01-29, 02:44 AM
Would it imply a lot of work to move the capture source definitions out of the gbpvr.db3? Because if it were in another base (or file) two (or more) computers could share the gbpvr.db3 base but still have their own capture sources, ie. one would be able to run "clients" with their own capture cards, recording to the same destination and sharing the schedule and epg. True distributed recording, in other words.
"I'd rather have a bottle in front of me than a frontal lobotomy"
2010-01-29, 02:57 AM
Sorry, that would also be a huge amount of work, so unlikely to happen. There is tons of code that relies on this data, and lots of relationships in the database which depend on the capture source, so its not easy to remove from the database. There is also lots of third party plugins and utilities that look at this data in the database.
2010-01-29, 11:11 AM
sub Wrote:Sorry, that would also be a huge amount of work, so unlikely to happen. There is tons of code that relies on this data, and lots of relationships in the database which depend on the capture source, so its not easy to remove from the database. There is also lots of third party plugins and utilities that look at this data in the database. So we have to rely on DVBLogic TVSource 2.0 for the time being? That works but makes it unnecessary complicated :p
[SIZE="1"]LianLi V600, Intel DG965WH, 4Gb, Core2Quad Q6600, 5x 1TB, 3x 500GB raid1, 3x TechnoTrend C-1501 dvb-c, 2x PCH A-100/A-110, WHS, NPVR, DVBLink
LianLi PC-V351, Intel DG45ID, 4Gb, Core2Duo E8400, 1x 1TB + 2x 500GB, TT C-1501 dvb-c, Win7 Ultimate, W2K8R2 Server, WHS2 Vail, XP Pro, Mandriva Linux Laptops: Acer 1810TZ, Acer 5235, Dell D610, Win7, Mandriva Linux, Hackintosh Fritz!Box 7270 WLAN-N/Dect modem/router, Netgear GS116 Gbit switch, Linksys 5 ports Gbit switch[/SIZE]
2010-01-29, 12:34 PM
What are the major changes/improvments of the new release?
"I'd rather have a bottle in front of me than a frontal lobotomy" |
|
|
