PG Music Home Forums PG Music Product Forums Band-in-a-Box for Windows How do I keep BiaB from changing my ASIO sample rate from 48K to 44.1K? [Resolved]

M and Gordon.weeeelll...lol..
(ive gone into a bit of detail in case potential new users are reading this topic.)

heres a perspective on things i suspect that are going on.
please feel free to tell me i'm a 'stupid A'....

1..in a typical daw there arent the same 'wrinkles' as bb.
one isnt comparing apples to apples. a typical daw isnt 'stitching together' bits from
a library of content...whereas...
2..bb is building tracks by 'stitching together' from a lib of content.

given the above if the content lib is set to a different sampling rate than the users preferred sample rate then obviously the added wrinkle is resampling routines right ?
this might lead to lag if the user is regenerating lots of tracks on a clunky pc ?
an added wrinkly is the driver technology and the users choice of interface which pg have no control over (same with the win OS.).

in summary for the poor app coder in some ways he/she is in a catch 22 due to limitations placed on he/she.

now what i'm wondering is how big the latency when regenerating oodles of tracks when the app doesnt have to resample the library content (cos sample rate is same as users set sample rate) versus when the app must resample cos the library content is a DIFFERENT sampling rate than the users sample rate set in preferences. so in the former case all is fine if content lib is 44.1 and user 44.1.
in second case content lib is 44.1k but users is 48k.
see what i mean ? does the resampling process introduce added latency due to the coder haveing to call up resampling routines ?

given the above we know that asio is lower latency than wasapi.
so the added wrinkle is what added impact does this have ?
as i said from my looking at things it seems that wasapi is fine for playback environments but asio beats it for recording.
also i'm wondering in conclusion if bb had oodles of tracks...lets take 38 for example to regenerate how much lag would be introduced whereby the users set sample rate was the SAME as the content lib versus when the users sample rate is DIFFERENT than the content libray <<< so resampling is needed.

i hope i make some sense.

Mr M. re reaps. hmm never given me a prob.
(actually i'm useing it less and less these days due to rb recent improvements.
i dont use bb plugin as rb for me has way more features. i just D n D from rb to other apps.
re Bitwig <<< interesting daw. particularly re the clap plugin implementation that apparently is better than vst ??. frankly i'm intrigued by some of the things that
multitrackstudio.com is doing includeing cross platform plus ipad support.
i really like how so many great features have been implemented within such a small
exe footprint. (btw what latency is reported for your new RME interface ?
RME is good kit. i'm very happy with audient (love the drivers) around 4ms asio here.)

happiness.

om