Originally Posted by Rustyspoon#
"Nothing is broken, it's just not your workflow."

THAT ^ is the philosophy that kept BIAB from where it needs to be for many years. Workflow has to be universally accepted, adhering to existing accepted software standards as much as possible, not analogue hardware world.

Historically you were pushing back against many workflow improvements that were offered in wishlist section, silencing new voices of reason. But what really striking is that you don't really use the features you so desperately trying to steer away people from. If obscure workflow and endless workarounds to achieve something trivial bring certain satisfaction to you - that's you. There is no need trying to stop much needed progress.
------
What really should happen is strong backward compatibility of content. That way, those who like modal windows, endless pop ups, artificial limitations, ten step workaround that should take two, can happily use whatever version they prefer, yet get a discounted content upgrade. Core program update was only $50 recently. I want to see BIAB live on, not fade away.

Misha misunderstood the point. Nothing is broken. Neither the process or his workflow. That his only considered method of working with underlying RealTrack midi data was the Tracks View and the limiting factor for accessing the data, causing the necessity to erase the RealTrack. The process otherwise is just as he explains it. By modifying his workflow to expand beyond the Tracks View, all of the parameters he desires and listed can be accomplished using BIAB.

I demonstrated it in RealBand because the view, easy toggling, retaining the RealTrack for more regenerations and exporting to a DAW are all done in a familiar DAW environment and view. It can be done in BIAB rather than RB. Partial Regeneration (Ctrl-F8) is also available in the Chord Sheet, Notation and Piano Roll views and several different menus.

Working with two or more Windows open allows easy toggling between midi and RealTrack, editing from either Window and exporting the midi data without losing the RealTrack which can be used for as many additional regenerations, midi data editing or both. Every regeneration can result in edited midi data to be saved or exported to a Legacy, Utility Track, or external DAW track.

The singular workflow in the videos for accessing the underlying midi data results in having to erase the RealTrack, losing the opportunity for continuing partial or full regenerations and is avoidable.

Underlying midi data appears to be a new discovery for some. Factually, this underlying midi data dates back at least a decade. Underlying midi data can also be added to a RealTrack that doesn't currently have it. Underlying midi data can also be added to imported or live recorded audio tracks. This has been possible since at least 2014 in Windows versions of BIAB and my post wasn't to bury his idea but to expand the capabilities while avoiding losing the RealTrack. Also to introduce the fact that partial and full regeneration is possible from multiple screens. To inform that underlying midi can be visible, edited and exported without compromising the RealTrack.

Historically speaking, this is just the same thing again; Tell the Forum BIAB/RB can do something and the real pushback comes. I didn't speak out against Misha's suggestion but offered BIAB/RB alternatives that exist that were not acknowledged or mentioned. There isn't an indication in his videos or posts he was aware of alternatives. Only, without question for input, declared the process broken. Since that post, others have spoken up they were unaware also.

I previously recorded a short video demonstrating a view of the Tracks View window, Piano Roll window and RealBand in a single screen display. The screen shot expanded RealBand from the background but prior to the midi export to RealBand, Piano Roll and Tracks View could either be used for multiple Partial Regenerations, Full Generations, audio editing, midi editing, audio export, midi export, audio/midi export, playback from Piano Roll or Tracks View, and the two BIAB views had curser sync with the Tracks View used as Master.

Honestly, I was unaware I was in a 6+ year dispute and thought the RB DAW view, avoiding erasure of the RT, both midi and RT visible and toggleable might initiate a discussion and the above information could be shared with everyone. Guess it wasn't meant to be.

Attached Files (Click to download or enlarge) (Only available when you are logged in)
Screenshot 2025-02-04 153659.jpg (214.99 KB, 130 downloads)
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.