User Details

Username: eyeala
Website: None provided
Facebook: None provided
Twitter: None provided
Soundcloud: None provided
Account Status: enabled
Member since: Oct 23 2021
About eyeala:
(report this profile)

Devices by eyeala

No devices have been posted by this user.


Comments by eyeala

Comments

Has anyone else been unable to get any usable sounds from this device? It looked super cool when I downloaded it, but I've tried using it in place of an amp simulator or just as a distortion stage. I've tried it on DI guitar audio & on Lead synths. None of these have had a good result.

Am I doing something wrong or is the device's tone supposed to be very "brittle-sounding"..?

Has anyone tried this device in Live 12 beta yet? Wondering if it is still usable, or if it will still be useful since Live 12 has all sorts of updates to the Live MIDI/Clips section.

I'm just going to admit that I have not used the Groove Pool since installing Live 12 beta.

This looks super interesting! Two questions:

1. Does Script Operations come with some useful scripts preinstalled? I looked over the Documentation, and it doesn't seem too complicated to write your own scripts, but I am a (scripting) novice so having some template examples available would make it easier to learn.

2. I use Live 11 Suite + Max 8, however I have been beta testing Live 12 (and plan on getting it when it comes out in March). So just wondering if you are aware of any issues that might occur when using Script Operations with Live 12 beta..?

@UdoRBrauna so far no big issues except for two things...

1. Hardware wrappers are opening the correct AU plugin (UAD-2), however, it is causing a spike in Ableton's CPU (%). Normally UAD-2 plugins shouldn't add to the CPU since the DSP processing is external. I double checked my UAD control panel and have confirmed that the Hardware Wrapper is opening the correct plugin, so IDK what's up with it..?

2. Both wrapper types (UAD-2 & UADx) won't let the external plug-in windows remain in view. As soon as I touch any parameter on the Wrapper UI, the (floating) Plug-In window immediately closes out. This is occurring in every single wrapper device, so I assume it is happening because of some preference within the Max Editor. Any idea..?

Will these devices work with the Live 12 update? They appear to be working with the Live 12 beta, however, I haven't updated my version of Max to go along with Live 12.

Wow this is dope!

Great concept!

Interesting… I’m gonna give it a go and see if it works with LIVE 11

Awesome! Can’t wait to see how this will develop across further updates