-
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 Pro Updates?
- Thread starter easyrider
- Start date
Vocalpoint
Active member
My thoughts exactly. v7.11 was not exactly an earth-shattering update with just 8 documented fixes.
Also - given the big fanfare around the Launcher in v7 - I continue to be (quietly) disappointed with its "basic-ness".
While I totally understood the need to "get it out there" - this tech is basically the same dish served in Oct 2024 with zero enhancement.
As always - I am sure something is baking in the oven - it's just a matter of serving it up.
VP
Also - given the big fanfare around the Launcher in v7 - I continue to be (quietly) disappointed with its "basic-ness".
While I totally understood the need to "get it out there" - this tech is basically the same dish served in Oct 2024 with zero enhancement.
As always - I am sure something is baking in the oven - it's just a matter of serving it up.
VP
Last edited:
sintil8
Active member
I admit I'm intrigued to see what comes out of the kitchen for the Launcher.
It will be interesting if it includes another Tab next to the Edit/Mix/Browse, It would make sense and align well with the project transfer stuff. But then I'm just thinking aloud/allowed ?
There are also options for hardware and and Midi2 with Property Exchange. Would be great for hardware controls to be laid out nicely?
Anyway regards as always.
It will be interesting if it includes another Tab next to the Edit/Mix/Browse, It would make sense and align well with the project transfer stuff. But then I'm just thinking aloud/allowed ?
There are also options for hardware and and Midi2 with Property Exchange. Would be great for hardware controls to be laid out nicely?
Anyway regards as always.
Per the video release announcement of Studio One Pro 7, each year PreSonus will release 3 to 4 updates.
Here's a link to the video that provides all the details for this...
The Future of Studio One Pro
Resonant Serpent
New member
I was just thinking about this today. On the 9th of May it will be seven months since v7 was released.
Same. I was actually happy about it. It feels like the longest it’s been in a while with a really stable release and I wondered if I missed an update.
OutrageProductions
Member
I'm calmly waiting for dim solo...
lokeyfly
Active member
Out loud, (aloud is also acceptable, and effectively the British form of out loud). Obviously, your English is very good, sintil8! Someday, I hope you can help me out with my Deutch as a 2nd language, which I'm working on.
Yeah, I'm looking forward to some improved development from the launcher. It's just another avenue for development, and a welcome one.
I don't really care when that happens, so all good on the development front so far. It's just like pouring a pint of Guiness from a tap, or a meal from a top chef. All good things take time.
Vocalpoint
Active member
Wish I felt the same way. I now keep wishing that Gregor would have been more specific in that video about "3 or 4 " major updates.
Given it will be May in a few days and we have had exactly one (very minor) update in 2025 (v7.1) - it is clear that "4" major updates are not going to happen and now we are looking at "3" - which - if stated right off the top back in the launch video - would have more realistic expectations.
And to be clear - I totally understand that my idea of a "major" update - may vary widely with others - I am 100% OK with that.
VP
JX-84
New member
The cynic in me expects the biggest update will come out October 10th so they can get more people subscribed re-licenced for another year.
Until then probably more reskins of Deep Flight One and further updates to the Splice integration.
Of course, I'd be delighted to be proven wrong and Presonus actually deliver some of the bigger feature requests.
Until then probably more reskins of Deep Flight One and further updates to the Splice integration.
Of course, I'd be delighted to be proven wrong and Presonus actually deliver some of the bigger feature requests.
Vocalpoint
Active member
You do bring up a VERY great point.
I keep thinking about this from a "2025" viewpoint - as in Jan 1. But in reality - I should be thinking about this from an Oct 9, 2024 - Oct 10, 2025 viewpoint.
Considering there was not a single major update between Oct 9 and Jan 29 (and sorry but I still do not consider v7.1 to be major in any way)
That alone effectively trimmed almost 4 months from the overall schedule right there.
In effect - as of today - with just 167 days to go before my "update" plan expires - I think I might be lucky to see just two more "major" updates before I am asked to pull out the credit card once again.
VP
Last edited:
Vocalpoint
Active member
I have to agree there. The lack of comms and the lack of an easy-to-understand purchase guide has always been a concern to me.
I do not think I have attempted to assist more users on anything in the Studio One world than trying to help people understand the Perpetual vs Sub Model.
That said - I continue to watch that Keynote Video from time to time - and I guess I misunderstood the spirit of it and my takeaway of it last October.
At that time - it spoke to me like "We are re-committing ourselves to getting everyone more good stuff - faster". And I read this to be more features. More bug fixes. More comms. More "connection". And since then- it has been less comms. Less bug fixes and let's call a spade and space - less features and/or major updates.
If anything - especially since the official company forums were closed - PreSonus has now become more secretive, more close to the vest (too close) and is displaying even more radio silence on updates.
Now maybe something good is coming. Or maybe a v7.2 arrives with 9 bugfixes and another new rompler than no one really asked for.
It is an interesting gap here - with so much time elapsed since Oct 9 and (when you think about the spirit of that video) - v7 (to me anyway) is essentially is the same thing we saw back in Fall 2024.
I cannot decide if this silence is a good thing or a bad thing.
VP
Last edited:
sintil8
Active member
VP. I get a case of this.
I also get a mailbox full of discounts on Vst's and lots of offers to comment or rate products, even if you try a demo, the market is saturated.
However, it makes an attractive package for folk just starting out having in house instruments available.
The number of discounts that are constantly on offer makes adding extra Vst's shallow water.
I could ramble on but I am sure lots of folk know this S*** already!
The silence... CBase have been canvassing for Beta Testers, the world has turned upside down, what more can ordinary folk say.
Regards as always folks.
apessino
New member
I try to stay positive as much as I can, but man the last few months with Studio One have been testing my resilience.
Forget about new features, I would happily settle for an update that fixes the longstanding issues with Apple Silicon Mac GPUs. I am *still* getting frequent, consistent graphical glitches and studders - often the UI will not update at all until I either move the pointer or, sometimes, click on something. Less frequently, the rendering will just be completely corrupted and all I can do is quit and restart.
This is the easiest problem ever to reproduce - I can do so in one minute. Open an empty, brand new song on any of my M3 Max, M4 Max MBPs or even my brand new, fully maxed out M3 Ultra Studio with *nothing* but S1 installed on it, open and close the browser, editors, inspector, mixer a few times and the UI starts to glitch, fails to update, leaves behind corrupted graphics, etc. Granted, S1 does not crash (most of the time), but working like this is getting really unbearable. PreSonus has acknowledged this issue, like six months ago! I cannot believe it still has not been addressed, and that the only way to mitigate the problem is to turn off GPU rendering, which then makes the underlying sluggishness all the more apparent.
Fixing that problem would go a long way into restoring my faith in S1 long term, but there are other bugs that affect my day to day, such as the fact that "delete time" still works like crap and can corrupt your whole project if you have any sort of complexity in your tempo track and/or time signatures. I have had so many problems with it I have sort of trained myself to work around the bugs, but it is hardly a pleasant endeavor. I frequently end up deleting one bar at the time, slowly cutting around where I know S1 will fail. Quite often that is still not enough, and I end up having to manually fix everything that follows the time region by hand (this can take forever to do, a major productivity drain). And again, there is nothing ambiguous or strange here... these (and the various associated Ripple Edit bugs) have been LONG acknowledged. How have they not been addressed yet? Shouldn't bugs like these be at the absolute top of the to do list?
I don't feel like S1 is missing anything at all - as a matter of fact, like most of the programs of this kind, it has a large percentage of features I could not care less about (that above mentioned stem separation is a perfect example, others would be the launcher or the show page). I don't mind that features that are not relevant to me are being added, and I appreciate that everyone's needs are different, but the way new features are prioritized over core, essential workflow is starting to affect me. If anything could use some updating, in my opinion, it's the MIDI editor, and particularly the CC automation editing (please give me the ability to control which CCs are shown in the tabs below the piano roll).
I have been using S1 since 2014, I know it like the back of my hand, when it works I *fly* around it - it is by all means second nature to me, and yet lately I find myself using Logic more and more. It is just so much more stable and performant with these new machines, especially with large number of tracks and heavy sample libraries. I still like S1 best when it comes to design, workflow and how much it can get out of the way when it comes to the creative loop, but if these bugs are not resolved in *very* short order I will have to switch.
Forget about new features, I would happily settle for an update that fixes the longstanding issues with Apple Silicon Mac GPUs. I am *still* getting frequent, consistent graphical glitches and studders - often the UI will not update at all until I either move the pointer or, sometimes, click on something. Less frequently, the rendering will just be completely corrupted and all I can do is quit and restart.
This is the easiest problem ever to reproduce - I can do so in one minute. Open an empty, brand new song on any of my M3 Max, M4 Max MBPs or even my brand new, fully maxed out M3 Ultra Studio with *nothing* but S1 installed on it, open and close the browser, editors, inspector, mixer a few times and the UI starts to glitch, fails to update, leaves behind corrupted graphics, etc. Granted, S1 does not crash (most of the time), but working like this is getting really unbearable. PreSonus has acknowledged this issue, like six months ago! I cannot believe it still has not been addressed, and that the only way to mitigate the problem is to turn off GPU rendering, which then makes the underlying sluggishness all the more apparent.
Fixing that problem would go a long way into restoring my faith in S1 long term, but there are other bugs that affect my day to day, such as the fact that "delete time" still works like crap and can corrupt your whole project if you have any sort of complexity in your tempo track and/or time signatures. I have had so many problems with it I have sort of trained myself to work around the bugs, but it is hardly a pleasant endeavor. I frequently end up deleting one bar at the time, slowly cutting around where I know S1 will fail. Quite often that is still not enough, and I end up having to manually fix everything that follows the time region by hand (this can take forever to do, a major productivity drain). And again, there is nothing ambiguous or strange here... these (and the various associated Ripple Edit bugs) have been LONG acknowledged. How have they not been addressed yet? Shouldn't bugs like these be at the absolute top of the to do list?
I don't feel like S1 is missing anything at all - as a matter of fact, like most of the programs of this kind, it has a large percentage of features I could not care less about (that above mentioned stem separation is a perfect example, others would be the launcher or the show page). I don't mind that features that are not relevant to me are being added, and I appreciate that everyone's needs are different, but the way new features are prioritized over core, essential workflow is starting to affect me. If anything could use some updating, in my opinion, it's the MIDI editor, and particularly the CC automation editing (please give me the ability to control which CCs are shown in the tabs below the piano roll).
I have been using S1 since 2014, I know it like the back of my hand, when it works I *fly* around it - it is by all means second nature to me, and yet lately I find myself using Logic more and more. It is just so much more stable and performant with these new machines, especially with large number of tracks and heavy sample libraries. I still like S1 best when it comes to design, workflow and how much it can get out of the way when it comes to the creative loop, but if these bugs are not resolved in *very* short order I will have to switch.
Unfortunately, the push to implement improvements and more features can often result in triggering more bugs.
Currently, here's the list of all the features/improvements and bug fixes since the release of Studio One Pro 7.
New Features and Improvements (22 total):
● 30-day demo version now available
● New virtual instrument “Cinematic Lights”
● “Transform to rendered audio” option for busses
● [Impact] Envelope controls for in-place editor
● [Impact] User-definable crossfade for looped samples
● Grid and event visibility improvements
● Note Event selection and editing improvements
● Multi-out instrument bus improvements
● New commands for Launcher
● Option to keep speaker format on bounce in place
● [Note Editor] Added Lydian and Locrian musical scales, also for Atom [SQ]
● Status indicator for transformed tracks, busses, and channels
● Moving/Copying Note Events with arrow keys now follow scale setting
● Improvements for Italian localization 1
● Splice extension updated to v1.1.1, requires Studio One 7.0.1
● Ability to set "follow key" from Studio One
● Populate BPM filter when turned on with the project's current BPM
● Added "Your Library", "Collections", Pack pages
● Support for fractional time signatures
● Improved visibility of grid lines behind translucent Events
● Improved DAWproject compatibility
● Improved visibility of selected vs. unselected Tracks and Channels
Issues that have been fixed (107 total):
● Console Scenes and visibility saved in previous versions not loaded
● [Ripple Edit] Deleting range with tempo setting "Don't Follow" changes event order
● [Ripple Edit] Deleting range leaves gap
● Ripple edit does not respect layers
● Cursor gets stuck after certain edits
● Transform to Bus ignores previous Track speaker format
● Transform back to Bus does not retain position in Console
● Locate Missing Files: Sound Sets not selected correctly for download
● [ARA] Detached editor window causes embedded editors to corrupt their position
● [Browser] Misaligned indicator for selected folder
● [Browser] Tagging Palette display is incomplete
● [CV Instrument] Calibration fails with SSL 12 interface
● [CV Instrument] Potential crash when uninstantiated
● [Documentation] Printer icon is not greyed out on Scratch Pad
● [Launcher] Two cells can be triggered on the same track
● [Linux] Certain pop-up close before user can take action
● [macOS] Build# cut off in installer dialog
● [macOS] File information in “Open” dialog not legible
● [macOS] Lyrics track is overlapping with Browser while entering text
● [macOS] Missing VST3 plug-in header for certain vendors
● [Console] Plug-ins not shown when loading .musicloop created in previous version
● [Note Editor] Notes with maximum velocity cannot be selected in certain situations
● [Note FX] Record armed track with Dropout Protection > “Low” may cause note or effect loss on locating
● [Project Page] Listen Bus disappears after importing I/O configuration preset
● [Show Page] Potential crash when switching patches using Studio One Remote
● [Score Editor] Cursor moves backwards in certain situations
● [Spectrum Meter] Empty bins at high sample rates
● [Windows] Event label text cut at bottom when scaling is not 100%
● [Windows] Potential crash on copying audio events w/Alt+Drag'n'Drop
● Ableton Link causes timeline issues in certain situations
● Adding automation for multi output virtual instrument creates unwanted Automation Track in certain cases
● Alteration indicator (asterisk*) won't disappear when a preset has been saved or recalled
● Auto-created busses don't load from track presets
● Bed Speaker names are cut off in Dolby Atmos Renderer
● Can’t copy notes from looped events
● Demo Song Info does not scroll
● Duplicating (full) multi-out instrument does not create new bus
● Event fade and volume handles vanish while scrolling
● Export Apple Spatial Audio results in a 92 kb fi le when output is set > 2 channels
● HTML code is shown in Studio One Pro+ community notifi cations
● Inconsistent mouse behavior in Console for "Drag Send Chain"
● Input Quantize does not work when recording to cells in Launcher
● Insert Silence in Loop corrupts Arrangement
● Instrument/FX window hides behind application window when losing focus
● Last-used “Launch Loops” template tempo is set as default for new songs
● Loop region locators not fully visible when Browser is open
● Loop tool alters transient of fi rst beat
● Mouse hover events not received when Splice plug-in is focused
● Moving events imported from MIDI fi le may cause freezing in certain situations
● Playback occasionally drops out when jumping back with position marker while playing
● Potential crash on Ctrl/Cmd+Click on Video Track
● Score Editor empty on Scratch Pad
● Select Takes menu not listing all takes
● Selecting part automation in certain ranges of values is broken
● Setting Track to Timestretch may cause unnecessary event resizing
● Spectrum Meter Waterfall/Sonogram corrupted on 2nd display
● Undo of removing / replacing an instrument resets keyboard range on Multi Instrument
● Channel strips and track controls desaturated when colorize option is active
● Colorization cannot be applied to certain channel types
● Korean EULA missing
● "OK" button is grayed out when selecting any PreSonus interface or ToneMaster Pro template
● "Page Up/Down Skip" not working in Macros
● "Transform To Rendered Audio" delivers unexpected results on mono Tracks
● [ATOM SQ] Screen parameters disappear when switching between audio Tracks
● [Browser] Freeze on browsing certain Sound Sets
● [Browser] Preview loop only playing once for short files
● [CLAP] Freeze on instantiating certain plug-ins
● [CLAP] Pitch Bend/Modwheel not relayed to certain instruments
● [CV Instrument] Transforming back to Instrument Track doesn't re-assign Trig/CV outputs
● [Deep Flight One] Volume and layer loss with "Cosmic Dreams" after reopen
● [Demo Template] Text and install button are cut off
● [Impact] Separated channels not visible for Sidechain
● [Launcher] Dragging another Scene to Arrangement causes gap between Scenes
● [Launcher] Frame does not disappear when a device is disconnected
● [Launcher] Track stops recording when switching Scene
● [Linux] ALSA: Artifacts when capturing audio data with certain devices
● [Linux] Crash when opening menu while running KDE Plasma >= 6.1
● [Linux] Flatpak build date is not correct
● [Linux] Keyboard modifiers don't affect drag operations
● [macOS] Potential crash with certain plug-ins
● [Note Editor] Unexpected note selection behavior in velocity lane
● [Show Page] Crash when copying Arranger blocks
● [Show Page] Unable to add lyrics at certain positions
● [Splice] "Pitch" doesn't follow "Transpose" parameter
● [Splice] Shift + Drag from Splice to Impact does not split sample at transients across multiple pads
● [Splice] Unable to drag sample from Splice to Impact after first dragging to Arrangement
● [Windows] Crash when using mouse wheel with Browser tabs
● Applying Mute Tool on looped events causes error message
● ATOM/SQ & Launchpads respond incorrectly active automation tracks
● Bass note can not be set to sharp in Chord Selector
● Connection with Studio One Remote slow with large songs
● Controller data is barely visible during recording
● Crash when stopping note recording into launcher cell in certain cases
● Error message in Macro Toolbar
● Events with Melodyne do not mute if inside 'merged' region
● Hanging notes with certain instruments on solo and "Chase Long Notes" option engaged
● K-Metering is inaccurate
● Kontakt 8 does not load sounds from song saved with Kontakt 7 or earlier
● Marker cursor not visible while moving
● Missing list column headers on Macro Organizer
● Multi Instrument tracks in folder lose routing after transforming to audio
● Muted Audio Event within Audio Part does not refl ect on Audio Part in Arrangement
● Part icons are stacked when recording into an existing part
● Pre-record buff er corrupts Launcher audio cell recording
● Selection exceeds pitch range in Drum View and Piano View with collapsed scale
● Sustain in loop recording takes does not sustain each take
● Waveforms not visible on looped events with tempo change at certain zoom levels
Currently, here's the list of all the features/improvements and bug fixes since the release of Studio One Pro 7.
New Features and Improvements (22 total):
● 30-day demo version now available
● New virtual instrument “Cinematic Lights”
● “Transform to rendered audio” option for busses
● [Impact] Envelope controls for in-place editor
● [Impact] User-definable crossfade for looped samples
● Grid and event visibility improvements
● Note Event selection and editing improvements
● Multi-out instrument bus improvements
● New commands for Launcher
● Option to keep speaker format on bounce in place
● [Note Editor] Added Lydian and Locrian musical scales, also for Atom [SQ]
● Status indicator for transformed tracks, busses, and channels
● Moving/Copying Note Events with arrow keys now follow scale setting
● Improvements for Italian localization 1
● Splice extension updated to v1.1.1, requires Studio One 7.0.1
● Ability to set "follow key" from Studio One
● Populate BPM filter when turned on with the project's current BPM
● Added "Your Library", "Collections", Pack pages
● Support for fractional time signatures
● Improved visibility of grid lines behind translucent Events
● Improved DAWproject compatibility
● Improved visibility of selected vs. unselected Tracks and Channels
Issues that have been fixed (107 total):
● Console Scenes and visibility saved in previous versions not loaded
● [Ripple Edit] Deleting range with tempo setting "Don't Follow" changes event order
● [Ripple Edit] Deleting range leaves gap
● Ripple edit does not respect layers
● Cursor gets stuck after certain edits
● Transform to Bus ignores previous Track speaker format
● Transform back to Bus does not retain position in Console
● Locate Missing Files: Sound Sets not selected correctly for download
● [ARA] Detached editor window causes embedded editors to corrupt their position
● [Browser] Misaligned indicator for selected folder
● [Browser] Tagging Palette display is incomplete
● [CV Instrument] Calibration fails with SSL 12 interface
● [CV Instrument] Potential crash when uninstantiated
● [Documentation] Printer icon is not greyed out on Scratch Pad
● [Launcher] Two cells can be triggered on the same track
● [Linux] Certain pop-up close before user can take action
● [macOS] Build# cut off in installer dialog
● [macOS] File information in “Open” dialog not legible
● [macOS] Lyrics track is overlapping with Browser while entering text
● [macOS] Missing VST3 plug-in header for certain vendors
● [Console] Plug-ins not shown when loading .musicloop created in previous version
● [Note Editor] Notes with maximum velocity cannot be selected in certain situations
● [Note FX] Record armed track with Dropout Protection > “Low” may cause note or effect loss on locating
● [Project Page] Listen Bus disappears after importing I/O configuration preset
● [Show Page] Potential crash when switching patches using Studio One Remote
● [Score Editor] Cursor moves backwards in certain situations
● [Spectrum Meter] Empty bins at high sample rates
● [Windows] Event label text cut at bottom when scaling is not 100%
● [Windows] Potential crash on copying audio events w/Alt+Drag'n'Drop
● Ableton Link causes timeline issues in certain situations
● Adding automation for multi output virtual instrument creates unwanted Automation Track in certain cases
● Alteration indicator (asterisk*) won't disappear when a preset has been saved or recalled
● Auto-created busses don't load from track presets
● Bed Speaker names are cut off in Dolby Atmos Renderer
● Can’t copy notes from looped events
● Demo Song Info does not scroll
● Duplicating (full) multi-out instrument does not create new bus
● Event fade and volume handles vanish while scrolling
● Export Apple Spatial Audio results in a 92 kb fi le when output is set > 2 channels
● HTML code is shown in Studio One Pro+ community notifi cations
● Inconsistent mouse behavior in Console for "Drag Send Chain"
● Input Quantize does not work when recording to cells in Launcher
● Insert Silence in Loop corrupts Arrangement
● Instrument/FX window hides behind application window when losing focus
● Last-used “Launch Loops” template tempo is set as default for new songs
● Loop region locators not fully visible when Browser is open
● Loop tool alters transient of fi rst beat
● Mouse hover events not received when Splice plug-in is focused
● Moving events imported from MIDI fi le may cause freezing in certain situations
● Playback occasionally drops out when jumping back with position marker while playing
● Potential crash on Ctrl/Cmd+Click on Video Track
● Score Editor empty on Scratch Pad
● Select Takes menu not listing all takes
● Selecting part automation in certain ranges of values is broken
● Setting Track to Timestretch may cause unnecessary event resizing
● Spectrum Meter Waterfall/Sonogram corrupted on 2nd display
● Undo of removing / replacing an instrument resets keyboard range on Multi Instrument
● Channel strips and track controls desaturated when colorize option is active
● Colorization cannot be applied to certain channel types
● Korean EULA missing
● "OK" button is grayed out when selecting any PreSonus interface or ToneMaster Pro template
● "Page Up/Down Skip" not working in Macros
● "Transform To Rendered Audio" delivers unexpected results on mono Tracks
● [ATOM SQ] Screen parameters disappear when switching between audio Tracks
● [Browser] Freeze on browsing certain Sound Sets
● [Browser] Preview loop only playing once for short files
● [CLAP] Freeze on instantiating certain plug-ins
● [CLAP] Pitch Bend/Modwheel not relayed to certain instruments
● [CV Instrument] Transforming back to Instrument Track doesn't re-assign Trig/CV outputs
● [Deep Flight One] Volume and layer loss with "Cosmic Dreams" after reopen
● [Demo Template] Text and install button are cut off
● [Impact] Separated channels not visible for Sidechain
● [Launcher] Dragging another Scene to Arrangement causes gap between Scenes
● [Launcher] Frame does not disappear when a device is disconnected
● [Launcher] Track stops recording when switching Scene
● [Linux] ALSA: Artifacts when capturing audio data with certain devices
● [Linux] Crash when opening menu while running KDE Plasma >= 6.1
● [Linux] Flatpak build date is not correct
● [Linux] Keyboard modifiers don't affect drag operations
● [macOS] Potential crash with certain plug-ins
● [Note Editor] Unexpected note selection behavior in velocity lane
● [Show Page] Crash when copying Arranger blocks
● [Show Page] Unable to add lyrics at certain positions
● [Splice] "Pitch" doesn't follow "Transpose" parameter
● [Splice] Shift + Drag from Splice to Impact does not split sample at transients across multiple pads
● [Splice] Unable to drag sample from Splice to Impact after first dragging to Arrangement
● [Windows] Crash when using mouse wheel with Browser tabs
● Applying Mute Tool on looped events causes error message
● ATOM/SQ & Launchpads respond incorrectly active automation tracks
● Bass note can not be set to sharp in Chord Selector
● Connection with Studio One Remote slow with large songs
● Controller data is barely visible during recording
● Crash when stopping note recording into launcher cell in certain cases
● Error message in Macro Toolbar
● Events with Melodyne do not mute if inside 'merged' region
● Hanging notes with certain instruments on solo and "Chase Long Notes" option engaged
● K-Metering is inaccurate
● Kontakt 8 does not load sounds from song saved with Kontakt 7 or earlier
● Marker cursor not visible while moving
● Missing list column headers on Macro Organizer
● Multi Instrument tracks in folder lose routing after transforming to audio
● Muted Audio Event within Audio Part does not refl ect on Audio Part in Arrangement
● Part icons are stacked when recording into an existing part
● Pre-record buff er corrupts Launcher audio cell recording
● Selection exceeds pitch range in Drum View and Piano View with collapsed scale
● Sustain in loop recording takes does not sustain each take
● Waveforms not visible on looped events with tempo change at certain zoom levels
Gary Shepherd
New member
I think anyone trying to make tempo changes will find the "tempo map" incredibly un-intuitive and clunky (almost unusable at times) - constant need to use Undo as each attempt to add another change in tempo goes wrong. If ever there was a need for a list editing function for tempo, then this is it.
And don't get me started on Scrolling and particularly Auto Scroll which switches itself off.
And don't get me started on Scrolling and particularly Auto Scroll which switches itself off.
