Type-IIx
Well-known Member
@hudson98 reading over my own contradictory post here has made me recognize that my brain is quite fried from a lot of mental work over the last 24 +/- hours. I'll come back to this, but let me reframe this as such - a hormonally enhanced individual that has abundant type I fibers can use different methods involving a higher number of contractions to achieve sarcoplasmic (i.e., this has an enzymatic basis and comes and goes more rapidly) than an individual with more abundant type II fibers (i.e., this latter individual can achieve greater growth of contractile elements that persist on a longer time-frame).Practically, not really. Type I fibers (slow twitch) just do not have much growth potential at all, and there's no evidence of type I -> II isoform transitions, but rather transitions occur within the broad types (e.g., type IIX -> type IIA).
Heavy load training (e.g., 1 - 3 RM) augments strength mostly by neural mechanisms (e.g., increased voluntary activation) rather than (if at all) by increased fiber size.
Sufficient loads (i.e., > 60% 1RM) to induce hypertrophy rely basically on growth of type II fibers, as these are really all that grow by resistance training.
If one is a predominantly slow twitch phenotype, they're basically fucked after a certain point, regardless of volume.
Now granted, there are myriad mechanisms that contribute to hypertrophy of skeletal muscle (here I've focused perhaps myopically on myofibrilar hypertroophy) aside from resistance training. AAS contribute to hypertrophy of slow twitch fibers and fast twitch fibers in relative equal proportion.
My point is that modulation of training volume and rep ranges (i.e., %1RM) should really be dictated by recovery & training status/age, as well as the task at hand (e.g., myofibrillar versus sarcoplasmic [i.e., noncontractile elements, that type I fibers are more abundant in] hypertrophy).
The former individual may indeed have higher training volumes.
Yet, the view that increasing volume benefits slow twitch phenotypes per se is incorrect (especially as usually implemented in practice).