@@mr.guitar_tab Im sorry but if you look at Enrique’s hand, you can see him doing a barre in the 5th fret. The tablature is therefor wrong. Please look more carefully 🙏
@@mr.guitar_tabyour "the notes are written correctly" only applies for the tab version because as mentioned before the classical score fails to spot a capo is used so in that score all notes are written 1 halfstep/fret to high and on top in the wrong octave. So you need a guitar with 24 frets (and an extra index finger to cover the 13th fret) to be able to play that "completely correct" score. In your latest short (pharaon) the same problem occurs. Again the classical notation failed to spot a capo is used so the classical score wrongly tells you to play every note 2 frets higher then the "matching" tab version (edit, you just posted a tangos of Paco with capo on 4 and the note version as expected ends up being 4 frets to high so it's official now, it structurally overlooks the capo and tells you to play the real pitch rather then the relative pitch so without capo it tells you to play an E, with capo on one to play an f, with capo on 2 to play #f. etc. That's not how a partiture should be written). This seems to be a recent point of concern (did you switch to another computer program?) so I repeat my first statement... Huston, we have a problem.
You might check your settings because unlike usual the program somehow doesn't adjust the fact a capo is used and a guitarscore should be written 1 octave lower.
@@arthurtigreat8929thanks for your reaction but I have no clue what you mean to tell. In above score the tab is correct but the score above is dead wrong by any means. It's annotated as if there is no capo so when an open E is played the tab corectly tells you to play an open E but the score above tells you to play an F on first fret. That counts for every note and that's why almost every note in that score has an added #. In short, the tab is annotated in E phrygian, the score above is annotated in f phrygian. On top it's annotated 1 octave to high, you won't find any note lower then the open D string. This is the only post that error occurs, in all other post it's done correctly.
@@ErikVanGoch I meant that for the guitarist, it is easier to learn the piece with the standard notation « as if » there was no capo. It is standard in classical guitar as far as I’m aware. The other videos features the « correct notes » because the program used automatically transcribed it. For this video perhaps the owner of the channel used another one, or just used the transcription of someone else.
Un grande maravilloso guitarrista un virtuoso de mis preferidos.
Excellent work as always. Thank you very much for your work.
♥️
Me encantan estos vídeos con tablatura .. gran trabajo
♥️
Amazing❤
The tabs at 0:44 are incorrect
It was checked. There was no problem. Please look more carefully🙏
@@mr.guitar_tab Im sorry but if you look at Enrique’s hand, you can see him doing a barre in the 5th fret. The tablature is therefor wrong. Please look more carefully 🙏
Yes, you are right. The notes are written correctly, but the tabs are written in the other place .♥️🌹
@@mr.guitar_tabyour "the notes are written correctly" only applies for the tab version because as mentioned before the classical score fails to spot a capo is used so in that score all notes are written 1 halfstep/fret to high and on top in the wrong octave. So you need a guitar with 24 frets (and an extra index finger to cover the 13th fret) to be able to play that "completely correct" score. In your latest short (pharaon) the same problem occurs. Again the classical notation failed to spot a capo is used so the classical score wrongly tells you to play every note 2 frets higher then the "matching" tab version (edit, you just posted a tangos of Paco with capo on 4 and the note version as expected ends up being 4 frets to high so it's official now, it structurally overlooks the capo and tells you to play the real pitch rather then the relative pitch so without capo it tells you to play an E, with capo on one to play an f, with capo on 2 to play #f. etc. That's not how a partiture should be written). This seems to be a recent point of concern (did you switch to another computer program?) so I repeat my first statement... Huston, we have a problem.
You might check your settings because unlike usual the program somehow
doesn't adjust the fact a capo is used and a guitarscore should be written 1 octave lower.
Hello my friend, it is written completely correctly, please check it again. Thank you for your opinion
@@mr.guitar_tab the tab version is correct, the note version isn't so please give that one another look yourself.
@@ErikVanGoch Usually for pieces with capo we leave it that way, since it is easier to learn and then adapt if you put the capo to another fret
@@arthurtigreat8929thanks for your reaction but I have no clue what you mean to tell. In above score the tab is correct but the score above is dead wrong by any means. It's annotated as if there is no capo so when an open E is played the tab corectly tells you to play an open E but the score above tells you to play an F on first fret. That counts for every note and that's why almost every note in that score has an added #. In short, the tab is annotated in E phrygian, the score above is annotated in f phrygian. On top it's annotated 1 octave to high, you won't find any note lower then the open D string. This is the only post that error occurs, in all other post it's done correctly.
@@ErikVanGoch I meant that for the guitarist, it is easier to learn the piece with the standard notation « as if » there was no capo. It is standard in classical guitar as far as I’m aware. The other videos features the « correct notes » because the program used automatically transcribed it. For this video perhaps the owner of the channel used another one, or just used the transcription of someone else.