Hello. At first let me thank you for your work. If I can get behind this and it works, then I will finally be able to make my own UltrastarSongs. Up until now the methods and programs used to create songs did really not motivate me to do so, but working in a DAW that I have some experience with, could help me a lot
So what I tried first now is to import a .txt of song that someone has already made, but that did not fit unto the mp3 /video I have. I want to edit and fix this.
I create a new folder and save an empty reaper project there. I also place the files (video, txt, mp3 etc.) into that folder (each have the same name and only different extensions).
The txt contains the correct names for mp3/video.
When I then try to import the txt with your script, the midi/vocals are created with page markers but the video / audio tracks stay empty.
Hi, thanks for your quick response.
I think it might have to do with german a german letter in the title ( Ü ). I ve noticed that the output .txt writes "ü" instead of "ü".
But that is not my main problem now.
I've loaded the txt I already got into reaper.
Then I added mp3/mp4 and started editing the notes. they were all wrong ^^ but nevertheless at least the lyrics were there and the page-markers etc.
In between my editing I've noticed that I had changed and cut the beginning of my mp3 file to fit the midi vocals in the txt.
Then I thought to myself: No, the mp3 of the song must be at exact zero in my project, like yours in your video. Then I moved the midi file to fit the mp3 without altering the mp3. The page markers did not move with the notes so I had to correct them.
After that I exported the project to an ultrastar txt, with your script, and ran a test in my ultrastar deluxe.
Result: The lanes which indicate the tones to be sung are correct, but the lyrics are messed up.
I will send you a pm with my files, so if you like to check, you can try it for yourself, I hope you can tell me, what I did wrong
You mean the import script break them or the original transcript was wrong ?
Quote:
The page markers did not move with the notes so I had to correct them.
To move markers with items, you should use Ripple Editing active on all tracks with move markers set to one (right click on the ripple editing button to see the settings).
For lyrics before export you can check them in the MIDI editor by double clicking on the MIDI items.
You will see that you have multi syllabic events like "zueinander", this is not how it should be written for ultra-star.
You have to split syllabus like zu+ein+and+er, and do that for for words (just like in uktrastar creator), and then when you use the lyrics script, it will place each syllabes on a different words.
So it is not the export which is wrong but the preparation
I don't see any .txt on the zip you send me, and no lyrics in project notes so not sure if the fact lyrics are not split is an import error or just a mis-preparation.
For the ü, I indeed see error but again without the txt hard to tell from where the error come. Be sure the original file written in UTF-8 though, cause the export is made in UTF-8, so it should work.
If it doesn't, you log in the console seems good, so you can at least copy paste from it to your file content.
You mean the import script break them or the original transcript was wrong ?
The original transcript had wrong pitches. It's still work in progress though.
Quote:
Originally Posted by X-Raym
To move markers with items, you should use Ripple Editing active on all tracks with move markers set to one (right click on the ripple editing button to see the settings).
Ok I will do that next time, but moving them afterwards cannot be a source of a problem?
Quote:
Originally Posted by X-Raym
For lyrics before export you can check them in the MIDI editor by double clicking on the MIDI items. You will see that you have multi syllabic events like "zueinander", this is not how it should be written for ultra-star.
Yeah, that is like they came with the original txt file. I did not know how it would look and left it as is, for the first try.
Quote:
Originally Posted by X-Raym
You have to split syllabus like zu+ein+and+er, and do that for for words (just like in uktrastar creator), and then when you use the lyrics script, it will place each syllabes on a different words.
I haven't tried the lyrics script, because the lyrics were already in the txt, but I will try it for sure. How does it work, does it simply set each syllable on each note?
Quote:
Originally Posted by X-Raym
So it is not the export which is wrong but the preparation
I'm still not sure if my problem is a result of the way the lyrics are written on the notes in my midi track, but i will try and experiment with it.
Quote:
Originally Posted by X-Raym
I don't see any .txt on the zip you send me, and no lyrics in project notes so not sure if the fact lyrics are not split is an import error or just a mis-preparation.
I thought you would create the txt yourself, with the files and your script. You don't see the lyrics on the midi notes? That's strange. Were is it saved then? In the rpp file the lyrics are (in a way) saved, if I open it with an editor I see them.
Quote:
Originally Posted by X-Raym
For the ü, I indeed see error but again without the txt hard to tell from where the error come. Be sure the original file written in UTF-8 though, cause the export is made in UTF-8, so it should work.
If it doesn't, you log in the console seems good, so you can at least copy paste from it to your file content.
Wouldn't the script just use the metadata when exporting from the project to txt? It's kinda strange that letters like "ü" were untouched *expect for one instance* in the lyrics part of the exported txt, but in the header (#) part it was changed into other code.
Last edited by MechanimaL; 12-29-2018 at 03:41 PM.
How does it work, does it simply set each syllable on each note?
Yes, just like in the video, it works on Project Notes content, and you have to write lyrics with Ultrastar creator syntax (meaning, split syllabes with a + sign, and using ~ if a syllabes have to be over several notes.
Quote:
You don't see the lyrics on the midi notes?
On don't see lyrics as .txt or as Project Notes. But yes I can see some as lyrics event.
Quote:
Wouldn't the script just use the metadata when exporting from the project to txt? It's kinda strange that letters like "ü" were untouched in the lyrics part of the exported txt but in the #Song part it was changed into other code.
Encoding issue can happen at every stage of the process. That's why the first step is to check that your original source file (the .txt) is written in UTF-8. UTF-8 is a format friendly with any characters.
ok thanks I've found out two things now: ultrastar does show the Ü and charakters like that correctly, even if some editor does not show it as this.
and for some reason some of the words in my midi track were marked as "text event" instead of "lyrics" and did not appear in the export - txt.
I'm now gonna sit down and try to learn lyrics formatting, so I can use it directly and correctly in the reaper project.
I think most of my problems result of the original txt and its lyrics formatting. Therefore I'm gonna send it to you as well. Thanks again, this is such a good project, I'm really looking forward to create many songs with it, once I've gotten into it 100%
*edit: I think its working now. I did not know about the [SPACE] you need after words and other details I'm finding out, it gets better step by step.
Last edited by MechanimaL; 12-29-2018 at 04:35 PM.
Some songs use - between the syllables others don't. I've not made up my mind yet
I've got another problem, but don't know if it has anything to do with markers or lyrics in my midi track.
I copy notes from the first verse to the second and they dont play correctly. Theyre kind of cut off. I can erase the note and set a new one at its place and still something is cutting it off, notes dont play to their given length. I clicked through many of the midi parameters but haven't found a reason for this behaviour yet.
Last edited by MechanimaL; 12-29-2018 at 06:00 PM.
I think the script use + as separator but maybe it also use - for compatibility.
For you midi problems this isnt related to these scripts so I cant really help there. If it 'sounds' different then it may be something with your VSTi, or your note velocity, or other things considered by your VSTIi to trigger different articulation if it does support it ... Things that are not important in this workflow (the import/export doesnt care about the VSTi you use, as long as the midi is good). It seems specific to your VSTi and its setting. Take a close look and try to find the difference between those notes :P
So, I finished my first song. The midi-notation problem must had something to do with my project or the imported txt file, at least now -on the second song - it did not re-occur.
This time I did not have an existing .txt to import. Only a vocals-midi.
So the Midi is now in place and correct. I had to tempo-map the song, because the time signature is not constantly the same. But it in the end, after I got the timing in there, the midi fit much better, than if I had ignored and just used an average bpm or sth like that.
What I'm not totally sure now is, how do I add the lyrics/text events at each note? I think I have to this before I can import the lyrics?
@MechanicaL
As explained above and to avoid to have to manually edit each lyrics event manually, I lade script to insert lyrics based on Project Notes and split at syllabes with + character lyrics.
Just edit in project notes and run the script untill its good :P
yeah sorry, I did look at your .gif again and installed also sws, to get into project notes window like you did. now I'm experimenting with it, looks like it's gonna work
If there's a gap(silence) at the beginning of a song, it would mess up with the time signature? would you suggest to always cut the gap? then I dont know how to not - re encode the mp3, which always means further loss of quality.
just good to know for future projects, what would be the best way.
if the imported txt does not start at the right time, is there a way to move the markers together with the midi file inside the project? I did not find it on the marker-wiki page
@MechanimaL
Move your MIDI item with Ripple Editing active (with the option to move markers, accessible via right click on the button).
This will allow to move the item and the markers next to its position with it.
ok sorry, you've had already answered this before x)
and thanks to x-raym the midi notes muting-problem could be solved: there were "note off" events, that can be deleted in the events editor.
x-raym: your mailbox is full btw
the script update worked for like half of the file I still had to clear out note off events, dont know if you were trying to tell me this, with that sentence I did not quite understand ^^
another thing I've noticed. I imported an existing folder (mp3, video, txt) into reaper and reaper automatically changed the rate of the audio+video-track.
so i think, maybe the script could be updated to set the mp3/video-tracks at timebase, not bpm based, so this won't happen?
@MechanimaL
My inbox went full very quickly this night, that's why I prefer public discussion (PM are nice for private data), so I invite you to go back on the public thread.
I think it's also okay to post your link there, these are not sensitive information I think and you can still delete the file once I get it.
Quote:
the script update worked for like half of the file I still had to clear out note off events,
That's weird it should have delete them all, I tested with your file and it works, so maybe you didn't run the script update but an old version of the script ? Script should be 1.0.2 now.
And here the file I get from it (see attachement).
Quote:
reaper automatically changed the rate of the audio+video-track.
This is weird, I don't see why (and how muchà it would change the tempo... are you sure this temlpo change doesn't happen after the import when you were editing your time signature ?
But yes my default is Time for all tracks, but that may be the case for other people so I set this tracks to Time too just to be sure. Update to v1.0.3 :P
@MechanimaL
My inbox went full very quickly this night, that's why I prefer public discussion (PM are nice for private data), so I invite you to go back on the public thread.
I think it's also okay to post your link there, these are not sensitive information I think and you can still delete the file once I get it.
That's weird it should have delete them all, I tested with your file and it works, so maybe you didn't run the script update but an old version of the script ? Script should be 1.0.2 now.
And here the file I get from it (see attachement).
This is weird, I don't see why (and how muchà it would change the tempo... are you sure this temlpo change doesn't happen after the import when you were editing your time signature ?
But yes my default is Time for all tracks, but that may be the case for other people so I set this tracks to Time too just to be sure. Update to v1.0.3 :P
good job man! I keep working and will come back if something is needed but I think I got over the first obstacles and you helped very well, so thank you.
Is there a way to update the ingame project lyrics from the ones on the midi notes? I want to use another way writing with ~ etc. but have already edited the lyrics on the midi notes and the project lyrics are the old ones.
so in short: the reverse function of your script to put project lyrics to midi notes.
the reverse function of your script to put project lyrics to midi notes.
I 'm don't understand, what is a reverse function ?
Can do you have and where do you want to go ?
You can directly edit MIDI lyrics if you want without going through the project notes lyrics, they are not the one used for export. Only MIDI lyrics data.
so that the lyrics in the project get updated from the ones on the notes?
but its not that important, my main problem now is, that I've got some notes overlapping in the ultrastar-game. so I go fix them in reaper by shortening or moving them. but after I fix them, other notes come out as overlapping, that I have not moved. something is interdependent or I dont know is it random?
also, might it work better with higher BPM rates? Ive noticed that for example in one song creator program you would double the bpm given by a bpm detector. could this help and lead to less overlapping? the notes dont overlap in the reaper project. its a project were I had to use multiple bpms, because its not recorded with a metronome..
@Mechanical
As shown in my video, it should be fine with flexible tempo, multiple time signature and whatever tempo it is.
One trick for ultra star MIDI notes is to not have them touch each other, but always leav some times, for consonant sounds and other non tonal element (like breathiing etc), not as you would usually write a perfect score.
Quote:
, other notes come out as overlapping, that I have not moved. something is interdependent or I dont know is it random?
This really sounds like user error.
It's been a while since I didn't use these scripts in context though, but last time I tried the export itself was fine. :/ I don't use them on that much cases, I hope anything hasn't been too overloocked (like the All MIDI Notes Off Error). Impossible to say without a full project folder. Last time I tried, it was doing a perfect 1 to 1 conversion from ultrastart to reaper, and from reaper to ultrastart, with already made songs.
Quote:
so that the lyrics in the project get updated from the ones on the notes?
I didn't make such things, as you can surely use other ultra star song creator to extract the lyrics in the desired format if needed.
Thanks! Just weeks ago I was looking for something like this and I will be looking forward to trying this out on the next occasion I have the need!
Thanks again
-W
__________________
"if DAWs are religions, REAPER is atheism" - The big J
__________________
Windows 10x64 | Asus Z170-a i7, 32GB ram | RME-Digiface USB
@Mechanical
As shown in my video, it should be fine with flexible tempo, multiple time signature and whatever tempo it is.
One trick for ultra star MIDI notes is to not have them touch each other, but always leav some times, for consonant sounds and other non tonal element (like breathiing etc), not as you would usually write a perfect score.
This really sounds like user error.
It's been a while since I didn't use these scripts in context though, but last time I tried the export itself was fine. :/ I don't use them on that much cases, I hope anything hasn't been too overloocked (like the All MIDI Notes Off Error). Impossible to say without a full project folder. Last time I tried, it was doing a perfect 1 to 1 conversion from ultrastart to reaper, and from reaper to ultrastart, with already made songs.
Of course my notes don't touch each other, but some things I've noticed:
- Notes overlap in Ultrastar. Then, when fixed, new problems occur, as if something was interdependent
- The output bpm also changed from one to another export, but I did not change anything on the bpm(s) in reaper, the only thing I changed were notes and maybe markers
Maybe the bpm was not constant enough it differs from like 62-68.
I'm tired now of over and over fixing and checking the result and all the new errors. I'm gonna try to fix the re-imported txt with the fixed bpm, somehow I've got the feeling that might work, I will check back with the result.
Another project, with a constant bpm, worked without those problems.
Last edited by MechanimaL; 01-07-2019 at 12:45 PM.
- The output bpm also changed from one to another export, but I did not change anything on the bpm(s) in reaper, the only thing I changed were notes and maybe markers
I remember that the exported BPM in the txt was supposed to be very high to be very high to be accurate (it doesn't matter if it change though),
and I think I made something like export as the BPM of the current cursor position, so yes this is where your different BPM can came from.
Regular ultrastart songs are about 400 BPM fixed BPM, and indeed 62 is pretty low, so I wonder if it could worth to try to do it on double the BPM (by editing the project or maybe by forcing output BPM at 400 inside the script)
Quote:
I'm tired now of over and over fixing and checking the result and all the new errors.
I can feel you ^^ That's the everyday tasks of a scripter :P If make more Ultrastar songs I'll surely see things which needs to be optimized. Or maybe if you send me project files as asked above.
Quote:
Another project, with a constant bpm, worked without those problems.
I guess with higher bpm there are smaller steps to be processed inside ultrastar. I did the "detect and set by selection" - bpm- detection- way and that's how I got the 6x bpm.
How is the easiest way to get the project to the double bpm and remain midi and markers as they are? If i set it to double the value and then the midi track to rate 0.5 it fits, but the markers are all off after bpm change and I dont know if the script will work with other midi item rates.
I guess it will be good advice to anyone not to use the quarter-note- bpm like you normally would (or maybe would) but the eighth. so like at least double the bpm. how to achieve this when setting the bpm yourself with the reaper detection method I dont know, but it's not a problem of your script.
and thanks for your help. your work for this is really extraordinary, everything is far from bad
@MechanicaL
Can you try to replace line 37 of the script
Code:
bpm = reaper.Master_GetTempo()
by
Code:
bpm = 400
just to see if change anything for ultra star ?
A tempo of 60 BPM is fine, it is just UltraStar which is somehow meant to work with very high BPM (like 400+) to increase precizion of note placement (not a very good system but it is how it is done).
(for infos, Here my discussion about the team on the subject)
with the suggested changes and 400bpm none of the overlapping occured.
if the original bpm plays a role anyway (?) maybe multiplying it in the script with x6 or sth like that would also work. most of the songs are between 50 and 100 bpm aren't they? but as I dont know the inner works and dont need to know ^^ you will be the best to give advice
edit: ok I've read this
Quote:
just adjust the bpm to fit into something like 250 and 400. Anything else would result in either not exact notes positioning or too much work when creating / editing the file.
from the discussion at usdx github.
i think for editing in reaper, where it is way more easy to put the notes on the exact original timing, there is no harm in smaller steps than 150ms. so that argument will work for the clumsy other software methods, but I see no reason for restricting bpm with the use in reaper? so 400+ is the way or even more ?
Last edited by MechanimaL; 01-08-2019 at 04:29 AM.
with the suggested changes and 400bpm none of the overlapping occured.
So everything is solved ?
I updated script to v1.0.5 with force BPM at 400 for export.
In REAPER, do your tempo map as you want. High BPM, Low BPM, it doesn't matter now from the script as it will take a fix BPM as reference (400). This is how UntraStar works, and this is why editors which works with this system aren't really handy with variable tempo songs.
@MechanimaL
There is a limit on precizion we can get in ultrastar, which according to those I talked too, was 400. Above seems overkill or could even create problems as far as I understood. 400 is already 1/400s precizion !
Now I've nearly finished another song, one that I did myself from the scratch.
Just while checking I've noticed that at one point, where I set a marker, the marker does NOT result in a line break like it should at one point. Normally in the txt there would be a "-" in the beginning where a new line is starting, but it does not do, even though in the project the marker is set. Do you have any idea what could be the reason?
Thanks.
After some months I've now come back to work on some songs again, some that are poorly done and probably some that have no version as of yet. Besides the fact that I've got to find my way back into the workflow of editing again, right with the first song I've tried to import I got an error message, which I hope, you might be able to tell me what to do??
Quote:
X-Raym_Import UltraStar txt.lua:127: bad argument #2 to 'TimeMap2_QNToTime' (number expected, got nil)
Scripts: Creating Karaoke Songs for UltraStar and Vocaluxe with REAPER (New: Viewer!)
Linear Mode
