Avoid Slices when importing audio from Logic Pro

[Guillem Rodriguez]

Hello there.

I'd like to know if there is a way to avoid slices every time I load a new audio file.

Slices are generated from tempo changes in logic pro. When you have a project with a non regular tempo (recorded without click) it becomes a nigthmare of slices when you import it into Qlab. I'm attaching two captures.

thank you everybody in advance

The Logic Pro project:

The audio file into Qlab:

[Brent Lord]

Hello --

We've made a note in our issue tracker to take a look at this when importing. In the meantime, I just wanted to mention that you can use either OSC or AppleScript to delete all the slices after the cue has been added to your workspace.

The OSC command is /cue/{number}/deleteSliceMarkers      (replace {number} with your cue number)

And an example AppleScript:

tell application id "com.figure53.QLab.5" to tell front workspace
set theCue to cue "2" -- change this to your cue number
set slice markers of theCue to ({} as list)
end tell

If this is something you find yourself doing frequently, you could always create a Network cue with a message that just points to the "selected" cue, then assign it a hotkey, e.g. /cue/selected/deleteSliceMarkers    Keep this Network cue in a separate "utilities" cue list, and then you can press the hotkey whenever you ned to clear slices. 

The Script cue version of a utility cue like that would have this script:

tell application id "com.figure53.QLab.5" to tell front workspace
set selectedCues to selected
repeat with eachCue in selectedCues
set slice markers of eachCue to ({} as list)
end repeat
end tell

Brent

[sftechguy]

If I recall correctly, OSC commands can take a wildcard for the {number} parameter, so if you've brought in a bunch of audio file with slices all at once, you should be able to use

/cue/*/deleteSliceMarkers

to delete all slice markers from all cues that have them.  Obviously, you wouldn't want to do this if you had cues with intentionally placed slices. 

If you numbered the cues something like "deleteslices_1", "deleteslices_2", etc., you can then use /cue/deleteslices_*/deleteSliceMarkers to more "surgically" accomplish your goal.

Just a thought...

-s

p.s.  Ironically, I sort of have the opposite problem. I do most of my editing using Audacity and wish I could figure how to get either clip boundaries or labels in a label track to show up as slice markers in QLab.