ZincT

4 hours ago, Zo said:

Guyz can inupgrade even if i don t own it padshoo yet anticipating cibase pro purchase ?

My guess is that you could buy the PadShop Pro upgrade license now. You just won't be able to use it until you buy Cubase Pro which includes Padshop or buy Padshop separately.  

6 hours ago, Tiger The Frog said:

Upgrade from Padshop to Padshop Pro is $9.99.

Upgrade to "Full version" is $34.99 and includes the Zero Gravity Instrument Set (normally $29.99).  So you'd save $5 with this bundle!

But if you waited for the sale you can get the Padshop Pro upgrade + Zero Gravity for $24.99.

 

Thanks TTF.

Do you have Zero Gravity and is it any good or any of the other Padshop expansions?

Chordpulse is a good and cheap alternative and there's a free 14 day trial.

Nowhere near the number of styles or complexity of BIAB but quick and easy to get decent results and you can export the MIDI for import into your DAW.

http://www.chordpulse.com/ 

A couple of others which I haven't used but may be worth a look...

Impro-Visor -- https://www.cs.hmc.edu/~keller/jazz/improvisor/ 

Musical MIDI Accompaniment - https://www.mellowood.ca/mma/ 

There are also quite a few IOS apps with this kind of functionality if you have access to a suitable device (iPad etc): Chordbot, Chordmaps2, Navichord, Suggester, AAccompanist, Chordbud, Odesi, Session Band and a load more I have probably missed.

Thanks Amicus. I bought micro but the email I got tonight tells me all about Elements but I don’t see a voucher anywhere. I also checked my Soundiron account.

I will email Soundiron and see what they say.

20 minutes ago, husker said:

Zinc - I don't seem to have it either.  I don't have the .vstsound file - all I remember is I paid $10 to upgrade to PadShop Pro.  Maybe that upgrade didn't include it....

Thanks for confirming husker. Yes I paid the same for the upgrade. 

The Zero Gravity expansion says that it is included with PadShop Pro but I think it must be in the full retail version as I don't see it in my version (I upgraded to PS Pro from the version included in Cubase Pro).

Does anyone have it and have any opinions?

Thanks

Expand your musical horizons with our 50% summer discount

Expand your musical horizons with massive savings on Groove Agent, Retrologue and Padshop expansions

Our summer sale brings you a wealth of new beats, grooves, drum and percussion sounds, granular synthesis, classic fat analog synths and basses at a spectacular 50% discount. Like the breath of a cool summer breeze, let Groove Agent, Retrologue and Padshop inspire fresh new ideas with a wide range of excellent expansions.

Take advantage of this great offer by entering the coupon code SUMMEREXPANSION at checkout. But hurry — it is only valid from July 8 to July 22, 2019.

https://www.steinberg.net/en/promotion/expansion_sale.html 

Good find abacab! 👍

Like others, I always deselect everything except 64bit VST on installers but I also had 2.5Gb of worthless content there cluttering up my SSD.

Not any more!

So sad to hear of your loss. You are in my thoughts and prayers this morning. 

I have now setup the same ST4 patches in both CbB and Cubase versions of my MIDI song and I now also get CPU thread 0 spikes and glitches in Cubase.

I have tested the patch save problem which I can also replicate in 4.0.5.

I also just tested the repeating MIDI note problem and can also replicate it. I drew some notes in the PRV which play fine on Arturia Piano V2 but repeated notes are missed on the ST4 C7 Grand Cinemantic 1 patch.

Roll on 4.0.6 indeed Promidi! Let's hope it is tested a bit more thoroughly before release. Maybe they should release beta versions for end users to test before releasing a "final" version. 

2 minutes ago, abacab said:

Were you running multiple instruments within a single instance of ST4?

Yes, the same as I was in CbB. The only difference was the selection of instruments but they were still drums on  ch 10 and various synths on ch 11 to 15. I will try it again with the exact same instruments in both. 

1 hour ago, abacab said:

I am definitely seeing that CPU max in both ST4 standalone and plug-in mode, and I have confirmed it with Ableton Live and Studio One, in addition to CbB. So IMHO it's apparently an IK thing.

I am fairly certain that the high CPU usage is an issue with the new ST4 instrument engine, as I can load up the ST4 interface with ST3 instruments that use the legacy ST3 synth engine, without overloading the single thread.

So I think that SampleTank has always been single threaded, just that it was not that noticeable in the past. Even if they could update ST4 to share cores, not sure that would benefit beyond the standalone product, unless the DAW could support a plugin that shared multiple cores from a single instrument track.

 

 

Thanks for confirming this abacab. I agree that it was not noticeable in older versions and I see your point regarding sharing cores from a single instrument track.

Oddly I have just tried recreating the problem in Cubase Pro and it plays fine with all cores running evenly. I cannot find a CPU usage meter in Cubase like the one in CbB so I was using the Task Manager performance view with the graph displaying logical processors.  

Got it this time and the Dope freebie.

Cheers Larry.

24 minutes ago, Promidi said:

Just a note that I think I may have found an issue with Sampletank 4.05. 

Saving instruments appears to be broken.  It creates files that cannot be subsequently reloaded on the next session. Instruments saved with 4.04 load ok, just not ones saved with 4.05.

Can anyone with Sampletank 4.05 verify this?

Thanks for the heads-up Promidi.

I will check that issue when I have a moment later but for now the main issue I have with ST4 is the apparent lack of multi-threading support.
This has not improved with version 4.0.5. I have a MIDI project currently which uses ST4 with drums on Ch 10 and various instruments on channels 11-15.
It's not a particularly busy project but thread 1 of 8 on my CPU is maxing out and causing audio dropouts. I understand others have found a workaround which is to use multiple instances of ST4 for each part but that seems like a cludge for what is supposed to be a multi-timbral instrument. I have been impressed by CbB's ability to load spread across CPU threads so I am pretty sure that it's not an issue with CbB although I will try it with Cubase, Studio One Pro 4 and Reaper when I get a moment. 

Thanks for the heads-up TS.

I did finally go for Pigments at 69 EUR for the crossgrade.

Not had any blank GUI issues with the demo either standalone or in CbB (I am running the latest version).

53 minutes ago, balinas said:

Is it correct to assume that I need only download the SampleTank4.0.5.zip, Cuban Trumpet sound content.zip, and the  ST4Max Sound Library Update1.4.zip?

That is what I assumed although I haven't installed the update yet (on my to do list for today).

Updated to reflect latest version. 

Details here... 

SampleTank 4 - Ver. 4.0.5 - Release Notes

Changes from version 4.0.4:

• Added Tooltip display when hovering over the main bar icons
• Added assigned note info for instruments with multiple articulations
• Improved smooth scrolling in Library browser
• Selecting “Load Instrument” now focuses on the corresponding Part number
• Optimized character limit for Part/Note value input in virtual pads
• Loading Syntronik Multis now remove previously loaded instruments on Parts 5-16
• Fixed built-in Mod Wheel not sending MIDI CC values to assigned MIDI correctly
• Fixed an issue with Pads Mode not reacting properly after recalling saved project
• Fixed an issue with Auto Pan potentially affecting audio when depth set to 0
• A Sound Library Update 1.4 is available. This adds new Brass and Woodwind instruments with key-switchable articulations and fixes an issue with Trombone 2 Staccato not installed properly (available for ST4 MAX and Standard only)
• Added a new key switch articulation instrument: Cuban Trumpet (available for ST4 MAX and Standard only)

I also decided to hold out and my Jampoints today have dropped from 194 to 160 so I guess it wasn't all of them that were due to expire today. 

Cheers Larry!

Got Townhouse this time (10.80 USD or around 8.50 GBP inc VAT) and Shredspread for free on Wednesday.  Noice. 

New video on MODO Drums...

Nice!

That sure is a deal for someone! Good luck husker.

39 minutes ago, Matthew Sorrels said:

Cubase normally doesn't blacklist the VST2 version of VST3 plugins, unless they are 32-bit plugins, which is the most common reason for the blacklisting (the other common reason is the DLL isn't a vst plugin at all, like for example all the iZotope support DLLs). 

In the case of MassiveX I think it got blacklisted because all my NI plugins take a long time to scan (most likely because I have too many of them).  Cubase 10.0.30 seems to have a lower timeout value for VST scanning than earlier Cubase 10's.

Thanks Matt. I am still on 10.0.20 awaiting a fully working update for ARA2 btw.

My NI plugins scanned quickly. but looking at my blacklist there's the odd 32bit plugin like Dropzone and Square and I try to keep 32 bit stuff off my PC although some installers don't make it easy. The others are mostly iZotope 64bit VST2 plugins of which the VST3 versions are not blacklisted.  TH-U 64 bit VST2 is also blacklisted which I think was due to a timeout. 

4 hours ago, Matthew Sorrels said:

... Oddly enough Cubase blacklisted it on startup for me.  Had to go re-enable it.  Maybe there is more to it, but my at first glance is it's kind of boring.

 I haven't tried it in Cubase yet but will give it a go. 

EDIT: Just tried it in Cubase and the it scanned OK.  However, I did just discover that Cubase seems to have blacklisted some VST2 plugin that also have a VST3 alternative. Is that normal behaviour?

Just going through the "best of" bank and it sounds tremendous-ly familiar. 😉Edit : have now been through most of the patches but expected more in some of the genres. Maybe they will release some more banks soon. Found one or two nice patches but couldn't help thinking that we've heard it all before. Some of what's on offer looks interesting and I will have to look into the performer module or whatever it's called. My cpu is Ivy Bridge so it's ok with AVX 1 but not AVX 2. 

CPU load seems reasonable -haven't seen thread 1 go much above 4% yet.