WATCH ALL STUDIO ONE WITH JOE GILDER VIDEOS: • Studio One with Joe Gi... PRESONUS SPHERE: bit.ly/3zku0vN STUDIO ONE: bit.ly/2Tfygx0 #StudioOne #JoeGilder OR #StudioOneMinute
Between Joe & Gregor my interest in StudioOne keeps growing. Close to making the switch too, and also going full SoundGrid Superack with a server and Presonus miser (hopefully still supports soundgrid plus i wanted the flexibility to take the studio system live maybe two times a year)
That is awesome. I wish I had seen this a month ago. I watched Gregor show three options and I just completed a whole song using Melodyne which works great but was much more time consuming I think. Can't thank you both enough for all of the awesome insight, especially for a beginner like me.
I've been doing it wrong for ages. This technique helps a lot. I was using too many bend markers to move the downbeats. This makes a more natural sounding transition - the last note of the phrase before the timing issue is just held longer. Thanks for this. S1 is so easy to use.
USEFUL TIP: you can just double click on event while using the range tool to split the event. no need to use "alt/option" in this case. that can improve your efficiency quite much) Thanks for your tutorials, Joe!)
Thank you Joe I learn quite a bit from your vedios .this one was just what I needed .You bring to light functionality with the mouse and keypad You Rock TOZZ
Great video - I would like to hear you compare and contrast using this method vs. adjusting the timing with Bend markers. It seems like for tiny slides like these, bending would have basically no artifacts and be easier to use, but I'm sure there are trade-offs.
Hey Joe, You likely know this already, but you don't have to select command to bring up the split tool. If it's underlined then when the cursor is a crosshair, simply double click and it will split the clip at the selected point.
With a mouse, at least, double-clicking will tend to jiggle to pointer a bit - might end up cutting in the wrong place. Not a big deal, but that's why the Control key alternate tool might be better.
You can get a thing with finger style bass where the player may hit the string a bit with their finger then drag their finger off a fraction later. That can make the waveform Look like the note is starting earlier than it actually is; Then if you go to slide it visually You can make it sound late behind the beat. Sometimes it reveals itself graphically as it can look like a Double Attack ...
cubase has " edit hitpoints " option and thats way accurate and better to work with. This is the only limitation due to which i have not been convinced to shift from cubase to studio one and Vari audio also. Rest you guys are doing good work. keep it up.
i personally don’t use the bend tool, but i believe it would cause some pitch/note issues and could sound detuned, if used too much. the slip event keeps everything clean, especially with crossfades
I always wondered how you got the little underline on some of the tools! Mine was always stuck on the mute tool (as though S1 was trying to tell me something)
Thx Joe! I am dealing with about 4 measures of bass and kick drum out of time and this is exactly what I need. My only issue is that I do not belive the slip function is available in my version 4. I' m near the end of a 7 song static mix phase of an EP project and don't want to risk downloading new version 6 and wrecking this whole project with losing plugins, new EQs etc etc etc. I'll have to suffer thru slight trial and error event moves( pops... Hopefully can be fixed with criss fades ) the hard way. The out of sync passage is subtle, but is an annoying distraction now that I know its there.( can't be unheard)
you know your screwed when you acting like stan (eminems stan stalker) but you aint stalking maddonna NOPE you chose to memorize every word that a chubby middle age rock proddy and sit watching him for over a 100 hours, it sounds bad like this but i am SLOWLY IMPROVING and thus cant stop
No timestretching which is also a part of fixing timing issues, imo. Timestretching also only seems to work by grabbing the event at the end - not possible on the start. Which means if you have the end correct and want to leave it - and you want to stretch from the start - it is not possible and you have to repeat "stretching the end + moving the whole event back to the right again" several times in a trial and error procedure. OR am I missing out on something?
You can do the equivalent of timestretching using Bend markers instead. You generally would work from the "middle" in that case - if you move a bend marker to the right, it will stretch the audio from the previous bend marker to the one you're moving, and shrink the audio from the one you're moving to the next one.
@@chrishillery yeah I know, but in my experience it is way better to timestretch whole events. The bend tool always ends up in a complete mess. You forgot to set an additional bend marker and you fuck up the whole event. I like to cut the event and timestretch only a whole event, this way I can be sure I don't ruin the previous part. But thank you a lot for providing a working solution to my problem, which is very kind of you.
When I want to record I press the star * button to record and always the cursor jumps from the bar I want and goes to the "major bar" to begin recording. So the only solution is " Autopunch " or can it be solved somehow??
@PreSonus are you aware of this problem? So it happens sometimes, you lose your audio, your Master bus pegs out and freezes at 666db??? Can it be any number but 666? Please, it needs to be fixed!!! Thanks
if it's a low #, I believe it's the number of times that it has clipped? If it's 666, its an error code. It's probably a plugin that hasn't been updated to work well with the version of Studio One you are using.
@@lofomuses I am particular what plug ins I use, I use top notch equipment and update and upgrade on regular basis. My Studio One 5 Pro is the latest upgrade 5.4 There is a forum since 2015 and no one at PreSonus is paying attention.
Hey Joe, what camera you used to record this vid (I suppose that I wasn't the first who asked). BTW. Lemme know if you'll need a better basslines than your own! XD Take care!
detection slice mode in studio one is horrible. it does not take transients where it should be and is different from stretch mode. I will never understand why studio one does not solve this terrible error. Two types of detection and the one that is really needed to not modify the waveform is the slice mode and it does it disgustingly. I want to go back to protools for this simple detail
Impossible to consider a purchase of Studio One 6 Pro, this DAW is not able to quantize Drums properly. This PRO feature is mandatory to avoid losing time on a customer production. When you quantize a Drums, it doesn't mark the beginning of the transient and doesn't align the hits correctly on the grid. PT, Logic, Cubase, all the other DAW can do this, it's a basic today. The only answer from Presonus for the last 7 years is: Please vote for this new feature". This is not a feature request, actually it's a bug.
What happens when you choose Action/Quantize? I empathize with you, as I'm a drummer myself. Actually, the issue that drives me nuts is the counter. When I used Sonar, going back to DOS 5, I was used to being able to break ea. 1/4 note into 120 ticks. It made quantization SOO MUCH easier than this.
Quantizing isn't always the most musical approach. It's also is harder to get right on bass in particular - because of the long waveforms due to low frequency, the detection of transients can be pretty far off where you'd want them to be.
@@chrishillery What does not a musical approach mean? This is juggling with terms, nothing more. Modern algorithms keep the original sound quality. And if the transients are far from the desired point, then this means only one thing - the bass part is unusable. And in this particular case, on this particular video, just an option is presented that can be easily solved by simple quantize and without that unnecessary waste of time that could be spent on other creative ideas.
@@dimafg1 By "isn't always the most musical approach", I meant that quantizing tends to make parts sound more robotic and less human. It depends on the strength of the quantize, of course. But for some genres, you want to leave in a lot of the bits where the player wasn't strictly "in time" and only fix the most egregious timing errors. A one-click quantize process can't know those nuances. Hence, not the most musical. As for the second part of my note about bass, you missed my point. If you have a low bass part without a lot of clickiness in the attack, the transients that your software will detect can be pretty unreliable. The low E on an electric bass is 41.2Hz, which means a single cycle of the waveform is over 24ms long. That might not look like a transient at all to your software, and even if it does, the exact time it'll pick could be off from what you'd hear as the "start of the note" by a significant amount. So now if you ask your software to quantize these poorly-detected transients, well, garbage in, garbage out. It could end up sounding sloppier than the original recording. It doesn't have anything to do with how well the part was played at all. If you're working in a genre where regimented timing is desirable, and if just clicking Audio Quantize works for you, great! But I think it could very easily have produced noticeably less satisfying results for the part Joe was playing here.
@@chrishillery If your arguments were voiced 20 years ago, I would certainly agree with you. But now 2021 is already ending. And therefore: As for what you mentioned about "robotic", that's exactly what I'm saying that modern processing algorithms are such that they just exclude this "robotization", if, of course, do it in moderation. And quantization by no means implies a strict placement of the transient in the share. You can safely specify the degree of quantization. And you can also adjust these transients yourself as you like manually if you suddenly don't like something. Or, in general, specify all the transients that you want to shift yourself, without resorting to quantization. This is exactly how I corrected the sound 20 years ago, as shown in this video. This is exactly how I worked. But nowadays, in the presence of more advanced algorithms for working with sound and faster solutions than those indicated here and, of course, have the right to exist, but taking on a large amount of resources and time, I see no reason to solve such problems in this way. In no way do I impose my point of view. As for the second point about bass, I didn't miss it. It's just that in this case, in the right parts of the bass, I independently apply the transient and already move it to the right space as I need it. And "stretching" this kind of sound doesn't distort the sound. But just in such cases, the method indicated in this video can produce an unwanted sound effect - with or without crossfade. Don't think that I rely only on software and its algorithms and that I think it will do everything on its own. Not at all. It is only to help and nothing more. To achieve a good sound, we only use the capabilities of the software, but we shape everything ourselves if we want to achieve a perfect and natural sound;) And I work in different directions, not only and not so much in electronic music, where transients are mainly located exactly in beats. It is in this direction that I do not work very much. I have to work a lot both in rock and jazz. I often record multitracks of groups, and I personally record my parts from both bass and guitars, which I also correct later. And not the first year;) It seems to me that you made the wrong conclusion about what I am;) If I am talking about quantize, it does not mean that I have nothing to do with live music;)
Thanks for that! However, it’s strange watching you fix bass music mistakes while making information video mistakes. For me it’s difficult because I’m paying close attention. So to first learn a mistake, then backtrack to the right way or word in a lesson is confusing. Maybe edit your videos to always relay correct info the first time. Cheers!
I can't say enough how much I appreciate all that you do! You are the reason I chose Studio One and I am so happy that I did! Your videos are awesome!
Between Joe & Gregor my interest in StudioOne keeps growing. Close to making the switch too, and also going full SoundGrid Superack with a server and Presonus miser (hopefully still supports soundgrid plus i wanted the flexibility to take the studio system live maybe two times a year)
Oh thank GOD for this! We are tracking our EP and I needed this but didnt know how to phrase it.
That is awesome. I wish I had seen this a month ago. I watched Gregor show three options and I just completed a whole song using Melodyne which works great but was much more time consuming I think. Can't thank you both enough for all of the awesome insight, especially for a beginner like me.
Good video, but you can't beat Bend markers for this kind of job: quicker, cleaner and less steps.
I've been doing it wrong for ages. This technique helps a lot. I was using too many bend markers to move the downbeats. This makes a more natural sounding transition - the last note of the phrase before the timing issue is just held longer. Thanks for this. S1 is so easy to use.
Dude! you are always so helpful!
USEFUL TIP:
you can just double click on event while using the range tool to split the event. no need to use "alt/option" in this case. that can improve your efficiency quite much)
Thanks for your tutorials, Joe!)
thanks man!
Thank you Joe
I learn quite a bit from your vedios .this one was just what I needed .You bring to light functionality with the mouse and keypad
You Rock
TOZZ
Great video - I would like to hear you compare and contrast using this method vs. adjusting the timing with Bend markers. It seems like for tiny slides like these, bending would have basically no artifacts and be easier to use, but I'm sure there are trade-offs.
i liked this with my several accounts. This is way too helpful. Thank you!
Hey Joe, You likely know this already, but you don't have to select command to bring up the split tool. If it's underlined then when the cursor is a crosshair, simply double click and it will split the clip at the selected point.
Very helpful, Joe. Thanks a bunch. :)
I'm just so glad I picked the right section!!
Select all the events and press command+b when you're done
You can also split the clip by double-clicking in the top half. (You need the 'link arrow and range tool' active).
Thank you! Great tip!
With a mouse, at least, double-clicking will tend to jiggle to pointer a bit - might end up cutting in the wrong place. Not a big deal, but that's why the Control key alternate tool might be better.
You can get a thing with finger style bass where the player may hit the string a bit with their finger then drag their finger off a fraction later.
That can make the waveform Look like the note is starting earlier than it actually is; Then if you go to slide it visually You can make it sound late behind the beat.
Sometimes it reveals itself graphically as it can look like a Double Attack ...
This is very helpful, thank you for sharing!
chef's kiss
This makes my life more simple!!!! Thanks Presonus for this
hey Joe, always grateful to you, I worship your deep knowledge. Correct pronunciation is "translusent"
Thanks Joe. Guess my sense of time isn't very sharp...the original bass recording and the final edited version both sounded fine and the same to me!
cubase has " edit hitpoints " option and thats way accurate and better to work with. This is the only limitation due to which i have not been convinced to shift from cubase to studio one and Vari audio also. Rest you guys are doing good work. keep it up.
Joe is there for us😍
@Jo -- Another better options is, edit it with Melodyne and fix the timing with Quantize time macro... easy as that
Why wouldn't use the audio bend tool to do this sort of stuff?
What would be the difference, pros and cons of using the bend tool instead?
i personally don’t use the bend tool, but i believe it would cause some pitch/note issues and could sound detuned, if used too much. the slip event keeps everything clean, especially with crossfades
Your voice is so god damn smooth
Def watching this after work. I’ve been wondering how to do this for a few years, having latency issues
Dang, I was going to say the endings and you just chose one spot 😅. Thanks for your great content always Studio One Team 💪🏽💪🏽💪🏽
omg, the slide feature thingy is fantastic, thx
Awesome. Would be nice to learn more about the slip function with editing vocals
Seems like maybe Studio One needs a setting to "Automatically apply crossfades when slipping audio events"!
I always wondered how you got the little underline on some of the tools! Mine was always stuck on the mute tool (as though S1 was trying to tell me something)
And if you have smart tool engaged, with double click you can also cut, which is the best :)
Wow! I'm tightening acoustic guitars as we speak. Nice refresher.
Great video JOE!!! like always!
thats some good helpful info
Joe how did you know I was having hard time timing my vocals this morning 🙏
Joe... my Dukes... whatca great tut on how to Pockt edit is it!!!
Where do I find all the shortcut page so I can add them to my memory???☆
Man Joe makes that bass look like an ukelele hahaha
Thanks again
Thx Joe! I am dealing with about 4 measures of bass and kick drum out of time and this is exactly what I need. My only issue is that I do not belive the slip function is available in my version 4. I' m near the end of a 7 song static mix phase of an EP project and don't want to risk downloading new version 6 and wrecking this whole project with losing plugins, new EQs etc etc etc. I'll have to suffer thru slight trial and error event moves( pops... Hopefully can be fixed with criss fades ) the hard way.
The out of sync passage is subtle, but is an annoying distraction now that I know its there.( can't be unheard)
Thank you for all the tips 👍
I’m going to have to go back and fix every song I’ve ever recorded now 😂
thanks joe
its very helpfull
Perhaps this can be the start for quantising if things are off to far?
Joe's the best! That was very helpful!
When audio quantize screws up your sound this is the right way to do it.
No! its not "Translucent" Its "Translucent" Happy to help any time. Oh! Good vid by the way. You "Translucent" guy you. :)
Fuck me im literally messing with a sample and thinking about this. PERFECT.
Thx Joe... 😃 👍 ❤️
you know your screwed when you acting like stan (eminems stan stalker) but you aint stalking maddonna NOPE you chose to memorize every word that a chubby middle age rock proddy and sit watching him for over a 100 hours, it sounds bad like this but i am SLOWLY IMPROVING and thus cant stop
In presonus Midi generated vst and instrument can't be used on one same track. Please make it possible like logic pro or Bitwig
No timestretching which is also a part of fixing timing issues, imo. Timestretching also only seems to work by grabbing the event at the end - not possible on the start. Which means if you have the end correct and want to leave it - and you want to stretch from the start - it is not possible and you have to repeat "stretching the end + moving the whole event back to the right again" several times in a trial and error procedure. OR am I missing out on something?
You can do the equivalent of timestretching using Bend markers instead. You generally would work from the "middle" in that case - if you move a bend marker to the right, it will stretch the audio from the previous bend marker to the one you're moving, and shrink the audio from the one you're moving to the next one.
@@chrishillery yeah I know, but in my experience it is way better to timestretch whole events. The bend tool always ends up in a complete mess. You forgot to set an additional bend marker and you fuck up the whole event. I like to cut the event and timestretch only a whole event, this way I can be sure I don't ruin the previous part. But thank you a lot for providing a working solution to my problem, which is very kind of you.
Now serious. Is there and way to quantize to grid with slip-edited waveforms ?
No timestreching involved.
Amazing bro... Thanx
Very helpful!
Coming from Pro Tools and moving to studio one. Is there a tab to transient like feature for quick edits?
great tips.
Best way to fix timing issues..? - Practice!
Thanks for the video! I like your click sound. Is that custom?
Is there a Studio One specific keyboard out there?
When I want to record I press the star * button to record and always the cursor jumps from the bar I want and goes to the "major bar" to begin recording. So the only solution is " Autopunch " or can it be solved somehow??
@PreSonus are you aware of this problem? So it happens sometimes, you lose your audio, your Master bus pegs out and freezes at 666db??? Can it be any number but 666? Please, it needs to be fixed!!! Thanks
if it's a low #, I believe it's the number of times that it has clipped? If it's 666, its an error code. It's probably a plugin that hasn't been updated to work well with the version of Studio One you are using.
@@lofomuses I am particular what plug ins I use, I use top notch equipment and update and upgrade on regular basis. My Studio One 5 Pro is the latest upgrade 5.4 There is a forum since 2015 and no one at PreSonus is paying attention.
I think if we can get latency correct it would help with sibilance better .
Please try to slow down when explaining your edit tools. Thanks
Hey Joe, what camera you used to record this vid (I suppose that I wasn't the first who asked).
BTW. Lemme know if you'll need a better basslines than your own! XD
Take care!
3 people that prob don't even know what avid protools is dislike studio one versatility, because yeah, they are pros.
new room?
You mean sockeye salmon?
No time stretching transient quantization like Ableton Live, Logic or Maschine? Literally 5 seconds to fix this in Ableton.
You can do that too. Just detect transients and then drag them wherever you want.
i didn't even hear it. i'm fucked.
detection slice mode in studio one is horrible. it does not take transients where it should be and is different from stretch mode. I will never understand why studio one does not solve this terrible error. Two types of detection and the one that is really needed to not modify the waveform is the slice mode and it does it disgustingly. I want to go back to protools for this simple detail
U missed 6.6.3... 😋
...and your Silverface de Luxe is not visible! A No-Go 😔
..*meduckingfortheslap*
Impossible to consider a purchase of Studio One 6 Pro, this DAW is not able to quantize Drums properly. This PRO feature is mandatory to avoid losing time on a customer production. When you quantize a Drums, it doesn't mark the beginning of the transient and doesn't align the hits correctly on the grid. PT, Logic, Cubase, all the other DAW can do this, it's a basic today. The only answer from Presonus for the last 7 years is: Please vote for this new feature". This is not a feature request, actually it's a bug.
I haven’t had any problems with my Q 🤷♂️
What happens when you choose Action/Quantize? I empathize with you, as I'm a drummer myself. Actually, the issue that drives me nuts is the counter. When I used Sonar, going back to DOS 5, I was used to being able to break ea. 1/4 note into 120 ticks. It made quantization SOO MUCH easier than this.
Why are these complications when you can apply quantize with one click?
Quantizing isn't always the most musical approach. It's also is harder to get right on bass in particular - because of the long waveforms due to low frequency, the detection of transients can be pretty far off where you'd want them to be.
@@chrishillery What does not a musical approach mean? This is juggling with terms, nothing more. Modern algorithms keep the original sound quality. And if the transients are far from the desired point, then this means only one thing - the bass part is unusable. And in this particular case, on this particular video, just an option is presented that can be easily solved by simple quantize and without that unnecessary waste of time that could be spent on other creative ideas.
@@dimafg1 By "isn't always the most musical approach", I meant that quantizing tends to make parts sound more robotic and less human. It depends on the strength of the quantize, of course. But for some genres, you want to leave in a lot of the bits where the player wasn't strictly "in time" and only fix the most egregious timing errors. A one-click quantize process can't know those nuances. Hence, not the most musical.
As for the second part of my note about bass, you missed my point. If you have a low bass part without a lot of clickiness in the attack, the transients that your software will detect can be pretty unreliable. The low E on an electric bass is 41.2Hz, which means a single cycle of the waveform is over 24ms long. That might not look like a transient at all to your software, and even if it does, the exact time it'll pick could be off from what you'd hear as the "start of the note" by a significant amount. So now if you ask your software to quantize these poorly-detected transients, well, garbage in, garbage out. It could end up sounding sloppier than the original recording. It doesn't have anything to do with how well the part was played at all.
If you're working in a genre where regimented timing is desirable, and if just clicking Audio Quantize works for you, great! But I think it could very easily have produced noticeably less satisfying results for the part Joe was playing here.
@@chrishillery If your arguments were voiced 20 years ago, I would certainly agree with you. But now 2021 is already ending. And therefore: As for what you mentioned about "robotic", that's exactly what I'm saying that modern processing algorithms are such that they just exclude this "robotization", if, of course, do it in moderation. And quantization by no means implies a strict placement of the transient in the share. You can safely specify the degree of quantization. And you can also adjust these transients yourself as you like manually if you suddenly don't like something. Or, in general, specify all the transients that you want to shift yourself, without resorting to quantization. This is exactly how I corrected the sound 20 years ago, as shown in this video. This is exactly how I worked. But nowadays, in the presence of more advanced algorithms for working with sound and faster solutions than those indicated here and, of course, have the right to exist, but taking on a large amount of resources and time, I see no reason to solve such problems in this way. In no way do I impose my point of view.
As for the second point about bass, I didn't miss it. It's just that in this case, in the right parts of the bass, I independently apply the transient and already move it to the right space as I need it. And "stretching" this kind of sound doesn't distort the sound. But just in such cases, the method indicated in this video can produce an unwanted sound effect - with or without crossfade.
Don't think that I rely only on software and its algorithms and that I think it will do everything on its own. Not at all. It is only to help and nothing more. To achieve a good sound, we only use the capabilities of the software, but we shape everything ourselves if we want to achieve a perfect and natural sound;)
And I work in different directions, not only and not so much in electronic music, where transients are mainly located exactly in beats. It is in this direction that I do not work very much. I have to work a lot both in rock and jazz. I often record multitracks of groups, and I personally record my parts from both bass and guitars, which I also correct later. And not the first year;) It seems to me that you made the wrong conclusion about what I am;) If I am talking about quantize, it does not mean that I have nothing to do with live music;)
отлично, правда первая нота, все таки, не в бит)))
Does it work on vocals lol I get horrible lil Wayne like artists
it works on any audio wave with recognizable transients... although I also prefer to use audio bend markers...
Thanks for that! However, it’s strange watching you fix bass music mistakes while making information video mistakes. For me it’s difficult because I’m paying close attention. So to first learn a mistake, then backtrack to the right way or word in a lesson is confusing. Maybe edit your videos to always relay correct info the first time. Cheers!
I just press 'q'