Hi @wwaag

Placed the new files: C:\Program Files\VEGAS\VEGAS Pro 21.0\Script Menu\Happy Otter Scripts

(overwriting the original files)

Unfortunately, same behaviour here.

Also tested with new project with just one single video file and no edits.

Get asked to save the project first, then CTD. Sorry.

@wwaag If your speech to text is by any chance based on my whisper speech to text script v7, I made an recent update v8 to fix an issue with the recent Vegas 21 builds: due to a Vegas version check in the code to be backward compatible with old Sony Vegas versions, I removed the build version in the version check as it confused V21 build 314, build 315 with old Sony Vegas main version 14, 15, as it should check on Vegas main version alone (like Vegas 21, 20, etc...)!

@Phil_P does it crash in older Vegas builds? Like 208?

@Phil_P does it crash in older Vegas builds? Like 208?

Hi @bitman
Can't really answer that I'm afraid. I don't have any way to check older version as I am in mid project. Sorry.

@bitman

No, it's not based on your scripts but I have made changes addressing the problem you had with builds 314 and 315.

OK I figured out the issue at this end: My Happy Otter Scripts exist in 2 locations:

1. C:\ProgramData\HappyOtterScripts\Magix Vegas Pro\Scripts
2. C:\Program Files\VEGAS\VEGAS Pro 21.0\Script Menu\Happy Otter Scripts

I had put the updated versions in location no.2 but the shortcuts on the Otter Bar are all pointing to the location 1.

So when I was running the scripts from the Otter Bar it was running the old versions.

I will try to get a new build out later in the week with the corrections to these scripts

Unless I'm mistaken, Wayne's scripts are not a partnered application.

@ccscotty A very good analyst right there....

@ccscotty

I presume this is what you mean??

If so, I have rarely, if ever, used this debugging approach. I just checked and see that it doesn't work for V20 and V21 although Vegas launches in earlier versions.

I don't use it for a couple of reasons. One major problem when using this debugging approach is that you can no longer use drag-drop operations since I always run Visual Studio as Administrator. And since many of the tools I've written support drag-drop, it can't be used. Additionally, you have to load Vegas each time you compile and want to test changes that you've made, which, as you know, takes quite a bit of time.

A far better approach (IMHO) and the one I use when possible is to simply keep Vegas "open" so that you don't have to launch it each time you want to debug changes you've made. For scripts, the following command will enable you to do that.

vegas.UnloadScriptDomainOnScriptExit = true;

Additionally, I make extensive use of simple MessageBox's when trying to identify lines of code that might be causing Vegas to crash during testing. Also try-catch regions to display the call stack when errors occur.

@ccscotty

I presume this is what you mean??

If so, I have rarely, if ever, used this debugging approach. I just checked and see that it doesn't work for V20 and V21 although Vegas launches in earlier versions.

I don't use it for a couple of reasons. One major problem when using this debugging approach is that you can no longer use drag-drop operations since I always run Visual Studio as Administrator. And since many of the tools I've written support drag-drop, it can't be used. Additionally, you have to load Vegas each time you compile and want to test changes that you've made, which, as you know, takes quite a bit of time.

A far better approach (IMHO) and the one I use when possible is to simply keep Vegas "open" so that you don't have to launch it each time you want to debug changes you've made. For scripts, the following command will enable you to do that.

vegas.UnloadScriptDomainOnScriptExit = true;

Additionally, I make extensive use of simple MessageBox's when trying to identify lines of code that might be causing Vegas to crash during testing. Also try-catch regions to display the call stack when errors occur.

 

Thanks form the information! Yeah, I assumed that once Vegas loaded and ran the script once it was locked until the program closed. That bit of code should be helpful.

New build 1.0.3.32 is now available.

Change log may be found here. https://tools4vegas.com/wp-content/uploads/HappyOtter-Change-Log.pdf

IMPORTANT: Limited rendering support for Vegas 22

• Rendering tools using DebugMode FrameServer do NOT work due to Vegas version changes
• Attempted use of rendering tools  with previous HOS builds will lead to Vegas 22 crash
• Only rendering tools supporting native Vegas Renderers continue to work
• New HOS build will be released upon completion of updates to FrameServer

New versions of Nvencc64, Qsvencc64, Vceencc64, MPC-HC

New Tools and Features

• KwikPreview2 – New Tool
  • Combines KwikPreview and KwikZoomPreview features  into a single tool
  • Option to use native Vegas renderers and templates
  • Additional split-screen comparisons—Left/Right and Top/Bottom
  • Option to compare the same half—E.g. compare left half for 2 different tracks
  • Option to select events in addition to render loop for preview
• Render Plus
  • Added MP4 chapter support using Vegas marker position and label

Bug Fixes

• Speech to Text and Text Assist—still failed with Vegas 21 Build 314 and 315—fixed

Known issue—help file needs updating for new KwikPreview2 and RenderPlus tools

Here is the direct download link. https://tools4vegas.com/ru4f7l9rxql9ykg/

Thank you for the quick turnaround with the new release! @wwaag I am having an issue suddenly. When trying to use ImportAssist to rewrap my MOV files to MP4, it creates a 0 byte file. Is there a log file I could look at to see what the issue here may be? This was working well previously. (I am not sure that this is a VP22 issue. When I go back to VP21 it has the same issue now too)

@Shaun_K

Just tried rewrapping an iPhone 4K 60P HEVC MOV file to an MP4 file and it worked without issue.

Note that the version (21 or 22) should not be affected since the DebugMode FrameServer is not used in this tool.

To troubleshoot, navigate to C:\ProgramData\HappyOtterScripts\Magix Vegas Pro\ImportAssist.

Then open the file "C:\ProgramData\HappyOtterScripts\Magix Vegas Pro\ImportAssist\rewrapLogFile.txt" with any text editor which gives the FFmpeg log which will usually tell you the problem. In the same folder you can also view the actual FFmpeg command line that is being used (rewrapCommandLine.txt) and also the script execute log (ImportAssistExe.log).

Let me know what you find.

@Shaun_K

Just tried rewrapping an iPhone 4K 60P HEVC MOV file to an MP4 file and it worked without issue.

Note that the version (21 or 22) should not be affected since the DebugMode FrameServer is not used in this tool.

To troubleshoot, navigate to C:\ProgramData\HappyOtterScripts\Magix Vegas Pro\ImportAssist.

Then open the file "C:\ProgramData\HappyOtterScripts\Magix Vegas Pro\ImportAssist\rewrapLogFile.txt" with any text editor which gives the FFmpeg log which will usually tell you the problem. In the same folder you can also view the actual FFmpeg command line that is being used (rewrapCommandLine.txt) and also the script execute log (ImportAssistExe.log).

Let me know what you find.

I think this is where the issue happens:
2024/07/30  18:34:02  --[mp4 @ 000001fd7ad40a40] Could not find tag for codec pcm_s24be in stream #1, codec not currently supported in container
2024/07/30  18:34:02  --Could not write header for output file #0 (incorrect codec parameters ?): Invalid argument
2024/07/30  18:34:02  --Stream mapping:
2024/07/30  18:34:02  --  Stream #0:0 -> #0:0 (copy)
2024/07/30  18:34:02  --  Stream #0:1 -> #0:1 (copy)
2024/07/30  18:34:02  --    Last message repeated 1 times

I see the problem. Your mov file has pcm audio which is not generally supported within an MP4 container. This has been an issue with FFmpeg for years. Could you upload a sample mov file somewhere that I could download and take a look.

BTW, why do you want to rewrap to an MP4 container since the most recent versions of Vegas handle MOV files quite well?

I see the problem. Your mov file has pcm audio which is not generally supported within an MP4 container. This has been an issue with FFmpeg for years. Could you upload a sample mov file somewhere that I could download and take a look.

BTW, why do you want to rewrap to an MP4 container since the most recent versions of Vegas handle MOV files quite well?

This is my workaround to the timecode issue I am having. Vegas Pro doesn't recognise my timecode in the mov file. When I rewrap with your tool to MP4, then it sees the timecode just fine. (I have raised this a few times here on the forum). I will find a sample for you and post.

@wwaag

I want to find and locate all transitions at the timeline.

If I open an old project with a new version of Vegas PRO it sometimes happens that there is an old transition which is no longer activated. At this point I want to replace this transition with a new one.

I use Vegas PRO 21.0 Build 315 and Happy Otter Script 1.0.3.32, but I do not find a function to do this.

Can you help me?

@PIT

Sorry. None of the tools in HOS or the HOS Free Tools Library will do what you are asking. As @jetdv replied in another thread, a special script would have to be written.

@wwaag @PIT

The Free Tools Script "Regions From Transitions" does this. It will create Regions on all existing transitions, making it easier to locate.

https://tools4vegas.com/regions-from-transitions/

+1 on this!

@joelsonforte.br

Thanks for reminding me of this text script. It could easily be changed to add markers rather than regions.

@joelsonforte.br, that script simply shows every overlap of events on the selected track(s). It doesn't actually look for "Transitions" - all crossfades will get a region as well.

Please try this script. It will list ALL TRANSITIONS in project and where on the timeline they are located. It's just a string list but it will show all actual transitions being used.

https://www.vegascreativesoftware.info/us/forum/find-and-locate-all-transitions-in-a-project--146712/#ca921437