Originally Posted by
Shishdisma
Oh, I completely agree that a support forum exists to notify a manufacturer about an issue with the ability to track it, but the issue is that doesn't really pan out all so great. Once a company is aware of an issue and working on it (like Pio's current situation) the topics regarding it steadily break down from "I encountered an issue, here was the situation, here was the issue, it is/isnt able to be replicated, can I send in the unit under warranty? (yes)" to "PIO U SHITLORDS y u abandon us? I 40 nd I nevr seen sch AWFUL service from company I literally sell family for equipment. I LITERALLY need doctor I stress so much I cannot sleep from such issue from product from such SHIT SHIT COMPANY." As the rational people report the problem, find a workaround, and then get on with their lives, while the bleaters rapidly degrade for attention.
If your library is sorted by filename, you're going to run into that same issue with literally every ID3 based application in existence. SSL is a bit of a holdover due to legacy dealings. Dumping your entire library organisation structure into a single arbitrary line and tossing the ID3 tags (and the things that sort them) to the wind just isn't a very viable long term strategy.
Check your grids properly, also try experimenting with Normal/Dynamic modes. Normal mode locks the counter at a steady average BPM, while Dynamic is near-perfect elastic gridding, but gets a little jumpy with quantised tracks. Ive actually found RB's detection engine to be pretty top notch, with a bit of error checking.
Bookmarks