You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I run mpv on osx (using /Applications/mpv.app/Contents/MacOS/mpv) from terminal it works but I don't have any output in terminal, even if I type --help or --list-options - nothing.
If I add terminal=yes to config it shows up everything (before 0.90 it didn't have this problem).
I guess it's because of pseudo-gui profile which mutes terminal output, but still I think it should respond in terminal to core commands. And it doesn't work correctly selecing pseudo-gui when execured without mpv.app
Considering on newer versions of OSX the finder doesn't use a psn to start the application it could be not trivial to figure out who started the application. At the moment we use [[NSBundle mainBundle] resourcePath] which doesn't care where the application was started from (Finder or shell).
Shouldn't mpv.app explicitly pass --profile=pseudo-gui to the bin while when executed?
Maybe another approach is to set env variable like MPV_PROFILE â but these are just ideas, it's not critical anyway, I just spent some time to get the output
You have bundle_started_from_finder, which is false if an argument is given on the command line. That prevents the terminal output from being redirected to the log file. Could you also use that to tell it not to read the bundled mpv.conf file? It's not perfect because it will still happen if mpv is called from the comand line with no arguments, but maybe it's an improvement.
Activity
pigoz commentedon Jun 20, 2015
Considering on newer versions of OSX the finder doesn't use a psn to start the application it could be not trivial to figure out who started the application. At the moment we use
[[NSBundle mainBundle] resourcePath]which doesn't care where the application was started from (Finder or shell).troex commentedon Jun 20, 2015
Shouldn't mpv.app explicitly pass
--profile=pseudo-guito the bin while when executed?Maybe another approach is to set env variable like MPV_PROFILE â but these are just ideas, it's not critical anyway, I just spent some time to get the output
lucianmarin commentedon Jun 22, 2015
The manual says you should use
--no-configwhen testing. Using this mpv displays the terminal output.A mpv.conf is bundled within mpv.app which states
profile=pseudo-gui(disables terminal output).This is a non-issue and should be closed.
sumyungguy commentedon Dec 12, 2015
You have
bundle_started_from_finder, which is false if an argument is given on the command line. That prevents the terminal output from being redirected to the log file. Could you also use that to tell it not to read the bundled mpv.conf file? It's not perfect because it will still happen if mpv is called from the comand line with no arguments, but maybe it's an improvement.cocoa: bundle
cocoa: improve bundle handling
cocoa: improve bundle handling
osx: improve bundle handling