Progressive_disclosure
Roadie
- Messages
- 422
I'm doing the same thing. The extended time is less of an issue now that we can batch them up and just let it run overnight. The only downside with the batching is that the finalization stage is awkward if you've captured a pool of different channels/settings - you then have to remember (or document) those settings if you want to compare the real amp to the capture in their A/B selector.Considering I care a lot about accuracy (typically because the real amp sounds and feels better to me), I only use the extended training.
I don't know if the difference is big (cause I haven't tried other options) but nonetheless.
And that is a lot easier now with the batch processing. Leave stuff overnight and come next day, can play through what I get.
If you haven’t trained them yet you can edit the metadata in the json file. There was an option to open file location and it’ll be in each sub folder. I had to update a bunch before training and it worked wellThat it does! But I still can’t access the other captures metadata that’s in queue so still can’t copy/paste the info. I’ll edit my post since it’s incorrect.
Yeah I imagined there was that option, thanks! I’m gonna try to see if I can do it later and otherwise I’ll go on a wild JSON adventure.If you haven’t trained them yet you can edit the metadata in the json file. There was an option to open file location and it’ll be in each sub folder. I had to update a bunch before training and it worked well
Btw, on a sidenote: I really always thought I prefered component modeling over captures (for obvious reasons), but for me there's something to be said in favour of captures.
but with modelers I often get lost in doing experiments "just because" instead
Yeah no surprise on the mac. Cloud processing has its pros and cons but definitely shines in scenarios like this. Im surprised IK dont offer it as a bolt on but im sure only a small % are making captures so might not be worth even offering it. Stadium going cloud makes complete sense for the masses.Trying out a plugin capture (using the Blackhole virtual audio cable, which seems to work a treat), switched the GPU acceleration off (I'm on a GPU-weak Macbook Air M3), but switched it back on when there wasn't any progress after 5 minutes. Using optimized training, estimated time is around 40 minutes. Wouldn't mind doing this more often if only it wouldn't clog up the entire machine so much. Anything I'm doing comes with brutal latency, be it tabbing through things, typing or whatsoever.
In case this capture comes out ok, I'll possibly queue some up and batch process them on a day when I'm not at home.
Maybe wrong threadI’m noticing even in the latest high gain video that Plexi is sounding pretty not bright capped. I’d love to hear a clip of that amp with the mid and treble really pushing. That’s one model that would really benefit from a switchable bright cap.
Yeah I quickly tried disabling GPU Acceleration yesterday as well and got the same behavior, nothing happened for awhile.Trying out a plugin capture (using the Blackhole virtual audio cable, which seems to work a treat), switched the GPU acceleration off (I'm on a GPU-weak Macbook Air M3), but switched it back on when there wasn't any progress after 5 minutes. Using optimized training, estimated time is around 40 minutes. Wouldn't mind doing this more often if only it wouldn't clog up the entire machine so much. Anything I'm doing comes with brutal latency, be it tabbing through things, typing or whatsoever.
In case this capture comes out ok, I'll possibly queue some up and batch process them on a day when I'm not at home.
Question: is it possible to adjust delay settings on the One at all? Haven’t managed to find that info yet.
Question: is it possible to adjust delay settings on the One at all?