HG Fortune: ProtoPlasm released! Was: prototype VSTi-free

VST, AU, AAX, CLAP, etc. Plugin Virtual Instruments Discussion
Post Reply New Topic
RELATED
PRODUCTS

Post

OK - now I understand. If you're not sure what's being asked then try http://babel.altavista.com/ for a helpful (and always amusing!) translation.

Regards,

Derek.
Less than 1000 posts and writer's block has set in :-(

Post

JackD wrote:I purchased ProtoPlasm and am very happy with it. One thing I've found is that many of the parameters respond to MIDI cc messages. I've made a list, but it is too long to post here. I've also got a RemoteXX template for ProtoPlasm.

thanks to jackd for settin me up with that :D
works lovely
:ud:

Post

Derek up North wrote: Regards,

Derek.

P.S. STS-21 ?? tell us more!
Well,
- the transition mode has been reworked and now there are two different modes for transition.
- each filter has it's own ADSR EG
- streamlined the system for better efficiency and even could optimise CPU-usage

cheers
HG

Post

Anybody using protoplasm in Ableton Live? Protoplasm fills Live's undo buffer with parameter changes, making undo useless. Is there a workaround? I think I need to turn off those blinking LEDs....
Close call glad I noticed this: I was just about to buy Protoplasm. Woulda been a waste cuz' I couldn't use it: I depend on Ctrl-Z a lot!

Post

djastroboy wrote:Anybody using protoplasm in Ableton Live? Protoplasm fills Live's undo buffer with parameter changes, making undo useless. Is there a workaround? I think I need to turn off those blinking LEDs....
Close call glad I noticed this: I was just about to buy Protoplasm. Woulda been a waste cuz' I couldn't use it: I depend on Ctrl-Z a lot!
Confirmed - same here :cry:

Post

djastroboy wrote:Anybody using protoplasm in Ableton Live? Protoplasm fills Live's undo buffer with parameter changes, making undo useless. Is there a workaround? I think I need to turn off those blinking LEDs....
Close call glad I noticed this: I was just about to buy Protoplasm. Woulda been a waste cuz' I couldn't use it: I depend on Ctrl-Z a lot!
Ok, I have a look into that.

You've got a pm

HG

Post

ok, thanks to djastroboy's crosscheck on a testitem this could be solved ... an update of ProtoPlasm should be out soon.

cheers

HG

Post

djastroboy wrote:Anybody using protoplasm in Ableton Live? Protoplasm fills Live's undo buffer with parameter changes, making undo useless. Is there a workaround? I think I need to turn off those blinking LEDs....
Close call glad I noticed this: I was just about to buy Protoplasm. Woulda been a waste cuz' I couldn't use it: I depend on Ctrl-Z a lot!
It is a problem that happens with many plugs in Live. Tell that to ableton, they know about it and will fix in the future, -how soon depends on customers, so complain about it, please.... I did...:)

Post

Fortune wrote:ok, thanks to djastroboy's crosscheck on a testitem this could be solved ... an update of ProtoPlasm should be out soon.

cheers

HG
That would be cool.... you are talking about auto-oscillating parameters in Live?

Post

waveriderarts wrote:
Fortune wrote:ok, thanks to djastroboy's crosscheck on a testitem this could be solved ... an update of ProtoPlasm should be out soon.

cheers

HG
That would be cool.... you are talking about auto-oscillating parameters in Live?
not really, probably their VST(i) integration (esp. Automation) is not as 100% compatible as it should be.

cheers
HG

btw. the update is done, the registered Pro version is already available via Paypal, via Shareit probably tomorrow - the free version will be available in a few days.

Post

waveriderarts wrote:
djastroboy wrote:Anybody using protoplasm in Ableton Live? Protoplasm fills Live's undo buffer with parameter changes, making undo useless. Is there a workaround? I think I need to turn off those blinking LEDs....
Close call glad I noticed this: I was just about to buy Protoplasm. Woulda been a waste cuz' I couldn't use it: I depend on Ctrl-Z a lot!
It is a problem that happens with many plugs in Live. Tell that to ableton, they know about it and will fix in the future, -how soon depends on customers, so complain about it, please.... I did...:)
Yeah I'll get on 'em. Is anyone compiling a list of these anywhere?

Post

Fortune wrote: not really, probably their VST(i) integration (esp. Automation) is not as 100% compatible as it should be.
So you think that Live's undo buffer should be able to distinguish between when I manually alter a parameter vs. when the VST alters it's own parameters?

Post

djastroboy wrote:
Fortune wrote: not really, probably their VST(i) integration (esp. Automation) is not as 100% compatible as it should be.
So you think that Live's undo buffer should be able to distinguish between when I manually alter a parameter vs. when the VST alters it's own parameters?
That would be the best way. Well after having found the workaround for that and thought a while about Live's general concept I think that could hardly be done. Now it seems to me their undo is some kind of 'floating' concept i.e. grabbing all changing/changed data for a certain period of time til the buffer is filled and then removing oldest when new data come in. Basically not a bad solution. Otherwise one might have to set a snapshot point manually for each undo step. But anyway this could be an option to be selectable.

cheers
HG

Post

i just purchased Protoplasm and i think it is outstanding. the only trouble i'm having is going through the patches, which at the current rate, will take me a couple of years -- since each brings its own new explorations and rewards. so far i'm thinking that the sounds can be categorized under these labels (if i'm missing any, please let me know):
1. Lush, dense atmospherics, soundscapes and pads.
2. Leads (solo parts).
3. Rhythmics, sequences and motion (ones with a discernable beat synced to MIDI tempo).
4. Drones.
My question is, has anyone grouped the patches so one could go through one or the other quickly and pick the one that's best for the job?
thanks, rob

Post

rwright999 wrote:i just purchased Protoplasm and i think it is outstanding. the only trouble i'm having is going through the patches, which at the current rate, will take me a couple of years -- since each brings its own new explorations and rewards. so far i'm thinking that the sounds can be categorized under these labels (if i'm missing any, please let me know):
1. Lush, dense atmospherics, soundscapes and pads.
2. Leads (solo parts).
3. Rhythmics, sequences and motion (ones with a discernable beat synced to MIDI tempo).
4. Drones.
My question is, has anyone grouped the patches so one could go through one or the other quickly and pick the one that's best for the job?
thanks, rob

well...thats why I tend to classify my patches according to type at the beginning of the patch name.

The above could be broken down to this:

PAD
LED
RYM
DRON

example: PAD Hyperspace TC

If the patch is renamed, and saved as FXP using MiniHost, then you can create a bank with all the types of pads, ect together using MiniHosts preset manager.A big job howver, so it's up to the user.

Post Reply

Return to “Instruments”