PreSonus Forums

Hi folks. I was working in Studio One 4 Pro on my PC yesterday - tracking V-Drums, etc. — and decided I'd begin to list problems/potential bugs that I'm encountering. Just out of curiosity, I'm wondering if anyone else is experiencing these three "issssues."

1) CC4 is not recorded in loop mode on a MIDI track via an input instrument/controller if the output is left empty.

2) Faderport (classic version): When pressing "rec" button to engage record on a single instrument track, it will actually engage record for ALL instrument tracks sharing that instrument.

For instance, yesterday, I was tracking V-Drums with SSD5 and when I pressed the "rec" button on the Faderport (classic, again), the record mode was activated for three instrument tracks, the one I was recording on, and also the two below it that were using SSD5 as their output instrument.

When using a mouse in the arrange view and clicking on a single track, this doesn't happen.

3) Clicking on a MIDI note: ]when an instrument such as a Presence XT synth is engaged, clicking on a MIDI note does not reliably play back that sound. I'm using a Focusrite interface set to 128 samples, which is fine for this use, and when I click on some notes, they sound back immediately, while others either don't sound at all or there is a long delay before they sound. This is needed for when you want to hear the pitch of a note before moving it around manually to another note lane.

[UPDATE re; #3: Seems to work okay on my Mac using a new song file; maybe it's file specific.]

If anyone cares to comment on any of these issues, I just want to get a bearing on whether they are common occurrences or whether they are just a product of my wild imagination.

Stop. No. I'm not crazy. Let go of me. Noooooooo! Don't taze me, bro.
[tzzzzzzzzzzz] [tzzzzzzzzzz] [tzzzzzzzzz]
[Call to Presonus HQ.]: "We have the suspect apprehended, Your Emminence."
[roll credits]

1. confirmed
2. dont own a faderport
3. cant confirm, can you post a song where this is happening? maybe its because of something else.

2. I own a faderport - I guess that is true although I would never have different tracks sharing the same instrument. Do you need to do that?

Two separate answers:

robertgray3 wrote...
3. cant confirm, can you post a song where this is happening? maybe its because of something else.

Thanks. So, you are able to click any MIDI note and it returns a sound immediately, without delay?

garyshepherd wrote2. I own a faderport - I guess that is true although I would never have different tracks sharing the same instrument. Do you need to do that?

I use them as "sectioned" tracks so that I can focus on particular sections. For example, one track will be used just to record "intro takes," while another is for "verse takes" etc.

That's why I do this—it keeps me focused on the part and avoids clutter cause I like to record a lot of takes. That's also why I noticed that all those tracks were being record activated.

robertgray3 wrote...
3. cant confirm, can you post a song where this is happening? maybe its because of something else.

UPDATE re; #3:
I tested it on my Mac and it seems to work okay there.

Maybe it actually is a problem that's specific to that file. However, if I'm working on one particular song file for weeks, I don't really care whether MIDI note monitoring works in a brand new file because I need it in the one I'm working on.

So I guess the question is: What makes it unreliable in that file and not another?

How would anyone know. It's such an esoteric thing to begin with: Some notes sound, others don't, but they're all part of a working, active MIDI file. Pffff...

roland1 wrote

garyshepherd wrote2. I own a faderport - I guess that is true although I would never have different tracks sharing the same instrument. Do you need to do that?

I use them as "sectioned" tracks so that I can focus on particular sections. For example, one track will be used just to record "intro takes," while another is for "verse takes" etc.

That's why I do this—it keeps me focused on the part and avoids clutter cause I like to record a lot of takes. That's also why I noticed that all those tracks were being record activated.

I understand - clutter indeed.

garyshepherd wrote

roland1 wrote

garyshepherd wrote2. I own a faderport - I guess that is true although I would never have different tracks sharing the same instrument. Do you need to do that?

I use them as "sectioned" tracks so that I can focus on particular sections. For example, one track will be used just to record "intro takes," while another is for "verse takes" etc.

That's why I do this—it keeps me focused on the part and avoids clutter cause I like to record a lot of takes. That's also why I noticed that all those tracks were being record activated.

I understand - clutter indeed.

Most of the time I will also have a separate song file for recording V-Drums with just a stereo mix of the song for cueing. That keeps things in their place when having to add or redo parts.

roland1 wroteThanks. So, you are able to click any MIDI note and it returns a sound immediately, without delay?

Yes. sometimes issues are complex. see if you can narrow it down. You said its a MIDI note that's part of a MIDI file? is a MIDI note in a MIDI file or a Note Event in an Instrument Part? two different things.

Oh no. We're at the Tower of Babel in DAW specific semantics.

I'm gonna write this like a child, not as an insult to you, but because I don't want to go into the manual and have to learn to speak Ancient Presonese like a scholar.

Here's what I mean:

When I play my keyboard, a rectangular shaped "note" is created inside of the rectangular shaped object that is in the instrument track I'm recording on—I hope that's called an "event." The thing I recorded, I refer to as a "note."

When I touch that "note" using a mouse click, sometimes it makes a sound, sometimes it doesn't. And sometimes it makes a sound, but only after a long delay (500ms).

That's all I know. I swear.

robertgray3 wrote

roland1 wroteThanks. So, you are able to click any MIDI note and it returns a sound immediately, without delay?

Yes. sometimes issues are complex. see if you can narrow it down. You said its a MIDI note that's part of a MIDI file? is a MIDI note in a MIDI file or a Note Event in an Instrument Part? two different things.

Win 10 Studio One Pro 64
Series III 24 board and Presonus Studio 192
Running Maximum Dropout Protection with Enable low latency monitoring for instruments on or off.

Anytime I select a midi note I hear the sound from the instrument. It is not delayed.

roland1 wroteOh no. We're at the Tower of Babel in DAW specific semantics

Super entertaining but people can’t help you out unless they know what you’re doing. I can audition note events in instrument parts without any delay. If you post a song file I can at least see what plugins are on the track. Maybe somethings reporting latency incorrectly, who knows, but it’s clearly something else otherwise me and Bbd would have been able to duplicate it.

robertgray3 wrote

roland1 wroteOh no. We're at the Tower of Babel in DAW specific semantics

Super entertaining but people can’t help you out unless they know what you’re doing. I can audition note events in instrument parts without any delay. If you post a song file I can at least see what plugins are on the track. Maybe somethings reporting latency incorrectly, who knows, but it’s clearly something else otherwise me and Bbd would have been able to duplicate it.

I did say it's working fine on my Mac. It's just on the PC file where it's wonky. But I guess, in summary, this feature "works" — at least for you guys in your specific files.

(Wasn't there also a setting somewhere where you could choose to have MIDI notes (those rectangular things I'm recording) sound out when clicked? I can't find that for some reason. Course, I also don't want to make a career out of trying to find out why S1 isn't working for me at various times.

yes its called Audition Notes its on the left side of the Music Editor and its the feature Bbd and I enabled to test your problem

I've been frantically looking in all the "wrench" menus and in the advanced MIDI options for that setting. DUH! Knew I saw it somewhere. I think I've got my head in too much software, including 3D...

Point is, though, that this setting is checked in my MIDI files on both Mac & PC.

I'm using the Presence XT Elec Piano preset and pressing randomly on the "notes" allows some to sound, other not (well, they actually make a clicking sound as if they're at least trying.).

On the track above it, which is using a Korg plugin, the same thing happens.

No idea.

robertgray3 wroteyes its called Audition Notes its on the left side of the Music Editor and its the feature Bbd and I enabled to test your problem

Thanks, Bbd.

I have Minimum Dropout Protection w/enable low latency monitoring for instruments on.

I just created a new song, put Presence in there; "Flugelhorn" just for kicks, added a few random midi notes via the pencil tool, humanized them a couple of times and then started "auditioning" them.

Same result. Some sounded, others didn't. But there is a low level click as though they are getting stuck at the start of the transient but not going further.

That's on my PC Win 10, S1 4 pro. v4.14. Latency is 128 samples. No unusual settings.

Bbd wroteWin 10 Studio One Pro 64
Series III 24 board and Presonus Studio 192
Running Maximum Dropout Protection with Enable low latency monitoring for instruments on or off.

Anytime I select a midi note I hear the sound from the instrument. It is not delayed.

Babel (from the online manual):

"Audio Events and Instrument Parts are referred to collectively as Events in this manual."

Why not Audio Events and Intrument events?
Or Audio Parts and Instrument Parts?

Instead, you have one that is a "part," one that is an "event," and yet both are "events."

whahahahaha....where's my cocktail of psychotropic drugs.

I'm also not seeing the word "MIDI note" anywhere, just instrument data, which could mean a multitude of things, including CC info, volume, pitch, banks and presets, etc.

If someone plays a "C" on a trumpet, they are playing a "note." That's all I know, it seems.

roland1 wroteThanks, Bbd.

I have Minimum Dropout Protection w/enable low latency monitoring for instruments on.

I just created a new song, put Presence in there; "Flugelhorn" just for kicks, added a few random midi notes via the pencil tool, humanized them a couple of times and then started "auditioning" them.

Same result. Some sounded, others didn't. But there is a low level click as though they are getting stuck at the start of the transient but not going further.

That's on my PC Win 10, S1 4 pro. v4.14. Latency is 128 samples. No unusual settings.

Bbd wroteWin 10 Studio One Pro 64
Series III 24 board and Presonus Studio 192
Running Maximum Dropout Protection with Enable low latency monitoring for instruments on or off.

Anytime I select a midi note I hear the sound from the instrument. It is not delayed.

Please open a Support ticket for this issue.
Thanks.

I just used my (classic) Faderport last nite to record without issues.

However, I used 2 audio tracks (stereo) for my acoustic guitar (44.1kHz).
When I get the part smoothed out, I'll switch to 48kHz.

I have Audio Dropout set to 'medium' and 256 samples.

Hi Scottyo7. The issue I'm having with the faderport is in regards to record arming instrument (MIDI or whatever they're called in Studio One) tracks. So it's not with audio tracks, just with tracks that are using a virtual instrument to play note events, data, parts, whatever.

When I try to record arm a single instrument track, it arms all the tracks that are sharing that instrument plugin. When I click to record arm using a mouse, this does not happen. So it's something that the faderport is doing when it focuses on that track.

scottyo7 wroteI just used my (classic) Faderport last nite to record without issues.

However, I used 2 audio tracks (stereo) for my acoustic guitar (44.1kHz).
When I get the part smoothed out, I'll switch to 48kHz.

I have Audio Dropout set to 'medium' and 256 samples.

robertgray3 wrote1. confirmed

I can confirm this too, but it is about any midi CC at all - not just cc4.

I tested from keyboard and mousewheel or sustain pedal etc - same thing.

If to do a bug report I mean, more descriptive of the problem.