Say guys, MODARTT really got on this one (extended range)  —and within a record response, a real zeal if I must say so myself.

Yes, it is great to have the extended range on the historical instruments, chromatic percussion and piano predecessors, a good step in the right direction. Enjoying this product immensely. The range can be increased by one note downward by setting the tuning to 415Hz and transposing.

Waiting patiently for the extended range for the acoustic pianos.

Maybe, if MODARTT keeps it up, everyone will see the often requested MIDI loop feature, added by version 7!

Piano manufacturers and their point of view

Great point - makes sense that some possible in-confidence clause material may exist for some pianos. I do also envisage eventually the possibility built fully in to the engine, and then whichever instruments have no such concerns may allow it, at least if not in default presets (user clicks the little button to engage it).

in fact thats the reason why i play mostly the K2 !
and since 6.3 or 6.4 also the Steinway D.

but totally understanding that this could be a dilemma vs. the Piano manufacturers and their point of view.

I'd love the option too. Makes no sense that some pianos have it and others not.

What about tuning and string length?
Without changing the string length surely the more modest size models will sound pretty poor with any extra octave in the bass?

Perhaps enabling extra octaves on any models should be an option on Standard and Pro where you can also change the string length (IOW have the extra bass octave become available when you elongate the strings in the settings to a suitable length). Perhaps Modartt could also add a bank of "retuned  & extended range" piano presets so this can work in the Stage version too?

Dunno if zealotry Amen, but, gulp - could be   Pianoteq is the only thing I'm remotely "fan boi" about.  In fact - I never really thought abou.. tha.. (inner voice "Am I?") - looks like.. yah.. Oh my, nooo.. what izzhAAAppenning to meE@!

Everyone posting more than X times here = Pianoteq fan boi.. c'mon admit it

Absolutely - this is kind of why I'd figure it will be optimal to see certain params engineered from the inside the engine out, rather than some sub-component code backed in with every instrument and their specific workarounds.

OMG though - Right there - did you see it?

I was just totally like that guy, 1st in line waiting for the new Sky-Phone... I'm sure that Snapppzzloozle is gonna pre-fab the whole notch plate with organza and fly it via the sub-factorization labs before some futzing with the I/O kernel procesess - which'll make it 0.76% faaaaster this quarter alone, you mark my words (slurps a slurpy) - the whole thingz code-name "Dianah-Huckspeth" - but don't TELL anyone willya, yah yah (checks multi-funcion watch to see how much more suger is possible today).

But - ermagerd and all that, I'm really just onlooking with interest and could be beyond wrong fer sure too

(buys lotto ticket)

Cheers

[EDIT to add the word totally]

Man, your zealotry is always outstanding!

For now, on a per instrument basis, seems each instrument code blob would carry more of the burden of pre-scoping that kind of low freq data handling into the engine (with whatever custom work-arounds req.) - but if the engine itself is reworked to natively begin from lower and higher points, then less per-instrument specialisation may mean super fast workflow by comparison to add extensions to all instruments.. but how long and complex would a larger engine cost etc.. (and what extra consumer CPU burden would be incurred etc.) 

Interesting stuff.

Been trying out the demo, and I like it a lot. The only thing that I would like is the option to extend the range of all the pianos, in particular the Ant. Petrof and the Blüthner. As we can see, the range is already extended on the Steinway D and K2.

I agree.

Not as sure how technically straightforward it would be but seems logical that at some future point.