First, here is my setup:
Rig:
Windows 10
AMD Ryzen ThreadRipper 3970x 32-core Processor (64 CPUs)
Nvidia GeForce RTX 3080 Ti
125 GB Ram
New installation of Premiere pro 2021 with updated importer files as requested here and downloaded here
When I import a video file that has already been processed in insta360 stitcher, and that look like this:
I start getting this error while premiere is trying to "Generate peak file", I don't even need to drag the file into the timeline before it starts complaining. I have been dealing with this problem for over a day and am at my wits end, here is what I have tried and where I get it from:
Placing files in the C drive instead of D drive suggested here
Disable Cuda and used "Software only" as the Playback and Rendering setting suggested here and here
Delete render files - this wasnt possible because it is greyed out but suggested here
Additionally I changed my graphics card Drivers to Studio Driver instead of Game-ready driver, this did not work either
The next thing I can try is to reroll back to pre 14.4 9 but I would really rather not have to do this.
==Edit==
I installed v 14.3 and got the same error so I installed 14.2 where i also got the same issue and then moved onto 14.1 where I am still getting the same issue. So this downgrade also is not working:
I am really at a loss as to what to try next, any suggestions would be most welcome.
Thank you.
I finally got this fixed, it turns out it was the plugin that came with 3.0.0 version of insta360 stitcher + updates.
Insta360 sent me their updated Stitcher 3.1.2 which comes with a brand new plugin but is not yet listed on their website. They have given me permission to post the file here for anyone who wishes to download it.
https://static.insta360.com/Insta360Stitcher/Insta360Stitcher_Winx64_3.1.2_build_202012301001.exe
Related
My Unity Editor was showing a blank white screen when trying to start a project. Image here:
This is for the Karting Microgame. When it loads it only displays a blank screen. When clicking the play button there is sound but nothing showing on the screen. This issue also occurs for other Unity3D microgames. I suspect it is an error with the graphics setup or maybe a bug?
Technical details:
Dell G15 laptop
Ubuntu 20.04
Unity version 2020.3.21f1, installed via Unity Hub
NVIDIA Graphics Card (NVIDIA GeForce RTX 3060 GPU)
NVDIA Driver Version 470 (https://packages.ubuntu.com/focal/nvidia-driver-470)
I also have an Intel integrated graphics card on my machine. Tried switching to integrated graphics via the sudo prime-select intel command but it didn't work. Also tried installing Dell G15 graphics drivers from the Dell website but it seems like they only have Windows graphics drivers. Currently the screen is still blank.
Relevant links:
Unity forum discussion, have the exact same problem except for Ubuntu:
https://forum.unity.com/threads/uni...n-problem-might-know-the-real-problem.545441/
Dell graphics driver link, but seems to only have for Windows:
https://www.dell.com/support/home/en-us/product-support/product/g-series-15-5510-laptop/drivers
Tutorial on switching graphics cards. First tried updating my drivers via the ubuntu-drivers command from my existing 470 version to the recommended 510 version, but ran into an error saying my computer holds broken packages. Then tried switching to Intel integrated graphics card via the prime-select command but it caused my GUI to break (had to switch back to NVIDIA via the command line.)
https://www.linuxbabe.com/desktop-linux/switch-intel-nvidia-graphics-card-ubuntu
Any help would be appreciated.
Open windows in safe mode and try again also there might be other programs open that are causing the blank screen for example vpn could cause it
I need to share this!
Try this:
In your project, delete the Library folder. I found that CurrentLayout-default.dwlt in particular must be deleted, so you can try that first if your project is big and want to avoid long rebuilding times.
In ~/.config/unity3d/Preferences/Editor-5.x, delete the Layouts folder
In ~/.config/unity3d, delete the Browser folder
In ~/.config/unity3d, delete the Editor folder (there is one sub-folder per editor version but the serial number cannot be trivially matched with a human-readable version, so maybe just delete the whole folder)
Restart the project
I found 1, 2 & 3 to work in my case, and only 1+2 or 2+3 not to work. At least it should work when installing a new editor / re-installing an editor version. I also did 4 at some point so it may be needed for editor versions already installed. I did 2 at the beginning so not sure if required.
Updated to 2019.1.12f1 and now have 62 errors. Project had no errors prior.
What happened:
Updated to 2019.1.12f1
How we can reproduce it:
Update from 2018.2.10f1 to 2019.1.12f1.
Most errors are assembly reference related and associated to UI Elements.
License type: Pro
Bug Reported. Case #: 1172477
Unity Version 2019.1.12f1_f04f5427219e
Computer: MB Pro Intel Core i5 2.7 GHz 8 GB ; Intel Iris Graphics 6100 1536 MB ; Mac OS X
I imagine I could go in and deactivate all references that point to non-existent packages and hope it doesn't screw anything up, but I'd like to know why the packages didn't arrive in the new build and where to find them.
Tried reimporting assets. Didn't help.
Tried deleting manifest and the newly generated one didn't help.
Expected for the project which was previously fine and working to work in the new version without 62 errors.
For those interested, Unity answered the bug report and the fix cleared all errors. Solution below.
Hi,Thanks for reaching out to us!
It looks like the issue is caused by the Unity Recorder. The scripts used by it are referencing Libraries that were either changed or deleted. Perhaps you have installed the Recorder from the Asset Store before upgrading?
Deleting Unity Recorder folder from the Assets gets rid of the errors. I have then re-installed the Recorder via Package Manager and this seems to resolve the issue.
Please let me know if this helps.
If you have any further questions feel free to add them in your reply.
Best regards,
Gytis
Customer QA Team
Since upgrading from MAMP 3 to MAMP 4, the GUI hangs on each action. Clicking something like the menu occurs after around 30 seconds of the spinning wheel of death. This happens for any action within the interface. Running 10.12.2
This almost makes the software unusable, as I can't configure the interface to begin development.
My experience was identical. Searching for some errors I ended up running Tools > Verify MySQL Databases... Among tons of OK'ed databases, several had errors - innodb_index_stats, innodb_table_stats, slave_master_info, slave_relay_log_info, and slave_worker_info.
From here a search lead me to mysql error: Table “mysql”.“innodb_table_stats” not found.
So, I deleted all the .frm and .ibd of the tables above and I ran the five-tables.sql file in Terminal: source five-tables.sql
Now MAMP Pro 4 runs smoothly and responsive.
Thanks, Kay Nelson.
I ended up doing a search for MAMP in all parts of the file, and removed every reference to it, after running the uninstaller.
I also removed references to any PHP & memcache not in the /Applications/MAMP folder.
I renamed /Applications/MAMP to /Applications/MAMP-old and reinstalled. This set everything up fresh and appears to be working. Something with a conflict with a system binary or other package was causing the issue.
I downloaded the new beta version of Unity (5.5.0b2) and when I open any project I always get an exception in the console that says:
The file C:\Program Files\Unity 5.5.0b2\Editor\Data\MonoBleedingEdge\lib/mscorlib.dll is an invalid CIL image
I really don't have any clue to what this means and what to do about it, I can't even enter play mode, any advice on how to solve this?
I'm currently on Windows 7 64 bit, the Unity version installed is 64 bit, too, I tried installing it on the main hard drive and the secondary but the error is still there.
I installed version 5.4.0f3 and replaced the folder MonoBleedingEdge of the version 5.5.0b2 with the one found in the previous version.
The folder is located at Unity 5.5.0b2\Editor\Data.
I'm running Windows Server 2008 with a Blackmagic Decklink card. Everything works fine with the GUI but when I try to start from command line it exits with an unknown error.
Any ideas?
Note: I have the desktop experience enabled.
Looks like a frequent problem that effects many FMLE users. Common suggestions include:
use the absolute latest version of FMLE
update DirectX
update all video and audio-related drivers
remove/rename startup.xml from "[volume]/Users/[user name]/AppData/Roaming/Adobe/Flash Media Live Encoder [version]/" so the program can get clean settings
There is also a small chance that tweaks to common security measures may help, such as disabling Data Execution Protection for all but essential OS files or exclude program directories in your anti-virus software (only if essential, of course!)
I found out what the problem was, apparently if the fmesessions.dat (C:\ProgramData\Adobe\Flash Media Live Encoder 3.2) gets large enough FMLEcmd.exe fails.