SOLVED: Issue with Collective
-
- KVRAF
- 1790 posts since 30 Dec, 2012
I'm not saying you should have it off all the time, just if you switch to another Edit and you don't want MIDI to go to a previous one.
I know this isn't the ideal solution, but there currently isn't the ideal in the app so this is a possible work around.
I know this isn't the ideal solution, but there currently isn't the ideal in the app so this is a possible work around.
-
- KVRAF
- 3735 posts since 17 Sep, 2016
Thanks for the explanation Dave! I think what @magicmusic was referring to is needing to use the audio engine while playback is stopped. I frequently use Waveform as a synth rack to play my virtual instruments live from my MIDI keyboard, without playback running. So that does require the audio engine to be active.dRowAudio wrote:
@zzz00m, this is also a good reason to disable "Run audio engine when stopped", pretty much the only reason really, to save CPU when the Edit isn't active.
Master solo/mute is one option but not really how the mix bus works, everything in an Edit is self-contained, even the previews are themselves tiny Edits so soloing between Edit's would be a bit of a break from this relationship.
I think adding something to either:
1) Avoid any active inputs when the Edit doesn't have focus
2) Disable (and automatically re-enable) "Run audio engine when stopped" when an Edit loses focus
Ideally, I'd like to add some Javascript handlers so you can run your own custom scripts when Edits gain/lose focus but I don't really have bandwidth for that any time soon.
I can say that this has been a pain when we've done trade shows in the past so expect it to be sorted in some form for NAMM next year
Your plan sounds good, and I look forward to it!
Windows 10 and too many plugins
-
- KVRAF
- Topic Starter
- 1605 posts since 9 Jan, 2018
I can help. Go to tracktion.com and click on Account...on the top menu in the upper right... then My Account to log in.
From there, click on My Downloadable Products on the left.
Scroll down to Collective, and look for the word BETA next to it. Click on that.
From there, click on My Downloadable Products on the left.
Scroll down to Collective, and look for the word BETA next to it. Click on that.
Spotify, Apple Music, YouTube, and even Deezer, whatever the hell Deezer is.
More fun at Twitter @watchfulactual
More fun at Twitter @watchfulactual
-
- KVRAF
- Topic Starter
- 1605 posts since 9 Jan, 2018
Dupe post
Last edited by Watchful on Wed Jul 04, 2018 4:48 am, edited 1 time in total.
Spotify, Apple Music, YouTube, and even Deezer, whatever the hell Deezer is.
More fun at Twitter @watchfulactual
More fun at Twitter @watchfulactual
-
- KVRAF
- Topic Starter
- 1605 posts since 9 Jan, 2018
Success!!!
My 13-year-old figured it out tonight.
First, thanks to all of you for your patience with me and many great ideas. Zzz00mm especially, for providing the clue.
I tried the FM-only sounds, and they worked. My 13-year-old then created a new sound with the sampled waveforms, and they worked. It occurred to him that the FM synth looks in a different place for those, which prompted him to check the Settings page. Sure enough, after the Waveform update, our Samples and Instrument paths were cleared out. Erased.
We pointed them to the default content locations and boom! All samples were back, and the house is filled with sounds from Collective once more.
Am using the latest Beta, with the filter fix, which is what I suspect caused some initial problems with Collective. Anyway, in between the latest Beta and zzz00mm's tip about the FM synth, it looks like all great news for us.
If folks want me to rename the thread title to Solved, I will, but sounds like there might be other people with unsolved issues, and I'm happy to leave this thread going as a catch-all for any Collective questions or concerns.
Thanks, again, everyone.
My 13-year-old figured it out tonight.
First, thanks to all of you for your patience with me and many great ideas. Zzz00mm especially, for providing the clue.
I tried the FM-only sounds, and they worked. My 13-year-old then created a new sound with the sampled waveforms, and they worked. It occurred to him that the FM synth looks in a different place for those, which prompted him to check the Settings page. Sure enough, after the Waveform update, our Samples and Instrument paths were cleared out. Erased.
We pointed them to the default content locations and boom! All samples were back, and the house is filled with sounds from Collective once more.
Am using the latest Beta, with the filter fix, which is what I suspect caused some initial problems with Collective. Anyway, in between the latest Beta and zzz00mm's tip about the FM synth, it looks like all great news for us.
If folks want me to rename the thread title to Solved, I will, but sounds like there might be other people with unsolved issues, and I'm happy to leave this thread going as a catch-all for any Collective questions or concerns.
Thanks, again, everyone.
Spotify, Apple Music, YouTube, and even Deezer, whatever the hell Deezer is.
More fun at Twitter @watchfulactual
More fun at Twitter @watchfulactual
-
- KVRAF
- 3735 posts since 17 Sep, 2016
Glad to hear you got it working again @Watchful! Collective is an powerful synth if you dig in! It shares a lot with the Biotek engine under the hood. You can mix your own samples with synth waveforms.Watchful wrote:Success!!!
My 13-year-old figured it out tonight.
First, thanks to all of you for your patience with me and many great ideas. Zzz00mm especially, for providing the clue.
I tried the FM-only sounds, and they worked. My 13-year-old then created a new sound with the sampled waveforms, and they worked. It occurred to him that the FM synth looks in a different place for those, which prompted him to check the Settings page. Sure enough, after the Waveform update, our Samples and Instrument paths were cleared out. Erased.
We pointed them to the default content locations and boom! All samples were back, and the house is filled with sounds from Collective once more.
Am using the latest Beta, with the filter fix, which is what I suspect caused some initial problems with Collective. Anyway, in between the latest Beta and zzz00mm's tip about the FM synth, it looks like all great news for us.
If folks want me to rename the thread title to Solved, I will, but sounds like there might be other people with unsolved issues, and I'm happy to leave this thread going as a catch-all for any Collective questions or concerns.
Thanks, again, everyone.
If you want to try your hand at sound design with user samples, you can also grab 1GB of free field recordings in WAV format at this sound designers site. They are excellent for creating your own soundscapes in Collective. The free sounds are available as individual downloads (via the SoundCloud link), but if you donate at least $5 to "Save the Children", he has made a downloadable zip bundle available, with a full license to use them in your works. http://www.luftrum.com/free-field-recordings/
Windows 10 and too many plugins
