Selecting RR 363, 85bpm RT in a slow song (60bpm) with a lot of chord changes, some times even every beat, gives a lot of errors on the chords. So i selected double time: a lot better, but more busy busy alas.

No i noticed ~~ when selecting 'normal time' and ~ with 'double time', see pictures below.
What's the idea behind it?

I understand that one of the tilde characters means that the track could be changed to a different RealTracks style using a higher tempo and still sound OK, and the other tilde shows if you have 'allow real tracks substitution' set and a real track has actually been substituted.

I don't know which tilde is which though.

tagging on to Trev's comments above... how I interpret the tildes is...

The single tilde says that the RT is skating on the thin ice at the edge of its recommended range.

The double tilde shows that the RT in use is a substitution and wasn't the RT that was used in the original style.

Regards,
Noel

Call that Double Trouble then ... thanks guys.

PS a Q for ye 2 being experts: i have a mono audio file, (16bit mono) and when imported into BIAB 2019 622 AND BIAB 2018 520, it crashes BIAB with no explanation; straight desktop. It plays alright, but when you press generate: Bingo! Can it be that there's some extra data involved causing this? Maybe a so-called 'broadcast wav', BWF, exported from Cubase and BIAB cannot handle it?

The bit rate is 16-bit, but what’s the sample rate of that file?

I can't find double tilde (~~) in the user manual, but the manual does talk about the single tilde.

Allow RealTracks substitutions based on tempo
When set, the program will find the best RealTracks to use at the current tempo. For example, it might substitute an acoustic bass recorded at a higher tempo, closer to the tempo of your song. The RealTracks name will appear on the main screen with a tilde (~) to indicate the substitution.

44.1kHz ...

OK. That's odd BIAB would have trouble. Can you play that particular file in other music programs?

I loaded it in Wavelab, and it says it's a Cubase bwf type WAV, probably has some extra data embedded. The weirdness is that BIAB crashes on generating the song with this wav loaded. It plays ok without generating the lot.

Regarding the tilde (~) and double tilde (~~) ....

This might help clarify things. It was under "Help" and if one searches for "Realtrack - settings" in the Index.

It's interesting to try the example given using _BALFRED.STY and see what happens at the different tempos.

Noel - what you posted is similar to what I posted (mine came from the user manual; yours came from the help system). However, I don't see in either where it addresses the double tilde (~~).

Hi John,

Apologies for not reading your post as thoroughly as I should have. I didn't realise I was doubling up.

While the what I posted doesn't specifically state what the ~~ sign means, it explains it by way of example using _BALFRED.STY.

Here's my re-writing of the example with a bit more detail...

1. Make sure that "Allow Auto Realtracks Substitution..." is active in Realtrack Preferences and that the substitution hasn't been disabled in Song Settings.

2. Set BIAB's tempo to 85.

3. In Stylepicker, load the demo song for _BALFRED.

4. Regenerate the song. There should be a few single tildes present in the track names. These indicate that substitutions exist for these tracks should the tempo range exceed a preset value that's determined by the programming.

5. Note the name of the tracks (481, 487, 555).

6. Set the tempo to 100 and regenerate. The same tracks are still present and the same tildes are still present.

7. Now change the tempo to 120 and regenerate. The tracks have changed (768, 771, 938) with ~~ in front of the names now to show that substitutions have occurred.

Regards,
Noel

thanks for the info, i'll try the _BalFred tomorrow, meanwhile Fred's at it already:

The confusion is caused by all of these cryptic shortcuts that permeate throughout the program.

Many years ago, I asked for this simple addition to the Song Picker. It got a lot of support, and would have taken 5 minutes to implement, but PGM still haven't considered it as being a worthwhile feature.

The concept is still current. Explain what the cryptic symbols actually mean, or replace them with user-friendly definitions. We are no longer living in the days of DOS limitations.