#1 2008-05-08 04:02:11
- Koekenbakker
- New member
- Registered: 2008-05-08
- Posts: 3
- Expertise
SUPER(c) ffmpeg parameters
Currently we are creating an application that uses FFmpeg. We are using your SUPER (2008 build 30) application to test various video conversions, which works great! However we now have two questions:
1) Is there any way that we can see the FFmpeg command line string that SUPER generates? We were hoping that SUPER would show the final command it uses to actually decode/encode videos using FFmpeg.
2) We can't use WMV3 files as input (invalid input) when using the FFmpeg that came with SUPER (2008 build 30). However if we drag the same file to SUPER, it manages to convert it. How does SUPER read WMV3 files without FFmpeg throwing an error?
Last edited by Koekenbakker (2008-05-08 04:25:24)
Offline
#2 2008-05-12 10:44:47
- jjones3535a
- New member
- Registered: 2008-05-12
- Posts: 1
- Expertise
Re: SUPER(c) ffmpeg parameters
Yes, I was wondering the exact same thing:
Is it possible to see the command line string generated by SUPER before passing it on to FFMPEG?
Last edited by jjones3535a (2008-05-12 10:45:02)
Offline
#3 2008-05-20 02:07:06
- Koekenbakker
- New member
- Registered: 2008-05-08
- Posts: 3
- Expertise
Re: SUPER(c) ffmpeg parameters
If bumping isn't allowed, I'm sorry. It's been two weeks; is there any news on this subject, or did it slip through the maze of those who watch the forum like a hawk? 
Offline
#4 2008-05-20 02:42:28
- 96crypt_mod
- Moderator
- Registered: 2006-08-02
- Posts: 2051
- Expertise
Re: SUPER(c) ffmpeg parameters
Offline
#5 2008-05-20 02:50:25
- Koekenbakker
- New member
- Registered: 2008-05-08
- Posts: 3
- Expertise
Re: SUPER(c) ffmpeg parameters
I was under the impression that when I selected "FFmpeg" as an encoder, it would use only that. Apparantly SUPER chains/pipes other processes when needed, which would explain the trouble we have with WMV11 files when trying it with FFmpeg alone.
Thanks for your answer!
Offline
