When I listen to this bass line in this as in other points, the note does not last as it was written but it is stopped. Why?

Hi. Could you give some more detail please, so we can verify it?

Is this a notated RealTrack? Or a MIDI track you entered?

Is what you hear shorter than what we see, so it's shorter than a dotted half note?

If it's a RealTrack, what style or RealTrack is this bass part? Does the same song do the same thing if you change the RealTrack or style?

If it's MIDI, go into the MIDI step editor and look for a rest.

The more you can tell us, the better.

I attach the file

BIAB2016 I not have Realtrack

I have edited this bass track

GOODMORNING

bar #7 and others stopped

To view the length of time that a note plays for, do the follow...

1. Go into Notation Mode.

2. Activate "Staff Roll Notation" as shown on the image below.

Two blue lines appear on the note-head. The vertical line shows the note's volume and the horizontal line shows how long the note plays for.

As can be seen on the note with the red circle around it (this is the first bass note in bar 7), it only plays for a short time.

This situation usually arises if you've been adding and deleting notes of different time values in this section of the bar.

To lengthen how long a note plays for, there are two easy ways...

1. Simply position the mouse cursor in the centre of the note-head and left-click once. The note's length will then automatically increase to fill the note's written value.

2. Alternatively, position the mouse cursor in the centre of the note-head and right-click and hold the mouse button down. Now drag the mouse cursor horizontally to the right to manually lengthen the blue line.

Regards,
Noel

Noel has clearly shown what's going on here, but we still don't know why it happened. I've seen it happen before occasionally (usually when entering, then deleting, then changing notes). But don't know exactly what caused it. I just fix it by changing the duration of the note (right click on the note and enter a new duration).

Also, for completeness, while the vertical line generally presents itself as the volume heard, technically it represents the note's velocity.

This is a bug of the program!!!.... and they have not even thought of a utility that allows you to fix all the notes with just one click and do not go and fix a note at a time

Hi Casak
I have reported the issue that you have identified to the developers. Like you, we are just users of the program also.

As I see it, it's not a bug. It's the way the program has always worked. I've been using it for many years.

I imagine that it's because of the semi-automatic note-entry method that PG Music have invented. It's a great system. No other program that I'm aware of has such an easy note entry approach. Most systems are fully manual with mouse-based note entry and much slower as a consequence.

Try disabling "Minimize rests" under "Options | Preferences | Notation" and see if that helps with the note display accuracy.

By the way, did my suggestion solve your problem?

Regards,
Noel

I'm not yet convinced we are ready to conclude that. A better approach is to prevent the occurrence in the first place.

I think we have, for years, put up with a lot of small problems in BIAB that new users consider as bugs. As soon as this problem was posted, many of us knew the answer imediately, and in our own work, fix it by adjusting the previous note whenever we delete one.

It is a bug, not a feature, but we deal with it and move on. There are so many good things about BIAB that we simply overlook the minor issues.

Many problems with notation have existed for years. There are many threads about time signatures other rhan 4/4 or 3/4, 4 chord max per bar, or even the limit of 256 bars per song. These are issues that will probably never be addressed without a major rewrite of the notation module, and somehow I don't see that in the immediate future.

I am not sure that we can do much about it. We seemed resigned to ignoring them because the rest of the product is so good. Maybe the beta testers should keep flagging the problems and hoping that PGM listen.

Do we need an FAQ and the known workarounds for the 'bugs', 'issues', 'features'?

Can't Tips & Tricks be used for this purpose? Sometimes I will see a great response to an interesting question and will ask the respondent to post the question and their response in Tips & Tricks. In most cases they are eager to make the information easier to find in future searches.

It would be nice if PG Music mined the forum for workarounds and tips then incorporated the information in the Support FAQs and user manuals once or twice a year but, then again, that's why site search is such an important function.