The VideoLAN Forums

Hello,

I'm running OS X 10.5.2 with a dual screen setup. I like to play my movies on full screen on my external screen. On 0.8.6d, this worked perfectly. On 0.8.6e and 0.8.6.f however, the full screen window will always appear on my main screen. I tried putting the playlist on the external screen before going to fullscreen (this is the method I used on 0.8.6c) but this also doesn't work.


I'm just reporting this bug here cause I like VLC
If you need any more info, feel free to ask

greetz,
Jeroen

How convenient, this is the EXACT problem I joined to post about.

My problem is the same as Sjoekie. I have multiple screes and with d I was able to drag the video to the screen I want it on and make it full screen for that monitor. e and f break that feature and only display full screen on the main monitor.

I like the changes made in e and f but the multi-screen problem is always a deal breaker.

I have found a workaround that works but seems to reset itself quite often for no apparent reason. If you go to the Video Device submenu under the Video menu and select "default" it will show fullscreen on whichever monitor the video is currently playing on. The real problem is that the selection does not stay set.

finally, it's been fixed!!! yay... check out the new nightly build: http://nightlies.videolan.org/build/mac ... l/?C=M;O=D. Although it's a bit unstable and some options have not been added

Hehe, tnx but I'll just wait for the 0.8.6g version... For now I'm fine with d

Glad to see they are working on it

Okay, its not a bug we just needed to select the screen we want.

In the menus: Video->Video Device->Screen 1 (or 2)

Works fine in f.

Hi, i dono if you guys are concern with this as much as i have and it's somewhat related to the topic.

is there anyway to turn off the my iMac's screen while i watch a movie in my secondary screen?

i joined EXACTLY for that point, i started my show, hit ctrl f like always and it shows up on my laptop instead of the tv, even if set to screen 2
the only way is to drag the video on screen 2 before, i real PITA
also the fade in fade out is pretty annoying, hope it gets fixed too

Okay, its not a bug we just needed to select the screen we want.

In the menus: Video->Video Device->Screen 1 (or 2)

Works fine in f.

Hello everybody.

I've installed 0.8.6f to see if the fullscreen problem is fixed as claimed in the release-notes.

Indeed, if you have a video playing (in a window, on screen 1) you can select screen 2 as you explained above. But the menu is greyed-out when no video is playing, and also VLC forgets this selection when you quit. It also forgets this selection when you go from fullscreen to window and then quit the video that is playing. The next video you open, the selection is back to screen 1.

The sad thing is: this (video starts fullscreen on 2nd monitor) works with 0.8.6c with no problems.

Also: I tried the latest nightly built to see if there where any changes. And yes, there is a big change in behaviour: the video now opens fullscreen on screen 2, but screen 1 turns black! Not good.

Anyway, back to 6c I think, that was for me the last version that did what I wanted. Or maybe I'm not seeing the obvious solution?

My config: MacBook Pro 2GHz Core Duo, OS X 10.4.11.

Thanks,
Joe

Yes, f did fix the problem but having to select the screen from the menu got too annoying so I'm back to using d again.

I agree, fading the other screen to black does not work. I like having a TV/Movie running in one screen and working on the other. If I wanted the screen black I'd just turn the monitor off entirely.

Yes, f did fix the problem but having to select the screen from the menu got too annoying so I'm back to using d again.

I agree, fading the other screen to black does not work. I like having a TV/Movie running in one screen and working on the other. If I wanted the screen black I'd just turn the monitor off entirely.

In h you can restore the old behaviour temperally by selecting Video->Video Device-> Default in the menu. However, vlc doesn't remember this after a restart. So still not fixed 100%.

Still, I'm glad to see they are working on it... Almost there

in another thread i read that it will be fixed with 0.9.0 but when is that gonna happen?