Testers required for OpenViX Python 3 images

[BrokenUnusableAccount]

Do completed timers show the same filenames?

Yes they do!
View attachment timers.xml

 

[BrokenUnusableAccount]

The option is there on my uno4k it just doesn't seem to adjust the volume switching from satellite to IPTV

root@vuuno4k:~# cat /proc/stb/audio/avl_choices                           dac spdif hdmi none

Guessing...
Does auto volume level require downmixing to stereo and you have forgotten to enable downmixing?

 

[twol]

The option is there on my uno4k it just doesn't seem to adjust the volume switching from satellite to IPTV

root@vuuno4k:~# cat /proc/stb/audio/avl_choices                           dac spdif hdmi none

Code hasn‘t changed - if the option is there then it should work, unless there is a driver issue.

 

[dsayers]

Guessing...
Does auto volume level require downmixing to stereo and you have forgotten to enable downmixing?

That seems to have sorted it. I had

AC3 downmix: Downmix
ACC downmix: Passthrough

Set both to Downmix and that seems to have worked. Thanks

 

[ccs]

Yes they do!
View attachment 62291

What have you got Recording and playback/Composition of the recording filenames set to?

Long filenames seems to work, but might eventually cause problems ??

eg

rw-r--r--    1 root     root      58523648 Jun 26 16:52 20210626 1558 - BBC ONE HD - MOTD Live_ Wales v Denmark - Live coverage from Amsterdam of Wales v Denmark, the opening match in the round of 16_ With commentary from Steve Wilson and Robbie Savage_ [S] [HD].ts

 

[BrokenUnusableAccount]

What have you got Recording and playback/Composition of the recording filenames set to?

Date First.

 

[BrokenUnusableAccount]

There's more than a good chance I'm just being dumb, but I don't understand why this commit to OpenViX/enigma2//Dev-python3-compatible is correct:

https://github.com/OpenViX/enigma2/commit/aa92a1cde8d95661c3718efc087c592e3a4264c2

Dev-python3-compatible is presumably the branch used to build the Py3 images.

 

[twol]

There's more than a good chance I'm just being dumb, but I don't understand why this commit to OpenViX/enigma2//Dev-python3-compatible is correct:

https://github.com/OpenViX/enigma2/commit/aa92a1cde8d95661c3718efc087c592e3a4264c2

Dev-python3-compatible is presumably the branch used to build the Py3 images.

So try the old version 1st attachment and a twist in 2nd version (ZASCIItranslit.py -----> rename to ASCIItranslit.py) ----> to /usr/lib/enigma2/python/Tools

 

[BrokenUnusableAccount]

So try the old version 1st attachment and a twist in 2nd version (ZASCIItranslit.py -----> rename to ASCIItranslit.py) ----> to /usr/lib/enigma2/python/Tools

Thanks.

First one just crashes.
Second one works correctly except I think I'm getting, or maybe only sometimes getting, an extra underscore at the beginning of the name of the recorded program (after the dash that sepatates the date part from the name part). It makes most of the underscores go away anyway.

But when it comes to understanding what's going on and why I'm the only one effected I'm really lost.
I might try setting things up from scratch again to see if something is odd in my saved settings.

 

[twol]

It would help if I knew which module was calling the Ascii translation module and why this is happening (only?) for you. You get the underscore because it has failed to translate the character - the alternative is to replace with a ? or ignore (that is drop the character)

 

[BrokenUnusableAccount]

It would help if I knew which module was calling the Ascii translation module and why this is happening (only?) for you. You get the underscore because it has failed to translate the character - the alternative is to replace with a ? or ignore (that is drop the character)

Possible misunderstanding maybe.
As far as I know it is being called in the normal way to make the file name from the name of the program (or is it the name from the timer).
All the things I said happen are happening as I start a recording.

 

[BrokenUnusableAccount]

Second one works correctly except I think I'm getting, or maybe only sometimes getting, an extra underscore at the beginning of the name of the recorded program

I was wrong. I get the same extra underscore with the 5.4.013 Py2 image.
Maybe I just never noticed it before.
I think possibly it's only on recording set from OpenTV EPG, and not on those set from Freesat EPG.

 

[twol]

I was wrong. I get the same extra underscore with the 5.4.013 Py2 image.
Maybe I just never noticed it before.
I think possibly it's only on recording set from OpenTV EPG, and not on those set from Freesat EPG.

So I have added debug to ASCIItranslit - can you copy to /usr/lib/enigma2/python/Tools and let me have debug logs ... rename existing module first.

Whatever I do, I am unable to get debug on my image from ASCIItranslit - this module is never entered on my system, so we need to find out why it is on yours.

It would be interesting to see debug from py2 & py3, if you have the time

If there is a crash (as said not able to test) due to the debug, please post crash log as well - it may help in showing who is calling the module

 

[ccs]

It would help if I knew which module was calling the Ascii translation module and why this is happening (only?) for you. You get the underscore because it has failed to translate the character - the alternative is to replace with a ? or ignore (that is drop the character)

It's called in RecordTimer.py, you probably know that already....

https://github.com/OpenViX/enigma2/blob/Dev-python3-compatible/lib/python/RecordTimer.py#L335

 

[twol]

It's called in RecordTimer.py, you probably know that already....

https://github.com/OpenViX/enigma2/blob/Dev-python3-compatible/lib/python/RecordTimer.py#L335

No - but thanks.
So why has Brian config.recording.ascii_filenames.value set??
if config.recording.ascii_filenames.value:
filename = ASCIItranslit.legacyEncode(filename)

@Brian
in menu/setup/Recordings/recording & playback, have you set Limit character set for recording purposes to Yes??

If Yes, still run my debug ASCIItranslit then turn it off!!!

 

[ccs]

in menu/setup/Recordings/recording & playback, have you set Limit character set for recording purposes to Yes??

If Yes, still run my debug ASCIItranslit then turn it off!!!

That certainly causes it!

 

[twol]

That certainly causes it!

Yes - issue with spaces - will try and fix i(changed to _ )

 

[BrokenUnusableAccount]

@Brian
in menu/setup/Recordings/recording & playback, have you set Limit character set for recording purposes to Yes??

Yes.
I must have thought it would make filenames that were the most likely to be compatible with any OS I wanted to copy them to.
But actually looking at the code of the function it looks like it's not designed for that purpose, so I won't use it in the future.

 

[BrokenUnusableAccount]

So I have added debug to ASCIItranslit - can you copy to /usr/lib/enigma2/python/Tools and let me have debug logs ... rename existing module first.

Whatever I do, I am unable to get debug on my image from ASCIItranslit - this module is never entered on my system, so we need to find out why it is on yours.

It would be interesting to see debug from py2 & py3, if you have the time

If there is a crash (as said not able to test) due to the debug, please post crash log as well - it may help in showing who is calling the module

in menu/setup/Recordings/recording & playback, have you set Limit character set for recording purposes to Yes??

If Yes, still run my debug ASCIItranslit then turn it off!!!

Log file attached: View attachment Enigma2_debug_2021-06-29_01-16-48.log

Are the weird characters at the start and end of program names normal?
(C2 86 before the name and C2 87 after it, my editor says they are SSA and ESA)

 

[BrokenUnusableAccount]

Are backed up settings from 5.4.x Py2 supposed to be compatible with 5.5.x Py3 images and vice versa?

I've been assuming that they are compatible, and they do seem to at least be mostly compatible but I noticed that restoring settings from one on the other one seems to mess up oscam. It seems to make it so that oscam will not start and only removing and re-installing oscam-latest from the feeds fixes it.