Jump to content

Noel Borthwick

Staff
  • Content Count

    1,712
  • Joined

  • Last visited

  • Days Won

    25

Noel Borthwick last won the day on October 3

Noel Borthwick had the most liked content!

Community Reputation

1,739 Excellent

About Noel Borthwick

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Please attach the minidump file listed in the error message so we can establish the cause off the crash. Have you tried the latest update release that we plan to release soon?
  2. Another updated build was posted today fixing some reported issues.
  3. A new build was posted that fixes the issues posted in this thread. This will be the last build before we release this officially so please try it asap.
  4. @Herve Maratrey it seems like you are running a really old laptop with a very old BIOS from 2011. It is very underpowered by todays standards and only has 4GB of RAM. At least for the graphics and memory - the CPU is a quad core which should be fine. What is the PC model? BIOS: BIOS Date: 08/10/11 12:28:49 Ver: 04.06.03 (type: BIOS) Processor: Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz (8 CPUs), ~2.2GHz Memory: 4096MB RAM Available OS Memory: 4002MB RAM Page File: 4818MB used, 3534MB available Windows Dir: C:\WINDOWS DirectX Version: DirectX 12 There are no obvious errors in the log but my guess is our code is incompatible with this version in some way. User DPI Setting: 120 DPI (125 percent) System DPI Setting: 120 DPI (125 percent) Can you temporarily change your DPI scaling in windows back to 100% and retry to rule out a scaling problem?
  5. No it doesn't. Once imported the data is lost since the file is transcoded. You will need to redo the data if you reexport.
  6. @steven galutia Can you provide some more information such as a video or screenshots of the problem you are seeing? Also which version of CbB were you using prior to updating. There are no changes in this version that should impact this so there may be some other factors leading to your issue.
  7. The articulations are actually stored in a clip. We'll evaluate of it can be excluded from selection.
  8. Well the articulation is data on the track so this is not that surprising I think? The same happens with envelope data.
  9. Thanks for reporting it. I can reproduce it and well fix it for the main release.
  10. @Andres Medina All three of your dump files are the exact same crash in Vienna Synchron player. Its not related to our release. You should contact Vienna since only they can solve this issue. I will also forward the dump files to them. Your stacks do not show that you are trying to save templates. When do the crashes occur - after the save? You may need to send them the project you are using to reproduce the crash as well since often the dumps are not sufficient. Unhandled exception at 0x00007FFE8B04007B (Vienna Synchron Player.vst3) in Test Articulation Maps Strings ref5_11212020_154833.dmp: 0xC0000005: Access violation reading location 0x00000000D5936058. Vienna Synchron Player.vst3!00007ffe8b04007b() Unknown Non-user code. Cannot find or open the PDB file. Vienna Synchron Player.vst3!00007ffe8aff8803() Unknown Non-user code. Cannot find or open the PDB file. user32.dll!UserCallWinProcCheckWow() Unknown Non-user code. Symbols loaded. user32.dll!CallWindowProcW() Unknown Non-user code. Symbols loaded. > mfc140u.dll!_AfxActivationWndProc(HWND__ * hWnd=0x0000000000200968, unsigned int nMsg=1024, unsigned __int64 wParam=0, __int64 lParam=0) Line 478 C++ Symbols loaded.
  11. Read the release notes. Rollback instructions are there. Which version were you using earlier? We don't have any uad systems to test on. Before rolling back make sure you try the latest 2020.11 release that we posted on Friday.
  12. I'll send you a link later. The rollback will take you to the previous major update. I don't the original .11 release will make any difference since i think the crashes are in synchron.
  13. The symptoms sounds exactly like the bug I fixed that's why I wanted you too retest with the new build.
  14. Not seeing any crash here. It may be related to your video drivers. Can you send a link of any loop you used just to verify that its not content related?
×
×
  • Create New...