D4 - Live recording with user drum kit and percussion map

Does anyone else have a problem when playing live with a user drum kit/percussion map. For me, Dorico says goodbye without comment as soon as I stop recording - even if I only record a single note. Manual input and playback, however, works without any problems!
greeting
Bertram

No crashes here. But while recording there is no sound and the result is a 16th note off (too early).

Ok - here are Dorico’s last words:
2022-01-18 09:29:57.193 [info] notifyPostCommandExecute: NoteInput.MIDINoteInput?MIDIPitches=72 (19 ms)
2022-01-18 09:29:57.599 [info] Posting command (requested): Play.Record Set=true, Post=true
2022-01-18 09:29:57.599 [info] Executing command: Play.Record?Set=true
2022-01-18 09:29:57.599 [info] ITransport::locate
2022-01-18 09:29:57.600 [info] addEventsForAudition() adding 1920 events to buffer #:0
2022-01-18 09:29:57.613 [info] processAuditionEvents() - processed 500 events
2022-01-18 09:29:57.644 [info] processAuditionEvents() - processed 500 events
2022-01-18 09:29:57.676 [info] processAuditionEvents() - processed 500 events
2022-01-18 09:29:57.683 [info] addEventsForAudition() adding 29 events to buffer #:420
2022-01-18 09:29:57.683 [info] AdlerAudioEngineImpl::startPlayback - wait for queue
2022-01-18 09:29:57.683 [info] AdlerAudioEngineImpl::startPlayback - queue finished
2022-01-18 09:29:57.699 [info] notifyPostCommandExecute: Play.Record?Set=true (100 ms)
2022-01-18 09:29:57.708 [info] ITransport::stop
2022-01-18 09:29:57.708 [info] ITransport::locate
2022-01-18 09:29:57.708 [info] ITransport::start
2022-01-18 09:30:03.385 [info] Posting command (requested): Play.Stop Post=true
2022-01-18 09:30:03.385 [info] Executing command: Play.Stop
2022-01-18 09:30:03.415 [info] addEventsForAudition() adding 1920 events to buffer #:0
2022-01-18 09:30:03.462 [info] processAuditionEvents() - processed 500 events
2022-01-18 09:30:03.462 [info] ITransport::stop
2022-01-18 09:30:03.496 [info] processAuditionEvents() - processed 500 events
2022-01-18 09:30:03.501 [info] Posting command (force): Edit.PasteFileAtPosition InstrumentIDArray=47, Position=0, 1, PunchInPosition=8, 1, LayoutID=0, FlowID=0, File=C:/Users/Mir/AppData/Local/Temp/Dorico 4/MIDI captures/capture 0030.mid, RecordOverwriteBehaviour=kOverwrite, Post=true
2022-01-18 09:30:03.501 [info] Posting command (force): NoteInput.DrumPadRecording BlobID=33, FlowID=0, Post=true
2022-01-18 09:30:03.522 [info] notifyPostCommandExecute: Play.Stop (137 ms)
2022-01-18 09:30:03.522 [info] Executing command: Edit.PasteFileAtPosition?InstrumentIDArray=47&Position=0, 1&PunchInPosition=8, 1&LayoutID=0&FlowID=0&File=C:/Users/Mir/AppData/Local/Temp/Dorico 4/MIDI captures/capture 0030.mid&RecordOverwriteBehaviour=kOverwrite
2022-01-18 09:30:03.525 [info] processAuditionEvents() - processed 420 events

and this is what VSTAudioEngine said at the time - maybe this will help::

2022-01-18 09:29:43 : addLink Send 38927 => 36 (idx 0)
2022-01-18 09:29:43 : endEdit [mixer]
2022-01-18 09:29:43 : beginEdit [mixer]: load-instrument-with-state-file-and-sends
2022-01-18 09:29:43 : endEdit [mixer]
2022-01-18 09:29:57 : setTransportRunning: Start at project time: 23.428568, system time: 518438.095000
2022-01-18 09:29:59 : License Info: ping response received: from silk service
2022-01-18 09:29:59 : License Info: ping response received: from silk service
2022-01-18 09:30:03 : setTransportRunning: Stop
2022-01-18 09:30:16 : License Info: ping response received: from silk service
2022-01-18 09:30:44 : License Info: ping response received: from silk service
2022-01-18 09:30:45 : License Info: ping response received: from silk service
2022-01-18 09:31:02 : License Info: ping response received: from silk service
2022-01-18 09:31:17 : enumerateDevices
2022-01-18 09:31:17 : =>Blackmagic Audio;Blackmagic Audio
2022-01-18 09:31:17 : =>Generic Low Latency ASIO Driver;Generic Low Latency ASIO Driver
2022-01-18 09:31:17 : =>Yamaha Steinberg USB ASIO;Yamaha Steinberg USB ASIO
2022-01-18 09:31:17 : getSupportedSampleRates
2022-01-18 09:31:17 : => 44100.000000
2022-01-18 09:31:17 : => 48000.000000
2022-01-18 09:31:17 : => 88200.000000
2022-01-18 09:31:17 : => 96000.000000
2022-01-18 09:31:17 : enumerateCurrentOutputIds: 2
2022-01-18 09:31:17 : =>UR22 Output 1/L
2022-01-18 09:31:17 : =>UR22 Output 2/R
2022-01-18 09:31:17 : getCurrentDevice: Yamaha Steinberg USB ASIO (samplerate 44100.000000) (blockSize 512)
2022-01-18 09:31:17 : enumeratePlugins: 34
2022-01-18 09:31:17 : enumerateInstruments: 19
2022-01-18 09:31:17 : enumerateEventInputIds: 1
2022-01-18 09:31:17 : =>I|Windows MIDI|Steinberg UR22-1;Steinberg UR22-1
2022-01-18 09:31:17 : enumerateEventOutputIds: 2
2022-01-18 09:31:17 : =>O|Windows MIDI|Microsoft GS Wavetable Synth;Microsoft GS Wavetable Synth

Bertram, can you please do Help > Create Diagnostic Report and attach the resulting zip file here? If it’s too big, please send it to me via e.g. WeTransfer or similar to my email address, d dot spreadbury at steinberg dot de.

Hello Daniel, thanks for the offer. But it contradicts me internally to send a considerable amount of logs / logged data on the net. If one or the other file can help, I’ll be happy to put it here as an attachment - no problem.

Live recording with my LA percussion map works in Dorico 3.5 with no visible problems. But doing the same with the same project in 4.0, Dorico crashes as soon as I stop recording, even if it was just a single recorded hit. (the VST audio engine keeps running)

For me personally, however, this is not an urgent problem.

greeting
Bertram

Fair enough if you don’t want to post the logs here on the forum, but you should please send them to me by email: although there is a chance that somebody else may eventually report the same problem and be happy to send us the logs then, without the logs or a set of steps that reproduce the problem, we can’t practically fix it. You can rest assured that we do not use any material you send us for any purpose other than diagnosing the problem, and we delete the data after we’re finished with it.

I really don’t want to start a discussion of principles here - but unfortunately it’s not just about logs or crash dumps, the automatically created zip file contains much more.

Then how about you generate the diagnostic report, look inside the generated zip file, extract the crash dumps, zip them up, and send them to me? It’s not as useful to us as having the application logs as well, because the application logs also allow us to perform a certain amount of correlation between the steps you took immediately before the crash and the stack trace of the crash, but having the crash logs is a lot more useful than not having them.

I think it’s great that you’re addressing this. Yes, I’m happy to post the dumps and the relevant log file section here.
This evening.
Thank you.

(By the way, I posted the relevant log lines from Dorico and the VST audio engine above)

The goodbye problem when importing live with a user drum map/kit that uses different aticulations has disappeared with the update to 4.0.1.

Special thanks also to Daniel for your exceptional support!

I’m glad to hear the problem is resolved as expected in the 4.0.10 update. Thanks for closing the loop!

Hallo!

Unfortunately, the ‘live’ import in a 5-line notation now only works with the 2 internal Dorico drum sets. When importing a user drum set, Dorico no longer crashes, but the tones that sound correct when playing are not set in notes - the 5 lines remain empty.
Also noteworthy: the ‘original’ Dorico drumsets exported and re-imported then behave just as sadly as user sets in this respect.


Das ‘live’ Einspielen in einer 5-zeiligen Notation funktioniert jetzt leider nur mit den Dorico internen 2 Drumsets. Beim Einspielen eines Anwender-Drumsets crasht Dorico nunmehr zwar nicht mehr, aber die beim Spielen richtig klingenden Töne werden nicht in Noten gesetzt - die 5 Zeilen bleiben leer.
Bemerkenswert ist auch: die ‘orginal’ Dorico drumsets exportiert und wieder importiert verhalten sich dann in dieser Hinsicht genau so traurig wie Anwender Sets.

Just wondering… Do those other drum sets have a proper percussion map set up in Dorico? I wouldn’t understand any specific treatment to the included ones, apart from the fact that the percussion map does come included too…

In the project with an internal Dorico drummer (Halion and Yamaha xmap), importing works with my piano good, as well as manual input. (However, it is only correctly mapped into the staves once the input has been activated with [Enter].)
But if I test the drum kit in the ‘Edit kit dialog’ export and re-import in a new project for a new empty player, then the piano recording does not produce any visible notes - at least for me - just like with my self-made kits.


Im Projekt mit einem internen Dorico-Drummer (Halion and Yamaha xmap) funktioniert das Einspielen mit meinem Piano gut, ebenso die manuelle Eingabe. (Allerdings wird erst richtig in die Notenzeilen gemappt, sobald einmal mit [Enter] die Eingabe aktiviert wurde.)
Wenn ich nun aber testweise das Drumkit im 'Kit-bearbeiten-Dialog" exportiere und in einem neuen Projekt für einen neuen leeren Spieler re-importiere, so erzeugt anschließend die Piano-Aufnahme keine sichtbaren Noten - bei mir jedenfalls - wie halt auch mit meinen selbstgebauten Kits.

Ok. But in this new project where it doesn’t work, is there the correct percussion map attributed to the instrument in Play mode. Excuse-me if I seem stubborn about it, but I feel the answer is there…

Yes, the player also gets the Yamaha XMap with the kit.
As I said, the manual input and playback works well.


Ja, der Spieler bekommt mit dem Kit auch die Yamaha-XMap.
Wie gesagt, die manuelle Eingabe und Wiedergabe funktionieren ja gut.

I’ve spent some time looking into this problem today and can confirm that indeed real-time recording into user-defined or imported percussion kits doesn’t work as expected. Unfortunately this is too late for us to include a fix in our next update, which is imminent, but I’ll make sure this gets addressed for our next update.

1 Like

Unfortunately, when I try again, I find that Dorico’s behavior when recording drums with an imported drum kit hasn’t improved in 4.031 either. When the recording ends, no notes appear and Dorico usually says goodbye after 1-2 seconds of thinking without comment. (see release notes Dorico 4.03)

This is easy to understand by exporting the internal simple drum kit and importing it again unchanged!

It is not an urgent problem for me …

greeting
Bertram


Leider stelle ich bei einem erneuten Versuch fest, dass sich das Verhalten von Dorico bei der Schlagzeug-Aufnahme mit einem importierten Drumkit auch in 4.031 nicht verbessert hat. Nach Beenden der Aufnahme erscheinen keine Noten und meistens verabschiedet sich Dorico nach 1-2 Sekunden Bedenkzeit kommentarlos. (siehe Versionshinweise Dorico 4.03)

Einfach nachzuvollziehen ist dies, indem man das interne einfache Schlagzeugkit exportiert und unverändert wieder importiert!

Es ist für mich kein dringendes Problem …

Gruß
Bertram

This problem is certainly fixed in Dorico 4.0.30/31. Can you please provide a set of diagnostics so we can examine the crash log to see what’s happening?

Dorico 4.03 - 4.031 / Windows 10

  1. Insert an empty project

  2. with a drummer (simple drumset).

  3. Export the drum kit.

  4. Take the drummer his drum kit and

  5. import for him the previously exported drum set.

  6. Record one/two of his punches and end the recording with the spacebar…


Dorico 4.03 - 4.031 / Windows 10

  1. Legen Sie ein leeres Projekt

  2. mit einem Schlagzeugspieler (simple drumset) an.

  3. Exportieren Sie das Drumkit.

  4. Nehmen Sie dem Schlagzeuger sein Schlagzeug und

  5. importieren Sie für ihn das zuvor exportierte Schlagzeugset.

  6. Nehmen Sie ein/zwei seiner Schläge auf und beenden Sie die Aufnahme mit der Leertaste …