Issue when creating new session, template or blank

[WarioBoi116]

Hey, all.

I recently installed Pro Tools First because I bought an audio interface (the Behringer U-Phoria UMC404HD) and wanted to get started with some recording and mixing. I successfully made an Avid account and downloaded and installed all the necessary files.

However I now have a problem when trying to create a new session, either blank or from a template. Whenever I click "Create", on a blank session or a template or whatever, it will attempt to load, the mixing windows will pop up for a second, and then disappear, leaving me back at the main Pro Tools First window with a little pop up that says:

'Could not save as "0000" because Assertion in "d:\ code\ scm\ protools\ release\ 2020\ r2\ protools\ app\ document\ uprojectbundlemgr.cpp", line 1701.'

I've looked all through the internet and database and I have seen nothing that fixes this error. When I read it, it confuses me more, because I haven't tried to save anything. I also tried looking for the specified file path and file but I couldn't find them either.

I have tried:

• Going through the Avid support page and trying all of the small settings fixes concerning battery or performance or whatever
• Searching that Seagate Database
• Searching google with that parameter they linked, the "site:http://duc.avid.com/index.php" thing

This is not too urgent but all the same I would like a response or a person to work with on this fairly soon.

Thank you! :)

Specs:

ID
Host Name : Ewan-PC
Workgroup : WORKGROUP

Computer
Model : Dell Precision M6600
Serial Number : 183****
Chassis : Dell Laptop
Mainboard : Dell 04YY4M
Serial Number : /183BCT1/CN7************
BIOS : Dell A18 09/14/2018
Intel vPro : 7.1.91.3272
Total Memory : 16GB DDR3 SO-DIMM

Processors
Processor : Intel(R) Core(TM) i7-2860QM CPU @ 2.50GHz (4C 8T 1.8GHz/3.6GHz, 1.8GHz IMC, 4x 256kB L2, 8MB L3)
Socket/Slot : FC PGA988 (G2)

Chipset
Memory Controller : Dell Core2M (Sandy Bridge-M) Mobile DRAM Controller 100MHz, 2x 8GB DDR3 SO-DIMM 1.33GHz 128-bit

Memory Module(s)
Memory Module : Samsung M471B5273CH0-CH9 4GB DDR3 SO-DIMM 2Rx8 PC3-10700SO DDR3-1334 (9-9-9-25 4-34-10-5)
Memory Module : Samsung M471B5273CH0-CH9 4GB DDR3 SO-DIMM 2Rx8 PC3-10700SO DDR3-1334 (9-9-9-25 4-34-10-5)
Memory Module : Samsung M471B5273CH0-CH9 4GB DDR3 SO-DIMM 2Rx8 PC3-10700SO DDR3-1334 (9-9-9-25 4-34-10-5)
Memory Module : Samsung M471B5273CH0-CH9 4GB DDR3 SO-DIMM 2Rx8 PC3-10700SO DDR3-1334 (9-9-9-25 4-34-10-5)

Video System
Monitor/Panel : LG Generic PnP Monitor (1920x1080, 4259G€173WF3
, 17.3")
Video Adapter : NVIDIA Quadro 3000M (240S 5C SM5.5 900MHz, 2GB 2.51GHz, PCIe 2.0 x16)

Graphics Processor
OpenCL : NVIDIA Quadro 3000M (5S 5C SM1.1 450MHz, 2GB 2.51GHz)
D3D 11 : NVIDIA Quadro 3000M (240S 5C SM11.5 450MHz, 2GB 2.51GHz)
OpenGL : Quadro 3000M/PCIe/SSE2 (2GB)

Storage Devices
Disk : LITEONIT LCT-512M3S (512.1GB, SATA600, SSD)
Optical : MAT****A BD-RE UJ252 (SATA150, BD-RE, DVD+-RW, CD-RW, 2MB Cache)

Logical Storage Devices
RECOVERY : 752MB (NTFS, 4kB) @ LITEONIT LCT-512M3S (512.1GB, SATA600, SSD)
OS (C:) : 476GB (NTFS, 4kB) @ LITEONIT LCT-512M3S (512.1GB, SATA600, SSD)
Hard Disk : 539MB (NTFS, 4kB) @ LITEONIT LCT-512M3S (512.1GB, SATA600, SSD)
Optical Drive (D:) : N/A @ MAT****A BD-RE UJ252 (SATA150, BD-RE, DVD+-RW, CD-RW, 2MB Cache)

Peripherals
LPC Hub Controller #1 : Dell QM67 LPC Controller
Audio Device : Dell Cougar Point High Definition Audio Controller
Audio Codec : Integrated Device Tech 76E7
Audio Device : Dell GF104 High Definition Audio Controller
Audio Codec : nVidia 0012
Audio Codec : nVidia 0012
Audio Codec : nVidia 0012
Parallel Port(s) : 1
Disk Controller : Dell ICH8 Mobile SATA RAID Controller
USB Controller #1 : Dell Cougar Point USB Enhanced Host Controller #2
USB Controller #2 : Dell Cougar Point USB Enhanced Host Controller #1
USB Controller #3 : Dell Renesas Electronics USB 3.0 Host Controller
SMBus/i2c Controller #1 : Intel ICH SMBus

Printers and Faxes
Printer : Microsoft Software Printer Driver (300x300, Colour)
Printer : Microsoft XPS Document Writer v4 (600x600, Colour)
Printer : Microsoft Print To PDF (600x600, Colour)
Fax : Microsoft Shared Fax Driver (200x200)
Printer : Brother DCP-L2540DW series (600x600)

Scanners & Cameras
Scanner : Microsoft Brother DCP-L2540DW series [3c2af41e9bac] (Scanner, USB)

Biometrics
Voice : Analog NUI Voice Virtual Sensor (Voice)

Network Services
Network Adapter : Intel(R) 82579LM Gigabit Network Connection (Ethernet)
Wireless Adapter : DW1501 Wireless-N WLAN Half-Mini Card (802.11n (HT), AES-CCMP, 101.25Mbps / 58.5Mbps)

Operating System
Windows System : Microsoft Windows 10 Professional 10.0.19041
Platform Compliance : x64

Performance Enhancing Tips
Warning 2513 : TPM not detected. Some security features are unavailable.
Tip 2 : Double-click tip or press Enter while a tip is selected for more information about the tip.

[Darryl Ramm]

Welcome to DUC.

First, important semantics, you are not creating a session, you are trying to create a project. One of the crippling limitations of Pro Tools First is it only works with cloud based projects not traditional Pro Tools sessions.

The first thing you should find Googling for this error message is https://avid.secure.force.com/pkb/ar...-cpp-line-1693

Did you try the plugin thing there? What exact playback engine/interface option showing up in the playback engine dialog panel are you trying to use? What exact ASIO driver/version did you install for the U-Phoria UMC404HD.

Forget everything else claimed anywhere by Avid or others, including on the above knowledge base article, if you actually want to work stably/productively in any version of Pro Tools on Windows you should have an interface like the U-Phoria UMC404HD that natively supports ASIO, you should not rely on ASIO4ALL. Do not install ASIO4ALL and if you have then uninstall it. Make sure you hold down the N key while Pro Tools is starting until the Playback Engine dialog appears and select the correct native ASIO interface.

Pro Tools First is so crippled and fussy to get running than almost any other DAW, and it’s cloud projects are so unreliable that I would not waste my time trying to use it. Other DAWS including Reaper for Windows users would be a better choice, or if you want Pro Tools compatibility then purchase a subscription to Pro Tools (standard) and work in local sessions, not unreliable projects.

[WarioBoi116]

First of all thanks a bunch, you seem like a nice person.

I will keep in mind the correct terminology.

I just tried deleting that plug in setting folder, Xpand!2 or something, it did not change the problem at all.

I don't understand your next question. All I am trying to do/use is just open up Pro Tools First, and then click create project with the "use a template" box unchecked. I am interacting with nothing else.

The driver provider for the UMC404HD is Behringer, the date is 3/14/2019, the version is 4.59.0.56775, and the digital signer is Microsoft Windows Hardware Compatibility Publisher. My computer thinks it's up to date when I click update driver. It should be up to date because I downloaded it off of the official Behringer product page only a week ago.

I haven't messed with any ASIO drivers or anything, the only driver I have installed is the aforementioned one.

When I hold down the N key as Pro Tools First starts, the Playback Engine window shows up, and I have selected UMC ASIO Driver, with Outputs 1-2 (vs. 3-4) and a sample rate of 48khz. My laptop can handle 48 easily I am sure so that is not the problem.

Your last comment interests me. What are the advantages of using Reaper over Pro Tools First? How steep is the learning curve?

I will use Reaper if I cannot fix this error then. If you think it's less of a hassle to just use Reaper rather than try and fix Pro Tools First that is fine with me. I'm looking to not spend any more money right now so I'm not interested in a Pro Tools Monthly subscription.

Again, thanks a bunch. Please get back to me when you can. :)

[Darryl Ramm]

Originally Posted by WarioBoi116

I just tried deleting that plug in setting folder, Xpand!2 or something, it did not change the problem at all.

The knowledge base article did not say delete the plugin setting folder, it said to uninstall the plugin from the (Windows) control panel. I have no idea what causes that plugin to trip up with this issue, or if it's really the cause here but it sounds like you are not exactly following what the KB article said to do??

The driver provider for the UMC404HD is Behringer, the date is 3/14/2019, the version is 4.59.0.56775, and the digital signer is Microsoft Windows Hardware Compatibility Publisher.

OK that's the right driver.

My computer thinks it's up to date when I click update driver.

Uh don't do that. Windows is brain dead, you should not trust it to check for any critical driver. Do that yourself.

When I hold down the N key as Pro Tools First starts, the Playback Engine window shows up, and I have selected UMC ASIO Driver, with Outputs 1-2 (vs. 3-4) and a sample rate of 48khz. My laptop can handle 48 easily I am sure so that is not the problem.

That's the correct ASIO driver. So nothing else to try with that driver.

Your last comment interests me. What are the advantages of using Reaper over Pro Tools First? How steep is the learning curve?

A lot less steep than learning how to use a DAW that is not running. At this point I'd just not waste more time on Pro Tools First if the KB article thing does not solve the problem. Even if you get it working you end up with a very limited DAW with flakey cloud project storage and poor support.