Fender Studio Pro 8.2 - Discussion Thread

[FMN-Music]

Freeze for FX Channels: FX Channels can now be frozen and rendered into Audio Tracks.

Can anybody check, if this means that "Mixdown Selection" is now possible for FX Channels (and Busses) as well?

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

That would be the feature that would push me over to renew my one year update plan.

 

[Vocalpoint]

Freeze for FX Channels: FX Channels can now be frozen and rendered into Audio Tracks.

Can anybody check, if this means that "Mixdown Selection" is now possible for FX Channels (and Busses) as well?

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

That would be the feature that would push me over to renew my one year update plan.

I had v8.20 on the main DAW for just 20 minutes this morning (prior to a rollback) and I do not think this has anything to do with Mixdown Selection.

I think this is just a new command (Freeze FX channel) that now appears when right clicking on an FX Bus.

See here from our friend Jonny Lipsham:

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

Scroll to the 18:00 mark...

VP

 

[MisterE]

You and I have had our moments discussing this at length - but I stand by my original tact.

MIDI 2.0 is simply not a thing until the hardware catches up. Which will be years from now.

It is a moot point for anyone to care whether MIDI 2 is there (or not) when deciding if Studio Pro is for them.

And make no mistake - there are no "other" DAWs out there who are even close to have this working either. From the 8 or 9 threads I have seen in the last 6 months - It's a crap shoot everytime some decides to flip that MIDI 2 switch - usually in Logic - just to see everything come tumbling down - especially when paired with Komplete Kontrol hardware.

Even the lead manager on Komplete Kontrol surfaces on the NI forums every so often telling users to not bother with MIDI 2 - for a long while.

VP

I've already acknowledged that you were right about the glacial MIDI2 rollout across the entirety of the electronic music landscape.

I'm still waiting to hear from great minds like yours what Fender gained by keeping their participation in any MIDI2 development under wraps for years until today or what it's gaining by remaining mum on deep integration with NI controller keyboards. Tell me how it's earned them dollar one and I'll shut up

 

[Vocalpoint]

I'm still waiting to hear from great minds like yours what Fender gained by keeping their participation in any MIDI2 development under wraps for years until today or what it's gaining by remaining mum on deep integration with NI controller keyboards. Tell me how it's earned them dollar one and I'll shut up

My take? Here we go...

MIDI 2: What has Fender gained by keeping their participation in any MIDI2 development under wraps for years until today?

Why do we always jump to conclusions thinking there is anything to gain? This is a nothing burger for any user - regardless of DAW. Adding this to FSP today is not going to drive sales - or will it suddenly upset anyone that bought another DAW 32 days ago and missed out on MIDI 2.

KK V2 FW: What is it gaining by remaining mum on deep integration with NI controller keyboards?

Why are we (especially me ) jumping to conclusions thinking there are (or were) any plans to add this?

While I fully admit - I thought this should have been a no-brainer back when the FW dropped - the longer this has gone on with zero evidence of it ever happening - has me thinking differently now.

This non-existent update could have many reasons ranging from possible development tradeoffs that may need to occur that maybe one or both parties are not inclined to make. Or it could be new owners (on both sides) or time constraints, or feature request levels or something else - as yet unknown.

But let's be realistic - the actual count of FSP users that actually use a KK MKIII (FW v2) device - pale in comparison to the overall total FSP user base. At the end of the day - the actual reason for this could be much more simple - maybe Fender just does not see this being worth their time - for now.

To be fair - I would rather have them continue to focus on their plans - and keep the overall base engaged with high quality updates like v8.2.0 today.

P.S: This "Where is it?" discussion reminds me of a similar debacle that was rampant about 3-4 years ago with ATMOS. People were literally yelling about it for 18 months straight and then one day - there it was.

After 15+ years - I never count these guys out. But I can tell you - they do not do anything - regardless of what it is - unless it benefits the user base AND the application and is implemented in an elegant fashion - if/when they decide to take to on.

Maybe one day - we get a surprise....just out of the blue.

VP

 

[Craig Anderton]

I've already acknowledged that you were right about the glacial MIDI2 rollout across the entirety of the electronic music landscape.

There are many reasons for that. Early on, covid killed international travel. Microsoft embarked on a complete re-write of the audio and MIDI stack, which was not trivial. VST3 has to know how to talk to it. Backward compatibility had to be bulletproof, which required a new, universal data packet. Personnel changes. The music industry is not doing spectacularly well right now...etc. etc.

MIDI 2.0 is also a very ambitious spec. Mistakes made early on could have huge consequences later on, so the industry is treading very carefully.

However, as someone who always felt MIDI 2.0 was years off, I now think that we'll see major progress at Winter NAMM. MIDI 2.0 will roll out over time, just like MIDI 1.0 did. Much of it is designed to accommodate future needs, and those aspects won't be available until the needs arrive. But I think we'll start to see the kind of features that matter right now, like higher resolution, additional controllers, and time-stamping to reduce timing jitter. Studio Pro is already moving in that direction. After that, we'll probably see profiles and capability inquiry take root.