Something I forgot. You can filter tracks to remove different types of MIDI 
events -- note data, controller data, program changes, sysex, and so on. This 
means if you want to get some of this out of a track you can duplicate the 
track and then filter what you want out of it. And with most of the gear I've 
dealt with tempo information is always on one track and unless the sysex is 
doing patch editing it's on the instrument's base track. So it might be easier 
than it seems to be to break this out to a separate QWS track.

Sent from my HAL 9000 in transit to Jupiter


-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Brian 
Olesen
Sent: Thursday, November 19, 2020 4:39 PM
To: QWS list <[email protected]>
Subject: QWS List SV: Resending this as it didn't get any responses.

Hi Nicole,
Awesome answer.
Thank you so much. Now I have some serious good stuff to work with in the 
morning. 😊
Very kind of you!

Best regards
Brian

-----Oprindelig meddelelse-----
Fra: [email protected] <[email protected]> PÃ¥ vegne af Nicole Massey
Sendt: 19. november 2020 23:23
Til: QWS list <[email protected]>
Emne: RE: QWS List Resending this as it didn't get any responses.

I responded to the first one -- did you not get it?

Here's what I replied:
First off, you can't view the lyrics in QWS, so you'll want to find some other 
way to view them.
Sonar, like almost every other sequencing program, makes some assumptions about 
what you want to do with MIDI data. QWS doesn't do this, so there's a bit of a 
learning curve at first but it's refreshing to not have a program making 
decisions for you. So open the type 0 file, perform a save as, and save as a 
type 1 file. It'll save every channel on a separate track.
You're probably going to find your program change and other data embedded in 
the track instead of in the properties window. You can leave it there or dig 
around for it and delete it and move it to properties. This may involve bank 
changes, possibly high definition bank changes on the track side, and if there 
are bank changes you'll need to convert them to high definition bank changes 
because that's the QWS default. (multiply low definition bank changes by 128 to 
get the high definition value) You can either dig around until you find 
something sent on CC0 immediately followed by CC32, or you can consult your 
best friend, the MIDI Implementation Chart, to find out what kind of bank 
changes it uses.
Make sense?

Sent from my HAL 9000 in transit to Jupiter


-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Brian 
Olesen
Sent: Thursday, November 19, 2020 3:02 PM
To: QWS list <[email protected]>
Subject: QWS List Resending this as it didn't get any responses.

Dear QWS dudes, and Dudettes,

I can’t tell for sure, but I use some commercial midi files written 
specifically for Yamaha Tyros 5 that I’d like to edit and work with hopefully 
in QWS.

When I open them I get only one track, so I assume they are written in format 
0. On the other hand they fully open in Sonar with the data already separated 
on 15 tracks.

 

But there are more than just one strangeness involved here. 😊

They include lyrics, they include sysx, and when I do a channel split they 
don’t contain the program changes on the separate tracks created. Where do I 
fine these, and how?

Is it possible to view the lyrics in the file with QWS?

Can I remove all notes and controller information from track 0 so only the sysx 
data remains, or how would you clean up such files, so the data ain’t being 
sent double?

 

I hope this wasn’t too confusing? 😊

Thanks in advance.

 

Best regards

Brian

 

 


To unsubscribe or change list options, see http://lists.andrelouis.com

for archived list posts, see http://www.mail-archive.com/[email protected]

To unsubscribe or change list options, see http://lists.andrelouis.com

for archived list posts, see http://www.mail-archive.com/[email protected]

To unsubscribe or change list options, see http://lists.andrelouis.com

for archived list posts, see http://www.mail-archive.com/[email protected]

Reply via email to