Page 2 of 2

Re: Vbox Multirecord

Posted: Thu Feb 02, 2017 1:37 pm
by MikeB2013
I can test on 0.28/Fixes and master backends with an XTI 3340 (1x DVB-S,1x DVB-S2, 2x DVB-T).

I can also run more limited tests using XTI 3442 (2 x DVB-T.T2). I say limited because it is in use on my production system (master), although I can remove it for a few days as this system also has a TBS-6280 (2 x DVB-T/T2 PCI-e card) which it will fall-back to.

Mike

Re: Vbox Multirecord

Posted: Sun Feb 05, 2017 5:28 pm
by MikeB2013
@paulh

Just found a problem with my multirec patch,some mythtv services API calls are not working correctly. There will some more changes, will let you know when I have it sorted. It involves some default parameters in dtv_multiplex table, the VBOX works properly, just not services API.

Mike

Re: Vbox Multirecord

Posted: Sun Feb 12, 2017 5:11 pm
by MikeB2013
@paulh

Here is the updated patch which applies cleanly to master 245e078 bump ABI after constructor changes.
The changes fix the services API issue by giving some default values.

I have also stopped xmltvid being updated when the VBOX is rescanned in mythtv-setup, user is likely to have changed the xmltvid, so we should not overwrite it

The patch includes the temporary fix to iptvtuningdata.h (stops mythsingledownload)

Also included in the patch is a change to videosource,cpp which moves Signal and Channel timeouts to the main configuration screen, instead of Recording Options, the defaults have been increased to 7000 and 10000. I did try just changing the values in the vbox extra panel but this does not work (also affects 0.28/fixes) - there is something strange going on just selecting Recording Options causes the Capture Card to be created in the database with type V4L, defaults of 1000 and 3000 for the timeouts, the type is then immediately updated to VBOX, I suspect a reload at this point picks up the 1000 and 3000 values instead of 7000 and 10000.

The patch has been tested using two VBOXs details as follows:

Code: Select all

# VBOX INFO
VBOX XYI 3442
Dual DVB-T/2 Tuners

Board Information
Serial Number 		000000 000000 344221 644C97
Hardware Revision 		A0
Manufacture ID 		0828
Product Number 		3442
Product Name 		3442-21
Software Versions
Software Version 		XTI_VJ.2.56
Linux 		3.4.100_stm24_0309.3-rc1-B2064_h205-STSDK
Kernel Image 		VJ04
Boot Loader Image 		3.1.3
Disk Image 		IVB-2.0-25

VBOX XTI 3340
Dual DVB-T tuners, single DVB-S tuner, single DVB-S1/2 tuner

Board Information
Serial Number 		000000 000000 001637 643852
Hardware Revision 		H0
Manufacture ID 		0827
Product Number 		3345
Product Name 		3345-21
Software Versions
Software Version 		XTI_VB.2.56
Linux 		2.6.32.42_stm24_V4.0-HDK7111_7111-STSDK
Kernel Image 		VB04
Boot Loader Image 		2.1.20
Disk Image 		IVB-2.0-25 
Mike

Re: Vbox Multirecord

Posted: Sun Feb 19, 2017 11:46 am
by paulh
Thanks Mike,

I've just committed your latest patch to master more or less as is for now, just cleaned the formatting up a little in a few places.

I'll come back to it when I have more time for Myth to fix the remaining issues.

Re: Vbox Multirecord

Posted: Tue Feb 21, 2017 11:33 am
by MikeB2013
@paulh

Thanks.

Just a heads up, nothing to with the patches, but there is a channel tuning problem following commit https://github.com/MythTV/mythtv/commit ... f5d5e7cdbc

Edit:
Ticket has now been resolved, software fix has been committed to mythtv master branch
I have raised a ticket see https://code.mythtv.org/trac/ticket/13002

Re: Vbox Multirecord

Posted: Sat Apr 08, 2017 11:43 pm
by perkins1724
Is it possible / likely to have this commit (https://github.com/MythTV/mythtv/commit ... 846b7bfe4b) pushed down to fixes/0.28?

I don't have the VBOX but it looks like the workaround applied to mythtv/libs/libmythtv/recorders/iptvchannel.cpp initiated from ticket 12773 (https://code.mythtv.org/trac/ticket/12773) which is bundled together with this commit may resolve (work around) my segfault.

If it is not possible for this commit as a whole to apply to fixes/0.28 could the ticket 12773 changes be separated out and be applied individually?