Which programs work for you in WINE?

[usrbinmadness]

Please list the programs (video/audio tools only on topic with this site) that work for you in WINE with the following information (copy/paste the following into your post and complete the information:)

1. Program name and version:
2. Program website (url link):
3. Does the program work 100% in WINE? (yes/no):
4. If "no" in #3, what doesn't work?:

I'm posting this because I feel a list of WORKING programs would be very useful for those of us here who use Linux, instead of posting several different threads here and there with different programs that work or don't work in WINE. Thanks for reading, I look forward to all positive responses.

[jggimi]

Have you seen this (http://forum.doom9.org/showthread.php?s=&threadid=55377&highlight=wine) thread?

[usrbinmadness]

Originally posted by jggimi
Have you seen this (http://forum.doom9.org/showthread.php?s=&threadid=55377&highlight=wine) thread?

Hi jggimi, thank you for pointing out that thread, I appreciate it. However, that thread is around six months old, and:

my purpose for this thread is not so much for a lengthy discussion on WINE and several related subjects, but instead for people to list (copy/pasting the info I provided and completing it) the programs that they currently use in WINE (related to video/audio programs discussed on this site).

While the other thread(s) you pointed out are useful, they are dated and contain troubleshooting and other discussions which differ from:

my goals for this thread, which is to be a list for people to clearly and simply see the programs other users here are using in WINE on their Linux system without the thread being bogged down with discussions and opinions.

Everyone who's reading this, please continue in this thread by replying to my first post, listing the programs that work for you in WINE. Thank you for reading.

[albertgasset]

Today I've managed to use Avisynth in Wine, It doesn't work at 100%, sometimes it crashes without showing any message: if the script is incorrect or when loading some AVIs. But these AVIs can be opened through VirtualDub's frameserving system (create the .vdr and open it in Avisynth script).

Software I use in Wine:

Avisynth 2.5.5 alpha 030304 (www.avisynth.org)
VirtualDub 1.5.4 (www.virtualdub.org)
Xvid 1.0_rc4 (Koepi's release at http://koepi.roeder.goe.net/)
ffvfw 20031117 (version from http://cultact-server.novi.dk/kpo/avisynth/avs_cvs.html)

I've not tested them too much (only today doing some editing), but they seem to work well, except for the problems in Avisynth.

I've also tried ffdshow, but it crashes ("api function blahblah not implemented yet", maybe in a future version of Wine).

[mikeX]

I think one should also mention whether he is using an existing windows installation or wine's native dll's

atm I've managed to use ChapterXtractor (http://christophe.paris.free.fr/main.php3) i think the site is down though, you can get it here at doom9 as well
and vsrip (http://sourceforge.net/projects/guliverkli)

I'm using wine's fake windows

If anyone knows of a native linux application for extracting chapter information I would appreciate it :)

[Inssomniak]

tcprobe (part of the transcode package) will pull chapter times and blocks from a DVD.

lsdvd -c pulls a similar list.

there are other tools to actually extract the chapters too, not just the information.

I know this has nothing to do with wine, but someone asked.:) I do all my DVD's completely linux native without the help of wine or win4lin or vmware.

[KpeX]

I think this thread is a very good idea, with a few additions. Make sure to mention which version of wine
which version of windows you're emulating with wine
installation method / other config file changes if applicable
program version
any additional steps to get the program to work (missing DLLs, special setup, etc.)
mention the program's functionality issues if there are any

wine setup
wine version: current CVS (essentially wine-20050310 at the moment) The windows version emulated is win2k, no other changes to wine config. wine was installed from source as described in the FAQ.

working programs
AviSynth 2.53: installer worked fine, no additional steps

QuEnc 0.5*: needed to copy MFC42.dll from windows install to the .wine/drive_c/system folder, after that QuEnc works fine.

XviD 1.0.3: I needed an mpeg-4 decoder for avisynth, the 1.0.3 installer from koepi's site ( XviD-1.0.3-20122004.exe ) worked fine.

DVD Shrink 3.2.*: No additional steps

DVD Decrypter (3.5.*): Requires SCSI emulation to be set up, see the wine & dvd decrypter thread (link is in the FAQ).

PULLDOWN 0.99D: No additional steps, works from commandline: wine PULLDOWN.EXE source.m2v target.m2v

BeSweet 1.5b*: Works great with BeLight 0.2*, unzip besweet & belight to the same directory and fire up belight.

Exact Audio Copy 0.95pb*: EAC only detects a drive in wine if a CD is mounted in it. This is a problem since normally one doesn't mount Audio CDs. The solution is to have data CDs mounted in all drives you want to use in EAC when you run it the first time. EAC's first run wizard should then detect the drives and help you configure them. Then every time you start EAC make sure a data CD is mounted in your CD drive, then after EAC starts eject the data CD and insert an audio CD which EAC should then detect.

lame 3.96.1: For use in EAC. Eac doesn't pop up a commandline window like in windows, but the lame.exe encoder still works fine.

MPEG audio collection 2.9*: MAC usually has visual issues the first time you run it (jittery display, non-responsive menus). You can usually solve the problem by running mac.exe, exiting, and re-running.

[Johnny_Deep_Down_Below]

One simple question: Why the hell do you run a linux-system, if you only use software written for Microsoft Windows Operating Systems????

[KpeX]

You've completely misunderstood the purpose of wine. Although linux as a desktop OS is quickly gaining popularity there are still a few programs that don't have native linux equivalents. The above list is an example of this: all the programs I listed either have no native linux counterpart, or are dependencies of one of the other programs.

The purpose of threads like this (and one of the purposes of wine's existence) is to help former windows users migrate to a *nix environment. I don't "only use windows programs", I use native programs for roughly 98% of tasks and I find new innovative native software that has no windows counterpart every day.