NEW Studio One v3 updates incoming.

[nIGhT-SoN]

OK so above is a perfect example of how marketing is already tricking people, this is exactly why it is not irrelevant, for some reason, because only one instance is seen of a front end of a plugin, this poster thinks that it will save CPU because it is just on a bus, now nobody has bothered to explain here that actually that process is on every single channel feeding the bus, not just the bus, in fact a few tests have already been done and it uses more cpu than VCC, there is no way that mix fx can save or use extra cpu cycles unless programmed rather badly, compared to the same algo in a VST, the fact that it uses more than VCC on the same channel count does not necassarily mean mix fx is worse than VST, it could mean the algo used is a bit heavier, like Lawrence has said, they are doing nothing new here, they are just doing it in a new way, the math is still the same math.

I was about to reply to you but I won't do it cause I know we'll get on a rolling stone and we'll never end so I will do it now.

Console Shaper is pretty great, wouldn't call it "new" since it's been done before in pro tools but it is pretty revolutionary in terms of workflow specifically in studio one. Can't wait to see what developers like slate will do with this technology.

Be careful what you say, people might think you are brainwashed by PreSonus marketing.

[Funkybot's Evil Twin]

still dunno why they created macros if it can't be automated ???



back to Cubase

The macros will write automation to any parameters they control. So if you have one macro controlling 3 different knobs, automating that macro will write automation for those 3 parameters. But I agree, it would be much easier and make a lot more sense if they just wrote automation for the single macro knob (one automation lane to edit versus three).

[SeeingInMidi]

Console Shaper is pretty great, wouldn't call it "new" since it's been done before in pro tools but it is pretty revolutionary in terms of workflow specifically in studio one. Can't wait to see what developers like slate will do with this technology.

Be careful what you say, people might think you are brainwashed by PreSonus marketing.

[Flandersh]

I do not know what the Mix Engine FX is all about, and so I may be off the road. But as I understand it, the Mix Engine FX may be of such a character that a description of it as a plugin format may be somehow misleading, as it may not be in the same league as in example VST, RE and so. Descriptions like "modular mixer", "mixer customization" etc. could well have done it. Reason have its SSL console, Sonar its Console Emulator, Cubase its MixConsole. Studio One join the game now with the addition that their console is open to third-party developers. As different console emulations work for different mixes, to have the option to choose from different high quality developers in this is at least for me a game changer.

The difference between what Studio One is doing with Mix Engine FX and Sonar's Pro-Channel effect is that the Mix Engine FX are at the mix engine level. This allows for channel 1 to bleed into channel 2, and bleed into channel 3, etc. Sonar's Pro Channel can't operate this way since it's basically sitting on top of the mix engine, versus inside of it. Hope that makes sense.

I may have been a bit unclear. My ignorance has to do with the actual possibilities of it, an ignorance coming from the fact that none other DAWs afaik utilize such an approach.

[xamido]

Wow that bungle is still going on with his crusade for pages. Calling others as fan bumping the thread while he's the only one keeping the thread more active than it's supposed to.

[nIGhT-SoN]

I guess he doesn't like PreSonus or their way of doing business. It's his opinion and I don't feel like spending time trying to change how this product is seen by others. I would rather spend my time reading something useful or making actual music.

[SeeingInMidi]

I guess he doesn't like PreSonus or their way of doing business. It's his opinion and I don't feel like spending time trying to change how this product is seen by others. I would rather spend my time reading something useful or making actual music.

Stop wasting your time working on music, use your time wisely and spend it on complaining about how absurd an update is.

[Igro]

Didn't see the promotion of 3.2, but the update was really nice.

[progtronic]

Just punished my CPU with Console Shaper for a while.. yeah.. I'll never use it. Warming up tracks is the polar opposite of what I want to do.. in the styles I'm working in, anyway.

VCA's and Smart Tool are nice though.

[Notecrusher]

Just punished my CPU with Console Shaper for a while.. yeah.. I'll never use it. Warming up tracks is the polar opposite of what I want to do.. in the styles I'm working in, anyway.

All that can be done w/ it is "warming up tracks"? Something tells there are much wider sonic possibilities...

[Shalotta]

Not sure if a dedicated v3.2 bug thread is more appropriate, I`ll place it here for now.

Can this be confirmed or solved (and can some post the solution to this user):

I can confirm this issue.

At first I thought it was something to do with folder/instrument prioritization.. but the more I fiddled with it, the more random it seemed.

Ticking an extra set of outs in Superior Drummer, resulted in the entire instrument being yanked out of the folder and thrown to the top of the list (happened with two separate instances of SD).

So.. I have no idea if this is a bug, or some sort of new "feature".

I'd definitely file a formal bug report just in case they're unaware.

Thanks for your replies,

I have this issue I believe since v2 as soon as audio and midi tracks are present in a song.
Midi tracks are jumping randomly to the top or in between other tracks while working on them.

New to me is the documented issue in v3.2
of not being able to move those tracks back into a desired order or position.

Question: if you recreate the project from scratch in 3.2 (which I understand if you don't want to do), does it still happen? I wonder if it's limited to old projects opened in 3.2 or happens in new 3.2 projects. Either way though, it's a bug.

I have to leave this question in the blur
since I am tired of being an involuntary beta tester and decided to collect reported bugs before updating S1.
Hopefully you`ll find a kind soul with an answer.

[SLiC]

Here is a list of all the changes in this free update.

New features and improvements:

• Mix Engine FX
• New plug-in API and interface for Mix Engine FX (Mix FX)

• New FX Plug-in Console Shaper (Mix Engine FX)
• VCA Faders
• quickly create VCA for selected channels
• unlimited nesting / overlapping
• VCA / folder linkage
• Merge option for VCA fader automation

• Arrow Tool enhancements
• Option to auto-select Range Tool in upper event area

• Range Tool improvements
• single click sets the cursor
• in stop mode, locate happens immediately (play cursor)
• in Play mode, it sets the edit cursor; the locate is deferred until transport
stops
• double click on event splits the event
• double click on a range selection splits range
• more Arrow Tool improvements: event size handles (left / right edges) are
now easier to access with the mouse (fade handles interfere less)

• Crossfade editing improvements
• in a crossfade, both sides can be sized easier
• moving a crossfade (X cursor) is easier now when zoomed out

• Extended layer/take editing (comping)
• navigation keys (when a layer is selected):
• Arrow up/down: navigate between layers (selects previous/next layer)
PreSonus Studio One 3 – Version History
2
• Arrow left/right: moves a range selection on a layer to the previous/next
area, determined by the event ranges on the main track.
• Shift+Arrow left/right: extend a range selection
• when another layer of a track is selected (Arrow up/down or click on layer
track controls), an existing range selection is moved to the previous/next
layer.
• Layer Solo:
• when a layer is selected, the Solo command ("S") now solos the layer (not
the track).
• the existing option "Solo follows Selection" now also applies when selecting
another layer.
• Layer Colors:
• Layers can now have (optional) colors, that can be chosen in the layer track
controls
• auto coloring also applies to new layers ("Add/Duplicate Layer")
• similar to event colors, the layer color can be undefined. The color of an
event on a layer is determined in this order:
• 1. Event color (as before)
• 2. Layer color
• 3. Track color (as before)
• Range Tool:
• previously, the "Quick Swipe" comping function was always used on layers,
regardless of the selected tool (except the listen tool)
• now the Range tool can be used to select ranges on layers
• a range can also be selected with a single click on a layer (selects the event
range from the main track). This also works with the Arrow tool.
• switching content on the main track:
• when an event on the track contains material copied from a layer, the
context menu of that event will have a sub menu "Select Layer Content",
listing all layers that also contain material in the event range.
• selecting a layer from the menu replaces the event on the track
• switching can also be done quickly with Alt+Mousewheel (next/previous
layer)

• Layer / Event naming:
• in the track controls of a layer, the track name is shown below the layer
• the generic default layer names ("Layer 1", etc.) are now assigned
permanently, so they don't change anymore when reordering layers (which
caused a lot of confusion)
• when promoting layer material to the track, events now get the layer name; if
the layer has no real name, the event name is "trackName layerNumber"
PreSonus Studio One 3 – Version History
3
• when recording, the name of the active layer is used in the event name:
"trackName layerName" or "trackName layerNumber" plus a running index

• Various:
• new "Expand Layers" button on track controls (shown when track has more
than 1 layer)
• when a range is selected on a layer, a button for the "Copy Ranges to
Track" Command" appears on the layer's track controls
• duplicating a layer now expands the track to show the new layer

• Extended tab-to-transient
• Tab: move cursor to next transient (as before; discards existing range
selection).
• Shift+Tab: create / enlarge a range selection from cursor to next transient
• Cmd+BackSpace: move cursor to previous transient
• Shift+Cmd+BackSpace: shorten range selection (end) to previous transient
• all these commands search for transients on the selected track(s).
• when used during playback, a separate "edit cursor" allows navigating
through transients, independently of the play cursor position.

• New transport options
• context menu on transport buttons
• consolidated "Options" in "Transport" menu

• New Play Start Marker
• decouples playback position from edit selection (called "Dynamic Transport
Mode" in ProTools)
• can be enabled/disabled via key command, context menu in the time ruler

• New "Loops follows selection" option
• New Quick Zoom options
• Select range with mouse + Alt key zooms range; single Alt+click to return to
previous view
• with the Arrow Tool selected:
• alt+click an event to select it AND zoom selection
• alt+click again anywhere to zoom back to previous view
• with the Range Tool selected:
• alt+drag to select range AND zoom selection
• alt+click again anywhere to zoom back to previous view

• New mixer options
• VCA channel placement and routing display
• preserve order of channels with folder track
PreSonus Studio One 3 – Version History
4

• Automation improvements
• quick range editing (automatic "bracket" tool)
• automation curve can now be "trimmed" via the upper 1/4 area of a selected
range (|--| Cursor appears)
• new command "Automation" - "Transform Range" (default key: Alt+T)
creates a transform selection from the selected range
• range selection creates Transform edit selection for automation (incl. simple
up/down dragging PLUS all other Transform options)
• matches track/channel default colors; selection follows; default names are in
sync

• Various workflow improvements
• improved "select to end / select from start" shortcut (track focus)
• drag instrument part to audio track renders audio and creates event
• double-click output meter in transport bar opens Main channel inserts
window (Channel Editor)
• move Insert FX (alt+drag) between channels (drag without modifiers still
creates copies)
• "Split" command (alt+X) now works for split range AND split at cursor

• Improved appearance controls and view/visibility
• main contrast slider is changing the text intensity (mainly),
• Arrangement contrast is changing the grid intensity now.
• Luminance and saturation are still the same, but change some colors in a
non-linear way now. (i.e. toolbar color saturation)
• track numbers added to Inspector Header

• Various Multitouch Improvements
• improved vertical zooming
• long tap to select is now shorter (had too much lag)
• smoother scrolling of arrangement and mixer
• OSX: mouse events are now sent properly to system
• control Console height and Browser width with touch
• touch support for color picker added

• Updated ProTools keyboard mapping scheme
• DSP Fat Channel + PreAmp Control for PreSonus RM and AI mixers
• Melodyne 4 support
• Melodyne 4 Essential inclusion (contains new “Universal” algorithm for highquality
time-stretching and pitch-shifting of polyphonic audio material)
• improved tempo map extraction
PreSonus Studio One 3 – Version History
5

The following issues have been fixed:
• [OSX] Presence XT has long loading times
• [OSX] Crash when removing MIDI device while MIDI port selector is open
• Cue send lock is not always working
• Playback issue with enabled audio cache
• Delete key not working in channel editor
• Delay compensation not working on output channels
• User login not working when password includes a mutated vowel
• Studio One is unresponsive when Input Filter plugin is used
• Sustain pedal automation could be ignored when rendering audio
• [OSX] Can not change Studio 192 sample rate when IO format changes (may still occur with 10.8.5)

[xbitz]

The macros will write automation to any parameters they control. So if you have one macro controlling 3 different knobs, automating that macro will write automation for those 3 parameters. But I agree, it would be much easier and make a lot more sense if they just wrote automation for the single macro knob (one automation lane to edit versus three).

please vote it http://answers.presonus.com/3586/extend ... on-control thx S1 is almost there but this one...

- https://forums.presonus.com/viewtopic.php?f=111&t=9871

[nIGhT-SoN]

This is a really good idea. What I would also like to see is being able add automation, on an automation track, into a clip this way I can move it anywhere I want even on other automation tracks. I know there is kind of a solution by drawing the automation on the midi clip, but that it sticked to the notes. What if I want the same automation on threshold knob of a compressor, I would have to copy the automation points, but I won't be sure I will place them in the same spot. With clips for automation would be a lot easier.

Something like this:


This way I can make a copy of that automation clip on the track under it really easy. As it is right now I would have to create a point where the song starts, select all points, move on the next track, paste there and clean up extra points in there.

[LawrenceF]

The only issue with proprietary plugins is you can only use them in one DAW. With Slate porting over his emu stuff how much is the cost difference between the 2 different versions ? We shall see.

That's the open question, yes. The best case would probably be if you bought VCC from Slate or whatever else similar from Acoustica or Softtube, that the MixFX format would just be in there with AU, VST, AAX, as just another format to install or not when you run the installer... assuming that's how they sell those now.

I guess we'll have to wait and see how that shakes out when they show up for sale.

Otoh, if a person only uses Studio One and doesn't want to use another daw and if it's packaged and sold just for Studio One, it might sell for substantially less than it does otherwise. No idea. And (speculating obviously) it would probably be to a company like Slate's benefit for someone owning one (if it was sold just for Studio One) to get an upgrade discount to buy into the VST/AU/AAX versions.

But yeah, we'll have to wait until they land to see how that works out.