How are you getting along with Studio One Seven? Pros - Cons, development.....

[Vocalpoint]

Way to stay on them Vocalpoint. Let's give it about a week (to tweak). Let's say, next Monday. Then we can post a compiled list of these ver. 7 issues much like the old version X is now released thread. That should make it visible. OR, if there is a lot of back and forth on each subject, perhaps Lukas can create such a suggestion room/place for each of those subject threads as he sees fit. It shouldnt be too many issues though, yet they're obviously all important. I'm guessing the subjects are something like:
[Color or GUI]
•color control panel differences,
•color gradient not always discernable,
•over bright highlight on selected event

[Duplication of audio events]
•re writing copied audio events?
•longer times when copying/duplicating?

[Other] Etc, etc.

I know Presonus doesn't look here, but we can have someone hang glide it into the Presonus Studio One compound, or where it will receive attention.

Good to see you, btw!

I know the MIDI crowd is a tad livid over the (now non-ability) to "range" select higher velocity tips and be able to have only those be selected (and adjusted).

v7 dumped now makes you adjust every note velocity manually. Nice move guys.

I am also staggered by the lack of any tools (or abilities) to manipulate MIDI data within a Launcher cell. No Consolidate. No Overdub. Or many of the other things I see in "other" launchers. Maybe I am doing this wrong or maybe this is part of a feature run and not a "fix" per se.

VP

 

[Crossinger]

It‘s already past 10am in Baton Rouge. I don’t think we can expect an update today.

 

[Vocalpoint]

It‘s already past 10am in Baton Rouge. I don’t think we can expect an update today.

Just heard from one of my internal contacts - a release candidate is in testing but yeah - no release today.

Will need to be patient I guess

VP

 

[lokeyfly]

It‘s already past 10am in Baton Rouge. I don’t think we can expect an update today.

True, but you can get crawdaddys, ochre, and Cajun voodoo death chicken there for lunch!

 

[Lukas]

I'm getting the feeling there will be no maintenance updates, just the updates for new features (which would obviously include bug fixes).

There will of course be maintenance updates. The next one is coming very soon.

Just heard from one of my internal contacts - a release candidate is in testing but yeah - no release today.

If that's true and your internal contact has access to a beta version, they're breaking their NDA (non-disclosure agreement) by sharing this information.

 

[Crossinger]

There will of course be maintenance updates. The next one is coming very soon.


If that's true and your internal contact has access to a beta version, they're breaking their NDA (non-disclosure agreement) by sharing this information.

But if the next one is coming „very soon“ then they should have a RC. And then this information is not undisclosing anything or revealing any more information than you do.

 

[Lukas]

I'm just pointing out that a tester is not allowed to talk about unreleased versions.

 

[Crossinger]

I'm just pointing out that a tester is not allowed to talk about unreleased versions.

Maybe Vocalpoint is best buddy with Arnd Kaiser? Okay, I'll stop poking fun at it now.

 

[lokeyfly]

Thanks Lukas on the heads up. I know you're privy to only outlining such conditions, and that is respected here as well. I hope numerous fixes are in the works. Respect.

@ Vocalpoint, ah yes I forgot about the the inability to "range" select higher velocity tips of MIDI notes and be able to have only those be selected (and adjusted). Let's hope all issues roll in.

I'm going to check my concerns tonight to not wait on that at all. Just to be clear on copying audio and having a robust duplicate as that isn't happening in this one song I'm working under. I'll check another song to make sure it's not some unique anomoly towards the one song. Cheers.
Updated]: No issue found and occurs on only one song.

 

[Vocalpoint]

If that's true and your internal contact has access to a beta version, they're breaking their NDA (non-disclosure agreement) by sharing this information.

I have no idea what my contact has access to - if he was a tester or is/was under an NDA - he would know better than to say anything.

Saying there is a "version" (beta or RC or whatever) in testing - is about as non-specific as it gets.

I mean let's be reasonable - things are in "testing" all the time - your stuff included.

VP

 

[lokeyfly]

.....I'm going to check my concerns tonight to not wait on that at all. Just to be clear on copying audio and having a robust duplicate as that isn't happening in this one song I'm working under. I'll check another song to make sure it's not some unique anomoly towards the one song. Cheers.

I'm happy to report that I saw no such issue on other songs. Duplicating, copying/pasting arrangement parts with all events contained within (both audio, MIDI, and automation) were instant. This is what I was hoping and expecting to see. The extreme delay I was recently experiencing is tied to only one song. While I don't know why that is, i suspect it's some property, or something that I'll soon figure out. I'll edit my point earlier as noted as to not cause any confusion.

Carry on, cheery-O, pip pip and all that rubbish.

 

[Dave71]

I can see that being an issue. It would be nice if a marker could be placed on an event with chords to define one place to mark. Then Tempo Detect could position to such a marker along with its other natural tempo marking.

That said, you can control transient resolution, bit I see your point. Tempo Detect chases any transients it sees. Hopefully, in the future, there is a way to scale transient detection.

Your other alternative would be to detect tempo based on some other instrument, such as perhaps drums or bass. Just a thought.

Absolutely! And that is what I would use if I had it. IN my case it was a mandoline and a harp, nothing else, and they were definitely not played consistantly. In the end I just had to put in the hours and manually do all this. I generally do't really need tempo detection because I have become really good at it myself over the years. But in these cases the goal was to detect the tempo from these files, then conform them to a steady tempo. And in this use case the markers you mention would have to be placed manually, which then sort of defeats the idea of having things done automatically. Scaling transient detection, that may well be the ticket indeed. Who knows what the future will bring!

 

[Lukas]

The maintenance update (7.0.1) is now online.

https://studiooneforum.com/threads/studio-one-7-0-1-is-online.72/

 

[marrybanilow]

I reverted back to S6 after a couple of days using 7 due to constantl freezing/crashing which in turn caused my macbook to shut down, and the UI emmitting random colours and bugging out. I see in the latest release notes theres a fix for macOS '[macOS] Potential crash with certain plug-ins' which i hope resolves this!

 

[lowerfreq]

Absolutely! And that is what I would use if I had it. IN my case it was a mandoline and a harp, nothing else, and they were definitely not played consistantly. In the end I just had to put in the hours and manually do all this. I generally do't really need tempo detection because I have become really good at it myself over the years. But in these cases the goal was to detect the tempo from these files, then conform them to a steady tempo. And in this use case the markers you mention would have to be placed manually, which then sort of defeats the idea of having things done automatically. Scaling transient detection, that may well be the ticket indeed. Who knows what the future will bring!

Looking forward to others evaluation of the new tempo function... tbh, it's the only reason I would upgrade to 7 at this point as the other new features, while sounding great, probably wouldn't improve what I do in S1-6. I still record to a click, but there are many times I would like to tighten things up when adding vsti drums, as I tend to rush things a bit as a song progresses, so this might be the tool I need. I'm unfortunately to lazy to manually do the work, especially with acoustic guitar, which invariably starts out all my songs

 

[Dave71]

Looking forward to others evaluation of the new tempo function... tbh, it's the only reason I would upgrade to 7 at this point as the other new features, while sounding great, probably wouldn't improve what I do in S1-6. I still record to a click, but there are many times I would like to tighten things up when adding vsti drums, as I tend to rush things a bit as a song progresses, so this might be the tool I need. I'm unfortunately to lazy to manually do the work, especially with acoustic guitar, which invariably starts out all my songs

Well, as I said in my first comment in this thread, I too mainly record the old fashioned way, but having a percussion or drum loop instead of a click does definitely make a difference in how you perform, so I would really recommend trying that. And if that is working for you, then the loop tools are a plus as well, including the launcher

 

[lowerfreq]

Well, as I said in my first comment in this thread, I too mainly record the old fashioned way, but having a percussion or drum loop instead of a click does definitely make a difference in how you perform, so I would really recommend trying that. And if that is working for you, then the loop tools are a plus as well, including the launcher

You are right... I neglected to say that recording with the drum loops certainly helps me with vibe and feel when recording. Need to check out some vids on Launcher too.