On 1/22/11 11:10 PM, Jon Christopher wrote: > The windows command would be something like > > comskip.exe --ini="/path/to/file.ini" /path/to/recording.mpg > > where recording.mpg is going to vary. This script will be invoked > from a python script, which is > in turn triggered by an applescript triggered from EyeTV. Surely, there's a Mac program that skips commercials. Why bother with Wine at all? Whenever there's a native version, our advice is usually "use the native version instead of mucking around with Wine." > I did some more poking around, and found a reference to ttydrv in the > wine.conf manual page: > > format: """GraphicsDriver""=""<x11drv|ttydrv>""" > default: "x11drv" > Tells Wine which graphics driver to use. Normally you'd want to use > x11drv (for X11). In case you want to run programs as text console/TTY > only without having Wine rely on X11 support, then use ttydrv. > > It *looks* like I should just be able to set wine to use ttydrv and > not have it fire up X. However, I don't have a wine.conf file (or a > ~/.wine/config file). I tried creating one containing the relevant > commands, but invoking wine still started up X11.app. That's because they don't exist anymore. Ever since Wine got registry support, all of Wine's settings have been stored in the registry. Also, the TTY driver is gone, too, so setting the GraphicsDriver won't do you any good. What we really need is for someone (me, possibly) to finish up quartzdrv. This is the driver that uses native Mac OS X graphics instead of X11 graphics. With quartzdrv, you won't need X11 anymore. Chip
