|
Post by italianstal1ion on Jan 18, 2012 17:56:33 GMT
I would like to mention something important. I've noticed that if you chart with Feedback dB, adding sections doesn't require you to do [section <section_name>], since Feedback already writes the events like such. And since Feedback navigates faster around beats, I would recommend you guys to use it when adding sections, cause it would probably save some time, and it would prevent from some event writing errors to happen. You still need to use Chart2Midi2Chart to convert the charts to midi, but I guess that anyone that knows how to chart should have that Java program anyways. EDIT: Actually I remember if you do so, it would probably remove all the real instruments from the chart, so I guess you shouldn't do that, unless you add in the sections BEFORE charting the song. EOF has a "Feedback" import feature, so no need to deal with Chart2Mid anymore. And you'll need to use EOF to do pro notation anyway. By the way, EOF imports "sections" marked in Feedback as "section 'yourtitle' " which I'm not sure if that works in Phase Shift. (Ex. If you name a section in Feedback "[verse_2a]" it will show up in EOF as "section [verse_2a]" not [section verse_2a]" like Phase Shift requires it to be) Maybe what you meant is to mark Events in Feedback? (I know this might be picking hairs but feedback has both) and label the events "[section verse_2a]" so that EOF does not put the extra "section" label in front of it. I hope this is making sense.
|
|
|
Post by raynebc on Jan 18, 2012 18:46:10 GMT
Here's an excerpt from a Feedback chart file:
[Events] { 286080 = E "section Gtr Solo" 319680 = E "section Bridge" 322080 = E "end" } I checked a couple dozen Feedback charts I happened to have accumulated, and none of them seem to have any section events with brackets in them, so it doesn't appear Feedback ever added them automatically. I did see a chart or two with animation events in brackets though, such as:
0 = E "[music_start]" I could probably have EOF modify the section events that are imported by ensuring they are properly encapsulated by brackets, and removing the "end" event. Or should the "end" event be kept?
|
|
|
Post by nerd42 on Jan 18, 2012 19:55:10 GMT
|
|
hotzin
Yorkshire Terrier
Posts: 53
|
Post by hotzin on Jan 18, 2012 21:30:19 GMT
I would like to mention something important. I've noticed that if you chart with Feedback dB, adding sections doesn't require you to do [section <section_name>], since Feedback already writes the events like such. And since Feedback navigates faster around beats, I would recommend you guys to use it when adding sections, cause it would probably save some time, and it would prevent from some event writing errors to happen. You still need to use Chart2Midi2Chart to convert the charts to midi, but I guess that anyone that knows how to chart should have that Java program anyways. EDIT: Actually I remember if you do so, it would probably remove all the real instruments from the chart, so I guess you shouldn't do that, unless you add in the sections BEFORE charting the song. EOF has a "Feedback" import feature, so no need to deal with Chart2Mid anymore. And you'll need to use EOF to do pro notation anyway. By the way, EOF imports "sections" marked in Feedback as "section 'yourtitle' " which I'm not sure if that works in Phase Shift. (Ex. If you name a section in Feedback "[verse_2a]" it will show up in EOF as "section [verse_2a]" not [section verse_2a]" like Phase Shift requires it to be) Maybe what you meant is to mark Events in Feedback? (I know this might be picking hairs but feedback has both) and label the events "[section verse_2a]" so that EOF does not put the extra "section" label in front of it. I hope this is making sense. If you open any of the charts that you guys already added sections in Feedback, you are gonna see that they show up without the brackets, and without "section". The only thing that shows up is the "name_1A" <- Actual name of the section. By the way, I'm almost sure that the way the sections are said when you open a .chart with the notepad is just how it is before they are converted to midis. I think the way Chart2Midi, GHTCP and GHEX worked, is that they converted Feedback events (which are exclusive to .chart), into a format that is compatible with the games. So pretty much "section verse_A", would simply turn into [section verse_A] once they are converted onto midis. But as I said, Chart2Midi usually gets rid of events real easily, so pretty much unless someone figures out a way to convert midi to charts to midi without losing the extra instrument tracks like Pro Guitar and Keys (which are set in different channels, which you might notice when you open it in Feedback), using this technique would probably give it too many step requirements, which are unnecessary.
|
|
|
Post by vandorb12 on Jan 19, 2012 20:59:13 GMT
Is anybody actively working on "Dropping Out Of School" or "Fake It"?
|
|
|
Post by miguelangelx72 on Jan 20, 2012 17:11:24 GMT
well i work in fake it
|
|
|
Post by Inf4mousKid on Jan 20, 2012 20:29:41 GMT
EOF has a "Feedback" import feature, so no need to deal with Chart2Mid anymore. And you'll need to use EOF to do pro notation anyway. By the way, EOF imports "sections" marked in Feedback as "section 'yourtitle' " which I'm not sure if that works in Phase Shift. (Ex. If you name a section in Feedback "[verse_2a]" it will show up in EOF as "section [verse_2a]" not [section verse_2a]" like Phase Shift requires it to be) Maybe what you meant is to mark Events in Feedback? (I know this might be picking hairs but feedback has both) and label the events "[section verse_2a]" so that EOF does not put the extra "section" label in front of it. I hope this is making sense. If you open any of the charts that you guys already added sections in Feedback, you are gonna see that they show up without the brackets, and without "section". The only thing that shows up is the "name_1A" <- Actual name of the section. By the way, I'm almost sure that the way the sections are said when you open a .chart with the notepad is just how it is before they are converted to midis. I think the way Chart2Midi, GHTCP and GHEX worked, is that they converted Feedback events (which are exclusive to .chart), into a format that is compatible with the games. So pretty much "section verse_A", would simply turn into [section verse_A] once they are converted onto midis. But as I said, Chart2Midi usually gets rid of events real easily, so pretty much unless someone figures out a way to convert midi to charts to midi without losing the extra instrument tracks like Pro Guitar and Keys (which are set in different channels, which you might notice when you open it in Feedback), using this technique would probably give it too many step requirements, which are unnecessary. well i have the chart2midi program with me i could have it sent so it would be embedded to eof worth a shot right? btw there were 2 versions made an exe and a jar file i think the exe would be best even tho i think its the only one i have dl.dropbox.com/u/47504442/Chart2Mid.exe
|
|
|
Post by miguelangelx72 on Jan 20, 2012 21:02:06 GMT
|
|
|
Post by asskickulater on Jan 20, 2012 21:08:55 GMT
looks like were down to one song and one part.
|
|
|
Post by David on Jan 20, 2012 21:15:58 GMT
Thanks! List Updated!
One left. . .
David
|
|
TDPNeji
Chihuahua
Thunder Dragon
Posts: 48
|
Post by TDPNeji on Jan 20, 2012 22:55:39 GMT
Awesome. One track for one song to do left. So, with this progress, would the release date for v1.0 would be in February?
|
|
|
Post by David on Jan 20, 2012 22:59:26 GMT
1.00 is out for people who helped chart the songs. 1.01 will be out soon after the last song is done.
Thanks David
|
|
|
Post by vandorb12 on Jan 20, 2012 23:27:31 GMT
So, is anybody working on the last song? I don't want to rain on anybody's parade.
|
|
|
Post by asskickulater on Jan 21, 2012 1:38:56 GMT
1.00 is out for people who helped chart the songs. 1.01 will be out soon after the last song is done. Thanks David haha what can we expect form 1.01?
|
|
|
Post by Oddbrother on Jan 21, 2012 1:49:50 GMT
haha what can we expect form 1.01? No, please. Just surprise us. ;D
|
|