Originally Posted By: Icelander
Originally Posted By: Charlie Fogle
Since PhillyJazz can make this work all the time and exports his midi track to a DAW (RB) to manually edit the patch #'s, is Realband necessary to be the DAW? Why wouldn't any sequencer/DAW work to edit the file to change patch #'s?
You make a very good point there. I really need to get a grip on this "we don't have RB" complex of mine, eh wink


I never gave thought to you having a complex but viewed the situation as a workflow issue. I've on occasion come across something that should be a simple task and not be able to either figure out how to do it or if it is available to do in RB. Quicker to do it in another DAW, especially if there is no regeneration of a track to do.

This leads to my thoughts on your last statement
Originally Posted By: Icelander
Yes, there is of course always the "take it to daw" workaround for pretty much anything. But this to me counts as taking the long route, which I generally think works against PG's interests (not to mention being cumbersome for the user). This one at least seems like something they could resolve, more like a mere oversight of some sort.


I've concluded over time BB considers moving to a DAW more of a workflow circumstance than a workaround circumstance. To me, the fact PGMusic developed the DAW button and drag/drop protocols, indicates they do not consider BB to be a DAW and concede that it makes for a better workflow to move tracks to a DAW of choice for further processing and continue to develop BB as an audio/midi generating software. I use RB as much as I can but I have other software that accomplishes some tasks more efficiently.

Charlie

BIAB 2025:RB 2025, Latest builds: Dell Optiplex 7040 Desktop; Windows-10-64 bit, Intel Core i7-6700 3.4GHz CPU and 16 GB Ram Memory.