issues with "Stereo to Mono" utility
hello, im trying to use the stereo to mono script but it always fails and gives an error at line 136 while seemingly trying to save a track preset. it happens in every session i try. im on the edit window and have it filling the whole screen. PT 2020.5.0
heres the log :
24.10.2020 12:25:05.01 [Backend]: !! Command Error: Stereo Track to Single Mono Track [user:cke01ekit0000wm101kup5lx4:ckcow4qb40000mx1091j16a31]:
Could not click popup menu item (Stereo Track to Single Mono Track: Line 136)
Could not find menu item with name: SoundFlow
thank you!
Linked from:
Christian Scheuer @chrscheuer2020-10-24 17:36:00.147ZHi Andrew,
I think you're posting this in the wrong package, there's no such script in the "Pro Tools Utilities" package.
Please see this link for how to best get help with SoundFlow and follow step 1:
- CIn reply toAndrew_Maury⬆:Caleb Nelson @Caleb_Nelson
I'm having the same issue. This is in the 'Track Data Utilities' pack from the store.
Christian Scheuer @chrscheuer2020-10-30 13:17:55.530ZMy apologies, I didn't see it. I've now moved the thread to the proper package.
@Andrew_Maury did you find a solution?cc @Chris_Shaw
- In reply toCaleb_Nelson⬆:
Chris Shaw @Chris_Shaw2020-10-30 22:01:59.126ZFixed. Update Track Data Utilities to V2.0.2
- CCaleb Nelson @Caleb_Nelson
Hey Chris. Thanks for updating. I'm still having some issues with this. It gets caught when it attempts to save a track preset. I installed the new update and ran your preset step before doing this. Here's the error:
01.11.2020 17:18:49.23 <info> [Backend]: Clicking with mouse here: 744, 240 01.11.2020 17:18:49.25 <info> [Backend]: Logging error in action (01) PopupMenuSelectAction: Could not click popup menu item 01.11.2020 17:18:49.25 <info> [Backend]: !! Command Error: DUAL MONO TO STEREO [user:ckgo4t0480008xz10tty0e7eo:ckgo6vgd2000kxz10dla4jsxo]: Could not click popup menu item (DUAL MONO TO STEREO: Line 189) Could not find menu item with name: SF Temp Track Preset << Command: DUAL MONO TO STEREO [user:ckgo4t0480008xz10tty0e7eo:ckgo6vgd2000kxz10dla4jsxo]```- Chris Shaw @Chris_Shaw2020-11-02 17:27:26.492Z2020-11-02 20:48:51.853Z
Caleb,
It would be helpful to have some more information:
Are you triggering the script from StreamDeck, Keyboard, or surface? If a Surface are you using an iOS/Android device or on the Mac?
Are you triggering from the Mix or Edit window?
You ran the setup script. Is there a SoundFlow folder in you track presets folder (open the workspace as shown above) and are there three presets present (No Insert, No Sends, SF Temp preset)?
"It gets caught when it attempts to save a track preset."
When this happens does the "Save Track Preset" window remain open?
- CCaleb Nelson @Caleb_Nelson
Hey Chris,
After you mentioned this, I found that the issue was that my IOS surface was triggering old code. Once I linked to your updated script all is functioning properly. Thanks for the guidance!
- Chris Shaw @Chris_Shaw2020-11-02 21:21:25.646Z
Great! That error reference seemed odd.
- In reply toCaleb_Nelson⬆:Chris Shaw @Chris_Shaw2020-11-02 21:28:44.693Z
Be sure to update any other scripts that you may be using from this package. I changed a lot of code in most of the scripts in it.
- In reply toChris_Shaw⬆:Chris Shaw @Chris_Shaw2020-11-02 21:03:01.305Z
Another question, have you edited the script or copied it to a different location?? In the new version of the script, line 189 in the code does not refer to SF Temp Preset at all.
This leads me to think that something may have gone wrong when you installed the new version or perhaps if you copied the earlier version of the script to a different location / package you didn't update it with the updated version.- CCaleb Nelson @Caleb_Nelson
Yeah that was the exact problem. I had copied the script over, so the update didn't follow. Thanks.
- JIn reply toAndrew_Maury⬆:Job Thako @Job_Thako
Same issue, please paste the link to the solution for this if theres one
- Chris Shaw @Chris_Shaw2020-10-30 22:01:36.454Z
Fixed. Please update Track Data Utilities to 2.0.2 in the store.
//CS// - In reply toJob_Thako⬆:Chris Shaw @Chris_Shaw2020-11-02 21:23:38.286Z
Job,
Please read the above replies to this issue. It has been remedied.- JJob Thako @Job_Thako
oh wow Chris, Thank you so much. im on it
In reply toAndrew_Maury⬆:Chris Shaw @Chris_Shaw2020-10-30 14:24:02.452ZJust to double check, have you run the "1) Create SoundFlow Track Presets" script in the Track Data Utilities package first? Most of the scripts inside of the Track Data Utilities package require that you run this first.
If so, then open the Workspace (opt-i) and look inside Track Presets > SoundFlow and check to see if there are any folders inside of the Soundflow folder. Most likely there will be a Melodyne folder present. Like this:
There is a bug that Andrew Scheps and I have discovered. Pro Tools tells Melodyne where to store its transfers and unfortunately it's telling Melodyne to store transfer data in the last place the PT saves something. So when you save a track preset (as you would be by using the Track Copy Data script) and then do a Melodyne transfer, the transfer will go into the track presets folder which unfortunately throws an error when you run the Stereo to Mono script. (Even worse, if you do a "Save Copy in…" and instantiate a new instance of Melodyne then those transfers will wind up in the same location where you saved the copy!)
For the moment, the only solution is to delete the Melodyne folder inside of the SoundFlow folder but I STRONGLY SUGGEST YOU DON'T unless you are absolutely confident that it won't affect your sessions.
There is a fix and I will hopefully have it out sometime today or first thing tomorrow. In the meantime, be aware of this severe Melodyne bug and report it to Avid if you are experiencing it.
Thanks
- Chris Shaw @Chris_Shaw2020-10-30 22:00:56.979Z
This is issue has been fixed. Please update to V 2.0.2 in the store
- Progress