For Classical Release Track Artist and Recording Artist are usually different because Track Artist should be the composer and the Recoriding Artist should be the main performers.
I added a new release, and the tracks require new associated Recording but there seems to be no way to add a different artist credit for the new recordings at the time of creating a new release, is that correct. And if so are there any efforts to change that ?
There seem to be no options for these automatically created recordings.
I had a similar problem when adding video recordings.
(I think, there exists a classical userscript that writes the performers to the recording artist, but I’ve forgotten which it was - and you to change the initially created recordings)
I believe one simple trick is to initially add your new release with the Performers in the track names. Save that. This make recordings in the Performers names. Then instantly come back into the track list and change to the composers in the Track lists, without changing any data on the Recordings page.
Do this within 24hours and you’re good to go.
The scripts solution means you have to go through all the relationships setting up the links in there first before the script can be used.
Okay so I see the practical logic behind this is that is easier to edit the track artist from the releases tracklist page then have to go to each recording and edit the recording artist. And also more likely to have multiple performers then multiple composers so doing it this way we only having to add one person to each track rather than multiple people to each recording.
However, I am suprised after all these years there is not a way to do this correctly in one go instead of using your workaround to on purpose enter the wrong details for track artist to start with, or to enter the right track artist, and then laboriously enter the recording artist for each each recording in subsequent edits.
I have alot of customers who use the Roon platform, an expensive music player geared towards hi-end audio equipment. and this make use of MusicBrainz data. Many of their customers have large classical music collections and I try to push them towards adding releases into MusicBrainz, but it is a difficult sell, especially when the UI makes it needlessy more difficult I wonder if the MB dev team realize that this is a real issue that disuades people from adding new releases.
I am also revisiting the MusicBrainz seeding, and Im trying to improve it for adding classical releases. One such improvement was identifying if the users release was a Classical release and if so ensuring when seeding that the MusicBrainz Track Artist is set to the composer because this is the right value, but its unfortunate that then the user would have to do manual edits to set the recording artist for new recordings as this cannot be done in the seeder either.
<Warning! Personal Opinion ahead… do not read 
Just personal opinion not a dig at anyone>
I agree @ijabz . Classical is a mess. A headache for noobs. I try to avoid going anywhere near Classical. A few times I tried, but got shouted at. It is a black art editing Classical. Too much assumption that you know the subject. To many rules within rules. So I just use hacky methods. Hit and run. 
If you are attempting to do this “properly” via code, then what you need to do is add some kind of performer credit to the recordings. Either performer, orchestra, conductor, instruments, etc. Then make use of this script: GitHub - loujine/musicbrainz-scripts: Collection of greasemonkey scripts for MusicBrainz That will move those details into the Recording Artist credit.
Personally I think there needs to be an option somewhere to tick “this is a classical edit” and head into a totally different set of pages.
There seems to be a shift towards using userscripts instead of making chnages to the core website. The trouble with this it is not suitable for casual users who are not aware of these scripts, and even if they are it is time consuming to find the right ones and learn how to use them.
And is not useful for my usecase where I am trying to making it easier for my customers to add releases by using the release seeding within an application, but its not practical to then expect them to install user scripts as well.
I believe the scripts have always been around. Some users are keen for features, but the core team who write the website is small and can only get through so much work at a time. So UserScripts fill in a gap until the site catches up.
Use the ticket system to vote on the changes to be made to the site\database\GUI. That is one of the better places to let devs know of the interest in certain features.
Yes I know and have raised many issues in the past but there are alot of issues, sometimes I think its useful to just discuss things again on the forum
Related to that I raised this issue in 2016 https://tickets.metabrainz.org/browse/MBS-9020
I see after adding a release it is relatively easy to add relationships to all recordings because of the Batch-add a relationship to recordings option, that would seem a good idea to add similar logic to the recordings tab.
