You are right in saying, I could use an external editor to edit loops more precisely, but I don´t know any, that would import slice markers from Qlab. If you have any suggestions, please let me know.thanks again
I might use an external editor to set up slice markers or precise in and out points, dropping slices regularly through an audio file, e.g every 2s for bars of 4/4 at tempo=120, or making crossfade loops for hard to loop material,
But, I think, for all the reasons outlined below, that this is pretty much a once only event, as opposed to a workflow where you can switch back and forth seamlessly from editing in QLab and an external editor.
QLab has no way of writing its markers back to the audio file, and you can't access the marker times through scripting. Therefore any work carried out in QLab puts QLab out of sync with the markers actually embedded in your audio file.
Even if Qlab could edit the embedded markers in a file, this would still not allow a full comprehensive workflow for too and fro-ing to an external editor as the markers are only part of the story. In addition to the markers in the external program, which equate to slices in QLab, you also have the repetition number for each slice and the start and end points for playback of the file. Unless figure53 created their own stand alone audio editor, then this info is not going to be editable externally.
Generally, if you want to edit start and endpoints in an external editor this editing has to be destructive.
Retargetting a cue that imported with embedded markers and refreshing of markers edited externally does not seem to be 100% consistent. I can't work out when start and end markers are reset to the bounds of the file/stay where they are, or when the existing slices remain or are cleared by the retargeting to an audio file with no embedded markers.
If an audio cue is opened in an external editor, the markers edited, and the file saved , the new marker positions do not immediately update in QLab
This script, generally, successfully forces the update:
tell application id "com.figure53.qlab.3" to tell front workspace
set selectedcue to the last item of (selected as list)
set currentFileTarget to file target of selectedcue as alias
set the file target of selectedcue to currentFileTarget
end tell
There was a recent in depth discussion about looping in this thread which explores some other points:
https://groups.google.com/forum/#!searchin/qlab/Loop%7Csort:date/qlab/FUxNxAmXJPg/8cAV7aSGiwUJ
I will use external editors for placing and moving slices used for devamp cues or slices used by devamp cues to fire other events. I have created crossfaded loops for notoriously difficult cues with lots of bass content. But generally, I have had few difficulties using the basic tools provided within QLab to achieve successful loops.
Finally, either an OSC cue or an applescript cue on a hot key allows you to set looping on or off for multiple cue selections:
Applescript:
repeat with eachCue in (selected of front workspace as list)
try
set infinite loop of eachCue to true
end try
end repeat
or
repeat with eachCue in (selected of front workspace as list)
try
set infinite loop of eachCue to false
end try
end repeat
OSC:
/cue/selected/infiniteLoop 1
to switch the loop on or:
/cue/selected/infiniteLoop 0
Mic