Thanks for the response. I did see your post in another thread when I was looking for a solution, a solution I had when I was using Nuendo. Having to be present to to batch cycle marker exporting is not a solution for me but I do appreciate your response. Some of the exports take 5-10 minutes due to the complexity of the project.
I will never understand why functions like this are excluded from Cubase and devoted to Nuendo. Having no upgrade path to Nuendo for Cubase users makes the problem even worse for those that need some of Nuendo’s features (not that I want to use Nuendo again).
So, M.E.A.P. can automate the export of cycle markers. According to the developer, there is no way to get the name of the cycle marker into the file name which really is a bummer.
Thanks again for the workaround. I’m just looking for a way to automate the process including naming so I don’t have to be present.