I have POI set up to censor certain songs and some with an autoloop at a specific mix point.
I've noticed a few times lately the censor doesn't cut in and tonight one of the autoloops didn't engage and the censor never cut in.
I'm using a Denon MCX8000 controller. I've previously noticed this but when I've tested at home the next day they mysteriously work.
Any ideas?
I've noticed a few times lately the censor doesn't cut in and tonight one of the autoloops didn't engage and the censor never cut in.
I'm using a Denon MCX8000 controller. I've previously noticed this but when I've tested at home the next day they mysteriously work.
Any ideas?
geposted Sat 09 Mar 24 @ 10:22 pm
I've found apoi can 'miss' sometimes, usually under heavy load conditions like computing stems or loading in a heavy VST.
I'm sure how they fix that without me knowing exactly why it's missed,
maybe it catches the apoi then it's missed to be acted on by the script engine which would just be a case of queueing actions and having a confirm that it did it [if it misses first time it tries again next time the script engine runs, ms later]
but it could be that the apoi wasn't noticed and that's a harder problem.
I ran into this when making Routine, I had to use a "if = or > than position" type of logic [only +30ms difference and quantize dealt with any slip], and I guess this problem is one of the reasons why "track edit based" flip was abandoned
I'm sure how they fix that without me knowing exactly why it's missed,
maybe it catches the apoi then it's missed to be acted on by the script engine which would just be a case of queueing actions and having a confirm that it did it [if it misses first time it tries again next time the script engine runs, ms later]
but it could be that the apoi wasn't noticed and that's a harder problem.
I ran into this when making Routine, I had to use a "if = or > than position" type of logic [only +30ms difference and quantize dealt with any slip], and I guess this problem is one of the reasons why "track edit based" flip was abandoned
geposted Sat 09 Mar 24 @ 10:56 pm
Nothing heavy running. CPU load around 2.5 percent with video output.
Stems are precomputed.
Stems are precomputed.
geposted Sat 09 Mar 24 @ 11:02 pm
it's not cpu load, it's vdj load.
like real life, if you get 5 requests an hour that's not busy, but if 5 people in person all request at exactly the same time, then walk away, you might miss one.
like real life, if you get 5 requests an hour that's not busy, but if 5 people in person all request at exactly the same time, then walk away, you might miss one.
geposted Sat 09 Mar 24 @ 11:31 pm
As I said nothing complex running, just playing a video as normal but the POI shows in the deck waveform but no action is carried out.
geposted Sun 10 Mar 24 @ 1:14 am
OK, finally figured it out. It's when the remote connection is running that POI are getting ignored.
I use them to censor vocals from tracks, create autoloops at specific points and switch the video skin on and off.
They work perfectly fine until the remote connection is live then they are ignored. Can this be investigated please?
I use them to censor vocals from tracks, create autoloops at specific points and switch the video skin on and off.
They work perfectly fine until the remote connection is live then they are ignored. Can this be investigated please?
geposted Sun 07 Apr 24 @ 6:47 pm
What's the script used?
(Perhaps it's a toggle, and executed from both remote and pc at the same time)
(Perhaps it's a toggle, and executed from both remote and pc at the same time)
geposted Sun 07 Apr 24 @ 6:53 pm
Here are some examples. The remote is just running on it's own with nothing else happening. As soon as it's connected to VDJ they just stop working.
![](/img/403488/59209/Screenshot 2024-04-07 200157.png)
![](/img/403489/76904/Screenshot 2024-04-07 200223.png)
![](/img/403488/59209/Screenshot 2024-04-07 200157.png)
![](/img/403489/76904/Screenshot 2024-04-07 200223.png)
![](/img/403490/79009/Screenshot 2024-04-07 200250.png)
geposted Sun 07 Apr 24 @ 7:02 pm
Hi Adion, did you get a chance to look in to this for me?
Thanks!
Thanks!
geposted Tue 09 Apr 24 @ 10:01 am
Yes, confirmed, will be fixed in next remote update
geposted Wed 10 Apr 24 @ 5:39 am
Brilliant, thank you so much!
geposted Wed 10 Apr 24 @ 7:37 am
Can confirm this is now fixed.
Incidentally I just had a crash and restart connecting to remote on my gig machine build 7921 if you want to take a look.
Cheers.
Incidentally I just had a crash and restart connecting to remote on my gig machine build 7921 if you want to take a look.
Cheers.
geposted Thu 16 May 24 @ 10:35 am