So what am I doing wrong? I'm using Studio One 6.1.2 on Windows 11.
Background: I am using either a mackie controller, or Atom SQ or faderport classic to arm record tracks. I am using one of these controllers only (not using a mouse or keyboard, that works fine). The screenshot shows track 2 as successfully armed as an example. Please refer to this image for when looking at the steps below. Examples that show expected behaviour: a) If I select track 1 (which is an audio track) and arm record, that works fine. b) If I select track 2 (which is an instrument track connected to a softsynth plugin) and arm record, that works fine. My issue: c) If I select track 3 (yellow), which is an instrument track connects to a TD-3 hardware synth, and when I press an arm record button on the track, it does not work at all. Note it has its own AUX channel. d) If I select track 4 (purple), which is an instrument track connects to a RD-6 hardware synth, and when I press an arm record button on the track, it does not work at all. Note it has its own AUX channel. Notes: With the tracks I refer to on steps (c) and (d) I can use SOLO which solos both track and channel. I can use MUTE, this mutes only the channel (which I assume is expected behaviour). Also note if I delete a related AUX channel (keeping the instrument track) the behaviour remains the same. So it appears the AUX channel isn't anything to do with this. What am I missing? Thx!
Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb. Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental). Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths. |
No response here so, ticket created, thx.
Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb. Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental). Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths. |
Hi PreAl,
I can confirm this dysfunction with the external instrument with or without a coupling of the Aux Chanel. It works with: solo, mute, but not with the "arm record button" ! Test on S1 V6.1.2,and 5.5.2, with Faderport Classic Thank you for reporting the behavior in Presonus |
Thanks for that!
Damn! I was really hoping I did something stupid! Another workflow dead end
Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb. Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental). Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths. |
Unfortunately this behavior exists since I use S1 (v2.6)
To circumvent this behavior, I use the computer keyboard with shortcuts (monitor and recording) there it works .. |
Right, I stated keyboard and mouse works fine.
Issue since 2.6? That's absolutely crazy! If that's the case it appears that there is probably no chance the issue will ever get fixed, if so, this is utter madness! It makes recording with a controller with any sort of flow pretty useless unless you never bother with hardware synths As it does work with keyboard and mouse, my assumption would be that this is a reasonably simple fix to implement.
Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb. Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental). Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths. |
PreAl wrote This is the case, I very rarely use my Hardware synth... and yet it sounds great! |
I've just worked out a workaround with the Faderport classic by assigning the user button to "Track-> Arm". I can also assign an Atom SQ a user button to "Track -> Arm" and it will work, but it is a very annoying workaround that involves pressing several buttons.
The Faderport classic Rec button, the Maschine Studio or the Atom SQ (Song button -> Rec) still won't work however with my original steps. Does somebody have a more modern Faderport (not a classic), and is able to follow the steps to reproduce in my original post please? Let me know. Thx.
Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb. Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental). Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths. |
Hi PreAl!
I can confirm this behaviour of the record arm button on a Faderport v2. It never works with an external instrument track. It also doesn't work with folders routed to a bus or VCA. Some very strange behaviours occurring there. My workaround also is the record-arm key command assigned to a button of my Loupedeck, which works in any configuration of tracks and folders kind regards wolfger |
Thanks Wolfger!
Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb. Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental). Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths. |
wolfgerb wroteHi PreAl! Oh boy - I see what you mean. Create say 5 audio tracks. Create a folder, and stick two audio tracks on it. Select any track, even outside the folder with a mouse With a mouse select the arm button associated with the folder, and the first audio track in the folder will arm which is expected behaviour (or however you've set it up within that folder). Now once again, Select any track, even outside the folder with a mouse. Then select the folder with a mouse. With a faderport select the arm record button, and that will record enable the last track selected, even outside the folder. Not good! Ouch....
Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb. Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental). Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths. |
Exactly, very disturbing behavior.
Workaround with loupedeck is ok for me. still wondering why developers didn't figure this out till now. faderport v2 is out for years now? |
I agree I'm perplexed on why this hasn't been sorted.
I'm in touch with Presonus support and pointing them to this thread. Strangely they say they don't have any controllers to run tests, maybe that's the reason. Maybe people with controllers don't bother creating tickets or forum posts!
Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb. Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental). Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths. |
So I suspect with the Faderport, if you assign F1,F2, F3, F4 to arm record (you are going to lose the ability to open inspector, editor, mixer, and browser, well one of these) to Track -> Arm that will work as expected with folders and instrument tracks assigned to hardware synths. It does with the "user" button on the faderport classic.
Still that's not a good workaround as an extra key has to be pressed which loses other functionality, and there is an an exposed "do not touch" dodgy button identified as "REC" still hanging around. My hunch is that within the source code of studio one, there are two ways to arm record, one is a legacy way which you cannot assign a keyboard shortcut to ("REC"), and another is "Track->Arm" which appears to work fine. That's a good sign, it means it should be simple enough to fix. So in the Studio One code they would need to delete the legacy code that handles that old "REC" arm record functionality, and then point the handler (could be multiple handlers for the controllers) to Track->Arm code instead, it's already there to be used. Then QA needs to test it on all the faderports, Atoms and Mackie. Job done. Even better, no firmware updates needed.
Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb. Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental). Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths. |
Tech support has submitted this to QA, although sadly I don't think tech support is telling them about this thread.
Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb. Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental). Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths. |
PreAl wroteTech support has submitted this to QA, although sadly I don't think tech support is telling them about this thread. They did. We will have an eye on this. Thanks for reporting! Ari
Ari Ahrendt - Quality Assurance Specialist
PreSonus Software Ltd. - Hamburg http://www.presonus.com/products/studio-one Modern electronic Synth Pop........../..........Musicproduction, Support & coaching http://www.denoisary.de/................./...........http://www.arimusik.de/ Windows 10 64-Bit, i7 6700k 4.0 GHz, 16GB RAM, 4TB SSD, Studio One 5 Professional |
PreAl wroteTech support has submitted this to QA, although sadly I don't think tech support is telling them about this thread. AriAhrendt wroteThey did. Thanks Ari, nice to know something is going on behind the scenes, appreciate your work.
Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb. Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental). Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths. |
wolfgerb wroteHi PreAl! PreAl wroteOh boy - I see what you mean. @wolfgerb Could you check this on 6.2.1? I think this is fixed at my end, would be nice to see if you've got this resolved too. Thx. (although the issue on the original post doesn't seem to be fixed )
Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb. Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental). Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths. |
PreAl wrotewolfgerb wroteHi PreAl! Hi, Hhmm, Rec-Arm still doesn't work with my Faderport V2 on VCA/Bus Folders over here in 6.2.1. It doesn't work on external Instr-Tracks either. It |
Oops, I screwed up following my my own steps to repro, it's still an issue on 6.2.1
Sorry to waste your time!
Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb. Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental). Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths. |