No, calc view performance is not impacted (at least to to this extent) by an invocation via a stored procedure.
Given the information you provided, there is no way to find what causes this effect - in fact we don't even know how you obtained the runtime numbers, so that could be wrong in itself.
Anyhow, an easy way to understand where time is spend by your query is to use PlanViz and to check the time single execution steps take and how much data these work on.
Most often this will provide the required information to move on.