Philip Meyer;645509 Wrote: > >its almost insane that anyone would even argue this point. > And yet you continue to argue.
i argue for sanity. Philip Meyer;645509 Wrote: > > >knowing you as i do, i'm sure you don't have any leading or trailing > >spaces, and since you don't, there will be no loss of speed to worry > >about. > > > No actually now that I've managed to actually complete a scan in 7.6, I > have indeed found a couple of artists where I had a space on the end. > Thanks to 7.6, it made this ERROR in my tags obvious, and I've now > fixed it, thus fixing the ERROR I had in my other apps. so, you don't NEED spaces! so, it was a PROBLEM for you that you had to fix! how interesting! how totally making my argument for me! and now that you fixed your issues, the logic won't need to be applied to your files, so again not a problem for you. the point you don't seem to get, (and not unlike another issue i can think of), is that you are AWARE of this issue, you knew to look for it, you knew how to figure it out and how to fix it. joe avg WON'T. joe avg would be better off if he never had to deal with it, and so would logitech support wise, not to mention the forums. i can just picture it now, endless posts of "oh yeah, did you look for invisible spaces?" what FUN that will be! Philip Meyer;645509 Wrote: > > >this is how it ALWAYS was done, and you never complained then. > I didn't know I had a problem then. thats b/c you didn't! SBS did the right thing! Philip Meyer;645509 Wrote: > Now I do, and now I haven't got a problem any more. so any fix wouldn't apply to you anyway! this is just a simple return to previous function. no good reason not to do it. Philip Meyer;645509 Wrote: > Is it really a big deal? It's simple to trim them once and for all, and > never have to worry about SBS or any other app having a problem ever > again. simple if you know what the problem is, know how to fix it, and don't mind being bothered with it. Philip Meyer;645509 Wrote: > > >now, if we are to worry over nonsense like how much slower the > scanner > >is trimming off leading/trailing spaces, what about how much slower > the > >scanner is putting SPACES as the only entry to a tag field? > There's no performance hit to consider for copying data from tags into > fields in the DB without guessing that the content needs additional > treatment. i don't know enough to know about spaces vs truly blank fields, or trim logic, or the rest. frankly, i don't know that you know either. but first of all, i value common sense over the cannard of performance in this case, b/c how it works from a user POV is more important than the nanoseconds of difference we're talking about here. secondly, i'd assume putting spaces rather than nothing for a field would take longer, but again i don't know. but what i do know, is that it adds extra noise (not data) to the DB which is unnecessary and could result in slower queries. thirdly, the logic might be post scan, or if done during the scan, might be just as quick with or without. until tested, one can't say. Philip Meyer;645509 Wrote: > If you don't want the spaces in the comment field, then delete them, > then you don't need to worry about the extra space being stored in the > DB. duh. but then again, i never needed to worry about them before the diacritics fix. i also would point out that i have never needed to worry about figuring out blank comments from comments with only spaces. total make work situation. Philip Meyer;645509 Wrote: > > >this isn't a diacritic, or a case difference, where at least you can > >SEE the difference. this is a trailing BLANK INVISIBLE SPACE. > > > Oh I see, thanks for clearing that up. I didn't know that space > characters were blank and invisible. Wow. Now I feel enlightened, and > my views are completely different. > NOT! and again, you dodge. you never have explained what the value is in these spaces, and you even have admitted ridding yourself of them. why do you insist it has to be the user who "fixes" the issue, and not the app? the app ALWAYS did it before, and everyone was happy! it only makes sense for the app to do it, b/c it saves the user from being bothered. all you can offer is sarcasm, but not a defense. Philip Meyer;645509 Wrote: > > >Phil Leigh;645230 Wrote: > >> The fact that they haven't been trimmed by other software is > completely > >> irrelevant - 2 wrongs don't make a right! > > > >correct. > > > Correct - it's wrong for those characters to be there, and it's wrong > to assume they should be stripped. What the user has entered should be > how they are stored and viewed. > > I've even heard of people purposely adding spaces to the end of items > to make them be treated as a different entity. eg. if two albums by > the same artist are meant to be different, and a user (rather stupidly) > wants to make them different by adding a space to the end of the second, > then let them do it. thats a kludge, not a reasonable solution, as you obviously know. its also not a compelling reason not to trim. Philip Meyer;645509 Wrote: > > >> Until you consider iTunes and MusicIP import plugins, when the data > >> won't then match if it needs to compare source with DB content. > There > >> may be the occasional thing that doesn't match between the two apps > >> that will cause problems. > > > >GREAT POINT, UNTIL YOU CONSIDER THAT THIS WAS NOT A PROBLEM BEFORE > THE > >DIACRITICS FIX. > > > Do you know that? There are many reported issues that haven't been > fixed; it could well be that there's been an issue with items not > matching between the two apps, which could now be fixed. it could well be that the earth will spin into the sun tomorrow, and so what? sorry, you can't claim as a hypothetical that this MAY fix nebulous problems of the past. you have to show your work. it is COMPLETELY reasonable for me to say that in the past no one EVER said that SBS trimming spaces broke their itunes/musicip exp. if you want to prove/claim that, the burden is on you to do so. you can't just claim that theory/guess that it MIGHT be the case, to back your view. this is just another canard. Philip Meyer;645509 Wrote: > > >most users just want a good experience given a reasonable looking set > >of data. most users won't even understand spaces are the issue, much > >less what to do about them. > > > They they would have the same problem in iTunes, iPod, iPhone, and be > used to it. maybe, maybe not. depends where and how the issue is encountered. Philip Meyer;645509 Wrote: > > >as you said yourself, a separator character with a space might as of > >right now, cause a problem where: > > > >XXX;YYY > > > >won't be equal to: > > > >XXX; YYY > > > >since it could (and probably does) result in a second unintended " > YYY" > >artist. > > > Perhaps, but I'd assme "; " would be the separator. so now we need special logic for space handling with separator characters? my solution is a lot more straightforward than that. Philip Meyer;645509 Wrote: > > >as said above ad nauseum, they are useless noise, and totally > >unintended, and serve no purpose whatsoever. > Then stop saying it. We all get the message/argument. There's just a > decision to be made by Andy. Leave it to him to decide now. There's > nothing more to add to the conversation. first of all, i support an option. that was mentioned earlier and its fine with me to have it be an option, as long as the default is ON. i'd also like an option for respecting case or not, and respecting diacritics or not. having said that... Phil, feel free to stick a cork in it any time you like, but don't deign to tell me when i can, or can't speak. if i don't want to respond i won't, if i do i will, whether i do or not isn't up to you, and unlike yu and Erland and Jim and others, i have never told the rest of you AT ANY TIME on any issue, not to respond. i don't try to call "last word" nor do i always take it. if i feel i have something more to say, i will, but thats only for me to decide, not you, thank you very much. BlueGasPode, very well said. exactly my view. -- MrSinatra www.lion-radio.org using: sb2 & droid (my home) / duet & ipeng (parents' home) - sbs 7.5.5b - win7 & xp pro sp3 ie9 - p4(ht) 3.2ghz, 2gig ram - 1tb wd usb2 raid1 - d-link dir-655 - 49k+ mp3/flac ::VOTE FOR 'BUG 15604' (http://bugs.slimdevices.com/show_bug.cgi?id=15604)!!!:: ------------------------------------------------------------------------ MrSinatra's Profile: http://forums.slimdevices.com/member.php?userid=2336 View this thread: http://forums.slimdevices.com/showthread.php?t=88154 _______________________________________________ ripping mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/ripping
