|
Post by raynebc on Sept 14, 2012 17:30:18 GMT
New in the next EOF beta, it will allow you to mark pro guitar notes with vibrato status. This status is marked with Sysex phrase ID #10.
Also, could this thread be stickied?
|
|
|
Post by David on Sept 14, 2012 18:47:51 GMT
Thanks David
|
|
|
Post by David on Nov 10, 2012 20:22:59 GMT
Continued discussion from here: dwsk.proboards.com/index.cgi?board=suggestions&action=display&thread=1155&page=1Sorry about not replying I've been trying to think of another way to handle this. It seems if we are gonna go down this route we might aswell expand the whole system to allow for multiple instruments too. We had talked about this before to allow any kind of instrument part to be charted but have some kind of marker to state what charting method is used. Bascially you might was to have a violin instrument that is charted using the standard legacy guitar notation. Or you might want a harp part that uses the pro keys notation. I don't see this being a priority right now but it's worth thinking about in the meantime. David
|
|
|
Post by raynebc on Nov 10, 2012 21:33:19 GMT
That's fine, this is kind of a specialty type of feature. This was asked about for FoF a long time ago, but I'll let you guess if they ever got around to it The XML mockup I proposed would allow specifying the name, MIDI track makeup, number of difficulties, etc: <custom_tracks = "1"> <custom_track name="Distortion" type="Real guitar" difficulties="3"> <difficulty number="0" midi_track="DGUITAR_0"/> <difficulty number="1" midi_track="DGUITAR_1"/> <difficulty number="2" midi_track="DGUITAR_2"/> </custom_track> </custom_tracks> If a custom track was a 5 lane track, we could specify that in the type parameter of the custom_track tag. "Pro keys" or "Real keys" could also be the type. I needed to start thinking about user-defined custom tracks in EOF because it will be necessary for Rocksmith authoring, which uses a variable number of difficulties and the track names can vary (ie. "Single" for single note arrangements, "Chord" for chord arrangements, "Combo #" for arrangements using both single notes and chords, etc). I will probably gravitate toward authoring the original guitar parts, ie. "Rhythm guitar", "Lead guitar", etc.
|
|
|
Post by David on Nov 25, 2012 7:24:30 GMT
I'm adding a new song.ini tag to set the the HOPO Frequency directly.
hopo_frequency = x
If this is not defined or it's value is set to 0 then the game will use the defaults. Tick Per Quarter Note / 3
hopo_frequency will override eighthnote_hopo if both are present.
Thanks David
|
|
|
Post by raynebc on Nov 25, 2012 7:38:15 GMT
So a third of a beat is the default HOPO threshold? How does hopo_frequency work, is it just a new divisor (replacing the default of 3)?
|
|
|
Post by David on Nov 25, 2012 7:58:36 GMT
The Default frequency is a 12th Note. So you can calculate this by dividing the TPQN by 3. The new value is the delta ticks between the notes. From looking at the RB files they have a value setting it directly that overrides the auto one.
So if the delta ticks between the notes are less than the HOPO frequency then it's a HOPO.
David
|
|
|
Post by raynebc on Nov 25, 2012 8:50:00 GMT
This might be more complicated than many users like, because they don't necessarily know about the inner workings on the MIDI file, such as what time division it's using. For a typical EOF MIDI, the time division is 480, so if they wanted a HOPO to be anything within a quarter of a beat (1/16 note if the time signature is #/4), they'd have to define a hopo_frequency value of 120?
|
|
|
Post by David on Nov 25, 2012 9:25:45 GMT
I understand this could be confusing but the values in these RB files are not all perfect divisions so I can't use standard divisions. I guess you could have in EOF a simple system but that outputs into the correct format. And maybe a manual setting or a slider that update in realtime so you can just drag it to the point where the hopo's look correct. I guess you can have snap points to make it easier or something.
David
|
|
|
Post by raynebc on Nov 25, 2012 10:06:07 GMT
The easiest thing I can imagine is if Phase Shift changed that INI value n so that if a note is within 1/n beats of the previous note, it is a HOPO. It's simple to program (only adds one division to how you've implemented it already) and simple for chart authors to understand.
|
|
|
Post by David on Nov 25, 2012 10:24:12 GMT
This is going to require floating points if you want to do anything that isn't a standard division. Bascailly, there is a song bluzer gave me that requires a 95 threashold. For that you'd require a value of 5.052631578947368.
David
|
|
|
Post by David on Dec 13, 2012 21:04:05 GMT
OK, this may be a pain but I am looking to change the way Real drums is stored in the MIDI. Right now Basic, Advanced and Real are charted to the same track. I want to separate Real from the rest to allow for different charting methods to be available. Right now if you want to chart open notes on blue then you can't have real drum open notes because they are on the wrong lane. Plus I'm looking to add some more advanced features that would complicate the current arrangement too. In EOF it would just require duplicating the the Drum mode and limiting the features in normal and advanced. All the rest of the standard would remain the same for the time being.
What do you think?
Thanks David
|
|
|
Post by raynebc on Dec 13, 2012 22:27:25 GMT
So it would just be written as a different MIDI track (containing all the current notation), and "PART DRUMS" would just be neutered a bit?
|
|
|
Post by David on Dec 14, 2012 5:54:13 GMT
Yea, that's about it. We can go with the track name PART REAL_DRUMS_PS.
David
|
|
|
Post by vandorb12 on Dec 14, 2012 7:17:50 GMT
I approve of these changes, and I have a feeling oddbrother would like them, too.
|
|