Fender Studio Pro 8.0.1 - Discussion Thread

[Ari]

@songshop

Should be an easy test for everyone to reproduce. Just provide both of your result audios from different DAWs.
Everyone should be able to look into these. I will support that with own tests.

Just provide your testing samples.

Best
Ari

 

[Midiboy]

Since you made me curious, I just recorded the same input in S1 as well as in Reaper simultaneously. Then I exported the files, imported them in Logic, aligned their phase, flipped the polarity on one and pressed play. Result: 100% silence. Case solved.

It's a pointless argument. People don't understand digital audio. I guarantee there is something (a setting, a pan law, a something else) that is at play. They probably don't even realize it.

 

[SwitchBack]

Recording straight to export doesn't use the mix engine. A better test would be to import two files, preferably one stereo and one mono, mix them together (make a note of fader settings), export the resulting mixes and do a null test with those.

 

[Rambler]

Recording straight to export doesn't use the mix engine. A better test would be to import two files, preferably one stereo and one mono, mix them together (make a note of fader settings), export the resulting mixes and do a null test with those.

Obviously you can expand the test to an ever evolving complexity (including bus summing, pan law, processing of plugins etc.) but in this case the claim was „grab an accoustic guitar track & A/B with Studio Pro. You'll be amazed. SP is magic.“ which I disproved with this simple test.

Also there have been endless summing tests like this on the internet for the last 20+ years. This topic is not exactly new and has debunked hundreds of times. So let’s get back to Studio Pro 8.0.1

 

[SwitchBack]

The point I wanted to make is that if you want to test/check a DAW (even in the most minimalistic way) you have to give it something to do. Exporting recorded files is testing the interface, not the DAW.

 

[Rambler]

The point I wanted to make is that if you want to test/check a DAW (even in the most minimalistic way) you have to give it something to do. Exporting recorded files is testing the interface, not the DAW.

I know but that was the claim. That one track in Reaper would sound worse than one track in S1.

 

[songshop]

...not closed. I didn't say check for phase cohesion... and there's more, like Reaper automatically engages a pass through of the 2nd binaural channel in a 'mono' track, that sums to the top of the channel fader bypassing your inserts, & it's hidden three menu's deep with no global bypass. Anyway, enjoy Reaper.

 

[Zirrex]

Hi, I'm sorry but this update is the least stable I've had since Studio One 5, constant visual glitches, crashes, the most amount of cpu spikes I've had with my M1 pro with projects that V7 handled more than fine. I hope the bug fixing and optimisation patch comes back really soon or I'll migrate to reaper...

If you go to Reaper, the developers of Fender Studio Pro 8 will not notice this. If 50 people switch to Reaper or Cubase from this forum, the developers will not feel it.

 

[Lukas]

Hi, I'm sorry but this update is the least stable I've had since Studio One 5, constant visual glitches, crashes, the most amount of cpu spikes I've had with my M1 pro with projects that V7 handled more than fine. I hope the bug fixing and optimisation patch comes back really soon or I'll migrate to reaper...

You might want to check your plug-ins. Or provide some details, so we can give you tips.

 

[Lukas]

I’ve removed recent off-topic posts regarding "REAPER sounds different than Studio Pro" and some verbal outbursts. Please keep the discussion focused on Studio Pro 8.0.1.

 

[sintil8]

In passing I'm enjoying the new Channel Overview, I'm begining to wonder how I ever got along without it ???

Nice one nuff said.

Regards to all

 

[Navar]

I am very curious, if the issue with the latency compensation is important for other people too. A lot of my projects are not fully working in V8 because of this and of course maybe there is a workaround of re-structuring projects and so on.
I'm referring to this thread, I've also added some easy examples with no 3rd party stuff involved.

Be aware of these Plugin Delay Compensation Fails

These are the areas where PDC is broken: 0:00 Sidechain in Groups 2:31 VST Instruments in serial 3:42 Hardware Inputs 6:18 Multi Instruments 7:03 Batch Processor - Aux Channels linked to external Instruments...

studiooneforum.com

 

[jff067]

Hello, in Windows 11 with FSP8 8.0.1, the program crashes when changing the chord in the CHORD track when using the original track with guitar, extracting chords from it, and using Tonalik on another track in the project. The program crashes constantly. Does anyone else have this problem?
My friend with a Mac M4 doesn't have this problem

 

[Justin]

With the new Chord Progression list in the inspector is there a way to audition the chord progressions?

 

[Lukas]

With the new Chord Progression list in the inspector is there a way to audition the chord progressions?

No. But once selected a chord progression, you can play the Chord Track, either with the built-in Chord Preview sound or with any instrument of your choice.

 

[audioworksHU]

Some Plug-In knobs are colored blue, green and yellow in the Channel Overview in Compact Views:

Is this random, or is there some application logic and uniform color coding, e.g green for time-based effects, blue for frequency-based effects?

 

[Crossinger]

Is this random, or is there some application logic and uniform color coding, e.g green for time-based effects, blue for frequency-based effects?

This is mere guessing: Do Chorus, Delay, Flanger keep their color when you change the order? My assumption (from your screenshot) would be that this is simply a visual separator for individual plugins.

 

[audioworksHU]

This is mere guessing: Do Chorus, Delay, Flanger keep their color when you change the order? My assumption (from your screenshot) would be that this is simply a visual separator for individual plugins.

The colors seem fixed, tied to the stock Plug-Ins. You can't set knob colors for third-party Plug-In's, the only option in blue.