Hi Peter, i am having difficulty figuring out how to import a .stsa file.
I have sucessfully created a copy of a song with loops in my beta version of ST3 and saved it to Downloads folder of the ipad i want to now import this file to the new ST3 player but can not figure it out, what exactly do we need to do to sucessfully copy a song file from beta ST3 to the new release of ST3.
Its not very obvious and i cant find any documentation, if i enter .stsa in the search in manual, there seems to be no detailed information on this proceedure.
Can you give me a step by step instruction so i can transfer all the song files from iPad , iPhone beta version that have already done loops to save me redoing them all again.
Thanks Damir
Copy files from Beta to new ST3 5.6
i'm interested too. I create an ExportedSongs.stsa file on my MBP, and would like to import it on my iPad.
Thanks!
Damir florence I'll give you a quick answer that might assist before @peter responds:
Make sure the songs you're importing don't exist in ST3 or you'll get a "0 songs imported" message. Using the FILES app in iOS, hold down your finger on the .stsa file. Look for SHARE in the list of options. Hit SHARE and find STAGE TRAXX 3 (not ST3 BETA) in the row of icons. It should open into ST3 and do the import.
I'd prefer that you could import from the + sign within ST3, but it doesn't appear to work that way.
- Edited
MasterAnt thanks Ant greatly appreciate you help il give it a try and see how it goes, I agree the import should be more obvious and the + area makes a lot more sense, especially if you don’t know you have the same files already it should just give you an option to overwrite instead of making you figure out which files you already have than find them then delete them, this is very labour intensive and time consuming.
But once I am done hopefully I won’t have to use this option very much.
If I get it to work in the first place , otherwise redoing the songs might be quicker.
Cheers Damir
Here’s an update and feedback.
I managed to do 3 out of 12 songs so far as doing it in one pass with all 12 songs is hard.
The reason I am doing it one song at a time is because I feel it is safer as I choose a song and export it I also name this .stsa file as it’s important to know which file is it that needs removal from the new ST3 5.6 so the beta version can be reliably imported then you have to enter all playlists you want to use this file , this takes a lot of time and brainpower.
The reason this system of transfer sucks big time is if I was to transfer a big bunch of songs at 1 time like my 12 songs, once you have chosen these 12 songs and exported them in to .stsa file you better have a pen and paper to write all the names of songs you have put in to this file as there is no way to know what files are in there anymore and you can’t load the songs unless you have deleted them all first so if you have hours to spare and you hopefully have removed all the songs you intend to load you cross your fingers and hope all 12 songs will load now this process takes time and if you don’t complete it Wright away the chances are you will not complete this next day as you have either forgotten the list of songs and you can’t double check what the .stsa file contains , so basically you can stuff things up easily, and I personally don’t feel comfortable deleting my songs out of my ST3 folder first then relying on a .stsa file to recover these files as I don’t see the files I just see one name of a folder that contain a shipload of songs and if I don’t get one song removed can cause a bad import, yet I don’t know which song I still need to remove.
You get my drift, it is not an efficient way to transfer files , I could put up with a message, do you want to replace all files or create copies, that way all files concerned will be done without any extra brainpower and waste of time and any new songs just get added automatically,
Phew! My finger is
The tutorial video next week will be about backups and song transfers. That might clear a few things up.
First, the export function is meant to immediately transfer songs between devices. So I don't see why anyone would need to remember which songs are in a file. You select the songs you want to transfer, export them, Airdrop them and directly restore them.
If you don't have the beta version installed in parallel to the normal version, you can just tap on a .stsa file and it will open ST3 and import all songs in that file. When you receive a .stsa file via Airdrop you can also directly select ST3 to open it with and import it.
If you export a whole playlist with songs, the file will be named after the playlist.
The reason why I chose to not overwrite songs in ST3 when loading an .stsa file is that in my view it will most likely be used to transfer setlists between band members. There is a high chance that you already have a couple of these songs on your device and they contain your lyrics, midi, whatever. It would be fatal if loading the .stsa file would replace your own settings with those from your bandmate.
So if you want to use this transfer option to move some files between your own devices just delete the included songs on the target device before opening the .stsa file.
- Edited
peter First, the export function is meant to immediately transfer songs between devices. So I don't see why anyone would need to remember which songs are in a file. You select the songs you want to transfer, export them, Airdrop them and directly restore them.
It sounds great for some users but it has major flaws for others.
It works for those transferring files from one device to another if they don’t already have those songs, then it works efficiently, but for people that use multiple devices like myself, I use iPad to perform iPhone to playback my backing and iMac to do some editing when at home, and I edit on all three devices whenever and wherever I choose for convenience and efficiency of not wasting time, I also use my iPhone as a backup device for my iPad and I use it as an extra device if I have a backup singer, this way of transfer is very narrow-mindedly created.
As it makes you remove something before placing the new version and yet when you create the .sata file you can not see what’s in it anymore so if you choose to shift or copy multiple files and you create a number of these transfer files to later update your devices you are stuffed as you don’t know exactly what songs they contain and what songs you need to remove so you can have a successful transfer.
This could all be fixed if you get a prompt and options to make choices as you are doing the transfer, like, this [song (Love me tender) already exists do you want to REPLACE or DUPLICATE this song? REPLACE ALL or DUPLICATE ALL ] now you have a system that quickly caters for all users, and it’s very efficient as it does things automatically for you it does not make you search to hunt down 12 songs amongst 10,000 songs then manually remove them, because I use ST3 as my music librarian and as my performance device SONG is my storage for everything , playlists divide these songs in to useable categories , everything is streamlined , by having to hunt for songs to delete them first makes me very nervous as a user, I’d rather the computer do this for me and just get it out of the way as soon as possible than me trying to figure out which song goes with what? It’s time consuming and stressful on the brain which is thinking about MUSIC.
I would say you will have more solo performers or just music lovers using this software than full on bands as a lot of bands run full on live anyway and this is way beyond them so catering for the majority makes more sense.
Anyway I am like a pig in shit at the moment, great work Peter it looks like the looping is here and working well I knew you could do it, we’ve certainly come a long way from ST2 even though the software seems bloated now it still beats everything in its class by miles, I noticed a few OnSong users switching to ST3 you wait when they all discover looping facility I can see a massive transfer coming , you deserve a great reward for your efforts all the best mate!
Cheers Damir
- Edited
Your use case will be addressed in version 3.7 which will introduce automatic iCloud sync of all your devices. Anything you edit on one device will automatically be synced to all other devices. This will be another killer feature if I manage to pull it off.
peter First, the export function is meant to immediately transfer songs between devices. So I don't see why anyone would need to remember which songs are in a file. You select the songs you want to transfer, export them, Airdrop them and directly restore them.
Thanks this works, but in my case the attached PDF files to Std Songs were not available on the destination device. PDF-Documents folder on the destination device is not updated. First time I did that, no overwrite possible. btw on my destination device, the complete folder is even not created...
Also like Damir, an Update or Overwrite dialog option for each song during the import would be great. For example ForScore is doing it well. (and even propose a duplicate option)
Yes, I am aware of the pdf problem with exports. This will be adressed in update 3.6.1.
peter Anything you edit on one device will automatically be synced to all other devices. This will be another killer feature if I manage to pull it off.
Hoping this will be selective, maybe per playlist? For users with a large library of break music, syncing all this music might not be a good idea.