patacalas

Hi @Barracuda09 I've just tried the latest version and I can finally tune in to channels with 16APSK modulation.  The request is still using mtype=qpsk param, but it works....

> So that means nothing of the tuning parameters (freq. pol ect) change only the stream ID? Multistream transponder example. Same frequency, polarization, FEC,... but different stream ID (check red...

> > The request is still using mtype=qpsk param, but it works. > > Were is this showing, in SatPI or what do you mean precise? Is this still not...

Hi @Barracuda09 I've tested the last version, it's working fine on previous scanned channels (no problem with stream ID param), but now I can't do channel search successfully. The stream...

> > Did scaning work in previous versions? > Hi @Barracuda09. Channel search worked almost fine on previous versions. About 90% success in normal transponders and 40-50% on multistream transponders...

Hi @Barracuda09 I've done new tests. I've tried again all the version you shared here to compare tuning times and procedures. All versions take about 16-17s between RTSP request and...

I've tried different values of DVR buffer, but changing that value doesn't make any difference.

Yes, normal transponders work faster.

Hi @Barracuda09 I was wondering if you can share the latest version compiled for ARM here. It's hard for me to compile the code on my Linux receiver. I would...

Sorry for my late response, I've been very busy. I've tested last release v1.2.44 and the problems continue. Client receiver only can tune 8PSK modulated multistream transponders (except 12149V). 16APSK...