Phil,
This is also the way it is on the Ipad as well. I didn't even think to
lay that out for you when I found this out.
On 01/14/2013 16:18, Phil Halton wrote:
Okay, you're all probably a little tired of this subject by now, but I
have found what I think is the problem and its solution, and think I
should detail it here for future reference.
It seems that a project must be in 4/4 time signature for the loop
browser to work. My project was in cut time (2/4) and I decided to
create a new project in 4/4 and voila, loops all over the place - the
place was lousy with them!
Then, to confirm my suspiscion I created another project, in 2/4 time
again, and not a loop to be found.
I guess it makes sense as apple loops are created with a certain beat
information embedded in the file and its probably based on a time
signature of 4/4. Anything other than that brings up no matchs in the
loop browser's sick logic.
I suppose I should experiment with other time sigs (3/4 etc) to see
what the limitations actually are, but for now, this is big news for
me and a big relief (I was beginning to think Apple had it out for me
personally)
Oh yeah, I also successfuly rebuilt the apple loop index as follows in
case there is interest.
(this procedure comes from Apple support pages and several other
sources on the web)
1) deleted all the entries in the /library/audio/apple loops index/
folder.
2) open GarageBand and try to open the loop browser, GB reports that
there are no loops installed.
3) drag the /library/audio/apple loops/ folder and drop it on GB's
loop browser.
to do this I found it necessary to:
1) place GB and Finder side-by-side on the screen with the resize
window functions (VO shift tilda)
2) Mark the Apple Loops folder with VO comma
3) command tab back to GBB, interact with the loop browser, and drop
the folder of loops with VO period.
It took a few minutes for GB to rebuild the index. After rebuilding,
the apple loops index folder contained 8 new entries (1 for each of my
loop folders)
I hope this is useful to others out there who are pulling their hair
out and crying themselves to sleep over this problem.
Also, if you have anything to add to this information, please do -
that's how we learn.
--
You received this message because you are subscribed to the Google
Groups "MacVisionaries" group.
To post to this group, send email to macvisionaries@googlegroups.com.
To unsubscribe from this group, send email to
macvisionaries+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/macvisionaries?hl=en.
--
You received this message because you are subscribed to the Google Groups
"MacVisionaries" group.
To post to this group, send email to macvisionaries@googlegroups.com.
To unsubscribe from this group, send email to
macvisionaries+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/macvisionaries?hl=en.
