Samplitude Pro X opinions

[Muziksculp]

@Hink,

Thanks for the additional feedback, and video tutorial link.

Cheers,
Muziksculp

[Hink]

@Hink,

Thanks for the additional feedback, and video tutorial link.

Cheers,
Muziksculp

seriously though...what am I'm missing?

[siriusbliss]

@Hink,

Thanks for the additional feedback, and video tutorial link.

Cheers,
Muziksculp

seriously though...what am I'm missing?

The 'block' approach exists in Samplitude /Sequoia - it's called Revolver tracks.

Arrange and re-arrange objects to construct a song.

Using Revolver tracks along with Take Composer, hotspots, etc. gives Samplitude users the same features as blocks, but with the added object-editing features.

G

[Hink]

@Hink,

Thanks for the additional feedback, and video tutorial link.

Cheers,
Muziksculp

seriously though...what am I'm missing?

The 'block' approach exists in Samplitude /Sequoia - it's called Revolver tracks.

Arrange and re-arrange objects to construct a song.

Using Revolver tracks along with Take Composer, hotspots, etc. gives Samplitude users the same features as blocks, but with the added object-editing features.

G

I already do that

[memyselfandus]

the main feature of blocks is to have another screen(multiple blocks-multiple screens)dedicated to composing and sketching out parts somewhere else.. outside of the main project and then bringing multiple blocks into the main project.





it would be Amazing to see a good video of this "blocks" type workflow in samplitude. even if it's not exactly the same. I am guessing lots of people would love to see this.. and would use it if they knew about it.

[Hink]

the main feature of blocks is to have another screen(multiple blocks-multiple screens)dedicated to composing and sketching out parts somewhere else.. outside of the main project and then bringing multiple blocks into the main project.

I must still be confused because I can do the same things without having to go somewhere else, just seems like a whole lot of extra steps if you ask me. But each to his own, I want for nothing when it comes to workflow.

[Muziksculp]

I think Blocks in Reason offer an easier, and more organized method of arranging your composition, and having more flexibility to edit the arrangement order in a consolidated window, which helps in experimenting with various ideas fast, and in an organized manner, also have the option of having multiple ideas/arrangements in the same project recalled with a mouse click. I feel this is a very valuable tool to have, in any DAW, since it gives you a good overall picture of your arrangement's sections/parts, in a consolidated window, not cluttered in your main arrange window, or in samplitude's VIP window.

i.e. Cubase offers the Arranger Track, which is very useful as well.

I will check out the revolver tracks, and try to see how I feel about using them, and some of the other features mentioned to organize/arrange a composition.

Cheers,
Muziksculp

[Hink]

Thanx for taking the time to clear it up...

[Sequent]

Meanwhile, I hope to demo this further as soon as I can get my vst's to work in it. It appears to be very problematic trying to get Samplitude Pro X to do a proper scan. It seems that just about everything has to be re-authorized, even though it's working perfectly in other hosts. I had to re-enter serial numbers, re-install iLoks, re-install e-licensers, etc., etc. and a couple things don't even show up at all. A bit of a nightmare to say the least! As I said, even though everything is working fine in other hosts. My iLok and e-licenser drivers are (and were) all perfectly up to date. Back to the 'drawing board' tonight. Still looking to this as an alternative to Cubase, but we'll see.

One thing that does impress me so far is that it seems like it's much more efficient in terms of using resources than some of the alternatives. Cubase in particular seems to be awfully bloated and requires a LOT more memory just to start it up and with nothing running. Whereas Samplitude uses just a fraction of the resources. So, that's a big positive so far.

[Hink]

Meanwhile, I hope to demo this further as soon as I can get my vst's to work in it. It appears to be very problematic trying to get Samplitude Pro X to do a proper scan. It seems that just about everything has to be re-authorized, even though it's working perfectly in other hosts. I had to re-enter serial numbers, re-install iLoks, re-install e-licensers, etc., etc. and a couple things don't even show up at all. A bit of a nightmare to say the least! As I said, even though everything is working fine in other hosts. My iLok and e-licenser drivers are (and were) all perfectly up to date. Back to the 'drawing board' tonight. Still looking to this as an alternative to Cubase, but we'll see.

One thing that does impress me so far is that it seems like it's much more efficient in terms of using resources than some of the alternatives. Cubase in particular seems to be awfully bloated and requires a LOT more memory just to start it up and with nothing running. Whereas Samplitude uses just a fraction of the resources. So, that's a big positive so far.

I had issues with the original avox with two or three pluggins not showing up, those exact pluggins did not show up in AA 1.0-2.0 either but they did show up in FL. I dont use those anymore, nor do I use anything my ilok is needed for anymore. With pro x the only nightmare I had (and it was bad) was with YT Indy, but the problem was my samples (the same exact ones) from earlier versions of indy would get seen, Magix sent me the boxed version with the full indy and all was set. I did spend an entire weekend downloading 70 gig of content the ended up not working though.

What pluggins are giving you are hard time? Perhaps Kraz or Greg can help

[Sequent]

What pluggins are giving you are hard time? Perhaps Kraz or Greg can help

Thanks... any suggestions are much appreciated!

So far, it seems the problems are with PSP Audioware (keep having to key in user name and serial number), Arturia (e-licensor not showing up), Novation (V-Station needs repeated re-authorization), GForce VSM (not showing up), Lexicon (iLok not showing up), Soundtoys (iLok not showing up).

I have several Arturia items, some are showing up some not. I also have some Sonnox stuff (on the same iLok as the Lexicon and Soundtoys). The Sonnox stuff seems to be fine. I also have Synthex from Xils Lab on the same e-licensor as the Arturia stuff and Synthex seems to be fine.

I think what I'm going to do tonight is check once more (probably in Cubase) to make sure everything is working and to make sure it isn't some sort of Windows 7 issue. Then I'll have Samplitude Pro X re-scan my vst folder and see what happens.

Also... I just realized that I don't think that I ran Samplitude Pro X "as administrator" so maybe that is a big part of the problem - especially during the initial scan?

As I said, thank you for the help. I really want this to work and to see if perhaps Samplitude Pro X will be more efficient and have a better workflow for me.

[Kraznet]

I had to re-enter serial numbers, re-install iLoks, re-install e-licensers, etc., etc. and a couple things don't even show up at all. A bit of a nightmare to say the least!

It seems very odd that such problems like this should arise after doing a scan of your VST plug-ins folder. Although it might be worth running Samplitude as administrator and see if that makes a difference.

Samplitude as such doesn't have a plug-in manager. But if you go to the following path C:\ProgramData\MAGIX\Samplitude_Pro_X_Suite and look for a file called VstPlugins.ini it will show you a list of the plug-ins and usually the ones which aren't working I have a 4 next to it.
Another thing worth noting is if you have your plug-ins in folders this can sometimes be a reason for plug-ins not showing up and it may be necessary to adjust the "directory recursion depth" and "directory display depth". This can be done by changing the entry at the top of the ini. In fact what I normally do is use the following settings:

DirectoryRecursionDepth=2
DirectoryDisplayDepth=2



If you have folders within folders you may need to set it to 3 & 3.

I also find it a good idea once you've made this setting to delete all the plug-in entries below and save the ini. Then when you re-open Samplitude it will do a rescan and the folders will be recognised. Yes it is a bit of a pain and hopefully they will improve VST plug-in management in a future version.

Regards
Kraznet

[Sequent]

@Kraznet, I think you may have hit the nail on the head. I won't quote back your post, but I think it very well is my folder structure, so I will try the "directory" adjustments you mentioned.

I have my vst folder divided into sub-folders organized by manufacturer and further organized by name of instrument/effect within the manufacturer folder. So, it sounds as if that might be my problem indeed.

Thank you!

[jazzimprov]

Have you already tried running the Samp exe as "admin"

I seen before where some wierd issues were resolved with this.

If it works you can set it to always "run as admin"

[Sequent]

I have tried running "as administrator" and with Kraznet's suggested directory depth adjustments. I set the folder settings to 3 just to be safe. So far so good. I almost managed to make it through the "A's" before it crashed, so it seems that 112DB, Arturia, and AAS items scanned okay. Each time it crashes and I try again it seems to go a little farther along.

I will try once more tonight and over the weekend.

Thank you to everyone for your help!

Have you already tried running the Samp exe as "admin"

I seen before where some wierd issues were resolved with this.

If it works you can set it to always "run as admin"