Adjust target bitrate on exporting

[j9036832]

Hi all,

Updated to latest Premiere Pro, and since then cannot 'fine tune' the target bitrate when exporting. 

Rolled back to previous version, and same thing. I assume one of my preferences has been changed, and searching for the answer has given me nada, so here I am.

Previously:

I could input a specific bitrate, say 1.2, or 3.65, etc etc

I could also use the slider that would increment in between whole numbers.

Now:

Slider goes 1, 2, 3, 4.... 18,19,20 etc

Manually entering a bitrate that isn't a whole number sees the bitrate jump to the nearest whole number.

How do I get it so I'm able to set the bitrate between whole numbers again?

Many thanks in advance.

[Ann Bens]

which export setting are you using

for example H.264 vbr1 i can set the target to 2 digit after the dot.

[j9036832]

Hi Ann,

seems there is a known bug, as upon posting the question some thread suggestions displayed here, including:

https://community.adobe.com/t5/premiere-pro-discussions/decimal-number-in-quot-bitrate-settings-quot...

I've reverted to 24.0 (I must have skipped an update or two), but still have the same issue. 

fwiw, export setting is h.264 vbr1, using win10. 

A workaround is going to media encoder instead of direct export, which is a pain for what I mainly use PremierePro for, but that kinda sums up the product. Appreciate your taking the time to answer, thankyou for that. I'll just do the workaround, when it comes to adobe's products, it's usually easier 🙂

[Ann Bens]

When you type in the numbers make sure the text field is empty.

Just typed this in

[j9036832]

My bad, I should have been more specific:

It's h264, but within a custom preset I have saved (so uses that as default export setting).

If I choose a different preset, that *isn't* a custom preset (so 'High Quality 1080p HD' and so on, the standard presets), THEN I can use the slider, or type in my target bitrate, without being confined to whole numbers.

It would seem to be a new bug that clashes with custom presets. That's my best guess anyway.

Was working fine until I updated, and I've tried a couple of earlier versions but get the same problem, I'm not sure what version I was using before I updated which is a bummer. 

[Ann Bens]

Make the custom preset again.