Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Tempo Mapping = fatal crash (MB32c v8.0.17)
#1
I set what I thought was a fairly simple (albeit artistic!) tempo meter change. Not only did MB32c crash but the file won't even open, i.e. the crash is immediate.

Does anyone know if this is one of the bugs referred to as a 'known issue and it is being addressed' or is this something different (and new).

Is there a way to recover a file (from history/log/whatever) when MB doesn't even seem to attempt to open the current/last saved version?
[MB32C v9, Soundscape, 11th Gen i9 5GHz, 32GB, Win 11 Pro, 2TB+ M.2 SSD, Control|24, MCS-3800, Dante & MADI network]
Reply
#2
There are known tempo mapping issues with the release of v8. The factory are working hard to get an updated release.
If you have a corrupted session that you want to recover email support : mixbus@harrisonconsoles.com
Macmini 8,1 | OS X 13.6.3 | 3 GHz i5 32G | Scarlett 18i20 | Mixbus 10 | PT_2024.3.1 .....  Macmini 9,1 | OS X 14.4.1 | M1 2020 | Mixbus 10 | Resolve 18.6.5
Reply
#3
Thx @Dingo. I'll email support and see if any of my files & logs are useful to them.

If it may be useful to those who fall upon this thread...

I was testing the new v8 CUE editor - so there are no audio files beyond those in the bundled package.
There were only 4 channels using 2 cues (A & C). They were all grouped and all assigned to a VCA.
Only three FX were in any chain - ADA STD-1 Stereo Tapped Delay, Unfiltered Audio Bass MINT, Melda CharmVerb
The meter changes were from 4/4 to 5/4 for one bar and then back to 4/4.

I saved the project, input the first change, crash, recover, input second meter change 19 bars in, crash, never to recover...

The error in the crash log is (excerpt):

____________________________________________________________________

Mixbus32C.exe caused an Access Violation at location 0000000077D8A39F in module temporal-0.dll Reading from location FFFFFFFFFFFFFFFF.

AddrPC Params
0000000077D8A39F 0000000012E4F5C0 00007FFF985DC6AC 00000000121A3A80 temporal-0.dll!Temporal::TempoMap::bbt_walk
00000000754C6A28 0000000000000000 000000000015FF18 0000000004EE3B20 ardour-3.dll!ARDOUR::TriggerBox::fast_forward
000000007538BE48 0000000000000000 00000000176B3AE0 0000000012E4F710 ardour-3.dll!ARDOUR::Route::non_realtime_locate
0000000075460172 0000000000000000 00000000518650AD 0000000000000000 ardour-3.dll!ARDOUR::Session::non_realtime_locate
0000000075463F6D 0000000000000000 0000000012E4FBA0 0000000012E4F93C ardour-3.dll!ARDOUR::Session::butler_transport_work
0000000075134663 000000000BD1A6C0 000000000BD1A6C0 0000000000000000 ardour-3.dll!ARDOUR::Butler::thread_work
00000000751361BE 000000000EF3F0E0 0000000075136160 00004F6D0E1AD4EC ardour-3.dll!ARDOUR::Butler::_thread_work
0000000077EF5DC8 000000001236D478 0000000000000000 0000000000000000 pbd-4.dll!fake_thread_start
0000000051864A84 000000001236D440 0000000000000000 000000000D011DE0 libwinpthread-1.dll!pthread_create_wrapper [./build/x86_64-w64-mingw32-x86_64-w64-mingw32-librarieswinpthreads/./mingw-w64-libraries/winpthreads/src/thread.c @ 1499]
00007FFF985FDFB4 00007FFF98655500 000000000D011DE0 0000000000000000 msvcrt.dll!_beginthreadex
00007FFF985FE08C 0000000000000000 0000000000000000 0000000000000000 msvcrt.dll!_endthreadex
00007FFF982A54E0 0000000000000000 0000000000000000 0000000000000000 KERNEL32.DLL!BaseThreadInitThunk
00007FFF98DE485B 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!RtlUserThreadStart

...
_____________________________________________________________________________________
[MB32C v9, Soundscape, 11th Gen i9 5GHz, 32GB, Win 11 Pro, 2TB+ M.2 SSD, Control|24, MCS-3800, Dante & MADI network]
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)