TubiLeSax previous tests

[pHz]

ok guys - initial responses -

works fine in tracktion so far [will check in bidule and massiva later / tomorrow] - trying all the usual tricks to get plugs to crash arent affecting it as yet

but -

- as mentioned by matias the legato isnt always convincing especially when playing rapid short notes but since youve explained why william i dont see this as a big issue at the moment

- occasionally noticing some clicking / glitching in playback - will try to pin this down and reproduce it before mentioning it again

- could just be me but the 'air' parameter doesnt seem to do very much at all

- the gui

will post further after further play but at the moment - looking pretty good fellas !!!

slainte rob

[WilliamK]

Thanxs for the tests bud. About the Legato, Luigi and I were talking about it. He told me to considerer a crossfade like mentioned above. I did that code once, but the problem is that when crossfade is in 50% of the stage and you load a new waveform. Maybe a solution would be, as Luigi pointed, a poly-crossfade. Or, I tought, that I could build a LIST of waveform-changes and do the next only when the crossfade is DONE. It could introduce a lag of some samples when playing fast. But maybe it won't be noticable. Anyway, how many samples fits in a 64 bar in a 120bmp song?

I will try this out.

Regards, WilliamK

[pHz]

ooh - this is odd -

you know i mentioned that the 'air' slider was having little effect ???

well it seems this is tracktion specific - ive now tried tubilesax in bidule and massiva and in those 2 hosts i can clearly hear the effects of tweaking the 'air' level [the 'keys' click also seems to be louder in these 2 hosts too]

like i said - this is obviously a tracktion problem and im just about to let jules know [he might need a beta to test it though if thats ok] - but i mention it here as it MIGHT affect other hosts too

possible related [but i dont know] - when opening my tubilesax test project in tracktion i get the following message appear -

Code: Select all

The VST Plugin 'TubiLeSax' has caused an internal error - please report this bug to your plug-in manufacturer.

(context: dispatcher (24, 0, 38440, dfcc0a8, 0.000000))

this might have corrupted other data, and could make Tracktion unstable. Do you want to risk this and carry on running ? (click 'cancel' to quit immediately)

even though if a opt to carry on the plug works fine [apart from the air / keys thing] - this is an internal tracktion message but something is obviously not connecting properly between tubilesax and tracktion [coincedentally i get a similar message with the new version of daAlfa2k only with the details -

Code: Select all

(context: dispatcher (24, 0, 77032, 30310a8, 0.000000))

so is there a lot of common code between the 2 plugs ??? ]

like i said - ill let jules know too

slainte rob

[WilliamK]

Ohh, maybe is something on the code or the new compiler we are using. I have to check that. I will send you an URL for a test file ok?

Regards, WilliamK

[pHz]

sure - np

slainte rob

[WilliamK]

BTW: Good news. I found the perfect solution for the Legato problem. It will take me some time to properly implement it. But latter today I prob going to have it done for testing.

Best Regards, WilliamK

[pHz]

ok william - got it and tried it -

same thing - tracktion error message on loading project even though plugin works fine [apart from air / keys]

plus -

some new error messages about not loading tuning files ['error loading scale files' - '12-equal temperament'] and apparent problems with the samples ['error!' - 'cant load bank, wrong file size']

note - these only happen if loading a project file that already includes the plugin - adding a new instance to an existing project it loads fine [apart from the scale error - but i guess this is due to just copying the new .dll into the vst folder as opposed to the proper install]

[EDIT]good news about the improved legato - looking forward to it[/EDIT]

slainte rob

[WilliamK]

Thanxs, delete that DLL and reuse the proper one, since this new one is not ready yet.

Ok, the problem is not the compiler so, is something else. The problem is that I just don't know what yet... maybe some incompatibility in tracktion, not sure...

Wk

[pHz]

Ok, the problem is not the compiler so, is something else. The problem is that I just don't know what yet... maybe some incompatibility in tracktion, not sure...

heehee [though not funny really]

swap 'tubilesax' for 'tracktion' and thats pretty much what jules said

any other tracktion users testing out there ???

slainte rob

[pough]

any other tracktion users testing out there ???

I definitely would be if I had the time. I have, I think, about an hour tonight free. It's race weekend here in Vancouver and then I have a few days to move. But if William's happy to let me test TubiLeSax in Tracktion for just a very short time, I'd be happy to do it...

[WilliamK]

Thanxs pough, I included you on the list.

BETA UPDATE

I just uploaded 3 new files. 2 For First time users, so people who allready got the first installers, just download the UPDATE ok?

The update (and also the 2 other files) includes some new things:

Do not try to load a prev saved song with this version!

- Several .txt Scale files for the MicroTuning code. Also an internal name fix.

- The timing of each note is synced to the host frame-buffer now. (just like on daAlfa2k V2.1 update)

- Crossfade from prev-note to the next note. Up to 4 voices of cross-fade. If you use more than 4 voices, it will apply an mono envelope to avoid clicks. So far on my test it does play much much better. Also, the sound was fairly good, no clicks on the sound detected.

For the update installer, just install on the same location, the Installer should overwrite .log uninstall data.

Also, you can delete the "Equal Temperament.txt" file from inside the "Scale" folder, since the Update replaces it with another file. If you don't delete, is not a problem, don't worry.

Best Regards, WilliamK

[pough]

Started with Chainer..
... all good so far - sounds good.
... changed soundset once... twice... three times and then Chainer has caused an error and will be shut down

Reboot

Load Tracktion
...new edit
...add TubiLeSax to a track
...move keyboard input to that track
...press a key and BOOM! sound!... followed by normal notes
...sounds good (other than inital really loud crashing sound)
...change soundset
...Tracktion seems to still be running, but I can't do anything with it or with TubiLeSax
...in fact, clicking on Tracktion will not take focus away from this text editor
...but Task Manager doesn't claim that Tracktion isn't responding - odd
...shut down Tubi with Task Manager
...NOW Tracktion crashes

Reboot

Load Tracktion
...open previous edit with Tubi
...ERROR (context:dispatcher (24, 0, 39976, d93098, 0.000000))
...keep Tracktion running instead of shut down
...plays okay for a little bit then I remove the plugin, save and shut down Tracktion

Load Tracktion
...open blank edit
...load Tubi
...plays okay... changes soundsets okay
...close Tracktion

Load Tracktion
...open previous edit with Tubi
...ERROR (context:dispatcher (24, 0, 39976, d93098, 0.000000))
...keep Tracktion running instead of shut down
...plays okay for a little bit then I remove the plugin, save and shut down Tracktion

[pough]

It seems to work well in the energyXT standalone beta. I even tried the alternate tuning in that and they worked no problem!

[WilliamK]

I just uploaded a new update. It fixes the problem on loading new SoundSets. I was doing something double on the code, I fixed.

About Traction, I have no idea on what that could be, drats...

Question, right now the Crossfader Attack and Release/Decay is fixed, should we add an option to select how fast/slow it should be?

Regards, WilliamK

[-SPYRO-]

The crossfade works like a charm! well done!

I found that the glissando function works strangely, it seems to jump from a higher note than the new one even if the previous was a lower note. hope that's clear