datho.
ive given this much further thought/your needs and other users needs from a computer engineering aspect as follows.
NOTE : I MIGHT BE COMPLETELY WRONG HERE.
but i find it interesting that other 2021 users arent haveing similar problems.
please follow my logic.

1. i am aware that some/many studios use higher end interfaces like rme for higher recording and sampling rates eg 24 bit // 96khz.
2. given point 1 and the fact that biab likes 44.1/16 bit
is this a possible source of problems/conflict/crashes ?

datho ; there is another aspect. from a computer engineering aspect.
i suspect from this standpoint that a NORMAL DAW THAT DOES NOT HAVE AUTO ACCOMPANIEMENT FUNCTIONS IN IT ; it is easier to support users needs/functions for HIGHER BIT DEPTHS AND SAMPLING RATES.

REMEMBER BIAB IS A UNIQUE PROGRAM. THUS i suspect if pg built in all sorts of supports for multiple sampling rates up to 192 khz PLUS multiple bit depths. this might realise not only a more bloated program...
BUT THERE IS ALSO ANOTHER MAJOR IMPLICATION.
remember the GENERATION OF REAL TRAKS PROCESS is building complete real traks from stored "snippets". its doing this in probably what some might term "look ahead" methods. ie building buffers of audio before they are needed.
A DAW DOES THIS TOO ! BUT IT DOESNT HAVE THE ADDED WRINKLE OF AUTO ACCOMPANIEMENT FEATURES AND GENERATING REAL TRAKS.

also datho if pg implemented multiple bit depths and sampling rates i suspect the real traks library would be HUGE.
which has user implications downloading in the future.
the download time would multiply and frustrate users.
lets take a piano RT it would have to have been recorded originally in multiple bit depths and sampling rates up to 32 bit 192 khz ?.
(pg can tell me if i'm wrong on this point.)

see what i mean ?
in conclusion it is too simplistic imho to expect biab to support all sorts of bit depths and sampling rates because there are software engineering implications down deep in the code.
if this stuff were trivial datho you would see many more biab competitors like there are many daw multitrak competitors .(Ptools/cubase/reaper/mixcraft/cubase/samp/nuendo etc etc.)

(now MIDI is a whole different story being just data.)

if i'm correct about the above datho from a software engineering standpoint THEN the pg software engineers are in a catch 22.
i am sure they would like to fulfill everyones desires for more than 44.1/16 support BUT they realise the complex implications.

maybe someone from pg will say "muso is out to lunch" and we can do that. lol.

in the interim datho it would be helpfull if you posted the following pics (otherwise the rest of us are guessing.)
.pics of your rme audio settings.bit depths and sampling rates.
.pics of your biab audio and midi driver settings.
.pics of your other music daw settings/bit depths/sampling rates. ie cubase and mixbus etc.
.pics of your win recording and playback bit depths and sampling rates

thus the rest of us plus pg simon who has rme can have a gander.

LET ME CLOSE IN ASKING DATHO ARE YOU USEING RATES HIGHER THAN 44/1/16 IN YOUR OTHER MUSIC SOFTWARE.


wishing you only the best.
i-think-rme-is-great-gear-oldmuso-an-ex-tech
ps maybe i'll get egg on my face lol.

Last edited by justanoldmuso; 05/27/21 04:54 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.)