Samplitude Pro X9?

[lfm]

Some decisions though made by devs are just strange.
- the field for cursor position and range start is always combined.

- even custom fields does not allow Start of range in a separate field

As soon as you move cursor that is shown in the field, not even moving start will tell you where it is?

I saw no other daw do that, they all have start and end in separate fields and always there. Move start and you see where it is in numbers.

There is room for 5 fields, why not a separate for Range Start....

Tbh you lost me there... I am not quite sure what you mean.

Drag a range selection in timelime ruler bar
- the left/position field is combined
- click somewhere so cursor moves inside or outside range
- you have no left range position number in display anymore
- field is taken over by cursor position

Now move the left range marker i timeline
- not even now do you get the positon of that range start
- you don't see where you drop it in numbers

All daws I used have separate fields for the selected range start and end.
- then one for cursor position
- Sonar has button too, to create a loop range for this range

Would be nice if an update allowed to customise so left range position can always have that number too, not only end position.
- I lost some vital information not having that

Cool you can customise 5 fields with some numbers of your choise, like mouse positon or something else. But the Start/Position field is only available as a combined fields.
- very odd to me

I think punch in range stays start and end though.

[careyletendre]

I think they're taking extra time to make a scalable/resizable GUI.

[mcaroul]

It looks like the official word from Magix is that X9 is not coming until summer (2025).

https://community.samplitude.com/topic/ ... ent-357152

"...we extended Pro X8 lifecyle and X9 should arrive somewhere around next summer."

[jens]

Not quite sure what to make of that...

However for me the honeymoon with Samplitude is definitely over anyway. I have the weirdest problems - which are almost exclusively related to audio-take handing - with it and so the songs that are at least halfway complete aside, I am done with it for now. It's really buggy and partly outright bizarre - and a HUGE PITA.

[mcaroul]

I find it buggy compared to reaper, but I love samplitude's workflow and just cannot connect with or understand reaper. But yes, unpredictable behavior in samplitude is slowing me down. Hoping for continued bug fixes in x8 and that x9 will be revolutionary

[jens]

I don't like Reaper, theoretically I like Samplitude a lot more for a variety of reasons - but personally I am quite familiar with Reaper and find working with it overall somewhat dull&boring, yet robust and predictable... even if its interface is somewhere between a nightmare and a bad joke to me for the most part of it.

[lotus2035]

I wonder how Sequoia handles things in comparison.
Surely the insane price difference means it's the program that Samplitude should have been right? Solid and dependable?
If not then it would be the worst case of the emperor having no clothes ever.
Imagine paying almost 2000 euros for that and it craps out on you at every opportunity.
Honestly, even Samp at full price is too much considering how it behaves and feels but it seems to have a lot of users judging by their forum.
I rebuilt a couple of my FL Studio projects in Samp Pro X7 and it felt like it was struggling. I don't think I could trust it with fully blown midi/audio projects. As an audio editor fine, but I already have Sound Forge for that.

[Mr D]

Sequoia is exactly the same as Samplitude, apart some obscure stuff that you probably don't need.

But the core functionality is identical.

I used to use Sequoia for mastering, but over the years they moved a lot of the mastering features over into Samplitude, so i don't need it any more.

I've tried every major DAW over the years and honestly i don't think there's anything that can touch Samplitude for pure audio editing.

If you need MIDI and complex mixing and production tools, then i'd look at another DAW.

[jens]

honestly i don't think there's anything that can touch Samplitude for pure audio editing.

Too bad that it's a total mess though when it comes to audio-recording...

[DaveClark]

Hi all,

One thing that Samplitude has been deficient in for many years is VST3 hosting. I've contacted Magix countless times about fundamental misunderstandings they apparently have. Just yesterday, I found another truly basic problem, causing me to wonder how many others have discovered this, perhaps long ago:

Here we are in 2025. Apparently Samplitude Pro X8 Suite (the latest and greatest) still does not descend into the bundle-folder structure if a project previously used a plugin stored in the old format. I found that Pro X8 Suite failed to load IK Multimedia’s recently updated Lurssen Mastering Console, now stored in a bundle, when opening a project that used to load Lurssen when stored as a file, the old non-bundle format which was deprecated in 2018. After renaming the bundle so that it wouldn’t clash with the plugin name, I moved the plugin up to the level of the top of the bundle, and Voila! The project loaded the plugin. I found exactly the same thing with MF-108S (Moogerfooger Cluster Flux) which I believe was updated since the project was (declared) completed.

It is a trivial programming exercise to attempt to open a file with certain "flags," then discover that the file wasn't what was expected, then continue appropriately - in the case of VST3 file versus VST3 bundle, this would be to descend into the folder structure. Instead Samplitude Pro X8 Suite simply returns something like: "Failed to load plugin." What makes this error so much worse is that Samplitude has usually already scanned the entire folder (usually VST3 under Common Files) and has all the information required to locate the plugin.

I repeat: The old file format was declared "deprecated" in 2018. In my experience, it takes Samplitude developers forever to fix a VST3 hosting problem.

Update (27 Jan 2025):

Tech Support responded just today that the developers had fixed the problem with the latest patch (24222) which I have installed already a few weeks ago. It is not a complete fix because to complete the job, one has to " delete VstPlugins.ini from the folder:

C:\ProgramData\MAGIX\Samplitude Pro X8 Suite "

In other words, start over again. I am testing whether or not this actually works right now. Many of their "fixes" don't actually work. In fact, when I deleted the file above, it got restored from somewhere, so the file needed to have all the plugin information deleted out of it, but exist. In VstPlugins.ini, I deleted everything after the tag [VstPlugins].

Update 2 (27Jan 2025):

No surprise: Test failed, not fixed.

Also, when VstPlugins.ini is deleted, it gets restored. What actually has to be done is to delete everything after the tag [VstPlugins]. Even though the scan works, including adding newly added bundles to the list of plugins when they are updated, Samplitude will still open old projects that had non-bundle format plugins previousy as if the plugins were sill the old format, therefore fail to descend into the bundle, resulting in an error message saying that the plugin failed to load.

[DaveClark]

Hi all,

Workaround for problem described immediately above:

If you find that opening an older Samplitude project (perhaps as recently as just before you upgraded a VST3 plugin a moment ago) results in a failure to open the plugin, you might want to go look at your version of:

C:\Program Data\MAGIX\Samplitude <Your version>\Vstplugins.ini

Search for your failed plugin in this .ini file.

If you see two or more of them, one a .vst3 *FILE* directly under VST3 (or other subfolder that contains your VST3 plugins):

VST3\<Your plugin>.vst3

with no further subfolders Contents or x86_64-win and the other one further down in what looks like a folder tree:

VST3\<Your plugin>.vst3\Contents\x86_64-win\<Your plugin>.vst3

For backup, you might want to save a copy of this file with another extension or zip it up, then delete the first line above, save the file and try again. There cannot actually be two different items named <Your plugin>.vst3 under VST3, even though one is a file and the other directory or folder (bundle name).

Now you may notice in the ini file that there appear to be two iems with subfolders Contents\x86_64-win that are almost identical, but at the end one has something like "--Other--" while the other has "". These are categories so result in multiple listings in the ini file for the SAME plugin. These are not an old plugin file at a higher level that was deleted and a newer version in a folder tree or bundle that is still there in the VST3 folder.

This is not from Magix, but my own solution to this problem. Hope it helps.

[TurnKeyLive]

Pro X9 landing probably tomorrow for anyone interested.

[lfm]

Seems they moved release another week or so now 25th.
- for 10 months they moved a full month for discount to expire and put a new one instead

I cannot see why they did not
- release new version home page already
- tell about grace period free upgrade for current owners

So you can export for a range in timeline
- been forever in Sonar/Cakewalk
- one thing that is first mistake not to select the timeline involved in an export

I just hope for some improvments/fixes from ProX8 to move some projects to Samp.
- I like the looks, good readability all over
- no stability issues going through the various recording phases
- figured out the "control room" to dim rest of mix while recording a new track
- manual is extensive and off line and you can usually find things out for yourself

But silly amount of cpu playing back video in Samp window is the worst holding me back.
- just playing video takes away about 30 tracks with plugins before needing to freeze tracks

If upgrade cost is about $100 only I might take a chance and just upgrading.
- if not fixing cpu on video I just abandon it, and loss is within acceptable

Good people on Magix, and they fixed a P2-serial right away, instead of current P3 that needs "phoning home" every month. My daw computer is not online other than for needing to update software. Even windows updates are turned off so not needing that.
- all is working, nothing to fix

[havran]

Hmm. Sale price for Samplitude Pro X8 runs until June 30th now.

[jens]

Yeah... I probably should have made screenshots of the Pro X9 product details several (German) retailers showed a forthnight or so ago... (it was quite bit more than what's shown above)


edit:

here's a but of it:

NEW FEATURES

Dolby Atmos: 3D audio rendering for immersive soundscapes in up to 7.1.4.
ADM editor offers advanced options for metadata.
Extended bus formats up to 12 channels.
New channel setups for Dolby 5.1 to 7.1.4 for extended surround mixes.
3D Reverb: Realistic surround sound ranging from small studios to large concert halls.
Range Marker: Clear overview and precise editing, even with complex audio projects.
Range Marker Export: Export specific project sections with precise control.
Multitrack (Stem) Export: Export all tracks of a project as individual audio files, including all applied effects and routing configurations.
Optimized support for ARA plug-ins: Seamless workflow with improved usability.

https://www.muziker.ch/en/magix-samplit ... muziker.ch

But there was still some more - mainly a completely reworked audio-engine, if I am not hallucinating...