No internet connection
  1. Home
  2. Packages
  3. Melodyne Helpers

Melodyne Prep - Error Message

By Brandon Metcalf @Brandon_Metcalf
    2020-10-28 02:39:59.087Z

    Hey Andrew!

    I've been using (and loving) this script since you first shared them. I'm noticing a couple things on my system that I wanted to mention in case anyone else is experiencing the same behavior.

    1. I'm getting this pop up error on the melodyne prep script. I didn't get it on the very first release of this package. I think it started after the first update.

    (the script has already done the heavy lifting at the point the error message pops up, so it's pretty inconsequential to manually delete the rendered track copy. only mentioning in case others are running in to this too)

    1. Melodyne seems to pick up some extra noise or something that shows as a note a couple octaves down from any vocal. It's just in the gaps and at the end of the vocal, and isn't audible. I noticed it does this every time I pull audio in via the script, but doesn't when I transfer the audio in to melodyne manually (in real time).
    1. I also use the "Track Data Utilities" package from the Soundflow store to copy/paste plugins + sends. I noticed that package uses a "Soundflow" subfolder of the Pro Tools track presets folder and I think the melodyne helpers does too. Sometimes those commands will error out, but will work again if I manually go to the track presets folder and delete any "melodyne transfers" folders from Track Presets - Soundflow. Not sure if that would trigger the error message I'm getting on the Melodyne Prep script or if that's totally unrelated.

    Still saving tons of time with the script! Just thought I'd mention in case any of this is helpful :)

    Reply1 Like
    • 19 replies

    There are 19 replies. Estimated reading time: 16 minutes

    1. Andrew Scheps @Andrew_Scheps
        2020-10-28 14:30:28.510Z

        Hi Brandon,

        Thanks for the feedback!

        Is there any way you could get me the complete error? When it comes up on the top right corner of the screen just click on it and it will open the full SoundFlow log, then you can copy and paste it into a post here. It's having trouble clicking ok in that dialog for some reason.

        As far as the other problems go, they are both Melodyne issues, so I don't think there's anything I can do about them. The random Melodyne folders all over the place is a known bug and is supposedly being worked on, not sure about the artifacts.

        Thanks!

        Reply
        1. Brandon Metcalf @Brandon_Metcalf
            2020-10-28 16:17:29.931Z

            Thanks for the quick response Andrew! See below for complete info pasted from the error:

            --

            28.10.2020 12:13:55.90 [Backend]: ProTools version: 20.09.1.123 class: PT2020
            ProTools processID: 32373

            28.10.2020 12:13:58.60 [Backend]: Early abort from trackSelect, since track was already selected

            28.10.2020 12:13:59.21 [Backend]: Clicking with mouse here: 823, 449.5

            28.10.2020 12:13:59.44 [Backend]: AXUIElementException in LoadUIElement: kAXErrorInvalidUIElement
            Logging error in action (01) ClickButtonAction: ClickButtonAction requires UIElement
            !! Command Error: Melodyne Prep [user:ckcv4yfbo00018l10b1mx5jhl:ckcnbae040002o510rmlddqi8]:
            ClickButtonAction requires UIElement (Melodyne Prep: Line 358)
            SoundFlow.Shortcuts.AXUIElementException: kAXErrorInvalidUIElement
            at SoundFlow.Shortcuts.AXUIElement.GetSubElements(String) + 0x1a5
            at SoundFlow.Shortcuts.Ax.AxNodes.AxElementArrayFromRole.get_RawItems() + 0x56
            at SoundFlow.Shortcuts.Ax.AxNodes.AxElementArray.get_Items() + 0x1b
            at SoundFlow.Shortcuts.Ax.AxNodes.AxElementArrayFilter.get_RawItems() + 0x40
            at SoundFlow.Shortcuts.Ax.AxNodes.AxElementArray.get_Items() + 0x1b
            at SoundFlow.Shortcuts.Ax.AxNodes.AxElementArrayIndexedItem.GetUIElement() + 0x45
            at SoundFlow.Shortcuts.Ax.AxNodes.AxElement.LoadUIElement() + 0x27 (AxElementArrayIndexedItem)

            << Command: Melodyne Prep [user:ckcv4yfbo00018l10b1mx5jhl:ckcnbae040002o510rmlddqi8]

            Reply
            1. Andrew Scheps @Andrew_Scheps
                2020-10-28 16:37:10.476Z

                Hi Brandon,

                Unfortunately that doesn't have the actual error, it should start with the description you can see in the upper right corner of your first screenshot ("clickButtonAction requires...")

                Reply
                1. Brandon Metcalf @Brandon_Metcalf
                    2020-10-28 17:06:09.922Z

                    Just ran it again - Looks like I'm getting the same info when I clicked to open the full Soundflow log in Console. Pasted below for ya just in case this one is different, but let me know if I should try to look somewhere else if this still isn't right!

                    --

                    ClickButtonAction requires UIElement (Melodyne Prep: Line 358)
                    SoundFlow.Shortcuts.AXUIElementException: kAXErrorInvalidUIElement
                    at SoundFlow.Shortcuts.AXUIElement.GetSubElements(String) + 0x1a5
                    at SoundFlow.Shortcuts.Ax.AxNodes.AxElementArrayFromRole.get_RawItems() + 0x56
                    at SoundFlow.Shortcuts.Ax.AxNodes.AxElementArray.get_Items() + 0x1b
                    at SoundFlow.Shortcuts.Ax.AxNodes.AxElementArrayFilter.get_RawItems() + 0x40
                    at SoundFlow.Shortcuts.Ax.AxNodes.AxElementArray.get_Items() + 0x1b
                    at SoundFlow.Shortcuts.Ax.AxNodes.AxElementArrayIndexedItem.GetUIElement() + 0x45
                    at SoundFlow.Shortcuts.Ax.AxNodes.AxElement.LoadUIElement() + 0x27 (AxElementArrayIndexedItem)

                    Reply
                    1. Andrew Scheps @Andrew_Scheps
                        2020-10-28 17:09:28.735Z

                        Ah right, sorry I didn't see it in there the first time. I see where it's getting stuck, but I don't know why. I'll try to get it to fail here and let you know.

                        Reply1 Like
                2. In reply toBrandon_Metcalf⬆:
                  Landon Bailey @LandonBailey
                    2020-10-30 23:04:47.270Z

                    Hey Brandon and Andrew - I'll agree this script is an insane time saver. But I am getting the prompt to permanently delete the vocal track, as well as the error message. I know you're working on it, but here is my log if it helps:

                    << Command: Melodyne Prep [user:ckgwtvb9n0001me10fj738sxn:ckcnbae040002o510rmlddqi8]

                    30.10.2020 19:00:34.71 [Backend]: >> Command: Melodyne Prep [user:ckgwtvb9n0001me10fj738sxn:ckcnbae040002o510rmlddqi8]

                    30.10.2020 19:00:34.79 [Backend]: Clicking with mouse here: 136, 28

                    30.10.2020 19:00:34.90 [Backend]: Clicking with mouse here: 136, 28

                    30.10.2020 19:00:35.17 [Backend]: Clicking with mouse here: 136, 28

                    30.10.2020 19:00:35.31 [Backend]: ProTools version: 20.09.1.123 class: PT2020
                    ProTools processID: 96234

                    30.10.2020 19:00:35.37 [Backend]: ProTools version: 20.09.1.123 class: PT2020
                    ProTools processID: 96234

                    30.10.2020 19:00:35.43 [Backend]: Executing CloseFloatingWindowsAction

                    30.10.2020 19:00:35.53 [Backend]: Clicking with mouse here: 718, 829

                    30.10.2020 19:00:35.55 [Backend]: PopupMenu full role:AXMenu

                    30.10.2020 19:00:35.55 [Backend]: Clicking popup menu element: small

                    30.10.2020 19:00:36.03 [Backend]: Early abort from trackSelect, since track was already selected

                    30.10.2020 19:00:36.04 [Backend]: Early abort from trackSelect, since track was already selected

                    30.10.2020 19:00:36.13 [Backend]: Clicking with mouse here: 335, 885

                    30.10.2020 19:00:36.20 [Backend]: PopupMenu full role:AXMenu

                    30.10.2020 19:00:36.41 [Backend]: Clicking popup menu element: multichannel plug-in

                    30.10.2020 19:00:36.44 [Backend]: Clicking popup menu element: Other

                    30.10.2020 19:00:36.50 [Backend]: Clicking popup menu element: Melodyne (stereo)

                    30.10.2020 19:00:37.53 [Backend]: Clicking with mouse here: 147, 144

                    30.10.2020 19:00:39.84 [Backend]: ProTools version: 20.09.1.123 class: PT2020
                    ProTools processID: 96234

                    30.10.2020 19:00:40.31 [Backend]: Early abort from trackSelect, since track was already selected

                    30.10.2020 19:00:40.89 [Backend]: Clicking with mouse here: 943, 459.5

                    30.10.2020 19:00:42.03 [Backend]: Executing SelectedTrackDeleteAction

                    30.10.2020 19:00:42.05 [Backend]: Logging error in action (01) ClickMenuAction: Could not find menu item: Track->Delete

                    30.10.2020 19:00:42.14 [Backend]: Clicking with mouse here: 820, 328

                    30.10.2020 19:00:42.17 [Backend]: Typing some keys...

                    30.10.2020 19:00:42.34 [Backend]: Logging error in action (01) OpenPopupMenuFromElementAction: popupMenu.open.fromElement requires an element
                    Logging error in action (01) PopupMenuSelectAction: Could not open popup menu

                    30.10.2020 19:00:42.34 [Backend]: !! Command Error: Melodyne Prep [user:ckgwtvb9n0001me10fj738sxn:ckcnbae040002o510rmlddqi8]:
                    Could not open popup menu (Melodyne Prep: Line 166)
                    popupMenu.open.fromElement requires an element

                    << Command: Melodyne Prep [user:ckgwtvb9n0001me10fj738sxn:ckcnbae040002o510rmlddqi8]

                    Reply
                    1. Andrew Scheps @Andrew_Scheps
                        2020-10-30 23:35:51.706Z

                        Thanks for the log. I'm still trying to reproduce the rror.

                        Reply
                        1. Kris Crunk @Kris_Crunk
                            2021-02-09 03:13:21.906Z

                            I've started getting this error when using the Melodyne Prep - It will load the audio into melodyne but it gets hung up when trying to select the new tracks to delete.

                            08.02.2021 21:11:44.21 [Backend]: Logging error in action (01) WaitForElementAction: Element was not found or removed after waiting 2000 ms

                            08.02.2021 21:11:44.21 [Backend]: Logging unknown error in action (02) RunCommandAction: Melodyne Prep Template: Line 365
                            !! Command Error: Melodyne Studio/Editor Prep [user:ckigi5tfk000oi310nheou0iw:ckjri7iyh000222104w7jd6yd#ckjri7sr4000322103ygnr7me]:
                            Element was not found or removed after waiting 2000 ms (Melodyne Prep Template: Line 365)

                            Reply
                            1. Andrew Scheps @Andrew_Scheps
                                2021-02-09 11:35:20.000Z

                                I think what's happening is the Commit is so fast there's no progress dialog (which the script is waiting for). I've just posted version 1.0.18 which hopefully will fix this. Thanks!

                                Reply
                                1. Kris Crunk @Kris_Crunk
                                    2021-02-09 16:49:49.877Z

                                    Really appreciate your help with this!!

                                    I updated and am still having the same issue.
                                    My button is triggering "Melodyne Helpers: Melodyne Studio/Editor Prep"

                                    (this video is unlisted)

                                    9.02.2021 10:44:28.59 [Backend]: Logging error in action (01) WaitForElementAction: Element was not found or removed after waiting 2000 ms

                                    09.02.2021 10:44:28.59 [Backend]: Logging unknown error in action (02) RunCommandAction: Melodyne Prep Template: Line 365

                                    09.02.2021 10:44:28.59 [Backend]: !! Command Error: Melodyne Studio/Editor Prep [user:ckigi5tfk000oi310nheou0iw:ckjri7iyh000222104w7jd6yd#ckjri7sr4000322103ygnr7me]:
                                    Element was not found or removed after waiting 2000 ms (Melodyne Prep Template: Line 365)

                                    Reply
                                    1. Andrew Scheps @Andrew_Scheps
                                        2021-02-09 20:44:42.442Z

                                        Aha, I didn't realise you were using the template, let me investigate...

                                        Reply
                                        1. Nnick krill @nick_krill
                                            2021-02-22 01:24:05.817Z

                                            Hi Everyone,

                                            Not Sure if this is helpful...but I was getting a similar error, and it seemed to be due to a mono track having a mono/stereo plug-in later in the instert path. Got a similar error when running the Melodyne Helper on a stereo track.

                                            On a regualr mono track the script works fine.

                                            Figured I'd share my experiance in case it lead to a clue.

                                            -nick

                                            Reply
                                2. In reply toBrandon_Metcalf⬆:
                                  Andrew Scheps @Andrew_Scheps
                                    2021-02-23 12:52:04.370Z

                                    Ok everybody, sorry for the slow replies here. I've just published version 1.0.19 which uses Freeze instead of Commit. While the neat-freak in me doesn't like the fact that this could leave extra audio on your drive, the part of me that wants the scripts to work knows that this is much less complicated, and therefore much more reliable. I've tested it on stereo tracks and that works here too.

                                    Please let me know if this clears up the errors.

                                    Reply1 Like
                                    1. OOrlando Ferrer @Orlando_Ferrer
                                        2021-02-26 00:16:13.596Z

                                        Hi Andrew, I just updated to latest version and now the Prep Doesn't work. Using a Preset works partially...

                                        Reply
                                        1. OOrlando Ferrer @Orlando_Ferrer
                                            2021-02-26 00:21:17.434Z

                                            25.02.2021 20:20:12.09 [Backend]: #Window: Activate "com.avid.ProTools" window "Edit: Joemil Ft. Yariel-PR_Day 1" -> PT Edit Window Deck [ckdqdegbi0008qj10fs2otzwj]

                                            25.02.2021 20:20:12.09 [Backend]: >> Command: PT Edit Window Deck [user:ckdgm8zoy0000qu10bwp3fork:ckdqct2a10007qj10kx574e6l]
                                            Showing Deck "PT Edit Window Deck" on Device "Stream Deck XL CL29J1A05487" (We were called with device "Stream Deck XL CL29J1A05487")
                                            [StreamDeck] Device 'Stream Deck XL CL29J1A05487' instantiating deck 'PT Edit Window Deck'

                                            25.02.2021 20:20:12.15 [Backend]: << Command: PT Edit Window Deck [user:ckdgm8zoy0000qu10bwp3fork:ckdqct2a10007qj10kx574e6l]

                                            25.02.2021 20:20:14.53 [Backend]: #StreamDeck: KeyDown (3,1) -> Melodyne Prep

                                            25.02.2021 20:20:14.53 [Backend]: >> Command: Melodyne Prep [user:cklljco5v0002u010pr593wj7:ckcnbae040002o510rmlddqi8]

                                            25.02.2021 20:20:14.61 [Backend]: Clicking with mouse here: 70, 28

                                            25.02.2021 20:20:14.64 [Backend]: JavaScript error with InnerException: null
                                            !! Command Error: Melodyne Prep [user:cklljco5v0002u010pr593wj7:ckcnbae040002o510rmlddqi8]:
                                            TypeError: Object has no method 'downloadFile'
                                            (Melodyne Prep line 29)

                                            25.02.2021 20:20:14.64 [Backend]: << Command: Melodyne Prep [user:cklljco5v0002u010pr593wj7:ckcnbae040002o510rmlddqi8]

                                            Reply
                                            1. Andrew Scheps @Andrew_Scheps
                                                2021-02-26 08:46:02.169Z

                                                Hi Orlando,

                                                Could you please run the script so that it fails, and then post a bug report? This will upload your logs so I can have a look. Also, screen recordings of it failing are always a help.

                                                Thanks,
                                                Andrew

                                                Reply
                                          • D
                                            In reply toBrandon_Metcalf⬆:
                                            Damien Lewis @Damien_Lewis
                                              2021-08-03 05:18:21.991Z

                                              same problem here, seems to be on stereo tracks not mono

                                              Reply
                                              1. Andrew Scheps @Andrew_Scheps
                                                  2021-08-03 11:19:09.069Z

                                                  Hi Damien,

                                                  Can you get it to fail and then use the "Help/Issue" from the SoundFlow menu to log a bug. This way I can see your logs and get to the bottom of it.

                                                  Thanks,
                                                  Andrew

                                                  Reply
                                                  1. In reply toDamien_Lewis⬆:
                                                    Andrew Scheps @Andrew_Scheps
                                                      2021-08-03 11:22:25.560Z

                                                      Actually I think I found the bug for stereo tracks. Should work with version 1.0.32.

                                                      Reply
                                                    ReplyAdd progress note