Strict Standards: Redefining already defined constructor for class BPDB in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/backpress/class.bpdb.php on line 183

Strict Standards: Declaration of BB_Walker_Blank::start_lvl() should be compatible with BB_Walker::start_lvl($output) in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/class.bb-walker.php on line 148

Strict Standards: Declaration of BB_Walker_Blank::end_lvl() should be compatible with BB_Walker::end_lvl($output) in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/class.bb-walker.php on line 148

Strict Standards: Declaration of BB_Walker_Blank::start_el() should be compatible with BB_Walker::start_el($output) in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/class.bb-walker.php on line 148

Strict Standards: Declaration of BB_Walker_Blank::end_el() should be compatible with BB_Walker::end_el($output) in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/class.bb-walker.php on line 148

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/backpress/class.wp-object-cache.php on line 285

Strict Standards: Redefining already defined constructor for class WP_Http in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/backpress/class.wp-http.php on line 67

Strict Standards: Redefining already defined constructor for class WP_Http_Cookie in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/backpress/class.wp-http.php on line 1633

Strict Standards: Redefining already defined constructor for class WP_Users in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/backpress/class.wp-users.php on line 11

Strict Standards: Redefining already defined constructor for class BP_Roles in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/backpress/class.bp-roles.php on line 11

Strict Standards: Redefining already defined constructor for class WP_Auth in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/backpress/class.wp-auth.php on line 36

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/backpress/class.wp-dependencies.php on line 33

Strict Standards: Redefining already defined constructor for class WP_Taxonomy in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/backpress/class.wp-taxonomy.php on line 36

Strict Standards: Non-static method BP_Options::get() should not be called statically in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/backpress/functions.bp-options.php on line 9

Strict Standards: Non-static method BP_Options::get() should not be called statically in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/class.bp-options.php on line 26

Strict Standards: Non-static method BP_Options::get() should not be called statically in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/backpress/functions.bp-options.php on line 9

Strict Standards: Non-static method BP_Options::prefix() should not be called statically in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/class.bp-options.php on line 49

Strict Standards: Non-static method BP_Options::get() should not be called statically in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/backpress/functions.bp-options.php on line 9

Strict Standards: Non-static method BP_Options::get() should not be called statically in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/backpress/functions.bp-options.php on line 9

Warning: Cannot modify header information - headers already sent by (output started at /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/backpress/class.bpdb.php:183) in /home/actidemann/kurtrosenwinkel.com/forum/bb-templates/genealogias-bb/rss2.php on line 1
The Kurt Rosenwinkel Forum » Topic: Handling player errors in transcribing http://www.kurtrosenwinkel.com/forum/ The Kurt Rosenwinkel Forum » Topic: Handling player errors in transcribing en Mon, 27 Jun 2016 02:11:31 +0000 silverwater on "Handling player errors in transcribing" http://www.kurtrosenwinkel.com/forum/topic/handling-player-errors-in-transcribing#post-6621
Strict Standards: Non-static method BP_Options::get() should not be called statically in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/backpress/functions.bp-options.php on line 9
Wed, 29 Feb 2012 22:06:57 +0000
silverwater 6621@http://www.kurtrosenwinkel.com/forum/ <p>I also make changes when transcribing, and not always because I felt the player intended to play something differently. Sometimes I just think it could have been better, to my taste, if it had been played a different way. </p> <p>If the reason for transcribing is to improve your playing by getting some fresh ideas in your ears and under your fingers, then just do whatever you think will further that goal. </p>
mattymel on "Handling player errors in transcribing" http://www.kurtrosenwinkel.com/forum/topic/handling-player-errors-in-transcribing#post-6589
Strict Standards: Non-static method BP_Options::get() should not be called statically in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/backpress/functions.bp-options.php on line 9
Fri, 24 Feb 2012 21:39:29 +0000
mattymel 6589@http://www.kurtrosenwinkel.com/forum/ <p>i always write down what they actually played but take a mental note that (for me) it would have been cooler if they did "this". though i also get the impression that the "mistakes" are often the parts that made me want to transcribe them in the first place. </p>
Floatingbridge on "Handling player errors in transcribing" http://www.kurtrosenwinkel.com/forum/topic/handling-player-errors-in-transcribing#post-6587
Strict Standards: Non-static method BP_Options::get() should not be called statically in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/backpress/functions.bp-options.php on line 9
Fri, 24 Feb 2012 17:12:26 +0000
Floatingbridge 6587@http://www.kurtrosenwinkel.com/forum/ <p>Think about the function of your transcription. If it is to improve your skills for notation then go far. There are limitations in notating things accurately any ways. If its not to communicate it to others and it's to get the ideas nder your fingers ( and the notes are correct ) maybe you have it down enough. </p>
JFB on "Handling player errors in transcribing" http://www.kurtrosenwinkel.com/forum/topic/handling-player-errors-in-transcribing#post-6584
Strict Standards: Non-static method BP_Options::get() should not be called statically in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/backpress/functions.bp-options.php on line 9
Fri, 24 Feb 2012 13:09:11 +0000
JFB 6584@http://www.kurtrosenwinkel.com/forum/ <p>There are no mistakes. </p>
guitarmageddon on "Handling player errors in transcribing" http://www.kurtrosenwinkel.com/forum/topic/handling-player-errors-in-transcribing#post-6583
Strict Standards: Non-static method BP_Options::get() should not be called statically in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/backpress/functions.bp-options.php on line 9
Fri, 24 Feb 2012 01:48:09 +0000
guitarmageddon 6583@http://www.kurtrosenwinkel.com/forum/ <p>I think you should write what the player intended, as, after all, it's the ideas that count.<br /> I would also suggest that excessively pedantic transcriptions can be a little unwieldy. </p>
surfinboy on "Handling player errors in transcribing" http://www.kurtrosenwinkel.com/forum/topic/handling-player-errors-in-transcribing#post-6582
Strict Standards: Non-static method BP_Options::get() should not be called statically in /home/actidemann/kurtrosenwinkel.com/forum/bb-includes/backpress/functions.bp-options.php on line 9
Fri, 24 Feb 2012 01:32:44 +0000
surfinboy 6582@http://www.kurtrosenwinkel.com/forum/ <p>Obviously a ton of solos have mistakes, and I'm running into a couple piano solos where it's pretty clear what the guy is meaning to play, but he accidentally hits a key next to it, hits 2 keys simultaneously, etc. I suppose the purist would leave it in, which I'm tempted to do, but do you insert some kind of note like the "sic" comment in writing? or put the note in perentheses? I do all my transcribing in Finale. </p>