-
Hi and welcome to the Studio One & Studio Pro User Forum!
Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by Fender. Learn more in the Welcome thread!
Plugins running in Fender Pro and too small...smaller than in Studio One 8
- Thread starter cdig2000
- Start date
I hope Fender will one day realize what a bad idea the new name was. Fender Studio? Fender Studio Pro? Fender Pro? Fender 8? What were they thinking? Were they thinking at all?
Anyway: In Fender Pro, DPI handling can be adjusted per plug-in. Is this something you’ve already tried?
First, if something important doesn't work anymore then it's probably best to use the previous version and wait for a bug fix release.
That said, high DPI mode is messy on Windows. There're just too many ways to set it up: Windows system wide setting, Windows app specific settings, plugin specific settings and DAW settings for itself and the plugins. Changing the Windows wide setting requires an instant reboot, DAW and plugin changes usually require a restart/reload.
I switched to high DPI mode a year ago and tried and reverted lots of configurations. From my experience, the following approach worked best for me (the order is important):
1. Change the Windows wide setting first and reboot. I use a 200% scaling on a 4k tv monitor but that's just my preference.
2. Open your DAW and enable high DPI mode and restart.
3. Load a plugin. If it is already properly resized and sharp then you're done with this nice plugin.
4. If the plugin is not resized then use the options the plugin itself offers: enabling high DPI mode or use a custom scaling and reload.
5. If it's now resized but not sharp then there's (very likely) nothing you can do about it except looking for an update for that plugin.
6. If resizing is not available then enable system high DPI setting in your DAW for that plugin and reload (see screenshot above). If it's still not resized then it's a very old plugin. If it's resized but not sharp then (again) there's very likely nothing you can do about it.
7. Good luck.
That said, high DPI mode is messy on Windows. There're just too many ways to set it up: Windows system wide setting, Windows app specific settings, plugin specific settings and DAW settings for itself and the plugins. Changing the Windows wide setting requires an instant reboot, DAW and plugin changes usually require a restart/reload.
I switched to high DPI mode a year ago and tried and reverted lots of configurations. From my experience, the following approach worked best for me (the order is important):
1. Change the Windows wide setting first and reboot. I use a 200% scaling on a 4k tv monitor but that's just my preference.
2. Open your DAW and enable high DPI mode and restart.
3. Load a plugin. If it is already properly resized and sharp then you're done with this nice plugin.
4. If the plugin is not resized then use the options the plugin itself offers: enabling high DPI mode or use a custom scaling and reload.
5. If it's now resized but not sharp then there's (very likely) nothing you can do about it except looking for an update for that plugin.
6. If resizing is not available then enable system high DPI setting in your DAW for that plugin and reload (see screenshot above). If it's still not resized then it's a very old plugin. If it's resized but not sharp then (again) there's very likely nothing you can do about it.
7. Good luck.
Cristofe
Member
As per usual, Fender has screwed the pooch. NOTHING can be done to make plugins that display just fine in PRESONUS S1 V6 from being microscopic in Fender Studio. The above mentioned solutions did, in fact, make Studio Pro itself display better....but not these plugins. I have and use many other hosts, (including the most recent release of Cubase), and none of them have this problem. So, yet another reason to not upgrade.
See attached pics of the same plugin instantiated in v6 & v8.......and, actually, on screen, the gui of the plugin on 8 is WAY smaller. Impossible to use.
See attached pics of the same plugin instantiated in v6 & v8.......and, actually, on screen, the gui of the plugin on 8 is WAY smaller. Impossible to use.
Last edited:
OutrageProductions
Active member
Resize the Plugin with the bottom right corner, close it, then reopen it. Is it retaining scale?
Cristofe
Member
Thanks for the suggestion but I'm not a noob. I've been working with plugins for decades. Many, like this one, are not resizable.
Those that are, generally, have a series of parallel lines in the lower right hand corner indicating that feature, (see pic). And, as I
thought I explained in my initial post, the problem is not the plugin itself, or the the display settings in my pc. The plugin displays
properly in at least a dozen other hosts including Presonus Studio One 6.6.4. The ONLY host that displays this, and other plugins,
in a microscopically minute size is Fender Studio Pro.
Those that are, generally, have a series of parallel lines in the lower right hand corner indicating that feature, (see pic). And, as I
thought I explained in my initial post, the problem is not the plugin itself, or the the display settings in my pc. The plugin displays
properly in at least a dozen other hosts including Presonus Studio One 6.6.4. The ONLY host that displays this, and other plugins,
in a microscopically minute size is Fender Studio Pro.
Last edited:
Cristofe
Member
Thanks Bob! That's a very generous offer. But, I don't have the time or inclination to test hundreds of plugins in Fender Studio Pro 8.
My main DAW is Presonus Studio One Pro 6.6.4 and the problem does not exist in that program or Cubase or any of the other hosts
I use. So, for me personally, it is a non-issue. Simply another reason not to "upgrade" to Fender Studio Pro 8. As others have reported
this issue here and on other pro audio forums, I trust the German "Fender" software team will get it sorted out eventually.
Cheers......Cristofe
My main DAW is Presonus Studio One Pro 6.6.4 and the problem does not exist in that program or Cubase or any of the other hosts
I use. So, for me personally, it is a non-issue. Simply another reason not to "upgrade" to Fender Studio Pro 8. As others have reported
this issue here and on other pro audio forums, I trust the German "Fender" software team will get it sorted out eventually.
Cheers......Cristofe
This, which I spotted at Guitar Center yesterday, is exactly what they were thinking:
Fender Quantum LT 2 Creator Recording Bundle
Fender Quantum LT 2 Recording Bundle includes a 2x2 USB-C interface with MAX-HD preamp, M7 condenser mic and HD7 headphones for detailed recording and monitoring.
www.guitarcenter.com
That would be Fender branded interface, speakers, mic, and headphones in one box, in other words a complete Fender recording studio in a retail box (that particular picture doesn't show that they've managed to squeeze all four into one retail box that was spotted on the sales floor). Just add a (Fender) guitar. And the forthcoming (? they should!) controller keyboard.
Last edited:
Jemusic
Active member
Would you mind listing a few that are still opening too small. I would love to at least check if we have any in common. So far I am not seeing this but then again it could be because I don't own the ones that are opening up small.
BoBF, Jemusic, nice effort but Cristofe doesn't look for help or anything constructive since he moved on to KVR as CapnLockheed to write the usual rants claiming "the FENDER FORUM MOD admitted this was a problem with the Fender Pro Studio itself" and then "a Fender Mod has confirmed it is an actual bug".
This, which I spotted at Guitar Center yesterday, is exactly what they were thinking:
Fender Quantum LT 2 Creator Recording Bundle
Fender Quantum LT 2 Recording Bundle includes a 2x2 USB-C interface with MAX-HD preamp, M7 condenser mic and HD7 headphones for detailed recording and monitoring.
That would be Fender branded interface, speakers, mic, and headphones in one box, in other words a complete Fender recording studio in a retail box (that particular picture doesn't show that they've managed to squeeze all four into one retail box that was spotted on the sales floor). Just add a (Fender) guitar. And the forthcoming (? they should!) controller keyboard.
Fender Studio Pro, Studio Pro, Fender Studio Pro 8, Studio Pro 8.
No one knows what this thing is called.
Cristofe
Member
Jemusic:
This appears to be a Windows related issue. I see you are on MacOS. No Mac users at KVR either had thisproblem or were able to replicate it. But thanks for your kind offer of assistance.
Jens: How nice of you to spy and snitch on me. If you have nothing constructive to say please mind your own business.
The fact of the matter was that when I couldn't get a suitable answer here. I did, in fact, look elsewhere for an answer to thisproblem (which Bob did acknowledge WAS an issue in this very thread). I only brought the issue to KVR because I got no
good answers here. No one here suggested changing the DPI setting of the plugin itself within Fender Studio. But a member
at KVR did.(see pic).
The most useful reply I got at KVR was from longtime member EnGee who stated:
"I must say it is Fender's fault to scare the new comers by this message! Just follow RexXx's instructions and I garantee you that nothing bad will happen."
So after all this nonsense, and EnGee's debunking of Fender's alarmist warning message, I now, at last, know that when and/or if I decide to "upgrade" to Fender Studio, I finally have a safe and effective solution to what would be a real problem for me. Thanks to those of you here and at KVR that at least tried to help without resorting to personal attacks.
Last edited:
First, I'm NOT a "Fender mod"
Second, I said I believed you are experiencing a legit; not necessarily a Studio Pro problem
Third, the warning you get guides you to seek compatibility from your plug-in vendor. Not alarming to me, just a bit of reality
Fourth, glad to see you're moving forward.
Cristofe
Member
All points well taken Bob. My apologies for any misunderstanding . I know this is not an official forum.
So it was my mistake to label any Mod here as a "Fender Mod". And it was also my mistake in misinterpreting
your assessment of the problem at hand. Like many longtime Presonus users, I am not thrilled by this transition
and the way it's being handled. I think, perhaps, I have allowed my frustration to color some of my comments.
Again my apologies. Personally, as a former official Presonus Forum Mod, I find my own behaviour unacceptable
and will try my level best to remain a bit more calm and professional in any future postings. Thanks for your help
and for setting me straight.
Cheers.......Cristofe
So it was my mistake to label any Mod here as a "Fender Mod". And it was also my mistake in misinterpreting
your assessment of the problem at hand. Like many longtime Presonus users, I am not thrilled by this transition
and the way it's being handled. I think, perhaps, I have allowed my frustration to color some of my comments.
Again my apologies. Personally, as a former official Presonus Forum Mod, I find my own behaviour unacceptable
and will try my level best to remain a bit more calm and professional in any future postings. Thanks for your help
and for setting me straight.
Cheers.......Cristofe
What Im not understanding is why are people calling it Fender Studio Pro?
Do you say Steinberg Cubase? or Avid Pro Tools? Microsoft Word! Magix Vegas?
No you leave out the company name.
If you will just call it Studio Pro or Studio Pro 8 the problem is solved.
Look at all the posts from a year ago and you won’t find anyone saying Presonus Studio one. Everyone always said Studio one or more often just S1 or S1-7.
So if the Fender brand bothers you just simply don’t say it.
Why type a word that is generally not added when talking about any Daw or Software.
If I said that I don’t have this problem using Cubase or Mixcraft, would you not know what Daw I was talking about.
So just get in the habit of calling it Studio Pro 8. We should have no problem understanding what you are talking about. Thank you.
Do you say Steinberg Cubase? or Avid Pro Tools? Microsoft Word! Magix Vegas?
No you leave out the company name.
If you will just call it Studio Pro or Studio Pro 8 the problem is solved.
Look at all the posts from a year ago and you won’t find anyone saying Presonus Studio one. Everyone always said Studio one or more often just S1 or S1-7.
So if the Fender brand bothers you just simply don’t say it.
Why type a word that is generally not added when talking about any Daw or Software.
If I said that I don’t have this problem using Cubase or Mixcraft, would you not know what Daw I was talking about.
So just get in the habit of calling it Studio Pro 8. We should have no problem understanding what you are talking about. Thank you.
Midiboy
Active member
It's cute how you ignored the fact that in the very 2nd post of this thread, someone pointed that setting out to as a possible fix, and yet you go seek help elsewhere complaining about this site and a "Fender Mod" told you that this was a known issue, etc., etc.
When someone offers help here, it's worth trying out before going on to other people and complaining about how "Fender screwed the pooch" and how "A Fender Mod" admitted this was an issue, etc.. This isn't even an official Fender website...completely independent.
I have been using Studio One / Studio Pro for over 10 years myself and absolutely love it. While the original Studio One forum started out as a great site for user help, unfortunately, certain users got a bit toxic (as the kids like to say). I'm thankful for THIS site. Most of the reliable, trustworthy and actual helpful people from that original site seem to have migrated over to here when the official one shut down. I have found this site very helpful. Probably more so than any other site like, for example, KVR. Why? Because the helpful users here LOVE Studio One / Studio Pro. It seems that there are even a few users here that have ties with the actual developers in a roundabout way, and many issues that have been brought up here, got their attention and were addressed.
So give us a chance. Also, when you have an issue, actually go through the forum and look for an answer rather than ranting on and on about screwing pooches...and actually try out what has been suggested.
Heck, I even found help here for a 3rd party plug in that stopped working with the new branding (Synth V) because it relied on actual folder names to work (How stupid is that?). That fix also worked for me...but the vendor just fixed it a few days ago via a beta patch.
Now, look at me ranting. Sorry about that.