specific use case is I’m trying to get a synth engine run through FX and resample that into sampler.
SO, I found using the FX ‘patterns’ works for this, I
create a pattern for each of the FX tracks that is like my master fx pattern (I use delay/reverb)
create another pattern for ‘insert’ fx (other fx, or other fx settings at least)
switch over to the insert fx when ready to resample
place a trig on step 1 of the synth track
switch over to sample track and arm recording + hit play on sequencer
this scoops up the synth engine sound and any automation, as well as filter and ‘insert fx’ all into one sampler patch.
switch back to the master fx pattern to continue song building.
Its so cool that this is possible and really helps alleviate the lack of insert FX.
That said, it’s a bit of a fiddly process with many switches between aux tracks, inst tracks, pattern switching etc. I can’t say I love it, but it works.
I’m mostly wondering how people are resampling in this scenario?
I find it a little weird to have to mute everything going on and place a single trig on a track and do all this switching around, but maybe that’s just the best way to control what you’re resampling?
It makes the workflow kinda slow and I can’t say it encourages using it this way.
I haven’t really developed a go-to way yet for resampling, but I think scenes could offer a easy solution, e.g. set up a dedicated resampling scene and only switch out the patterns that are relevant. Leave everything else muted or empty.
I wish there was a way to duplicate or copy/paste a scene. It seems like the first scene is replicated to all scenes unless otherwise changed, so if I overbuild on the first scene and start editing with subsequent scenes, I have to redo each and every change, every time. It would be awesome to be able to copy/paste a scene to another scene so that changes could be more iterative instead of comprehensive every time.
Sadly, I returned my XY this afternoon. I liked what I was able to make with it, but the OS feels too half baked at the moment. Will revisit in a year or so hopefully after they’ve delivered on stability and promised features.
I’m either the luckiest, or I’m just not pushing the XY enough because I haven’t had one crash or come across one bug. How is everyone using it mostly? I’m only using it to build linear songs-- recording unquantized 256-step patterns + arranger + song mode. Are most of the bugs coming from using/setting up live projects?
here’s how im using it… i compose really basic sounding beats, really just generic melodic harmonic stuff, on the xy, at 120+ bpm. bounce those to op-1 drum sampler, drop an octave or what have ye, and then sequence slices with op-xy’s sequencer… print that to op-1 tape, resample song parts to op-xy, and now build patterns with the original beat over top the slowed down slices. liberal use of op-xy’s tape track. here’s two results so far–
Can anyone direct me to a good video on getting external instrument to play through the assigned track?
I can control/sequence another synth via midi but I can’t get the audio of the synth to play through the OP-XY. I can only hear it when I go to the sampler page.
I bought the M8 and DN2 just before this came out, but I’m taking the XY everywhere with me. I know it’s the same price as a Mac M4 Pro, and probably could do even more with Live and plugins but, it’s a lot less fun and accessible with a laptop.
I’m still learning a lot about its quirks and coming from Elektron, it’s same-same but very different in how it achieves its goals. It’s a beautifully made piece of gear, marred by its silly micro fonts used for its UI when they made such deliberate decisions on their design choices including the effort spent on selecting the perfect shade of gray!
The good thing is, perhaps this micro fonts situation may change as one of their team said some UI interfaces will undergo changes. I can only hope. It’s a shame, for something so portable that I need to remember to bring along reading glasses just to use the XY… oh well.
I dunno its hard to say… it is expensive, like more than the budget of some peoples studios but also I feel like it is the first groovebox type thing that does sample/synths/sequencing and doesn’t just fall flat on its face in some way. Like its easy to get samples in, easy to sample, easy to sequence, fun ways to sequence, synths are fun and better than I expected although I do kind wish there was like an old school VA type sounding one (this is where multi sample comes in I suppose) but yeah if your budget allows for it I say yeah it is really good and will likely get better with time, it plus a monosynth or a little modular or a nice poly and well you are really off to the races.
I dunno I have a big complex studio, with a cirklon lots of modular, some expensive polys, and XY doesn’t like make me wish I was just using my proper studio like other single boxes tend to… its really good, its really expensive but yeah I don’t feel any regrets or oh I could have gotten all this other stuff, its just really good.
Hey gang. Just trying to see if this is normal or if I’ve got a faulty unit:
The knobs seem to always work, but on some screens there seems to be “slippage” (two or three clicks to move up or down one selection) while on other screens the same knob very precisely is 1 click to one selection change. I’m wondering if it’s software based and there’s some kind of knob acceleration algorithm thing going on?
Is anyone (everyone) having a similar experience? Or do some of you have a perfect 1 knob click to one selection change on every screen?
It’s mostly not annoying, but on certain screens I’ll have to get three or four knob clicks before something changes. The ratio parameter on the Prism synth is a specific case where it’ll take several knob clicks before anything registers on the screen.
(Edit: I guess I’m trying to figure out if this feels like a hardware or a software (fixable) issue…)
Yeah that’s a tough one. I’d say it depends on how much gear you’ve invested in up to this point, and how much you’re willing to sell/spend to cop it.
I don’t have expendable money like I once did, so I shouldn’t really have expendable gear. But for some reason I kept holding onto expendable gear because I thought I could create a workflow that would make them non-expendable. It never worked because it always felt disconnected and clunky, no matter the combination. XY feels unified, and has been the only thing that makes those tools feel expendable.
I have sold/am selling everything except my hardware fx, XY and a Renoise dedicated laptop for arrangements (that said, the arranger and song mode of the XY is super quick and fun, so I’m stoked about creating whole tracks with XY). After it’s all said and done I’ll be on the plus side by around $2500, and that’s after buying the XY. So yeah good riddance to unneeded baggage, and hello decent chunk of change in return.
Nah I mentioned this in an early note like right when I received it. In my case and my opinion it’s a software setting/acceleration thing.
I initially noticed it differs on the same encoder just by changing the LFO type, so it makes me think it’s just software not hardware.
Ultimately I felt like it was worth saying that it’s just a minor bug because the only real downside is a little bit of a weird feeling when experiencing the encoder response act non-consistently. Not a big deal, but kinda weird?
I noticed that step components work, like Skip Trig, work on the entire step, even if you are using the nifty “note + record” feature that shows u just the sequence of that particular note
I know it makes sense that a Step components affects the whole step, but I’d like to essentially program a drum fill and figured I could sequence and skip trig on those steps independently, but if a fill note happens on the same step as the main beat, then the step component will just skip all the notes on that step.
So how are yall programming in fills using step components? It would be awesome if there was a way to have certain notes playback every 2nd or 4th time
That’s what the very last step component does, you can set it to play every “x” number of bars. For more weirdness, you can use the second to last step component to make the step component you just set only activate every “X” number of bars.
