VLC 2.0.5 logo overlay problem with telnet control

[HowardL]

VLC2.0.5 does not seem to allow logo file overlays to be controlled from the telnet interface.
No logo-file errors are reported (status returned is 0) but I am unable to control either the logo file to be used or the opacity
when using the telnet code:
@logo logo-file C:\Users\Howard\AppData\Local\Temp\ovly0.png
or
@logo logo-opacity 128

VLC 1.1.11 works for opacity changes but not logo-file changes

When I try this using the menus built into VLC, things "seem" to work however things are definitely funny.
After starting VLC and going to the video effects overlay menu, I can select a logo file. Everything works until I UNcheck the logo file
option and then recheck it. Nothing happens until I change transparency settings which then brings up the overlay originally
specified on the command line even though the logo filename in the window still shows the one I selected from the menu.
I suspect this is a menuing bug....

After trying the above menu procedure, VLC THEN responds to the @logo logo-opacity commands from telnet.



I use the following startup args:

vlcargs (in single quotes):
'--extraintf=luacli', '--rc-quiet', '--rc-host=127.0.0.1:4400', '--video-filter=motionblur:adjust', '--sub-filter logo:marq', '--logo-opacity=0',
'--logo-file C:\Users\Howard\AppData\Local\Temp\ovly0.png', '--width=1440', '--height=900', '--fullscreen', '--marq-marquee="DVD is NOT playing actual movie"',
'--marq-x=-1', '--marq-y=-1', '--marq-refresh=500', '--marq-position=4', '--marq-opacity=0', 'dvd:///F:\'


vlcpath : C:\Program Files\VideoLAN\VLC205

[HowardL]

Follow up on this issue.

I neglected to mention that I use overlays the same size as the full screen (as a variable opacity mask over the entire window).

It 'appears' to be related to running fullscreen while using the Direct3d or Direct2d renderers.

Running in NON full screen mode, everything works no matter which renderer is used.
Running fullscreen using the directX renderer, everything works. Even the OpenGL renderer sort of works (but sloooow).

In troubleshooting, I discovered that if I sized my overlay SMALLER than the full screen (by 100 pixels!) even the Direct3d renderer worked.
The error messages seem to point to a problem creating huge OSD windows - like 2700 by something - when the screen size was 1440 pixels wide (and the image 1440 pixels wide). This may be an edge case in choosing the OSD size to create.

And (sorry about the title), it seems to NOT be a telnet problem but a general renderer problem between 1.1.11 and 2.0.5.
It was just that all my controls use the telnet interface.