Tracktion 7- Selecting MIDI In as input not an option
-
- KVRer
- 2 posts since 3 Aug, 2022
Some one please explain how to fix the issue I'm having the same one I go to my settings tabs where it displays my midi and everything is working but when I got to set my arturia keylab 49 essential to record with it it doesn't pop up as a input device I'm using the USB cord and my midi driver is installed but it doesn't have it as a option for a input
-
- KVRer
- 2 posts since 3 Aug, 2022
Can you explain to me how to reset the file so I can use my keylab it's driving me nuts my Instagram username is lost_boykaedo message me on there if you have it I'm bad about checking this site and it's a little bit of a pain in the a.. for mePeter Widdicombe wrote: Mon Jan 06, 2020 1:48 am Yeah, seems that Traction 4 folder and settings is a carryover from that release.
I have wished there were separate settings files, say tracktion32.settings and tracktion64.settings; or per release, as I use both 32/64 bit and have to keep playing with the scan lists for .VSTs.
-
Peter Widdicombe Peter Widdicombe https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=336849
- KVRian
- 1205 posts since 29 Aug, 2014
Are you sure the MIDI keyboard is live/connected BEFORE you start Waveform; and that the USB cable is "good"? I find that ANY minor interruption in the USB connection will lose the device in Waveform and the only solution (at least with Windows) is to completely shut down Waveform and restart Waveform (not Windows!) to get the USB device back.
The "refresh MIDI devices" in USB settings appears not to do anything - in any release.
The "refresh MIDI devices" in USB settings appears not to do anything - in any release.
Waveform 13; Win10 desktop/8 Gig; Win11 Laptop; MPK261; VFX+disfunctional ESQ-1
-
- KVRist
- 359 posts since 21 Jun, 2020
I did the same restart, but then I just began to Disable / Enable the "lost", "not working" device on the settings page, without restarting WF12.
-
- KVRian
- 502 posts since 3 Dec, 2021
I noticed in 12 Pro I can turn in my keyboard, simply go from edit tab to settings tab/midi devices, don't touch anything, then click back to the edit page and my keyboard is now visible. No idea when that changed but happy days.
-
- KVRAF
- 1601 posts since 9 Jan, 2018
Tracktion 7 was very irritating in this regard. Unplugging a USB cable, powering up hardware or shutting something off while T7 was running frequently locked up the DAW or caused it to crash hard.
My rule was: power up everything you thought you might be using in this session, wait until everything was 100% ready, and THEN start T7. When finished, exit fully out of T7, then start powering hardware down. Anything else caused no end of aggravation, including T7 refusing to recognize external devices.
Waveform 9 improved on this quite a bit, but even now in 12, it still can't recognize a new device in an open project without help. I either need to power up before opening the project or, if a project is open, go to the MIDI Devices page and make sure my device appears there. Only then will it show up as an input in the project.
That's a minor gripe, because it's way better than the intolerance of T7 to *any* change in MIDI device status.
My rule was: power up everything you thought you might be using in this session, wait until everything was 100% ready, and THEN start T7. When finished, exit fully out of T7, then start powering hardware down. Anything else caused no end of aggravation, including T7 refusing to recognize external devices.
Waveform 9 improved on this quite a bit, but even now in 12, it still can't recognize a new device in an open project without help. I either need to power up before opening the project or, if a project is open, go to the MIDI Devices page and make sure my device appears there. Only then will it show up as an input in the project.
That's a minor gripe, because it's way better than the intolerance of T7 to *any* change in MIDI device status.
Spotify, Apple Music, YouTube, and even Deezer, whatever the hell Deezer is.
More fun at Twitter @watchfulactual
More fun at Twitter @watchfulactual
-
GuitarPlayerinNYC GuitarPlayerinNYC https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=453621
- KVRist
- Topic Starter
- 207 posts since 23 Dec, 2019
I believe the answer is at the beginning of this thread. Peter Widdicombe provided the answer.
Using Explorer, certain things need to be deleted. On my phone now, sorry I can't provide more detail.
Using Explorer, certain things need to be deleted. On my phone now, sorry I can't provide more detail.
-
Peter Widdicombe Peter Widdicombe https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=336849
- KVRian
- 1205 posts since 29 Aug, 2014
Ah, that works ! Taking the device that was listed as active but non-responsive after a connection error, it was dead and I used to shut down and restart waveform. It appears the disable and reenable of the device on the MIDI settings page can "revive" it - at least as an input device.nowgad wrote: Sat Jan 07, 2023 3:22 pm I did the same restart, but then I just began to Disable / Enable the "lost", "not working" device on the settings page, without restarting WF12.
I'll have to try it with my controller keyboard to see if it revives - it's bigger and seems to occasionally exceed the USB limits on my laptop if mouse and headphones are ALSO plugged in !
(Or break down and buy a USB POWERED hub rather than passive
Waveform 13; Win10 desktop/8 Gig; Win11 Laptop; MPK261; VFX+disfunctional ESQ-1
