No products in the cart.
creativenorthmedia
Participant
Topics Started: 6
Replies Created: 36
Has Thanked: 1
Been Thanked: 2
Would love to hear an update on this now that PT has officially added support.
Also it is now not exporting at all properly. There are major changes I have made to the file, like playing different cymbals in certain sections. None of these changes are being reflected in the exported files.
EDIT: please disregard this comment, I’m an idiot and forgot that re-importing files with the same name won’t create new files inside PT.
Hey John,
Sure thing so this is using the plugin version. I am exporting and then importing to the host. Pro Tools 2023.6.0.
Tempo adherence on import setting is disabled in PT.
Library is Metal Foundry and yes indeed it’s from the same library.
It should be noted that this didn’t occur at all before routing this extra track.
Also it appears now that none of the tracks are exporting properly and the first several bars are empty. See attached. The workaround has been to put a single hit at the very very start of the file, the files then export at the proper length.
Also worth noting this issue occurs despite the midi clip inside of SDX being set to start at the start of the PT project (bar #1)
Other misc info:
Export dialog settings
Do you mean the PT project or SDX or both?
Yeh ok dude, look I’m not upset but I think maybe you are for some reason? You do this on every one of my threads on this forum and I think it’s just time to stop now.
There are plenty of other people available to answer my question if they wish. I don’t wanna be like this, but if you continue responding to my threads I’m just gonna hit up the mods.
You have your corner, I’ll have mine.
Dude I’ve put forward a very sane and rational argument for improvements to this plugin, but all you seem concerned about is getting upset because someone dare suggest something outside what you deem is acceptable.
What I have suggested is not outside the realms of possibility. I’ll say it again: if I can manually import these tempos, then programming imports automatically or at least having an option on the export menu, should also be possible. I’m guessing you’re not a software engineer, that’s fine. I am and I’m telling you straight up, these solutions are possible.
Anyway you’ve jumped on a few of my threads now. I think this might be the 3rd time we have disagreed on something, which is fine in itself, but I find you particularly unpleasant. So I’m going to ask you this nicely: please do not engage with my threads in future, your engagement is not welcome. I’m happy to continue being a part of this community but if you continue to engage with me in any way I’ll just have to take it up with the mods.
Have a good one.
“The options you stated are not possible because plug-ins cannot control their hosts and cannot get any information from them beyond being provided the information in real time.”
Sorry I don’t buy that, if you can import it manually using a button then you can add options to make this issue more obvious on export.
What’s more, if you can have a button that does it manually then you can have it import automatically. If you can’t listen for events in the VST framework then fine, but a loop that imports tempos every 10 seconds or so could be a solution. This might interfere with processing, so a button or checkbox on export is better.
The idea they “did it in 2017” is some kind of viable defense against progress is just silly. Just because they did it, doesn’t make it good.
Also “professional”, “convenient”, whatever dude that’s just semantics. No reason we can’t improve this clunky workflow and make it more idiot proof for everyone.
Thanks John, I’m sure there is a solution for this whether its having the VST control playback, or a checkbox to import the midi on export, or simply warning users about this issue when exporting and directing them to import the tempo changes manually.
Though if I’m honest, any manual solution should be discouraged. Not exactly what I would call professional tooling.
Fair enough. It seems to be there when you hit the issue, not exactly helpful in showing the user how to avoid the issue in the first place. Also searching “tempo bounce” doesn’t return this info. Even “tempo” doesn’t show anything till waaaaaaayyyyy down at the bottom.
Something like this should be shown as a warning when bouncing, seems like a very critical oversight that could cost people time and money.
I’m not sure why this is so difficult to understand. I get what you are saying, but if follow host is active during playback then it should also apply when exporting. This is not a stretch to imagine.
Also, I was asking if this isn’t possible due to some unforeseen limitation with the VST format and thereby placing that limitation on a technical level.
Ah yes I see, that is absolutely moronic. These libraries should just install with SDX itself, it shouldn’t be possible to fragment the installation like that
Yet another thing not in the manual.
If it’s not a limitation then why doesn’t SDX export those tempo changes?
Thanks for the suggestion I will do that in future. SDX not following host native tempo changes when exporting is yet another piece of information not located in the fucking manual.
False alarm it doesn’t work.
It works for the initial installation and metal foundry, but the trying to open my .sd3p file prompts me to install EZdrummer and midi libraries? Opening the folder for each pack says “this is not a proper installation”? We had to go into the Contents and choose that folder, that broke the entire installation
This is way too difficult guys seriously… it should be a simple click to find a library and away you go. Also this needs to be in the manual.
No products in the cart.
Get all the latest on new releases,
updates and offers directly to your inbox.
Note: By clicking the 'I WANT IN' button, you will not be creating a Toontrack user account. You will only sign up to get our newsletters, offers and promotions to your inbox. You can unsubscribe at any time from a link at the bottom of each email. If you want to learn more about our privacy policy, please find detailed information here.