Yes, as you mentioned, when I changed the trigger condition to profile-cond=height==1080 and width==1440, it worked. However, I still hope that the complex conditions I used previously could be effective. Is there any hope that this could be fixed?

Chainik wrote:

tried simple test, works for me...
start with something simple like "width>1000" and go from there

anyway, there're no issues with SVPlayer here

No, even when the corresponding video file has been playing for a long time, the parameters in the target profile do not take effect. I have attached my mpv.conf and the complete log for reference.

Chainik wrote:

probably the error logged before actual file was loaded, thus 'path' is still not defined...
https://github.com/mpv-player/mpv/issue … -743144580

I'm using a rooted Android tablet, and I've added the following content to mpv.conf:

```

[test]
profile-cond=path:find('[example-rawmaker][example-tittle]')
glsl-shaders="~~/shaders/AMD_FSR_rgb_RT.glsl:~~/shaders/nlmeans.glsl"

```

However, when I play a file that meets the condition, I get the following mpv log output:

```

[   0.015][v][auto_profiles] Re-evaluating auto profile test 
[   0.015][v][auto_profiles] Profile condition error on evaluating: [string "profile test condition"]:1: attempt to index global 'path' (a nil value) 
[   0.015][v][auto_profiles] Re-evaluating auto profile test 
[   0.015][v][auto_profiles] Profile condition error on evaluating: [string "profile test condition"]:1: attempt to index global 'path' (a nil value)
Chainik wrote:

you'd better give a clear example of what you think must work but it doesn't

> removed the related functional module from mpv

i don't think so

As mentioned in the title, does this mean that svp for android has removed the related functional module from mpv?