tja
Converser
Posts: 44
|
Post by tja on Aug 16, 2018 22:11:52 GMT
Going to sleep now, thanks already a big bunch for your efforts!!!
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Aug 16, 2018 22:15:39 GMT
OK, I am finished for tonight! :-)
I will take another look in the morning and pull in the .mid file
Thanks for your patience and testing. You might want to revert back the the last version that was working best for you until I make this work how it should - even with ChordFlow... (I do not give up easily, and I understand what is happening - I think)
Regards, Nic.
|
|
|
Post by Dchild on Aug 16, 2018 22:24:10 GMT
OK, I am finished for tonight! :-) I will take another look in the morning and pull in the .mid file Thanks for your patience and testing. You might want to revert back the the last version that was working best for you until I make this work how it should - even with ChordFlow... (I do not give up easily, and I understand what is happening - I think) Regards, Nic. Following the thread in anticipation π Thanks for all your hard work fellas.
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Aug 17, 2018 8:08:08 GMT
Morning tja , Sleeping on this helped and this morning I found I had a stupid bug in the reworked script. You'll notice in your last tests that all the tiny events were 100% consistent with the source notes - D'oh! Anyhow, here is v5 to try out. This one worked for me with the ChordFlow and MidiSteps sequences you uploaded, manually with a keyboard and my own internal tests. Famous last words, though. This new version lets you decide what to do with the source events using the K2 variable. Set this to 2 to hear only the bass notes. If you were to add a bigger delay (probably don't need to) then you can set K2 to 1 to match the incoming source events time-wise with the bass notes too. Or... try this: ASS K0 = 3 FA 0 and the generated bass notes will be delayed for 250ms - interesting effect! Regards, Nic. Attachments:Scene-autobass.mfr (3.13 KB)
|
|
|
Post by Dchild on Aug 17, 2018 8:27:35 GMT
Hey Nic
Will V5 work in both the MidiFire / StreamByter AU current versions or would I need the beta version.
You added me as a beta tester to StreamByter.
If I need MidiFire, happy to buy it to get access to the beta.
Thanks π
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Aug 17, 2018 8:36:15 GMT
All the latest versions (marked from v2.1 onwards) require MidiFire - they won't work in StreamByter AU at all because they use the inject flag to sequence the events in order to determine the lowest note accurately. The original version in this post will work in the latest StreamByter AU and *may* even work with the App Store version (I was waiting for someone to try it out!) - it does work well for manual playing but with sequenced events you may get tiny event 'artefacts' due to the order in which the sequenced notes are presented to the script. For the original version to work perfectly with no artefacts, the lowest note needs to be presented first. I have added you into MidiFire beta also; just install from TestFlight. Regards, Nic.
|
|
tja
Converser
Posts: 44
|
Post by tja on Aug 17, 2018 8:53:19 GMT
Hey Nic Will V5 work in both the MidiFire / StreamByter AU current versions or would I need the beta version. You added me as a beta tester to StreamByter. If I need MidiFire, happy to buy it to get access to the beta. Thanks π It works with the regular MidiFire. But only in the StreamByter beta. EDIT: Nic answered already much more correct :-)
|
|
tja
Converser
Posts: 44
|
Post by tja on Aug 17, 2018 9:02:07 GMT
Hello Nic, sadly, I need to say that the latest version shows the same artifacts for me, when using MIDIsteps.
I also tried to route the MIDI into the MidiFire modules or into a new MIDIsteps module instead, but this was the same. It did not yet test with StreamByter beta, but can later do so.
What I noticed, is that the StreamByter module flashed in red, this was not the case earlier.
Later, I will also retry with ChordFlow and also Xequence - so far, everything was OK only in Xequence.
If I shall do something specific, I'm at your command ;-)
As with "K0 = 3 1 0" it did not work, I also tried "3 9 0" and "3 2 2", but nothing changed.
About K2 at 0, this shall pass the source events? What does this mean? They are not delivered to channel 4....
My MIDI knowledge is quite low :-D
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Aug 17, 2018 9:11:39 GMT
Hi tja, That is indeed very sad! Now I am getting very confused. I was sure this was going to be correct as I understood what was happening and was able to pipe in your .mid files and everything worked as it should. Did I upload the wrong thing? Let me recheck by downloading what I uploaded and install that myself and get back to you. No need to test with the AUv3; v2.1 and on will not work with that in any case. ASS K0 = 3 1 2 - you should only hear the bass notes coming out of the module You should have seen the red flashing before in previous versions. This means that the module is blocking events (this is normal as I am blocking those internal sysex messages) Let me recheck everything and get back to you for what to do next. Regards, Nic.
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Aug 17, 2018 9:33:34 GMT
Hi tja , Can you confirm that in your MidiFire Scene that the Stream Byter is labelled as 'tja autobass v5' ? I just downloaded from here and got the correct version. The fact that you say ASS K0 = 3 2 2 doesn't change anything makes me wonder if it's v5 you are using. Just need to check the obvious. Regards, Nic.
|
|
tja
Converser
Posts: 44
|
Post by tja on Aug 17, 2018 9:46:55 GMT
Yes, v5
I still don't understand the passing... On channel 4, I only ever got the bass line.
|
|
tja
Converser
Posts: 44
|
Post by tja on Aug 17, 2018 9:48:20 GMT
I am going to try "3 FA 2"
|
|
tja
Converser
Posts: 44
|
Post by tja on Aug 17, 2018 9:54:48 GMT
I send MIDI from MIDIsteps to MIDIsteps Out, removed the MidiFire module and used a MIDIsteps module instead. In Cubasis, I hear to MIDIAsteps channel 1 and to Virtual MIDI channel 4. The delay of "FA" clearly works, as can be seen. Still not sure what the passing means. Attachments:
|
|
ki
MidiFire Beta
Posts: 25
|
Post by ki on Aug 17, 2018 9:57:03 GMT
nic Is the inject feature (or something simular to re-insert notes at a later time back into the script) planned for a future StreamByter AU version ?
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Aug 17, 2018 10:01:06 GMT
Hi tja, Thanks for confirmation. That's definitely v5! Let me look further into this. What I mean by passing is that the original notes from MidiSteps/ChordFlow pass through the autobass module and into Cubasis. If you ASS K0 = 3 1 2 then these original notes will be blocked by the module and not forwarded to Cubasis. Regards, Nic.
|
|