search

alex9490 / editor-on-fire

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

Add lyric padding #125

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
As reported here:
http://www.fretsonfire.net/forums/posting.php?mode=reply&f=11&t=32725#pr536496

SUSAltd indicated that FoFiX malfunctions by not including the first lyric in 
each lyric phrase unless there is artificial padding.  I think this padding was 
something that was implemented before, but users shouldn't have to do that to 
work around bugs in FoFiX.  Either of us may need to check with FoF's 
developers to see if they can get this working.  Otherwise, perhaps it could be 
made a user option whether to artificially pad phrases.

Original issue reported on code.google.com by raynebc on 9 Jul 2010 at 10:17

GoogleCodeExporter commented 8 years ago 
I opened a FoFiX bug here:
http://code.google.com/p/fofix/issues/detail?id=1203

Original comment by raynebc on 9 Jul 2010 at 11:11

GoogleCodeExporter commented 8 years ago 
The easiest solution would be to apply padding on the sorted events list that 
is built.  Padding with deltas will allow for the least skew, but it may make 
it simpler if the events list was made to store the delta time instead of the 
realtime of each event.

Original comment by raynebc on 15 Aug 2010 at 7:33

GoogleCodeExporter commented 8 years ago 
This is not a defect of EOF, but one of FoFiX.

Original comment by raynebc on 30 Aug 2010 at 11:27

GoogleCodeExporter commented 8 years ago 
One of the FoFiX developers lowered the priority of the issue, so it looks like 
it's up to us to provide the workaround sooner instead of later.

Original comment by raynebc on 1 Sep 2010 at 3:15

GoogleCodeExporter commented 8 years ago 
This is probably fixed in r340, which alters the order of the events written 
for PART VOCALS and implements padding.

Original comment by raynebc on 1 Sep 2010 at 6:41

GoogleCodeExporter commented 8 years ago 
I'm willing to consider this fixed.  If users report this still being an issue, 
we can make adjustments as necessary.

Original comment by raynebc on 7 Sep 2010 at 7:18