Hi
Cakewalk support has problems with their Internet site.
 
Hi Support
 
I have had a problem with my Tyros 5 keyboard when using System exclusive to playback Synths with Portamento.
Even though I play a portamento Synth with the sweep sound , it does not sound on playback using midi to trigger Tyros 5 through Sys Ex.
I do not know whether this occurs on other brands of workstations but It does with Yamaha synths and Workstations.
I have gone through this with some people in the know and now found out by advancing the note value by one tick does correct the problem and triggers the effect. A minute amount
I am talking about mono synths playing Portamento ,everything else is ok.
You can see It would be a pain to increase all notes played in a passage of a song and would be long winded and frustrating.
Could you put a fix In for this.
A kind person on the forum has written a Cal script file to apply to a track with portamento in it and it does work.
I have the cal script file If you want it.there Is no way to attach it on this enquiry (A forum member wrote the file for me ,much appreciated)
It would be great if you could implement this in a update as I bet many other yamaha owners have discovered and maybe other makes of keyboard owners.
For me this would be a massive update and also to people using onboard sounds from their workstations.
 
All the best
John
 
Ps, I will send this to support when their internet is up an not broken

I agree that CW should think about possible solution within there MIDI processing engine. For CW: the problem is that in case of Portamento Yamaha sends "Note Y On" event before "Note X Off" event, but both have the same time stamp. Since Sonar internally converts that into "Note X + duration", "Note Y", that information is lost and the output is "Note X Off", "Note Y On" and Portamento is not triggered.
 
That is more feature request, I guess they have no place to store such exceptions.
 
What we can do in the mean time is define MIDI FX (I have "AZ Lua" now, so that is a half an hour task, mostly to document the preset and upload it...). In such case you can just insert this MFX into the track in question and select required preset. The setup is saved within your project (as other FXes).Advantages over CAL solution: you do not need apply CAL on every MIDI clip, MFX will work automatically for all use cases, I mean live/recorded.
The only consequence is that I will need to occasionally extend by one tick notes which do not have to be extended (the explanation is too technical to write here). But I guess 1 tick longer notes (~0.001 of one beat duration) is impossible to notice (I repeat, that will rarely happened if at all).
Let me know what you think about such proposal.

If you have the sysex in a bank that is triggered there are various settings for delays etc.
Not sure if this is used when embedding sysex in the track though - but it should if that is what you are doing.
 
Many sysex are composed of a range of such F0...F7 messages and may need proper delay in between for receiver to process and not loose some of them. Detailed midi specs for instrument often tell which is appropriate delay for processing a request. I've seen on Roland and Hammond etc.

Hi Azslow
 
What Is AZlua  --program language!!!!
 
I am no good at program language and limited in that department.
I thank you for your reply and all I know is if to advance notes a tick or a few ticks in event list the Portamento triggers.(manually editing)
The cal script file works when you apply it to a track and I am very grateful for the man who wrote it for me.(I think it advances all notes with a little written program which save you doing it manually)
I would of though cakewalk would fix things like this instead of giving us landr and free loops etc
If I sent them the Cal file would it not be easy for them to implement a permanent fix.
 
All the best
John

lfm
If you have the sysex in a bank that is triggered there are various settings for delays etc.
Not sure if this is used when embedding sysex in the track though - but it should if that is what you are doing.
 
Many sysex are composed of a range of such F0...F7 messages and may need proper delay in between for receiver to process and not loose some of them. Detailed midi specs for instrument often tell which is appropriate delay for processing a request. I've seen on Roland and Hammond etc.

All things work sending sys ex to the Tyros 5 ,but not Portamento for some reason (notes need to be advanced just a tick or two in event list to make it trigger) Slightly out of alignment In my language.
Mike bedeseem and Sea Gruff (Psr Tutorial site) solved the issue but Cakewalk needs to Implement the solution.

igiwigi

lfm
If you have the sysex in a bank that is triggered there are various settings for delays etc.
Not sure if this is used when embedding sysex in the track though - but it should if that is what you are doing.
 
Many sysex are composed of a range of such F0...F7 messages and may need proper delay in between for receiver to process and not loose some of them. Detailed midi specs for instrument often tell which is appropriate delay for processing a request. I've seen on Roland and Hammond etc.

All things work sending sys ex to the Tyros 5 ,but not Portamento for some reason (notes need to be advanced just a tick or two in event list to make it trigger) Slightly out of alignment In my language.
Mike bedeseem and Sea Gruff (Psr Tutorial site) solved the issue but Cakewalk needs to Implement the solution.

So if you have the sysex on a separate track and advance that x ticks earlier in time, it does not work?
You have a setting on midi track for time alignment which I use to line up rendered audio for external gear.

lfm
So if you have the sysex on a separate track and advance that x ticks earlier in time, it does not work?
You have a setting on midi track for time alignment which I use to line up rendered audio for external gear.

OP problem has nothing to do with SysEx. The word was used several times, but the problem is with MIDI interpretation within Sonar (the explanation you can find in my previous post).
 

igiwigi
What Is AZlua  --program language!!!!

Almost all plug-ins are written in C++, I guess your Yamaha firmware is written in C/C++/Assembly/Some scripting. That does not prevent you from using the staff.
"AZ Lua" is a plug-in, written in C, but the effects are implemented in "Lua" programming language. As an "end user" you get plug-in window, with normal GUI (when required, not is this case). May be I should think how to rename the plug-in so it is not "programming oriented".... What about "AZ MIDI Universe" / "Eierlegende Wollmilchsau MFX" ( en: "MIDI Swiss army knife" ) ?
 
So, in case you like the final functionality I have explained in the previous post, I will prepare corresponding preset myself.

The cal script file works when you apply it to a track and I am very grateful for the man who wrote it for me.(I think it advances all notes with a little written program which save you doing it manually)

Since I do not have Yamaha, as with the CAL script I just need someone who can test it works correctly and report in case it does not.
 

azslow3

lfm
So if you have the sysex on a separate track and advance that x ticks earlier in time, it does not work?
You have a setting on midi track for time alignment which I use to line up rendered audio for external gear.

OP problem has nothing to do with SysEx. The word was used several times, but the problem is with MIDI interpretation within Sonar (the explanation you can find in my previous post).
 

 
I see what you mean, that is quite another story.
A midi monitor like TenCrazy could tell the exact sequence of events:
http://www.tencrazy.com/gadgets/mfx/
 
As far as I recall CAL is never realtime, so another solution could be to use the Cockos ReaJS and JS scripting languange which also works in realtime. Not a MFX plugin, just VST, and can be routed through a separate track or with the new AUX+patch points more freely.
 
BlueCat Audio also has Plug'n Script which is VST only, but extensive scripting possible in realtime.
 

Hi
Sorry for Interupting here, but all this jargon confuses me.
Is there a simple way of cakewalk Implementing a script Into Sonar or am I a small percentage that nothing will be done.
I can use the cal script file  but It would be nice to see It In Sonar Instead of landr etc
Apologies to AZSLOW--You wrote the script for me!!! --Still a big thanks there and much appreciated
I suppose it is a dead end asking Cakewalk to look at this.!!.We can all live In hope!!
 
All the best
John
 
 
 

igiwigi
Hi
Sorry for Interupting here, but all this jargon confuses me.
Is there a simple way of cakewalk Implementing a script Into Sonar or am I a small percentage that nothing will be done.
I can use the cal script file  but It would be nice to see It In Sonar Instead of landr etc
Apologies to AZSLOW--You wrote the script for me!!! --Still a big thanks there and much appreciated
I suppose it is a dead end asking Cakewalk to look at this.!!.We can all live In hope!!

I do not know for what you decide to apologies... Leaving jargon for the following reply to lfm, let me ask you the question one more time (in shorter form): do you think inserting MFX (MIDI FX, the same procedure as putting VST into audio track FX bin) into the track in question can improve your framework over CAL solution?
If yes (which means you are ready and have some time to try that), I will prepare the preset. If no, lets wait for CW.
 
@lfm:
The problem origin is already understood. TenCrazy tools are in fact can help tracing, but that was already done.
 
"AZ Lua" is Sonar native version of "ReaJS", MIDI only and based on Lua instead of JavaScript. It works like Sonar own MIDI plug-ins, in realtime and as a processor. There are some general problems with DX based MIDI processing, so all such plug-ins have nasty limitations. Markleford (the author of TenCrazy plug-ins) has initiated related discussion more then 10 years ago. Unfortunately, nothing is changed since that time.
 
VST based MIDI processing in Sonar is hard to call a solution, it is dirty and error prone workaround (coming form the fact Sonar converts MIDI to/from DX based representation which is significantly different).
 
AUX + Patch points are not MIDI capable, I do not see how they can help in the area.