Announcing AxeCapture: A plugin to save Axe-FX presets in your DAW project.

henryrobinett said:
That's not exactly true. I don't want to go behind his back but I have been in contact with him. He does know. Something happened here that he found personally offensive. He knows the link is broken. He broke it on purpose.
Click to expand...
Thank you for clarifying that.

I knew he felt unwelcome here, which is a shame, but i wasn't sure how he felt about the plug-in.

@AlGrenadine, seems to me he wouldn't want it on your site in that case. Too bad.
 
Last edited:
henryrobinett said:
That's not exactly true. I don't want to go behind his back but I have been in contact with him. He does know. Something happened here that he found personally offensive. He knows the link is broken. He broke it on purpose.
Click to expand...
I'm really not trying to be a jerk here, but anybody could potentially make that claim. Out of respect for his work though, and an over-abundance of caution, I'll take down my links.

I will still provide it to anybody who specifically asks, unless there's some actual update from Glenn like a DM or a post or even just an update to the web page.

Dave Merrill said:
I knew he felt unwelcome here
Click to expand...
Man, that's hard for me to wrap my brain around. This place is so much more awesome than most places on the internet these days.
 
Last edited:
Dave Merrill said:
I knew he felt unwelcome here, which is a shame, but i wasn't sure how he felt about the plug-in.
Click to expand...
Dedicated product forums aren’t for the thin skinned by their very nature, caused by a huge expertise/knowledge/information access gradient (and us being apes with a thin layer of rationality which easily retreats in response to some silly triggers), and that shapes some unhealthy traditions over time in every single one of them. :)

Although this one surely isn’t the worst example, it’s tricky for a guy like this to survive and not to want to burn the whole house down.
 
This is directly from Glenn - he told me I can post this to the forum:

"I received a complaint from Fractal Audio about the messages I post to the forum. There was a friendly difference of opinion on the matter, but Fractal Audio are good people and I don't want to be the source of any trouble, so I think the best way to honor their wishes is to cease participating in the Fractal community, and that includes distributing AxeCapture. Regardless, anybody who has AxeCapture can count on me to provide help with solving any problems they may have with it."
 
Last edited:
henryrobinett said:
This is directly from Glenn - he told me he can post this to the forum:

"I received a complaint from Fractal Audio about the messages I post to the forum. There was a friendly difference of opinion on the matter, but Fractal Audio are good people and I don't want to be the source of any trouble, so I think the best way to honor their wishes is to cease participating in the Fractal community, and that includes distributing AxeCapture. Regardless, anybody who has AxeCapture can count on me to provide help with solving any problems they may have with it."
Click to expand...
That's understandable... He was pretty vocal about a few things that he thought should be done (that weren't) or implemented in another way.

I thought that might have been the issue...

Glenn was a very good resource so it's too bad.
 
henryrobinett said:
This is directly from Glenn - he told me he can post this to the forum:

"I received a complaint from Fractal Audio about the messages I post to the forum. There was a friendly difference of opinion on the matter, but Fractal Audio are good people and I don't want to be the source of any trouble, so I think the best way to honor their wishes is to cease participating in the Fractal community, and that includes distributing AxeCapture. Regardless, anybody who has AxeCapture can count on me to provide help with solving any problems they may have with it."
Click to expand...
that's truly a shame.
He is a great professional and his knowledge will be missed
 
henryrobinett said:
This is directly from Glenn - he told me he can post this to the forum:

"I received a complaint from Fractal Audio about the messages I post to the forum. There was a friendly difference of opinion on the matter, but Fractal Audio are good people and I don't want to be the source of any trouble, so I think the best way to honor their wishes is to cease participating in the Fractal community, and that includes distributing AxeCapture. Regardless, anybody who has AxeCapture can count on me to provide help with solving any problems they may have with it."
Click to expand...
I got pretty exactly the same response a while back, when i pm'd him asking if he was ok, since he hadn't been around. I hope it's ok with him that i say that. I wouldn't have related that here without his explicit blessing, except for the post above saying the same thing.

We didn't discuss AxeCapture at all though. @henryrobinett's posts are the only real info I've seen about that.

This whole kerfuffle is unfortunate, and very much not what this place is usually like. I'm kind of astounded. Mostly we're able to speak our opinions and wishes, and defend them heartily, without things getting overheated to the point that someone feels they have to leave.

These are two very smart and strong-willed people. I hope things can eventually normalize somehow.
 
Last edited:
Dave Merrill said:
I'm kind of astounded. Mostly we're able to speak our opinions and wishes, and defend them heartily, without things getting overheated to the point that someone feels they have to leave.
Click to expand...
This kind of conflict is built into the very nature of a forum like this. That you don’t see things overheated is a matter of restraint, moderation etc, but the tension doesn’t go anywhere (that there’s no way to vent frustration actually makes things worse, not better). So it’s natural for people to disengage every now and then, and they are rarely happy when they get to this point.
 
So... If axe-capture just isn't gonna be a thing anymore can we maybe close and/or delete this thread? huge bummer to come here and find that this is totally unavailable now. just bought a new computer and trying to get all my plugins back only to find that one of my favored ones is no longer around...
 
Amparkmusic said:
So... If axe-capture just isn't gonna be a thing anymore can we maybe close and/or delete this thread? huge bummer to come here and find that this is totally unavailable now. just bought a new computer and trying to get all my plugins back only to find that one of my favored ones is no longer around...
Click to expand...
Close? Maybe. But delete? Nah. Don't wipe out the record of the man's work.
 
I disagree that this thread should be closed, and certainly not deleted. AxeCapture is certainly "still a thing" - it is a valuable tool for many members of this community that rely on Fractal hardware. Also, there was relayed openness from @GlennO via post #244 ^^on this thread-

"...anybody who has AxeCapture can count on me to provide help with solving any problems they may have with it."

Also, AxeCapture is still available. Links to the .vst are posted throughout pages 10-12 of this thread.

With Cliff and the other developers tuning up the firmware at such solid intervals, there are still chances that updates will impact the functionality of Axe-Capture in future. Another reason to keep this thread alive.
 
IN FACT! To my above point I'm wondering if I've found a bug with AxeCapture after Firmware v31.00 was released/installed and would like others to help test and verify:

DEVICE: Axe-FX III Mk1
FIRMWARE: 31.00
SOFTWARE: Axe-Edit III v1.14.22
DAW: Studio One Pro 7

BUG TEST -
(00) Turn on your Axe-FX III, open Axe-Edit III, open your DAW
(0) Load an instance of AxeCapture on a track in your DAW
(1) Note the current preset (ex: p100s06 // Solo 99, Thick Lead)
(2) Flick "Catch"
(3) Go to an empty preset (ex: p440s01) -OR- a low-risk copy of a preset
(4) Flick "Release"

When I do this, the plugin now overwrites the information of the current preset with the information that was gathered with 'Catch' --- RATHER than switching back to the original preset.

So, the <EMPTY> preset of 440 becomes a Solo 99 Thick Lead tone with the option to save.

Does this issue occur with you also?
 
haplo said:
IN FACT! To my above point I'm wondering if I've found a bug with AxeCapture after Firmware v31.00 was released/installed and would like others to help test and verify:

DEVICE: Axe-FX III Mk1
FIRMWARE: 31.00
SOFTWARE: Axe-Edit III v1.14.22
DAW: Studio One Pro 7

BUG TEST -
(00) Turn on your Axe-FX III, open Axe-Edit III, open your DAW
(0) Load an instance of AxeCapture on a track in your DAW
(1) Note the current preset (ex: p100s06 // Solo 99, Thick Lead)
(2) Flick "Catch"
(3) Go to an empty preset (ex: p440s01) -OR- a low-risk copy of a preset
(4) Flick "Release"

When I do this, the plugin now overwrites the information of the current preset with the information that was gathered with 'Catch' --- RATHER than switching back to the original preset.

So, the <EMPTY> preset of 440 becomes a Solo 99 Thick Lead tone with the option to save.

Does this issue occur with you also?
Click to expand...
I'm not in front of my music system but I think this is standard behavior for AxeCapture. It 'captures' the parameters of a preset, rather than the preset number, and sends it back to your Axe. As you mention you now have the option to save that as a preset.
 
NY Guitarist said:
I'm not in front of my music system but I think this is standard behavior for AxeCapture. It 'captures' the parameters of a preset, rather than the preset number, and sends it back to your Axe. As you mention you now have the option to save that as a preset.
Click to expand...
Hey @NY Guitarist - It does ‘Catch’ very well. I’ve been using AxeCapture for almost 1 year on various projects and up until v31.00 (maybe even v30.00, there was a stretch of several updates in quick succession) the .vst functioned by switching to the appropriate preset/scene, and not overwriting data of the current preset - I did read back through the first pages of this thread and AxeCapture is claimed to be firmware version agnostic.

Anyway, that is how I discovered the issue - I opened a previous project that had a specific bass patch, AxeCapture ‘Released’ what should have been p417s04 but it wrote to my main patch, 400. It was a moment of concern. Maybe I'm giving myself the Mandela Effect with this.

Today I’m going to test it will other DAWs and see if it’s a Studio One issue or a corrupt .dll file. Then I might escalate to sending @GlennO an email.

---UPDATE---
In attempting to open an instance of AxeCapture a few other DAWs (Ableton Live 11/12 and Cubase 14) it gives the "No Connection. Restart AxeEdit and your DAW" every time - I'm now wondering if the .dll is corrupted because it used to work in these DAWs as well.
 
Last edited:
haplo said:
---UPDATE---
In attempting to open an instance of AxeCapture a few other DAWs (Ableton Live 11/12 and Cubase 14) it gives the "No Connection. Restart AxeEdit and your DAW" every time - I'm now wondering if the .dll is corrupted because it used to work in these DAWs as well.
Click to expand...

Glenn provided a solution to that issue here:
https://forum.fractalaudio.com/thre...esets-in-your-daw-project.195049/post-2478116

I solved it for Cakewalk doing this:

Go to Preferences -> MIDI -> Playback and Recording, and make sure UWP is selected for the driver mode. That's the new Windows MIDI API. Alternatively, like Androo says, go to Preferences -> MIDI -> Devices and turn off the Axe-FX for both input and output. You may have to restart Cakewalk after you do that.
 
You must log in or register to reply here.
Back
Top Bottom