In AudioEdit View, on the Master Track, Using Volume Automation...
I faded out the end of the tune from Bar 40 to Bar 43.
But, instead of following the volume automation, it actual started fading at Bar 23.

I highlighted all nodes (Control A) on the on the Master Track, deleting all nodes, and audio returned.
Tried again, with same results. Guess I'm just having a bad day.

Hello Thunderthud,

I suspect that this is fixed in build 1104, which is in pre-release testing for another day or two. Here is a link to the patch:
https://dl11.pgmusic.com/support/patch/bb2024_win_update_build1104.exe

Thanks! Will try in the morning.

Andrew,
I appreciate getting the patch early, but I'm sorry to say that "Patch 1104" does not fix the problem. The Master Track no longer fades early, but it doesn't fade at all. The fade drawn near the end of the track, just continues at full volume.

Thanks for trying!
Hope this gets addressed.

Hi Thunderthud,

I have 1104 and the Master fade works for me. I don't know if you've tried it yet but when BIAB starts doing something unusual, "Return to factory settings" is worth trying. (I use the MOST option.)

Try this song and see if it works for you...

https://www.dropbox.com/s/ozrux7stf6pjk4e/thunderthud%20master%20volume%20fade.SGU?dl=1

Regards,
--Noel

I have 1104 and the Master fade works for me as well.

Noel, in short no. Tried factory reset, behaving the same. Tried your SGU, same problem. Never had this before. Weird.
But thanks!

Noel, I noticed that it does what's in the attached screenshot when it's acting funky....

And this on it shows the fade starting late into bar 34, but it is actually starting to fade at 31. It is acting totally erratically. Giving up for the moment! Thanks.

I have exactly the same problem: volume automation is starting at the wrong bar number.

Has this problem been solved?

Volume automation is so important to me, if this problem can't be solved, I have to revert my software back to 2023.

BiaB 2023 seems to be a less buggy software to use.

Hi MusicVillain.

What build of BIAB '24 are you running? There have been a couple of updates that have addressed issues with Audio Edit and volume.

Regards,
--Noel

Band-in-a-Box® Version 2024 Update - Build 1108 (Jan 2 2024)

_______________________________________________________

Summary of Changes (build 1109) (Jan 12, 2024)
_______________________________________________________

Added: Three extra RealTracks added, that should have been included in sets 444, 445, and 447: Bass, Electric, VintageCountryWaltzSlow Sw 085; Guitar, Electric, Soloist BroCountryPopJohnny Ev 110; Guitar, Electric, Soloist ModCountryTravellerJohnny Sw16 075
Fixed: _Chase.sty triggered HiQ error.
Fixed: _Beefy.sty might show N/A RT.
Fixed: Apply button should be enabled in MultiPicker if no item is selected.
Fixed: F5 dialog was out of sync in some cases.
Fixed: Chord Builder previews when using chords accessed from the [..] buttons.
Fixed: When importing MIDI files that use a higher PPQ than 120 will place the lyrics at the wrong times.
Fixed: When exporting MIDI files with lyrics, the lyric events were saved as plain text events instead of lyric events.
Fixed: MIDI lyrics export option “PG Music format (old)” which was obsolete, changed to “Plain Text Events”.
Fixed: MP3 loop files would not not play.
Fixed: Playback auto-scrolling in the Audio Edit window might stop working after right-clicking.
Fixed: “Record from bar” might place recorded audio at wrong location if the track was empty before recording.
Fixed: Copy/Move tracks failed to copy audio.
Fixed: Possible crash when generating songs with very short riffs and “Automatically fill gaps between riffs” is enabled.
Fixed: Opening the Lead Sheet window would make the Piano Roll disappear.
Fixed: Delete key should delete the current chord if in ACW mode in the Audio Edit window.
Fixed: Using “Choose colors for Chord and Notation display” in the ChDisp menu wouldn’t permanently change the Notation Window’s background color.


_______________________________________________________

Summary of Changes (build 1108) (Dec 21, 2023)
_______________________________________________________

Fixed: Possible program freeze if using “Auto-Fix Sour Notes” feature.
Fixed: Mix-paste in Audio Edit was not working properly.
Fixed: Visual metronome dialog now counts in correctly if bars 1 and 2 have timesigs like 3/4 5/4 7/4.
Fixed: Partial Generation improved for RealDrums, on drums and other tracks, including notation.
Fixed: Apply button on MultiPicker should be enabled for all except Melodist, Soloist if None is selected.
Fixed: UserTracks were taking a long time to generate, even if .bt2 files were present.
Added: Audition chord on beat 2 or 4 by pressing Control-Shift-Enter (note: Shift-Enter already auditions beats 1 or 3).

_______________________________________________________

Summary of Changes (build 1107) (Dec 19, 2023)
_______________________________________________________

Fixed: UserTracks might play some phrases in the wrong key.
Fixed: UserTracks would not play if frozen when loaded.
Fixed: “Loop (Restart when wav ends)” did not work.
Fixed: CTRL+A and Shift+End keys did not work on tracks window.
Fixed: ACW track might go out of sync if using loop playback.
Fixed: F5 dialog updates after loading song, style.
Fixed: Chord Progression dialog has new items (shiftClick to audition only, “Var” button to show another variation, clear chord button, hints)
Fixed: regular chord builder, shift-click will audition only.
Fixed: MultiPicker Styles tab would play same demo if standalone picker had been used.
Fixed: an exception could occur in stylePicker if using the up/down arrow key.

_______________________________________________________

Summary of Changes (build 1106) (Dec 19, 2023)
_______________________________________________________

Fixed: Tracks out of sync if using multiple styles on a track.
Fixed: Access Violation error if attempting to make audio harmonies.
Fixed: Issues with viewing volume nodes on mono tracks.
Fixed: Selecting a blank track in the Audio Edit window would display the wrong track data.
Fixed: “Auto-Fix Sour Notes” features were not working.
Improved: If changing “stretching quality” setting in RealTracks Settings dialog, relevant tracks will be reprocessed immediately.
Fixed: Problematic style changes with styles like 'Airduo' and Aircelt' that have no drum part.
Updated: PDF Documentation, help file.
Fixed: Rebuild in the RD Picker duplicates some multidrum entries during the current session.
Added: style _MIASMA (rt431)
Fixed: Possible problems playing style Demo songs that were frozen.
Fixed: Trumpet, Background RnBFunky Ev 120 (1TrackHornSection) not playing properly
Updated: RT Memos for all RealTracks included in the 2024 release.
Improved: The following RealTracks have improvements including better phrase transitions:
- Piano, Acoustic, Soloist JazzFastRH Sw 190
- Guitar, Electric, Soloist ModCountryTravellerJohnny Sw16 075
- Guitar, Electric, Rhythm MetalModernTripletSyncReverse12key Sw 140
- Guitar, Electric, Soloist BroCountryPopJohnny Ev 110
- Bass, Acoustic, SoulJazzMellow ev 85
- Piano, ElectricVintage, Rhythm SoulJazzMellowTrem Ev 085
- Bass, Acoustic, Fusion70sFunk ev16 100
- Piano, Electric, Rhythm Fusion70sAvantFunk ev16 100 h
- Guitar, Electric, Soloist Metal80sPopFast8ths Ev 130
- Guitar, Electric, Soloist AmericanaGentleTrain ev16 085

DAW Plugin 6.0.13 release notes

Fixed: Crash opening the plugin
Fixed: RD Stems not loading from SGU
Fixed: Destination REAPER track should not be deleted before sending to REAPER
Fixed: Renamed some labels in REAPER Panel

_______________________________________________________

Summary of Changes (build 1105) (Dec 12, 2023)
_______________________________________________________

Fixed: “Automatically fill gaps between riffs” feature was not working.
Fixed: Various GUI issues with Audio Chord Wizard mode.
Fixed: Possible slow bootup for some users.
Fixed: Tracks with multi-drums would stop generating if restarting playback.
Fixed: Audio Conversion Error -1072875854 when exporting MP3 or M4A files.
Fixed: Right-click on Chords button should show the Chords Display menu.
Fixed: Home key did not work on tracks window.

Perhaps consider this beta pre-release version which is still being beta tested. Andrew from PG Music provided this link:

https://update.pgmusic.com/support/patch/bb2024_win_update_build1109.exe

Can you describe your steps in detail? This could be a very specific problem.

Andrew:

1. Open BiaB, enter chords, select a style, generate and play.

2. Open Audio Edit Window, set nodes for volume automation of each instrument.

3. The nodes are either -inf (mute) or 0 (unmute).

4. For example, a guitar is turned on (from -inf to 0), at the location of bar 9.

5. The problem is, when playing the full song, that guitar is turned on at bar 6, several bars earlier than the nodes.

6. Even the AEW shows correct nodes, the playback is wrong.

That doesn't happen in my testing. Could you send a song file that has the problem?

It's not the problem of the sgu but the software. I fixed the problem by downgrading my BiaB from 2024 to 2023.

There is another problem, just so you know. When you do Alt+F8 partial regen, you can only do regen on RealTracks, not RealDrums. Is this also a bug, or is it normal?

Generally, the hardest part of fixing a problem is being able to make the problem happen.
Hopefully your SGU will allow the developers to make the problem happen.

I really agree with what others have mentioned and have really reached out to help. Why just blame the software and instead not provide objective situations that others could use to help solve any potential issues?

Maybe it is a software issue. I don't know. But how can anyone identify and work to fix it when after requesting a sample, no sample is provided, nor relevant information on how to create the issue?

Team work is beneficial.

Because I don't want to waste Andrew's time. After opening that sgu in BiaB 2023, everything is working fine. If I send that sgu to Andrew, he will also find it's working with no issue.

My bad. I shouldn't have rushed to upgrade to 2024. Many people in this forum advised not to upgrade the software until end of summer each year (in north hemisphere), when all bugs are fixed and the software is ready to go.

I will come back to test BiaB 2024 in September, after Build 1124 is released.

By your decision not to provide a requested sample song that works in BIAB 2023 but not in a particular build of 2024, you are raising the odds someone else will encounter the same problem that could have been solved.

It is the old part of the problem or part of the solution syndrome. MV why not try to help out here. I know this can be frustrating when issues arise but if we work with PGM instead of getting mad and shutting down far more can be accomplished. Send the man the file and let's see if they can find a solution for you. unless you are afraid the problem is in your system not the program. Just making a suggestion here from experience. I have had that happen to me more than i want to admit sometimes.

Too late. After downgrading, I already open that problematic sgu in 2023, tested it out, and saved it. Once saved, it's overwritten, and it's no longer a problematic file anymore, and that's why I think it's a waste of everyone's time to share a perfectly normal sgu for the purpose of debugging.

I think I started this thread and so far with 1109 I'm not seeing this issue anymore. Thx

Whatever, your choice.