Hawthorn

I've searched the forums and haven't found a solution to my problem.

The basic version is I want to be able to create AIFF files in Logic that have internal loop points. Then, I want to bounce the file from Logic and import it into a buffer object, so that it will play from the start of the file, hit the end of the loop, loop back to the beginning of the internal loop, then keep playing through until I send it a "loop 0" message to unloop. This is kind of a vamp/de-vamp idea for a project. Using the audio preview program Snapper, I can seem to export files with marker info, but not loop info.

I'm posting to a Logic forum next, but does anyone have experience with internal loop metadata embedded in AIFF files?

OK. I continued experimenting before posting this and I have some additional weirdness. I can get an internal marker, embedded by Logic, to show up as a sustain loop end point with the info~ object, but ONLY on buffers that have a file included as an argument. So, an info~ object for [buffer~ test -1 2] won't show an internal loop point, but an info~ object for [buffer~ test cello-f2.aif -1 2] WILL work. Does that make sense? This trick seems to only work if the filename used as an argument actually exists, so "fakefile.aif", for example, won't work. I'm so perplexed.

Thanks all...hopefully I'm ignorant of/missing something simple.

The basic version is I want to be able to create AIFF files in Logic that have internal loop points.  Then, I want to bounce the file from Logic and import it into a buffer object, so that it will play from the start of the file, hit the end of the loop, loop back to the beginning of the internal loop, then keep playing through until I send it a "loop 0" message to unloop.  This is kind of a vamp/de-vamp idea for a project.  Using the audio preview program Snapper, I can seem to export files with marker info, but not loop info.

OK.  I continued experimenting before posting this and I have some additional weirdness.  I can get an internal marker, embedded by Logic, to show up as a sustain loop end point with the info~ object, but ONLY on buffers that have a file included as an argument.  So, an info~ object for [buffer~ test -1 2] won't show an internal loop point, but an info~ object for [buffer~ test cello-f2.aif -1 2] WILL work.  Does that make sense?  This trick seems to only work if the filename used as an argument actually exists, so "fakefile.aif", for example, won't work.  I'm so perplexed.

Thanks all...hopefully I'm ignorant of/missing something simple.


loop-points-inside-aiff-files-used-with-info-and-buffer

 object can read loop points from WAVE files. Unfortunately I didn't include aiff loops in the object yet. Maybe I could add this feature in a close future but in the meantime you could try to work with WAVE rather than AIFF?

The sfmarkers~ object can read loop points from WAVE files. Unfortunately I didn't include aiff loops in the  object yet. Maybe I could add this feature in a close future but in the meantime you could try to work with WAVE rather than AIFF?

Loop points inside AIFF files (used with info~ and buffer~)