Ok,thanks. What does this mean? I am not very good with these kind of things.Watchful wrote: Fri Sep 27, 2024 5:29 pm 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.
Soundcraft ui 24 recording
-
- KVRer
- Topic Starter
- 25 posts since 17 Jul, 2023
-
- KVRist
- 374 posts since 18 Nov, 2023
If you created a project in WF12, and then open it in WF13, then WF13 changes something on the saved project file, and this change is not compatible to WF12. If you try to open the project again in WF12, then WF 12 will claim that the project cannot be opened.
What you could do: before you open a project in WF13, which you later on might want to open once more in WF12, then you first have to make a copy of the project BEFORE you touch it with WF13. Store this copy in a directory, where WF13 is not working with. Now, opening the project with WF13 will change it. After you have closed WF13 and want to use WF12 again, this time move the project touched by WF13 to a safe storage directory, then put the WF12 project version back in place, and now WF12 can work with it again.
Or, what else you could do, after Watchful placed a hint to it, you could manually enter the file which saves important configuration data about the project and manually reverse the changes which WF13 did to it. For doing this, you will have to use some Text-Editor, not any Waveform app.
So, you could learn how to manually enter and edit such configuration file with an Test-Editor. Then you could with WF13 even change things in the music stored in the project, after having closed WF13 apply the necessary correction in the configuration file to make it WF12 compatible again, and then opening this project in WF12 should show you also there the new music things.
As I by myself did not investigate by now what has to be reversed in the project configuration file, I right now cannot help more with this.
What you could do: before you open a project in WF13, which you later on might want to open once more in WF12, then you first have to make a copy of the project BEFORE you touch it with WF13. Store this copy in a directory, where WF13 is not working with. Now, opening the project with WF13 will change it. After you have closed WF13 and want to use WF12 again, this time move the project touched by WF13 to a safe storage directory, then put the WF12 project version back in place, and now WF12 can work with it again.
Or, what else you could do, after Watchful placed a hint to it, you could manually enter the file which saves important configuration data about the project and manually reverse the changes which WF13 did to it. For doing this, you will have to use some Text-Editor, not any Waveform app.
So, you could learn how to manually enter and edit such configuration file with an Test-Editor. Then you could with WF13 even change things in the music stored in the project, after having closed WF13 apply the necessary correction in the configuration file to make it WF12 compatible again, and then opening this project in WF12 should show you also there the new music things.
As I by myself did not investigate by now what has to be reversed in the project configuration file, I right now cannot help more with this.
Classical guitar --> Line Audio CM4 @ SSL12 --> KDE-Plasma @ Debian-Linux --> Waveform PRO 13.5
-
- KVRist
- 374 posts since 18 Nov, 2023
I cannot see anything wrong here.markkure wrote: Fri Sep 27, 2024 11:42 am 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
I assume that you also checked the entries in "SETTINGS - Control Surfaces" and confirmed that no Soundcraft device would be listed there.
You said already that you used the identical Laptop with the identical Waveform installation for all tests, and that with other software the Soundcraft audio-interface works fine.
And you said already, that you checked in SETTINGS - Keyboard Shortcuts that no weird shortcut settings or macros appeared when the Soundcraft audio-device is connected and in use.
Do I assume correctly that you did not test all the time inside the same, failing project, but created a fresh project for testing the issue?
Classical guitar --> Line Audio CM4 @ SSL12 --> KDE-Plasma @ Debian-Linux --> Waveform PRO 13.5
-
- KVRer
- Topic Starter
- 25 posts since 17 Jul, 2023
I think that I used the same project all the time. It never crossed my mind that a new project should be opened. I just got stuck in that same thing. Well, something I must do. I want to thank you all for your patience and all your help. Like I said,I'm not very good with computers. It is getting very frustrating but I am not giving up. So if you have the patience to help me more I would be very grateful.
-
- KVRer
- Topic Starter
- 25 posts since 17 Jul, 2023
Settings- control surfaces. I believe I looked at that and I didn't see Soundcraft there. I just connected Presonus to my laptop and Presonus faderportV2 appeared. I have no chance to connect Soundcraft right now because I at home now. Should it appear when it is connected like with Presonus happened? If it doesn't appear,how can I fix it? I think we are on to something now.
-
- KVRist
- 374 posts since 18 Nov, 2023
"Presonus faderportV2" is not your Presonus audio-interface. You can search on the Presonus product pages and see, that the Faderport and your audio-interface are two different devices serving two different purposes. The Faderport is a device usually known as a MIDI Controller device. Waveform calls Control Surfaces the configuration entries which define how Waveform shall interact with a specific MIDI Controller.
We wish to see that the Soundcraft audio-interface does NOT become falsely recognized as a MIDI Controller, so that signals and data send from the Soundcraft audio-interface to Waveform could not trigger functions like the RECORD ABORT button in the DAW. No audio-interface shall have a Control Surface entry, only MIDI Controllers should have it. Confirming that for your audio-interface does not appear there an entry helps to exclude such weird misconfiguration as a possible cause.
Best would be if you could upload screenshots showing all entries in that Surface Control list. I would be much surprised if there would appear something which doesn't belong there. But, your issue is strange, so better to exclude even strange things.
When back at the Soundcraft device, make sure to create a new project and test for the issue in the newly created project, just to make sure that a maybe re-used project is not corrupted under the hood and causing the problem.
We wish to see that the Soundcraft audio-interface does NOT become falsely recognized as a MIDI Controller, so that signals and data send from the Soundcraft audio-interface to Waveform could not trigger functions like the RECORD ABORT button in the DAW. No audio-interface shall have a Control Surface entry, only MIDI Controllers should have it. Confirming that for your audio-interface does not appear there an entry helps to exclude such weird misconfiguration as a possible cause.
Best would be if you could upload screenshots showing all entries in that Surface Control list. I would be much surprised if there would appear something which doesn't belong there. But, your issue is strange, so better to exclude even strange things.
When back at the Soundcraft device, make sure to create a new project and test for the issue in the newly created project, just to make sure that a maybe re-used project is not corrupted under the hood and causing the problem.
Classical guitar --> Line Audio CM4 @ SSL12 --> KDE-Plasma @ Debian-Linux --> Waveform PRO 13.5
-
- KVRist
- 374 posts since 18 Nov, 2023
The next step for investigating the issue could be to inspect all Waveform configuration files. But this could disclose information which you might not want to share. Also, it would be a laborious and tedious work. Additionally, I am myself not working with Microsoft Windows and couldn't guide you quickly to the location of the configuration files in question. Taking all this into account, my usual recommendation for users with good computer system knowledge and data maintenance experience would now be to not simply guide them to re-install the App, but to remove it completely, including all its configuration files stored for the user.
This requires that you have good experience with searching for configuration file directories, making backups, and maybe recovering configuration data and projects from the backups - unless you would be very sure that you wouldn't mind if all your Tracktion Waveform installation including all your personal Waveform configurations become lost.
So, the idea is, start from scratch and make sure that no old Waveform configuration files would still stay in place from a former installation. I believe that deleting the old configuration files before re-installing the App would resolve the problem, although we would never learn how it was caused.
It will be worth to learn how to maintain your computer system by applying such steps, if needed. Just make sure, if you are not experienced by now, that some more computer savvy person helps you with this, if you do not want to loose your old Waveform works.
This requires that you have good experience with searching for configuration file directories, making backups, and maybe recovering configuration data and projects from the backups - unless you would be very sure that you wouldn't mind if all your Tracktion Waveform installation including all your personal Waveform configurations become lost.
So, the idea is, start from scratch and make sure that no old Waveform configuration files would still stay in place from a former installation. I believe that deleting the old configuration files before re-installing the App would resolve the problem, although we would never learn how it was caused.
It will be worth to learn how to maintain your computer system by applying such steps, if needed. Just make sure, if you are not experienced by now, that some more computer savvy person helps you with this, if you do not want to loose your old Waveform works.
Classical guitar --> Line Audio CM4 @ SSL12 --> KDE-Plasma @ Debian-Linux --> Waveform PRO 13.5
-
- KVRer
- Topic Starter
- 25 posts since 17 Jul, 2023
Tracktion support told me that they couldn't help but I said that I was thinking of buying Pro version, but why should I because it is not working. Now they want to see all kind of pictures of settings and everything. A little bit of threat is always a good thing.
Lets see what they are thinking.
Lets see what they are thinking.-
- KVRist
- 374 posts since 18 Nov, 2023
What's about a re-install of Waveform, but assuring that all old configurations are moved away to a secure place before installing newly. Do you feel experienced to do this with some help?
Classical guitar --> Line Audio CM4 @ SSL12 --> KDE-Plasma @ Debian-Linux --> Waveform PRO 13.5
-
- KVRer
- Topic Starter
- 25 posts since 17 Jul, 2023
That could be possible. I would need good, clear instructions how to do that. I have external hard drive where I can store those old configurations,if that was what you meant.
-
- KVRist
- 374 posts since 18 Nov, 2023
Please check your PM (private messages) here in your forum account. I volunteer to help you, as far as I can. I am curious myself now to figure out what happened to or in your Waveform, and of course to get you up and running soon.
Classical guitar --> Line Audio CM4 @ SSL12 --> KDE-Plasma @ Debian-Linux --> Waveform PRO 13.5