77 replies to this topic

[isteric2005]

After the settings of the tuner

 

I run an automatic channel scan

 

as you notice I can not select the tuner to scan,
I will do all the automatic,
but I get this response

 

Edited by isteric2005, 15 October 2016 - 21:58.

[isteric2005]

then I try the scasione fast and I get this response

 

 

I do not think it's normal, how can you fix ??

Edited by isteric2005, 15 October 2016 - 21:58.

[isteric2005]

And 'normal that if I switch from satellite to DTT I always give the tuner A ??

[isteric2005]

Also I realized that with the image output on channel volume now only works from the last green segment on the skin

[isteric2005]

I tried another image, and in this you can scan for tuner used as shown in the panel

 

Attached Files

•  screenshot9.jpg   69.22KB   6 downloads
•  screenshot10.jpg   59.78KB   6 downloads

Edited by isteric2005, 16 October 2016 - 09:24.

[isteric2005]

I hope my message is clear and easy to understand

[littlesat]

Currenly with our image you can only scan the tuner type you select... There is some work in progress here... The other images make as far we can see a dirty patch... (Lets now wait for the comments)...

When you select dvb t you can scan dvb t, when you select dvb-s you can scan dvb-s... And when you select dvb-s it also can tune dvb-c/t...

Edited by littlesat, 16 October 2016 - 09:42.

[littlesat]

B.t.w. Athoik is working on this topic... I hope he'll read this and continue his nice work on this one...

[athoik]

Hi,


The C++ "engine" of Enigma2 is ready and all the fixes I was familiar with applied for multituner.

The python "engine" of Enigma2 (aka UI) needs now improvements in order to allow scanning multiple types without changing types.

I am not so good with UI so I leave it to the experts.

[littlesat]

Shoot...! I cannot really help here

[athoik]

So sad nobody has a clean design on his mind about bringing Enigma to next level supporting multituner devices natively using UI.

I known only the UI code OpenATV did and most parts seem fine in the UI.

I had mentioned internally what should be change with examples since the prerelease of osmini+, but seems nobody interesting in UI.

Edited by athoik, 16 October 2016 - 14:40.

[littlesat]

I did hoop you could finished it...

Sorry I do not have much time yet and my os minimis currently in the box...

Edited by littlesat, 16 October 2016 - 16:21.

[isteric2005]

With the image output now adjust the sound is zero until it does not reach the skin before the yellow line that displays the audio

[littlesat]

Sorry I don't understand....

[isteric2005]

Loo Look at the skin up to now no audio

ok at the skin

up to now no audio

 

Look at the skin
up to now no audio

Look at the skin up to now no audio 

Look at the skin
up to now no audio

 

Look at the skin

up to now no aud

 

Attached Files

•  screenshot.jpg   61.04KB   3 downloads

Edited by isteric2005, 16 October 2016 - 17:43.

[isteric2005]

So you understand?

[littlesat]

Nope....

[WanWizard]

From what I understand, there is no sound when you turn the volume up, until you get to a certain point (about half way looking at the screenshot).

 

If so, is it then loud all of a sudden, or does it slowly come on? How is the box connected to the TV? Or it is connected to an amplifier? Is downmix perhaps not enabled, so there is a difference between PCM (stereo) audio and AC3 (which is always 100%)?

[athoik]

Downmix is on or off? If off change to on.

[isteric2005]

You've got it right,

the tests I performed with scart connection.

 

Until I arrive at that point no sound and then comes ......

it is as if the skin would mark a value not corresponding to reality

 

Downmix is in the default position

Edited by isteric2005, 16 October 2016 - 19:39.