Skip to main content
Participant
October 6, 2022
Question

Export result/settings seriously wrong!?

  • October 6, 2022
  • 1 reply
  • 438 views

Hi, when I export a videofile from Rush Windows 10-version this is the result below. Original file from camera is 3840x2160 90kbit/s 60fps 461Mb.

 

This is the exported results from Rush. Note that High and Medium result is the same:
Export setting High: 3840x2160 12kbit/s 60fps 58Mb (expected file size 394Mb)
Export setting Medium: 3840x2160 12kbit/s 60fps 58Mb (expected file size 394Mb)
Export setting Low: 3840x2160 45kbit/s 60fps 222Mb (expected file size 232Mb)
Export preset Youtube: 3840x2160 40kbit/s 60fps 197Mb (expected file size 204Mb)

 

Someone else experience this problem?

/Marcus

This topic has been closed for replies.

1 reply

Participant
October 7, 2022

I've done some more testing and the kbit/s and filesize are all over the place. The original file from camera is 3840x2160 90kbit/s 60fps 461Mb but strange things happen when converting to 30fps. Suddenly the medium setting increase in quality and file size compared to when exported in 60fps. The low settings on the other hand decreases in quality and file size. The high and Youtube preset almost stays the same. 

@Adobe you need to fix the export settings and also give us the possibility to choose kbit/s manually.

 

Export setting: Result

High: 3840x2160 12kbit/s 60fps 58Mb

High: 3840x2160 11kbit/s 30fps 55Mb
Medium: 3840x2160 12kbit/s 60fps 58Mb

Medium: 3840x2160 47kbit/s 30fps 237Mb
Low: 3840x2160 45kbit/s 60fps 222Mb

Low: 3840x2160 21kbit/s 30fps 110Mb
Youtube: 3840x2160 40kbit/s 60fps 197Mb

Youtube: 3840x2160 40kbit/s 30fps 200Mb

Participating Frequently
October 7, 2022

I just found out something *very* interesting in this context. I just exported the same video file at the exactly same settings (4k@60fps at high bitrate) two times, once with hardware decoding/encoding acceleration activated in the settings and once without.

 

The results are:

With HW acceleration activated:
- Stream #0:0[0x1](eng): Video: h264 (High) (avc1 / 0x31637661), yuv420p(progressive), 3840x2160 [SAR 1:1 DAR 16:9], 49038 kb/s, 59.94 fps, 59.94 tbr, 60k tbn (default)

 

Without HW acceleration:
- Stream #0:1[0x1](eng): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709, progressive), 3840x2160, 113407 kb/s, 59.94 fps, 59.94 tbr, 60k tbn (default)

 

So as you can see, encoding *without* acceleration results in a more than 2x higher (!) bitrate than encoding *with* acceleration. Both exports use the same video codec (h.264). The version without HW acceleration also almost exactly corresponds to the calculated file size.

 

For me it seems that encoding with hardware acceleration seems to be buggy / resulting in a much less bitrate (and thus quality) than expected.

 

I think I will, for now, only encode with hardware acceleration deactivated, even if it takes longer, since I want to get the best quality before uploading to YT.

 

I do hope to hear back something from the Adobe team on this. This seems like a bug.

 

@Marcus_FPV - I'm pretty sure if you repeat your tests with HW acceleration off, you will get the real / correct file sizes. Maybe you want to give it a try.

 

Participant
October 7, 2022

Thanks for your input! I'll give it a try and report back.