Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[rpalmer68]

I have had a couple of recording failures this week.

Both times the kids have been watching a TV recording on the server and have received a number of popup errors telling them the recording has failed due to timeout.

If I look at the Tv status the tuner will have "error" status and the next tuner is being attempted.  After all the tuners are tried then the recording finally fails.

Once the kids had finished watching their recording I tried to play live TV on the same tuners and everything worked fine, so I know the tuners are OK and there is signal.

So I'm not sure what is going on, but  it seems that if something is being watched at the same time that a recording is scheuled a recording can fail.

I've had no failures at any other time, just when there happened to be something being watched.

Log is here ;  (oh BTW these logs get huge, maybe they need to be auto trimmed!)
www.thepalmers.com.au/temp_txfr/jriver/JRiver_Log_2012-07-10_17-18-55.zip

Richard

[rpalmer68]

Still seeing these failures.

Apparently it happens quite often, the kids just don't bother to tell me that they see the errors pop up on the screen.

Today they were watching ABC3 and a program on ABC2 tried to record.  It went though all my tuners before finally failing.

After I generated the log (see link below) I stopped the live TV playback and was able to watch ABC2 on all the tuners in my system, so it's certainly not a signal issue.


log is here;
http://www.thepalmers.com.au/temp_txfr/jriver/JRiver_Log_2012-07-22_09-32-45.zip

[Yaobing]

I got the logs and will do some investigation.

So your kids were watching something that may or may not involve a tuner at all.  Background recording just failed, and failed on all tuners.  Weird.

[rpalmer68]

I got the logs and will do some investigation.

So your kids were watching something that may or may not involve a tuner at all.  Background recording just failed, and failed on all tuners.  Weird.

I know! The latest log was when they were watching LIVE TV so maybe focus on that one first.

The interesting thing is the program that failed today (Playschool: Farms on ABC2) actually recorded 11 minutes of the program somehow even though it failed and all my tuners had "Error" as their status (other than the one used to watch live TV).

Cheers
Richard

[rpalmer68]

Same problem again this morning, kids were watching ABC3 (live) and got an OSD prompt to switch to ABC2 (they clicked cancel before I could read it).

I checked the tuner status and they all had errors again, so they must have been prompted to switch to ABC2 so that the scheduled recording on ABC2 could be recorded.

I created another log should you need it.

Richard

[Yaobing]

Maybe your DirectShow system has some problem.  When loading a tuner, MC always fails to obtain the name of the device.  Previously I thought maybe it was just with a particular device.  Your recent logs show that it fails in every attempt to create an instance of any tuner.

[rpalmer68]

Maybe your DirectShow system has some problem.  When loading a tuner, MC always fails to obtain the name of the device.  Previously I thought maybe it was just with a particular device.  Your recent logs shows that it fails in every attempt to create an instance of any tuner.

Hmm, but then live playback on the same tuners should also fail I would have thought.

[Yaobing]

Hmm, but then live playback on the same tuners should also fail I would have thought.

Good question.  One possibility is that the system starts to show problem when multiple tuners are to be used.  Maybe it is OK when you only use one or two tuners.

[rpalmer68]

Good question.  One possibility is that the system starts to show problem when multiple tuners are to be used.  Maybe it is OK when you only use one or two tuners.

Maybe, but I can have three or four scheduled recordings all work fine as long as live TV isn't being watched.

In fact most nights at least three recordings are all happening at the same time and I don't get any errors.

Is there anything I can do/test here to help?

Richard

EDIT:  Same issues again this morning, live TV being watched and scheduled recording generating errors.

[Yaobing]

This entry

Code: [Select]

Playback: GetDeviceName: Failed to read FriendlyName or Description from PropertyBag. hr=0x80070002
is found in log files in every attempt to instantiate tuner filters.  Since it is non-essential that we have filter names, we just continue building the graph.

The error has to indicate something is wrong.  The code hr=0x80070002 means "file not found".  This can apply to a missing file, or a missing registry entry. 

[rpalmer68]

This entry

Code: [Select]

Playback: GetDeviceName: Failed to read FriendlyName or Description from PropertyBag. hr=0x80070002
is found in log files in every attempt to instantiate tuner filters.  Since it is non-essential that we have filter names, we just continue building the graph.

The error has to indicate something is wrong.  The code hr=0x80070002 means "file not found".  This can apply to a missing file, or a missing registry entry. 

So you see that error even when starting live TV (that always works) or a schedule that works?  Or only when the recordings are failing when live TV is already started?

[Yaobing]

The error is seen on every attempt to load a tuner, including successful playback.

[rpalmer68]

The error is seen on every attempt to load a tuner, including successful playback.

OK.

But if you just ignore the error anyway, that shouldn't be causing the failure then, especially given multiple tuners work for scheduled recordings and live playback works on its own.

 

[rpalmer68]

I have run a registry cleanup, in fact a couple of different ones and also reinstalled all my DVB-T drivers.

But I still see the same error in the logs, what I don;t understand is how MC can get the friendly name here;

Code: [Select]

0004851: 2912: TV: CDeviceList::EnumAndAdd: Start
0004851: 2912: TV: CDeviceList::EnumAndAdd: Indexed FriendlyName: 01. 7162 BDA DVBT Tuner0
0004851: 2912: TV: CDeviceList::EnumAndAdd: DevicePath: \\?\pci#ven_1131&dev_7162&subsys_752317de&rev_01#4&13f77309&0&00e0#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}\{3ff44ee5-8547-402a-94f3-d44700020000}
0004851: 2912: TV: CDeviceList::EnumAndAdd: Indexed FriendlyName: 02. 7162 BDA DVBT Tuner1
0004851: 2912: TV: CDeviceList::EnumAndAdd: DevicePath: \\?\pci#ven_1131&dev_7162&subsys_752317de&rev_01#4&13f77309&0&00e0#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}\{3ff44ee5-8547-402a-94f3-d44700020001}
0004851: 2912: TV: CDeviceList::EnumAndAdd: Indexed FriendlyName: 03. DNTV Live! Tiny USB2 BDA
0004851: 2912: TV: CDeviceList::EnumAndAdd: DevicePath: \\?\usb#vid_13d3&pid_3223#0008ca1953ec#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}\{a0f9219e-7c58-4a1d-b8e7-7325f0bc4501}
0004851: 2912: TV: CDeviceList::EnumAndAdd: Indexed FriendlyName: 04. DNTV Live! Tiny USB2 BDA
0004851: 2912: TV: CDeviceList::EnumAndAdd: DevicePath: \\?\usb#vid_13d3&pid_3223#0008ca195478#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}\{a0f9219e-7c58-4a1d-b8e7-7325f0bc4501}
0004851: 2912: TV: CDeviceList::EnumAndAdd: Indexed FriendlyName: 05. AF9015 BDA Filter
0004851: 2912: TV: CDeviceList::EnumAndAdd: DevicePath: \\?\usb#vid_1b80&pid_e402#5&1eaa782a&0&3#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}\{9b365890-165f-11d0-a195-0020afd156e4}
0004851: 2912: TV: CDeviceList::EnumAndAdd: Indexed FriendlyName: 06. AF9015 BDA Filter
0004851: 2912: TV: CDeviceList::EnumAndAdd: DevicePath: \\?\usb#vid_1b80&pid_e402#5&1eaa782a&0&3#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}\{9b365890-165f-11d0-a195-0020afd156e5}
0004851: 2912: TV: CDeviceList::EnumAndAdd: Finish (0 ms)
0004851: 2912: TV: CDeviceList::Init: Finish (0 ms)
0004851: 2912: TV: CDeviceList::Init: Start
0004851: 2912: TV: CDeviceList::EnumAndAdd: Start
0004867: 2912: TV: CDeviceList::EnumAndAdd: Indexed FriendlyName: 01. 7162 BDA Analog Capture0
0004867: 2912: TV: CDeviceList::EnumAndAdd: DevicePath: \\?\pci#ven_1131&dev_7162&subsys_752317de&rev_01#4&13f77309&0&00e0#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{bbefb6c7-2fc4-4139-bb8b-a58b00000000}
0004882: 2912: TV: CDeviceList::EnumAndAdd: Indexed FriendlyName: 02. 7162 BDA Analog Capture1
0004882: 2912: TV: CDeviceList::EnumAndAdd: DevicePath: \\?\pci#ven_1131&dev_7162&subsys_752317de&rev_01#4&13f77309&0&00e0#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{bbefb6c7-2fc4-4139-bb8b-a58b00000001}
0004882: 2912: TV: CDeviceList::EnumAndAdd: Finish (31 ms)
0004882: 2912: TV: CDeviceList::Init: Finish (31 ms)
0004882: 2912: TV: CTVManager::CreateTVControlForAllDevices: Start
0004882: 2912: TV: CTVManager::CreateTVControlForAllDevices: Digital Device Friendly name: 7162 BDA DVBT Tuner0 (digital)
0004882: 2912: TV: CTVManager::CreateTVControlForAllDevices: Serialized Name: \\?\pci#ven_1131&dev_7162&subsys_752317de&rev_01#4&13f77309&0&00e0#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}\{3ff44ee5-8547-402a-94f3-d44700020000}
0004882: 2912: TV: CTVManager::CreateTVControlForAllDevices: Digital Device Friendly name: 7162 BDA DVBT Tuner1 (digital)
0004882: 2912: TV: CTVManager::CreateTVControlForAllDevices: Serialized Name: \\?\pci#ven_1131&dev_7162&subsys_752317de&rev_01#4&13f77309&0&00e0#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}\{3ff44ee5-8547-402a-94f3-d44700020001}
0004882: 2912: TV: CTVManager::CreateTVControlForAllDevices: Digital Device Friendly name: DNTV Live! Tiny USB2 BDA (digital)
0004882: 2912: TV: CTVManager::CreateTVControlForAllDevices: Serialized Name: \\?\usb#vid_13d3&pid_3223#0008ca1953ec#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}\{a0f9219e-7c58-4a1d-b8e7-7325f0bc4501}
0004882: 2912: TV: CTVManager::CreateTVControlForAllDevices: Digital Device Friendly name: DNTV Live! Tiny USB2 BDA (1) (digital)
0004882: 2912: TV: CTVManager::CreateTVControlForAllDevices: Serialized Name: \\?\usb#vid_13d3&pid_3223#0008ca195478#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}\{a0f9219e-7c58-4a1d-b8e7-7325f0bc4501}
0004882: 2912: TV: CTVManager::CreateTVControlForAllDevices: Digital Device Friendly name: AF9015 BDA Filter (digital)
0004882: 2912: TV: CTVManager::CreateTVControlForAllDevices: Serialized Name: \\?\usb#vid_1b80&pid_e402#5&1eaa782a&0&3#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}\{9b365890-165f-11d0-a195-0020afd156e4}
0004882: 2912: TV: CTVManager::CreateTVControlForAllDevices: Digital Device Friendly name: AF9015 BDA Filter (1) (digital)
0004882: 2912: TV: CTVManager::CreateTVControlForAllDevices: Serialized Name: \\?\usb#vid_1b80&pid_e402#5&1eaa782a&0&3#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}\{9b365890-165f-11d0-a195-0020afd156e5}
0004882: 2912: TV: CTVManager::CreateTVControlForAllDevices: Analog Device Friendly name: 7162 BDA Analog Capture0 (analog)
0004882: 2912: TV: CTVManager::CreateTVControlForAllDevices: Serialized Name: \\?\pci#ven_1131&dev_7162&subsys_752317de&rev_01#4&13f77309&0&00e0#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{bbefb6c7-2fc4-4139-bb8b-a58b00000000}
0004882: 2912: TV: CTVManager::CreateTVControlForAllDevices: Analog Device Friendly name: 7162 BDA Analog Capture1 (analog)
0004882: 2912: TV: CTVManager::CreateTVControlForAllDevices: Serialized Name: \\?\pci#ven_1131&dev_7162&subsys_752317de&rev_01#4&13f77309&0&00e0#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{bbefb6c7-2fc4-4139-bb8b-a58b00000001}
Then not get it here;

Code: [Select]

0004898: 2912: Playback: CJRPlaybackEngine::Play: Start
0004898: 2912: Playback: CJRPlaybackEngine::Play: Volume protection: 0
0004898: 2912: Playback: CJRPlaybackEngine::Play: Playing: TV Channel DTV 1282 (12820-1312)177500, 7, 4115, 514, 4, 0, 513, 512, 516 (DVB-T).tvlb
0004898: 2912: Playback: CJRPlaybackEngine::Play: Filetype: tvlb; Type: 11; Can play: 1; Playback object: 0x531f130
0004898: 2912: Playback: CJRPlaybackEngine::StartPlayFile: Start
0004898: 2912: Playback: CJRPlaybackEngine::TV_PlayFile(): Command:
0004898: 2912: Playback: CDisplayPlugin::LoadPlugin: Start
0004898: 2912: Playback: CDisplayPlugin::LoadPlugin: Plugin: Current Playback Display
0004898: 2912: Playback: CDisplayPlugin::LoadPlugin: Finish (0 ms)
0004898: 2912: Playback: COSDWindow::Show: Start
0004898: 2912: Playback: COSDWindow::Show: Starting TV..., -1, 0
0004898: 2912: Playback: COSDWindow::Show: Creating OSD window
0004898: 2912: Playback: COSDWindow::UpdatePosition: Start
0004898: 2912: Playback: COSDWindow::UpdatePosition: Finish (0 ms)
0004898: 2912: Playback: COSDWindow::Show: Finish (0 ms)
0004976: 2912: TV: CMJTVCtrl::FinalConstruct: Start
0004976: 2912: TV: CMJTVCtrl::FinalConstruct: HWND: 0. MainTVManager created: 0x52a52e8
0004976: 2912: TV: CMJTVCtrl::FinalConstruct: Finish (0 ms)
0004976: 2912: TV: CMainTVManager::OnSize: Start
0004976: 2912: TV: CMainTVManager::OnSize: OnSize called. Width - 0, Height - 0
0004976: 2912: TV: CMainTVManager::OnSize: Finish (0 ms)
0004992: 2912: TV: CMainTVManager::SetInfo - 0x52a52e8: Zone: 1002
0004992: 2912: TV: CMainTVManager::SetInfo - 0x52a52e8: DigitalTVDevice: @device:pnp:\\?\usb#vid_1b80&pid_e402#5&1eaa782a&0&3#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}\{9b365890-165f-11d0-a195-0020afd156e4}
0005007: 2912: TV: CMainTVManager::SetInfo - 0x52a52e8: DigitalTVDevicePath: \\?\usb#vid_1b80&pid_e402#5&1eaa782a&0&3#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}\{9b365890-165f-11d0-a195-0020afd156e4}
0005007: 2912: SDK: CMJAutomation::CMJAutomation: Global Count: 3, Main 0, 69f3eb0
0005007: 2912: TV: CMainTVManager::OnSize: Start
0005007: 2912: TV: CMainTVManager::OnSize: OnSize called. Width - 320, Height - 180
0005007: 2912: TV: CMainTVManager::OnSize: Finish (0 ms)
0005007: 2912: TV: CMainTVManager::SetInfo - 0x52a52e8: Zone: 0
0005007: 2912: SDK: CMJAutomation::~CMJAutomation: Global Count: 2
0005070: 2912: TV: CMainTVManager::SetInfo - 0x52a52e8: DSPCore: 053195B0
0005070: 4580: Playback: CMainTVManager::Thread: Start
0005070: 4580: TV: CMainTVManager::Initialize: Start
0005085: 4580: TV: CMainTVManager::Initialize: before InitializeDevices
0005085: 4580: TV: CMainTVManager::InitializeDigitalVideoDevice - 0x52a52e8: Start
0005085: 4580: TV: CMainTVManager::InitializeDigitalVideoDevice - 0x52a52e8: Creating CDigitalTV object for AF9015 BDA Filter
0005085: 4580: Podcast: CDXColorControls::Clear: Start
0005085: 4580: Podcast: CDXColorControls::Clear: Finish (0 ms)
0005132: 4580: Playback: GetDeviceName: Failed to read FriendlyName or Description from PropertyBag. hr=0x80070002
0005132: 4580: TV: CMainTVManager::InitializeDigitalVideoDevice - 0x52a52e8: Finish (47 ms)
0005132: 4580: TV: CMainTVManager::Initialize: Finish (62 ms)
0005132: 2912: TV: CMainTVManager::SetInfo - 0x52a52e8: TunerInputType: DVB-T
0005148: 2912: TV: CMainTVManager::SetInfo - 0x52a52e8: DVBChannelGroup: C:\Users\HTPC\AppData\Roaming\J River\Media Center 17\Temp\TVChannelData.xml
0005163: 2912: TV: CMainTVManager::SetInfo - 0x52a52e8: SetVolume: 0
Could it be related to the fact that some tuners have the same name?

Still not convinced it's the cause of the recording failures either to be honest.

Richard

[jmone]

Hi Yaobing,
I can confirm the issue (see log).
1) Started Live TV Playback
2) When Scheduled TV Recording was to start MC popped up an error msg window and the recording was cancelled (tested in Std View)

[rpalmer68]

Hi Yaobing,
I can confirm the issue (see log).
1) Started Live TV Playback
2) When Scheduled TV Recording was to start MC popped up an error msg window and the recording was cancelled (tested in Std View)

Thanks for testing Nathan, glad it's not just me seeing this issue.

R

[rpalmer68]

Yaobing,

I rolled back to 17.160 tonight (a build prior to several  TV changes that were made) and tested that and I DO NOT get the recording issues.

I can watch live TV AND have two scheduled recordings start in the background fine.

I still see the friendy name errors  in the log, but live recordings worked fine.

Richard

[Yaobing]

Richard, that is good info to have.

[rpalmer68]

Richard, that is good info to have.

Thought it might be

Just tested 167 and that works OK too.

Have installed 170 and will test that in the morning.

R

[rpalmer68]

Have deleted a number of posts from over the weekend, and will start again....

In my initial testing since using build 160, I'd schedule a recording that would start in the next 5 minutes, then start live TV and wait to see if I got an error.

Doing this builds 167, 170, and 176 all worked fine.  BUT I left built 176 on my system and later in the day I got tuner failures as originally reported.

So I now suspect that maybe live TV needs to be running for a while before the error gets triggered.

So I rolled back to build 160 again to start my testing all over, unfortunately 160 has a bug where tuners get a status of "undefined" not "recording" and stay in that state.

I am now running build 167, tuners are not being left in an "undefined" state so will continue testing and report later tonight after several scheduled recordings have passed.

EDIT:  So far 167 is working fine, several recordings have started while live TV was running, including overlapping recordings. 

I will continue to test, but I am prerry confident that 167 is a good build while 176 and beyond are not.

Richard

[JimH]

Thanks for the testing and for your patience, Richard.

[Yaobing]

Can you try build 171 and see if it works?

[Yaobing]

And, if build 171 works, check build 172.

[rpalmer68]

And, if build 171 works, check build 172.

On my initial round of tests 171 seems to be OK.  Will now try 172 and let you know.

R

[rpalmer68]

So far 172 is OK as well.

Have had live TV running for 3 hours and several scheduled recordings have worked fine.

Will keep testing and report back if I see issues.

Richard

[Yaobing]

This does not confirm my suspicion.  I will therefore look for other suspects.  Let me know when you find out which build has the problem.

[rpalmer68]

This does not confirm my suspicion.  I will therefore look for other suspects.  Let me know when you find out which build has the problem.

I know 176 is the issue so I'll split the difference and try 174 and let you know....

EDIT:  174 worked fine, now testing 175

[rpalmer68]

175 has been working fine all evening, I'll continue using this build for another day but it seems build 176 may be the first of the problem builds.

R

[Yaobing]

I have looked over all changes I made between builds 175 and 176.  Can't identify anything that could cause recording to fail

[rpalmer68]

I have looked over all changes I made between builds 175 and 176.  Can't identify anything that could cause recording to fail

And you are probably right, 175 generated the errors this morning so is does start at an earlier build.  

I just can't put my finger on what is causing it, unless it's a memory leak type issue so MC needs to be running for a while before it happens or the scheduled recording has to be part of a subscription as all the ones failing are part of subscriptions while my testing ones haven't been.

For my testing I schedule a recording and have live TV play for at least 45 minutes prior to the recording starting, this hasn't been failing.... but this morning the kids were watching live TV and the scheduled recording failed.  Looking at the TV status, all tuners have "Error" except the one being used for live playback.

I'll roll back to 171 and run that for a few days to see what happens.

[rpalmer68]

(throws hands in the air is despair!)

171 had generated the failures tonight.

The only pattrern I can see is that a TV recording (jtv) is watched, then live TV is started after that and then a scheduled subscription will fail on ALL tuners while live TV is playing.

I'll roll back to 167 and try it all over again, just wish I could find the trigger that causes the failures.

I do notice that there were some TV changes in 167, is it possible these are related to this issue?  

I'll test 166 and if that doesn't fail after a couple of days  I'll go back to 167, although I think 166 might give me the same tuner undefined issues that 160 gives as I'm sure the changes in 167 were to fix that issues.... ( http://yabb.jriver.com/interact/index.php?topic=72441.0)


Richard

[Yaobing]

I do notice that there were some TV changes in 167, is it possible these are related to this issue?  

I'll test 166 and if that doesn't fail after a couple of days  I'll go back to 167, although I think 166 might give me the same tuner undefined issues that 160 gives as I'm sure the changes in 167 were to fix that issues.... ( http://yabb.jriver.com/interact/index.php?topic=72441.0)

There were two changes in 167:

One is closely related to the current problem.  The tuners left in "undefined" status were the ones that failed to record.  The change I made in 167 put them in "error" status.  So the problem may have started much earlier.

The other change in that build was a threading change for stopping recording.  That would not cause failure to start recording.

[rpalmer68]

OK well 166 has behaved this morning, it is currently recording while live TV is playing and the kids normally complain of "the error" in at this time in the morning.

The tuner says "Undefined" not "Recording" but it is actually recording.  

I will continue using 166 to see what happens....


EDIT: Once MC stops recording tuner stays in "Undefined" state and isn't released.  I have restarted MC and will see if I get any errors today/tonight.

[Yaobing]

Can you get me a log, showing MC putting a tuner in "Undefined" state even though it started recording successfully?

[rpalmer68]

Can you get me a log, showing MC putting a tuner in "Undefined" state even though it started recording successfully?

I think I may be wrong,  I seem to be missing a recording from this morning and I think it may have been the one that had the  "undefined" status.

I've tried to schedule recordings tonight and they have all worked even with live TV so I still can't work out how to trigger the error or the "undefined" tuner status!

I have reset the logs and will wait for the undefined tuner tomorrow morning and then grab the logs. Then I can give you a log with the undefind status and one that has worked for you to compare.

Richard

[rpalmer68]

OK here is a log.

http://www.thepalmers.com.au/temp_txfr/jriver/JRiver_Log_2012-08-03_08-07-47.zip

1) Spongebob recorded first thing this morning (with nobody watching anything live) and completed OK and tuner returned to "idle".
2) Watched NINE DIGITAL live for a bit
3) Kids then watched the spongebob recording from earlier
4) Kids then watched ABC3 (live)
5) The scheduled recording (Charlie and Lola) started (and said "recording" in status initially) but failed (no error in OSD) and left tuner in "undefined" status.
6) I generated the log


Hope this helps,

Many thanks
Richard

EDIT:  Just to add to this, the next scheduled recording worked fine after I'd generated the log and live TV had been stopped.  It used the first tuner, while the 2nd tuner was still in the "undefined" state.

[rpalmer68]

Just a friendly reminder that I'm still having issues wiht this.... I'm now on MC18 but the same problem exists.

If watching LIVE TV then all scheduled recordings will fail on all the other tuners in my system (With warnings popping up on the screen each time a tuner fails).

If I stop live TV, then the next tuner attempted will work fine!

Yaobing:  FYI I'm still on direct sound not wasapi and it's still failing.

I know nobody else has reported this, but maybe there aren't many that run their scheduled recordings on the same machine they watch live TV on??

Or maybe many don't watch anything live!  (I know I try to avoid it so I can skip the adds)

Thanks
Richard

[Adcom]

Hi,

Same problems here, hope it gets sorted soon.


Regards
Mike

[rpalmer68]

Hi,

Same problems here, hope it gets sorted soon

Well I'm glad somebody else is seeing this too, assuming it is the same issue.

Maybe if you could send a log to Yaobing(at) jriver.com so he can see if there is a common pattern.

Cheers
Richard

[Yaobing]

Does it matter which video renderer you use for live playback?  Richard's latest log file shows madVR.  Which video renderer do you use, Mike?  Can you both try using a different video renderer?

[Adcom]

Hi,

I'm not sure it really matters which video renderer is used for live playback. I don't have to be watching live TV for the second scheduled recording to fail to start, it's like MC is only seeing one single tuner although all tuners are listed.

I thought it was perhaps having a mixture of DVB-T and DVB-T2 tuners was causing the failure but I've pulled the DVB-T tuner and the problem still persists. How does MC sort out which tuner to use when there is a mixture of DVB-T and DVB-T2 tuners, in WMC you can select which tuner is assigned to any particular channel, so only the DVB-T2 tuner will be used for HD channels. Is there a similar feature in MC18?

For me MC18 would be perfect solution if and when the TV side of things gets sorted, until then I'll have to use WMC7 for TV / TV recording.

Regards
Mike

[Yaobing]

DVB-T and DVB-T2 are treated the same.  That may be a problem if you have tuners that can only handle DVB-T but not DVB-T2.  So your situation may be different from Richard's.

Can you confirm that the failure occurs when MC attempts to record a DVB-T2 channel using a DVB-T tuner?  But if you pulled all DVB-T tuner out and the problem still exists, then it is something else. 

Please email me a log file, as Richard had suggested.  I am yaobing at jriver dot com

[Adcom]

Hi,

Log file sent.

I've also noticed that in TV settings, that my Blackgold BGT3620 DVB-T2 is correctly identified as having twin tuners. However, one of the tuners has (1) at the end of it's name. If this tuner is reordered to the top of the tuner list then no TV picture is displayed, if it is moved down one place and the tuner without (1) is at the top then a picture is displayed OK. It looks like the second tuner (1) is not being used.


Regards
Mike

[Sandy B Ridge]

However, one of the tuners has (1) at the end of it's name. If this tuner is reordered to the top of the tuner list then no TV picture is displayed, if it is moved down one place and the tuner without (1) is at the top then a picture is displayed OK. It looks like the second tuner (1) is not being used.

Make sure both tuners are set to DVB-T in the settings.

SBR

[Adcom]

Make sure both tuners are set to DVB-T in the settings.

SBR

Hi,

Both set to DVB-T

Mike

[Sandy B Ridge]

Both set to DVB-T

ah well. It was just a thought.

What happens if you set the working one to something else like ATSC? (you can easily change it back again) Does the other one kick in? Can you scan for channels on the (1) one?

SBR

[Adcom]

ah well. It was just a thought.

What happens if you set the working one to something else like ATSC? (you can easily change it back again) Does the other one kick in? Can you scan for channels on the (1) one?

SBR

Hi,

Set the working channel it to ATSC, no picture at all, set it back to DVB-T, can view channels OK. Can scan and find channels fine with (1).

What tuner config do you have and can you watch live TV and record other channels in MC18?

Regards
Mike

[Sandy B Ridge]

Set the working channel it to ATSC, no picture at all, set it back to DVB-T, can view channels OK. Can scan and find channels fine with (1).

OK, so it sounds like MC can talk to tuner (1) and that it can work OK, but for some reason gets its knickers in a twist when showing a channel.

I can't really help any further. Sounds like Yaobing needs a log to figure out the problem.

What tuner config do you have and can you watch live TV and record other channels in MC18?

I'm still on MC17 [hangs head in shame]. (Haswell, my toddler is taking up all my fettling time; Ivy is expecting again - a Trinity this time! So that means I have zero time to upgrade and fiddle).

But yes I can tune 2 channels at once. BTW I have a BGT3600 with 2 DVB-T and 2 DVB-S. I've stopped using the DVB-T now because I had problems with my terrestrial aerial, so just using DVB-S now.

There have been some 'issues' with some BGT cards discussed in avforums where they had a faulty batch of components, but I don't think the 3620 was affected so much. I assume it work OK to tune 2 channels in other software?

SBR

[Adcom]

OK, so it sounds like MC can talk to tuner (1) and that it can work OK, but for some reason gets its knickers in a twist when showing a channel.

I can't really help any further. Sounds like Yaobing needs a log to figure out the problem.I'm still on MC17 [hangs head in shame]. (Haswell, my toddler is taking up all my fettling time; Ivy is expecting again - a Trinity this time! So that means I have zero time to upgrade and fiddle).

But yes I can tune 2 channels at once. BTW I have a BGT3600 with 2 DVB-T and 2 DVB-S. I've stopped using the DVB-T now because I had problems with my terrestrial aerial, so just using DVB-S now.

There have been some 'issues' with some BGT cards discussed in avforums where they had a faulty batch of components, but I don't think the 3620 was affected so much. I assume it work OK to tune 2 channels in other software?

SBR

Hi,

Thanks for your input, I have already sent the log, hope he can figure out what the problem is.

All four tuners work as expected in WMC7.

Regards
Mike

[Yaobing]

You have four tuners, but only two are DVB-T, the other two are DVB-C.  You set all of them to DVB-T.  The log shows MC trying to record a DVB-T channel using one of the DVB-C tuners and failed.

There maybe other issues, but the above is one that I can identify for now.  I see, inexplicably, ATSC appearing in the log.  Maybe that was you experimenting with changing something to ATSC?  If you set a tuner's type to ATSC, then it should not be loaded by MC for DVB-T recording/playing.  I am not sure what is going on there.

Here is what you need to do:

Tools > Options > Television, select a device from the list box under "Devices", and click Confgure..., on the resulting "Tuner Type" property page, choose DVB-T for tuners that are named "7231 BDA DVBT Tuner" or "7231 BDA DVBT Tuner (1)", and choose DVB-C for tuners that named "7231 BDA DVBC Tuner" or "7231 BDA DVBC Tuner (1)".