New Mediacoder with CUDA problems.

[Stears555]

Hello!

I use windows x64 version of the newest mediacoder (build 5348).

The cuda compressor doesn't when the FFMPEG is the video source. The error-message is "No file outputted"

The other problem is the bitrate, I chose AVISYNTH as video source, CUDA encoder constant bitrate 16Mbit/s or 9Mbit/s, but It encoded the video with 16Kbyte/s(!!!) and 9Kbyte/s(!!!).

Thank you for your reply!


The test video-file is located here (67 Mbyte only) http://dictaphone.atw.hu/mozdony.MTS

[aedipuss]

this isn't the place to report your problems with the program. mediacoder has it's own website and forum for reporting bugs.

[Stears555]

Wrong. I think it is an ffmpeg problem. The bugs multiplied many times in the new versions of ffmpeg.
Many softwares are simple Graphical user interfaces, and they use ffmpeg, instead of doing a real own motor for their software. It is caused by laziness.

[aedipuss]

i checked the latest x64 version and it works fine with ffmpeg used as source and creates working output video. so most likely you should leave source set to auto as you don't seem to know what you're doing and maybe the proper decoder will be selected for the source you are using.

[Stears555]

i checked the latest x64 version and it works fine with ffmpeg used as source and creates working output video. so most likely you should leave source set to auto as you don't seem to know what you're doing and maybe the proper decoder will be selected for the source you are using.

Are you sure?
Read this: http://forum.mediacoderhq.com/viewtopic.php?f=2&t=12420

[poisondeathray]

Wrong. I think it is an ffmpeg problem. The bugs multiplied many times in the new versions of ffmpeg.
Many softwares are simple Graphical user interfaces, and they use ffmpeg, instead of doing a real own motor for their software. It is caused by laziness.

How can it be a ffmpeg problem?

ffmpeg (the binary) works fine with your file. The newest versions even appear to have fixed the "PsF" framerate bug read as the field rate (29.97 read as 59.94, 25 read as 50) . Which "multiplied bugs" are you referring to ?

The problem is definitely mediacoder or cuda, or user error, or perhaps they are using outdated versions of ffmpeg binary

[Stears555]

Wrong. I think it is an ffmpeg problem. The bugs multiplied many times in the new versions of ffmpeg.
Many softwares are simple Graphical user interfaces, and they use ffmpeg, instead of doing a real own motor for their software. It is caused by laziness.

How can it be a ffmpeg problem?

ffmpeg (the binary) works fine with your file. The newest versions even appear to have fixed the "PsF" framerate bug read as the field rate (29.97 read as 59.94, 25 read as 50) . Which "multiplied bugs" are you referring to ?

The problem is definitely mediacoder or cuda, or user error, or perhaps they are using outdated versions of ffmpeg binary

Was your output 16Kilobit/s instead of 16Megabit/s?

[Stears555]

Wrong. I think it is an ffmpeg problem. The bugs multiplied many times in the new versions of ffmpeg.
Many softwares are simple Graphical user interfaces, and they use ffmpeg, instead of doing a real own motor for their software. It is caused by laziness.

How can it be a ffmpeg problem?

ffmpeg (the binary) works fine with your file. The newest versions even appear to have fixed the "PsF" framerate bug read as the field rate (29.97 read as 59.94, 25 read as 50) . Which "multiplied bugs" are you referring to ?

The problem is definitely mediacoder or cuda, or user error, or perhaps they are using outdated versions of ffmpeg binary

Read this: http://forum.mediacoderhq.com/viewtopic.php?f=2&t=12420

[poisondeathray]

Wrong. I think it is an ffmpeg problem. The bugs multiplied many times in the new versions of ffmpeg.
Many softwares are simple Graphical user interfaces, and they use ffmpeg, instead of doing a real own motor for their software. It is caused by laziness.

How can it be a ffmpeg problem?

ffmpeg (the binary) works fine with your file. The newest versions even appear to have fixed the "PsF" framerate bug read as the field rate (29.97 read as 59.94, 25 read as 50) . Which "multiplied bugs" are you referring to ?

The problem is definitely mediacoder or cuda, or user error, or perhaps they are using outdated versions of ffmpeg binary

Read this: http://forum.mediacoderhq.com/viewtopic.php?f=2&t=12420

Maybe you should have read it? That's not a ffmpeg issue

[Stears555]

Mediacoder didn't solved the fps problem of psf videos. Mediacoder could use PSF video only with coreavc source with avisynth. Coreavc was the only possibility to transcode 25psf into a real 25p video in mediacoder.

[aedipuss]

i checked the latest x64 version and it works fine with ffmpeg used as source and creates working output video. so most likely you should leave source set to auto as you don't seem to know what you're doing and maybe the proper decoder will be selected for the source you are using.

Are you sure?
Read this: http://forum.mediacoderhq.com/viewtopic.php?f=2&t=12420

<sigh> .

[Stears555]

finally: The mediacoder proved unable to use its new cuda5 encoder.... (creating a 16kbit/s video instead of a 16Mbit/s video )))))

[poisondeathray]

Mediacoder didn't solved the fps problem of psf videos. Mediacoder could use PSF video only with coreavc source with avisynth. Coreavc was the only possibility to transcode 25psf into a real 25p video in mediacoder.

Why not use other software then ? Coreavc isn't the only possibilty , couldn't you use ffdshow (free) . Other free software certainly works

Did you read what I wrote above?

New ffmpeg binaries (from 2013) have fixed the problem with field rate . If you use mediacoder, you should request mediacoder developer to update their software

[Stears555]

Mediacoder didn't solved the fps problem of psf videos. Mediacoder could use PSF video only with coreavc source with avisynth. Coreavc was the only possibility to transcode 25psf into a real 25p video in mediacoder.

Why not use other software then ? Coreavc isn't the only possibilty , couldn't you use ffdshow (free) . Other free software certainly works

Did you read what I wrote above?

New ffmpeg binaries (from 2013) have fixed the problem with field rate . If you use mediacoder, you should request mediacoder developer to update their software

"Why not use other software then ?" Because, when they answered my mails, they promise everything and do nothing...

I correct: Coreavc with avisynth is the only possibility in mediacoder, which can transcode a 25psf video into a real 25p video.

"New ffmpeg binaries (from 2013) have fixed the problem with field rate"


Oh really? Can you offer a software which can transcode my 25PSF MTS videos into a real 25PSF MP4 video with direct-stream-copy ? Most softwares trancode them into 50PSF MP4 (((((

[poisondeathray]

I correct: Coreavc with avisynth is the only possibility in mediacoder, which can transcode a 25psf video into a real 25p video.

Can't mediacoder use ffdshow as the directshow decoder ? ffdshow definitely works correctly with avisynth , directshowsource for these types of files (I'm suggesting a free alternative to CoreAVC)

Oh really? Can you offer a software which can transcode my 25PSF MTS videos into a real 25PSF MP4 video with direct-stream-copy ? Most softwares trancode them into 50PSF MP4 (((((

Not for direct stream copy, it will be the same as the original (25p, encoded interlaced) - ie it's the responsibility of the next decoder to see if it decodes it properly

"Transcode" implies re-encode (technically there is a difference between transcode and re-encode), but the point is neither transcode or re-encode means "direct stream copy"

But decoding bug is fixed (no longer reads the field rate), thus when you re-encode the files are not 50, but 25 . No decoding is done when you use direct stream copy - do you see the difference ?

[aedipuss]

finally: The mediacoder proved unable to use its new cuda5 encoder.... (creating a 16kbit/s video instead of a 16Mbit/s video )))))

why would you even try to use constant bit rate mode? it's a waste of space, and like cq mode i don't think it's even supported by cuda.

[Stears555]

I correct: Coreavc with avisynth is the only possibility in mediacoder, which can transcode a 25psf video into a real 25p video.

Can't mediacoder use ffdshow as the directshow decoder ? ffdshow definitely works correctly with avisynth , directshowsource for these types of files (I'm suggesting a free alternative to CoreAVC)

Oh really? Can you offer a software which can transcode my 25PSF MTS videos into a real 25PSF MP4 video with direct-stream-copy ? Most softwares trancode them into 50PSF MP4 (((((

Not for direct stream copy, it will be the same as the original (25p, encoded interlaced) - ie it's the responsibility of the next decoder to see if it decodes it properly

"Transcode" implies re-encode (technically there is a difference between transcode and re-encode), but the point is neither transcode or re-encode means "direct stream copy"

But decoding bug is fixed (no longer reads the field rate), thus when you re-encode the files are not 50, but 25 . No decoding is done when you use direct stream copy - do you see the difference ?

I know the diference between direct-stream copy and reencoding/transcoding since the late 1990s.

My experience with video transcoding etc... started after I bought an early rudimentary TV-tuner in 1998.


My problem is the direct-stream transformation of transport stream formats into mp4, and its frame rate / field rate confusion.

[Stears555]

Can you see it?

[poisondeathray]

I know the diference between direct-stream copy and reencoding/transcoding since the late 1990s. My experience with video transcoding etc... started after I bought an early rudimentary TV-tuner in 1998.


My problem is the direct-stream transformation of transport stream formats into mp4, and its frame rate / field rate confusion.

For stream copy - there are still problems with ffmpeg's MP4 muxer, but you can mux into MKV and it will be 25p (used to be 50p with old ffmpeg)

However, you still have problems with "PsF" or interlaced encoding and flags, because it's a stream copy (eg if you upload it to youtube for example, it will still deinterlace)

(BTW, I'm only referring to ffmpeg only, not any other program)

[Stears555]

I know the diference between direct-stream copy and reencoding/transcoding since the late 1990s. My experience with video transcoding etc... started after I bought an early rudimentary TV-tuner in 1998.


My problem is the direct-stream transformation of transport stream formats into mp4, and its frame rate / field rate confusion.

For stream copy - there are still problems with ffmpeg's MP4 muxer, but you can mux into MKV and it will be 25p (used to be 50p with old ffmpeg)

However, you still have problems with "PsF" or interlaced encoding and flags, because it's a stream copy (eg if you upload it to youtube for example, it will still deinterlace)

(BTW, I'm only referring to ffmpeg only, not any other program)

That's why I use ffv1 codec to upload full HD youtube video content. It has enormous size, and the upload slow down my internet connection for days (((((

[aedipuss]

[Attachment 15685 - Click to enlarge]
Can you see it?

haha - yes i see it and if you check cq mode and other 264 modes are also there. doesn't mean they work for cuda. you're being an ass about a fine quality free program. if want quality encodes don't use cuda, it sucks and is only known for speed. for quality mp4 only use the h264 encoder.

[Stears555]

[Attachment 15685 - Click to enlarge]
Can you see it?

haha - yes i see it and if you check cq mode and other 264 modes are also there. doesn't mean they work for cuda. you're being an ass about a fine quality free program. if want quality encodes don't use cuda, it sucks and is only known for speed. for quality mp4 only use the h264 encoder.

I've never stated that I used mediacoder or CUDA for good quality transcoding.
Do you want to see a good Quality web-video?

Than see my short flash video (only 8mbit/s , but it's much better than Youtube!!!)


http://dictaphone.atw.hu/mozdony/mozdony.html


My only problem is the lack of HW acceleration in the web player. I've a Core I7 CPU, however I must think for people, who have slower CPUs.

[Stears555]

Did you see it Aedipuss ?

[aedipuss]

yes stears. 8mbps flv is nice and you must have a very fast server.

i'd recommend a tripod and please learn to pan slowly. you don't want people to barf.

[themaster1]

It's probably just a colorspace issue, cuda don't work with yv12 but I420(change it in the picture tab) at least with my card, i'm using an old build by the way, 5210 on win7 x64

[Stears555]

It's probably just a colorspace issue, cuda don't work with yv12 but I420(change it in the picture tab) at least with my card, i'm using an old build by the way, 5210 on win7 x64

Hi!

Sorry, it didn't help.

I can't get higher video bitrate than 16kilobit/s instead of 16Mbit/s !!!

[aedipuss]

instead of expressing great delight at finding a possible mediacoder bug here, why not post a message on mediacoder's bug tracking forum? it makes much more sense and might actually be useful to them.