1. What kind of problem with off notes? Can you be more specific?
2. You mean opening curves saved with an older version of the plug? I don't think that will work as the plug's internal parameters have changed, you will probably have to recreate any curves you had and re-save them.
3. Like I said, it might be possible but it would require a total redesign of the plug. I don't have the time to look at it right now as I'm really busy with several other projects...
VST MIDI Velocity Curve Scaler for Tracktion
-
- KVRAF
- 6740 posts since 25 Mar, 2002 from sheffield, england
-
- KVRAF
- 6081 posts since 27 Jul, 2001 from Tarpon Springs, Florida, USA
Hello IIRs,
1. I use Cubase SX3 and energyXT. I open two Virtual grand pianos in energyXT. One has Veleocitycurve before and the other has no VC. All is OK until I set both tracks to sustain. The one Piano with the VC the notes on the keyboard stay down when stricken. If you can help here it will be great.
2. I believe I had not saved the FXB. Now the FXP show up.
1. I use Cubase SX3 and energyXT. I open two Virtual grand pianos in energyXT. One has Veleocitycurve before and the other has no VC. All is OK until I set both tracks to sustain. The one Piano with the VC the notes on the keyboard stay down when stricken. If you can help here it will be great.
2. I believe I had not saved the FXB. Now the FXP show up.
-
- KVRAF
- 6740 posts since 25 Mar, 2002 from sheffield, england
What do you mean by "set them to sustain" ... you mean the hold pedal, controller 64?
It seems to work ok here in Tracktion. I don't have a sustain pedal but I drew in some cc64 data and it worked as I expected.
It seems to work ok here in Tracktion. I don't have a sustain pedal but I drew in some cc64 data and it worked as I expected.
-
- KVRAF
- 6081 posts since 27 Jul, 2001 from Tarpon Springs, Florida, USA
Hello IIRs,
After further testing I was able to replicate this problem without the VelocityCureve. In fact the problem appeared readily as soon as I employed Inserts - Midi Control - Controller 64. The problem occurred even if did not use energyXT.
I apologize for not looking deeper into the problem before posting. Thanks again for the VelocityCurve!
After further testing I was able to replicate this problem without the VelocityCureve. In fact the problem appeared readily as soon as I employed Inserts - Midi Control - Controller 64. The problem occurred even if did not use energyXT.
I apologize for not looking deeper into the problem before posting. Thanks again for the VelocityCurve!
-
- KVRAF
- 6740 posts since 25 Mar, 2002 from sheffield, england
No problem! 
I had a quick play with those 3rd party modules btw, to see if I could get the midi channels to pass through as you wanted: they weren't working as I expected them to at all, so I would need to talk to the developer to find out why... it might happen one day.
I had a quick play with those 3rd party modules btw, to see if I could get the midi channels to pass through as you wanted: they weren't working as I expected them to at all, so I would need to talk to the developer to find out why... it might happen one day.
-
- KVRAF
- 6740 posts since 25 Mar, 2002 from sheffield, england
I had a go at making a version with SynthMaker instead:
The spline waveshaper was stolen from Sambean and modified slightly: click on the curve to add a new node (max 20) or drag & drop a node outside the region to delete it. Let me know if it works ok: I never made a midi only plug with SM before.
download
The spline waveshaper was stolen from Sambean and modified slightly: click on the curve to add a new node (max 20) or drag & drop a node outside the region to delete it. Let me know if it works ok: I never made a midi only plug with SM before.
download
-
- KVRAF
- 8519 posts since 7 Apr, 2003
nice. is it easier to move the nodes and such with the SM ver?IIRs wrote:I had a go at making a version with SynthMaker instead:
The spline waveshaper was stolen from Sambean and modified slightly: click on the curve to add a new node (max 20) or drag & drop a node outside the region to delete it. Let me know if it works ok: I never made a midi only plug with SM before.
download
thanks IIRs!
-
- KVRAF
- 6740 posts since 25 Mar, 2002 from sheffield, england
Its much easier to create curves as you need fewer nodes: the compress and expand presets all use just 3 nodes, while the one pictured above uses only 4.
Also it solves the midi channel issue: midi data is (hopefully) passed through unchanged apart from velocity, so no need to select input or output channels.
One thing I haven't managed to get right is the moving point on the graph to indicate the current values: it worked but caused a glitch in the sound whenever it moved, so I took it out again... I might have to shout for help on the SM forum with that one.
Also it solves the midi channel issue: midi data is (hopefully) passed through unchanged apart from velocity, so no need to select input or output channels.
One thing I haven't managed to get right is the moving point on the graph to indicate the current values: it worked but caused a glitch in the sound whenever it moved, so I took it out again... I might have to shout for help on the SM forum with that one.
-
- KVRAF
- 6081 posts since 27 Jul, 2001 from Tarpon Springs, Florida, USA
Hello IIRs,
Well the node concept is great. This creates smoother curves and is noticeable while striking the keys. Also very fast to edit. Why are the nodes so jumpy? They seem to snap to a location. Can this be fixed?
I may yet not have to buy another keyboard! The keyboard world should know about your VelocityCurve.
The channels were unchanged on the output. So I doubly appreciate it here. Due to the improvements it may not be necessary to show the indicator in my opinion.
Thanks again for all the time and effort you have put in to helping me and all the others that are velocity challenged.
Well the node concept is great. This creates smoother curves and is noticeable while striking the keys. Also very fast to edit. Why are the nodes so jumpy? They seem to snap to a location. Can this be fixed?
I may yet not have to buy another keyboard! The keyboard world should know about your VelocityCurve.
The channels were unchanged on the output. So I doubly appreciate it here. Due to the improvements it may not be necessary to show the indicator in my opinion.
Thanks again for all the time and effort you have put in to helping me and all the others that are velocity challenged.
-
- KVRAF
- 6740 posts since 25 Mar, 2002 from sheffield, england
Probably... problem is I don't understand the workings of the waveshaper well enoughKalamata Kid wrote:Why are the nodes so jumpy? They seem to snap to a location. Can this be fixed?
I figured out how to change the array size to 127, but frankly SM's graphics modules still scare me a bit. 
Warmonger wrote:Looks like SynthMaker > SynthEdit!
-
- KVRAF
- 6740 posts since 25 Mar, 2002 from sheffield, england
-
- KVRAF
- 6081 posts since 27 Jul, 2001 from Tarpon Springs, Florida, USA
IRRs,
I believe that did it. It works great.
The nodes make it fast and easy to edit.
Thank again.
I believe that did it. It works great.
The nodes make it fast and easy to edit.
Thank again.
-
- KVRAF
- 6081 posts since 27 Jul, 2001 from Tarpon Springs, Florida, USA
IIRs,
Will the VC download link be up for awhile? Can I post this on related energyXT thread?
Will the VC download link be up for awhile? Can I post this on related energyXT thread?
-
- KVRAF
- 6740 posts since 25 Mar, 2002 from sheffield, england