19 posts
Page 1 of 1
When using note repeat with input quantize results in wrong note lengths caused by the timing of the input trigger.
When a note is triggered ahead of the quantize value, the repeated notes are too long (overlapping). When a note is triggered behind a quantize value, the repeated notes are too short.

Also the first note triggered on or after the quantize tick, is consistently missing.

See vid with 7 MIDI in triggers, 3 ahead, 1 dead on, 3 behind.
phpBB [video]

OS: Windows 11 Pro | HW: Gigabyte Z690-UD-DDR4 • INTEL i7 12700K • 64GB • 3x EVO 860 • NVIDIA GT1030 (@WQHD) • RME AIO
User avatar
by jasonbrown19 on Sun Jul 23, 2017 5:16 pm
Hi Everyone,

I can also confirm that The "Note Repeat" function is basically unusable at the moment unless you use some kind of workaround which then takes more time and thus defeats the point in the feature being available in the first place.

Here's my version of what's happening:
https://answers.presonus.com/19440/note-repeat-malfunctioning

I hope this gets sorted as it's quite a big creativity killer.

Cheers,

Jason.
User avatar
by snb1 on Mon Jul 31, 2017 12:17 pm
Yes I just confirmed, I get the same results.

Studio One Pro 6.6 64 bit, macOS Monterey 12.6, 14" MacBook Pro M1 (2021),16gb ram, 512 SSD, 8-core CPU

SkipNo Beet
User avatar
by niles on Fri Sep 29, 2017 1:57 am
Still standing for 3.5.2

OS: Windows 11 Pro | HW: Gigabyte Z690-UD-DDR4 • INTEL i7 12700K • 64GB • 3x EVO 860 • NVIDIA GT1030 (@WQHD) • RME AIO
User avatar
by AriAhrendt on Wed Oct 04, 2017 2:01 pm
Can you show me your repeater plugin?
Or gimme the song file.

The video looks to me like the gate scale function.

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
User avatar
by scottmoncrieff on Wed Oct 04, 2017 3:01 pm
AriAhrendt wroteCan you show me your repeater plugin?
Or gimme the song file.

The video looks to me like the gate scale function.


He's not using a plugin, he's using the 'Note Repeat' function found on the 'Record Panel' as shown in the video. The function that is built into Studio One itself..

...
Niles, it would probably help if you actually described any issue's with spoken words in addition to the screencast, rather than relying on a just screen / program capture. The developers might be German but there's good chance they also understand English :D

THE INTRANCER- Digital 2D & 3D GUI / Music Artist |- Full Orchestral -Trance - Ambient - Film Scores 27 on S-Cloud 7000+genuine plays | 16 on S-Click | Studio One 3 Concept Re-Designs - Sample One XT | Reason X | S-O-3 Pro | Reaktor 6.0 | Reason 7 | C4D | CS6 |Win 7 64 Bit-Intel I7 [email protected],Focusrite Pro 14, ATH M50's, Casio XW P1&G1 Producer 20+ years - FOH - UK Stadium / Festivals) >>Studio One 3D GUI's<<
User avatar
by AriAhrendt on Thu Oct 05, 2017 8:52 am
Ah ok, gotcha. Note repeat, not note repeater. my fault. :)

Ok, let me see your video again.
What I see looks correct to me. And I try to explain you why.

Your main issue is that the lenghts are different, right? BUT you played everytime different lenghts while recording. So the grid doesn't mean, that every note has the same lenght. Why it should?! It is a normal MIDI keyboard input recording. The repeater just repeats the same length as the first incoming note. So it is always the same in every... hmm... note line.

What you additional doing is that you play not correct in timing. So because of the IQ (input quantize) Studio One records it perfectly on the next grid and stops recording exactly when you release the key. (note off) That means that the note is shorter than you played it, because you startet to early (S1 starts perfectly recording on grid) and ends perfect with the Note OFF incoming into studio one.

I hope that was not to confusing because of language issues.
The issue is very clear and I hope you get it now. :)

At the end - there is no software issue. Just a user input inaccuracy during recording.

Cheers
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
User avatar
by niles on Thu Oct 05, 2017 1:14 pm
AriAhrendt wroteYour main issue is that the lenghts are different, right?
Yes

AriAhrendt wroteBUT you played everytime different lenghts while recording.
No, the length of the input was always 2 beats (0000.02.00.00)

AriAhrendt wroteSo the grid doesn't mean, that every note has the same lenght. Why it should?! It is a normal MIDI keyboard input recording. The repeater just repeats the same length as the first incoming note. So it is always the same in every... hmm... note line.
Let me quote the manual under the section Note Repeat:
With Note Repeat enabled, any notes played during the current recording pass retrigger according to the current Quantize setting. For example, with a Quantize setting of 1/16, held notes create a series of 16th notes at those note values.

So what I expect when Input quantize is enabled, Quantize set at 1/16th and Note Repeat enabled too is: A series of 16th notes being retriggered as long as I hold the key. What you say, that notes being repeated with the same length as the first incoming note, doesn't make any sense because the repeater could only retrigger as soon as a note off is received then. ;)

AriAhrendt wroteWhat you additional doing is that you play not correct in timing. So because of the IQ (input quantize) Studio One records it perfectly on the next grid and stops recording exactly when you release the key. (note off) That means that the note is shorter than you played it, because you startet to early (S1 starts perfectly recording on grid) and ends perfect with the Note OFF incoming into studio one.
No not entirely. Like mentioned above I hold the note for 2 beats with input quantize enabled. So the input (Note On) should be exactly on the grid. Studio One quantizes the start of each retrigger correctly, however does not quantize the end correctly. So when I play the input note a fraction earlier than the quantize value the length of the retriggers will be too long. When I play the input note a little later than the quantize value the triggers will be too short.

AriAhrendt wroteI hope that was not to confusing because of language issues.
The issue is very clear and I hope you get it now. :)
The issue is very clear to me too, only I (and the manual) expect it to work differently from how it works now. ;)

AriAhrendt wroteAt the end - there is no software issue. Just a user input inaccuracy during recording
I doubt that.

OS: Windows 11 Pro | HW: Gigabyte Z690-UD-DDR4 • INTEL i7 12700K • 64GB • 3x EVO 860 • NVIDIA GT1030 (@WQHD) • RME AIO
User avatar
by AriAhrendt on Thu Oct 05, 2017 1:33 pm
niles wroteSo the input (Note On) should be exactly on the grid. Studio One quantizes the start of each retrigger correctly, however does not quantize the end correctly. So when I play the input note a fraction earlier than the quantize value the length of the retriggers will be too long. When I play the input note a little later than the quantize value the triggers will be too short.

The description is correct.
That is how it works.

Then end will not quantized. To what? The end is your note off. If you start earlier then it ends earlier.
So we really have to be carefull here not to get wrong expectations.

At the moment I can not see a software issue here.
It is just a behavior you don't like I guess. But this is not the nature of a bug.

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
User avatar
by niles on Thu Oct 05, 2017 2:22 pm
AriAhrendt wroteThen end will not quantized. To what?
Length to the current Quantize setting.

AriAhrendt wroteThe end is your note off. If you start earlier then it ends earlier.
If what you say is true (which I doubt it is) it still is a bug because the retriggers end later when the Note On is before the grid (earlier) and vice versa.

AriAhrendt wroteSo we really have to be carefull here not to get wrong expectations.
I literally expect what is written in the manual. Retriggers by the length of the quantize setting. When I set quantize to 1/4 and when holding a note I expect repeated notes with a length of 1/4th and when I set quantize to 1/16, I expect repeated notes with a length of 1/16th. If that expectation is wrong, the manual should be clearer on what actually happens.

AriAhrendt wroteAt the moment I can not see a software issue here.
Then I rest my case.
For fun run a Note Repeat session IQ enabled and disabled and compare the results.

AriAhrendt wroteIt is just a behavior you don't like I guess. But this is not the nature of a bug.
I don't use it so it's not relevant if I like it.

OS: Windows 11 Pro | HW: Gigabyte Z690-UD-DDR4 • INTEL i7 12700K • 64GB • 3x EVO 860 • NVIDIA GT1030 (@WQHD) • RME AIO
User avatar
by AriAhrendt on Thu Oct 05, 2017 2:43 pm
niles wroteLength to the current Quantize setting.

I think exaclty this is the missunderstanding.
There is no function in this case that stretches or cuts the lengths of notes. This is not part of IQ or Note Repeat.

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
User avatar
by niles on Thu Oct 05, 2017 3:01 pm
AriAhrendt wrote
niles wroteLength to the current Quantize setting.
I think exaclty this is the missunderstanding.
There is no function in this case that stretches or cuts the lengths of notes. This is not part of IQ or Note Repeat.
So why does the note length of retriggers change when changing the Quantize value?
And why are results with the same Note On message (on the grid) different when IQ is enabled or disabled?

Image

OS: Windows 11 Pro | HW: Gigabyte Z690-UD-DDR4 • INTEL i7 12700K • 64GB • 3x EVO 860 • NVIDIA GT1030 (@WQHD) • RME AIO
User avatar
by AriAhrendt on Thu Oct 05, 2017 3:07 pm
So I would say everything works now.
You just showed it. All in the expected length. The question is why don't you do this what works when you need it?

I have the feeling, that I talking against a wall. If I try to explain one specific example, then another show case is the answer. I think I spent enough time with this for now. I told you everything. For this reason I am out of here.

If you have more real issues and bugs feel free to write to the support.
And discuss this issue with the support.

good night.
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
User avatar
by niles on Thu Oct 05, 2017 3:19 pm
No it does not work because the Note On was started exactly at bar 3 (hence the first retrigger is missing, which was part of this report) and the issue only arises when the Note On is not exactly on the grid.

Good night to you too.

OS: Windows 11 Pro | HW: Gigabyte Z690-UD-DDR4 • INTEL i7 12700K • 64GB • 3x EVO 860 • NVIDIA GT1030 (@WQHD) • RME AIO
User avatar
by Skaperverket on Thu Oct 05, 2017 3:29 pm
I know niles can speak for himself, but I'd like to add that I totally agree with niles' views on this one.

P.S.: According to music theory, a quarter note is the description of the length of a note (not the distance between the starting point of each note).
User avatar
by niles on Fri Oct 06, 2017 2:38 am
Skaperverket wroteI know niles can speak for himself, but I'd like to add that I totally agree with niles' views on this one.
Thank you.
If Ari opened the first version where Note Repeat was introduced (Studio One 3.0.0.33329 Win x64 (Built on May 19 2015)) he would have noticed it worked just like explained in the manual and how I expect it to work which is different from how it works now.
There was no need to patronize me like he did a few posts above.

OS: Windows 11 Pro | HW: Gigabyte Z690-UD-DDR4 • INTEL i7 12700K • 64GB • 3x EVO 860 • NVIDIA GT1030 (@WQHD) • RME AIO
User avatar
by scottmoncrieff on Fri Oct 06, 2017 8:44 am
niles wroteThere was no need to patronize me like he did a few posts above.


Arguing with Ari on Studio One should always be done at arms length and with caution ;) .

Interestingly though, the Note Repeat function is something I've never really took too much notice of. I think that's party due to me having arpeggiator functions on my main keyboards over the years, I had a Yamaha DJX for over a decade before the XW's I use now. Still the Note Repeat function is kinda cool and useful, it's sort of like an in-between between step and realtime recording in a way. I came from P-Heads Reason I which left at version 7, it doesn't do step time nor have note repeat on the sequencer, so for me how it works doesn't really matter too much, it does what it does, and don't have an issue with it particularly.

Side note..FR. I'd like to see them add 'rest' interval separations in step-time recording like one has on sound trackers between notes, for more flexible program recording.

THE INTRANCER- Digital 2D & 3D GUI / Music Artist |- Full Orchestral -Trance - Ambient - Film Scores 27 on S-Cloud 7000+genuine plays | 16 on S-Click | Studio One 3 Concept Re-Designs - Sample One XT | Reason X | S-O-3 Pro | Reaktor 6.0 | Reason 7 | C4D | CS6 |Win 7 64 Bit-Intel I7 [email protected],Focusrite Pro 14, ATH M50's, Casio XW P1&G1 Producer 20+ years - FOH - UK Stadium / Festivals) >>Studio One 3D GUI's<<
User avatar
by garryknight on Fri Oct 06, 2017 12:02 pm
I also agree with Niles that the observed behavior doesn't seem to agree with what the manual states. And it's because of this that I don't use Note Repeat.

Garry Knight
Studio One 3 Professional
Melodyne Editor 4, NI Komplete 11
Focusrite Scarlett 2i4 audio interface
Windows 10 Professional 64-bit, 16 GB RAM, Core i5
Microsoft Surface Pro 3, Core i7, 8GB RAM, 128 GB SSD
Nektar Impact LX49+, Samson Graphite 25, and Korg microKey 25 MIDI controllers
Novation ZeRO SL MkII mixing control surface
Korg nanoKontrol 2 mixing control surface
Reaper, Logic Pro X, GarageBand
https://soundcloud.com/garryknight
User avatar
by jasonbrown19 on Sat Oct 07, 2017 6:59 am
Hi folks,

I have to chime in on this too as Niles is totally correct in everything that he's stated on this topic and he and I actually had a conversation on this forum a few months back when I made a post on here regarding the same issue whilst using the Impact drum machine.

You can read my version of the problem at the top of this thread underneath Niles' initial post.

I'd just like to say that the condescending way in which Ari replied to Niles' posts really was unwarranted and uncalled for especially as seen as Niles makes good posts on here.

Anyway that's my two cents on the topic and I really wish Presonus would fix this bug as it's actually quite a big issue for some of us.

Take it easy everyone,

Jason.

19 posts
Page 1 of 1

Who is online

Users browsing this forum: No registered users and 42 guests