Rubens wrote:Hi Wolfgang!
I share with you the same disappointments, the first not being able to use cross bar notation and the second to not receive a proper answer for this important issue...

If you are asking about (a) cross staff beaming or (b) cross staff notation, then there was a quite surreal discussion about this last year starting in November 2012, and it continued until a de facto armistice emerged, where one way to characterize it is that everyone generally agreed (a) it is a good idea; (b) it is
not a trivial software engineering task; (c) Notion Music is aware of this feature request; and (d) it probably will happen sooner or later, but in a way that makes sense with respect to prioritizing new features, functionality, and enhancements . . .
This is the link to the discussion:
Cross staff notation (Notion Music FORUM)From a different but related perspective, it is primarily an engraving function, and one might expect that a proficient pianist should be able to determine how best to play a complex two-hand crisscrossing piano piece . . .
When using NOTION 4 for playing and performing digital music, it does nothing of value, and if one must have it for printing sheet music, then the obvious solution is to get a competitive crossgrade to Sibelius and to use it to customize the engraving based on exporting the music notation from NOTION 4 in MusicXML format . . .
THOUGHTSIf "cross bar notation" is different from (a) cross staff beaming or (b) cross staff notation, then explaining will be helpful . . .
Regarding software designing and software engineering, it is useful to know that NOTION 4 is designed and programmed in a very specific way to make composing and performing music in real-time on the fly as easy and efficient as possible, and this in turn requires doing everything in a very specific way . . .
NOTION 4 is the only music notation, composition, and performance software on this planet that does these three activities elegantly, and from my perspective this is the primary focus of NOTION 4 . . .
NOTION 4 also prints sheet music, but I think that printing sheet music is a secondary activity . . .
For reference, I have a university degree in Computer Science, and I have been doing graphic user interface (GUI) designing and programming since the first version of Windows, although I switched to the Mac in 2001 and now vastly prefer Mac OS X . . .
As best as I can infer from studying the way NOTION 3 and NOTION 4 work, I think that the various real-time playback and performing algorithms are intimately connected to single staves, even in the case of Piano grand staves and Electric Guitar and Electric Bass dual staves, where for the latter the top part is regular music notation and the bottom part is what colloquially is called a "guitar tab" . . .
There is so much stuff happening behind the scenes--especially when one is using a lot of VSTi virtual instruments, each of which has its own proprietary engine--that it is a bit mind-boggling in the extreme, and everything has to be coordinated and managed in such a way that all the work is done very rapidly so that there are no perceived delays in requesting all the audio for each note; loading the required samples; rendering the samples; and so forth and so on . . .
When one is using the Conductor and performing aspects (NTempo), as well as the MIDI recording aspects, there are additional real-time considerations, and so forth and so on . . .
I have not examined any of the source code for NOTION 3 or NOTION 4, but from my experience doing some of this type of programming, I would not be the least bit surprised to learn that some of the algorithms required extensive fine-tuning to do the necessary work very rapidly, and when this is the case, the fact of the matter is that there are not so many software designers and software engineers who can do this type of work, because in some instances it requires dropping down to machine code and devising strategies for optimizing specific and usually small but often used sections of code that normally would be fine based on the way they are compiled using standard options and so forth in the C/C++ programming language, which itself if low-level, although not as low-level as machine code . . .
Rather than wander into thoughts on discovering the indisputably optimal way to perform a repetitive section of code in real-time on the fly, the summary version is that if it were simple, then it already would be a feature in NOTION 4 . . .
Nevertheless, one cannot avoid a bit of wandering, and many years ago I had the opportunity to work with a software engineer who specialized in optimizing algorithms, and it was quite fascinating. The key is to find ways to avoid repetitively loading the same value over and over and over, and there are various techniques for identifying when this happens . . .
One of the first questions I asked him was whether one or the other of the following two statements was better, and the answer was that it did not matter, because they only do one thing, and they do it pretty much optimally, hence it does not make a lot of sense to pay someone to try to improve incrementing an integer variable, which I thought was cool:
- Code: Select all
int i;
i = i + 1;
OR
i++;
The practical perspective is that most pianists learned how to play piano using G. Schirmer Inc. music books, and most of them do
not have cross staff beaming . . .
Consider the following bit of Mozart, who I think was a pretty good composer for piano and stuff . . .
[
NOTE: Whether this is the entire thing or is just an excerpt is something about which I have no idea at present, but so what, because I can input the notes one at a time to NOTION 4 and then listen to it, which works for me . . . ]
W. A. Mozart, Piano Concerto No. 24 in C Minor, K. 491, finale (var. 5)I think one needs to be a vastly proficient pianist to play the stuff on the top two staves and the bottom two grand staves, which I am guessing are the piano notes, and this is my overall perspective on cross staff beaming or whatever one wants to call it, really . . .
Really! 