Thank you, and which HW buffer size?ScrLk wrote: ↑Tue Dec 15, 2020 11:03 amCubase 11 / Windows 10 / VST3TB-ProAudio wrote: ↑Tue Dec 15, 2020 10:31 amWhich OS, which DAW and which plugin format?
Click seems to be very strong on BigSur (ARM)...
In any case we will have a look.
TBProAudio: ISOL8 - Mix Monitoring Plug-in for Windows and Mac OS X
- KVRian
- Topic Starter
- 711 posts since 16 May, 2014 from Germany
-
- KVRist
- 299 posts since 2 Nov, 2020
It was probably 128 samples... I'm not there right now.TB-ProAudio wrote: ↑Tue Dec 15, 2020 11:04 amThank you, and which HW buffer size?ScrLk wrote: ↑Tue Dec 15, 2020 11:03 amCubase 11 / Windows 10 / VST3TB-ProAudio wrote: ↑Tue Dec 15, 2020 10:31 amWhich OS, which DAW and which plugin format?
Click seems to be very strong on BigSur (ARM)...
In any case we will have a look.
- KVRian
- Topic Starter
- 711 posts since 16 May, 2014 from Germany
Just released V2.2.5, reduces clicks when bands are toggled.
-
- KVRist
- 299 posts since 2 Nov, 2020
Great! It's less distracting like that at least for me.TB-ProAudio wrote: ↑Wed Dec 16, 2020 7:43 amJust released V2.2.5, reduces clicks when bands are toggled.
-
- KVRer
- 16 posts since 7 Sep, 2015
Hi I just a chance to verify, is this intentional?TB-ProAudio wrote: ↑Sun Dec 13, 2020 9:45 amHm, we always used TBPA as our label in Protools. But it is correct, 2.0 is not parameter compatible with 1.x. This is why we recommend to uninstall 1.x.ReverbHead wrote: ↑Sun Dec 13, 2020 5:46 am I just updated to the latest version and it broke compatibility with previous projects in Pro tools. It now shows up under TBPA and and pro tools sees it as a different plugin.
This is the previous available version on your site
this is the current:
Thanks.
- KVRian
- Topic Starter
- 711 posts since 16 May, 2014 from Germany
Thank you. We fixed this. Update will be released soon.ReverbHead wrote: ↑Thu Jan 07, 2021 12:43 amHi I just a chance to verify, is this intentional?TB-ProAudio wrote: ↑Sun Dec 13, 2020 9:45 amHm, we always used TBPA as our label in Protools. But it is correct, 2.0 is not parameter compatible with 1.x. This is why we recommend to uninstall 1.x.ReverbHead wrote: ↑Sun Dec 13, 2020 5:46 am I just updated to the latest version and it broke compatibility with previous projects in Pro tools. It now shows up under TBPA and and pro tools sees it as a different plugin.
Thanks.
-
- KVRer
- 16 posts since 7 Sep, 2015
Just updated to 2.2.6 and I'm still getting this when loading a session which had ISOL8 (2.1.2) already on it.
It is showing the right manufacturer name though.
Thanks
It is showing the right manufacturer name though.
Thanks
- KVRian
- Topic Starter
- 711 posts since 16 May, 2014 from Germany
Well, it seems that the change of manufacturer name broke parameter compatibility.ReverbHead wrote: ↑Tue Jan 12, 2021 4:08 pm Just updated to 2.2.6 and I'm still getting this when loading a session which had ISOL8 (2.1.2) already on it.
Thanks
Remove V2.2.6 from your project and deinstall this version.
Install V2.1.2 again, open your project and remove the plug.
Deinstall V2.1.2.
Install V2.2.6 again.
-
- KVRer
- 16 posts since 7 Sep, 2015
Manufacturer name appears to be the same for both versions, something else is breaking it.
-
- KVRer
- 16 posts since 7 Sep, 2015
Hi, It looks like Isol8 is not volume compensating while summing to mono, If placed after a limiter it is going above 0. It used to compensate bofore.
Thanks
Thanks
- KVRian
- Topic Starter
- 711 posts since 16 May, 2014 from Germany
Hmm, wired. Have you engaged "Filter Bypass"?ReverbHead wrote: ↑Mon Feb 08, 2021 3:56 pm Hi, It looks like Isol8 is not volume compensating while summing to mono, If placed after a limiter it is going above 0. It used to compensate bofore.
Thanks
If yes mono level cannot exceed left/right max. as mono= (left+right)/2.
- KVRian
- Topic Starter
- 711 posts since 16 May, 2014 from Germany
-
- KVRer
- 16 posts since 7 Sep, 2015
TB-ProAudio wrote: ↑Mon Feb 08, 2021 5:02 pmHmm, wired. Have you engaged "Filter Bypass"?ReverbHead wrote: ↑Mon Feb 08, 2021 3:56 pm Hi, It looks like Isol8 is not volume compensating while summing to mono, If placed after a limiter it is going above 0. It used to compensate bofore.
Thanks
If yes mono level cannot exceed left/right max. as mono= (left+right)/2.
Here you go. had not had a chance to properly reproduce.
https://we.tl/t-VnHu5myzEc
I have attached both a video and a pro tools session for you to reproduce, this is happening in both stereo and mono.
there is also a pop when engaging the plugin.
thanks
- KVRian
- Topic Starter
- 711 posts since 16 May, 2014 from Germany
Thank you for the video. As I said, signal can go over 0 dBFS if filter bypass (ISOL8, top right of the GUI) is NOT engaged. If you press the knob all ISOL8 filters are bypassed. Then your 0dBFS mono signal should not go over 0 dBFSReverbHead wrote: ↑Mon Mar 08, 2021 11:36 pmTB-ProAudio wrote: ↑Mon Feb 08, 2021 5:02 pmHmm, wired. Have you engaged "Filter Bypass"?ReverbHead wrote: ↑Mon Feb 08, 2021 3:56 pm Hi, It looks like Isol8 is not volume compensating while summing to mono, If placed after a limiter it is going above 0. It used to compensate bofore.
Thanks
If yes mono level cannot exceed left/right max. as mono= (left+right)/2.
Here you go. had not had a chance to properly reproduce.
https://we.tl/t-VnHu5myzEc
I have attached both a video and a pro tools session for you to reproduce, this is happening in both stereo and mono.
there is also a pop when engaging the plugin.
thanks
- KVRian
- Topic Starter
- 711 posts since 16 May, 2014 from Germany
Update to 2.4.2:
- NEW: touch control
- NEW: online version check
- NEW: GUI scaling up 3x
- UPDATE: Smart filter bypass, if all bands active
- UPDATE: GFX elements adjusted
- FIX: Ableton VST3, wrong default init GUI scale
- FIX: possible faulty text entry box
- NEW: touch control
- NEW: online version check
- NEW: GUI scaling up 3x
- UPDATE: Smart filter bypass, if all bands active
- UPDATE: GFX elements adjusted
- FIX: Ableton VST3, wrong default init GUI scale
- FIX: possible faulty text entry box