Soundcraft ui 24 recording

[talby]

Am I understanding correctly that you are using the identical Waveform installation on a laptop, and at one location connecting it to the PreSonus device and at the other location to the Soundcraft device?

Indeed, strange!

Could you also provide the described 3 screenshots taken for the Personus and for the Soundcraft devices in use? Important would be to have the Input section left of a track selected and the Controls Panel open, to see the details of the input during recording. In the video a whole track is selected. I doubt that I might find something wrong in there, but you never know...

[markkure]

Yes, I am using only one laptop. Signal is coming in like it should be but... Tomorrow I have a chance to take pictures . Yesterday I took Presonus with me and connected it to my laptop and everything was working nicely. Waveform of played instruments was there just like before. With Soundcraft, nothing. Tomorrow I try to take the pictures ,If I understood what you were asking. I live in Finland so english is not my native language.

[Watchful]

Your English is excellent. This sounds like an issue with the audio interface.

[markkure]

Just a quick note, we recorded drums and bass using Soundcrafts multitrack to USB stick and no problems. They are opening fine in Freewave 13. So it seems that the problem really is Soundcrafts audio interface. But the search continues.

[talby]

Well, your video shows clearly that Waveform received audio signals on the various armed tracks. The recorded signal appeared so clearly on the graphical level meters that I imagined the tracks recording various mics at drums before I got a chance to also listen to the video besides only watching the film. This lets conclude that your audio-interface works properly up to this point.

The question is indeed the one you initially asked us: Why are the recorded clips discarded by Waveform?

I see in your video at the end of second 19, that the playhead jumps back to the position where it was located when the recording started. This, and the fact that the recorded clips have become discarded, looks like the record ABORT behavior, but you didn't have your mouse over the ABORT button. And you said, this only happens with the Soundcraft device connected, but not with your PreSonus device connected.
May it be that your Soundcraft device for what reason ever shows up as a Control Surface (SETTINGS - Control Surfaces)? If this would happen, then maybe the Control Surface configuration overwrites the record STOP button with the ABORT function? I could not explain how and if this could happen, but that's currently the last idea I have.

Following this idea, in your video the mouse is not moved, and I assume that you cannot click with it without also moving it slightly. Therefore I assume that you start and stop the recording by a keyboard shortcut. If so, under SETTINGS - Keyboard Shortcuts, for sure the key stroke you used for stopping the recording shall not be configured to trigger "Abort recording, discard takes".

Let's confirm it:
Searching with term "abort" in the left top field (SETTINGS - Keyboard Shortcuts), by default there should only appear configured for "Abort recording, discard takes" the shortcut key "F4", and under macros (activate at the bottom "show macro editor") should only be written the one line entry "Tracktion.stopRecordingAndDiscard();".
For no other entry appearing by search terms "stop" or "record" this "Tracktion.stopRecordingAndDiscard();" text should appear in the macro editor. Otherwise something became misconfigured.

Again, I could not explain how and if at all a keyboard shortcut configuration could be changed by connecting an audio-interface. Here the experts from the Tracktion support will need to chime in.

When taking the already described 3 screenshots, please add to them the screenshots showing the full list of Control Surfaces, and the "abort", "stop" and "record" keyboard shortcut pages with the macro editor open.

You may want to sent also to the Tracktion support team the link to the video and the screenshots on your cloud drive, and maybe also the link to this thread here.

[markkure]

When it came back to start I pushed spacebar, nothing else. I also looked shortcuts and there is everything like you described. I will take pictures and put those together with the video. Spacebar should only stop and play,not take recording back to beginning.

[pough]

I would watch the video if it didn't require me to request access.

You did check to see if the input's Trigger Level is -INF, right?

[markkure]

I would watch the video if it didn't require me to request access.

You did check to see if the input's Trigger Level is -INF, right?

Yes,it is - INF. Everything is like they are supposed to be. That's why this is so strange.

[talby]

I pushed spacebar, nothing else. I also looked shortcuts and there is everything like you described.

The follow-up question is obviously : what happens if you click with the mouse on the STOP RECORDING button, instead of using a keyboard shortcut?

[markkure]

Yep, that will be my next move. Today I didn't have time to do anything but I will try tomorrow.

[markkure]

I tried stopping recording from the stop button, it didn't help. I took some pictures and made a folder in my Drive. https://drive.google.com/drive/folders/ ... vl5SZjbC32

[markkure]

I tried another software and recording was successfull. So problem seems to be with Freewave 13 . Tracktion support said that because I am using free version they are not able to help me. Should I downgrade 13 because it used to work?

[talby]

To my knowledge, at least for the Linux versions of WF, you can have different major versions installed in parallel (WF12.x alongside WF13.x, only subversions cannot be installed in parallel, so 12.0 can not stay installed in parallel to 12.5).

[Watchful]

That's correct on the Windows side, but be advised--if you've opened a project in 13, it cannot be opened in 12 again without editing the XML in the project files.

[talby]

Oh, that is a very important advise! Special Thanks for this!