Again something, maybe requests, for the “new” export which was introduced some versions ago. It’s great and I like but…
The jobs can’t be disabled, they’re machine depending. the mixdownfolder isn’t configurable, so why the mixdownfolder is NOT the same on another machine?! The export stores the folder with an absolute path, which for me is not acceptable or understandable. Some guys says “beware of configurations on their machines”, but again, the mixdownfolder isn’t configurable, it’s under the projectfolder. AND this is ok!!! But why absolute paths?!
Why export jobs must be activated or not? Sometimes stems or another version with another intro should be relevant.
Steinberg. Make your job(s) right and don’t thing all users are on ONE machine!
I suppose the export paths are absolute because you can use any path you want as the target. For users on one machine, or with a networked drive, that’s good.
But I guess what you’re asking for is the ability to be able to export to a path that’s relative to the mixdown folder of the project–for portability, right?
You want something like named export-jobs so you don’t have to manually select the tracks/stems for each export?
Yes, it’s good, but as I wrote, if you select the Mixdown folder which ist not configurable, it’s under the projects folder…anytime… So exporting from Mac and you share the prject with a Windows user, the export in this machine must be deleted first because if path issues.
So, I want the absoulte path thing if you select the path, selecting the Mixdown folder the the Mixdown folder under the project ist selelected and not anywhere on the machine(s)
Are you on 13 as listed on your profile? The export jobs storing absolute paths bit was changed in version 14 and should work as you expect since then.
