Transposition: Adjusts the pitch of the Apple Loops up or down by the chosen amount. Follow Tempo: This parameter (on by default) allows Apple Loops to follow the project tempo. - that's not entirely true, it also works for audio recorded in the current project, and probably for any audio recorded in Logic. Later edit: Thanks to Eric C., we now know these parameters only appear after flex has been switched on at least once (I assume it uses the results of the Flex analyses for the Follow Tempo and Transpose functions - I didn't realize that).

So it probably works on any audio that's been analyzed for Flex. Which makes total sense, as both parameters are 'derivatives' from flex time and flex pitch. So not a bug in the program, but a mistake in the manual. And if you're talking about the statement 'Follow Tempo: This parameter (on by default) allows Apple Loops to follow the project tempo.'

This page contains information about the User Guide for the StudioLogic CMK-149 from Fatar. User review from Menestrel de malheur about Fatar / Studiologic CMK-149: Ok.

I wouldn't say it's a mistake. The statement is not wrong, it's just incomplete, which is typical of technical material written before the software went to gold master. Armin Van Buuren More Intense Torrent here.

'Incomplete' and 'wrong' are for the most part semantic differences in this case, since I consider incompleteness to be a 'subspecies' of wrong. How it is formulated straightforwardly implies there are no other applications for these parameters. Though I do understand how this came to 'print', and don't see this as a conspiracy to confuse 'innocent' users. But, if any manualwriter happens to come across this topic, (s)he can make an editorial note of it. I frequently see dismissive 'it's just semantics' statements these days. Words MATTER!

I don't think you really took in the completely non-dismissive spirit of my use of the word, plus my general caring attitude towards words and what they mean. I also explained (or tried to) the semantics of this particular instance. I argued/defended/presented my 'case', if you will. Here it is only a matter of semantics, since whatever you call it (incomplete or wrong) the solution is the same: to alter and append the information.

Ashermusic wrote. I still disagree. The manual explicitly implies that those two parameters are exclusively applicable to Apple Loops. This is not the case. A implication of something that is not the case, is commonly referred to as 'wrong'. The implication (that those parameters only affect/work with Apple Loops) is wrong. The statement that those parameters work for Apple Loops, is in itself correct.

That's what's confusing. --- Simply replace 'Apple Loops' by 'Audio'. I hope we don't have to take this case to a higher court. : I still disagree.

The manual explicitly implies that those two parameters are exclusively applicable to Apple Loops. This is not the case. Linn Basik Lv V Tonearm Manual Muscle. A implication of something that is not the case, is commonly referred to as 'wrong'. The implication (that those parameters only affect/work with Apple Loops) is wrong. The statement that those parameters work for Apple Loops, is in itself correct. That's what's confusing.

--- Simply replace 'Apple Loops' by 'Audio'. I hope we don't have to take this case to a higher court. It's either explicit or implicit.What you wrote is unambiguously polysemous.