*Keeping it real, I had a 101 way back in the day and I hated it at the time. Sold it to get a Quasimidi Rave-o-lution. So my tastes are clearly questionable.
)
One Synth Challenge #188: Six-Traq by Full Bucket Music (Taron Won!)
-
- KVRist
- 109 posts since 11 Sep, 2022
I guess it's a matter of taste*. I'd wager that we're going to get some fantastic sounding tracks this month, though.
*Keeping it real, I had a 101 way back in the day and I hated it at the time. Sold it to get a Quasimidi Rave-o-lution. So my tastes are clearly questionable. )
*Keeping it real, I had a 101 way back in the day and I hated it at the time. Sold it to get a Quasimidi Rave-o-lution. So my tastes are clearly questionable.
)-
- KVRAF
- 3204 posts since 17 Apr, 2010 from Slovenia
AHammm....it may be one of the rather buggiest FullBucket babies... so to say: A FullBugged? 
At least on MacOS it really has issues.
From within Cubase it can just crash when trying to save a preset, for example. But only now and then.
Oh, and it wouldn't save (or reload) MIDI LEARNS.... very forgetful this one.
In MuLab I've loaded up an instance and somehow a few of the note slots wouldn't play notes. Unisono then would hide that issue, but going back to single brings back the problem.
I sincerely and dearly dislike the envelopes. Probably is an authentic issue with the inspiration synth, but dang, it's bad.
It's probably the least "practical" synth in the line-up of many true super-gems from Björn and definitely the least inspiring to play with. But that really does make it a pretty big challenge, hehehe. Possibly some creative EQing. But the little bugs are puzzling and I'm sure there are more. I can feel it!
Woops, and a nasty, nasty crash in MuLab while adjusting Filter Envelope Decay during playback.
So, yeah, not sure if I'll get around to do something...
At least on MacOS it really has issues.
From within Cubase it can just crash when trying to save a preset, for example. But only now and then.
Oh, and it wouldn't save (or reload) MIDI LEARNS.... very forgetful this one.
In MuLab I've loaded up an instance and somehow a few of the note slots wouldn't play notes. Unisono then would hide that issue, but going back to single brings back the problem.
I sincerely and dearly dislike the envelopes. Probably is an authentic issue with the inspiration synth, but dang, it's bad.
It's probably the least "practical" synth in the line-up of many true super-gems from Björn and definitely the least inspiring to play with. But that really does make it a pretty big challenge, hehehe. Possibly some creative EQing. But the little bugs are puzzling and I'm sure there are more. I can feel it!
Woops, and a nasty, nasty crash in MuLab while adjusting Filter Envelope Decay during playback.
So, yeah, not sure if I'll get around to do something...
-
- KVRian
- 804 posts since 14 Apr, 2019
-
- KVRAF
- 2481 posts since 22 Sep, 2016
Is there a real INIT preset?
-
- KVRian
- 954 posts since 25 May, 2010 from Hessisch Uganda, Germany
Hey Taron, just tell me what your system is (Intel, Silicon) etc. And maybe the "N" version works fine?
-
- KVRian
- 954 posts since 25 May, 2010 from Hessisch Uganda, Germany
To initialize a Program right click the PROGRAM button and read page 18 of the manual
There's also a short cut: Right click RECORD button and press the 0 button like on the original Six-Trak.
-
- KVRAF
- 3204 posts since 17 Apr, 2010 from Slovenia
Hey Björn, it's Silicon (M1). N version? I'll have a look tomorrow for sure!Full Bucket wrote: Wed Oct 02, 2024 6:48 pm Hey Taron, just tell me what your system is (Intel, Silicon) etc. And maybe the "N" version works fine?
By the way, when MuLab crashed last, it literally just got completely hung up, stuck. I had to Force Quit it.
The voice slot failure thing happened while it was playing and I changed the AMP env release parameter to 0. I imagine that this trapped a few of them somehow. I would consider a kind of "reset" function for any accumulating fields. Akin to a "panic" button, if you know what I mean.
-
- KVRian
- 735 posts since 31 Oct, 2019 from Wonderland
In addition to what Taron mentioned. At least in Bitwig, the changed presets are not saved in the DAW, mentioned from one of the OSCers. They are saved in Cakewalk, I checked it.
One more thing: after changing any factory preset, I switch to the next one, but my changes in the previous one are not reset. Synthesizers usually don't save unconfirmed changes. This has also been noticed in several.
I can't complain that the size of the GUI, even after saving the current one, returns to the minimum. Most likely this is my Windows 7 and I should use version N, it helped me out a few times, thanks for this foresight!
In general, I am delighted with the concept of superimposing 6 independent synthesizers in mixed mono-poly modes, and humbly accept the remaining limits as a tribute to the original synthesizer.
P.S. I recommend that no one attack Sultan Ifrit, his fire shield reflects 20% of the damage back!
One more thing: after changing any factory preset, I switch to the next one, but my changes in the previous one are not reset. Synthesizers usually don't save unconfirmed changes. This has also been noticed in several.
I can't complain that the size of the GUI, even after saving the current one, returns to the minimum. Most likely this is my Windows 7 and I should use version N, it helped me out a few times, thanks for this foresight!
In general, I am delighted with the concept of superimposing 6 independent synthesizers in mixed mono-poly modes, and humbly accept the remaining limits as a tribute to the original synthesizer.
P.S. I recommend that no one attack Sultan Ifrit, his fire shield reflects 20% of the damage back!
-
- KVRAF
- 2481 posts since 22 Sep, 2016
Attention: STATE SAVING IN BITWIG seems BROKEN.
After reloading my session from yesterday, 4 hours work,100% patches gone and instances reset to "percussive organ". Omg, I'm really "happy". I have saved only 3 of 10 or so patches along the way...
Immediately lost motiviation. Sorry. Not here to beta test.
--
Updated: Removed 1st preview ...
After reloading my session from yesterday, 4 hours work,100% patches gone and instances reset to "percussive organ". Omg, I'm really "happy". I have saved only 3 of 10 or so patches along the way...
Immediately lost motiviation. Sorry. Not here to beta test.
--
Updated: Removed 1st preview ...
Last edited by ] Peter:H [ on Fri Oct 04, 2024 2:20 pm, edited 1 time in total.
-
- KVRian
- 954 posts since 25 May, 2010 from Hessisch Uganda, Germany
It is important to know which version of Bitwig because there was such a bug with CLAP in older versions...
-
- KVRAF
- 2481 posts since 22 Sep, 2016
Bitwig 5.2.4 on Windows 11.Full Bucket wrote: Thu Oct 03, 2024 8:07 am It is important to know which version of Bitwig because there was such a bug with CLAP in older versions...
SixTraq 1.0.2, Clap
-
- KVRist
- 136 posts since 11 Nov, 2012
Hi everyone,
@Full Bucket : It happens when i browse programs. Not every program but many of them.
the DAW crashes and closes
Win10 + Reaper 7,22 (vst3 version of SixTraq)
Bye!!!
@Full Bucket : It happens when i browse programs. Not every program but many of them.
the DAW crashes and closes
Win10 + Reaper 7,22 (vst3 version of SixTraq)
Bye!!!
You do not have the required permissions to view the files attached to this post.
-
- KVRist
- 109 posts since 11 Sep, 2022
I also was… surprised… when I opened my Bitwig project to find all of settings unsaved. Latest Bitwig on Windows 10 with CLAP plugin.
Thankfully, decades of getting screwed by Microsoft Office crashes has made me a “save everything always” paranoid so I had saved my presets AND the bank using the plugin interface. It’s still annoying having to reload the bank in every plugin instance when reopening the project though.
I’ll try the VST3 version tonight to see if that’s a workaround.
Thankfully, decades of getting screwed by Microsoft Office crashes has made me a “save everything always” paranoid so I had saved my presets AND the bank using the plugin interface. It’s still annoying having to reload the bank in every plugin instance when reopening the project though.
I’ll try the VST3 version tonight to see if that’s a workaround.
-
- KVRian
- 954 posts since 25 May, 2010 from Hessisch Uganda, Germany
Hi folks,
I'll try to tackle all your issues; not sure if can get MuLab on Mac right, though. My time & resources are limited to handle each system/host combination.
I assume that the Meta Parameters of Six-Traq are confusing some hosts. And there are a lot of them: For example, each Program Number of a track is a Meta Parameter which, when changed, causes other parameters to change as well. Audio Units requires them to be explicitly denoted in the declaration section or else hosts like Logic wouldn't even let the plugin pass validation.
. And it depends on the "level" on which you operate: When switching between Presets, the plugin state is maintained (this is what at least all my plugins do and what I want them to do). When changing Programs within a Preset, you will be asked whether you want to commit your changes (if there are any and as long as you haven't disabled this option in the Options Menu). On the original Six-Trak, your changes would have silently gone (which I find pretty annoying).
Cheers, Björn
I'll try to tackle all your issues; not sure if can get MuLab on Mac right, though. My time & resources are limited to handle each system/host combination.
I assume that the Meta Parameters of Six-Traq are confusing some hosts. And there are a lot of them: For example, each Program Number of a track is a Meta Parameter which, when changed, causes other parameters to change as well. Audio Units requires them to be explicitly denoted in the declaration section or else hosts like Logic wouldn't even let the plugin pass validation.
Yeah, hosts are obviously doing things in a different way... It would help me enormously if you could send me your Bitwig, MuLab or whatever projects that fail to load! And please provide some context on what you where doing.IV! wrote: Thu Oct 03, 2024 12:06 am At least in Bitwig, the changed presets are not saved in the DAW, mentioned from one of the OSCers. They are saved in Cakewalk, I checked it.
I respectfully disagreeOne more thing: after changing any factory preset, I switch to the next one, but my changes in the previous one are not reset. Synthesizers usually don't save unconfirmed changes. This has also been noticed in several.
. And it depends on the "level" on which you operate: When switching between Presets, the plugin state is maintained (this is what at least all my plugins do and what I want them to do). When changing Programs within a Preset, you will be asked whether you want to commit your changes (if there are any and as long as you haven't disabled this option in the Options Menu). On the original Six-Trak, your changes would have silently gone (which I find pretty annoying).Cheers, Björn
-
- KVRAF
- 2481 posts since 22 Sep, 2016
Bitwig 5.2.4, SixTraq 1.0.2 CLAP.
I have tried to prepare a project from scratch for demonstration as Björn has aked for ... and now it gets ridiculous.
Bouncing changes preset
1. Added SixTraq to new Bitwig track
2. Menu > Init
3. Changed some settings of the patch to make sure the difference is clearly audible, one was open cutoff fully.
4. Bounced a short sequence of the changed patch to collect the changed sound as evidence.
5. But the bounce audio was again "Percussive Organe" original AND the patch of the synth was actually really reset by the bounce operation.
-
Duplication Track does reset the patch on the Copy
1. Added SixTraq to new Bitwig track
2. Menu > Init
3. Changed some settings to make sure the difference is clearly audible.
4. Did a "duplicate track" to get a copy of the initially changed track
5. Duplicate is reset to "Percussive Organ"
-
Summary: It does not even involve saving and reopening a project. State Saving seems to be broken completely.
-
I actually vote to change the synth for october in order to give the time to fix the bugs. Björn state above he needs time to look into all the DAWs and test it thoroughly.
And then let's have SixTraq in November.
What do you think?
I have tried to prepare a project from scratch for demonstration as Björn has aked for ... and now it gets ridiculous.
Bouncing changes preset
1. Added SixTraq to new Bitwig track
2. Menu > Init
3. Changed some settings of the patch to make sure the difference is clearly audible, one was open cutoff fully.
4. Bounced a short sequence of the changed patch to collect the changed sound as evidence.
5. But the bounce audio was again "Percussive Organe" original AND the patch of the synth was actually really reset by the bounce operation.
-
Duplication Track does reset the patch on the Copy
1. Added SixTraq to new Bitwig track
2. Menu > Init
3. Changed some settings to make sure the difference is clearly audible.
4. Did a "duplicate track" to get a copy of the initially changed track
5. Duplicate is reset to "Percussive Organ"
-
Summary: It does not even involve saving and reopening a project. State Saving seems to be broken completely.
-
I actually vote to change the synth for october in order to give the time to fix the bugs. Björn state above he needs time to look into all the DAWs and test it thoroughly.
And then let's have SixTraq in November.
What do you think?