at the end of a script which writes TRACK TEMP (e.g. my discogs scripts or dano's extended discogs scipts). TRACK TEMP is written to the TRACK field and to the field simply called 3 here.
(use a discogs release with letters as track positions (vinyl release) to have TRACK TEMP written first)
This seems not very logic to me, but it can be very usefull. However it seem to be a somewhat unstable solution. Changeing things in the script which should not be related to this afterward resulted in TRACK TEMP being written to TITLE instead of TRACK.
Can anybody explain this to me?
Is this a bug in the web scripts language or wanted behaviour?
Is there a way to use this for overwirting TRACK and set the 3 field afterwards without having TRACK restored to its original value?
I got further with my experiments. Here is a little web sources script which demonstrates the possiblilty to change the output of TRACK:
outputto "title temp"
outputto "track temp"
say "album name"
say "artist name 1|artist name 2|artist name 3|"
sayoutput "title temp"
sayoutput "track temp"
set "title temp"
set "track temp"
Seems to be necessary to let the script write exaclty three tracks. With every | an additional track is written.
If I leave that away, the script writes always as many tracks as I have files. That would be no good behaviour for web scripts, because you would not notice if your mp3 album is incomplete.
Seems like there is an even easier way to do that. The ...temp fields are not necessary. I just had them from my trial & error experiments and thought they were part of the sollution.
But these four lines at the end of the script are enough: