It is my custom to Mix all tracks to a stereo pair (L+R), then make plugin adjustments
the Mix Pair.

For final Stereo WAV mixing in RB I go to the Audio menu, choose Merge Audio and DXi Tracks to Stereo File - OK.
Generally I end up with a file about 41,000 KB - for the size of a 4 min WAV.

Today I did my first such Mix under Build 6, and found the resulting WAV to be half the usual size.

Checked things out including remixing stereo WAVs in Build 6 but previously done under Build 5. They were half size too after remixing in 6 - probably mono mix or a mis-stated 44/16 - but I think mono. My hearing can't determine this with headphones.

Just to be sure I moved the SEQ Master to PT2011 - and mixed my usual way - and everything was fine. The usual stereo wave mix.


ERROR/BUG - Merge to Stereo Wave in Audio Menu is not creating Stereo waves in Build 6.

Could someone double check this please.

Ian

Hi Ian,

I justed tested this using RealBand 2012 build 6. I tried merging and audio and MIDI track (set to CoyoteWT DXi), and got a stereo file as the result. I just installed RealBand recently, so I am using factory settings.

If you check the file in Windows explorer, by right-clicking on the file and choosing Properties, then Summary, it should say whether it is Mono or Stereo.

Hi Blake

I tried it again and I went to Explorer as you suggested - the file was mono at 705kbps - it was only 21,000+-.

The one I did in PT2011 - was 1411kbps, stereo and 4,000+-KB.

I used the same process in both RB(6) and PT2011. RB (6) gives me Mono, PT2011 gives me stereo. So my sound card is OK.

I just did it a couple of more times in Build 6 with the same 1 channel result. I reinstalled Build 6 and rebooted the comp and RB (6) - still got mono. The same as if I had "Exported to WAV" file.

PowerTracks works the way it should merging to Stereo.

I'm using XP_SP3, 32bit.

You mention factory defaults - which setting could effect stereo/mono of a merge - this prob was in Build 5.
because I went back to Build 5 and tried it.

Ian

Worked fine here also

Bob -

The same Merge to Stereo procedure was working fine on RB2012 (5).
The Build 6 upgrade worked OK for that procedure, and then suddenly didn't.
I used the same SEQ in PT2011 and it worked fine at creating the stereo merge file.

Any ideas what could have changed in RB? or could it be something in BIAB which controls that Merge?

If anyone has input or ideas, it would be appreciated.
Ian

I have experienced this prior to build 6. Not sure what the cause is. Some tunes render stereo file, others produce a mono file ?

Just tried this and it works fine on VSTi + Audio tracks to produce both stereo and tracks of the correct lengths.

Mitch, Lyn, Bob, Blake, thanks for the responses.

Mitch did you ever solve it? How do you get around it?

But the "Merge audio etc...stereo file" is still delivering a mono wave in my RB2012(6). BUT Stereo is delivered when the same SEQ is moved to PT2011.

PG - is this controlled by a DLL file?
Is it possible that a control file has become corrupted, or an RB Ini file suddenly become corrupted?

How do I solve this? Yes I can use PT but I should be able to use RB.
What's the next step?

Thanks - Ian

Ian,

I reported my 'bug' but never did get resolution. I cannot figure out what / when causes the mono rendering. When it DOES occur, I mix all my tracks to a single, stereo track (TRACK -> MERGE), then export the single mixed stereo track to a .wav file. That's been my 'work-around'.

Hi Mitch

What I can't figure out is why it works for me in Pt and not in RB . . . but it did. . . and then "poof" - gone in RB.

Ian

Ian,

Given that you're a longtime user of PG Music products, I suspect that you've already tried the below. Just in case you haven't, though ...

It sounds like the "Merge to mono" option is electronically engaged even though it mightn't be checked. (See image below.)



What I'd try is the following ...

1. Do a merge with this option selected. Then do a second merge with the option unselected. That might just give it a kick to reset.

2. Failing that, I'd reset RB to factory settings by renaming the REALBAND.INI file and RB.CFG to something like REALBAND.INI.OLD and RB.CFG.OLD. This will effectively "delete" those files so that RB is forced to create new ones (thus the factory rest). If the problem is not solved by doing this, you can always delete the newly created files and then return the original files to their original names.

Hope these thoughts work,
Noel

Thanks so much Noel - I hadn't thought of that. Will give it a shot in the morning.
Both ideas much appreciated.

Ian

Hope all is well.

I Merge to Stereo Wave using the Audio > Merge and this saves a stereo file in my work folder for the song. This wave is then imported back into the RealBand song to a MIDI track and gives the options successively to select Stereo, split channels to separate tracks and then finally Mono. If the track is already set to Stereo then this setting is used immediately by the imported file.

Check also Pref > Audio > Import Channel for Mono Tracks - this can confuse the issue. Mine is set fo Left Channel.

Sounds like one of the ini files got reset to a mono setting.. at least that seems most likely to me. Don't remember which one could hold that info right now..

Check realband.ini under [Miscellaneous Settings]
See if you see anything suspicious..

Thanks for the input everyone.

The problem was solved this morning thanks to Noel - that was exactly the problem.

For some reason the "the merge to mono" check did not disengage. I had to restore to factory settings as Noel suggested.
Now when I use the Audio menu to create a "stereo wave" merge, it works.

Mitch - perhaps you might want to check it out, as you mentioned having a similar problem.

PG - perhaps you might want to check why the Merge on the Track Menu does not really disengage the "merge to mono" even when the check is removed from the window and OK is clicked. Also why does it seem to over-ride the Merge to Stereo on the Audio Menu.

Thanks Noel - great frustration removed. It seems to be a "bug".

Cheers - Ian

Hi Ian,

Glad you got it going again

Noel

Ian, send a note to support so they can see the circumstances surrounding the issue. Include link to this thread (it may help)
Then maybe they can dupe it and fix.