Avid Pro Audio Community

Avid Pro Audio Community

How to Join & Post  •  Community Terms of Use  •  Help Us Help You

Knowledge Base Search  •  Community Search  •  Learn & Support


Avid Home Page

Go Back   Avid Pro Audio Community > Legacy Products > Pro Tools 10

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 01-09-2012, 08:44 PM
janos janos is offline
Member
 
Join Date: May 2011
Location: Seattle
Posts: 3
Default Problems Reading Imported MIDI (Sibelius)

I'm working in Sibelius as Midi editor and importing MIDI files into PT session.

After importing the data and connecting midi tracks to Aux Input tracks (and selecting voices (Xpand2) with plug-ins) I'm noticing subtle differences during playback.

This led to looking at the MIDI data in PT (using Midi Editor), where i realized that something is definitely different, or getting lost in the translation.


For example, in Sibelius, I had sextuplets (6notes in the space of four 16th notes). and additionally, note 2 of the group 6 was a 16th-note rest:

x.xxxx (where "." represents the rest in this sextuplet group)

PT MIDI editor shows

x x xxx (where "x x" are two 16th notes (instead of a group of three 16th note triplets), and "xxx" represents a group of 1/16th note triplets).

What gets lost in this example, is the 16th note triplet rest (indicated above by the ".") .

I have increased the MIDI output "ticks" or PPQNs (pulses per quarter note) in Sibelius when exporting the files. HOWEVER, Sibelius literature indicates that:
"Choosing a higher PPQN value doesn't make the exported MIDI file any more "accurate," since Sibelius's internal resolution is fixed at 256."
Question:
Does anyone know how to bridge this gap between Sibelius and PT to get more accurate imported MIDI file readings?

Janos
__________________
MacBook Pro 2.40 GHz Core i5, 4G RAM, OS Lion, mBox2 PT10
Reply With Quote
  #2  
Old 01-09-2012, 11:08 PM
panamajack's Avatar
panamajack panamajack is offline
Member
 
Join Date: Jan 2011
Location: Miniappleapolis
Posts: 713
Default Re: Problems Reading Imported MIDI (Sibelius)

There is a program marketed to deal with the reverse of your problem: the tuplet "lost in translation" issues when exporting MIDI files from a sequencer into a notation program. Not sure if it works going the other direction, as you are attempting, but you can download a free trial for either Mac or PC.

Scroll down for the "Switchblade" products, the software and computer hardware advertised at the top of the "store" page are something else entirely:

http://www.audioimpressions.com/store

I have heard about this program, but not used it yet myself.

Or check out this bit from the Sibelius blog...

http://www.sibeliusblog.com/news/not...ius/#more-1799

:)
Reply With Quote
  #3  
Old 01-13-2012, 02:30 PM
John_Toolbox's Avatar
John_Toolbox John_Toolbox is offline
Moderator
 
Join Date: Feb 2004
Location: Minneapolis
Posts: 5,403
Default Re: Problems Reading Imported MIDI (Sibelius)

Quote:
Originally Posted by janos View Post
I'm working in Sibelius as Midi editor and importing MIDI files into PT session.

After importing the data and connecting midi tracks to Aux Input tracks (and selecting voices (Xpand2) with plug-ins) I'm noticing subtle differences during playback.

This led to looking at the MIDI data in PT (using Midi Editor), where i realized that something is definitely different, or getting lost in the translation.


For example, in Sibelius, I had sextuplets (6notes in the space of four 16th notes). and additionally, note 2 of the group 6 was a 16th-note rest:

x.xxxx (where "." represents the rest in this sextuplet group)

PT MIDI editor shows

x x xxx (where "x x" are two 16th notes (instead of a group of three 16th note triplets), and "xxx" represents a group of 1/16th note triplets).

What gets lost in this example, is the 16th note triplet rest (indicated above by the ".") .

I have increased the MIDI output "ticks" or PPQNs (pulses per quarter note) in Sibelius when exporting the files. HOWEVER, Sibelius literature indicates that:
"Choosing a higher PPQN value doesn't make the exported MIDI file any more "accurate," since Sibelius's internal resolution is fixed at 256."
Question:
Does anyone know how to bridge this gap between Sibelius and PT to get more accurate imported MIDI file readings?

Janos
If I read this right, you are trying to fit 6 notes in a space that can be divided into 256 equal sections.

Based on that math, the number 256 doesn't divide equally by 6, you get 42.666666667~

I'm guessing that quantizing at 256 is rounding the note events just enough to cause this anomaly.

One other question, is it just the score display that is wrong? what does the midi grid editor look like in PT?
__________________
- John

If a MIDI event triggers a sample of a tree falling and there's no one there to hear it, does it make a sound?
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Imported Sibelius MIDI Files in Pro Tools 10, not playing back Eric.Yeung Windows 2 06-07-2012 04:34 AM
Problems with MIDI in 002R since I installed Sibelius 6.2 Chris7514 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) 3 12-04-2010 09:56 AM
Problems with MIDI I/O of 002R while running Sibelius 6.2 Chris7514 MIDI 0 12-03-2010 11:45 AM
Sibelius 6 midi files to into Protools problems LungFish MIDI 5 08-03-2010 06:25 AM
problems with mbox1 reading usb midi kylltyme MIDI 1 07-19-2006 07:44 PM


All times are GMT -7. The time now is 05:00 PM.


Powered by: vBulletin, Copyright ©2000 - 2008, Jelsoft Enterprises Limited. Forum Hosted By: URLJet.com