|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Re: PARIS ASIO/Scherzo64 Coming along very nicely! [message #107187 is a reply to message #107158] |
Fri, 03 August 2012 00:26 |
|
Mike, YOU ROCK!
For me, I'd just like to be able to use PARIS again. I have 16 audio inputs dying to be used again.
On my secondary drive where I installed Win 7 32bit, I still haven't been able to get the current version of the scherzo driver to initialize my PARIS hardware.
I've been using SONAR X1 for quite a while. I like the fact I'm able to use VST instruments. A feature like that in PARIS would have been absolutely incredible. With the new PARIS ASIO driver would I be able to use my PARIS hardware with SONAR?
By the way, what will you be charging for the new 64bit drivers?
Cheers, JON
P.S. I hope everything turned out fine with your wife.
|
|
|
|
|
Re: PARIS ASIO/Scherzo64 Coming along very nicely! [message #107190 is a reply to message #107189] |
Fri, 03 August 2012 08:35 |
mikeaudet
Messages: 477 Registered: February 2009 Location: Canada
|
Senior Member |
|
|
Well, this could take some time, but yes, I'd like to see that. I have to decompile the ensoniq written effects subsystem to assembly language and figure out how it works. Once I've got that done, I'll be in a position to write a new one in c++, and that's where things can get interesting.
Now, this is going to take some time. It's a big, big, ambitious project. Some might call it crazy. But, I really love PARIS, and I want to see it happen. I've already read a huge book on assembly language and tested some decompilers. It's started.
I always think long term with things.
Here are the steps - and they will take years. I guess step zero was the 64 bit scherzo.
1) ASIO driver - figure out how the voice engine works (done) and how we assign MEC modules (about to be done)
2) Fix the effects code - figure out how to build a VST host and how to assign effects to the EDS cards.
3) At this point, I'll know all I need to to write some kind of 64 bit PARIS software, be it all new code or written an an extension to an existing app.
That's what I'm thinking right now. But, I may change direction at some point. I'd also like to write a MIDI sequencer plugin for PARIS that would load in an effects slot and would be timed to the sample position. I may do that, or I may just get a new app going. There are so many possibilities. There's also always the faint hope that I'll get access to the PARIS source.
All the best!
Mike
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Re: PARIS ASIO/Scherzo64 Coming along very nicely! [message #107240 is a reply to message #107231] |
Sun, 26 August 2012 18:03 |
mikeaudet
Messages: 477 Registered: February 2009 Location: Canada
|
Senior Member |
|
|
Hi everyone,
I've been working of the C16 support. Reaper does not send feedback to a control surface without using a plugin. So, without a Reaper extension, there is no way to get the arrow lights to appear when the C16 is out of sync with the application.
So, I've been reading the Reaper API examples, and I'm going to write one that sends the needed feedback over a MIDI port. This way, the driver will work as envisioned on any other apps that send feedback, and Reaper will work, too.
Things are never as easy as I hope they will be, but we're making progress.
All the best,
Mike
|
|
|
Re: PARIS ASIO/Scherzo64 Coming along very nicely! [message #107248 is a reply to message #107240] |
Sat, 01 September 2012 17:14 |
Philip
Messages: 67 Registered: June 2009 Location: Utah
|
Member |
|
|
mikeaudet wrote on Sun, 26 August 2012 19:03 | Hi everyone,
I've been working of the C16 support. Reaper does not send feedback to a control surface without using a plugin. So, without a Reaper extension, there is no way to get the arrow lights to appear when the C16 is out of sync with the application.
So, I've been reading the Reaper API examples, and I'm going to write one that sends the needed feedback over a MIDI port. This way, the driver will work as envisioned on any other apps that send feedback, and Reaper will work, too.
Things are never as easy as I hope they will be, but we're making progress.
All the best,
Mike
|
This is insane. I am still lurking here. Using paris for my important projects and reaper when I am just tracking ideas for fun. So beyond Cool! Thanks for all your efforts Mike, and nice to see all the interest out there over this project. It seems like the interest in Paris is growing more now than I have seen since its hay day back in 1998-00.
Thanks to kerry too.
Rock!
-Phil
|
|
|
Re: PARIS ASIO/Scherzo64 Coming along very nicely! [message #107255 is a reply to message #107158] |
Thu, 06 September 2012 23:00 |
mattcelt
Messages: 31 Registered: July 2009
|
Member |
|
|
Hey Mike, had to chime in and add my thanks to the mix here. I cannot wait to send you a payment for a new driver.
I've been working with the Reaper actions a bit in the past couple of days, trying in vain to get my Griffin Powermate to work in Reaper the way the C16 jog wheel works in PARIS. So far, it's been a no-go. So your work with that is of real interest and relevance.
Forgive my ignorance, I hope I'm not stirring the pot unnecessarily here... but I was wondering, is MIDI really the best way to go for the C16's functionality? Would something like OSC (which Reaper already supports) or another protocol altogether be better? I don't have the technical know-how to reverse-engineer the RS-422 codes the board uses, so I don't know what the hardware supports, but I guess I'm worried about latency and that the density of codes one would need to process for a large-scale PARIS rig might overwhelm a MIDI channel. (Of course, I'm taking it as a given that the new ASIO driver would support multiple EDS/MEC/C16s...)
Also, completely off-topic... one of the main reasons I have never been able to get comfortable with another DAW is their user interfaces all look so damn flat. One of PARIS' best features (IMHO) is the very, very 3D look and feel of the system. Has anyone ever made a PARIS-lookalike theme for themselves in Reaper?
|
|
|
Re: PARIS ASIO/Scherzo64 Coming along very nicely! [message #107258 is a reply to message #107255] |
Fri, 07 September 2012 04:21 |
mikeaudet
Messages: 477 Registered: February 2009 Location: Canada
|
Senior Member |
|
|
Hi Matt,
You raise some good questions. The C16 uses a MIDI like protocol that has 10 bit values instead of 7 bit, as in the case of MIDI.
There is no danger of several C16s overwhelming a MIDI channel. It only sends data when a fader is moved or a button is pressed. The way I've set it up, each C16 sends the data over it's own midi channel. The first C16 sends data on channel 1, the second on channel 2, etc.
There might have been an argument to use the Reaper API instead of MIDI, but Reaper's API controls send and receive fader data as 7 bit values, just like MIDI. So, my thinking is that it's better to make something that will work with any audio app that supports MIDI control, since there's no advantage in Reaper to doing it using the API.
As for latency, I haven't noticed any at all. Keep in mind, it's MIDI, but it's all using internal "virtual" MIDI ports. There's no actual data going into and out of the computer.
Cheers!
Mike
|
|
|
|