Re bb plugin development.

All.

I hope this post doesnt mean people will jump all over me..
and yes i think it's a great idea for the bb plug in etc.
i just think , pg shouldnt become over reliant on the bb plugin.
this post explains why.

let's talk about business strategy and the long term survival of pg to grow and prosper.

some background.

ive seen in the past in tech companies whereby a critical part produced by someone else is incorporated in the tech companies product.
In summary the market is littered by companies that fell because they didnt 'row their own oar' and relied on a third party for success.

So how does this relate to the pg plug in ?
yep …everyone wants the plug in to operate with their own personal fav daw…totally understandable BUT there is a downside per the example i gave above re tech companies relying on third parties…viz..

Now pg developers have to worry about not just imposed os changes and impacts on the plug in but also maybe the daw itself changing that the plug in is interfacing with.
so things might evolve whereby pg developers are in constant 'react mode'
using lots of pg developer resources due to things outside their control ... such has felled many a good company in the past. for example there is a new plug in format emerging and being adopted by some daws…ie CLAP.
to support it more resources will be needed if CLAP becomes dominant.

In summary…from a strategic biz perspective and long term survival of a company there are dangers in 'putting all one's eggs in one basket'.
cos if the basket changes…the implications are obvious etc etc.

Here's an example small biz study on why relying on factors outside one's control can lead to problems.
years back i knew a family that operated a thriving restaurant in a busy tourist region in england.
For years the business had provided a decent living for the family. (no great riches…just a living.).
for years the tourist buses stopped at the bus stop outside the family restaurant which was always busy. until one day the powers that be determined to move the bus stop. and you can guess the rest..the family lost a decent living cos the buses didnt stop outside the restaurant anymore.

In summary, given the above…yep develop the plug in further…
but all i'm suggesting is dont rely on it…because then pg becomes in a 'master slave relationship' whereby a third party, the master can impose conditions on the slave so the slave is in constant react mode.
and thus chew up valuable development resources.

in summary i feel strongly that pg's long term survival (from many case studies ive seen in industry) should not just be tied to third parties but also pg should 'do their own thing' and 'row their own oar' also in their product development.

should anyone doubt what i'm saying just look at case studies why some companies failed in the past due to reliance on third parties.
its no cakewalk being solely a plugin developer.

let the rotten eggs start flying…lol.
seriously…my concern is for the long term survival of pg ... .so us musos will continue to get nice new features in pg's music software apps.

happiness to all.

om

Last edited by justanoldmuso; 11/12/23 07:05 AM.
my songs....mixed for good earbuds...(fyi..my vocs on all songs..)
https://soundcloud.com/alfsongs
(90 songs created useing bb/rb)
(lots of tips of mine in pg tips forum.)