In my view any sync issues is important yes.
But you can’t expect Arturia will reply in this community, even if they sometimes do.
When Arturia have confirmed bugs, all you can do is to wait for the next update where the bugs hopefully is fixed. Sometimes Arturia can tell what happens and when.
Oh, Arturia’s support is really good and I get answers to my emails. Always. But that doesn’t mean Arturia’s programmer are the same good as support. Maybe not enough people report this issue? This is strange because if someone will use Pigments arp preset in Analog Lab and made it works somehow (by creating negative delay to sync it with song), project will be broken after AL update (if bug will be fixed). I expected that maybe people on this forum can confirm this bug (and maybe report it to Arturia as well?).
Have Arturia support confirmed a sync bug in Pigments? I still don’t know what it is. I understood you had a change from earlier. But that can perhaps be about other things.
Now you mention something about a negative delay in a DAW. Did’nt you add that before?
How do you record? Is the first note at a initial keypress delayed? Is the delay the same all the time? How much is the delay?
Both outcoming audio and incoming midi notes or audio will have a delay. That’s not a Pigment sync issue, if that’s what this is about.
It’s very easy to check. Made any arp in Pigments and put a note in your DAW. Add some metronome to check if it plays proper. Then open the same preset using Analog Lab and check. That’s all.
AL plays with one note delay as you can hear compared to Pigments.
Tested on several DAWs (in case you ask about it).
Really, it’s easy to reproduce and easy to check.
Just tested. I can confirm the first note in Analog Lab start later. I think a 1/8 note no matter tempo and timing.
I assume other users have reported this to support. But i don’t know. They might depend on others do. I suggest you contact Arturia support and both describe the issue and post the video. Perhaps also give them a link to this thread. That is if you have’nt already.
I have tested on Windows 11.
DAW Studio One 6 PRO.
Because I already have confirmation about this bug, there is nothing more I can do. I just assumed that maybe more reports about the same bug will speed up fixing it. Anyway, fingers cross - maybe next update?
I’m not an Arturia employee. I’m a user like you that’s also a external moderator.
I suggest you to contact Arturia support because that might help. That’s up to you.
As I mentioned, I already reported it to support and have confirmation about this bug. Unfortunately, while support answers pretty fast and is very helpful, programmers are not. No fixes for many months.
Well, today Analog Lab gets an update and… no fix. I wonder why some developers just choose to ignore bugs and pretend that they’re not exists. I feel sorry for the support guys who has to respond to users while the developers completely ignore the problem.
Please fix the ARP sync bug, it’s really bad
Nope, Arturia only updates AL by adding compatibility to new software, but doesn’t care about existing bugs. Two updates and nothing changed.
I think it’s a little unfair to say the Devs dont care. Developers generally dont like it when their code doesnt work as intended. I worked in IT for many years, not development but support. So, I would come across bugs, report them and test fixes. Bugs are normally assigned a severity based on a variety of factors ranging from ‘it crashes the s/w’ to a ‘minor visual issue’. Another factor is if there is a temporary workaround while the issue is being investigated. Given that this is a relatively minor bug and that switching from using Pigments in AL to Pigments resolves it, I suspect the issue has been given a low priority. I dont think it’s been forgotten. Its likely to be fixed at some point and bundled up with other fixes.
I can switch from AL to Pigments, you too. But many users who have just Analog Lab (Pro/Intro/Play) can’t just switch to Pigments. And number of arps are huge in Pigments. Even more - if someone find a workaround like note shift or track delay, all projects that use Pigments arps in AL will become be broken when (if) Arturia fixes this bug. And it’s not the only bug I found over last years. Support is very helpful and nice, can even confirm reported bugs, but none of them were fixed (except maybe modwheel behaviour in AL). So maybe in your opinion developers don’t like when their code doesn’t work as intended, but as life shows, they don’t really care about it. For example - I may not like when my computer is bloated, but I am too lazy to take any actions to fix that.
Let’s be honest - this minor (in your opinion) bug is not something that any programmer can’t fix in few hours max. And soon it will be a year when I reported it. At some point it stops being a matter of discussion when the facts speak for themselves.
I agree. It does require the full version of Pigments to workaround the problem.
Ultimately, having bought a licence to use the s/w and not buying the s/w itself, we are at the mercy of Arturia.
Lets hope it gets fixed soon.
I can’t play your video/audio. It says: “no video with supported format and mime type found”
Can you share it in some other way, please?
Sorry, I accidentally deleted it from my server (or not re-uploaded it during server change). Now it should works good.
Thanks, I’m checking it out now. I just encountered a problem in AL, myself. I’m not sure if it’s the same problem / bug, but it sounds a bit like it. Here is the topic I just created:
I will attempt to do a recording, myself, to show my own problem.
EDIT: I have a recording ready but I can’t seem to upload it. It’s not accepting MP4 or MKV
So upload it to youtube (as unlisted video, so only people who knows link will see it) and paste link here.
Here is the problem I experience. Video uploaded to Google Drive:
Yes there is Sync issues.
I have also replied you here:
Follow us for the hottest sounds, fresh content, exclusive offers and Arturia news as it happens.