Studio one bugs will eventually be ironed out , bitwigs sluggish gui when doing heavy projects hasn't been adressed yet since it's release .Trancit wrote: Sun Jun 23, 2019 7:20 amThis ...plus having to insert a plugin just to see the value read-out is a bit cumbersome...andypryce wrote: Sun Jun 23, 2019 6:31 amBut it still shows pre fadergentleclockdivider wrote: Sat Jun 22, 2019 10:54 pm Insert a level meter set to true peak right click and select expand
![]()
I stay with my statement... not to have realtime meter readouts on the individual channels for a quite new DAW is absoluely silly ...
Same goes for folder clips...
That they turn into blank clips not showing any content at all if not all content can be squeezed into this poor graphics and therefor not having any indicator that this a folderclip is not really helpful in terms of general overview...
This all plus a couple of very nervig bugs especially after the 4.5 update made me switch to Bitwig...
Studio One post fader level per channel
-
gentleclockdivider gentleclockdivider https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=203660
- Banned
- 6787 posts since 22 Mar, 2009 from gent
Eyeball exchanging
Soul calibrating ..frequencies
Soul calibrating ..frequencies
-
- KVRAF
- 5071 posts since 27 Jul, 2004
... at the very end this tells nothing as Bitwig could eventually update to a GPU supported system too as some bugs in S1 were present a long time as well...gentleclockdivider wrote: Wed Jul 03, 2019 11:49 am Studio one bugs will eventually be ironed out , bitwigs sluggish gui when doing heavy projects hasn't been adressed yet since it's release .
On top of that, there are many little (while some are bigger) things I cannot really stand in S1 like:
- the already mentioned lack of realtime numeric peak level readouts on single channels...
This alone is a no-go for me in a quite new DAW... and in opposite to the OP, no... hoovering over the peakmeter, trying to find the right point and have a more or less precise guess is definetely no option or workaround
- the already mentioned silly graphics of the folder clips... from all silly options available they chose the worst... How can one think, letting the folder clip turn blank could be an acceptable option??
- sometimes absolutely silly auto numbering of multiple FX instances even if they are on different tracks... if you want to get rid of the number, it doesn´t let you saying there would be an instance with the same name already...
- implementing a slicing option for drum loops without having any chance to have the original midi part created (apart from the browser with rex files)... dude, even Reaper can do that...
- when you got an deactivated hidden track in between 2 others and you lasso select the events of the visible 2 and duplicate them, the hidden and deactivated ones got automatically duplicated too... well done...
In some situations the folder clips increased to regions where no visible clips were present... till you suddenly figure out, the hidden ones which stupdily got duplicated too and had a longer length were increasing the folder clip...
- new for me in 4.5 (I don´t remember everyhting I found... this was just too many): If you got a folder track at last track in an arragement and you want to place another track underneath... it doesn´t let you... no way via draggin the track down...
- ...just to name a few as I don´t remember much stuff anymore... but from my feelings this can be continued till the end of all times...
Every DAW got it shortcomings and bugs but the ones in Studio One were (for me) killer ones... my first reaction on every single one was equal..."Seriously... are you kidding me...?"
Everybody is different, works different, but I never tried a DAW before which gave me such bad feelings in terms of shortcomings and bugs than S1 ...sadly, as I like it in general and it´s featureset is quite impressive...
-
- KVRer
- Topic Starter
- 23 posts since 11 Jan, 2019
@gentleclockdivider and @Trancit, I appreciate both your input, but let's not escalate this into a Bitwig vs Studio One discussion. I'm sure you would keep it civil, but it was not the intention of my post.
Thanks.
Thanks.
-
- KVRAF
- 5071 posts since 27 Jul, 2004
Why Bitwig vs S1???hevok wrote: Thu Jul 04, 2019 6:39 pm ...but let's not escalate this into a Bitwig vs Studio One discussion. ...
Because I mentioned using Bitwig now???
You could say "anti S1 thread" but I didn´t do a comparison to Bitwig ...
And I am sorry but posting problems with S1 should be allowed in a " I have a problem in S1" thread and hasn´t anything to do with any escalation...
-
- KVRer
- 1 posts since 9 Jan, 2020
Yes I am having this issue too...I insert Level Meter and it just shows pre fader no matter what level I move the fader to. Makes it difficult to set automate volume levels on a track...I have to mainly use my ear.