Not enough items when autocrafting problem

[AlexDiego123]

Describe the bug

Hi, I noticed in the Statech Industry modpack that AE2 doesn't put the correct number of redstone in the steam blast furnace when trying to autocraft molten redstone, causing it to lock up after some time because it thinks that it's making molten redstone but the steam blast furnace is empty. For example, it should put 18 of redstone in the Steam Blast Furnace to craft 2 buckets of molten redstone, instead it puts exactly half the redstone it needs. This problem doesn't happen if you put a chest next to the ME pattern provider, only when it goes into a Steel Item Input Hatch. How do I fix this?

How to reproduce the bug

In the lastest Statech Industry modpack, create a pattern that autocrafts 111MB of molten redstone with 1 redstone and then put it in an ME pattern provider next to the item input hatch of the Steam Blast Furnace of the mod Modern Industrialization.

Expected behavior

When autocrafting, AE2 has to put the correct number of redstone in the Steam Blast Furnace to autocraft the correct amount of molten redstone that it has to craft, for example for every 2 buckets of molten redstone, it should put 18 redstone in the Steam Blast Furnace, but instead it puts exactly half of the redstone it needs for some reason, even if the UI that prompts you to start an autocrafting says that it will put 18 redstone but it puts 9 for some reason. Then it locks up because it doesn't craft enough molten redstone but thinks it's doing it right.

Additional details

I know that this issue only happens when the ME pattern provider outputs items in the Steel Item Input Hatch of the Modern Industrialization mod, but i decided to post this issue anyway in case someone that played Statech Industry knows how to solve this and sees this issue.

Which minecraft version are you using?

1.19

On which mod loaders does it happen?

Fabric

Crash log

https://pastebin.com/Z3jSZ0Nv

[Technici4n]

Are you sure that this is not an issue with one of the patterns you encoded? Could also be a 1.19-exclusive bug.