24 bit I/O with Native

Pyramix Native users forum
Forum rules
The Merging Technologies team cannot be held responsible for support queries logged on the public forums. If a support query is logged here and only here, it may not be found and dealt with by the appropriate team.
To ensure that your support issue or bug report is dealt with properly and in good time, please use the link to the tech support request form page on the Merging website.
Make sure to let us know what version you are using when you send your mail. THANKS!
Davey
Posts: 18
Joined: Thu May 05, 2005 16:31
Location: New York, NY
Contact:

24 bit I/O with Native

Postby Davey » Wed May 24, 2006 23:21

With versions before 5 there was an issue with Native being able to record and send 24 bits - this was confirmed by a tech support person in Switzerland. Of course you could load and send 24 bits via firewire or DVD drive but that's it. I believe monitoring was limited to 16 bits as well. Has this issue been resolved in v5?

Thanks for any information about this.

Kees de Visser
Posts: 57
Joined: Fri Sep 27, 2002 19:51

Re: 24 bit I/O with Native

Postby Kees de Visser » Mon Sep 11, 2006 21:53

Davey wrote:...I believe monitoring was limited to 16 bits as well. Has this issue been resolved in v5?


Right now I'm testdriving a Pyramix native demo on my MacBook. It seems that there are only 16 of the 24 data bits active in the desk and monitor output.
My first thought was to blame Apple's windows driver for the MacBook digital I/O, but after reading your post I'm not too sure.
Did you get a final answer about this ?

User avatar
Graemme
Posts: 2260
Joined: Wed May 15, 2002 22:18
Location: Gabriola, BC, Canada
Contact:

Re: 24 bit I/O with Native

Postby Graemme » Tue Sep 12, 2006 01:24

Using the Dirext-X implemenation of Pyramix Native, you get 16 bit I/O. Use ASIO to ensure 24 bit I/O. Internal mixes/bounces aren't affected, just I/O.

Best,

Graemme

Kees de Visser wrote:
Davey wrote:...I believe monitoring was limited to 16 bits as well. Has this issue been resolved in v5?


Right now I'm testdriving a Pyramix native demo on my MacBook. It seems that there are only 16 of the 24 data bits active in the desk and monitor output.
My first thought was to blame Apple's windows driver for the MacBook digital I/O, but after reading your post I'm not too sure.
Did you get a final answer about this ?
Graemme Brown
Zen Mastering
1460 Wild Rose Drive
Gabriola Island, BC
Canada V0R 1X5
+1.604.874.9096

"A Horus, A Horus; My Kingdom for a Horus!"

Kees de Visser
Posts: 57
Joined: Fri Sep 27, 2002 19:51

Re: 24 bit I/O with Native

Postby Kees de Visser » Wed Sep 13, 2006 11:33

Graemme wrote:Using the Dirext-X implemenation of Pyramix Native, you get 16 bit I/O. Use ASIO to ensure 24 bit I/O. Internal mixes/bounces aren't affected, just I/O.

Sorry for asking again, but I'm new to Pyramix, Windows and ASIO. Did I get it right that:

- Pyramix provides only 16 bit I/O when using Direct-X. This is a limitation of the Pyramix implementation and not of Direct-X.

Could Pyramix change its software to allow 24 bit Direct-X if they wanted ?
I'd love to be able to use my MacBook's internal converters at 24 bit. Pyramix doesn't seem to recognize the asio4all driver I've installed yesterday (or perhaps I missed something). Is there anything else I could try ?

Best regards,

Kees de Visser
Galaxy Classics

User avatar
Graemme
Posts: 2260
Joined: Wed May 15, 2002 22:18
Location: Gabriola, BC, Canada
Contact:

Re: 24 bit I/O with Native

Postby Graemme » Wed Sep 13, 2006 19:52

- Pyramix provides only 16 bit I/O when using Direct-X. This is a limitation of the Pyramix implementation and not of Direct-X.


Yes, it's a Pyramix limitation.

Could Pyramix change its software to allow 24 bit Direct-X if they wanted ?


If they wanted to, yes. However, (Now, I'm surmising out loud...) ASIO makes much more sense from a small company's development perspective. ASIO is a much more 'Pro' architecture (low and predictable latencies, etc.) and there's probably some connection to Merging's evolving VST implementation as well.


I'd love to be able to use my MacBook's internal converters at 24 bit.


I understand and also note that the workaround (bus-powered USB interface with ASIO driver) isn't that painful, financially.

Pyramix doesn't seem to recognize the asio4all driver I've installed yesterday (or perhaps I missed something). Is there anything else I could try ?


Which steps did you take when you attempted to load the asio4all driver? Did you switch Pyrammix from Direct-X to ASIO in the VS3 settings control panel?

Best Regards,

Graemme
Graemme Brown
Zen Mastering
1460 Wild Rose Drive
Gabriola Island, BC
Canada V0R 1X5
+1.604.874.9096

"A Horus, A Horus; My Kingdom for a Horus!"

User avatar
Graemme
Posts: 2260
Joined: Wed May 15, 2002 22:18
Location: Gabriola, BC, Canada
Contact:

Postby Graemme » Wed Sep 13, 2006 20:11

Hi Kees,

I just succesfully loaded and ran the asio4all software on my Toshiba laptop. After installing the asio4all software, go to the 'VS3 settings' control panel (Start Menu/Settings/Control Panel/VS3 Settings) and select the 2nd tab (ASIO). Click in the "Use ASIO..." checkbox, select the asio4all driver from the drop-down list and save/exit the control panel.

Now when you run Pyramix, go to the 'Formats & Sync' area of the 'General Settings' window and you should see the 'asio4all' driver listed as your master sync device. Underneath that is a button labelled 'Control Panel' - open it and click on the advanced button, noticing the change of picture...

Good luck,

Graemme
Graemme Brown
Zen Mastering
1460 Wild Rose Drive
Gabriola Island, BC
Canada V0R 1X5
+1.604.874.9096

"A Horus, A Horus; My Kingdom for a Horus!"

Kees de Visser
Posts: 57
Joined: Fri Sep 27, 2002 19:51

Postby Kees de Visser » Thu Sep 14, 2006 13:05

Hi Graemme,

thank you so much for your fast and helpful answer !
After some fiddling I managed to activate the asio4all driver myself, but it's good to have the procedure confirmed :)
With this asio driver however the only I/O option I get is 24/48. This looks like a limitation of the driver, since the MacBook hardware is definitely capable of more. Anyway, it seems I'll have to choose between 16 bit DirectX at original samplerate, or asio with 24 bit, but SRC'd to 48 kHz. Unless you know a solution to switch samplerate with asio.

It looks like a long Pyramix learning curve, but I'm sure it's worth it :)