P&m Plug-ins Bug Reports, Please report bugs or any kind of problems using DC V.I.P. Plug-ins |
P&m Plug-ins Bug Reports, Please report bugs or any kind of problems using DC V.I.P. Plug-ins |
Sep 18 2011, 10:55 AM
Post
#1
|
|
DontCrack Staff Group: Team Posts: 563 Joined: 26-May 05 Member No.: 67 |
Dear friends,
If you encounter systematic bugs or any other kind of problems using our DC V.I.P. Series plug-ins, please report them here ! Please visit our Tech Support Pages before you do so. In order to fix bugs, we need to reproduce them in the exact same environment as yours. We therefore ask that you bring as many technical details as possible concerning your computer, DAW and overall studio environment : 1- Platform (Mac or PC) 2- Exact computer OS version 3- DAW sequencer with exact version 4- Which audio interface are you using (internal sound card or external audio interface) 5- Are you using third party software such as VST rappers ? 6- Anything else that can help our team reproduce the problems you encounter. Thanks in advance for your time helping us improve our products. Kind Regards - peter -------------------- Eric Nolot
CEO / President www.DontCrack.com |
|
|
Jul 17 2015, 12:36 AM
Post
#2
|
|
Member Group: Members Posts: 13 Joined: 22-May 14 Member No.: 16,126 |
I've noticed what I believe is a bug, whereby any track that has 2 or more Plug & Mix plug-ins inserted, will not null, when a printed down-mix is compared to real-time session playback.
This was with a full mix. I haven't tried it with individual tracks, but presumably it would be the same. The material that is audible during a null test, modulates in volume, and flails wildly all over the stereo sound field. 1. PC 2. Windows 7 (Home Premium) service pack 1 3. Pro Tools 11.3.1 (with Plug & Mix VIP version 3.3) 4. External audio interface 5. No 3rd party software in use 6. Command 8 control surface in use This post has been edited by Carl Kolchak: Jul 17 2015, 12:38 AM |
|
|
Jul 17 2015, 12:14 PM
Post
#3
|
|
Member Group: Members Posts: 13 Joined: 22-May 14 Member No.: 16,126 |
I've noticed what I believe is a bug, whereby any track that has 2 or more Plug & Mix plug-ins inserted, will not null, when a printed down-mix is compared to real-time session playback. This was with a full mix. I haven't tried it with individual tracks, but presumably it would be the same. The material that is audible during a null test, modulates in volume, and flails wildly all over the stereo sound field. 1. PC 2. Windows 7 (Home Premium) service pack 1 3. Pro Tools 11.3.1 (with Plug & Mix VIP version 3.3) 4. External audio interface 5. No 3rd party software in use 6. Command 8 control surface in use I'm also too much of a luddite to figure out how to edit my previous post further (after having signed out), but point 6 should have mentioned that Offline Bounce had been used, so could possibly be a factor (though I've never had any previous issues between realtime, and offline bounces in Pro Tools 11). There was in fact no control surface present, when I discovered the above mentioned bug, not that would be a factor either way (although I have discovered a bug on at least one of the P&M EQ plug-ins, whereby the predetermined frequency bands on the gui : 60Hz / 75Hz / 100Hz etc appear on the control surface as 1 / 2 / 3 etc. When I have time to do a more detailed test, I will post about this issue separately). Cheers! This post has been edited by Carl Kolchak: Jul 17 2015, 12:16 PM |
|
|
Jul 31 2015, 11:17 AM
Post
#4
|
|
Staff Group: Team Posts: 615 Joined: 19-June 12 From: Montreal - CA Member No.: 11,576 |
I'm also too much of a luddite to figure out how to edit my previous post further (after having signed out), but point 6 should have mentioned that Offline Bounce had been used, so could possibly be a factor (though I've never had any previous issues between realtime, and offline bounces in Pro Tools 11). There was in fact no control surface present, when I discovered the above mentioned bug, not that would be a factor either way (although I have discovered a bug on at least one of the P&M EQ plug-ins, whereby the predetermined frequency bands on the gui : 60Hz / 75Hz / 100Hz etc appear on the control surface as 1 / 2 / 3 etc. When I have time to do a more detailed test, I will post about this issue separately). Cheers! Hello Carl, Could you describe your method for doing the null test? Do you create a new stereo track, pull in the bounced mix, invert the phase and then listen to the result? Best Regards, Nick |
|
|
Aug 3 2015, 12:24 PM
Post
#5
|
|
Member Group: Members Posts: 13 Joined: 22-May 14 Member No.: 16,126 |
Hello Carl, Could you describe your method for doing the null test? Do you create a new stereo track, pull in the bounced mix, invert the phase and then listen to the result? Best Regards, Nick Hi Nick, Yes. The entire mix ends up routed through a mix bus, which outputs directly to the hardware outputs. The hardware outputs are selected as the bounce source, in Pro Tools "bounce to disk" dialog, and the bounce is performed "Offline", i.e faster than realtime. The bounced file is automatically imported to a new track, in sample accurate sync with the original, and is output directly to the hardware outputs (i.e. there is no accidental double bussing. It's not routing through the mix bus a second time). Both the multi-mono Trim, and the multi-channel EQ III stock Avid plug-ins are used (independently of course) to invert the phase of the imported, bounced file. The track levels, and panoramas, are not adjusted. The tracks that I first noticed this on were : Drum F/X channel, which comprised of P&M Digital Reverb > Analoger > Monster Boost Bass Guitar, which used P&M Retro Compressor > American Tweed > Retro Equalizer In some cases there were additional 3rd party plug-ins, between the various instances of P&M plug-ins, in others it was P&M only. In either case, a single P&M plug-in did not exhibit any issues during null tests - it is only when two, or more P&M plug-ins are present on any given track, that it exhibits artefacts. I doubt it's directly related, but I have observed that Monster Boost causes severe comb filtering / phase issues, when it is bypassed (I will flag this up as a separate issue). Cheers! |
|
|