Melodyne Prep fails at Line 382
Hey folks!
Just starting out with Soundflow, really looking forward to using the Melodyne Helper. In my first tests with it, it seems to fail at line 382, right a Pro Tools dialog about clearing selected clips comes up.
Here's what I copied from the error log:
02.01.2022 14:35:43.64 [Backend]: Logging error in action (01) MouseClickElementAction: MouseClickAction requires valid UIElement
02.01.2022 14:35:43.64 [Backend]: Logging unknown error in action (02) RunCommandAction: Melodyne Prep Template: Line 382
02.01.2022 14:35:43.64 [Backend]: !! Command Error: Melodyne Studio/Editor Prep [user:ckxxlzm0j000027109gl5m0mk:ckjri7iyh000222104w7jd6yd#ckjri7sr4000322103ygnr7me]:
MouseClickAction requires valid UIElement (Melodyne Prep Template: Line 382)
<< Command: Melodyne Studio/Editor Prep [user:ckxxlzm0j000027109gl5m0mk:ckjri7iyh000222104w7jd6yd#ckjri7sr4000322103ygnr7me]
02.01.2022 14:36:11.25 [Backend]: [SF_FIREBASE_WS]: Sending keep-alive
Any thoughts?
Andrew Scheps @Andrew_SchepsThis could be because some Pro Tools keystrokes are being overridden by another macro program? A screen recording of it failing would help immensely. Thanks!
- JJonathan Wyman @Jonathan_Wyman
Hey Andrew! I don't have another macro program, though I do use automated tasks like Chronosync and Backblaze for backup, though I don't think those have keystroke macros.
Here is a video showing the failure at line 382:
On another note, does the script have a limit as to how many tracks at a time it can work with? I can get it to the above step for about a half a dozen tracks or so, but more than that and there's some scroling that happens and the mouse seems to lose its way. I do use multiple monitors, and though the screen capture only records my main monitor, I can see the cursor on the monitor ABOVE my main monitor, attempting to move inserts. Like I said, this only seems to happen when selecting a larger batch of tracks.
Here's the error log for when the screen jumps:
03.01.2022 08:05:02.38 [Backend]: Clicking with mouse here: 601, 375
03.01.2022 08:05:02.44 [Backend]: PopupMenu full role:AXMenu
03.01.2022 08:05:02.45 [Backend]: Clicking popup menu element: small
03.01.2022 08:05:04.23 [Backend]: Pressing key: kVK_ANSI_P. Flags: Zero
03.01.2022 08:05:05.09 [Backend]: Dragging from 292, -427 to 306, -427
03.01.2022 08:05:05.99 [Backend]: Dragging from 292, -427 to 306, -427
03.01.2022 08:05:06.83 [Backend]: Dragging from 292, -427 to 306, -427
03.01.2022 08:05:07.65 [Backend]: Dragging from 292, -427 to 306, -427
03.01.2022 08:05:08.46 [Backend]: Dragging from 292, -427 to 306, -427
03.01.2022 08:05:09.26 [Backend]: JavaScript error with InnerException: null
Logging error in action (01) RunCommandAction: Could not move inserts
(Melodyne Prep Template line 246)03.01.2022 08:05:09.26 [Backend]: !! Command Error: Melodyne Studio/Editor Prep [user:ckxxlzm0j000027109gl5m0mk:ckjri7iyh000222104w7jd6yd#ckjri7sr4000322103ygnr7me]:
Could not move inserts
(Melodyne Prep Template line 246)<< Command: Melodyne Studio/Editor Prep [user:ckxxlzm0j000027109gl5m0mk:ckjri7iyh000222104w7jd6yd#ckjri7sr4000322103ygnr7me]
Thank you SO much for your help with this!
Andrew Scheps @Andrew_SchepsHi @Jonathan_Wyman ,
You're having two interesting problems. The first one is being caused by the fact that the wrong dialog is coming up when trying to delete the file. It is a while-file clip, so it should bring up the dialog that lets you delete it, not just remove it from the session. There must be some setting in Pro Tools that is causing that, I'l have a hunt around. The second problem is that it shouldn't have scrolled down to the bottom of the screen, and I',m not sure why it did, I use it on a large selection of tracks all the time and don't see this issue. I'll investigate...
Thanks,
Andrew- JJonathan Wyman @Jonathan_Wyman
Thanks, Andrew!
I don’t know if this affects anything, but the tracks are within folder tracks (which I tend to use for managing large track counts). Some of the tracks may also have elastic audio enabled.
Unrelated to Soundflow, but since you mention using lots of tracks simultaneously is Melodyne, I find that when I have more than a dozen or so tracks loaded in, it gets bogged down a bit and I occasionally get the spinning rainbow wheel for a couple of seconds. It’s not the most powerful system ever (2019 MBP 2.6 i7 with 32 gigs of ram) but not a slouch either. Anyone else experience this, or know what could improve performance? If this is too off topic, accept my apologies and ignore!
- Andrew Scheps @Andrew_Scheps
Ah, I'll bet the elastic audio is the issue. Try disabling "Enable Elastic Audio on New Tracks" in the Processing tab in Preferences.
The scrolling thing I'm not sure about, I'll keep looking.
- JJonathan Wyman @Jonathan_Wyman
Disabling elastic audio did the trick! I don't have it on by default, but was using it on this project to varispeed some BGV's. Committed the varispeed and the script runs right as rain.
It did not affect the scrolling thing, so still hoping to figure that part out.
thanks much!
- Andrew Scheps @Andrew_Scheps
I'm still trying to reproduce the scrolling error. I suppose in the meantime just do it in a couple of batches?
- JJonathan Wyman @Jonathan_Wyman
Yup, that's what I'm doing, as it helps to avoid Melodyne itself getting bogged down.
Thanks again for the help on this.