Comments

Reyfox wrote on 12/12/2023, 1:44 PM

I am waiting on a fix for AMD graphics cards with the latest drivers. In the "here and now", TP7 isn't working. It will load, but as soon as I click on Library... that's it.

I'm sure I can "roll back" to 22.5.1, but it should work with the latest drivers and doesn't. NBFX is aware of the issue and said they are working on it.... everything else in TotalFX 360 is working.

Last changed by Reyfox on 12/12/2023, 1:45 PM, changed a total of 1 times.

Newbie😁

Vegas Pro 22 (VP18-21 also installed)

Win 11 Pro always updated

AMD Ryzen 9 5950X 16 cores / 32 threads

32GB DDR4 3200

Sapphire RX6700XT 12GB Driver: 25.3.1

Gigabyte X570 Elite Motherboard

Panasonic G9, G7, FZ300

Mykee wrote on 4/22/2024, 4:19 PM

I am very angry! I simply cannot use Titler Pro 7 properly with Vegas 21 B300. I record a title as Media Generator, but as soon as I want to adjust the length, I get undo buffer error many times. If I then try to change anything in the video project, again undo buffer error. I have to save, restart the whole Vegas. I already reported not one memory dump. Very annoying not to be able to use it and it keeps crashing Vegas.

jetdv wrote on 4/22/2024, 6:52 PM

@Mykee, if you can provide a repeatable situation to NewBlue support, they'll definitely look into it. However, NewBlue has nothing to do with VEGAS' undo buffer.

Mykee wrote on 4/22/2024, 11:36 PM

@jetdv But if I don't use Titler Pro OFX, I don't get this error. Yesterday I made 12 videos, all of them had the error when using Titler Pro. Whether it was resizing, inserting a second title, sometimes even inserting the first title. It's just unusable, and the undo buffer error was caused by Vegas.

Tommaso-Greco wrote on 4/23/2024, 6:52 AM

@jetdv But if I don't use Titler Pro OFX, I don't get this error. Yesterday I made 12 videos, all of them had the error when using Titler Pro. Whether it was resizing, inserting a second title, sometimes even inserting the first title. It's just unusable, and the undo buffer error was caused by Vegas.

I solved my problem by going back to using Vegas 20, when I have to use Titler Pro 7. Unfortunately there is nothing to be done, Titler Pro 7 is no longer supported by Vegas Pro 21, it can only be used stand alone. I believe it is a political-administrative choice.
Vegas Pro sucks, especially for constant crashes, however it is the most user friendly software out there. What can I say, it takes a lot of patience.

Mykee wrote on 4/23/2024, 7:11 AM

@Tommaso-Greco Upgrade your version of Titler Pro to the latest version, it will open automatically in Vegas 21. It "only" gives an undo error.

Dexcon wrote on 4/23/2024, 7:24 AM

Re TP7 builds, the TP7 build in TotalFX build 7.8.230213 (so from Feb last year) works fine for me in Vegas Pro 21.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 19.0.3, BCC 2025, Mocha Pro 2025.0, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

jetdv wrote on 4/23/2024, 7:49 AM

@Tommaso-Greco, please show a screenshot of your App Manager (but please hide the serial numbers listed.)

When I add Titler Pro and go to Help - About in the designer, mine is showing as version 231017

I have TotalFX 230905 installed.

If you go to www.newbluefx.com/login and log in and go to "My Account", and you will see your products listed there. Go to Activations/Downloads and then click on Downloads.There you will see many different versions available so you can try a different version than what you currently have installed.

Tommaso-Greco wrote on 4/23/2024, 9:33 AM

@Tommaso-Greco, please show a screenshot of your App Manager (but please hide the serial numbers listed.)

I uninstalled Live2Post at the request of one of the many support people who tried (in vain) to fix the problem. I finally received the final email from Vegas Pro confirming that the Title Pro 7 program no longer works with Vegas Pro 20 and that I would have to use the "stand-alone" version of the software.
But now I read that @Mikee uses it instead (apart from one mistake that I didn't understand). WTF! I'm tired of begging for technical support, also because, as specified by them, I was told that Titler Pro7 NO longer works with Vegas Pro 20.

Reyfox wrote on 4/23/2024, 12:16 PM

@Tommaso-Greco in your User Profile, it's all blank. What are your specific PC specs? You can add that to your Signature like everyone else. Saves a lot of repeat questions asking for the same info. See my Signature below.

Newbie😁

Vegas Pro 22 (VP18-21 also installed)

Win 11 Pro always updated

AMD Ryzen 9 5950X 16 cores / 32 threads

32GB DDR4 3200

Sapphire RX6700XT 12GB Driver: 25.3.1

Gigabyte X570 Elite Motherboard

Panasonic G9, G7, FZ300

jetdv wrote on 4/23/2024, 1:45 PM

For everyone that's had problems. I've always recommended this version:

https://s3.wasabisys.com/files.newbluefx.com/Win/titler/NewBlueTitlerPro7VegasPro-230907.exe

 

jetdv wrote on 4/23/2024, 1:46 PM

You might also remove "Live2Post" first and then reinstall this version. Live2Post is, basically, a stripped down version of Titler Pro 7 which is definitely not needed since you have the full version.

Mykee wrote on 4/25/2024, 12:56 PM

For everyone that's had problems. I've always recommended this version:

https://s3.wasabisys.com/files.newbluefx.com/Win/titler/NewBlueTitlerPro7VegasPro-230907.exe

 

I have 231017 version. Does your version work better, does it not cause such crashes?

Update: I installed this version of Vegas, but unfortunately it is not compatible with my Ultimate license. Hooray.

Mykee wrote on 4/25/2024, 1:20 PM

Here is my undo buffer problem, Live2Post has been uninstalled:

paul-marshall wrote on 4/26/2024, 7:01 AM

I have a 'quite like/hate' relshionship with TitlerPro7. For some time now I have only used TP 7 (V 7.9, 231017) in VP21 by using the stand alone version and exporting to a movie file which I can import into Vegas, that being the most reliable and least frustrating why to make titles.

But I notice that it is actually working quite well in VP21 build 300 so I have gone back to using it as it should be.
Incidentaly, why is exporting to a Movie file deprecated?

 

Windows 11.0 (64-bit)
Intel® Core™ i9 Eight-Core Processor i9-11900K (3.5GHz) 16MB Cache
Motherboard GIGABYTE Z590 UD AC (C (LGA1200, USB 3.2)
64GB Corsair VENGEANCE DDR4 3200MHz (4 x 16GB)
GPU Nvidia GEFORCE RTX3060Ti
I/O drives: Intel SSD PEKNU020TZ 2TB, Samsung SSD 870 EVO 1TB, Samsung SSD 870 EVO 1TB
SEAGATE BARRACUDA SATA-III 3.5" HDD, 2TB, 6GB/s, 7200RPM, 256MB CACHE
Audio: Soundblaster Z SE
Cameras: Sony AX-700, A7-IV, RX10-II
Vegas Po 22 latest version. Vegas user since V10

 

Dexcon wrote on 4/26/2024, 7:22 AM

@paul-marshall

Incidentaly, why is exporting to a Movie file deprecated?

Are you asking why Quicktime is a deprecated feature in Vegas Pro? If yes, Quicktime is a deprecated feature because Apple ceased QT support for Windows some 8 years ago in 2016. I recall that years ago Vegas staff advised on the forum that QT was deprecated because the lack of QT support for Wndows updates since 2016 (that would now include Windows 11) thus the possibility that aged QT inclusion in VP's default programming might have unwanted side-effects.

Last changed by Dexcon on 4/26/2024, 7:23 AM, changed a total of 1 times.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 19.0.3, BCC 2025, Mocha Pro 2025.0, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

paul-marshall wrote on 4/26/2024, 7:43 AM

Are you asking why Quicktime is a deprecated feature in Vegas Pro?

Understood. In that case I suppose my question should really be directed at Newblue as to why the only available export to video format is 'Movie File (deprecated)'. I shall ask them.

Windows 11.0 (64-bit)
Intel® Core™ i9 Eight-Core Processor i9-11900K (3.5GHz) 16MB Cache
Motherboard GIGABYTE Z590 UD AC (C (LGA1200, USB 3.2)
64GB Corsair VENGEANCE DDR4 3200MHz (4 x 16GB)
GPU Nvidia GEFORCE RTX3060Ti
I/O drives: Intel SSD PEKNU020TZ 2TB, Samsung SSD 870 EVO 1TB, Samsung SSD 870 EVO 1TB
SEAGATE BARRACUDA SATA-III 3.5" HDD, 2TB, 6GB/s, 7200RPM, 256MB CACHE
Audio: Soundblaster Z SE
Cameras: Sony AX-700, A7-IV, RX10-II
Vegas Po 22 latest version. Vegas user since V10

 

jetdv wrote on 4/26/2024, 7:45 AM

In Titler Pro, exporting to a Movie file gave you an MOV file that was a png sequence. That format works very well except for a couple of issues: VEGAS requires Quicktime to read those files and the newest versions of Quicktime on the Mac no longer support that format!

Finally Titler Pro will export a format that VEGAS will read natively!

Dexcon wrote on 4/26/2024, 7:58 AM

@paul-marshall  ... fair enough and a good idea ... but if you are using TP7 as a plugin in Vegas Pro, you don't need TP's .MOV export option. Just by placing it on the timeline as a media generator event or directly on to a video event as an FX via the plug-in chooser and hitting the 'green tick' icon in TP7's lower LH corner is all that is needed. And you can use the "File / Save to Library / Project" option to save the project to a folder of your choice.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 19.0.3, BCC 2025, Mocha Pro 2025.0, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

Former user wrote on 4/26/2024, 8:10 AM

@paul-marshall It's also because the exported video needs an alpha channel, MP4 doesn't support alpha, there's a few others that do like AVI & some image sequences, PNG, EXR.., there's also .mov ProRes but that's tied in to Adobe n legally gets complicated, apparently. So that doesn't leave a lot of choices.

jetdv wrote on 4/26/2024, 9:05 AM

If not added directly on the timeline, the export format to use is PNG Sequence. That will create a series of PNG files that can be imported directly by VEGAS. As @Former user mentioned, the requirement is that the format must support alpha channel and there's not many options available - especially that are reasonable in size. PNG Sequence is much smaller than uncompressed AVI.

paul-marshall wrote on 4/26/2024, 10:05 AM

If not added directly on the timeline, the export format to use is PNG Sequence.

Indeed, but it is the only option apart from the deprecated .mov fille. I dont see a png sequence as convenient but luckily the .mov files work well. The whole point of doing this is because using Titler Pro 7 as a plugin in Vegas Pro has in the past been massively frustrating with frequent crashes but the latest VP update has imrpoved things dramatically.

The point of my post though was to say to @Tommaso-Greco that TP7 does in fact work well in VP21 build 300.as a plugin.

Windows 11.0 (64-bit)
Intel® Core™ i9 Eight-Core Processor i9-11900K (3.5GHz) 16MB Cache
Motherboard GIGABYTE Z590 UD AC (C (LGA1200, USB 3.2)
64GB Corsair VENGEANCE DDR4 3200MHz (4 x 16GB)
GPU Nvidia GEFORCE RTX3060Ti
I/O drives: Intel SSD PEKNU020TZ 2TB, Samsung SSD 870 EVO 1TB, Samsung SSD 870 EVO 1TB
SEAGATE BARRACUDA SATA-III 3.5" HDD, 2TB, 6GB/s, 7200RPM, 256MB CACHE
Audio: Soundblaster Z SE
Cameras: Sony AX-700, A7-IV, RX10-II
Vegas Po 22 latest version. Vegas user since V10

 

paul-marshall wrote on 4/28/2024, 4:28 AM

The reply from NewBlue support was as others have said here:
"The "Movie File" export create an MOV PNG-sequence file. To load that in VEGAS requires having Quicktime installed. Plus, Quicktime on the Mac has stopped supporting PNG-Sequence files (not sure why). Now you will want to export to PNG Sequence. This will create a folder with a sequence of PNG files. The good news is that the PNG Sequence can be imported direct by VEGAS without Quicktime."

I find it astonishing that a Windows based system is so dependent on Apple that when support is withdrawn for the aging QT that we are left with no readily available video format that has an alpha channel. I find importing a png sequence to be a tedious clunky work around compared to simply drag and dropping a .mov file onto the timeline. For a frequently used title it's much more convenient to use a video file even than using the TP7 as a plug-in on the timeline. I suppose I could import my frequently used title as a png sequence then render to video file. But which format? - I only see APPLE Prores with alpha. What a situation!

Windows 11.0 (64-bit)
Intel® Core™ i9 Eight-Core Processor i9-11900K (3.5GHz) 16MB Cache
Motherboard GIGABYTE Z590 UD AC (C (LGA1200, USB 3.2)
64GB Corsair VENGEANCE DDR4 3200MHz (4 x 16GB)
GPU Nvidia GEFORCE RTX3060Ti
I/O drives: Intel SSD PEKNU020TZ 2TB, Samsung SSD 870 EVO 1TB, Samsung SSD 870 EVO 1TB
SEAGATE BARRACUDA SATA-III 3.5" HDD, 2TB, 6GB/s, 7200RPM, 256MB CACHE
Audio: Soundblaster Z SE
Cameras: Sony AX-700, A7-IV, RX10-II
Vegas Po 22 latest version. Vegas user since V10

 

Dexcon wrote on 4/28/2024, 5:50 AM

@paul-marshall  ... there is another option in Vegas Pro for rendering with an alpha channel but with a significant disadvantage.

In Render As, choose Video for Windows and then a template that is either what you want or is the closest to what you want.

If you need to change the frame size, say to 4K, in the 'Frame size' field, select '(Custom frame size)' and then the width and height fields become available for you to manually select the W and H.

In the 'Video format' field, select 'Uncompressed' and then check the 'Render alpha channel' checkbox, then click 'OK' and render. The AVI video will render with an alpha channel.

The disadvantage: Uncompressed AVI files are huge. But then so have been the few ProRes renders that I've done.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 19.0.3, BCC 2025, Mocha Pro 2025.0, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz