I've tried to record some audio in 2022, but I have encountered a problem whcih I've never experienced before. When recording a second audio take, your previous recording won't get muted.

To replicate:

1. Open / create a song
2. Click on "Record audio", use standard settings (see attached image)
3. Record some bars > Stop > OK Keep take
4. Press Play > Your audio will sound as expected
5. Repeat step 2 to record a second take.
6. Problem > The previous recording will sound while you're recording

I have tried with WAS, MME and ASIO drivers, but no luck, and "Overdub underlying audio" is un-checked.

Am I missing something? Can anyone replicate?

Thanks!

Two questions:

Are you recording to the same track each time?

Are you disabling "Retain Audio Past Recording"?

Yes, I'm recroding to the audio track each time. Enabling / disabling "Retain audio past rexording" doesn't make any difference.

Does recording a second audio take work as expected for you?

The second time you record do you leave the button default at "Record From The Start" or change the button to "From Bar #" and then enter the bar number to start from?

I normally do not record in BiaB however I created two test recordings to accurately respond to your question.

Test # 1 I left the button at default. I created two four bar recordings. The two recordings were merged into one recording that was four bars long.

Test # 2 Recording 1 I left the button at default. Recording 2 started at bar 5 of chorus 1. The two recordings played one after the other.

Band-in-a-Box treats test 1 as a sound on sound recording and test 2 as punch in recording.

Thanks Jim!

Yes, for the second take I leave the default options (Record from the start).

On your test #1, I suppose you had "Overdub underlying audio" activated for the second take, isn't it? In that case, I would expect to hear the previous take as reference when recording, of course. But if that option is deactivated, recording a new take while you're hearing the previous one is definitely not what I would expect in any audio program, since it makes the recording process virtually impossible

After I recorded bars 1 to 4 I heard my first recording during playback. During the first test, bars 1 to 4 were recorded both times and my second recording was merged with the first recording. During the second test I listened to bars 1 to 4 as a lead in to my second recording and the second recording did not start until bar 5.

Notice my "Overdub during playback" checkbox is grayed out so I can't select it. I suspect that is a response to the audio interface and may vary from interface to interface. In my tests I was using a USB gaming headset with microphone and headphone capability. It is not unusual to both listen and speak at the same time while gaming.

Sound on sound use to be a common technique. The technique was invented by Les Paul in 1949 +++ Les Paul Sound-On-Sound +++. He is the only person that's in the Rock & Roll,Country and Inventor Hall of Fame.

For a fun little sound-on-sound test try recording a count of 4. Only record the numbers 1 and 3 the first pass and the numbers 2 and 4 the second pass. Do you stay on the beat? Are the two recordings equal in volume and tone? It's more difficult than you think until you become proficient but it can be done.

Other users have reported exactly the same problem with MIDI, it looks like a bug:
https://www.pgmusic.com/forums/ubbthreads.php?ubb=showflat&Number=693151#Post693151

MIDI appears to be somewhat problematic in 2022.

I did respond to the audio recording question in the thread you linked to. I suspect in that thread the user is wanting to use punch in recording. The settings for punch in recording defaults to 1 bar before the chord sheet starts.

The punch in recording text boxes are unlabeled. From left to right they are chorus, bar, beat and tick.

Two words! Real band.

I’m not trying to be difficult but while BiaB can handle basic recording RB does it with style. And hey it’s free! Oh yeah it opens up BiaB song files.

And Mac users don't have access to RealBand so it is not a solution for them.

Yeah, Jim you right about that I have 2021 on my Mac. 2022 on my win 10. Right now while 2022 is still percolating I do most serious projects on the Mac. I also use Studio one on the Mac as well, and the plugin is solid there. I can’t wait till the new features are in Mac as well cause the multiriff is awesome so far.

While I don’t use RB much anymore I do suggest those new to BiaB who want to “stretch out” their project, RB is a great companion.

I've tried RB in the past, but it didn't work for me. I've used Reaper for many years and I also don't pretend to use BIAB as a DAW, I'd just like to record my instrument with BIAB while I'm practising at home from time to time, that's all. This is basic functionality, but it seems to be broken with this new version.

By the way, this is not the only issue I've found when recording audio in 2022. This feature used to work reasonably well with 2019, but it's a little bit unstable (at least in my system) with 2022.

Hello Cerio,


This is working as you describe, and I think that it is working correctly and as intended, unless I'm missing something.

If you choose to "Take Again" at the end of recording, the recording is discarded and you do not hear it during your second take. If you choose to Keep Take, you'll hear the audio data if you record again. If you chose to keep the take and don't like it, you can click on the track | Track Actions | Erase. Alternatively, if you want to do a few takes and choose one later, you could mute the track and record to a Utility track. It is possible that it works slightly differently than 2020 and earlier in this respect. For one thing there weren't additional audio tracks to use.

Hi Andrew, and thanks very much for responding. Yes, I've just tried and 2022 works differently in this respect:

With 2019 ("Overdub underlying audio" is un-checked):
- If you record any audio (ex. bars 1-4) and then record again (bars-1-4) you don't hear the previous take while recording > That's expected behaviour > OK

With 2022 ("Overdub underlying audio" is un-checked):
- If you record any audio (ex. bars 1-4) and then record again (bars-1-4), you hear the previous take while recording > Definitely not what I would expect. Why would anyone want to hear a previous (discarded) take when recording a new take? That makes re-recording a new take a nearly impossible task. What's more, punch-in recording is also nearly unusable, since (again) hearing the previous take while you're trying to record a new one is really, really confusing.

I'm sure I'm missing something, and probably there's a reason for that design change, but honestly, I find it kind of weird and counterintuitive, and I don't know of any other audio program behaving that way. May I ask why this has changed?

(Of course there are workarounds, it's just that I can't see the logic behind that design change.)

Thanks!

Cerio, describe what pops up at the end of a take, I.e. what options are presented. Do you get a pop up with any choices. What your describing sounds to me like you are getting a choice pop up or maybe wording has changed so it no longer clear.

Not in from if the computer now, but I'm pretty sure that it happens no matter the options you choose. If you can, please try to record a second take in any track following the steps described on my first post, and let me know if you're able to record a second take without hearing the previous one.

I’ll test that as soon as i can tomorrow

Hi

Yes, this is not working as it should.

Unchecked overdub means the previous recording attempt will not be used and hence it should be muted. Currently it's played.

Checked overdub then the previous recording is to be heard and merged with latest recording if the take is ok.


cheers
Thomas

(on the latest win10/64)

Exactly. Thanks for trying!