Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More than half of the knobs seem to have no change in noise volume. Is this normal? #177

Closed
Jpro600k opened this issue Jul 11, 2022 · 25 comments
Assignees
Labels
change request Changed behaviour of existing function

Comments

@Jpro600k
Copy link

Jpro600k commented Jul 11, 2022

Added noise mod. Successful mixing noise, Tape 44 works well.
however, I was wondering if I could hear more intense roaring noise, but it wasn't.
More than half of the knobs seem to have no change in noise volume. Is this normal?

@image-et-son
Copy link
Owner

I think that Matrxi12x should comment on this. Maybe I need to change the travel. But I'd need more feedbakc on this.

@matrix12x
Copy link

I’m not 100% sure what knobs we are discussing. “Half of the knobs” is this half of the total number of knobs or the range of a particular knob ?
Or does it mean the response of menu option 44?
Or is it the mix a and b knob ?

when I installed my noise mod, I set the output voltage to the same level as the saw waveform on the vco.

@Jpro600k
Copy link
Author

Jpro600k commented Jul 12, 2022

it does mean the response of menu option 44. speed knob.
speed knob value 50-99 sounds almost the same.
From 50 to 99, can you hear the difference clearly?
I think the voltages are probably not the same. I don't know because I haven't measured it. Your opinion will be helpful. Thank you.
I may also solder to input B.
Will input B follow from 50 to 99?

@matrix12x
Copy link

I agree. Above the halfway point there is little to no change in response.

@image-et-son
Copy link
Owner

In GliGli's version the value was set as follows:

sh_setCV(pcExtFil,24576,SH_FLAG_IMMEDIATE); // value from the emulator

Maybe 24576 is the max value? Maybe you can get this from the circuitry...

That value would be around 38 (which is a lot smaller than 50). From what you say I could do a ">>1" and that would already improve the situation a lot. What do you think?

@image-et-son image-et-son self-assigned this Jul 12, 2022
@image-et-son image-et-son added the change request Changed behaviour of existing function label Jul 12, 2022
@matrix12x
Copy link

If you want I can measure the control voltages at different settings. Let me know. Maybe we should make the response curve log

@matrix12x
Copy link

So I did some measurements.
Pin 10 of U458 at parameter 44 value of 50 is about 2.5V and at 99 it is about 5V.
The nose when measured at the output of the synth plateaus at about 1.75V p-p at parameter 44 value 38-39 or so (which seems to match GliGli's values above).

Accordingly, 24576 should be the max value. I suggest making this code change.

Also of note, @Jpro600k if you need more volume maybe hook up 100K resistors/noise to the B side also. It would increase your noise volume by 3dB (double).

@Jpro600k
Copy link
Author

I would like you to change it so that it changes smoothly up to the value 99.

@Jpro600k
Copy link
Author

Jpro600k commented Jul 13, 2022

if you need more volume maybe hook up 100K resistors/noise to the B side also. It would increase your noise volume by 3dB (double).

Thank you for your wonderful survey. After a while, connect to input B as well.

@image-et-son
Copy link
Owner

Hi, here is a trial version with the external voltage control (i.e.noise level) scaled to the range we have identified. Please check it out and tell me if it is ok. And then don't copy, reuse or distribute this firmware version - it is not a tracked version.

BTW: it has all the fixes after beta 2 in it and also the one new feature: LFO Trigger (parameter 222) "Key". This retriggers the LFO with a new key stroke when no other key is held (similar to modulation delay). I think this is very useful :-)
p600firmware_beta_2022_2_fix177.zip

@matrix12x
Copy link

I confirmed LFO trigger works. but it is located at parameter 1 1 1 , and I thought it said 'Hey', not 'key'. I was excited. lol
also, the ext voltage control has no additional effect after about 50. it works fine from about 0 to about 50. I watched the noise level on a scope on the output while turning the knob (parameter 44).

@image-et-son
Copy link
Owner

So the noise travel doesn't work!? Will look into it tomorrow.

@matrix12x
Copy link

correct. If you want I can measure the control voltage at pin 10 at mid and max range. but I think at max range we want it to be 2.5VDC, based on my testing not the full scale 5V.

@image-et-son
Copy link
Owner

Haha ... the change was such a no-brainer that it made me sloppy. For the change I copied the old line of code where the voltage is set and then forgot to delete the old line. And then since it came after the new one....

Here is the corrected one.
p600firmware_beta_2022_2_fix177_2.zip

@image-et-son image-et-son moved this from Ready to deploy to Ready for test in v2022 - new stable Version P600 GliGli Firmware Upgrade Jul 15, 2022
@Jpro600k
Copy link
Author

Also of note, @Jpro600k if you need more volume maybe hook up 100K resistors/noise to the B side also. It would increase your noise volume by 3dB (double).

Hi, Matrix12x

I also connected to B.
The amount of noise is definitely increasing. Very close to ideal.

@matrix12x
Copy link

@image-et-son the updated version above works (fix 117_2). I monitored the signal on a scope and it changes level over the entire range.

@Jpro600k
Copy link
Author

I heard a step when I turned the knob.
fix 117_2

Check this.
step_noise.zip
.

@matrix12x
Copy link

I have this steps too, but this seems to be more of a set and forget setting than a live performance tweak setting, so I didn't care.

@Jpro600k
Copy link
Author

Jpro600k commented Jul 15, 2022

After updating to fix117_2, I noticed that the tuning was significantly out of sync. I turn off the power, wait for a while, short the TP301, and then tune again.

@Jpro600k
Copy link
Author

I have this steps too, but this seems to be more of a set and forget setting than a live performance tweak setting, so I didn't care.

Is there a possibility that it can be done smoothly?

@Jpro600k
Copy link
Author

Jpro600k commented Jul 16, 2022

About beta_2022_2_fix177_2

I removed the noise modification, restored it to its original state, and then tuned it, but the pitch is random. Is there a way to fix it?
sound test
tuning_issue.zip

like a CDEFGABCBAGFEDCCDEFGABCBAGFEDC

Haha ... the change was such a no-brainer that it made me sloppy. For the change I copied the old line of code where the voltage is set and then forgot to delete the old line. And then since it came after the new one....

@Jpro600k
Copy link
Author

After updating to fix117_2, I noticed that the tuning was significantly out of sync. I turn off the power, wait for a while, short the TP301, and then tune again.

I tried to adjust the pitch by the TP301, but the display is random and unstable, it works only in the range of 99 to 40, and I can not approach 0.0.
The noise mod is reattached.
The LED is displayed normally when booting in normal mode. There is no random display.

@matrix12x
Copy link

@Jpro600k I think the synth does not "mute" the noise mod properly when tuning.

NOTE: My noise mod has a volume trimer one the output. I found I have to manually turn down the noise mod to almost zero volume then tuning works.

Its weird because the code looks like it should mute the noise during the tuning sequence. This should probably be spun off as another bug. But it's a long existing bug, I know my code had the issue.

@image-et-son
Copy link
Owner

Yes, I looked it up as well: the noise level (as corresponds to the menu parameter 44) is set to zero in preparation of tuning. I have not experience with the noise mod, though. So I don't know if it somehow still enters the tuning procedure even if set to zero.

@matrix12x
Copy link

I may at some point monitor the voltage on pin 10 and see what happens during tuning.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
change request Changed behaviour of existing function
Development

No branches or pull requests

3 participants