Jump to content

Latest EOF releases (9-26-2020)


raynebc

Recommended Posts

Hi,

 

I made a short vid to help explain this problem of EoF messing up the end of charts when the tempo is changed.  I think it occurs when you change the tempo more than once in a song, but I'm not positive.  It is common enough for my workflow to be designed around this issue i.e. set up the beat map then re-import.

 

http://youtu.be/uvaWgyt6E-U

 

I don't know why it didn't record sound, but you can see that it's messed up the end of the chart and when I re-import it sorts it out.

 

It is pretty common and happens (to me) a lot, but I know that you are going to ask for the specific GP file so here it is

 

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

 

What I did

 

-Import on 120

 

-Changed it to 96 as per GP file

 

-Changed again to 91 a few bars in when I realised 96 was too fast

 

-Continued setting up the beat map from left to right, and when I got to the end the notes were squashed

 

-Re-imported the GP file and it gave me the full chart back

 

 

I was using 1355, but it's been going on for quite a few revisions now.  It really fkd me up a few times when I was less experienced (and didn't realise what was going on and how easy it was to fix), and I am sure it must really mess with some new charters heads...

 

 

 

Thanks for any help :D

Link to comment
Share on other sites

I'll check it out in the near future.

 

I think about note durations based on BPM so I can use notes lenght related to tab bpm.

EOF has logic scattered around in the GP import source file that has relevant math, but it assumes 4/4, just like those note length calculator links you posted. Around line 2699 of gp_import.c is where EOF processes the timings from the Go PlayAlong XML file and does the math to change the beat markers. From what I've been able to tell, determining the length of a beat (in milliseconds) in any time signature is similar to how EOF is determining it throughout the program, except the length has to be scaled by (4.0 / (Time Signature numerator)) to account for a quarter note not necessarily being one beat long. From what I remember, that's the logic I went with for the GPA import whereas the rest of EOF doesn't scale the length that way.

 

I made a short vid to help explain this problem of EoF messing up the end of charts when the tempo is changed.

I'll look into it.
  • Like 2
Link to comment
Share on other sites

found a few issues with a tab, a few things are not imported correctly and are missing

 

Here is the tab http://tabs.ultimate-guitar.com/m/metallica/the_unforgiven_ver10_guitar_pro.htm?utm_expid=18438345-117.Xl9Y1cGLRGGq9QYsTE9P2A.0

 

The mejor problem seems to be with the notes as small numbers as hopos. The hopos as normal size numbers seems to be imported correctly.

 

In measure 7 till 10 in Track Kirk - Acoustic the hopos dont get imported.

 

measure 17 in Track Kirk - Distortion the hammer on on the 10 does not get imported correctly, it gets imported as a 09 chord. It repeats a few times.

 

in measure 92,93,94 in Track James - Distortion the hopos dont get imported. In Track Kirk - Distortion its the same for measure 93,94

  • Like 1
Link to comment
Share on other sites

Before looking at it, those sound like grace notes. The way those are authored in the GP format, it would be messy to try to get EOF to import them so I would prefer not to tackle that at this time. If that's not what they are, let me know.

 

2 out of the 3 problems seems to be indeed related to grace notes but the problem at measure 17 that i described does not look like a grace note but i could be wrong.

Link to comment
Share on other sites

*bug with ctrl+]*

I've got a bug, when I select all notes and move them using this tech it combines\erases trailing notes.

I forget how to move notes like Push offset Up\Down for the bpm :(

I tried to reproduce this, but I couldn't. Could you send me a project with which this problem can be caused reliably?
Link to comment
Share on other sites

@@raynebc, not project related.
To reproduce bug:
set grid snap to 1/48
place sequence of notes on each grid lane(4 notes would be enough)

set grid snap to 1/4
select this notes
hit Ctrl+]
Done.

Notes merged according to gridsnap, but it should not affect note relative position in sequence, isn't?

Link to comment
Share on other sites

I'm not able to determine/reproduce a problem. I placed four notes that were 1/48 grid snap apart, selected them all and used CTRL+] several times and they all moved forward in increments of one grid snap, keeping properly spaced even when moving over tempo changes. When the end of the chart was reached, EOF didn't allow me to move the notes another grid snap forward anymore and the notes each remained one grid snap apart as expected. I guess I'd need more information about what's going wrong, perhaps a before/after screen capture.

 

EOF will allow the notes to move over other notes in the active track difficulty that aren't selected, but it won't run the fixup logic that would merge overlapping notes until you perform another function like changing tracks, adding/deleting a note, etc.

Link to comment
Share on other sites

@@raynebc, maybe I'm doing smth wrong?

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

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

also I have a suggestion about slides, haw about store slides like signed offset value related to note?
Like just 7slide up2frets instead 7 slide up 9 (if we change it to 9 - well have no slide :) ) it would be useull for those who tab a song in eof, ofc EOF can adjust sides when you +\- fret value and set undefined slide when open strum, but I think It's better with offsets like alternative exact or relative value. how do you like it? 

Link to comment
Share on other sites

I have a feature request that might take a while to implement: allow us to select individual strings/notes which are part of a chord, and apply individual techniques to them. for example:

 

http://puu.sh/c89f0/461901f0db.png/ss%20%282014-10-11%20at%2005.07.21%29.png

 

is imported as

 

http://puu.sh/c89oY/661c8965fb.png/ss%20%282014-10-11%20at%2005.10.12%29.png

 

As you can see, the bend is applied to both strings (at least, as far as I can tell), instead of just the first string. This limits our... creativity. Yeah. That.

 

Maybe something like, when you press alt + click on the string, you only select the string you're hovering over. Normal click = select all strings of that chord/double stop/power chord.

 

Edit: tech notes. Duh.

 

Also: the first note on the second string should have the "linknext" status automatically applied to it. Import bug? :)

Link to comment
Share on other sites

Another bug? I can't select some notes that not placed one by one(adjacent?) and mark them as tremolo.. Rayne, can you say that it's expected behaviour, when I select first note in song and then last note mark as Tremolo and it will mark whole song?

Link to comment
Share on other sites

Also: the first note on the second string should have the "linknext" status automatically applied to it. Import bug? :)

Maybe not a bug so much as a limitation. There are so many specialized ways notes can overlap and tie that it will be difficult to program for all of them.

 

Another bug? I can't select some notes that not placed one by one(adjacent?) and mark them as tremolo.. Rayne, can you say that it's expected behaviour, when I select first note in song and then last note mark as Tremolo and it will mark whole song?

If you can't select some notes, see if SHIFT+Pg Up/Dn correctly seeks to affected notes. If not, the notes may not be properly sorted or something and things may work a little strangely. If you change tracks or add/delete a note EOF should immediately do some cleanup which includes sorting the notes. I don't think the move by grid snap functions automatically do this cleanup after each use because it would cause notes to combine immediately when they line up with other ones that weren't being moved. I'm not sure if that's how people would want it to work but it's probably better that way for the sake of stability.
Link to comment
Share on other sites

May have been reported already but there is an import bug which causes extra notes to be imported.  It's like it imports extra "bass" notes, where there should be a single gem there is a "chord" of 2 notes, much of the time the "bass" notes is some stupid fret number like 38.

 

It's happened to me a few times recently, but this file definitely does it

 

https://www.sendspace.com/file/4fnqdd

 

At bar 25 you will see what I mean.

 

 

I went through previous EoFs and it's actually the change from 1341 to 1349 i.e. 1341 imports that file correctly and from 1349 it imports incorrectly.  I don;t know if there were any releases between them, that's the only ones I have.

 

 

 

Thanks :D

  • Like 1
Link to comment
Share on other sites

I found another GP import bug:

 

http://puu.sh/cD5H2/a21d57b602.png/ss%20%282014-11-04%20at%2006.07.00%29.png

 

As you can see, bar 161 imports correctly, but bar 162 is missing one chord. Also happens at bar 163 and bar 166. It also goes out of sync by a few bars around bar 166.

 

I've uploaded the GP file here for you to look at: https://www.sendspace.com/file/bapkut.

EoF file is here: https://www.dropbox.com/s/j76e1sgpfc8b12b/Mayan%20-%20Paladins%20Of%20Deceit%20%28Pro%29.eof?dl=0

Accompanying .ogg file: https://www.dropbox.com/s/igpclk05gdbnikf/guitar.ogg?dl=0

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. - Privacy Policy