The first major revision to Steinberg's Cubase SX incorporates the newly developed audio engine from Nuendo 2, new features for media composers, and classic features from Cubase VST. Does it all add up to a substantial improvement over version 1?
In the relatively short time that's passed since the first Cubase SX release in August 2002, Steinberg have released an OS X version, a slimmer version in the form of Cubase SL, and a major upgrade to the company's high-end media production system, Nuendo 2. Now, Steinberg have now come full circle, releasing the much-anticipated 'version 2' of Cubase SX.
In the same way that Cubase SX was originally developed from technology used in Nuendo 1.x, much of the technology in SX 2 is derived from Nuendo 2, which isn't surprising as Steinberg have been moving towards a 'common framework' approach for some time. However, this strategy has caused a degree of discontentment amongst users of Cubase and Nuendo over the past year as the two applications 'leapfrog' each other with every new version, but with Cubase SX 2 and the forthcoming Nuendo 2.1 update, which will incorporate SX 2's new feature set back into Nuendo, Steinberg have finally reached the point where they can roll out new Cubase and Nuendo versions much closer than in previous releases. This should make it much easier for prospective users to decide which product better suits their needs, without fear of essential features appearing in the 'other' program first. For more information about this subject, I spoke to SX's Product Manager, Arnd Kaiser, and you can read his comments in the 'Spot The Difference' box.
Given that so many of the new features in SX 2 are pretty much identical to those found in Nuendo, which were discussed in great detail in September 2003's issue, I'll only give a brief overview here, and focus primarily on those features that debut for the first time in Cubase SX 2. For a more detailed tour of the functionality that's shared by both Nuendo 2 and SX 2, check out that Nuendo 2 review.
As with Nuendo 2, Steinberg supply both Mac OS X and Windows XP/2000 versions of Cubase SX 2 in every box (on separate CD-ROMs), even if you're upgrading from a previous version, which means that every Cubase SX 2 user has the ability to switch platforms whenever they want. I think this is a commendable move, and with Logic now sold as a Mac OS-only product by Apple and Emagic, Cubase and Nuendo remain the only cross-platform sequencers on the market that are not tied to one manufacturer's audio hardware.
In terms of system requirements, Windows users will need at least an 800MHz Pentium or Athlon-based system, although 1.4GHz or greater is recommended, unless you're using a laptop system with a Pentium-M processor, for example, where clock frequencies can't be directly compared. Mac users will need at least an 867MHz G4 system, and while Steinberg recommend a dual-1.25GHz G4 for best results, this doesn't mean it's impossible to use SX 2 on a G3-based system, it's just rather slow. You'll need at least 384MB RAM, and Steinberg's recommendation of 512MB is, I think, fast becoming the minimum amount of RAM you'd want in a music computer.
The first time you run Cubase SX 2, you'll notice that the user interface has visibly changed quite a bit from the previous version, although this is mainly an aesthetic change influenced by the new 'look and feel' of Nuendo 2, and existing users shouldn't have too much problem finding their way around. The appearance of a user interface is always going to be a personal thing, but for the most part I do prefer the new, darker facade of SX 2. In any case, it's now possible to configure the basic colour scheme via internal Themes, and you can also now adjust the colours used in the Project and editor windows via faders to fine-tune the contrast of the 'cycle intensity', 'work area brightness', horizontal and vertical lines, and so on. A nice touch.
Aside from appearance control, Nuendo 2 also allowed the user to extensively customise the user interface, and while SX 2 doesn't quite go so far as making it possible to reconfigure all the menu options, the most useful configuration options have been kept. This means that in addition to simply enabling and disabling various parts of the much-expanded, Nuendo-derived Transport Panel, toolbar elements and Track Control buttons, you can now make presets of the various combinations. It's definitely useful to be able to configure the user interface for different situations, such as recording, editing and mixing, but as with Nuendo 2, I'd love to see future versions make it possible to create global combinations that encompass all the individual presets, rather than the user having to select different presets for different parts of the program manually.
Steinberg advertise Cubase SX 2 as having over 100 new features, and a large proportion of these are found in the audio side of the application, thanks to the inclusion of the new VST 2.3 audio engine. As you may already know, this is the same audio engine used in Nuendo 2, meaning that Cubase's Mixer now has multi-channel signal routing and delay compensation through the entire signal path. Also, since the VST 2.3 audio engine has been optimised to make use of hyperthreading (Intel's technology for making the redundant processing power of a CPU appear to the system as a second processor), SX now takes full advantage of the latest Intel Pentium 4 and Xeon processors.
As in the previous version of SX, the audio engine implemented in SX 2 is limited to six-channel paths, making it possible to do 5.1 surround work (or indeed any configuration up to six channels, such as LRC, LRCS, Quad, and so on), as opposed to the 12-channel path in Nuendo. However, this is a limitation few involved in music production will be concerned by, and 5.1 mixes could easily be adapted to 7.1 or other surround configurations in Nuendo later on in the production cycle if need be.
The new signal routing system also sees the VST Inputs and Outputs windows being amalgamated, rather sensibly, into the Device Setup window. And, in addition to simply enabling and disabling the physical input and output ports on your audio system as before, you now need to configure input and output busses for audio-based Tracks in the new VST Connections window. While this extra step may seem a little complicated at first, it overcomes the problem of most ASIO drivers presenting ports as stereo pairs, which is especially important if you want to use a 5.1 Audio Track with a 5.1 input.
The only area where the VST Connections window differs in SX 2 compared with Nuendo is in the lack of Child Busses. These allow you to create a stereo output buss that outputs to the left and right channels within a Nuendo surround output buss, for example, and while it might have been a nice touch to have Child Busses in SX, especially for those who want to work in stereo and 5.1 configurations within a single Project, again, I don't think this is a serious omission for Cubase users.
In addition to the VST Inputs and Outputs windows disappearing in SX 2, the VST Effects window has also taken its leave because, as in Nuendo, send effects benefit from the system-wide delay compensation and are now handled by the new FX Channels on the Project window and Mixer. FX Channels are, in effect, much the same as Group Channels, and, as with other audio-based Tracks, support up to eight insert effects. This means that it's now easy to chain effects on a single send — for instance to EQ a reverb — and it also puts the send effects controls and outputs directly onto the Mixer, saving you from opening additional windows.
The Mixer window has also evolved in SX 2, and is, unsurprisingly, the same Mixer window found in Nuendo 2. Input and Output Channels can now be displayed in two split sections of the Mixer, allowing you to monitor and process the signals coming into and out of your audio hardware, both before and after they've been processed by the Audio Tracks. By using insert effects on the Input Channels, you can now record an audio signal which has already been processed by a plug-in onto an Audio Track, and the Output Channels effectively eliminate the need for the dedicated Master Channel in previous versions of Cubase.
Since the audio functionality of Cubase SX 2 is the biggest area of feature overlap with Nuendo 2, I recommend looking back to the original Nuendo review, as mentioned in the first part of this article, for a more detailed analysis of the new audio features in SX 2. But overall, if you thought the audio features were great in SX 1, you're going to be requiring at least one change of underwear when you work with audio in SX 2.
Many users' biggest criticism of the original version of SX was the lack of any features for manipulating tempo, beyond simply the ability to create a tempo change to 150bpm at bar 11, for example. So it's perhaps no surprise that one of major improvements in SX 2 targets this very area of the sequencer with the inclusion of a new feature called the Time Warp tool.
The basic concept is of the Time Warp tool is that it enables you to drag any bar or beat location to any time location, which comes in very handy when you want to build a musically sensible structure of bars and beats around material that wasn't necessarily recorded against a strict metronome. If this description sounds a little vague, imagine that you want to use the score editor to represent a MIDI recording not played to a metronome click, or that you have some video with visual events that need to be tied to bar or beat locations, so-called hitpoints. In these scenarios, the Time Warp tool provides possibly the most intuitive method yet seen in any sequencer of creating a tempo map, enabling you to make sense of time-based material in terms of bars and beats.
In its default mode, the Time Warp tool works by automatically switching all the Tracks in a Project to the Linear Timebase (rather than the default Musical Timebase), so that all the Events in your Project retain their locations in time. As you drag the Time Warp tool, the preceding Tempo Event (which will be at bar one if you haven't added any tempo changes already) changes so that the bar or beat you're dragging will line up with the correct position in timecode. One thing I found initially frustrating about dragging bar and beat lines with the Time Warp tool was that there's no indication as to what timecode location the bar or beat line is hovering over, in the way Cubase indicates the location when you're copying or moving objects. However, Steinberg are planning to sort this out in v2.01, and if you set Snap mode to Events, you can get the Time Warp tool to snap to an existing object, which can be placed at the required timecode position.
New Tempo Events can be added with the Time Warp tool by clicking with the Shift key held down, and if you want to limit the area of the Project affected by the Time Warp tool, you can make a range selection before selecting the tool. When you drag the Time Warp tool in a range selection, new Tempo Events are created automatically at the start and end points of the selection to isolate it from the rest of the Project, which is pretty useful. And another nice touch is that when the Time Warp tool is selected, the Project's Tempo Events are displayed as flags in the Ruler with their numerical values displayed.
In addition to being available in the Project window, this default mode for the Time Warp tool can also be used in the Key, Audio Part and Sample Editors, which really is rather handy. The ability to use the Time Warp tool in the Key Editor is great for those writing to picture, and those cleaning up the timing of freely recorded MIDI Parts, while being able to use this tool in the Sample Editor makes it very easy to line audio up against the musical timeframe in the Project. However, there's also a second 'musical events follow' mode for the Time Warp tool that's only available in the Project window, and this effectively leaves the Tracks in Musical Timebase so that objects stay locked to their musical position in bars and beats, and so move about in time, as you drag the Time Warp tool.
Good though the Time Warp tool is, it does have a serious limitation, in that it doesn't allow for situations where you need to process multiple tempo changes with one command, such as the old Process command in Cubase VST's Master Track Editor. If, for instance, you have a Project that lasts one minute, but you later need to make the same Project last 55 seconds, there's currently no way to compress or expand a group of Tempo Events to make this kind of operation possible in SX. To overcome this situation, I think it would be good if you could hold down another modifier key while using the Time Warp tool to expand or compress the positions of a group of Tempo Events, perhaps marked by a range selection or from the position of the Project Cursor. However, I don't want to sound too negative about this feature. While it doesn't offer a true replacement for all the tempo functionality available in Cubase VST, the Time Warp tool is an innovative first step in the right direction, and I know Steinberg have plans to take develop this feature in future versions.
When Cubase SX first appeared, many users of previous Cubase versions complained about features that were 'missing' in SX compared to the Cubase they already knew; and in some cases, while alternative solutions were provided instead, some existing Cubase users felt they preferred the old way. Fortunately, though, Steinberg have responded to these criticisms, and SX 2 contains both features from Cubase VST 5.x, along with many 'classic' Cubase alternative ways of working.
One such classic feature that returns to Cubase in SX 2 is the Toolbox, which displays the tools available in two rows of icons for a particular window, be it the Project window or an Editor, allowing you to choose another tool to work with. This is an alternative to SX's Quick Menu, and can be displayed by holding down Control/Command and the right mouse button, or you can configure the Toolbox to appear in place of the Quick Menu when holding down the right mouse button via a Preferences option. Personally, I didn't mourn the loss of the Toolbox in SX, but I know many people did, and I'm sure they'll be celebrating its return.
Similarly, as in pre-SX versions of Cubase, you can now repeat objects on the Project window by holding down Alt/Option with the Selection tool and dragging the object's right-hand extension handle, which temporarily displays the Draw tool, although strangely, this doesn't seem to work when the Draw tool is actually selected. Multiple Audio Events and Parts can now be edited simultaneously in a single Audio Part Editor window again, and it's also possible to drag MIDI files from the Desktop directly.
Another feature making a welcome return for those who use Cubase's Score Editor is the MIDI Meaning window, available from the Global Settings submenu of the Scores menu. When active, MIDI Meaning allows certain score symbols to affect the notes to which they're attached in terms of adding or subtracting length or velocity, making it possible for staccato or accent markings to be played back as intended.
If the Time Warp tool is a step in the right direction, there's another new feature in SX 2 that's practically Jonathan Edwards — before he retired, of course. Hyperbole aside, I'm talking about a feature called Stacked Cycle Recording, which solves a problem that too many sequencers and audio workstations have yet to overcome, in my opinion: handling multiple takes of the same track(s).
Say you're recording a vocal track and you manage to get a successful first take in the Project window. There were a few areas that need attention, but you want to keep that take and record another. In an ideal world, you want to record another take straight away, of course, but with exactly the same Channel settings, while keeping the original take (once it's been muted, of course) on the Project window for later editing. And this is where it gets tricky: the only real way to record another take in SX 1 was to set up another Track and copy and paste the settings from the Track on which you had recorded the original vocal take.
In previous versions of Cubase, the only true mechanism for dealing with multiple takes meant you had to use Cycle Record mode to record each take one after the other — without stopping the sequencer — which was obviously impractical. However, multiple takes could later be compiled in the Audio Part Editor, which was actually a pretty good solution, with each take displayed on a separate horizontal lane (much like the Project window). But this didn't work for MIDI Parts, of course, and the facilities for cycle recording MIDI data in SX 1 were generally regarded as being a little inadequate.
Stacked Cycle Recording does much as its name suggests: it allows you to stack recordings made in Cycle Record mode within a single Track, and best of all, it works for both MIDI and Audio Tracks. To make use of this new mode, you first set up for cycle recording as normal, setting the Left and Right Locators to define the region you want to record, and enabling Cycle mode. Next, set Cycle Record mode to Stacked in the Transport Panel, and as you record each cycle, you'll notice that Cubase begins to subdivide each Track into lanes, with each take assigned to its own lane within the Track in a top-down order.
The main advantage of Stacked Cycle Recording is that where you would previously have needed to compile Audio Events into an Audio Part and used the Audio Part Editor to compile a 'perfect take' using its lane-based approach, all of this can now be done on the Project window. Indeed, the multiple lanes within a single Track on the Project window behave in exactly the same way as in the Audio Part Editor, with the lowest lane having playback priority.
In addition to the Time Warp tool, many other useful features that have been added in SX 2 to aid tempo manipulation. Nuendo 2 included an option in the Beat Calculator that allowed multiple tempo changes to be created based on a regular pulse of MIDI events in a selected MIDI Part, and although this option is missing from the Beat Calculator in SX 2, it's implemented instead as the 'Merge Tempo from Tapping' function in the MIDI menu. If you're trying to align a long MIDI Part not recorded to a click, the quickest first approach is perhaps to use this function, then the Time Warp tool to fine-tune the tempo changes later on.
Another new feature in the Tempo editor is a Tempo Recording slider on the toolbar, which allows you to record tempo in the same way you might record volume automation during playback, for example. If you're working to picture, such a slider is obviously useful so you can 'ride' the tempo whilst watching the film, and it's also a nice addition for adding tempo-based expression to your music generally. My only request here is that it would be great if you could assign this Tempo Recording fader to a MIDI controller number, allowing you to control tempo from a physical fader, and perhaps making it possible to limit the tempo range to overcome the seven-bit limitations of MIDI controller data.
Lastly, Steinberg have made it possible to import and export tempo maps separately from the rest of the Project, which is great news for users who would previously have to import and export MIDI files to achieve this result. And speaking of tempo maps, it's now possible for the precount (or the count-in) to follow the Tempo Track, rather than simply counting in at a static tempo.
If all Steinberg had done was to integrate the Audio Part Editor (which is still present in Cubase SX 2, incidentally) into the Project window, Stacked Cycle Record mode would still have the same disadvantage when it came to recording multiple takes of the same Track — which is to say, not being able to stop the sequencer in between takes in order to use the same features for dealing with multiple takes. So instead, with Stacked Cycle Record mode enabled, when you record again on a Track that already contains a Part or Event, Cubase will simply create a new lane on the Track where the new material will be recorded, and the original take will be automatically muted. This is absolutely brilliant, and something I (and many others, I'm sure) have dreamed about since using Nuendo 1.0 over three years ago.
As with any new feature, there's always room for improvement; and, as with the Time Warp tool, Steinberg already have plans to extend stacked recording in future versions of both SX and Nuendo — including the ability to use it outside of Cycle Record mode. One issue that becomes apparent as soon as you use Stacked Cycle Record is that for this mode to become active, the first record pass made in Stacked Cycle Record mode must complete a full cycle, reaching the Right Locator. Mind you, this could be overcome by recording a dummy one-bar pass before moving the Locators to record a full take, since subsequent takes don't have to record all the way to the Right Locator.
This workaround highlights another interesting point with Stacked Cycle Record mode, which is that once it's been activated on a Track, you can move the Left and Right Locators, changing the Cycle Record region, and Cubase will continue stacking up the recordings on different lanes. However, if you record on a completely empty area of a Track that already contains Stacked Cycle recordings, Cubase will place the new recording on the uppermost Lane, rather than the Lane on which it previously recorded. This makes sense in some situations, but, even though it's easy to move objects to different Lanes, it might be nice to be able to manually force which Lane you're recording onto, in addition to the current 'auto' option for a future release.
Pro Tools has handled multiple takes elegantly for many years, thanks to its Playlist feature, effectively allowing you to create virtual tracks (the so-called Playlists) within a given track to record alternate versions, or compile a final take by copying and pasting between these different Playlists. In many ways, I think Stacked Cycle Record mode is a better solution since it allows you to see all the 'playlists' at once, but there's one area where Cubase doesn't quite catch up in the current version.
If you're recording multiple takes of a drum kit, for example, that's separated out across many Tracks, there's currently no quick way of choosing to listen to a particular take on a number of Tracks. Instead, you have to manually mute all the takes you don't want to hear, or move the required takes to the lower-most Lane, which you can do manually or with the useful 'Move To Next or Previous Lane' commands. What's needed is a way of quickly being able to mute everything but the chosen Lane across selected Stacked Cycle Record mode tracks. However, this criticism is admittedly more about the icing than the cake, because even in its current state, Stacked Cycle Recording is a killer feature, and a very welcome addition to SX.
As mentioned in the review text, there's been some confusion and criticism concerning the similarities between Cubase SX and Nuendo, despite Steinberg stating on many occasions that the two products were designed for music production and post-production. In order to better understand how Steinberg hope to make this distinction clearer, I spoke with SX's Product Manager, Arnd Kaiser, who comes to Steinberg after working on products such as Alesis' Andromeda and Hartmann's Neuron.
"Our distinction for Cubase and Nuendo has indeed been music production and post-production or media production. I learned that people who have a problem separating between these two products are usually musicians or music producers. They don't see the extra features offered by Nuendo, such as the external synchronization, advanced crossfade editing, more powerful surround, and so on, and how important they are for a post-pro user, but that's OK. We've just accomplished an important step by merging the code base of both applications, which will have enormous advantages for development in the future. After the next round of updates, the differences between both applications will become a lot more obvious, but Nuendo will always inherit all Cubase features, meaning it will always be complete — and SX users can always crossgrade."
With Cubase now being the only cross-platform, hardware-independent sequencer available, I also asked Arnd if Steinberg were committed to this strategy. "Absolutely. Our goal is to design products for users, not for platforms, and the users themselves should be able to decide which system they build their studio on. Cubase SX is powerful in many different fields, and limiting it to just one platform would work against that. I like systems to be open, by supporting multiple platforms, keeping things compatible, and being open for other formats as well, such as OMF. That's a good thing to have, isn't it?"
The VST 2.3 audio engine, the Time Warp tool and Stacked Cycle Record mode are definitely the 'big three' improvements in Cubase SX 2, but that's not to say they are the only areas where program has evolved. The MIDI Editor windows have received some welcome attention, especially when it comes to working with multiple Parts displayed in the same Editor window. For example, it's now possible to display multiple Parts in the List Editor as well as the others, and to make it easier to mask the data displayed in the List Editor, you can now choose to mask data based on Logical Editor presets, which I think is really great idea.
In the Key Editor, a Part list pop-up menu has been added to the toolbar, enabling you to easily select which Part is selected for editing, which is both an improvement on the 'blindly clicking notes' approach in SX 1, and the Next and Previous Part commands in VST 5. A further improvement to this mode of working is the Edit Active Part Only button, and when this is enabled you can only edit (yes, you've guessed it) the active Part, which makes it possible to use selection commands without having to worry about altering events from other Parts being displayed in the editor.
You can now open a MIDI Editor, as in Cubase VST 5, without having any Parts selected, whereupon all the Parts on the currently selected Track are opened; and another classic Editor feature that's back in SX 2 is the ability for the Editor to have its own internal Cycle playback Locators that work independently of the main Left and Right locators. Other improvements include a chord indicator, where the chord made from the notes currently under the Project Cursor is identified, the ability to set five different insert velocities when entering notes, which can be switched via Key Commands or selected from a pop-up menu on an editor's toolbar, and that it's now possible to use the different Draw tools for entering and manipulating controller data in the Controller Lanes.
If you enjoyed the rather long-winded technique for extracting grooves from MIDI Parts and applying this when quantising other MIDI Parts (see March 2003's Cubase Notes), you'll really like the new 'Part to Groove' command in SX 2, which finally catches up with most of the features previously available via the Groove Control window in Cubase VST 5. It's now possible to use a MIDI Part to create a quantise template (or 'groove'), and use this to quantise other MIDI Parts.
In addition to inheriting Nuendo 2's audio engine and the majority of the related feature set, Cubase SX 2 also gains other 'first seen in Nuendo 2' features. These include the EQ Graph and Notepad Sections in the Inspector, the inclusion of a velocity parameter for MIDI Parts and the ability to select and modify multiple objects in the Event Infoline, and one of my favourites, the ability to effectively split the Project window in half with the Divide Track List feature, allowing you to hold Marker and Video Tracks at the top of the Project window, for example, while scrolling the other Tracks in the lower half.
Two other long-term Nuendo features that have been included in SX are OMF import and export, enabling Cubase users to share their Projects with users of programs such as Pro Tools, and Libraries, which are basically Pools that can be loaded into a Project in addition to the Project's own Pool. This is useful where you have groups of audio files, such as a sound-effect or drum-loop collection, that you want to be able to copy into other Projects without having to worry about where the original files are stored on disk.
Last but not least, Steinberg have also added a 'freeze' feature, where the user can click a newly added button on a particular VST Instrument in the VST Instruments window and signals generated by that VST Instrument are frozen into an audio file. The VST Instrument is then disabled and Cubase plays back the audio files instead. The process is entirely transparent from the user's perspective, and you can later unfreeze a VST Instrument if you want to make changes. Unlike some competing implementions of this concept, only the output of a given VST Instrument is frozen (and not any insert effects that may be used on the outputs), which is actually quite useful if you want to free up processing resources for mixing, and you have to freeze the output of the VST Instrument for the entire length of the Project.
My biggest criticism of most current freeze implementations is that they only save processing resources: any memory used by the VST Instrument remains reserved when the VST Instrument is frozen, rather than being unloaded, which means you may run out of memory long before you run out of processing resources, especially if you're using sample-based instruments. Still, that's not to say SX's Freeze command can't be useful, especially with soft synths like Absynth that are fairly processor-intensive but doesn't use that much memory.
While both the Mac and Windows versions of SX 2 are functionally identical, my experience has been that the Windows version is pretty stable, with the odd crash occurring when I was running applications like Gigastudio alongside Cubase, although this was admittedly quite rare.
While the Mac version has improved significantly since SX 1, it still doesn't feel quite as snappy as the Windows version, and there seem to be many more odd little issues that vary from machine to machine. Admittedly, though, this could be down to the hardware itself, and unfortunately I wasn't able to get hold of a G5 in time to gauge Cubase performance on the most powerful Macs.
Cubase SX 2 enters the market at an interesting time, facing tough competition from the latest generation of other MIDI + Audio applications, such as Sonar 3, Digital Performer 4 and Logic 6. From a personal perspective, putting the feature lists to one side for just a moment, I think I like using Cubase SX the most out of all the sequencers, primarily because the Project window is powerful, elegant, and, as I said in the original SX review a year ago, never feels like it gets in the way of what you're trying to achieve. As Steinberg make it possible to achieve more and more in just the Project window, I think the brilliance of the design is proven because, even with all the new features, it doesn't feel cluttered.
Existing SX users should upgrade to SX 2 immediately, without a doubt, because they'll simply love the new feature set. For OS 9-based Cubase VST 5.x users who didn't feel comfortable in making the jump before because of so many 'missing' features, SX is now a far more viable prospect than before and deserves serious consideration, especially since you can't actually buy a new Mac that boots in OS 9. However, whether users of other sequencers will be tempted to switch is another, perhaps more subjective and personal matter, although I'm sure some users will at least be curious about using Nuendo's advanced audio functionality at a lower price, especially if cross-platform work is important to you.
At the end of the day, SX 2 is a remarkable improvement over SX 1 in just about every respect. Although there are some features that still need to be brought back from VST 5.x, along with the issue of manipulating multiple Tempo Events in one go, and other small improvements that could be made, Steinberg have at least made an effort to address the weaker areas in the first release of SX a year ago. The more I worked with this new version, the more I liked it, and the more improvements I discovered; when I need to use a sequencer, the red diamond is still the icon I'm going to be double-clicking.