I don't understand your question. You can't use CALL AUDIO before CALL SYNTHE, that launches an application.
Please quote my complete sentence:
"However, the MSX-AUDIO standard specifies that this instruction must always be present in a complete MSX-AUDIO cartridge, to allow the launching of an MSX-AUDIO application and each manufacturer can include any MSX-AUDIO application."
I just would like to know why MSX datapack says do not enter CALL SYNTHE after CALL AUDIO.
CALL SYNTHE simply does not work when you have used CALL AUDIO before. I had already mentioned that in this discussion.
I know it doesn't work. An illegal function call occurs, but why?
I find it amazing that this expensive extension has such poor firmware, and it's not just this app.
I have the impression that you are inventing explanations to justify the previous erroneous explanations. This app is a part of MSX-AUDIO BASIC from the start. It conflicts with MSX-Audio BASIC just because it was poorly developed.
For me, an instruction that prevents to use CALL AUDIO and the other MSX-AUDIO BASIC instructions should not be part of MSX-AUDIO BASIC, but I can't fight against the datapack that creates confusion between the MSX-AUDIO standard and the MSX-AUDIO BASIC. I think sdsnatcher73 has an opinion that is very close to my opinion.
To prove the contrary, someone should debug this poor application, not only to accept CALL AUDIO before CALL SYNTHE, but also to allow exit from the application and back to the BASIC screen.
It is up to the person who affirms something to prove that what he says is true, not to the one who doubts to prove the contrary.
For me, an instruction that prevents to use CALL AUDIO and the other MSX-AUDIO BASIC instructions should not be part of MSX-AUDIO BASIC
For me too, but ASCII (or Panasonic?) had probably to choose it for lack of anything better. Most manufacturers of the time did the same. Almost all firmware are useless even at the time. Manufacturers wanted to show that their machine has plenty in the trunk rather than put something really interesting in it. At that time, it was the size of the ROMs that was used as an argument.
In the case of MSX-Audio, they probably didn't think it was a problem since you can't quit the application (as is the case for most cartridge software).
For me, an instruction that prevents to use CALL AUDIO and the other MSX-AUDIO BASIC instructions should not be part of MSX-AUDIO BASIC
For me too, but ASCII (or Panasonic?) had probably to choose it for lack of anything better. .
I notice we agree on this point. The difference between our approaches is elsewhere: you prefer to present the things as they are presented in official docs, I consider that the official docs don't always say entirely what is true.
The advantage of your approach is to avoid stupid questions by people comparing infos from different sources, and that's the current status in the Wiki, but it's not incompatible with additional infos explaining why the reality could be seen differently from the official docs, and that's the text I've added.
I wonder if the built-in software uses the MSX-AUDIO BIOS. It probably doesn’t, since it was developed by Toshiba for a module without BIOS. It would not surprise me if it conflicts with the MSX-AUDIO BIOS, and that is the reason that you can not run the software after initialising the BIOS / BASIC with CALL AUDIO.
I think CALL AUDIO initializes the MSX-AUDIO BASIC driver like CALL MUSIC initializes the MSX-MUSIC driver.
The built-in software uses probably its own driver to be able to boot directly from ROM, and it conflicts with the BASIC driver.
I am surprised to see that CALL AUDIO does not reduce user memory.
I am surprised to see that CALL AUDIO does not reduce user memory.
That's because the MSX-AUDIO cartridge has its own work RAM.