I got the update but now this new interface has the same screen lagging like the SYNTH. I don’t get why you put a processor that is not enough for these machines.
Here is a video of it while trying to edit one of the synths:
I got the update but now this new interface has the same screen lagging like the SYNTH. I don’t get why you put a processor that is not enough for these machines.
Here is a video of it while trying to edit one of the synths:
I haven’t experienced it, but It is optimized to slow down visual performance instead of compromising audio performance when at the peak CPU. So I imagine if you are using 3 synths + samples, or doing something very CPU-hungry, it would slow down visually. I would recommend trying to lower the voice count or going to a separate pattern and just playing the synth you are editing if you are pushing it hard.
You ‘‘polyend team’’ haven’t experience it? .. Can someone confirm /reconfirm ?
I believe someone stated this was happening with a demo project with the new synth.. surely this can be experianced if it is … and if it is not, does that mean that this unit has some mechanical fail ‘‘encoder sensitivity?’’
& if CPU is reaching its max my recommendation in oder to make the Play+ reach greatness as in:
DWA engine
Slice chopping engine with multiple levels of playbacks and configuration
Add filter types for more variety of color/ behavior in sample engine
Color mode for sounds and patterns
Stellar Song mode with instant copy and paste /playback of song steps
View mode for all rows on first 4 16xox rows /the lower being sample pool
Play mode whereas the grid becomes note scales
More Fx / swappable for reverb /delay and performance Fx including a Frequency shifter semi timestreach effect
Render to sample pool (for resampling)
Now this would be bananas .. Id take it over the OP XY TBH
Q:How would Team Polyend achieve this with limited CPU?
A: You have a system setting where the user can calibrate the consumption by sacrificing polyphony !! ![]()
the power of this device is not in polyphonic synthing (the option is always+/ resampling) in fact using multiple tracks for poly shadows the power of running multiple synthesis across 8 tracks just using few voices ..
Think all of us would welcome greatness in sacrifice of 2 or 3 voices of poly system setting to set the Play+ free to preform magically
IMO dont try to go for HiFi sound (delay &reverb are very nice) but go for more lofi and gritt ‘‘more design choice & CPU friendly’’ on this unit …
All the best…
Btw what do I have to do to win a P+ somewhere
![]()
Yeah, Ive run into this speed bump, too, but I can confirm what Mitch is saying. I don’t have any issues with it until im pushing max CPU. My tracker mini does the same thing, so it just didn’t think of it as a bug I guess. I’ve also experienced lag in previous firmware when pushing the CPU. I like to keep my polyphony no more than 7 as a rule of thumb so that I dont run into overloading issues and I typically dont run into issues. Running less intensive synths can also help, but I can usually run 2 instances of WTFM and a less power hungry one with the polyphony set to 7 or lower between all 3 synths with little issue.
I am not happy with their response. The device is great, fun and inspiring, but these things are import to me. It is a $900 device, the same price I paid for Digitakt 2. Have you see an Elektron screen lagging ever? Don’t get me wrong, I admire Polyend and their instruments but “it is the way it is” is not for me.
They normalized this with the SYNTH. They knew some patches would make the screen unable to have a stable feedback while editing.
Just speaking from personal experience as a sound designer/users of the beta. I spent a lot of time with it and made all music for the Dirt sound design video as well as making a couple complete projects that were not used without it happening(if you wondered why that video doesn’t sound as good as Iso’s normal video music, now you know. haha). Not saying it can’t happen or it is unheard of but I should probably pass this to QA for a better answer. ![]()
Hey @david.acosta, could you share a link to your project?
You can send me a DM if you don’t wish to share your project in public ![]()
So this is unusual on the Play? ![]()
Seam like on the synth it can be seen via tons of macro automation ..
For me it already happens opening some of the factory scenes. Specially when I play the pads at the same time when moving a parameter.