PG Music Home Forums PG Music Product Forums Band-in-a-Box for Windows Why doesn't PGMusic put out notices on what they're working in the next release?

Just about every other piece of software I use puts out blog posts or simple messages on what they are working on in their next release, which keeps everyone excited about what's in store for the next release, but when I come here, I see nothing like that. The last maintenance update was back in June, and all of the posts are about last year's release. I know a new release will be coming in December, but once again I leave the website uninspired about the future of Band in a Box. A little communication on what's being tested in the beta releases would go a long way to keeping people excited about the future.

Perhaps, the mystery of what new magic the good folks at PG Music are going to come up with is even more enticing than advance teaser posts.

Notes ♫

The beta testers are required not to disclose anything about the new features. And as you know, PG Music has never pre-announced.

I don’t have any major music software that does what you describe, so you must have other software than I do. I’m curious if you could cite some examples.

Those of us that are older will remember Vaporware. That was when software companies promised something but didn't deliver it. Even if what they did deliver was better than what was promised people still loudly complained that said feature was included. Thus companies stopped posting what was coming. Today some companies will disclose what is included in updates when the product is in the last beta stages.

I can just imagine what would happen if they did announce.............half the forum would be sayting 'that's not what we want at all'...............and the other half would be suggesting 'improvements'............then the complaints would come in that the new features are only availalble as a paid upgrade and other software often includes upgrades in lifetime licences.......i don't blame PG for keeping quiet

The fact that updates are so few and far between is, in my opinion, a testament to the great work the beta testers and BIAB programmers do to make a clean product. When there is an issue, in my experience, they are on it fast and resolve any problem users are having.

There is always the wish list page to make recommendations for future BIAB releases.

Personally, I'm always excited to see what new comes along and don't particularly need to know ahead of time. Focus on what's in hand and let Dr. Gannon do his thing. There are always plenty of surprises at the proper time.

Likewise, I don't blame them either for keeping things under wraps until release date. Not that I blame A_R for being excited about upcoming releases either. I just think it's better they keep it under wraps.

It would be a hot mess!

There will be plenty of time for all that after the new release!

Bull. Nobody in their right minds announces details about what they are working on.

I'm not familiar with any music software where the developer announces future functionality until the product is virtually ready for release.

Except just about everyone does, even the company who's software PG Music uses to create band in a Box does.

A_R give an example. If your talking about Delphi then hhhmmm maybe but that is apples and oranges. All a coding software releases is a few bug releases and a new feature or two. Only interesting to, well coders.

Music programs with vast user bases, I don’t think so. Presonus doesn’t Cubase doesn’t Cakewalk doesn’t, Protools doesn’t, Harrison doesn’t, Abelton doesn’t, No one I can think of. Maybe Reaper to a degree as they welcome the entire user base to get involved and play with pre-releases long before release. Kind of unique.

Not trying to be argumentative with you, but name one benefit to PGM for listing the new features and content prior to release?

Just another Thursday for Trevor so he is ready to test! No turkey day down undah! Just daily routine and a vegemite sammich for lunch! Wash it down with a Cooper’s dark ale!

I can think of a couple benefits right off the top of my head...

1) Engaging/creating user community, especially younger users (The Future!)

2) Gaining critical insights as to what users want (multi-riffs) and what they don't want (VideoTracks) before you invest all of your limited resources.

JJJ, They do listen to users hence the wish list forums. We can all post things that we wish would be implemented. Then they choose what to do and how to do it rather than endure constant badgering to take the program in multiple directions. Ones they know may not be possible at this time. It is what it is, it is up to PGM to decide how they run their business.

They have been rather consistent in the business model. So far it is working. You or I may do things different if we were in charge. You never know if we were we may make the exact same decision if we knew what they know. You have to admit that they are also in step with the majority of the Music software industry, which also keep things under wrap until they release.

I was a beta tester for 20 years for Encore, an early music notation software. They were bought out and the new owner let it languish. I converted to another program (and I’m a beta tester for them now too).

Last year, summer of 2022, the original developer of Encore bought the company back, announced detailed plans on a new website, and promised delivery in Fall 2022. Guess what? The website changed a few months ago to Fall 2023. Recently it changed to Winter 2023. All the while, they got hammered in the user forum for missing the announced deadlines. We aren’t anywhere near finding out whether the announced features will be implemented. What fun that will be if they aren’t.

Is that what is being requested?

Bull.

How about some evidence to support your unsubstantiated claim?

A lot of the Add-on suppliers do, I constantly get spam with emails and newsletters of what they are working on, Positive Grid is one I can think of off the top of my head which does it. I don't see the big deal of allowing customers to have a road map of where things are going, I like knowing if it's moving in a direction I want to invest my time in

Why are you so angry? There is no need to get so emotional about this.

A_R you are correct there is no need to get angry or upset. It's just software. I see your point. I think a good thought it that BiaB is not a scaler, or ezkeys or positive grid, even a Studio one or reaper. it is a 30 year old program that has feature that encompass a lot of ground and goes in a lot of direction. It is not a plugin or actually a DAW in the strictest sense, it is an auto accompaniment program that has multiple layers of capability. It is now days a slow growth like an old oak. They are unlikely to rewrite the program using newer code as it would upset the revenue cycle. For what it is worth there is a lot of emotion attached to the old gal. Folks here get passionate about it. Many have decades of usership. I've actually been here 20 years. So you question is not a bad one, but unlikely to ever happen.

Imagine if they posted all the new features and fixes, then took the time to answer every question, suggestion, and response that would develop from that post. Imagine how many different "I think you should do this or add that" it would cause. There are folks here with deep attachment to many other programs, that would love PGM to go their direction. Some are midi people, others music teachers, some recording studios, still others hobbyist, some do loops, some real tracks and on and on. Each with a unique workflow, and maybe a unique DAW they finish projects in. Some want it to mirror the newer DAW programs, others would like it to remain old school and neither see the other sides views.

They added the wish list forum a few years back so everyone can post their thoughts, and I can tell you they do listen, but having met Peter on two occasion at online events, he does not want to open it up more as the release cycle for windows and mac are brutal and it takes all year to get done what they do.

People constantly post regarding they should just stop and rewrite for a year, or use this code source, or try this or that. The problem is those comments while coming from sincere folks that care, they simply do not know what goes on behind the screen, and what it would take to make those changes. It's easy to play Monday quarterback, when you are not the one throwing the ball.

Anyway, good question, and sorry it gets heated sometime. Please continue to offer ideas, and suggestions.