Slate Digital FG-X 1.1

[Steven Slate]

I haven't been able to reproduce the fade in bug since 1.3... Try to rebounce and see if it's repeatable.. if so email support

[machinated]

I only recently updated to 1.3 and started getting the fade in thing. Seems temperamental, usually goes after a few bounces.

[sr2000]

does anybody know if or when 64-bit is coming to Mac?

[joe_04_04]

Steven, I'll try to reproduce the bug during a bounce, but it is very random. Sometimes it happens 5 times in a row and other times it doesn't happen at all, even after 15 or 20 playbacks. Hopefully I can capture it.

[joe_04_04]

Well, actually I hope it goes away, but for the sake of getting a fix, hopefully I can capture it

[AshleySmith06]

Hi everyone,

Please can we kindly request all customers/users ply us with as much detail as possible when logging bug reports and support queries, and also fill in the properties - computer specs (model, OS, etc...), DAW and version, product and version, etc. This will enable us to better support you (quickly) rather than await further correspondance for such critical informations.

Thank you for your adherence.

Kind regards,

[AshleySmith06]

Hi everyone,

Please can we kindly request all customers/users ply us with as much detail as possible when logging bug reports and support queries, and also fill in the properties - computer specs (model, OS, etc...), DAW and version, product and version, etc. This will enable us to better support you (quickly) rather than await further correspondance for such critical informations.

Thank you for your adherence.

Kind regards,

[joe_04_04]

Has the bug been been spotted by the slate team? I know steven said he couldn't reproduce it, just wondering about the progress.

[AshleySmith06]

Hi all,

If anyone is seeing such dual monitor GUI issues with our products in "Pro Tools", please kindly log a ticket on our system: Slate Digital Helpdesk

...and detail comp specs, full name and e-mail address. I'd like to sort you with some future builds to test.

Best regards,

[mirrorboy]

Just wanted to point out that this plug is not meant to be CPU-friendly.

And, it doesn't need to be.

It's a mastering plug. So you should only have a session that has one or two tracks.

I'd hate for Slate to "optimize" the code (if that means cut corners / quality to save CPU).

It's fine as it is, IMO (as far as CPU use).

Thx.

Scott

[JackV]

I like it, but it gets distorted and mushed really quickly. And very CPU heavy going against my tradition of mastering whilst mixing.

[TranscendingM]

Originally Posted by JackV

I like it, but it gets distorted and mushed really quickly. And very CPU heavy going against my tradition of mastering whilst mixing.

Mushed?

[bryan k]

Originally Posted by JackV

I like it, but it gets distorted and mushed really quickly. And very CPU heavy going against my tradition of mastering whilst mixing.

-Try lowering the ITP slider down
-Try not to master WHILE you mix. This plugin was meant as a mastering processor (separate application). Its not a "master while you mix, with a hundred other plugins" processor. Its a very CPU extensive plugin......

[jeremy.c.]

Originally Posted by bryan k

-Try lowering the ITP slider down
-Try not to master WHILE you mix. This plugin was meant as a mastering processor (separate application). Its not a "master while you mix, with a hundred other plugins" processor. Its a very CPU extensive plugin......

It's not? Whoops! I wish someone would have told me that before I did an entire album the way you just said not to use it. Ha!

Seriously though, I did use it on my master buss and just finalized as I mixed. it was a hog, but I made it work.

[Mikey MTC]

Originally Posted by bryan k

-Try lowering the ITP slider down
-Try not to master WHILE you mix. This plugin was meant as a mastering processor (separate application). Its not a "master while you mix, with a hundred other plugins" processor. Its a very CPU extensive plugin......

I don't buy this whole "you're not supposed to use it that way" thing. The compressor on this is so good that I WANT to use it on my mixes.

Right now I'm mixing a documentary, and I've got maybe 12 or 14 tracks and lots of automation flying everywhere. The whole thing is being beautifully held together with the FG-X compressor and limiter.

I'm not actually doing any significant limiting in terms of crashing into 0dBFS. But the Dynamic Perception control brings up all the low level detail magically and squeezes everything together. There's no "mastering" involved in projects like these. The mix the mixer does is the one that goes out and any limiting needs to be done in the main pass.

The problem is the CPU usage bypassed is 40% and unbypassed it jumps to over 70% - on a 2009 Nehalem Quad Core w/HD Native. I'm getting some subtle ticks and clicks on some transients which are not repeatable - ie, they're happening randomly. I'm not sure if CPU consumption is to blame or not as it's random and it gets worse as you progress through a session.

Still looking . . . . . .

[TranscendingM]

Originally Posted by Mikey MTC

I don't buy this whole "you're not supposed to use it that way" thing. The compressor on this is so good that I WANT to use it on my mixes.

Right now I'm mixing a documentary, and I've got maybe 12 or 14 tracks and lots of automation flying everywhere. The whole thing is being beautifully held together with the FG-X compressor and limiter.

I'm not actually doing any significant limiting in terms of crashing into 0dBFS. But the Dynamic Perception control brings up all the low level detail magically and squeezes everything together. There's no "mastering" involved in projects like these. The mix the mixer does is the one that goes out and any limiting needs to be done in the main pass.

The problem is the CPU usage bypassed is 40% and unbypassed it jumps to over 70% - on a 2009 Nehalem Quad Core w/HD Native. I'm getting some subtle ticks and clicks on some transients which are not repeatable - ie, they're happening randomly. I'm not sure if CPU consumption is to blame or not as it's random and it gets worse as you progress through a session.

Still looking . . . . . .

Yea the randomness of it gives it away that it's CPU related but also if you render the file and listen back you'll notice the clicks are not there. Just some peace of mind that the audio is not actually being compromised.

[bryan k]

Originally Posted by Mikey MTC

I don't buy this whole "you're not supposed to use it that way" thing. The compressor on this is so good that I WANT to use it on my mixes.

You dont have to buy anything I say, my word is not gospel......and im not the holy jesus who everyone should listen to and take word for word.....

The comp is GREAT, its the most transparent compressor ive heard. But this plugin marketed as a MASTERING PROCESSOR. You master after your done mixing, and usually its done as a separate task.

If you want to use FG-X as a compressor on your mixbuss while you mix, go for it......it sounds killer. But if your computer cant handle the CPU load.......I dont know what to tell you.

Its like buying a Hot Rodded Indy Race Car. Sure you can drive them on the normal street if that what you really want to do with it.......but they are not built for that.....so dont Bitch about them being a gas guzzler......

[antstudio]

I use VCC, VTM and FG-C all in a single project. But I structure the project into stages (drums, drums+bass, instruments, vocals) where each stage can be printed as a stem. I work the mix as "live" as possible, with all stages working including mixing into FG-X. But when I eventually hit my CPU limit, I "print" one of the earlier stages, mute all its tracks and disable all its plugins. Then I continue until the next CPU hit. When I'm near the end I usually have several printed stems but I'm mixing the stems into FG-X.

This works great. If I get to the end and I think the snare or a BG vocal needs volume adjustment, I can usually re-enable just that stage and do a bit of refinement before the final master. I can also turn off the mastering stage, which is CPU intensive and which I've been refining throughout the mix, re-enable several stems and do several tweaks on the mix, print the stems and the turn on the mastering again, usually with no need to adjust mastering any further.

It all works well and I'm planning for the future because eventually with CPU upgrades I'll be able to open these projects and work 100% live all the time.

..ant

[Steven Slate]

We've received so much praise about the compressor module that it will eventually be its own module, and will have its own makeup gain. Not having the LEVEL module will save a ton of CPU too.

Cheers,
Steven

[TranscendingM]

Originally Posted by Steven Slate

We've received so much praise about the compressor module that it will eventually be its own module, and will have its own makeup gain. Not having the LEVEL module will save a ton of CPU too.

Cheers,
Steven

sick

[edva]

Originally Posted by Steven Slate

We've received so much praise about the compressor module that it will eventually be its own module, and will have its own makeup gain. Not having the LEVEL module will save a ton of CPU too.

Cheers,
Steven

Good move, and thanks, it certainly is one of the best ITB comps ever.

[Home Studio 87]

what about EQ ?

[sonicdefault]

Originally Posted by edva

Good move, and thanks, it certainly is one of the best ITB comps ever.

And it's no wonder considering Fabrice's former work.

Slate guys, you should consider creating a new compressor collection in the future. That'd be awesome.


-SD

[jrhager84]

As owners of fgx, would we be able to download and use just the comp for free as well? I'd love the saved CPU lol

Sent from my SAMSUNG-SGH-I777 using Gearslutz App

[jonas tatit]

I've been working for months with Slate Fg-x, with Logic 9.1.7 and in same cases this plug in doesn't work well. If I'm working with a smooth project, I don't have problems with Slate. But if I'm working with a session with midi channels and/or with channels with a lot crossfades, the problem appears! I hear pops end clicks or a crazy behavior about stereo image... If I remove the plug in and after insert him again, the problem disappears. But, in few minutes, the problem comes back!
This situation is a pity, because this plug in has the best buss compressor and limiter that I've ever seen...

[Steven Slate]

You have the new 1.3 update that came out last spring?

What's your CPU look like when you have the FG-X on?

Cheers,
Steven

[jonas tatit]

Originally Posted by Steven Slate

You have the new 1.3 update that came out last spring?

What's your CPU look like when you have the FG-X on?

Cheers,
Steven

Yes, I have the last version 1.3.2.
No problem with my CPU. I have a macbook pro intel core!7, with 8GB memoria ram.

[The Beatsmith]

Hi, any idea on a release date for FGX2? I thought it was going to be out last spring.

Thanks

[kgdrum_nyc]

Sorry if I missed it,I use FG-X and recently made the transition to 64bit with DP8,I was a bit surprised to find FG-X is not 64bit for OSX yet.
Is there any plans or eta for FG -X to be updated for Mac 64bit users?
Thanks,
KG

[kgdrum_nyc]

*Update,additional questions & bump.

After not seeing any reply here ,I contacted Slate Digital support via phone yesterday & I'm kind of dismayed at the pace updating FG-X to 64bit seems to be taking.
I love what Slate Digital has done with
VCC which I have and use and VTM looks awesome but a bit CPU demanding for my modest Mac,plus I already have UA'S tape plugins.
With that being said I am starting to feel FG-X is the forgotten child in Slate Digitals stable.
It feels like updating it to 64bit has been put on the back burner and it's not enough of a money maker at this time to be a priority for the Slate company to update or even answer a question about the update in this thread for more then a week.
I use FG-X and recently made the transition to 64bit with DP8,I was a bit surprised to find FG-X is not 64bit for OSX at this date in time.
After talking to tech support the most I could gleam was a vague noncommittal answer that Slate Digital "hopes" to have a 64bit Mac update for FG-X some time early next year.
Why has updating this awesome plugin to be 64bit on Macs been placed on such a low priority by the Slate team?
FG-X has many 64 bit Mac users now with Logic,DP and I'm sure other 64bit Mac DAWs as well.
The fact that Slate hasn't even answered my previous post about this is a bit disheartening, why no love for 64bit FG-X Mac users?
Thanks,
KG