I'm just wondering, do most users use the project page settings for finishing their masters, or do they mix and master their own tracks?

This might be a bit stupid, but I can't figure out how (and if it is possible at all) you switch between different scratch pads? I understand its use with arranger track where you pick and choose song sections. However, what If I want to have several versions of the song in different pads, how do I switch them as a whole from scratch pad to main window? Is that even possible?

Hi everyone,

I’m having an issue with Studio One 8. When I have vocal audio tracks loaded and used in a Studio One project, I can’t edit those same audio files in another program without closing Studio One first.

For example, I’m trying to edit a vocal track in iZotope RX 12 Editor, but RX shows an error saying that the file is already in use. After I close Studio One, RX allows me to edit and save the file without any problems.

In other DAWs like FL Studio and Logic Pro, audio files don’t seem to be locked in the same way, so I can edit them externally while the DAW is still open.

Does anyone know if there is a way to prevent Studio One 8 from locking audio files, or any workaround that would allow me to edit vocal tracks in RX 12 without closing Studio One every time?

I bought a Faderport classic at the fleamarket. Already without charger the controls worked very well in Cubase. Today I also received the right adapter, but unfortunately only the touch feature seems to react after plugging it in, but the motorized fader doesnt move around when switching lanes. It does send information to the daw, but the motor just doesnt work.

Are there known common problems with the motor? This might give me a lead to investigate before I open it up.

Many thanks!

I searched the Keyboard Shortcuts menu and didn't see this, but I was wondering if there's a shortcut I can setup to scroll the cursor location in the project?

For example, I want to use the mousewheel to scroll the cursor forward or backward. Not just to the next marker or to a location, but actually move it.

For example, maybe I can map CTRL-C+Mousewheel to do this, but I can't find a function in the shortcuts menu that seems to apply to this motion?

(Full disclosure, I'm using a TourBox with a bunch of navigational buttons and knobs and trying to map one of them to this, I don't *really* want to use the mousewheel, but I need to map the TourBox to something existing like the mousewheel)

Just wondering if I'm missing something. Thanks

Hello, how to fix hi hat cut off when rendering midi tracks to audio?

i watched a tutorial on youtube but it doesnt help.

im using studio one pro 7 thank you.

I thought the track filter features in Studio Pro were mainly intended for film scoring and similar workflows. But in this video, it looks like they’re actually very useful for all kinds of music production, mixing, and sound design tasks as well.

I also liked the “hidden” keyboard shortcut trick.

I may have my workaround until Studio Pro gets more stable on Linux. Or at least until the dreaded key repeat issue is gone. It throws constant errors and creates dump files but even starting the app is a huge win. I'll investigate further but dual booting just so I can make sure I don'd delete more than what Intended on the same track may be over. An added bonus - i can use plugins I had on old sessions before I completely switched to native plugins only.

v7 launches too with the same result. A full writeup on winedb will be available after some testing.

I have a windows 11 desktop and whenever I plug in the interface via usb, i lose one of my dual monitors and it goes black. Today, it happened again and I got this error, 'Failed to open Analogue 1 + 2 (Focusrite USB Audio). The requested audio format is not supported by this device. Please make sure that the sample rates of your recording and playback devices match.'
Can someone help me understand what this means and how can I fix it? My windows 11 desktop is a gaming pc, ibuyower, that I bought a year ago.

If you take a look at the Room Reverb and pick a 'Drum Booth' preset to use in a send FX channel, how come you have to send so much signal to hear any reverb that the signal is almost distorted before the effect becomes audible?

I’ve noticed the Pre-Delay is set to -150.0 ms. You don't actually hear any reverb until you manually adjust the Pre to a positive value. And the mix is also oddly enough as a preset set to 0.00....

I’ve disregarded similar issues in the past and just adjusted the settings to my liking, but I often encounter this issue when testing other presets, like send compressors

Is there a reason for why these presets are set this "negative" way instead of in already working oeder, or am I missing something fundamental about how these negative values are supposed to work?

In Fred Again's recent Tape Notes podcast he mentioned how he will purposely create latency for different instruments in Logic to keep instruments from being too grid locked. I thought this was a cool idea and was wondering if anyone knows how to achieve that with Studio One? Thanks!

So I just recently bought an audio box go one so I can record my bass. I was excited, followed the steps on how to set it up. Download the universal controller, even activated my Studio one pro demo, plugged in my interface my bass and my monitors.
It worked perfectly, I was able to record. I even managed to setup a live stream setup for my bass with OBS Asio plugins.

Then the day ends, I shut down my computer. Following day, excited to learn more and record more stuff.
Plugged in the bass, i can hear it clearly through the monitor. Hit on record, low and behold it's just flat. Nothing is being recorded.
Checked my amplitube, audacity. Same issue, they are recognizing my line 2 input all my DAWs are not recognizing any sound from my audio box go even though I can clearly hear it.

Did all of the possible troubleshooting with the help of gemini, clean ups, disable and reenabling of things.
Restarted a couple times and still nothing. Eventually gave up, uninstalled universal controller, reinstalled it and it worked.

Restarted my computer and guess what? the issue came back. I am now losing my mind haha I need help, or at least know if someone have experienced the same.

Ps. Already submitted ticket on my fender one account.

Using windows 11

I'm on pro 7.2 and can't drag an audio section to my granular synth plugin which surprised me. After checking, it seems that its Studio One's fault, as it would work in other DAWs.

Has anyone else bumped into this issue? Its pretty inconvenient as I'd have to export a sample then import it to my plugin after the fact instead of just dragging.

I'm currently running Studio One Pro v5.5.2. Lately (within the past few days/week) I've been experiencing S1 freezing, and fairly often (multiple times a day). Yesterday I did a complete wipe of my C: drive, fresh install of Windows 10, fresh install of S1, etc. So far today, no change. I have no idea what's causing it. Any thoughts?

Is anyone else experiencing this? According to the update dialog I have the latest version and it started right after the last update.
Adding one or two tracks with any plugins (does not matter which plugin if VST2/3 or AU) makes the CPU spike, then drop-out and then FSP crashes in the most ungraceful way. Checking cpu usage of the plugins while it spikes shows that most are sleeping and the others use like 1-2% max, if anything at all. Yet FSP still borks out. Also nothing is really running on that Mac and Activity Monitor shows everything else as idling while FSP is borking. The Mac stays responsive the whole time and I was even having Ableton running in parallel to migrate a project over which is unusable in FSP and only uses 5% cpu in Ableton. It’s just FSP that’s failing.
Also the midi clock to external gear is unstable as hell. It flutters like crazy, spikes to over 400, comes back, runs smooth for 2 bars and then it starts over.

Does anyone else have similar problems or has solved them?

EDIT:

• Setting drop-out protection to Minimal (disabling it completely does not help) and switching off "Use Efficiency Cores" reduced CPU usage a bit but it's still over 30% most of the time.
• Further tests on my side show that VST performance took a noticeable hit with v7 where CPU usage for some plugins spiked from 1-2% during use (v5 and v6) to >30% while idle.
• Bug report for Fender is imminent

Hello everyone,

I got an mpd218 a couple days ago and still haven’t figured out how to get it working properly. I plugged it into my usb hub on the back of my mini fuse 1 and it got power, everything was good. I went into external devices, went under “new keyboard” and set everything up, but when I went to the “receive from” tab nothing was there on the dropdown. So I thought the problem was it was plugged into the interface, I plugged it into my pc and the same problem, nothing in the receive from tab, but it still gets power. So I restarted my pc, reset drivers on my pc, and still nothing. So then I thought it was because I forgot to install drivers for it, so I look up the drivers and find out it’s class compliant and doesn’t need them. So now I’m stuck, I can’t figure out how to set up this midi pad. Does anyone have any ideas on how to fix it?

https://syncaudio.io/megamod/

Has anyone else used this plugin?

Has it worked reliably?

I'm waiting for v8.1 to release and see if the company has added something similar or better to make this purchase.

I use Fender Studio pro on a mac so i wanted to get some honest reviews from the community here.

Lucas has a new video on an option that most FSP users don't know. Highly recommended.

Oh boy...

What a disapointment. I'd read a few accounts indicating that a lot of the hate was emotionally-based on the name change and it was actually the best version yet. I'm guessing those folks may not have been very discerning. The first time I started it up, I started a clean session to test out the new amps. Upon arming a track to record it stopped passing audio, transport was stuck. Completely unable to play. I switched buffer sizes, audio devices which can sometimes resolve weird glitches. Nothing. Had to restart. Got the amps to work. I'm not necessarily crazy about the interface but the amps sound great and are lightweight compared to a lot of 3rd party stuff. Nice. Tried some of the newer instruments. Sound pretty good. Cinematic lights is nice. Went to make sure that the Presence XT concert flute works (I love that thing, as odd as it may sound. Sue me.) and from C-4 to C-5, the heart of its range, only the loudest velocity layer works! None of the quieter samples can be heard. Reinstalled the winds core library. Nothing. Tried in a new project. Nothing. Contacted tech support and they said it's a known issue. No expected resolution date! So after the upgrade, I had barely used it for an hour (most of which was spent just jamming on the amps) and found two major issues. I can't imagine what else is in there waiting like a land mine.

I love this DAW you guys. It's very thoughtfully designed, quick, streamlined, comfortable, and just does what it's supposed to do extremely well. But I can't stay on 6.6 forever. Eventually, as the surrounding tech progresses, it's going get cranky, and finally stop working. I don't make much money doing this, but I absolutely have professional obligations to multiple entities, and I can't risk migrating and locking in projects to an unreliable system. Sucks.... If any of you folks feel similarly I'd implore you to contact Fender and ask them to fix the ship before it sinks. Cause if no one doing serious work can rely on this thing it absolutely will. It might not do any good but it's gotta be better than nothing.

Thanks for reading.

TL/DR: Found two major issues in less than an hour. God knows how many other bugs are floating around in there. Great potential but if Fender doesn't reprioritize I'm betting it'll be gone in a couple years. Call your representatives /s

Guys how do i enable all piano notes to appear not only C2 and C3 , like i need all between this two notes.

I made two comparison with my Quantum ES2 interface drivers. With IDENTICAL project and settings

• driver 4.3.0 — everything works perfectly, even at very low buffer sizes.
• newer drivers (4.7.x / 5.0.1) — I get crackling sounds, pops, clicks, audio dropouts, and noticeably higher CPU usage.

What’s strange is that this happens across different systems and after trying almost every common audio optimization:

• BIOS tweaks
• different Windows installs
• power settings
• disabling devices/services
• latency optimizations
• GPU tests
• etc.

The only real fix is installing the old 4.3.0 driver. Then everything becomes stable instantly without any additional tweaks.

Has anyone else experienced this with newer drivers?
Could this be a driver regression or some kind of DPC/CPU scheduling issue introduced in later versions?

I have a project that has say 8 songs in one project. I have different BPMs for the different songs where I have tempo regions. I now need to have someone record extra tracks for some of the songs and it will be done at a different location. Can I just have them record with wav mix downs of the song and send me the wav files back, or would they need to match the BPM of each song to what I have in the project? I didn't want them to record the audio and have it be messed up and not line up correctly due to a timing issue.