I get your point, (I guess). Still, you should be able to trim and extend the audio to take up a full measure so it can be repeated every bar.
if you think it doesn’t apply to you and it’s a problem with a specific system or user error, please try this and see for yourself.
Start a new project at 44.1k.
Set tempo to 127 (doesn’t need to be this tempo, but some tempos 120bpm for example will give exact line-up)
Add an instrument track and create a one bar event…draw in some notes
Export Audio Mixdown of that track and import back to project
Zoom in as far as possible on the end of the event
The audio event is longer than the midi event…no?
Thanks for further clarification of the problem as there was no initial mention of exporting audio directly from a MIDI track. The issue was described with emphasis on the problem with the extra trailing audio at the end of an export and the subsequent having to trim the exported “Audio” using another program.
To be fair, I suppose had I given much thought to the one time mention of
The loops are always seamless in Cubase when I loop it (the wav, not midi)
and read between the lines of that statement against the initially stated concern; perhaps I would have figured it out.
Nonetheless, I followed your instructions in effort to reproduce the issue. Directly exporting the audio generated from 1 bar of the MIDI instrument at 127 bpm and subsequently importing the file back into Cubase and the audio loops seamlessly. I also enlarged the audio and there is no extra audio at the end of the file.
I don’t claim to be an expert by any means but I’ve worked with MIDI and Audio for enough years to know the distinct difference between a MIDI event and the Audio that is generated from the event; and I think it would be more than a reasonable and fair statement to say that no one should realistically expect a MIDI event to be in “perfect” alignment with the audio it generates.
Not to say that it is entirely impossible and achievable with some additional work, but in the very broadest sense that should be (IMHO) a potential realization and not something of surprise. Latency, CPU and other aspects affecting the signal between the trigger and the actual audio play important factors in the outcome.
All that said, should this said anomaly exist for other users (because apparently I must be an exception); then that audio can be trimmed and made useful as a loop within Cubase without having to resort to another product. Which was also the other point I was trying to make. Would you not agree?
I’d be the first to come up with numerous (pet peeves) regarding Cubase and things that I’m not particularly happy with; but that’s speaking off point of the subject. My point is that I haven’t seen any instance during my years of use with Cubase where it cannot trim imported audio and you not be able to perform that within Cubase and have a seamless loop of Audio.
And since its been stated that there obviously is no issue when the audio is looped and the issue is specific to MIDI. Then why wouldn’t one simply route the audio from the VST directly to an audio track, perform any audio trimming and alignment within the audio editor, set the audio to music mode and then export the audio with the tempo definition as I stated?