Copy link to clipboard
Copied
Hi Adobe, all,
can we please get custom bitrate settings when we export video? My source video is 4k@60fps@150Mbit. At the highest export setting the Android app tops out at 4k@60fps@60Mbit. Windows Desktop version is a bit better at 4k@60fps@112Mbit. Even the really inferior (when it comes to User Interface) GoPro Quik app manages to do 4k@60fps@95Mbit on my Android and it even supports h.265.
I really want to use Premiere Rush, because I like its user interface, but with the existing export settings I already loose substantial quality even before uploading it to YouTube. That's not acceptable for me.
Please enable/support custom bitrates and you will have a winner here š
Many thanks and all the best,
Michael
Copy link to clipboard
Copied
I just tried it on my Windows Laptop (Surface Pro) and it's getting more confusing. The Laptop will - at the same settings - also only give me 4k@60fps@60Mbit - the same as with my Android phone! I would have expected it to give me the same 112Mbit as my other Desktop PC. That is confusing š
Copy link to clipboard
Copied
Also have similar problems. Really like Rush but this makes it unusable for me unfortunately. Please Adobe, fix this or at least give us the possibility to decide kbit/s.
Copy link to clipboard
Copied
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.
Copy link to clipboard
Copied
I just found out one more thing regarding this bug.
It only happens on my Surface Pro Laptop, not on my regular Desktop PC. On my regular Desktop PC the bitrate and corresponding file sizes are identical, no matter if HW acceleration is on or off. And they correspond to the estimation of the program. The difference here is that my Desktop PC has dedicated graphics (NVIDIA 1080), while my Surface Pro Laptop only has integrated graphics.
So this bug may be specific to computers with integrated graphics.
Maybe this helps the dev team when / if they try to reproduce this bug.
All the best, Michael
Copy link to clipboard
Copied
... aaaand another update.
It seems Premiere Pro has the same issues with too low bitrate when using HW acceleration:
https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/44368392-issue-poor-hardwar...
In the case of the link above it is connected to Apple devices, but as we saw above it happens on Windows machines as well.
This unfortunately also means that Rush is unuseable for me on Tablets and Smartphones, since one cannot turn off HW acceleration there. So you will always get the low bitrate renders there, reducing the quality of your videos.
Copy link to clipboard
Copied
My last one for today. Sorry for being so noisy about this today.
But I just researched this some more and it seems to be a well known problem, not only for Rush but for Premiere Pro as well, which has not been fixed since a long time.
Here is a video from 3 years ago about exactly this issues which we seem to have "rediscovered" now:
https://www.youtube.com/watch?v=DXWWJvuexqE&ab_channel=PugetSystems
For me that means no editing on mobiles / tablets and only using software encoding on PCs / Laptops in order to not reduce the quality of my videos.