View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 15 posts ] 
Print view Previous topic   Next topic  
Author Message
Search for:
PostPosted: Sat Dec 01, 2018 8:51 am 
Offline
Joined: Sat Sep 16, 2006 4:09 pm
Posts: 48
I've been trying linhes 8.5 for about a year with both a hauppauge 950q and an 850. They both have the same chipset so mythtv should think they're identical.

I get a failed recording about once a week though and I've been taking another shot at trying to solve that. I've seen something about a "950q usb quirk defect" in the 4.9 kernel.https://lwn.net/Articles/727671/ but it looks like that was fixed in kernel 4.9.37.

Is anybody getting reliable results with linhes 8.5 and hauppauge 950q tuners?


Top
 Profile  
 
PostPosted: Tue Feb 05, 2019 10:52 am 
Offline
Joined: Tue Aug 08, 2006 7:08 pm
Posts: 557
Location: UK
I don't know about the quirk, but is there any pattern to the problem, like particular channel(s) or a particular mux (transport) that they fail on?
It may sound like the bleedn' obvious, but is your LH box being hit with a particular heavy task at the same time?

I've had the occasional zero byte recording when using the ability to record off of the same mux, and the recordings are set to start at the same time. One will start, the other has a recording fail, if you catch it early enough the recording can be restarted.
In the settings for the card under Recording Options (in the backend setup program), there should be some options (I don't know for LH8.5 but it was there for earlier versions):

Code:
Recording Options
Max Recordings: 2
Wait for SEQ Start Header: Yes
Open DVB Card On Demand: Yes
Use DVB Card for active EIT scan: Yes
DVB Tuning Delay (msec): 700


So you might try fiddling around with these, also you might try altering the Signal Timeout and Tuning Timeout settings as well

Bruce S.

_________________
Updated 2019/01/31: AthlonII X2 265 Asus M5A78L-M LE
2Gb PC 1333 DDR3, 1TB+2TB SATA HDD,
SATA DVD-RW TSSTcorp SH-224DB , Onboard Radion HD3000
Hauppauage Nova-T 500, Nova-T LinHes R7.1


Top
 Profile  
 
PostPosted: Wed Feb 27, 2019 4:52 pm 
Offline
Joined: Sat Sep 16, 2006 4:09 pm
Posts: 48
Thanks for the reply. Unfortunately I can't find any pattern tied to a particular pattern or mux. Nothing obvious from the backend logs going on during the failure either.

It happens about once every couple weeks, with the longest time without a failure being a little over 3 weeks. The failure have all been with only 1 tuner attempting to record.

I have two physical tuners, a hauppauge 950q and a 850. They're both setup for a max of two recording each.

I definitely tried messing with the wait for seq start header as well as open dvb card on demand. Didn't seem to affect the failure rate.

I have Use DVB Card for active EIT scan off, since I get guide info from Schedules Direct.

I cranked up the tuning and scan times to 20,000.

Really not sure how to gauge how reliable this thing should be. Bugs me that there is never any root cause for the for the failures.


Top
 Profile  
 
PostPosted: Thu Feb 28, 2019 11:12 am 
Offline
Joined: Sat Jan 06, 2007 7:08 pm
Posts: 80
I've been watching your post as I have been curious about zero length recordings. i also had a zero length files issue, which i ultimately resolved. Unfortunately, I have a suspicion that my solution may not apply to your scenario. As you haven't found a solution as of yet, I'll offer my experience.

i use over the air ATSC

To make a long story short, I eventually noticed that while i had great ATSC signal level, "signal quality", and "symbol quality" (using HDHomeRun vernacular and tools) were bad. i had a strong, but noisy signal with a high bit error rate. Apparently, on occasion, if the tuner couldn't lock onto the signal when the recording was starting, a zero length file would result.

Once i cleaned up the signal, the zero length file issue was resolved. However, in my case, I knew i had reception problems, as it was obvious from viewing live tv or other recordings.

I didn't have any success with changing the various timeout settings

_________________
DH87MC i7-4770 16GB ram Xonar Essence ST geforce 710 LinHes 8.6


Top
 Profile  
 
PostPosted: Thu Feb 28, 2019 5:44 pm 
Offline
Joined: Sat Sep 16, 2006 4:09 pm
Posts: 48
Thanks for the reply. I've been suspicious of a signal quality issue too. I just never see any problem with live tv. Maybe there is some intermittent signal problem. I'm using ATSC as well. How did you clean up your signal?


Top
 Profile  
 
PostPosted: Thu Feb 28, 2019 6:53 pm 
Offline
Joined: Sat Jan 06, 2007 7:08 pm
Posts: 80
In my case, I live 2 miles from the main broadcast towers, so i have lots of signal. Unfortunately, due to obstructions and house layout, i need to locate an antenna at the opposite end of the house, using about a 45 foot run.

this setup worked for a while, but started to degrade over time as the frequency of the zero length file issue increased. if it were to rain, i could predict that the issue would occur.

i had multiple issues with the 45 foot run. i had used old, questionable coax. also, i was using signal amplifiers when i should not have been. i had been using the amps to compensate for the signal loss due to the long run of poor coax. unfortunately, the amps just made the signal noisier, resulting in reception errors.

i first replaced the old coax with some quality coax and removed the amps. this fixed the issue perhaps 90%, but i was still getting zero length files.

using signal measuring tools, i could see that the errors were minimal when connected at the antenna, but greater at the end of the 45 foot run.

in the end just did away with the long run by retiring the pci tuner cards in my mythtv, and purchasing a HDHomeRun device. i located the HDHomeRun device right next to the antenna to maximize the signal. i have not had a zero length recording since

you may wish to monitor your signal quality. hauppauge must have some diagnostic tools, and there is a keystroke that can be used to display the signal quality and signal errors in mythtv. what that keystroke is escapes me at the moment.

even after i cleaned up the signal with the HDHomeRun solution as best as i could, when monitoring multiple channels all broadcasting from the same tower cluster, i still see sporadic dips in signal and symbol quality that can be seen as artifacts on screen. but, its as good as its going to get, and there are no zero length files

the lesson i learned in the end was to make sure the signal and symbol quality was good, and not to worry about maximizing signal strength.

_________________
DH87MC i7-4770 16GB ram Xonar Essence ST geforce 710 LinHes 8.6


Top
 Profile  
 
PostPosted: Mon Mar 04, 2019 5:08 pm 
Offline
Joined: Sat Sep 16, 2006 4:09 pm
Posts: 48
Thanks for the suggestions. I did try the Hauppauge signal quality monitoring, but I never saw any errors. Couldn't find a way to let it monitor for a day or so. Maybe I should try that in case there are just intermittent quality issues and nothing I can catch when I go looking.


Top
 Profile  
 
PostPosted: Mon Mar 04, 2019 11:03 pm 
Offline
Joined: Tue Aug 15, 2006 11:14 am
Posts: 1281
Location: Orlando FL
there was an awesome android app for monitoring signal strength from you phone. Sadly it was third party and it has left the Play store. I had to back up the app from my old phone and load it onto my new phone. It was called "Hdhomerun Signal Meter". It was handy for tuning my antenna in the attic. I too have some dropouts with OTA and have thought about moving my HDHR closer to the antenna.

_________________
My System


Top
 Profile  
 
PostPosted: Tue Mar 05, 2019 6:11 am 
Offline
Joined: Sat Jan 06, 2007 7:08 pm
Posts: 80
nlin1996,

as a reminder, my reception problems were obvious, so that is why i first targeted this as a likely cause. if you aren't seeing reception issues, then the possibility that this is the cause of your symptoms is decreased.

i am assuming you are using the "digital signal monitor" as described here

Code:
http://www.hauppauge.com/pages/support/support_digital_signal_monitor.html


the section entitled "Using the Signal Monitor to adjust a digital TV antenna" addresses the need to minimize the errors more concisely than i can write.

when i was gathering signal quality data, i used a command line tool from HDHomeRun to gather data continuously. it is unclear if hauppauge provides such a tool. it appears there may be such a tool on sourceforge, or the vl4 tools may work

_________________
DH87MC i7-4770 16GB ram Xonar Essence ST geforce 710 LinHes 8.6


Top
 Profile  
 
PostPosted: Wed Mar 06, 2019 5:05 pm 
Offline
Joined: Sat Sep 16, 2006 4:09 pm
Posts: 48
Yep, that was the tool I used. I could never get any error count besides zero. I did just catch some pixilation watching live tv though. Came and went, didn't seem to last more than couple minutes. Hard to conclude something intermittent like that happens right at the time I'm trying to record something. Not very likely...


Top
 Profile  
 
PostPosted: Sat Mar 09, 2019 8:26 pm 
Offline
Joined: Tue Aug 15, 2006 11:14 am
Posts: 1281
Location: Orlando FL
it might be completely off topic..... but...... the channels I have the most problem with drop-outs on are high bandwidth shows. Such as full 1080 surround sound yadda yadda and the all the signal meters in the world give me great signal at 11:00 pm when it's low bandwidth show on but stuff like the Oscars has drop outs. Does this match your experience at all?

_________________
My System


Top
 Profile  
 
PostPosted: Sat Mar 09, 2019 10:00 pm 
Offline
Joined: Sat Sep 16, 2006 4:09 pm
Posts: 48
No, doesn't seem to matter if it's HD or SD for me. i haven't been able to find any pattern at all, just completely random, which is not giving much clue to narrow it down.


Top
 Profile  
 
PostPosted: Sat Apr 06, 2019 6:53 pm 
Offline
Joined: Sat Sep 16, 2006 4:09 pm
Posts: 48
Thought I'd see if anyone knows how the signal monitor works. I noticed that when my recordings fail, I never get SetTVCT or SetProgramNumber in the backend.log:

2019-04-06T09:30:01.117848-05:00 mythbackend[16036]: I TVRecEvent recorders/dtvsignalmonitor.cpp:206 (SetChannel) DTVSigMon[1](/dev/dvb/adapter_static_dvb_1/frontend0)::SetChannel(19, 3):
2019-04-06T09:30:01.118168-05:00 mythbackend[16036]: I TVRecEvent tv_rec.cpp:1943 (SetupDTVSignalMonitor) TVRec[1]: Successfully set up ATSC table monitoring.
2019-04-06T09:30:01.118417-05:00 mythbackend[16036]: I TVRecEvent tv_rec.cpp:4446 (SetFlags) TVRec[1]: SetFlags(SignalMonitorRunning,) -> RunMainLoop,SignalMonitorRunning,RingBufferReady, @ tv_rec.cpp:3846
2019-04-06T09:30:01.118660-05:00 mythbackend[16036]: I TVRecEvent tv_rec.cpp:4455 (ClearFlags) TVRec[1]: ClearFlags(WaitingForSignal,) -> RunMainLoop,SignalMonitorRunning,RingBufferReady, @ tv_rec.cpp:3847
2019-04-06T09:30:01.118897-05:00 mythbackend[16036]: I TVRecEvent tv_rec.cpp:4446 (SetFlags) TVRec[1]: SetFlags(WaitingForSignal,) -> RunMainLoop,WaitingForSignal,SignalMonitorRunning,RingBufferReady, @ tv_rec.cpp:3852
2019-04-06T09:30:01.119127-05:00 mythbackend[16036]: I TVRecEvent tv_rec.cpp:4455 (ClearFlags) TVRec[1]: ClearFlags(NeedToStartRecorder,) -> RunMainLoop,WaitingForSignal,SignalMonitorRunning,RingBufferReady, @ tv_rec.cpp:3913
2019-04-06T09:30:01.119352-05:00 mythbackend[16036]: I TVRecEvent tv_rec.cpp:4446 (SetFlags) TVRec[1]: SetFlags(NeedToStartRecorder,) -> RunMainLoop,WaitingForSignal,NeedToStartRecorder,SignalMonitorRunning,RingBufferReady, @ tv_rec.cpp:3915
2019-04-06T09:30:01.119574-05:00 mythbackend[16036]: I TVRecEvent tv_rec.cpp:4033 (TuningSignalCheck) TVRec[1]: TuningSignalCheck: Still waiting. Will timeout @ 09:59:50.000
2019-04-06T09:30:01.119829-05:00 mythbackend[16036]: I Scheduler scheduler.cpp:2936 (HandleRecordingStatusChange) Tuning recording: "The Pink Panther Show":"Pink Quackers": channel 1193 on cardid [1], sourceid 1
2019-04-06T09:30:01.120247-05:00 mythbackend[16036]: I Scheduler scheduler.cpp:2356 (HandleReschedule) Reschedule requested for CHECK -3 32 0 UpdateRecStatus2 | The Henry Ford's Innovation Nation | Speed Reading App | An app that helps increase reading speed; tape that helps athletes stay on the playing field; a phone case with pop-out legs protects against falls; microwave ovens. | EP019919100123
2019-04-06T09:30:01.120558-05:00 mythbackend[16036]: I SignalMonitor recorders/dvbsignalmonitor.cpp:302 (UpdateValues) DVBSigMon[1](/dev/dvb/adapter_static_dvb_1/frontend0): UpdateValues -- Signal Locked
2019-04-06T09:30:01.120795-05:00 mythbackend[16036]: I SignalMonitor recorders/streamhandler.cpp:57 (AddListener) SH[1](/dev/dvb/adapter_static_dvb_1/frontend0): AddListener(0x7ff9b4331358) -- begin
2019-04-06T09:30:01.121025-05:00 mythbackend[16036]: I SignalMonitor recorders/streamhandler.cpp:69 (AddListener) SH[1](/dev/dvb/adapter_static_dvb_1/frontend0): AddListener(0x7ff9b4331358) -- locked
2019-04-06T09:30:01.214889-05:00 mythbackend[16036]: I SignalMonitor recorders/streamhandler.cpp:91 (AddListener) SH[1](/dev/dvb/adapter_static_dvb_1/frontend0): AddListener(0x7ff9b4331358) -- end


When I have a good recording they happen right after what I pasted above:


2019-04-06T09:00:00.831183-05:00 mythbackend[16036]: I TVRecEvent recorders/dtvsignalmonitor.cpp:206 (SetChannel) DTVSigMon[1](/dev/dvb/adapter_static_dvb_1/frontend0)::SetChannel(8, 1):
2019-04-06T09:00:00.831533-05:00 mythbackend[16036]: I TVRecEvent tv_rec.cpp:1943 (SetupDTVSignalMonitor) TVRec[1]: Successfully set up ATSC table monitoring.
2019-04-06T09:00:00.831924-05:00 mythbackend[16036]: I TVRecEvent tv_rec.cpp:4446 (SetFlags) TVRec[1]: SetFlags(SignalMonitorRunning,) -> RunMainLoop,SignalMonitorRunning,RingBufferReady, @ tv_rec.cpp:3846
2019-04-06T09:00:00.832765-05:00 mythbackend[16036]: I TVRecEvent tv_rec.cpp:4455 (ClearFlags) TVRec[1]: ClearFlags(WaitingForSignal,) -> RunMainLoop,SignalMonitorRunning,RingBufferReady, @ tv_rec.cpp:3847
2019-04-06T09:00:00.833207-05:00 mythbackend[16036]: I TVRecEvent tv_rec.cpp:4446 (SetFlags) TVRec[1]: SetFlags(WaitingForSignal,) -> RunMainLoop,WaitingForSignal,SignalMonitorRunning,RingBufferReady, @ tv_rec.cpp:3852
2019-04-06T09:00:00.833480-05:00 mythbackend[16036]: I TVRecEvent tv_rec.cpp:4455 (ClearFlags) TVRec[1]: ClearFlags(NeedToStartRecorder,) -> RunMainLoop,WaitingForSignal,SignalMonitorRunning,RingBufferReady, @ tv_rec.cpp:3913
2019-04-06T09:00:00.833719-05:00 mythbackend[16036]: I TVRecEvent tv_rec.cpp:4446 (SetFlags) TVRec[1]: SetFlags(NeedToStartRecorder,) -> RunMainLoop,WaitingForSignal,NeedToStartRecorder,SignalMonitorRunning,RingBufferReady, @ tv_rec.cpp:3915
2019-04-06T09:00:00.833948-05:00 mythbackend[16036]: I TVRecEvent tv_rec.cpp:4033 (TuningSignalCheck) TVRec[1]: TuningSignalCheck: Still waiting. Will timeout @ 09:29:50.000
2019-04-06T09:00:00.834178-05:00 mythbackend[16036]: I Scheduler scheduler.cpp:2936 (HandleRecordingStatusChange) Tuning recording: "The Henry Ford's Innovation Nation":"Speed Reading App": channel 1081 on cardid [1], sourceid 1
2019-04-06T09:00:00.834409-05:00 mythbackend[16036]: I SignalMonitor recorders/dvbsignalmonitor.cpp:302 (UpdateValues) DVBSigMon[1](/dev/dvb/adapter_static_dvb_1/frontend0): UpdateValues -- Signal Locked
2019-04-06T09:00:00.834635-05:00 mythbackend[16036]: I SignalMonitor recorders/streamhandler.cpp:57 (AddListener) SH[1](/dev/dvb/adapter_static_dvb_1/frontend0): AddListener(0x7ff9b4331358) -- begin
2019-04-06T09:00:00.834879-05:00 mythbackend[16036]: I SignalMonitor recorders/streamhandler.cpp:69 (AddListener) SH[1](/dev/dvb/adapter_static_dvb_1/frontend0): AddListener(0x7ff9b4331358) -- locked
2019-04-06T09:00:00.927323-05:00 mythbackend[16036]: I SignalMonitor recorders/streamhandler.cpp:91 (AddListener) SH[1](/dev/dvb/adapter_static_dvb_1/frontend0): AddListener(0x7ff9b4331358) -- end
2019-04-06T09:00:01.028342-05:00 mythbackend[16036]: I DVBRead recorders/dtvsignalmonitor.cpp:449 (HandleTVCT) DTVSigMon[1](/dev/dvb/adapter_static_dvb_1/frontend0)::SetVCT(): tvct->ProgramNumber(idx 0): prog num 1
2019-04-06T09:00:01.028889-05:00 mythbackend[16036]: I DVBRead recorders/dtvsignalmonitor.cpp:223 (SetProgramNumber) DTVSigMon[1](/dev/dvb/adapter_static_dvb_1/frontend0)::SetProgramNumber(1):
2019-04-06T09:00:01.029269-05:00 mythbackend[16036]: I DVBRead mpeg/mpegstreamdata.cpp:93 (SetDesiredProgram) MPEGStream[1](0x7ff9b4331358): SetDesiredProgram(1)

Anybody know what could prevent the dtvsignalmonitor code from ever getting to HandleTVCT or SetProgramNumber?


Top
 Profile  
 
PostPosted: Fri Apr 19, 2019 3:22 pm 
Offline
Joined: Sat Sep 16, 2006 4:09 pm
Posts: 48
Starting to follow this a little further. Looks like the problem is in mpegtables.cpp. When recordings fail, the code never makes it to ProgramMapTable::Create(). That's the method that prints out the "Created PMT" below. ANybody know the code for this?

2019-04-19T03:00:00.834817-05:00 mythbackend[5646]: I SignalMonitor recorders/streamhandler.cpp:91 (AddListener) SH[1](/dev/dvb/adapter_static_dvb_2/frontend0): AddListener(0x7f305c04cc10) -- end
2019-04-19T03:00:00.936355-05:00 mythbackend[5646]: I DVBRead mpeg/mpegtables.cpp:464 (Create) Created PMT #012Program Map Section#012 PSIP tableID(0x2) length(117) extension(0x1)#012 version(12) current(1) section(0) last_section(0)#012 pnum(1) pid(0x30) pcrpid(31)#012 Registration Descriptor: 'GA94' ATSC program ID A/53#012 Content Advisory, Possibly Dishnet Rights Descriptor (0x87) length(19). Dumping#012 000 c1 01 01 00 f4 0d 01 65 6e 67 01 00 00 05 54 56 |.......eng....TV|#012 010 2d 31 34 |-14|#012 Stream #0 pid(0x31) type(0x02 video-mpeg2)#012 STD Descriptor (0x11) length(1). Dumping#012 000 ff |.|#012 Smooting Buffer Descriptor (0x10) length(6). Dumping#012 000 c0 bd 62 c0 08 00 |..b...|#012 Data Stream Alignment Descriptor (0x06) length(1). Dumping#012 000 02 |.|#012 Stream #1 pid(0x34) type(0x81 audio-ac3)#012 Registration Descriptor: 'AC-3' ATSC audio stream A/52#012 Audio Stream Descriptor full_srv(1) sample_rate(48kbps) bit_rate(=448kbps, 15)#012 bsid(8) bs_mode(0) channels(3/2) Dolby(Not indicated)#012 mainID(0) #012 ISO-639 Language: code(eng) canonical(eng) eng(English)#012 Stream #2 pid(0x35) type(0x81 audio-ac3)#012 Registration Descriptor: 'AC-3' ATSC audio stream A/52#012 Audio Stream Descriptor full_srv(1) sample_rate(48kbps) bit_rate(=384kbps, 14)#012 bsid(8) bs_mode(2) channels(3/2) Dolby(Not indicated)#012 associated_service(0x0) #012 ISO-639 Language: code(spa) canonical(spa) eng(Spanish; Castilian)
2019-04-19T03:00:00.937042-05:00 mythbackend[5646]: I TVRecEvent tv_rec.cpp:3941 (TuningSignalCheck) TVRec[1]: TuningSignalCheck: Good signal
2019-04-19T03:00:00.937456-05:00 mythbackend[5646]: I TVRecEvent tv_rec.cpp:730 (SetRecordingStatus) TVRec[1]: SetRecordingStatus(Tuning->Recording) on line 4039
2019-04-19T03:00:00.937802-05:00 mythbackend[5646]: I TVRecEvent tv_rec.cpp:2126 (TeardownSignalMonitor) TVRec[1]: TeardownSignalMonitor() -- begin
2019-04-19T03:00:00.938175-05:00 mythbackend[5646]: I TVRecEvent recorders/dvbsignalmonitor.cpp:152 (Stop) DVBSigMon[1](/dev/dvb/adapter_static_dvb_2/frontend0): Stop() -- begin
2019-04-19T03:00:00.938553-05:00 mythbackend[5646]: I CoreContext scheduler.cpp:729 (UpdateRecStatus) Updating status for "The Simpsons":"The Great Phatsby: Vol. II" on cardid [1] (Tuning => Recording)
2019-04-19T03:00:00.938907-05:00 mythbackend[5646]: I TVRecEvent recorders/streamhandler.cpp:99 (RemoveListener) SH[1](/dev/dvb/adapter_static_dvb_2/frontend0): RemoveListener(0x7f305c04cc10) -- begin
2019-04-19T03:00:00.939243-05:00 mythbackend[5646]: I TVRecEvent recorders/streamhandler.cpp:111 (RemoveListener) SH[1](/dev/dvb/adapter_static_dvb_2/frontend0): RemoveListener(0x7f305c04cc10) -- locked
2019-04-19T03:00:01.038417-05:00 mythbackend[5646]: I TVRecEvent recorders/streamhandler.cpp:128 (RemoveListener) SH[1](/dev/dvb/adapter_static_dvb_2/frontend0): RemoveListener(0x7f305c04cc10) -- end
2019-04-19T03:00:01.038941-05:00 mythbackend[5646]: I TVRecEvent recorders/dvbsignalmonitor.cpp:158 (Stop) DVBSigMon[1](/dev/dvb/adapter_static_dvb_2/frontend0): Stop() -- end
2019-04-19T03:00:01.039299-05:00 mythbackend[5646]: I TVRecEvent recorders/dvbstreamhandler.cpp:85 (Return) dVBSH[1]: Closing handler for /dev/dvb/adapter_static_dvb_2/frontend0


Top
 Profile  
 
PostPosted: Thu Apr 25, 2019 1:20 am 
Offline
Joined: Mon Apr 23, 2007 1:45 pm
Posts: 398
Location: Fargo, ND, USA
Go to
>Service Menu>Mythtv Settings>Setup>Video>General>General Auto Expire>Extra Disk Space
Change default 1 GB to 15 GB

>Service Menu>Mythtv Settings>Setup>Video>General>General Auto Expire>Time to Retain Deleted Recordings in (days)
Note if Default 1 Day has been changed

If it works post back to me
1. Extra Disk Space setting (GB before change)
2. Time to Retain Deleted Recordings in (days)
3. Size of hard drive
4. Hard drive space available listed on the main (home)screen
5. Type of RAM and how much
and I will speculate what may be happening.

_________________
TVBox
LinHES R8.6.1


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 15 posts ] 


All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 3 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu