SmellyOrc

Seems to me that the current language you're using right now (something something version 4, no?) is just very inefficient. Would upgrading it to the latest version make any such changes easier to implement in the future?

If you're using a notebook/laptop, you know it has USB ports that you can use to hook up a mouse, right? :huh:

If you're using a desktop and still using a touchpad, you'd better find a mental hospital. ;)

If you don't have a scroll wheel on your mouse,

WHAT YEAR IS THIS?

I've uploaded a new version using the same link. I've fixed a few chords. It does sound pretty much like the song now, in my opinion. Except for the part where it goes 4-4-4-466 on the sixth string (changed that to start on the fifth string).

Used Riffstation to check the chords, and everything's 100%.

https://www.dropbox.com/s/rx3vcpcwhryc50q/Xandria_Dreamkeeper_v1_p.psarc?dl=0

In the meantime I've released the song, record page here if anyone else has any comments, oh 1 other thing, regarding hand shapes / finger positions, is there a way to define them in EoF as default, so they are automatically updated in any future songs?

You will have to edit the "chordshapes.xml" file in your EoF folder (the one that contains eof.exe, not your project folder). I have no idea how to correctly add in chord(shapes), so you'll have to study that on your own. Or ask @@raynebc

Okay, different type of testing needed this time! I "fixed" (at least, I hope I actually fixed it :D) a guitar pro tab with a stupid tuning (BADGBE, really?!), and I want to know if I did it correctly. So people with good ears: help me! I want to know if I used the right chords, or if I'm completely off.

Song is in D Standard.

Xandria - Dreamkeeper - https://www.dropbox.com/s/rx3vcpcwhryc50q/Xandria_Dreamkeeper_v1_p.psarc?dl=0

Oh, whups, my mistake! Works just fine with that enabled.

This time around, 5/8 time signatures are not imported/handled correctly (bar 162 and 165 for example):

http://puu.sh/hwJpz/f1b2e7f167.png

From guitar pro file:

http://puu.sh/hwJrm/f2e8943c26.png

GP file: https://www.sendspace.com/file/5uwi1j

Midi file: https://www.sendspace.com/file/r9f1ju

 

I've been thinking that for short bends that setting the bend point actually 2/3rds into the length of the bend

It would be easy for me to change all bends with no tech notes to put it 2/3 through the note's length, but making it different based on how many beats long the note is adds more complexity. Any other folks have thoughts on this?

Yes. Use tech notes. -_-

This is what your tuning window in EoF should look like for B Standard tuning (7 string with the highest string dropped):

http://puu.sh/hijRX/21fbe5e972.png/ss%20%282015-04-18%20at%2006.39.30%29.png

And the tuning that is set in EoF, is the tuning that the song will use. Setting a different tuning in the toolkit will only lead to getting a different tuning in the menu, but not in the song itself. Though I believe in the later toolkits, this setting is actually ignored.

EDIT:  If you need to blow smoke then please go to the bathroom and do it in private.

Maybe it's because it's the internet, and sarcasm and whatever aren't well transmitted... but are you implying I'm making this up or something?

All I know is, I get the error using the latest build, and when I use 2.6.0.04174fc7b, adding the arrangements the EXACT same way, using the exact same tones in the exact same place, everything works fine.

@@SmellyOrc The check box "If checked, tone slots are disabled to prevent autotone failure", is alerting you not to make any changes to the tones (names).  I will have to see if I can modify the code to accommodate the the types of tone changes you are showing above.

 

So are you using toolkit "Load Tone" button to replace (change) these custom EOF tones?

 

A temporary work around should be to rename your custom tone *.tone2014.xml file to match the custom tone names that you used in EOF and then Load Tone in the toolkit.

It doesn't matter if i load the tones before or after i add the arrangement, I get the same error.

Also, I have ALWAYS used generic/descriptive tone names in EoF, only to replace them with the real tones (with different tone names) once in the toolkit. Why? Because I don't know beforehand which tone(s) I'll use. I'm NOT changing that. That's bullshit :) Worked just fine with 2.6.0.0. If there's a change in that behaviour, that's a downgrade/downdate, not an upgrade/update.

On import:

http://puu.sh/hg6pK/9e5f13c43a.png

After changing to the right tones:

http://puu.sh/hg6ux/7ce09dc13f.png

Saving goes fine, then when generating:

http://puu.sh/hg6xj/d0b84c9886.png

And yes, all the tones are defined. They all work. I've released the CDLC as generated using 2.6.0.0 (Nightwish - Edema Ruh), and all the tones work just fine.

The .xml file is generated by EoF, where I did define the tones:

http://puu.sh/hg6KQ/727e46e1d1.png/ss%20%282015-04-16%20at%2006.53.56%29.png

No user changes were made to the xml.

Tone list in the toolkit:

http://puu.sh/hg6Sd/c737fa5afe.png/ss%20%282015-04-16%20at%2006.56.07%29.png

Link to the XML:

https://www.sendspace.com/file/e58d1f

With the last builds, I have had a problem with using more than 1 custom tone in a song. Gives me an error upon generating: Undefined tone name. Goes as far back  as build 8e53d3ccdf. 2.6.0.0 (rev 4174fc7b) Works fine with the exact same setup. Saving the template in that old build, and then opening it in a later build and generating a package also works.

The latest builds also ask me to give a name to every tuning I add, even if it's already in the list. So, if I add an arrangement in D Standard, it'll pop up that window, with every string already at -2, which is correct, but still asks me for the name. This also goes back to build 8e53d3ccdf.

Toolkit version: c37d42bd9b

I get a new error when I want to save a template as an XML:

http://puu.sh/gSQZk/77bfa908f2.png/ss%20%282015-03-28%20at%2010.57.21%29.png

It also comes up with errors like: "Part REAL_GUITAR" does not exist, when I try to generate a package. It saves just fine when there are no arrangements added.

When I downgrade to eea374be0e the errors are gone, and the toolkit saves the file just fine.

I noticed a bug in EoF: chords with a duration of a sixteenth note are truncated to 1ms, even with the truncate short notes preference off.

 

If you're able to find any unused keyboard shortcuts that seem like they would be a good fit, let me know.

Maybe Ctrl + C(from Catalog)?

Oh wait.....

Anyway, thanks for your awesome work, raynebc!

Yes, it was generated by EoF. It was my own custom, so I had no need to unpack a file. Anyway, I deleted the file, and had EoF write a new one. That one went fine in the DDC. I guess there's a problem with EoF not correctly overwriting existing files?

I used the DDC tab from the toolkit (a9d2fe5b) on an XML file generated by EOF. I've checked the XML file, and there is no content after </song> besides a single enter. I've uploaded the XML file here: https://www.sendspace.com/file/04f02j

Edit: XML file is generated by EoF r1377, the latest one atm.

Received this error when adding DD.  Song works fine.  Any ideas what I can do to fix it?  Thanks.

 

http://i.imgur.com/mDRAR6X.png

Getting the same error:

http://puu.sh/gJWmX/b7bd27fa0e.png/ss%20%282015-03-21%20at%2010.48.35%29.png

Maybe allow the user to change it him/herself my just click and dragging it to a lower/higher position?

If not, I'd only put "no guitar" higher up the food chain. The rest, I couldn't care less about.

You can use Part_Real_Bass_22 for a bonus lead or rhythm. Just Set it to 6 strings and 24 frets max and you're off!

That would work as well.

Would it be a good idea to have sometihng like the "add metronome arrangement as bonus arrangement" function, but for DD? So, a "add DD as bonus arrangement" function when adding an arrangement? I hate DD and I don't include it because it's just an extra step, but if that step is just enabling that function, I can see myself using it.

Actually, it looks like there was an issue with the tone itself. I tried a different tone, and that one worked. So now I'm investigating why that other tone won't work.