I have:

Made sure the style selected is RB only (no MIDI)

Entered my chords

Selected "Generate all BB Tracks (entire song)"

All I get is the Real Drums. No other tracks. I just updated to build 4, and I rebuilt my styles.

Am I once again the only person seeing this?

Can you expose the style used and any other steps necessary to reproduce?
(not sure what "Made sure the style selected is RB only (no MIDI)" means ..

EDDIE.
If you tell us the style name i’ll whack some chords in and run a gen test. i have 7k styles.
so assuming i have the style your useing etc....

ps ..do you only see drums waveform in traks view ?
Best
om

The style is

_DIR_AMP



Yes. It is only generating the drums.

Harv, "Real, no MIDI". I embellished. I rarely to never use MIDI tracks.

Also know that this is the first time I ran 2022. And before I did I installed the update. According to the sales page info I have downloaded and installed everything I paid for, which was the Ultra Pack.

I have now tested with 4 different styles. None will generate anything but the drums. I CAN generate individual tracks manually. My next test is to go into the style, copy the names of the Real Tracks and generate them manually, but what a PITA that is.

It all boils down to "It ain't working" at this point.

Tomorrow I will pull out the hard drive and reinstall it all from hard drive, because at this point I am beyond annoyed that it isn't working. I keep throwing money at this stuff and I always have these problems.

Whoever is testing this, to do exactly what I did, set up this chord progression (though that shouldn't matter in any way at all).

Full measures of

Am - G - F - G
Am - G - F - Em

Over and over.

I did it twice for a total of 16 bars.

EDDIE.
_DIR_AMP all R T’s in dire style.
5 RT’s…ALL GOT GENNED WAVEFORMS ON 5 different tracks.
All good here..whole song played...all ok.
2022 ultrapak

Best
om

A geeze. Here we go again. Works for you, not for me.

I have a headache. I'm going to bed.

EDDIE.
works also with your chords.

Q's.
1. DO YOU SEE 5 DIRE TRAK NAMES ON 5 SEPERATE TRAKS.
mouse down in case of hidden.
2. make sure traks not nuted.
3. in mixer for rb do you only see drums led and not the
other 4 traks ?

best/happiness.
om

No. It generates the drums and stops. And just because, I let it run 10 minutes on the last attempt. It simply doesn't generate. Since it works for you I have to assume it is my installation.

EDDIE.
I think ive figured a possible reason you get probs.
TEST THIS>>>>
Go to rb preferences.
Choose song generation tab at top.
MAKE SURE THAT ALLOW REAL TRACKS IS TICKED !!
press ok.

Best
om

That box WAS checked (I verified it) and the path to the tracks is correct. (Default locations.)

This sucks.

EDDIE.
1...does this problem occur with styles other than DIR AMP ?
2...q'...are you running shebang from ultrapak usb drive direct ? as received from pg ? rather than installing somewhere else ?

om

I could not generate tracks in any of the 4 styles I tested with, so I will assume it just isn't working.

I installed the full monte onto my hard drive, overwriting 2021, just like I did to install 2021, 2020, 2019.... everything is exactly the same as it has always been. And the fact that it generates the drum track, and only the drum track, which normally comes LAST after the instruments, means something is very wrong.

I don't want another link in the data chain, especially through a USB port, so I don't want to run from the USB drive. In fact the drive is not even connected to the computer anymore. I have never left the USB drive connected in the what, 11-12 years I have been using PG. In fact I don't recall every running anything from a USB device.

On the last song I did with Rog, he sent me a file. I loaded it, and did the singing on this very computer, so manual recording works fine. Just Real Track generation doesn't work. Real DRUMS work. I can generate a drum track, and I manually generated 3 of them outside of what the "Generate all tracks" gave me, so a total of 4.

I have not yet installed it on the computer upstairs, which is the main music computer. And I won't install it until I can make it work on this one. I have 2020 up there that works.

I am removing and reinstalling. I have done too many "upgrade by overwrite" so I am going to start clean.

Eddie.
ok...hope you get sorted.
i used to install to an internal drive...but as the ult
pak usb drive is fast i use that daily after haveing backed it up first when i got it..

i have shortcuts on win main screen pointing to
rb 2022 and bb 2022 on the pg drive.
so far good.
pg is correct..one can in fact work straight off the pg drive....but of course takes up a usb port.
i'm a back up nut...ssd's/old drives in enclosures etc

best
om

Eddie, since the style utilizes the Amplitude module, that's likely where it's stalling. Before re-installing the whole package, check to be sure the pathway through Amplitude is correct.

Also, since you plan on re-installing, in which case you lose your settings anyway, apply [Options|Return to default settings] before doing the re-install.

I would also load the style demo before re-installing. That may reset the Amplitude settings. Probably not. I don't know. But probably not. It's just something I'd try.

Charlie

Yeah I know it CAN run from their drive but I prefer it to be on my SSD. Just a matter of preference.

I found that I didn't have over half the real tracks I was supposed to have in a chat with support. I am 99.99% sure that the style I picked called up real tracks I didn't have. I'll know in an hour or so. There had to have been a glitch during the download install because the newest real tracks were from 2020. I am now installing from the hard drive. It never hurts to start fresh rather than spend 3 times as much time trying to fix something that can't be fixed without reinstalling, though I DO like a challenge. This coming from a man who was once described by his best friend by her saying "You are so stubborn you'd bury yourself alive to prove you know how to use a shovel." And she was right!!

Charlie, I tried it with 4 different styles, including one of the Dire Straits settings that I have used before. I completely removed all the old instances and am installing as if this computer has never seen PG before.

Fortunately I remember my serial number! LOL!!

Okay. Removed and reinstalled and nothing changed. Sent my small test file to PG and they tried it and the same thing happened there. One of the engineer level guys is going to look things over and maybe do a Team Viewer session to watch things first hand. The odd thing is that Muso can generate successfully with the same style. I have now tried it on 5 styles and all of them failed.

AND...

I loaded a copy of a song I did months ago, maybe even a year ago. It was done in a waltz tempo. I selected a similar but different waltz style and tried to generate, and it did only the drums. Now, I sent my seq file to PG and the same thing happened THERE too. We may have stumbled onto something that needs attention.

But I worked on this for 9 hours today and I am tired, hungry, and frustrated beyond belief.

Eddie.
i'm sorry time to get back to this...medical stuff on occasion to deal with. all good.

wow pg found same prob.

i have a q' eddie.
in rb in the stylepicker when you load a or any style DEMO ...
do all traks get genned ?

so far i can honestly say ive had no prob, and i'm genning each day on my songs.
i'm running a refurb i5/ssd/win 10 system.
(win 10 not been updated since i got the pc years ago)
its a studio pc only...never sees the net // no avirus etc//lean system.

in fact tother day i had occasion to call pg with a tech question, and mentioned to the ever helpfull catherine
that i was very happy so far with the audient interface
and played a punker rock cockney song i'm working on right now,...
and some cockney vocals so she could hear the audient quality roughly. thus obviously i'm not lying.

in addition ive been loading old bb songs into rb, recent bb songs and loads of stylepicker demo songs in a vain effort to duplicate your problem....and failed...
all is what i expected.

only other thing i can think re rb is i'm on 2022 build 2
rb.

i wish you the best eddie and hope you get it sorted.

best
om

Muso I just tried that and it only generated the drums.

Now to have lunch, clear my thoughts, go upstairs to the other computer that I don't think I yet updated with the V4 patch and see if it acts the same.

If I don't have this new song ready for our little meetup Mr. Snyder is going to run me over with my little camper trailer.

The reinstall included my deleting every reference to the software, so resetting to default would have been moot. I just wonder if that update to V4 is the problem. Muso does not have the problem and he is still on V2. I THINK my upstairs computer was not updated yet and I will test up there in about 10 minutes. (Lunch first to clear my head of this and go in fresh.)`

I may get desperate enough to load an old version like 2019 JUST to get this song finished because Mr. Snyder said he'd run me over with my own camper trailer if I didn't bring a new song with me in April.

The style works in my version of RealBand as well. The things I listed above are steps I would have taken prior to doing a re-install. I have no indication they would have worked and the re-install would have been necessary anyway. I'm on a higher version than (2) also.

Do you have somewhere to post one of your failing SEQ files?
On the target tracks; is the Track Type MIDI or Audio?
IOW, what is your default track type? I assume Audio since you said you rarely use MIDI (which seems weird for a guy with a bunch of synths).
If Audio, are they MONO or Stereo?

Just pondering possible causes since it seems to be related to the file you have saved.
.. or your Untitled.Seq file if you haven't ever saved it.

Wonder if renaming that file so it creates a new one would do anything.
I'm pretty sure RB opens that file (if it exists) when you open RB, as a default.
If that default file it opens is corrupted, I suppose everything you did after that would have issues.

No harm trying .. force RB to create a brand new starting file (Untitled.SEQ) by renaming the old one .. in whatever folder you are running RB from.

At least then we know the base seq file template is clean
maybe??
Sure is a weird one from what we know so far

Link to problem child is HERE

The link is to a newly created file not related to the one I made initially. It is a rather unimaginative thing that is just a chord progression that will get looped. The style SHOULD be _DIRE_ST. I say should be because I don't know what is functioning correctly and what isn't. I made that little file (just 8 measures), tried to generate, got only drums, and did not resave.

My default track type is audio - mono. (When I want to play with MIDID I change a track one at a time and play the data in. I will do that more as I sort this stuff out and change my gear from tabletop racks to one server rack type tower. I needed to buy more cage nuts and an installation tool and more rack screws.) I have some weird stuff in my mind that will require me testing different sounds so now playing MIDI data in rather than playing the track right many times is the more prudent path.)

Something to mention is that Muso created a file with the same style I am using and it worked fine, BUT he has not yet updated to V4. I am currently installing 2022 upstairs and will try the seq file BEFORE running that patch.

What gets me is they at PG WERE able to duplicate this issue. That would seem to lessen the likelihood that it is my PC that's the problem. Maybe there's a small glitch in the latest update.

Other things I have done are to try and load a demo from the style page window and loading a copy of an old song that failed the same when when I tried to regen the old song, so it isn't just this song. I don't know any way I haven't tested. You know pretty well how thorough of a nerd I am.

My thoughts were;
PGMusic started with YOUR file to replicate
(you sent them your file right? At least I thought I read that)
.. so I thought maybe it's that file that RB opens when you start it up .. that's all
I mean if IT is bad you are starting out with an issue to begin with
Renaming should force RB to create a new one .. just a thought

Well, here's the update. I reinstalled 2022 on this PC. I did NOT run the update to V4. Everything generated just fine. (The SONG is a piece of crap but it's just a test file.) The computer downstairs IS updated to V4. (Or build 4, whatever they call it.)

So, I think Holmes and Watson called that "a clue". Just like when OldMuso tested that style on V2 it ran fine, so did it here.

OK, I downloaded your sample SEQ file, generated and got the result in the image below
Not sure if it helps (probably not), but I got other tracks .. not sure what the expected result was.
I used Generate; generate all BB tracks.
Using latest build 4 ..
<shrug>
I dunno, out of ideas

No idea why it worked for you and not everybody. And why the same file worked for me on build 2 but not build 4. When it didn't work on a computer at PG I was shocked.

So guess who won't be updating the upstairs computer?

Works fine here too:

Merci pour le test. Vraiment très étrange.

Charlie, could I get you to go to the link I posted in this thread and download MY seq file and see what happens?

These inconsistent results are making me crazy here.

I downloaded it just now, opened and generated in RB and it works fine.
Edited it a bit a re-generated with no issues.

Charlie

So you go to column A, the DID work side of the page. This is getting more and more strange every day. Thanks for doing that.

I have deleted and recreated that little 16 bar songlet about 6 times now. I have tried 4 different styles. Nothing has worked.

I saw someone say to reinstall only Real Band. How do I do that? I click setup and go through the defaults and it wants to install everything again. That would be the 4th time I am installing.

Same thing + many times + expectation of different results = insanity.

I then looked at the file properties of bbw2_64.exe and was shocked to see a modified date of 1-21-2022 because I didn't even install the 2022 version until March. It's been a while since I paid attention to how such things work but isn't the modified date the last time I touched that file? I mean, that file didn't exist until March 8th, 2022 at 6:01:45 PM.

Also interesting is to look at that file on the hard drive that the date is 12-1-2021. What is the relevance of 2-15-22 as Andrew stated in a reply?

Here are the 2 files side by side.



At this point I am more confused than a virgin on his wedding night.

RESOLVED!!!!!

I skipped an update to BIAB (since I have never used BIAB) and it exposed how little I know about the intertwining of the 2 programs. I updated BIAB to 920 and now RB works.