guitarix go's midi

[brummer]

Do you meen there is no visual output in the tuner widget ??
No tune's are show'n, no graph wip to the right side ??, nothing at all ??
strange, . .

You can try to edit the file ~/guitarix/src/main.cpp line 28
#include <math.h>
replace it with
#include <cmath>

let me know the result.

You can also checkout svn again, anyway, if the midi out dont work for you, you find a new effekt modul, valve, it's a tube simulation were you can select how many tubs you run, and a overdrive modul in the amp section.
For the midi_out I have open the triggerpoint a bit, and set down the selectable minimal limit. But if the tuner dont work for you, you dont get midi output.
I have replace the round() funktion with a declared inline funktion, so maybee it work now for you.

[thorgal]

brummer, I see the problem: for the stuff to work (tuner and MIDI), you need the audio engine to be on. I thought the engine would only be affecting the different processing modules.

Anyway, I checked again in kmidimon and I see CC messages coming from guitarix:


what would be fun is some note on / off but that would be too random, as you would not be able to know the approximate note played on the guitar that fast.

[brummer]

for the stuff to work (tuner and MIDI), you need the audio engine to be on.

sure, switch the engine off (stopp) disable any output, meen set it to 0 and stopp processing.

anyway, if the tuner dont work, you cant get Note's, this meen the midi output are only note off messages. They come when the engine cant detect a recent input for longer .
I have explaine the Note off knob wrong, as higher you set it, as faster the engine will send Note_Off messages, set it to a lower level <20 .

So I have reduce the entry value with 1/10 to check lower values for a beat/frequence.
try rev 110

[brummer]

To give a example how it work for me, her is a guitarix_session0.ogg
http://FileHost.JustFreeSpace.Com/220gu ... ssion0.ogg

[thorgal]

Hermann, the tuner works fine, I just don't get a Note On event, just a Control Change

[brummer]

Hermann, the tuner works fine

Ah, thats good, so it must be the beatdetector. Have you try rev 110 ?
there I have set down the entry value for the beatdetector, now you can set it down to 0.005
also set the note_off to a lower level, leve note_on at 20
set the sensity for the channel to 1
turn on velocity and volume.
connect only one port with guitarix_in

If it dont work, please connect a micro with guitarix_in and try if you get a Midi_output when you sing.
If so I will include a push-switch to incrase the gain from the input signal befor it meat the beatdetector.

[funkmuscle]

no tuner, no midi for me... ZZTop tone with new effects. a little muddy sounding but working on it..
Hey guys try this, load one of the caps amp sim plugins in ardour after recording a clean guitar track. For that plugin with the impulse convolver ladspa plugin. Run it in 44100, not 48000, etc.
I got a really true amp sound as the impulse convolver ladspa plugin uses real IR files. I think it has 13 or 15 or so. In fact, I have those IR files and I use them under jconv.
Maybe the Impulse Convolver on guitarix can be modelled after that...

[brummer]

no tuner, no midi for me

mmm. . .

You can try the following, open ~/guitarix/src/dsp.cpp with a texteditor and edit line 1459
float fTemphp0 = checkfreq ;

replace it with
float fTemphp0 = input0;

recompile it

switch on tube to 10 and drive to 10 and anti aliase (slider to the right side) try the tuner

[brummer]

rev 111

try the new midi engine, if you dont have loose your interesst in audio2midi funktion.
I have rearange the frequence and beat detection, maybee it work now also for you ??

[funkmuscle]

qsynth receives the signal as always, the channels don't. No working at all.
The issue is between qsynth and the soundfonts...maybe not because I tried loading the soundfonts on the audigy card and still not sound.

Hey, I found a nice distortion for linux. Well, it's been ported to linux. the mda plugins.
I tried it with a caps ampsim and an IR file. I will try to make a sample if I have time.

Here a a quick SLOPPY sample but you hear what is sounds like...
http://FileHost.JustFreeSpace.Com/794sample1.mp3

no EQ, verbs, nothing...and very bad playing, only had 5 minutes to do something so this is raw

[brummer]

so I gues you dont like the fixed resonator guitarix used. I have made it selectabel now, switch it off if you dont like it.

qsynth receives the signal as always, the channels don't. No working at all.

realy strange, no output from the tuner, have you try a MICROFON to guitarix_in ?
I need to now if the tuner give a output when you capture a MICROFON, to debug this issues ?

[thorgal]

HOLY CRAP! that stuff is crazy SHIT!!
I updated the svn version, and fiddled with the beat detector. Now the VSTi I connect to guitarix MIDI out plays every wild guess the tuner is making. It sounds hellish man!

there must be parameter combination that plays cool I hope but it is working

but let me record a sample (I connect guitarix to Pianoteq). I disabled guitarix audio outputs, so it's only the piano ...

here it is: http://FileHost.JustFreeSpace.Com/568gu ... 2piano.mp3


HOLY SHIT 2!! have you tried paulstretch ?? http://hypermammut.sourceforge.net/paulstretch/
I just applied a stretch factor of 20 on my sample above ... CRAAAAZZZY!

[funkmuscle]

To get that sound I sampled under linux using software, only vsts or vsts mixed in sounds like that. Guitarix with jconv sounds cool on a clean tone or a little crunch but the amount of distortion in that sample I can't get from linux apps.

I finally got the tuner working with my guitar and mic. Still not working with qsynth. I even updated to the latest qsynth released a day or 2 ago... still, I see the qsynth1 tab light flashing but nothing on the channels.

doesn't work with my audigy card too. will try to find a free vsti and try it...

[brummer]

I finally got the tuner working with my guitar and mic. Still not working with qsynth.

Okay, that's the half rent.

Now, the question is "Is your input signal to low ?" or "Is it noisy ?"
It's, the beatdetector work with the input signal, it detect a change in the value. When you feed it with a noisy signal, it can't detect a beat. also when the signal is to low. Both cenario's need different sollutions. So let's analyse. Can you produce with your guitar a view in the secound oscilloscope like this on ?


The read wave is the input signal, the dashed line on top is the input volume, the dashed line on base is the output volume, the green wave(you cant see it here because it's under the red one) is the output signal. Intersting is here if you can produce a red wave like this one witch is wipping up and down ? when you play, or is it more static ? And is static but the dashed line on top is wipping ?

HOLY CRAP! that stuff is crazy SHIT!!

Yea, it need's a bit fiddled with the beat detector and the sencity knobs to get a usefull output.
I like it the following way. Set the sensity to 1 and start with the beat_attack at a low level. Push the beat_attak higher up to the point were you hear on synth-output when you hit your strings. Now, for percusion set the sensity to 10 or so, set the sensity for the bass to 30 or so, set the sensity for a background noise (sitar, cello, or so) higher then the bass. Play, if it is to mutch output, set the beat_attak higher.
The Note_on knob show how many sampels will be analysed befor get the note out of it. Dont set it to low, 20 is a good value, maybee higher for some cases.
Nice could be the autogain option for the bass and the background.

HOLY SHIT 2!! have you tried paulstretch ?? http://hypermammut.sourceforge.net/paulstretch/ ... CRAAAAZZZY!

Haden't the time to look at it, but yea, it sound's like a app that I could like .

[funkmuscle]

got all the colours in the oscilloscope but still nothing... you know on qsynth when you click the channels button, you see the soundfonts, they have a light on the left, those lights don't come on at all but qsynth is getting a signal but not to strong. The oscilloscope colours looks just like your pic.

I don't think this will work for me..