Bugs/Mark - Revision history

Dave: /* Word spacing */

2012-09-22T17:24:43Z

Word spacing

← Older revision		Revision as of 17:24, 22 September 2012
Line 27:		Line 27:

	<span style="color:magenta;">Note: I am pretty sure that this phenomenon only occurs on the first words of a line.</span>		<span style="color:magenta;">Note: I am pretty sure that this phenomenon only occurs on the first words of a line.</span>

			-- from an email
			So, I think I have figured out the issue where words are joined together. Apparently in the fly file the word is missing terminal white space. This seems to always be the case in the examples I have looked at.<br>
			However, there are some caveats:<br>
			1) I have seen other words with no terminal space, and they seem to render fine (so maybe I am misunderstanding the file format).<br>
			2) This problem always occurs on the first word of a line,so maybe that information can be used to generate afix.<br>

			This info may (hopefully) greatly aid in expediting a solution.

	==Better pre-post gap settings==		==Better pre-post gap settings==

Deusexmachina at 08:08, 22 September 2012

2012-09-22T08:08:34Z

← Older revision		Revision as of 08:08, 22 September 2012
Line 4:		Line 4:

	Some of these things I suspect are trivial, specifically fixing the fact that meta data gets reverted, extending the bleep.txt file functionality to global search and replace ("yeh" --> "yeah, "cuz" -> 'cause, etc.) and adding a warning if quitting Producer will lose changes		Some of these things I suspect are trivial, specifically fixing the fact that meta data gets reverted, extending the bleep.txt file functionality to global search and replace ("yeh" --> "yeah, "cuz" -> 'cause, etc.) and adding a warning if quitting Producer will lose changes
	The two tricky ones that will provide the most benefit are the top two. Together these ~~four~~ items are the bulk of the problem.		The two tricky ones that will provide the most benefit are the top two. Together these items are the bulk of the problem.

	==Word spacing==		==Word spacing==

Deusexmachina at 08:08, 22 September 2012

2012-09-22T08:08:03Z

← Older revision		Revision as of 08:08, 22 September 2012
Line 3:		Line 3:
	''In order of priority (subject to change):''		''In order of priority (subject to change):''

	Some of these things I suspect are trivial, specifically fixing the fact that meta data gets reverted and adding a warning if quitting Producer will lose changes		Some of these things I suspect are trivial, specifically fixing the fact that meta data gets reverted, extending the bleep.txt file functionality to global search and replace ("yeh" --> "yeah, "cuz" -> 'cause, etc.) and adding a warning if quitting Producer will lose changes
	The two tricky ones that will provide the most benefit are the top two. Together these four items are the bulk of the problem.		The two tricky ones that will provide the most benefit are the top two. Together these four items are the bulk of the problem.

Deusexmachina at 08:05, 22 September 2012

2012-09-22T08:05:27Z

← Older revision		Revision as of 08:05, 22 September 2012
Line 2:		Line 2:

	''In order of priority (subject to change):''		''In order of priority (subject to change):''

			Some of these things I suspect are trivial, specifically fixing the fact that meta data gets reverted and adding a warning if quitting Producer will lose changes
			The two tricky ones that will provide the most benefit are the top two. Together these four items are the bulk of the problem.

	==Word spacing==		==Word spacing==

Deusexmachina at 08:02, 22 September 2012

2012-09-22T08:02:24Z

← Older revision		Revision as of 08:02, 22 September 2012
Line 2:		Line 2:

	''In order of priority (subject to change):''		''In order of priority (subject to change):''

	~~==Arrow key nudging/time entry for blobs in Inspector==~~
	~~It would be really nice if it were possible to nudge elements around on the page using the arrow keys, instead of the error-prone use of the mouse/trackpad.~~

	In the same vein, it would be very helpful to have a blob's time position editable in a field in the Inspector window, just like you can enter scrubber position by clicking in the time field on the left of the Timeline.

	==Word spacing==		==Word spacing==
Line 42:		Line 37:

	But whatever works. The ultimate goal is just to prevent it from doing those instantaneous sweeps, where the singer thinks he has a certain amount of time, but the word just vanishes, and the page changes. If it is better to do it with a minimum duration in seconds, that is fine. I just suspect that it would be more accurate to the original if it were a percentage.		But whatever works. The ultimate goal is just to prevent it from doing those instantaneous sweeps, where the singer thinks he has a certain amount of time, but the word just vanishes, and the page changes. If it is better to do it with a minimum duration in seconds, that is fine. I just suspect that it would be more accurate to the original if it were a percentage.

			==Arrow key nudging/time entry for blobs in Inspector==
			It would be really nice if it were possible to nudge elements around on the page using the arrow keys, instead of the error-prone use of the mouse/trackpad.

			In the same vein, it would be very helpful to have a blob's time position editable in a field in the Inspector window, just like you can enter scrubber position by clicking in the time field on the left of the Timeline.


	==Fix "save MSI default"==		==Fix "save MSI default"==

Deusexmachina: /* Word spacing */

2012-09-22T08:00:50Z

Word spacing

← Older revision		Revision as of 08:00, 22 September 2012
Line 11:		Line 11:
	<span style="color:magenta;">Note: This is potentially just an incorrect assumption somewhere in the code..</span>		<span style="color:magenta;">Note: This is potentially just an incorrect assumption somewhere in the code..</span>

	<span style="color:green;">ADDENDUM: As mentioned in e-mail, One common trait of all such conjoined words is the lack of terminal white space on the first word. So "<>love <>" becomes "<>love<>". Although there are other times that this white space is missing, it seems key here in that it prevents the following word from being separated from the first word in lines so affected.</span>		<span style="color:green;">ADDENDUM: As mentioned in e-mail, One common trait of all such conjoined words is the lack of terminal white space on the first word. So "<>love <>" becomes "<>love<>". Although there are other times that this white space is missing, it seems key here in that it prevents the following word from being separated from the first word in lines so affected. This theoretically makes it much simpler to fix, and as such, bumps this up to the top of the list.</span>

	''Second most time consuming, because every track must be checked, it is hard to do by visual inspection, and since when a track needs one edit, it often needs MANY, and involves lots of zooming in and zooming out, and blob dragging, which is not particularly efficient in the current interface:''		''Second most time consuming, because every track must be checked, it is hard to do by visual inspection, and since when a track needs one edit, it often needs MANY, and involves lots of zooming in and zooming out, and blob dragging, which is not particularly efficient in the current interface:''

Deusexmachina: /* Word spacing */

2012-09-22T07:58:33Z

Word spacing

← Older revision		Revision as of 07:58, 22 September 2012
Line 10:		Line 10:
	==Word spacing==		==Word spacing==
	<span style="color:magenta;">Note: This is potentially just an incorrect assumption somewhere in the code..</span>		<span style="color:magenta;">Note: This is potentially just an incorrect assumption somewhere in the code..</span>

	<span style="color:green;">ADDENDUM: As mentioned in e-mail, One common trait of all such conjoined words is the lack of terminal white space on the first word. So "<>love <>" becomes "<>love<>". Although there are other times that this white space is missing, it seems key here in that it prevents the following word from being separated from the first word in lines so affected.</span>		<span style="color:green;">ADDENDUM: As mentioned in e-mail, One common trait of all such conjoined words is the lack of terminal white space on the first word. So "<>love <>" becomes "<>love<>". Although there are other times that this white space is missing, it seems key here in that it prevents the following word from being separated from the first word in lines so affected.</span>

Deusexmachina: /* Word spacing */

2012-09-22T07:58:12Z

Word spacing

← Older revision		Revision as of 07:58, 22 September 2012
Line 10:		Line 10:
	==Word spacing==		==Word spacing==
	<span style="color:magenta;">Note: This is potentially just an incorrect assumption somewhere in the code..</span>		<span style="color:magenta;">Note: This is potentially just an incorrect assumption somewhere in the code..</span>
			<span style="color:green;">ADDENDUM: As mentioned in e-mail, One common trait of all such conjoined words is the lack of terminal white space on the first word. So "<>love <>" becomes "<>love<>". Although there are other times that this white space is missing, it seems key here in that it prevents the following word from being separated from the first word in lines so affected.</span>

	''Second most time consuming, because every track must be checked, it is hard to do by visual inspection, and since when a track needs one edit, it often needs MANY, and involves lots of zooming in and zooming out, and blob dragging, which is not particularly efficient in the current interface:''		''Second most time consuming, because every track must be checked, it is hard to do by visual inspection, and since when a track needs one edit, it often needs MANY, and involves lots of zooming in and zooming out, and blob dragging, which is not particularly efficient in the current interface:''

Dave: /* The separate thing® (Meta data gets reverted) */

2012-09-21T19:08:07Z

The separate thing® (Meta data gets reverted)

← Older revision		Revision as of 19:08, 21 September 2012
Line 63:		Line 63:
	If possible, and perhaps it simplifies things, the real way to do this would be to just assign default colours based on position (first item in the list gets colours a, b, c, and d; the next item, say Male 1, gets colours e, f, g, and h, the next item, say Male 2, gets colours i, j, k, and l. This way there is only a need to store three or four default colour sets, not an unlimited number.		If possible, and perhaps it simplifies things, the real way to do this would be to just assign default colours based on position (first item in the list gets colours a, b, c, and d; the next item, say Male 1, gets colours e, f, g, and h, the next item, say Male 2, gets colours i, j, k, and l. This way there is only a need to store three or four default colour sets, not an unlimited number.
	The one caveat being that if there is only one singer, that should have it's own default.</span>		The one caveat being that if there is only one singer, that should have it's own default.</span>

			==That forum post==
			https://karaoke.kjams.com/forum/viewtopic.php?f=7&t=1965&p=10944#p10944

	==The separate thing® (Meta data gets reverted)==		==The separate thing® (Meta data gets reverted)==

Deusexmachina: /* Fix "save MSI default" */

2012-09-15T02:58:17Z

Fix "save MSI default"

← Older revision		Revision as of 02:58, 15 September 2012
Line 59:		Line 59:
	Also, I have tried to edit the xml by hand, and while I can get certain things to change, I have not been able to reliably get the RIGHT thing to change. Colours seem to change at random, or sometimes not at all. If I could just get a working copy of the XML with all the right settings, then being able to correctly save wouldn't matter. I could just lock the file, and possibly swap another copy in as needed, but nothing I do in the file works reliably, and nothing really makes sense, anyway.		Also, I have tried to edit the xml by hand, and while I can get certain things to change, I have not been able to reliably get the RIGHT thing to change. Colours seem to change at random, or sometimes not at all. If I could just get a working copy of the XML with all the right settings, then being able to correctly save wouldn't matter. I could just lock the file, and possibly swap another copy in as needed, but nothing I do in the file works reliably, and nothing really makes sense, anyway.

	NOTE:		<span style="color:green;">NOTE:
	I think one of the main problems here is that you are trying to save based on the Singer type (Male Vocal 1, Rap, Sing, Female, etc.). I think this is a problematic way of doing things, because these names can change from song to song quite a bit.		I think one of the main problems here is that you are trying to save based on the Singer type (Male Vocal 1, Rap, Sing, Female, etc.). I think this is a problematic way of doing things, because these names can change from song to song quite a bit.
	If possible, and perhaps it simplifies things, the real way to do this would be to just assign default colours based on position (first item in the list gets colours a, b, c, and d; the next item, say Male 1, gets colours e, f, g, and h, the next item, say Male 2, gets colours i, j, k, and l. This way there is only a need to store three or four default colour sets, not an unlimited number.		If possible, and perhaps it simplifies things, the real way to do this would be to just assign default colours based on position (first item in the list gets colours a, b, c, and d; the next item, say Male 1, gets colours e, f, g, and h, the next item, say Male 2, gets colours i, j, k, and l. This way there is only a need to store three or four default colour sets, not an unlimited number.
	The one caveat being that if there is only one singer, that should have it's own default.		The one caveat being that if there is only one singer, that should have it's own default.</span>

	==The separate thing® (Meta data gets reverted)==		==The separate thing® (Meta data gets reverted)==