AdminDurin G (Adobe)
(Product Manager, Adobe Audio, Adobe DVA)
My feedback
-
1 vote
-
1 vote
Thanks, Michael. I think there may be some third-party plugins which can rotate the "flat" 5.1 field, but I'm not familiar with anything offhand. Let me look into it, and in the meantime, I'll add this as a feature request in our system.
In the meantime, you might be able to use the Channel Mixer effect to achieve this work more easily, rather than breaking out the channels as individual stems and remixing manually.
-
8 votesUnder Review · 9 comments · Audition » Workflow & Interoperability · Flag idea as inappropriate… · Admin →
A change in cross-application functionality with MacOS 10.15 (Catalina) appears to have introduced this problem in certain configurations. The command line parameters Premiere sends to Audition are being stripped or limited. We anticipate this to be resolved in an upcoming update.
-
2 votes
It looks like this issue may be caused by use of custom macOS boot argument being used on the affected system. We're investigating further and it looks like we may be able to prevent this undocumented functionality from negatively affecting Adobe applications in an upcoming update. In the meantime, if you are aware of any tools or settings on this system that may be customizing the computer boot parameters, it may be worth disabling it and verifying if that resolves the issue in Production mode.
-
1 vote
Do you mean "Ducking" instead of "Docking"? The VO isn't triggering the volume of music tracks to reduce?
There is a known issue that is being investigated with regards to the side-chain input compression functionality. We anticipate this to be resolved in an upcoming update. In the meantime, you can install an earlier version of Audition using the Creative Cloud Desktop application, or consider using the Ducking feature in the Essential Sound panel.
-
1 vote
I'm not sure I understand. When you turned off the effect in the Effects Rack, I assume you mean you clicked the power button next to the Amplify effect? Auto-Ducking uses the Amplify effect to achieve the ducking, generating the initial keyframes automatically. Powering an effect on and off isn't an undoable action, as it's common for editors to A/B effects on and off frequently while adjusting or mixing. But powering the effect on and off shouldn't affect its keyframes, even if you modified the ones the Ducking tools generated.
There is a difference, though, if you're toggling the Ducking parameter in the Essential Sound panel on and off. Unchecking it there removes the effect and any custom automation.
-
1 vote
Hi, Ellen.
Any chance you could share a short screen capture of this happening? You should be able to use Quicktime Player to capture a screen recording and either post it here or send it to audbugs@adobe.com and we'll take a look. I think we've seen one report of this in the past, but were unable to reproduce it ourselves. Your comment has many more details, but seeing it happen would be very helpful for troubleshooting.
-
1 vote
Hi, Alex.
We're investigating, but this appears related to changes Apple introduced in MacOS 10.14 and how applications and plugin compatibility is affected by changes introduced into Xcode. It looks like older plugins which were compiled for and relied upon older MacOS graphics libraries may crash - not just in Audition but any DAW which was compiled with the MacOS 10.14 SDK or higher.
We've confirmed the plugins scan correctly, and if part of an existing session, import correctly, but crash when the UI is displayed. The crash occurs within MacOS frameworks, not Audition, but may crash Audition as the parent process. We'll reach out to plug-in providers and Apple, but it appears more recent versions of these plug-ins are fully compatible with MacOS 10.14 and higher, and do not introduce stability issues in Audition or other DAWs tested.
-
1 vote
You can create a new audio file at any arbitrary sample rate you like by clicking the text in the "Sample Rate" box in the new file popup. Please see the attached image for more details. Files recorded at non-standard sample rates should be imported at the same rate, provided the audio file format supports the rate.
However, the actual sample rate that your audio interface feeds samples to Audition (and therefore, the sample rate options in the Audio Hardware preferences) are provided by the audio interface drivers themselves. Most audio devices support a fixed set of sample rates which are required to match in order to communicate between audio device and application. If your audio device is using one sample rate, say 48,000Hz, but your audio file is configured for another, say 528Hz, Audition will interpolate the incoming audio stream of 48,000Hz as 528Hz when writing the sample data to the file. If you're aware of another DAW which supports native communication at non-standard sample rates like you've listed, please let me know and we can investigate further.
-
1 vote
Hi, Jamie.
Please reach out directly to audbugs@adobe.com to troubleshoot this issue. There have been no other reports of similar issues that we're aware of, and we have been unable to reproduce this issue in our own testing. We need additional details to continue.
Thank you.
-
1 vote
Thanks for the suggestions. I'm happy to say we're actively looking into some of these requests, and I'll add your notes to the other items in our backlog where they fit.
-
10 votes
We're looking into this as a feature for a future release. In the meantime, you could work around the limitation right now by adding the rack effects to separate clips or tracks in a multitrack project, then sharing the session file. The other user would need to save each configuration as a new rack preset on their side, but it would contain all of the effects and parameters as you've created them. Not ideal, but will get the job done right now. Thanks for the suggestion and notes.
-
1 vote
Hi, Vadim.
When you crash, do you submit the crash report when prompted? If so, could you include your name or a comment in the notes so that we can find the crash information in our reporting database and see what may be going on?
-
1 vote
When you try to define the print first, do you see the popup window indicating the noise print has been captured? And opening the Noise Reduction effect immediately afterward shows you the graph of the recording and not a message that there's no noise print?
-
1 vote
This is sort of what the Opacity control is for. The lower the opacity of the selection, the less processing is applied. I believe there is an "auto-feather" item in the backlog, though. Let me take a look and update it with your comments.
-
1 vote
The team is investigating this issue.
-
1 vote
Is the source file an MP3 or other compressed format? Certain compression formats, especially using Variable Bit Rates, can be tricky to know the actual duration before the file has actually been opened and fully read. In this case, it sounds like Audition is drawing a clip with the duration reported by the importer, but after uncompressing the data, the actual duration is a bit longer. This can be avoided by using uncompressed sources like WAV or AIFF. Otherwise, importing into Files panel first or adjusting the clip length after the fact will ensure the full contents are played.
-
1 vote
Can you give a little bit more information about the issue? Are you trying to record into Waveform or Multitrack modes? Are you using all 3 channels on the Tri Capture?
Thanks
-
10 votes
Hi, James and other upvoters.
We'd be interested in chatting with you about your visions and expectations for Team Projects support in Audition. Please feel free to reach out to audbugs@adobe.com and we can chat further.
-
6 votes
Yes, I still haven't received a clear reply from Slate Digital. I'll reach out again as, unsupported or not, the VST3 specifications are very clear and straightforward and plugins should work in any host with VST implementation.
Hi Ricardo,
I'll need to reach out to Slate as we certainly have a relationship with them and they have access to all of our applications, including Audition and Premiere Pro which use the same effects engine, for their testing needs. And since Audition and Premiere Pro fully support the VST 2.4 and VST 3.0 effect specifications, there shouldn't be any problem using 64-bit Slate plugins like the VMR. Are you having a specific problem with it?
As for 32-bit plugins, I don't think we're likely to implement native support for these, but we do work well with applications like jBridge which can "wrap" your 32-bit effects in a 64-bit container and do the translation necessary for them to work in Audition or Premiere Pro.
Audition used to have an Upload to Soundcloud menu option, implemented using their SDK. However, they stopped supporting it and the SDK eventually broke on Windows so the feature was removed in its entirety.
It would probably be better at this point for SoundCloud to develop an extension panel that would not just upload, but better support their full creation and administration workflow. Are there any features beyond just uploading that you'd like such an integration to support?