slipperhero

Hi folks, I've encountered a very frustrating issue where the start of the audio content is being cutoff/silenced when exporting multiple short regions IF plugins are enabled in the export. I have 100+ very short regions (character vocalisations for a video game) lined up on a track. I've added the required plugins to the track (logic EQ, logic comp, Waves L2 limiter). I then select all the regions and "export as audio files", and here comes the issue. Even though the exported audio files are exactly the same duration as the originals, the content at the very start has been "silenced". See the attached image. If I disable plugins on the export, the problem does not occur. But however, if I enable plugins but only export a SINGLE region rather than all the regions simultaneously, the problem also does not occur. It's only when I export multiple regions simultaneously WITH plugins enabled that the issue occurs. Very strange! Anybody have a suggestion as to why this is happening? ==UPDATE== Turns out it was the Waves L2 plugin that was causing this behaviour. As soon as I substituted that for Logic's native limiter I was able to export all 100+ regions in one go without the issue. Leaving this here in case anybody else experiences the same bug.

Thanks for the suggestion polanoid, but as soon as I route the mono track to an Aux channel (rather than mono Output 1), the files are exported as stereo, with or without plugins on the Aux channel. Also the exported files aren't exported through the plugins inserted on the Aux track, as I expected they wouldn't be as the export function just looks at the channel strip the regions are on as far as I believe.

Thanks for testing this David. What’s the process for submitting an official bug report to the Logic team?

Hi folks, I think I've found a bug in relation to exporting regions from mono tracks with "Include Volume/Pan automation included" enabled. Now I know that in order to export a mono file you need to route the track to a mono output (Output->Mono->Output 1 for instance), and then you can export regions as mono files with the volume automation. I've done this successfully many times. However, the thing I've just discovered is that if you have any plugins inserted on the track whatsoever (mono plugins of course), the exported files will be stereo. I would have perhaps expected this behaviour if the plugin inserted on the track was a stereo instance of the plugin, but as you can see in the attached video, I'm simply adding a mono instance of Channel EQ. So the track should still be completely mono right, and as such not effect the result of the export? If anybody has any idea how to get around this, or can see something I'm doing wrong, please let me know, otherwise I'm pretty sure this is a bug. Very annoying as I have hundreds of mono regions with volume automation I need to export. Many thanks in advance. Here's a video illustrating the issue: Just to clarify: Mac Studio M1 Max Logic 10.7.4 (also reproduced the issue in 10.7.9)

The buffer size is already set to it's peak. Could it be that some of the other settings here might be causing the glitches when bouncing multiple tracks in place?

Hi folks, I'm experiencing some random glitches and dropouts on certain tracks when using the Bounce>Tracks in Place function. Note, the glitches do not occur when soloing the same tracks and bouncing them manually. This is a bit of an issue as these are very large projects (around 100 tracks), and I need to export the tracks to a 3rd party to mix. Only a handful of the tracks will contain the dropouts/glitches, the majority of the tracks bounce as expected. I haven't experienced the same issue when using Export>Tracks as Audio files, but in some cases I need to include the Aux sends, so need to bounce rather than export. Has anybody else experienced this, and if so is there a trick to prevent it from happening? Thanks in advance. -------------------- Mac Studio M1 Max MacOS 12.4 64GB

Thanks for your reply Christian. That makes perfect sense of course, and I certainly hadn't started a project with negative bars until trying out this Spitfire BBCSO template. it does seem odd to me that they would setup the template in this way, with this limitation of exporting midi files in mind. Everything else in the template has been setup so thoroughly, and considering the majority of their professional user base will be using this template just for mockups, later to be orchestrated, it seems like a fundamental oversight.

Hi folks, I'm in the process of exporting midi files to hand over to an orchestrator. I'm finding however that after exporting the midi files using File -> Export -> Selection as Midi file feature, that when the orchestrator opens the midi files, the regions are offset by 3 bars. Now I've worked out why this is happening! It's basically because I'm using the Spitfire Audio BBCSO template as a starting point for all of these cues, which starts at Bar -2, to allow for a preroll and count-in. After moving the project start position to Bar 1 (deleting the preroll and count-in), the midi file exports the regions at the correct bar positions. So, although I've found the work around mentioned above, it seems like a major oversight that midi files can't be exported with the intended bar position, even if the project starts before bar 1. I've produced multiple cues for this project, hence this will be quite a pain if I need to change the start position of every project before exporting. Is there in fact a way to export the midi files that I might be missing, which ensures all the exported regions start at the correct bar position without the offset, without having to adjust the project start position? It seems quite odd that Spitfire Audio would deliver the template in this way, starting at bar -2, if there wasn't a way to export the midi files correctly with the template as they set it up. Any suggestions are much appreciated. See attached images for what's happening.

That's true, I often use that "feature" when saving multiple versions of a project. Could be as you said because the root folder was once used as the project destination once upon a time, and perhaps something was cached or something at that point which is causing this. Do you know of any system files/prefs I could try deleting in case that's what's happening?

I've been noticing some unusual behaviour recently with regard to the location/folder where a project is saved to. It used to be as far back as i can remember that when you save a new project, you're first prompted for the folder location, and then when saving in that location a new folder would be automatically created with the name of the project, containing the actual project file and subfolders (Audio Files, Freeze Files). What seems to happen now, not always but occasionally which makes it hard to debug, is that instead of a new folder being created containing the new project, the project file and subfolders will be saved directly in the root folder you selected rather than within the expected subfolder. (see images attached). Does anybody have any idea why this behaviour occurs? It does seem to be random at the moment when Logic will create the automatic subfolder and when it won't.

Hi folks, Is anybody here using either an X-Touch One or the new version of the Faderport with Logic? If so, what's your experience with it? Looking to replace my ancient original Faderport which hasn't really worked with Logic for the past few years. Thanks in advance for any info and user experiences.

Haha, ridiculous, but genius. Thanks Fuzzfilth.

Anybody know if when dropping multiple audio files into a project, and selecting the "Place all files on one track" option, if there's a way to define a default gap/space between the regions, rather than placing them literally right up next to each other as is the default behaviour? I often need to drop multiple short sfx files onto a single track, and it would be nice to have a gap between the regions automatically created rather than having to move the regions myself.

I've always tried to avoid updating "anything" when approaching deadlines, but that's a good tip about zipping up the current version in case you need to rollback. Thanks Eriksimon.

Bumping this thread, as i'm experiencing the same bug here. I'm on Logic 10.4.2. Mac OS 10.12.6. Was there a solution for this? Can't update OS right now as i'm in the middle of a project.