Multidec almost working - Cannot record multiple shows

[sub]

Thanks Reddwarf, I still have stability problems and I am trying different setups.

I have however discovered another multirecord problem that I can not figure out. Currently I have 2 multidec instances setup. If I start to record two prallell shows it works fine but if I cancel one recording and try to watch another channel NPVR gives me the "unable to find available capture device" for some of the channels wheras other work.

Were these channels on the same frequency? ie, I'd expect only some channels to work (since they're on the same frequency), and the others to report 'unable to find available capture device' (since they're on a different frequency).

[agerdin]

Yep, All channels where recording and watching worked were on the same frequency. So I guess this is an expected behaviour. Will it be resolved or is this a limitation we should count on?

Thanks,

\\Agerdin

[sub]

Yep, All channels where recording and watching worked were on the same frequency. So I guess this is an expected behaviour.

These two sentences seem to conflict. If they were on the same frequency, then it shouldnt give you ''unable to find available capture device'', so not expected behaviour - or did you mean to say they're on different frequencies?

Will it be resolved or is this a limitation we should count on?

I wasnt expecting to make any further changes to multidec support, but this sounds like it is outside of that.

[agerdin]

These two sentences seem to conflict. If they were on the same frequency, then it shouldnt give you ''unable to find available capture device'', so not expected behaviour - or did you mean to say they're on different frequencies?

Not sure anymore The two channels that I started to record was on the same frequency. After cancelling one of them I could ONLY watch channels from that same frequency. Trying another channel gave me the "unable...." message.

[sub]

Not sure anymore The two channels that I started to record was on the same frequency. After cancelling one of them I could ONLY watch channels from that same frequency. Trying another channel gave me the "unable...." message.

If that other channel that gave 'unable..' message was on another frequency, then that is the correct behaviour. At the end of the day, your tuner can only be tuned to one frequency at a time.

[Barsk]

I have also seen this bug with "unable to find capture device" although there would be one tuner sitting idle (as I recall). I haven't been able to reproduce it though. But now we have two sightings at least... I guess this is why there is still Beta in the name

[sub]

I have also seen this bug with "unable to find capture device" although there would be one tuner sitting idle (as I recall). I haven't been able to reproduce it though. But now we have two sightings at least... I guess this is why there is still Beta in the name

To be honest, I havnt seen anything that makes me think there is really an application problem causing this. In agerdin's case, I'm guessing he is just trying to use a channel on another frequency.

If you want to reproduce your problem and post the logs, I'm happy to take a look.

[Barsk]

Yes, If it happens again I will zip the logs for sure. The problem is that it only happened when I was stress testing my multidec/multirec settings, And to reproduce the situation would probably need a couple of hours of devotion. Which I dont't have at the moment.
There is another bug that has a connection to the NMT integration though that is far more important. It hangs the whole service. I´ll post more of it in my little list of bugs thread...

[sub]

Yes, If it happens again I will zip the logs for sure. The problem is that it only happened when I was stress testing my multidec/multirec settings, And to reproduce the situation would probably need a couple of hours of devotion. Which I dont't have at the moment.

Ok, post the log when you find the time. Until then, I'll just assume there is no problem.

[agerdin]

Ok, post the log when you find the time. Until then, I'll just assume there is no problem.

Ill also try to get you a set of logs where the problem clearly can be identified. Will probably not happen until next week since Ill be out of the country for a couple of days.

\\Agerdin