Originally Posted by Bass Thumper
It's been one week since our White Paper was shared on this thread and because of a hijack, much of this time has been wasted with many of us frustrated.
It's possible that collectively, hundreds of person-hours have been spent reading, thinking and responding to the hijack.

Can we all ignore the hijack and return to the original purpose of this thread?

Regarding the paper:

What did we get wrong?
What did we get right?
What could be improved?
What did we omit?
The White Paper did a good job of showing different user communities having potentially different purposes and requests for the tool.

It could have gone into more details about certain weaknesses such as workflow which is hundreds of small things small things about consistency.

It could have gone into more detail about why old and new ways to do the same thing is not good. BTW, having 5 different ways to get to the same code is a good thing. 5 different ways to get to 5 different versions of the same idea is a bad thing.

It could have gone into more detail about modern software using panels instead of modal dialogs. By the way BIAB already has several examples of using Docked Panels and just needs to replace all its modal dialogs with that approach. BTW floating dialogs are a generation before panels.

It could have gone into a little more detail about global and hierarchical aspects of the software such as the transport layer, the cursor, loop selections, and some very fundamental things found in any software that has to deal with editing things in a time frame.

Modern software uses vector-based graphics or at a minimum has 2 to 3 scales of graphics for people who are on large 4K screens versus laptop, so the graphics is always crisp.

It could have gone into more detail not just AI but about the pros and cons of a "Session Player" workflow concepts of which the competitors have 4 dynamic/smart ones and BIAB has 2900 live ones. It's two different approaches to trying to do the same thing.

Rest assured PGM has noted the white paper.
Look closely at the thread and you'll see a few of these ideas being brought up.
I would ask the community to engage in that input.
Embracing a Session Player
Hierarchy of Session players/instrument
Quicker ways to find your Session player

Last edited by jpettit; 06/05/24 12:47 PM.
Studio One (latest version), Win 11 23H2 , i9 -10940X 3.3 GHz, 32GB Mem, a 4K 40" monitor, PreSonus Studio Live III Console as interface/controller. secondarily test on Reaper, Cakewalk, and S1 on Surface Pro 3 Win 10 (latest versions).