search

alex9490 / editor-on-fire

Automatically exported from code.google.com/p/editor-on-fire
Other
0 stars 0 forks source link

RS2014\RS2011 While save issue #280

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
EOF doesn't save my fixing progress after I fixed it.

Hit save, EOF say that you having problems with arrangement->
Agree with EOF and do the fixes, Save again and do that fixes again->
and again->and again-> and again, thx.

Plus About tuning - I don't want to see alert about it for RS2, can we do 
something?

Original issue reported on code.google.com by ul0fka on 25 Nov 2013 at 7:15

GoogleCodeExporter commented 8 years ago 
I'll need a sample project file to test with.  I'd need to think some more 
about an option to disable RS1 compatibility messages, it would probably become 
an option in File>Preferences if anything.

Original comment by raynebc on 26 Nov 2013 at 1:18

GoogleCodeExporter commented 8 years ago 
Here my sample project, with deleted fields to infine doing job :)

Original comment by ul0fka on 26 Nov 2013 at 6:37

Attachments:

GoogleCodeExporter commented 8 years ago 
When I opened and saved the project, EOF warned that chord fingerings were 
missing and I opted to correct that, and when I allowed it to fill the 
fingerings in automatically it only gave one more warning:  That it will add 
fret hand positions to the XML file because there aren't any defined in the 
project.  When I saved again, the missing fret hand positions were the only 
warning brought up.  Are you getting any other warnings?  If not, then it's 
intentional behavior.  When you finish authoring the arrangement, you could 
have EOF add automatic fret hand positions to the project (and not just the XML 
file) by using "Track>Rocksmith>Fret hand positions>Generate all diffs".

About the tuning warning, I'll think some more about a user preference to 
suppress Rocksmith 1 warnings.

Original comment by raynebc on 27 Nov 2013 at 7:46

GoogleCodeExporter commented 8 years ago 
The tuning warning was implemented a while ago.  Was there anything left to do 
on this issue?

Original comment by raynebc on 25 Apr 2014 at 10:19

GoogleCodeExporter commented 8 years ago 
I think its solved, thank you :)

Original comment by ul0fka on 26 Apr 2014 at 1:27

GoogleCodeExporter commented 8 years ago

Original comment by raynebc on 26 Apr 2014 at 8:29