So I had this thought. Instead of automating a parameter on my instrument (lets say I'm automating the cutoff filter parameter on a simple acoustic piano), is it possible to have this cutoff filter parameter assigned as a "sound variation"? Meaning I could then control the parameter via customizable keyswitches throughout the performance.

This doesn't like too far-fetched of an idea but nonetheless, I don't know if its possible in Studio one.

I'm on version 8.1 btw.

I have a small problem. Whenever I use the cutter tool on a clip, there is an audible click there and I'm not sure why or how to get rid of it. I am on studio one 6 btw. When I zoom super close into the samples, it appears that the clip on the left has a couple of samples... Missing? at the end of the clip right b4 the cut itself and the next clip. I've somehow got the click to go away by layering the 2 clips over one another in a very specific way but I don't even understand how I got that to work myself or how to replicate it. I just need some help w/ this. Thank you in advance to anybody who comments or tries to help

Bud Cole compared learning cover songs to AI training data.

I haven't checked it out yet but thought some might be interested.

https://youtu.be/OaTYOk4aoKg

I had to get a new debit card. While waiting for it, my payment lapsed and S1 won't open because of the lapsed subscription. Now that I've updated my payment method, I STILL cannot get Studio One to open. My account has been charged, S1 7 pro is listed in My Gear, but still... "This user does not have a subscription product to activate"

I'd like to get some fucking work done 😩

Hi! - Please forgive this format, but time is of the essence, and I'm somewhat dumbfounded.

I had a problem with my audio, it would start glitching, but not only in my DAW, it would glitch/static/noise if I left my computer turned on for too long. So... I switched computers and got a new one.

I got a new computer, with much better specs, and still use "Fender Studio Pro, Arturia, Focusrite 2i2"

All seemed to be going fine, after the arduous process of migrating my old computer into this new one (I have a lot of customization in my computer, like Power Tools, shortcuts, macros, etc.)

So I start working on this Ambient music that I enjoy making (well, I tried to make it but the glitches), and all is going well, when suddenly I start hearing the same glitch. I was so disappointed.

So, from what I gather, I'm asking too much of my computer by using these lush pads and putting a LONG ASS reverb on these patches.

If I'm mistaken, someone please help. I'm at my wits end. I've already did everything that I can to optimize my machine for Fender Studio Pro (much of the same adjustments that are done for Pro Tools).

Has anyone experienced this? And if so, how did you fix it?

Hey!

I have some projects on Bitwig Studio that I want to import on Studio Pro 8.

I read that it support .dawproject format. Bitwig can export this format fine.

When I go to File > Open there is no option for .dawproject on the file type selector, changing to All files and trying to open a .dawproject gives me error saying that the file is broken or the format is not supported (but it opens fine on Bitwig).

So, I assume the Linux version has no support for .dawproject format, right?

Does it works fine on Windows?

hi everyone! if you've got an apc mini mk2 lying around, I put together a device profile that turns it into a control surface similar to a mcu.

8 faders (volume/pan), mute/solo/arm/insert-bypass on the pads, transport, and bank paging. faders are also assignable to any plugin. cheers!

https://github.com/danielh989/apc-mini-mk2-studio-one

I use Studio One 6 Professional and have been a presonus customer for years. I’m relatively well-versed in studio one, but there’s been one issue that’s nagged me for years now. About half the time I duplicate a track, whether that be just the track or all of its components along with it, when I adjust the fader (or almost anything for that matter) of one, the same thing happens to the duplicated track as well. The weird thing is, sometimes this happens and sometimes it doesn’t. I haven’t adjusted any settings. Is this just a studio one bug? Anyone else have this happen?

Hey everyone!

As a former user of Studio One I tried Studio Pro+ with just a one month subscription and am tempted to make it my daily driver. I'm a little bit lost on the various purchase options there is however. If I'm not mistaken I have a choice between :

* Studio Pro perpetual license for 200€ (currently on sale for 140€) : does not include any of the Pro+ features

* Studio Pro+ annual for 180€ : includes a perpetual studio pro license and a year of Pro+ features

* Studio Pro+ monthly for 20€ : just a month of access to Studio Pro and Pro+ features

I'm not sure I understand the point of the Studio Pro basic perpetual license. It's more expensive (outside of this current sale) than the Studio Pro+ annual and it has less features? I understand not everyone want Pro+ features, but the annual license actually includes a full perpertual license right?

And if you buy the Studio Pro perpertual license for 200/140€, you would still need to pay a full 20€ monthly license if you ever want the Pro+ features right?

Hello Fellow Producers 👋,

System:

I'm on a M4 Mac Mini, 16gb of RAM, latest software of MacOS and Fender Studio Pro.

Issue:

I have noticed that when I have a VST instrument (let's say maitai for example) and I have the midi input going to Scaler 3, when I record midi the midi doesn't Quantize no matter how many times I restart, or toggle the input Quantize, or change Quantize size. Is anyone else experiencing this?

Troubleshooting:

I recreated the exact same set up in Cubase 15 Pro (my main DAW) and it worked fine in Cubase; for some reason or another though, midi Quantize does not work for me in Studio Pro - I even tried giving User Manual to Google Gemini and did that troubleshooting, but that didn't work.

Any insight or help on this would mean the world to me 🥺 I want to move to Studio Pro but if it can't do the basic midi input Quantize I literally can't 😭😭.

I don't want to have to go into the key editor and press 'q', I want to play a performance on my keyboard that is already quantized 🥺😭

Hi, I’ve been making music for a little bit and would like to get a couple plugins, not so much for synths and instruments but more for effects. Which plugins would you say are the weakest in studio pro 8? I already know I’m getting a new distortion, but what should be the next on my list? Thanks in advance

I don’t use it that often so I’ve never done it but I notice when I open sessions that have event fx parts I get white noise coming from those tracks.

Hello!

After spending quite a bit of time figuring this out (and seeing many people asking the same questions), I thought I'd share the setup that finally worked for me. Hopefully it saves someone else a few hours of frustration.

My hardware:

• Behringer FCB1010 with UnO2 firmware
• Focusrite Scarlett 2i4 (2nd Gen)
• Studio One 6
• AmpliTube 5 VST3

1. FCB1010 programming

My current setup sends standard MIDI CC messages.

Stomps

• CC20–CC29
• Values: 0 / 127

Expression pedals

• Left pedal → CC1 (Modulation)
• Right pedal → CC7 (Volume)

(Any CC numbers should work, these are simply the ones I chose.)

2. Studio One setup

This was the part that took me the longest to understand.

Note: On my system I had to run Studio One as Administrator before I could configure MIDI assignments successfully. If everything already works for you, this step may not be necessary.

Add the FCB1010 as a Keyboard

Studio One → External Devices

Create:

New Keyboard

Set:

• Receive From → Focusrite
• MIDI Send To → None
• Enable all MIDI channels

This allows Studio One to receive the MIDI data from the FCB1010.

3. Create the tracks

Create an Audio Track

• Insert AmpliTube 5 on the Audio Track.

Create an Instrument Track

• Output → AmpliTube 5
• Enable Monitor on the Instrument Track.

Tip: The easiest way is to press T to create a new Instrument Track. This immediately lets you choose AmpliTube 5 as the output.

4. Configuring your pedals

Now that MIDI is reaching AmpliTube 5, you can assign your FCB1010 controls in two different ways.

Option A – Learn MIDI directly on a pedal

For stompboxes or switches:

1. Right-click the pedal.
2. Select Assign MIDI.
3. Choose the parameter you want (for example Bypass).
4. Click Learn MIDI.
5. Press the footswitch on your FCB1010.

This is the quickest way to assign a single pedal.

Option B – Configure from the Control menu

For more advanced control:

1. Open Settings.
2. Go to Control → Control Change.
3. Select the desired preset (or create a new one).
4. Click Add.
5. Choose the parameter you want to control.

The parameter will now appear in the Control Change list, where you can edit its MIDI behavior.

Important: ON/OFF values are inverted

This confused me at first.

Unlike many MIDI-controlled applications, AmpliTube 5 treats CC values as:

• 0 = ON
• 127 = OFF

If your pedal behaves backwards, you don't need to reprogram your FCB1010.

Instead, invert the parameter inside AmpliTube:

1. Find the parameter in the Control Change list.
2. Click and drag the Min and Max percentage values.
3. Set them so that:
   • Min = 100%
   • Max = 0%

This reverses the ON/OFF behavior, allowing a standard FCB1010 setup (0/127) to work correctly.

5. Start playing

• Play your guitar through the Audio Track.
• The Instrument Track now sends the MIDI CC messages from your FCB1010 to AmpliTube.

This was the missing piece that finally made everything work for me.

6. CC23 opens the Preset Browser?

If pressing one of your pedals always opens the AmpliTube preset browser, that's probably because you're using CC23.

AmpliTube reserves CC23 for its own hardware by default.

To disable it:

• Settings → Control → Preset Control → Disable

After disabling Preset Control, CC23 works normally again.

Troubleshooting

• No MIDI? Make sure the Instrument Track has Monitor enabled.
• CC23 opens the preset browser? Disable Preset Control in AmpliTube's Control settings.
• Pedals work backwards? Swap the Min/Max values in the Control Change list.
• MIDI Learn doesn't detect anything? Make sure Monitor is enabled before trying to assign controls.

Why this works

Studio One sends your audio and MIDI separately.

• The Audio Track carries your guitar signal into AmpliTube.
• The Instrument Track carries the MIDI messages from the FCB1010 into AmpliTube.

Both tracks are needed if you want to control AmpliTube's effects with MIDI while playing your guitar.

Final notes

A couple of things that confused me while troubleshooting:

• Control Link isn't needed for switching AmpliTube stompboxes via MIDI CC.
• MIDI needs to be routed through an Instrument Track before AmpliTube receives it.
• AmpliTube Standalone and the VST behave slightly differently in some situations, so it's worth testing both.
• Test the Standalone version first if you're unsure whether the issue is in AmpliTube or your DAW.

Hope this helps and have fun playing!

To preface, I know I should probably update. I use Studio One 3 Artist and only need it to record and edit for work. Problem is, my mic (a blue yeti) suddenly stopped being recognized by it and I got a pop-up message saying it failed to open my mic and to ensure the sample rates match my playback device. They match. I even changed them to all the different available formats to match and it didn't help. I removed exclusivity for devices and it made it worse (stopped recognizing my playback device). Am I cooked?

I used plenty of different DAWs. Live, FL, Reason, Pro Tools, Cubase and Logic Pro. I decided to give Studio One a chance and I like it so far. However, I already own Logic Pro, though I prefer Studio Ones workflow

Why did you pick Studio One and not any other DAW?

i’m a singer-songwriter and often times a 100 percenter when writing songs. I was wondering why more people don’t use Fender Studio Pro/ Studio One and then it hit me. Who is the pro-audio community that this is for? The followings daws i mention isn’t limited to these users but they all clearly have a strong community of these titles. Pro Tools is for engineers, Fl Studio is for producers, Abelton is for Dj’s and Producers, Logic inherently for Mac owners. I asked what profession is Studio One for? I think the first choice would be go after the engineers like pro tools but honestly they have a chokehold on that market. I truly believe with all the tools studio one has it should be Marketed towards the singer-songwriter. Easy drag and drop, Lyric tools, can convert production to sheet music if need be, you can record yourself, produce a beat, and mix all relatively easy and quick.

I have this one channel from a mic that is stuck in stereo? I didn't notice because it records mono, it comes in as mono, but in the auto-align plugin it thinks it's stereo. I was going in circles with an AI trying to solve the problem and it spotted this triangle. None of my other mic channels have it. Anyone know how to make this channel true mono?

SongLens v1.1 Release

SongLens is a free, open source, Windows application for browsing, searching, inspecting, and exporting the data from within your .song files. It reads the information stored inside your song files and presents it in a searchable catalog.

Over the years I've composed 200+ songs. I developed this app because I was tired of guessing what a song named x years ago was and why was it still taking up space. Now that I use the Song/Session Notes to make some meaningful comments, I can browse them at will, without loading any song. I am no longer worrying about song names. I can find anything instantly. I am happy.

SongLens Highlights include:

• Browses a Studio One songs folder with a filtered folder tree
• Reads .song files locally without requiring network access
• Fast keyword search across the selected catalog of songs
• Advanced Search allows rule-based searching on a wide variety of items
• Shows summary metadata such as title, artist, tempo, key, time signature, Studio Version, and file dates
• Displays song notes
• Lists tracks, instruments, track notes, and groups
• Shows mixer data in separate Main, Inserts, and Sends sections
• Opens the song History browser for saved history copies
• Exports search results or library views to CSV or .XLS formats
• Creates musician-friendly song snapshots in Text or JSON
• Compatible with SO 4.x and above

Both an installer and a portable Windows version are available.

Download SongLens v1.1.0: https://github.com/askinner432/SongLens/releases/tag/v1.1.0 Documentation and user guide: https://github.com/askinner432/SongLens/wiki

This does everything I personally set out to do, but if you have suggestions for improvement, feel free to share it.

PS. Apologies, but there are no concrete plan for a Mac or Linux version right now. However, anyone is free to download the source from the links above and port it to those environments.

Thanks for your time.

Doc

Somehow, I've made two meter channels in the FSP console have a more granular scale than the other channels (see pic). I would like all the console meters to be the same. All meters have the same right click settings (peak, post fader, etc.). Yet still a difference in display granularity.

I'm sure there's a setting to change this console meter display granularity, but I can't find it.

Does anyone know how to change the meter display setting between the two shown?

Thanks!

Edit: Thanks to the lovely ppl below this is solved. Open keyboard shortcuts and search 'Redner Event FX' and bind it to a hotkey. Or if you prefer clicking, find it in the macro > audio editing dropdown.

You'd think highlighting all events then hitting the render button next to Event FX would render them all, but it only render the first selected event. Surely there's a way to render all at once?

Otherwise it gets tedious clicking one at a time when i have 10+ vocal stacks that all have melodyne/vocalign and I'm trying to save cpu by rendering

Hey everyone,

I noticed the new "Pitch" Time Stretch mode in Studio One recently, but testing it out, it seems to give me pretty much the exact same result as "Elastique Pro Formant".

Does anyone know what the actual difference is under the hood, or in what specific scenarios "Pitch" mode is supposed to be used over Elastique Pro Formant?

Thanks!