Hello all. This information is for PS3 and the s/w is on the windows side.
Here is my list of Beatles songs that exhibited the loop-ending issue. Along with their midi and song lengths and the [end] event setting I used. I apologize that all of this info is not available for all the songs. I was part way through when I realized that I should be writing stuff down, but it was too late. Once you encrypt the midi, you cannot look at it again.
Thanks to BornGamerRob for his post on extracting the midi from a con file. Many thanks to Shroud who I have been PMing so I didn't look more of a fool than I am(better to be quiet and thought a fool than open your mouth and remove all doubt-Twain or Lincoln I think).
I did try method 1 from post 12 above on all of these, but it did not fix any of them. I tried the 'fix mogg that loops' on a couple but no dice.
My procedure is:
Click 'Song Analyzer'. This opens a new window, click 'File', 'Open song file' and then navigate if needed to your song directory. If you left everything as the default setup, just have your problem cons in the CONS directory. Click the song you want and then 'Open'. You will get a nice window that will show all sorts of info about the midi file. The one we need is the Midi length in seconds, near the top and the audio length in seconds near the bottom.
Nearly all the songs with problems have the midi length greater than the audio length(and even now I am not sure if this audio length is the actual length of the audio of the mogg file).
Then we drag the con file onto a blank area(other areas may work) of the C3ConTools window. Another window will open. Click the MIDI button and this will extract the midi from the con file and place it onto the Clipboard. You can then click on your destination folder and do a Paste. Do not close the other window or this will not work. You can close it after the Paste.
Start Reaper(YMMV but I kept reaper in the same Customs folder I installed everything into. I found this easier for moving files around and keeping track of the updates. Reaper then just uses the same con directory as the tools). You do not use a template or project for this process.
Click on Insert and then Media File at the top and then navigate to your directory and choose the mid file you want to use. You will get a Dialog box open for Import Options. Expand Tracks and Merge Source Tempo should both be checked and hit OK.
You may or may not get additional Dialog Boxes to choose Import 2-Channel MIDI as Multichannel on a single track. This did not occur all the time. I guess if I unchecked the Always prompt box, it would go away(a Reaper genius I am NOT).
If you double click the Event Track(and sometimes just a single click would work on some songs), you should get a window at the bottom below the one with the tracks. If you click one of the indexes, you will see the line on the upper window move to that position. At the bottom of the list is an index with a Text Event with a Parameter of [end]. This will be at the last time index in the midi file. Anything beyond that is what is thought to be the issue. You might notice another index event call 'All Notes Off'. This is sometimes on the other tracks as well and does not cause any issues even if it's position is after the [end] event.
Click on the line with the end event and notice where the indicator moves to on the upper window. There is also a nice large counter at the top of the lower window. This has both the position info and a time stamp on it. You will probably find that the time is past the audio file length. This is what needs fixing. if you double click the position box, it will turn blue and you can then change it. This position will look something like 104.1.99 which corresponds to 3:06.7 or 186.7 seconds of midi file time. If your audio length was 184 seconds, then we need to shorten the midi length. You can change the 104.1.99 to 103.3.99. I found if you input 103.4.0, Reaper would change it to 103.3.99 most of the time. These are the 'quarters' that Shroud is referencing in post 12. An event can occur at any time in the midi, but Beats happen on the quarters so our [end] event is best kept to quarters(or within the .01 that Reaper likes).
Now that you have moved the [end] event before the end of the audio length, you have to check all the other tracks to make sure that there is nothing happening in any of them that is past the new [end] time. Click/Double click on each one and look near the bottom. Change the position value of the last index to be before the new [end] event. In Venue it might be [ProFilm_a.pp] among other ones. There might be multiple events with the same position, just change them all. One of the most important is the Beat Track. If there are any entries past the [end] event position, highlight the row and delete it. You will notice that one of the bars on the actual beat track in the upper window will disappear. The last Beat entry should be starting at the quarter before the [end] event starts. I do not know what happens if you remove a few extra.
When you click on the instruments and vocal tracks, you are looking for the Text Event [idle]. Again if past the [end], change the position value. Again ignore the All Notes Off entry. There might also be an [idle realtime] entry. These are to tell the character animation to stop. Just change the position value to be before the [end].
When you have finished all that, you can go to File, Export Project Midi. You will get a Dialog Box. It should have Entire Project and All buttons at the top and Multitrack Midi File at the bottom. Embed Temp Map is checked. You can specify the file name, or just leave it as midi_export.mid. NOTE the program will not give you a warning about overwriting files with the same name.
Now this is for the setup that Reaper shows me. If you have watched pksages Lets Author twitch stream, he gets a Reaper window with lots of colours in the different windows. I have not been able to get mine to look like that.
So your now modified mid file is ready. At this point you might want to make a copy of it so you can change it later. At this point you need to make sure that your modified mid file has the EXACT same name as the one that was extracted from the con file.
And once again we use the wonderful C3ConTools. Click the PS3 Converter button. You get the PS3 Converter window opening. Click Encryption Options. Make sure MIDI to Edat Encryption is Type 3 and then PAL or NTSC. If you have(and you must have) used the converter before, the options remain the same. Click Encrypt Replacement Midi File(s), and a file window will open. You can then choose(up to 10 I think) the files you wish to convert. It takes the mid file and changes it to a mid.edat file. I'm not sure if the mid file gets changed into the edat or the edat gets created and the mid file is deleted, but once you do this, your mid file is no longer accessible. Unless you made a copy in case it still loops.
You can now copy the edat file onto the PS3 into the same folder as the original. Nothing else needs to be copied, this doesn't affect the mogg or the songs.dta file.
The next post will have the file names