Okay, I thought the syntax I was using was wrong but...[
midi@00:00.01
C14@3]
[midi@00:11.01C15@3]
this doesn't work for me at all.
Do not load next at the end of song
sorry,
[midi@00:00.01C14@3]
[midi@00:11.01C15@3]
I don't know what is up with the emoji or it just my machine?
apparantly : + P is an emoji.
Flee the only way i can think of fixing your delay need of endings is insert the ammount of silece you require on the end of all songs you need this delay.
It might be your quickest way without stuffing around , if you are running on an ipad the software to insert silence i can strongly recommend is (Twisted Wave) its quick,simple and easy to import and export back to ST3, this will fix one of your problems, but changing program change midstream in a song is something i never use but expect it to work as you describe, you should be able to place a program change at a specified time in the song so you can change sounds as required otherwise whats the point.
If this isnt working than Peter needs to know about it , but its also possible you might not be entering the correct command, all these things are so touchy if you have one little thing wrong it just doasnt work.
Hope you can work out a system that works for you.
Cheers Damir
Flee i was going to ask whats with the emoji?
Thats one of your problems, I am sure Peter will work it out for you but i am very interested in the immediate load and highlighting of lyrics , and the immediate program change, this definitely would affect users using program changes and be more nuicance than practical , i never thought of this problem, my frustration was a lesser one where the new song loaded and immediately highlighted the first lyrics line without the song started, this seemed wrong to me , but Peter had a reason for it i cant remember why, but your issue is a more important one as you dont want to change your program change as you are finishing a song but then again it would be nice to have your program change occur at start so you can play the correct sound before you hit start, so to conclude my feelings, you would be better off just adding silence to the end of songs you expect to have a longer ending and then using the ending trim control to fine tune your actual endings.
Lets say you leave an extra 30 seconds of silence on all your songs as a standard, you can then use the end trim to perfectly tailor your individual songs to your liking and when the next song loads it auto changes your program change at the time you need it ready for the next song start.
This will definitely work for you and standardise a method when finalizing your songs just make sure you have enough silence at end of every song to cater for the longest endings.
It means a little more work for you but it looks as though you are putting in a lot of effort in programming you show this would not be that much more effort.
Good luck
Damir
Damir Just another thought, if you program your STOP/START button to cue up next song when you hit STOP, this will eliminate end trim requirement, you just add the ammount of silence you think you need the most on all your songs , this then allows you the freedom to adlib your endings till the cows come home and when you hit STOP button it automatically loads up your next song and sets up your next sound or whatever, then hit START and youre off againg to finish the songs as you please, this is probably more flexible and less work but you do need to insert silence at end of songs, and as long as the STOP/START button setting suits you it will work, i use my as PAUSE and continue but in your case that might not be an issue at all.
I appreciate your help Damir but why isn't Peter helping with this problem?
I can easily work around the issue if the midi commands actually worked as detailed in the manual per MIDI Commands.
[midi@01:20.00: PC5@3]
[midi@01:50.00: PC30@3]
the application blows right past these and does not execute or else it executes then all at once at the beginning.
I'm running Catalina on an Macpro i7 16GB.
What are the MIDI stop and Pause commands for? The do not stop or pause the playback when embedded in the lyrics.
A simple command like "PAUSE 00:10.0" command in the lyrics would be helpful if implemented like pause playback for 10 seconds then resume.
So why arent the MIDI commands working correctly for me? Am I using the syntax incorrectly or are the broken in code?
Flee I’m sure Peter will help as soon as he can but I thought the midi commands were there to control external equipment like program changes for midi keyboards or lighting desks or guitar pedal program changes or perhaps Control Changes, I don’t think the text edit midi commands were meant to control the actual ST3 , but I could be wrong.
I use to extensively use midi years ago but now I keep things real simple to save time.
There is a global delay start but I don’t think that’s going to help your needs.
I agree with you if the midi commands worked as we expect you should be able to achieve everything you need, surely someone else uses midi commands and this issue would have been discovered by now, as I don’t use midi to control anything I can’t confirm if it’s the software or the way you are trying to use it is incorrect or perhaps not possible.
Hopefully Peter will help you soon he must be really busy as he normally responds very quickly.
Good Luck
- Edited
Sorry for the late answer. I usually check the forum for new posts at least once a day but yesterday I was working hard on update 3.6 and completely forget to check the forums and today I just turned on the computer.
As far as I can tell your syntax is wrong. There needs to be a whitespace after ":" and that's also the reason the forum is showing this smiley. Also there can only be one MIDI tag per line and it must be the first tag in that line. Something like [00:03.00][midi:PC14@3] will not work (2 syntax errors in one line).
So the correct command for you is this (note the whitespace and nothing else in the line):
[midi@00:00.00: PC14@3]
As an alternative you could send the MIDI when playback starts by using:
[midi@play: PC14@3]
@Damir MIDI commands with timecode 00:00.00 are not sent when the song is loaded. They are only sent during playback. Only scrolling and highlighting also works when no playback is running. So simply loading a song will engage the highlights for timecode 00:00.00.
peter yes I’ve been using the 00:00:01 timecode as my first line timecode and it’s all good, and it’s good news that the midi was entered incorrectly, it means we’re all happy and you can concentrate on the looping feature, I can imagine it is very difficult as if it was easy someone else would have done it by now so good luck with it and if there’s anything you need help with that we can help you just ask, if anyone can do it you can.
Cheers Damir
Thanks for the reply. You are correct! I see now that I was also using a colon after midi. [midi:00:00.1 PC14@3]similar to the [midi: PC14@3] command without a timed event. It is working correctly. Now I have to edit 80 songs and get back to testing/practicing. Thanks!
@ "Flee" # p7523
I had kind of the same problem.
Sometimes someone get feelings and play a longer solo or sometimes we let the audience sing along for a couple of refrains in the middle of the song. Then it might happen that ST3 reach end of song before the band, and therefor change patches of synths, lights, FXs etc ...
I "solved" this by setting the length of the song longer that ever expected and tuned the scrolling to respond correctly.
Then I can select the patches for synths and FXs when I select the song, so I'm ready for next intro, and select patch for the lights at "play" with [midi @ play: ....]
I've watched most of the ST3-youtube-tutorials, that's very good and learned several how-to's..!!
I'm eager to see what Peter has saved up his sleeve for the next version.