madFloyd
Member
Personally I found that the 'racetrack' makes it a lot easier to distinguish between adjacent events.
Options are always good though! I think the event editing is just a little more fussy now due to the looping feature.
-
Hi and welcome to the Studio One User Forum!
Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by PreSonus. Learn more in the Welcome thread!
Studio One 7.0.1 / 7.0.2 - Discussion Thread
- Thread starter Ari
- Start date
Personally I found that the 'racetrack' makes it a lot easier to distinguish between adjacent events.
Options are always good though! I think the event editing is just a little more fussy now due to the looping feature.
John Pihel
New member
It is impossible to work 10 hours in the studio with the color scheme of the seventh version. I hoped to fix it in 7.02, but it did not happen. Therefore, I converted all projects to the sixth version and work in it. Phew...
P.S. By this I mean the color contrast between a selected and unselected audio/MIDI event on a track.
P.S. By this I mean the color contrast between a selected and unselected audio/MIDI event on a track.
Last edited:
Well, then, it's now my time to raise the voice ...
I feel intense buyer's remorse for having upgraded to V7 (Pro+ for the first time)
Lots of damaged areas not being fixed, while one is forced to watch in disbelief they are still adding new (rudimentary) stuff each and every time instead of resolving issues - creating additional overhead plus even more hassle each and every time.
And on top of this, even I wouldn't benefit using V7 at this time (compared to V6), I'm ufortunately one of those who just can't get along with the non-adjustable new "Grid"-Llook", so I am stuck with V6 anyway.
Money gone, as well as my trust for things turning to the better in the future.
Trying to get away vom S1 now ... better to prevent than to be sorry later.
I am really fed up with it. Sorry for my "insensitive" verbal approach ; -)
I love (and need) the chord Track and there are not so many alternatives on the market.
And I love the scratch pad - as far as I know without competition. Both make my life as a musician (not engineer) much, much easier.
Will be hard to find an alternative if one exists ...
I feel intense buyer's remorse for having upgraded to V7 (Pro+ for the first time)
Lots of damaged areas not being fixed, while one is forced to watch in disbelief they are still adding new (rudimentary) stuff each and every time instead of resolving issues - creating additional overhead plus even more hassle each and every time.
And on top of this, even I wouldn't benefit using V7 at this time (compared to V6), I'm ufortunately one of those who just can't get along with the non-adjustable new "Grid"-Llook", so I am stuck with V6 anyway.
Money gone, as well as my trust for things turning to the better in the future.
Trying to get away vom S1 now ... better to prevent than to be sorry later.
I am really fed up with it. Sorry for my "insensitive" verbal approach ; -)
I love (and need) the chord Track and there are not so many alternatives on the market.
And I love the scratch pad - as far as I know without competition. Both make my life as a musician (not engineer) much, much easier.
Will be hard to find an alternative if one exists ...
marrybanilow
New member
I get your frustration. It would be nice if any new UI appearance options were optional however that seems to rarely be the case in any software.
I've tried alot of DAWs, most recently Cubase 14 because it is the closest to Studio One for me in terms of features and does everything i do in Studio One but going one better with their Hit Detection option being super accurate compared to the Audio Bends on S1 (which to this day i don't understand why it hasn't been fixed/or if intended, revised).
The reason i come back and stay with Studio One though is the workflow. In my opinion no other DAW comes close which is why i cant ever see myself moving away full time
madFloyd
Member
Can you summarize the issue with Audio Bends in S1?
marrybanilow
New member
It places the bend marker within the transient rather than at the start of it. I think this is delibrate on Studio Ones part as i have seen this discussed so many times over the years in forums but it does not make sense (which is also the general consensus from what i've seen/spoke to others). My use case is, i get live kick, snare and toms and i want to use audio bends to turn this into midi hits. Because of the way Studio One does this, the midi note is off from the actual transient of the source therefore it is not an accurate representaion so it's unusable for this situation - unless you go through all the bends and manually place them at the start of the transient, which is a total workflow killer. I have to resort going into Cubase and use their Hit Detection feature instead as this is extremely accurate, create a MIDI there then import into Studio One.
If they sorted this, i wouldn't even glance at another DAW ever again
Last edited:
THANK YOU. I have felt like I’m taking crazy pills when I edit in S1 vs Pro Tools. I run an ancient computer with PT 10 for editing only simply because of the inane bend marker rules. I’m so glad I’m not the only one.
Crossinger
Member
Yes, unfortunately this design decision renders the feature useless for certain use cases. 
It's a pity that one has to reach out for external workarounds in order to achieve the desired results.
It's a pity that one has to reach out for external workarounds in order to achieve the desired results.marrybanilow
New member
In terms of my workflow, it is by far the worst thing about Studio One but also one of the most important things. I have (maybe false) optimism at some point (even though it has been years already) that this will get sorted at some point. I hate having to use different DAWs for different things
I totally agree. When the bendmarkers went into Studio One they had one thing in mind which is a nice feature while using them for stretching. And this is this transient protection area. This ensures, that the transient stays intact while using the bend tool. Nice but completely useless if you want to create precise note informations out of the transient detection. If you want to fully replace a bad sounding drum track with a sample you might get along with this if it's not a high end production, but if you want to augment a drum kit with samples than you are cursed because you will get flams and phasing issues all over the place.
Sadly even with a lot of feature requests in this direction it got never touched again. A checkbox to use the transient protection area or not would be perfect so you can decide what you want. I really gave up with this feature, I reported this so many times.
This is the craziest part. The phasing and flam issues are absolutely awful and the wonky data that comes out of a roll / fill is so unusable and really makes you question how unserious about drum editing Presonus is. I check bend marker placement every time they come out with a new version and am disappointed every time.
Crossinger
Member
I have a dim memory there was some kind of clumsy macro solution as workaround? It was 32x jump to next bend marker and then some adjustment. I found the download link at KvR, but the result was not convincing.
Hm yeah, this might work for some percentage of the hits, but the note itself doesn't have the same offset because it's some kind of energy funtion to determin how long the transient is and this can vary from hit to hit.
John Pihel
New member
I received a response from Presonus technical support about the problem I wrote about in the topic above. They replied that they are aware of the problem and are working to solve it. All that remains is to wait for the next updates.
yeah dude whats up
New member
Vocalpoint
Active member
Same here. While I have managed to compromise now to a point of workability - I still think it was a poke in the eye with a sharp stick for Presonus to completely change the color space - the way the LUM and SAT and CONT controls work and so on.
Again - I am all in for moving forward - but make this Fisher Price vibe optional.
Some of us are really set on the look and feel we have had for years in S1.
VP
I also don't understand the rational behind changing the wave form view to 'mono' when track height is reduced. The whole point of the track view is to give you visual information regarding the tracks in your session, why the heck are they removing useful visual feedback from the track view??
This is quite jarring because I regularly have large sessions (many times over 100 tracks) where I used to be able to determine what tracks are what, just by looking at the wave forms, and this strange "collapses into mono" feature (or bug?) is a step backward. There seems to be no workflow enhancement or other purpose to this change, and if they are trying to mimic Logics wave form view, they shouldn't, because logics wave form view is trash.