TBProAudio: ISOL8 - Mix Monitoring Plug-in for Windows and Mac OS X

VST, AU, AAX, CLAP, etc. Plugin Virtual Effects Discussion
Post Reply New Topic
RELATED
PRODUCTS
ISOL8

Post

ScrLk wrote: Tue Dec 15, 2020 11:03 am
TB-ProAudio wrote: Tue Dec 15, 2020 10:31 am
ScrLk wrote: Tue Dec 15, 2020 9:13 am There is a small click when toggling bands, I think a short crossfade would help.
Which OS, which DAW and which plugin format?
Click seems to be very strong on BigSur (ARM)...

In any case we will have a look.
Cubase 11 / Windows 10 / VST3
Thank you, and which HW buffer size?

Post

TB-ProAudio wrote: Tue Dec 15, 2020 11:04 am
ScrLk wrote: Tue Dec 15, 2020 11:03 am
TB-ProAudio wrote: Tue Dec 15, 2020 10:31 am
ScrLk wrote: Tue Dec 15, 2020 9:13 am There is a small click when toggling bands, I think a short crossfade would help.
Which OS, which DAW and which plugin format?
Click seems to be very strong on BigSur (ARM)...

In any case we will have a look.
Cubase 11 / Windows 10 / VST3
Thank you, and which HW buffer size?
It was probably 128 samples... I'm not there right now.

Post

ScrLk wrote: Tue Dec 15, 2020 9:13 am There is a small click when toggling bands, I think a short crossfade would help.
Just released V2.2.5, reduces clicks when bands are toggled.

Post

TB-ProAudio wrote: Wed Dec 16, 2020 7:43 am
ScrLk wrote: Tue Dec 15, 2020 9:13 am There is a small click when toggling bands, I think a short crossfade would help.
Just released V2.2.5, reduces clicks when bands are toggled.
Great! It's less distracting like that at least for me.

Post

TB-ProAudio wrote: Sun Dec 13, 2020 9:45 am
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.
Hm, 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.
Hi I just a chance to verify, is this intentional?

This is the previous available version on your site
Image

this is the current:
Image

Thanks.

Post

ReverbHead wrote: Thu Jan 07, 2021 12:43 am
TB-ProAudio wrote: Sun Dec 13, 2020 9:45 am
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.
Hm, 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.
Hi I just a chance to verify, is this intentional?

Thanks.
Thank you. We fixed this. Update will be released soon.

Post

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.

Image

It is showing the right manufacturer name though.

Image

Thanks

Post

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
Well, it seems that the change of manufacturer name broke parameter compatibility.
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.

Post

Manufacturer name appears to be the same for both versions, something else is breaking it.

Post

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

Post

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
Hmm, wired. Have you engaged "Filter Bypass"?
If yes mono level cannot exceed left/right max. as mono= (left+right)/2.

Post

2.2.10:
- UPDATE: Mac universal binaries

Post

TB-ProAudio wrote: Mon Feb 08, 2021 5:02 pm
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
Hmm, wired. Have you engaged "Filter Bypass"?
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

Post

ReverbHead wrote: Mon Mar 08, 2021 11:36 pm
TB-ProAudio wrote: Mon Feb 08, 2021 5:02 pm
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
Hmm, wired. Have you engaged "Filter Bypass"?
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
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 dBFS :-)

Post

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

Post Reply

Return to “Effects”