What do people use nowadays to put errant programs where they belong?

"Lionel Muller" wrote

| I did use DVDFlick instead, but what DeVeDe does in 2 hours, DVDFlick
takes
| 8 hours, so, the main reason I use DeVeDe is because the program works,
and
| it's the same on Linux as it is on Windows (so I don't have to learn
| another GUI).
|

An update on this. Yesterday I tried installing DeVeDe
for XP. I haven't tried the 7/10 version. The install is
3x the size of DVD Flick. 122 MB! Then I couldn't get it
to start. There seems to be some kind of funky, multiple
EXE thing going on. Apparently it's not entirely a kosher
Windows EXE. It needs python libraries to run.
I run the main EXE or the launcher and nothing happens.
But the main EXE is running, along with iconv.exe and
mplayer.exe. Yet nothing is onscreen. So I kill devede.exe
and then the program comes up.

It was fast, but then the ISO never showed up. So I
don't know what it actually did. And that was the last time
I managed to get the window to appear.

Maybe it's faster than DVD Flick. Maybe it's really a
Linux program that's only partially adapted to Windows.
I don't know. But DVD Flick works fine, so I think I'll
stick with that.

Mayayana wrote:
"Lionel Muller" wrote

| I did use DVDFlick instead, but what DeVeDe does in 2 hours, DVDFlick
takes
| 8 hours, so, the main reason I use DeVeDe is because the program works,
and
| it's the same on Linux as it is on Windows (so I don't have to learn
| another GUI).
|

An update on this. Yesterday I tried installing DeVeDe
for XP. I haven't tried the 7/10 version. The install is
3x the size of DVD Flick. 122 MB! Then I couldn't get it
to start. There seems to be some kind of funky, multiple
EXE thing going on. Apparently it's not entirely a kosher
Windows EXE. It needs python libraries to run.
I run the main EXE or the launcher and nothing happens.
But the main EXE is running, along with iconv.exe and
mplayer.exe. Yet nothing is onscreen. So I kill devede.exe
and then the program comes up.

It was fast, but then the ISO never showed up. So I
don't know what it actually did. And that was the last time
I managed to get the window to appear.

Maybe it's faster than DVD Flick. Maybe it's really a
Linux program that's only partially adapted to Windows.
I don't know. But DVD Flick works fine, so I think I'll
stick with that.

At 122MB, that seems a bit bigger than the 49MB version
I could find a reference to.

It uses a bunch of helper EXE programs to do the conversion.

It has some EXE it uses to make ISO files.

You are likely required to be a "bit mechanic", go
over the main file and see whether you've satisfied
all the helpers. Either these were in your file,
or you're expected (as a Windows user) to go and get them.

"mplayer.exe"
"mencoder.exe"
"dvdauthor.exe"
"vcdimager.exe"
"iconv.exe"
"mkisofs.exe" or "genisoimage.exe"
"spumux.exe"

That's from some text file I found on my disk here.

There is a newer version (devedeNG), which runs in Linux only.
The author claims, rewritten for a newer version of Python,
which would be mostly pointless.

You could always test the Linux version. In a VM,
using VirtualBox or the like. Yes, there's a bit of
a learning curve. You can stop any time, before
suffering too much hair loss :-)

To make a fair test of that here, I'd need some idea
on what the "input files" look like. My inputs
here are usually some sort of uncompressed AVI
files (from my WinTV capture card). That's not
likely to be the format of your starting materials.

And your conversion could go faster, if Intel QuickSync
on your processor is available (this is used during
decode of source in some cases). I don't have any
samples of QuickSync here, so that's a disadvantage
if I'm having a benchmark contest.

Paul

"Paul" wrote

|
| You are likely required to be a "bit mechanic", go
| over the main file and see whether you've satisfied
| all the helpers. Either these were in your file,
| or you're expected (as a Windows user) to go and get them.
|

Those are all in the package. The need to track
down support files was for an older version. It's a
full install. It's supposed to work. It doesn't.

| You could always test the Linux version. In a VM,
| using VirtualBox or the like.

Yes. I could also move to California. Or I
could take up stamp collecting. But the task
was to write some MP4s to a DVD. That hardly
warrants installing a new OS.

Mayayana wrote:
"Paul" wrote

|
| You are likely required to be a "bit mechanic", go
| over the main file and see whether you've satisfied
| all the helpers. Either these were in your file,
| or you're expected (as a Windows user) to go and get them.
|

Those are all in the package. The need to track
down support files was for an older version. It's a
full install. It's supposed to work. It doesn't.

| You could always test the Linux version. In a VM,
| using VirtualBox or the like.

Yes. I could also move to California. Or I
could take up stamp collecting. But the task
was to write some MP4s to a DVD. That hardly
warrants installing a new OS.



It took me a while to find a source AVI to use,
but I finally kicked off a DevedeNG run. It's
in the Ubuntu package manager.

It's doing single-pass conversion. I selected "NTSC"
in the GUI, and notice that it has selected a target
of "pal-dvd" instead of "ntsc-dvd". That might set
the frame rate to 25 instead of 30 or something.

ffmpeg -i source.avi -i source.avi -map 1:0 -map 0:1
-vf pad=720:540:0:30:0x000000,fifo,scale=720:576
-y -target pal-dvd -sn -g 12 -bf 2 -strict 1
-ac 2 -aspect 1.3333333333333333 -s 720x576
-trellis 1 -mbd 2 -b:a 224k -b:v 3796k
/tmp/movie/movies/movie_0.mpg

Time = 45 minutes
CPU cores = about 2.8 cores.
Tool = ffmpeg, instead of mplayer

I ran it from a LiveDVD (no install).

I'll check the quality later.

Paul