The PARIS Forums - RDF feed
https://paris.kerrygalloway.com/index.php
ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=107792&th=15424#msg_107792
I am still using XP 32bit but the ASIO is much needed to work Paris hardware with Cubase 5...
Any update regarding the current status of your work if any progress ??
Thanks a lot for all that you do for Paris !!
Regards,
Dimitrios]]>Dimitrios2013-06-27T15:04:41-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=107810&th=15424#msg_107810
The ASIO project has been on hold while we moved and I get caught up on work. But, I'll be back at it in August.
Cheers!
Mike]]>mikeaudet2013-07-26T13:33:53-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108197&th=15424#msg_108197
What is the situation today with progress regarding asio driver ?]]>Exhale2014-05-09T15:27:52-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108198&th=15424#msg_108198
It's had a major re-write. I'm still debugging the changes. The next step will be more UI work for the control panel.
All the best,
Mike
]]>mikeaudet2014-05-09T16:41:52-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108200&th=15424#msg_108200
The reason the bug persisted (it actually manifested itself differently - it crashed my rewrite) is because there is virtually no documentation for how the code in the Paris Studio Control Library works. So, I've read the original ASIO driver and the code in the PSCL to try to understand the API. Bugs in the code are really tough because I then have to guess at how it is supposed to work.
It's fixed.
I'm getting an access violation when the buffer switch occurs, but that's my bug, and it's now making it pretty far into the process now.
I realized that I have to make some changes to my approach, too. The EDS1000 cards can only manage 24 streams of audio at once. In the PARIS app, that's okay because a track is either playing back or recording, never both at once. In an ASIO driver, the inputs and outputs exist separately. So, I'm going to have to put an option in the control panel for how to divide up the ins and outs, ie. 12 ins and 12 outs (which is what the original driver did) or 22 ins and 2 outs, or whatever.
That's where I'm at.
All the best,
Mike
]]>mikeaudet2014-05-10T14:44:21-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108201&th=15424#msg_108201
This is great news, if you can finish this soon I'll be back in PARIS full time. I'm doing everything I can right now not to buy one of the newer interfaces like the ID22 or Crimson.
If you need testing let me know. I use Live 9, Studio One V2.6 for production and Reaper 4 for Nebula.
]]>Will The Weirdo2014-05-10T15:41:54-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108204&th=15424#msg_108204
James]]>excelav2014-05-11T18:15:45-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108205&th=15424#msg_108205
If I can't do this, there will be an option in the control panel to divide up the streams however you want.
All the best,
Mike
]]>mikeaudet2014-05-11T18:19:56-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108207&th=15424#msg_108207
James]]>excelav2014-05-12T16:14:19-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108229&th=15424#msg_108229
It's passing 24 bit audio.
There's lots of work to do, but the new core finally works.
Cheers!
Mike
]]>mikeaudet2014-05-22T23:23:28-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108230&th=15424#msg_108230
kerryg2014-05-22T23:24:54-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108231&th=15424#msg_108231
Will The Weirdo2014-05-23T00:29:41-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108232&th=15424#msg_108232
mikeaudet2014-05-23T00:40:11-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108233&th=15424#msg_108233
It's going to be a million times easier to fix bugs add features now, too. It's just so tidy.
I'm totally exited about this!
]]>mikeaudet2014-05-23T00:46:41-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108234&th=15424#msg_108234
laurent2014-05-23T08:42:31-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108235&th=15424#msg_108235
It has been some ggod time not working with Paris but I would be very excited working Cubase with Paris hardware...
Thanks for still working with Paris !
Regards,
Dimitrios]]>Dimitrios2014-05-23T09:53:24-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108236&th=15424#msg_108236
mani11472014-05-23T13:06:09-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108237&th=15424#msg_108237
Now me, I look forward to the day I can use PARIS hardware in PT and all the other DAWs....
"DAW Wars II - PARIS Strikes Back"
]]>Will The Weirdo2014-05-23T13:51:50-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108238&th=15424#msg_108238
Even my debug build is now doing 180 samples. Even doing a control-alt-delete and starting the task manager just made a couple of small clicks and then the stream recovered.
Too cool!
]]>mikeaudet2014-05-23T15:46:36-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108254&th=15424#msg_108254
any idea of when you'll have a usable version ?
will we be able to use the expansion cards too ? adat 8in 8out...
am thinking of either waiting for your final driver, or purchase a computer only to re use the 32 bits version and paris 3.0.
would love to have all the hardware on 1 pc only.
thanks !]]>portscan2014-06-03T13:28:55-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108257&th=15424#msg_108257
As for timelines, I have no idea. I get closer every time I work on it, but time is tight. I'll do my best to get it out as soon as possible.
All the best!
Mike]]>mikeaudet2014-06-03T18:11:13-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108292&th=15424#msg_108292
did rebuild my studio and it is ready now .
Still works the asio driver now ?
Where can i buy it ?
I like to run Paris Hardware under Cubase 4 & 5 on one system.
It is very interisting, cause a college use Cubase and a good old Paris too.
Best regards
Dan]]>danielcornelius2014-07-06T15:35:29-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108297&th=15424#msg_108297
I've been working really hard on this.
I just tracked down a bug that must have existed in the original version. It involves the deleting of sound buffers before the EDS cards are done with them. I'm going to have to do some re-factoring to fix it. I've been banging my head against the wall for most off the last week trying to track it down.
This is where I am with the project:
What's done:
I've refactored the driver so that one can assign I/O channels to up to 24 audio streams per card(that's all an EDS1000 card supports). The streams can be either inputs or outputs. The selections are currently loaded from the registry.
I've got the driver able to select any MEC expansion card for each of the two in and out banks per MEC. The selections are loaded from the registry. Just to be clear, 8 in cards, 8 out cards, and ADAT cards are all supported.
The driver loads the buffer size and sample depth from the registry.
The driver plays back and records 24 bits.
The driver can be closed and opened by the host app without resetting the hardware (resetting just took too long).
What's left to do:
Fix the buffer bug I just found.
Finish the control panel so that the settings that are currently loaded from the registry can also be accessed from via a user interface.
Deal with a few more items relating to the C16. I haven't assigned some of the knobs to MIDI notes yet.
We're getting closer. I'll get it done as fast I can while still making sure it's done well.
All the best!
Mike
]]>mikeaudet2014-07-07T14:02:23-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108299&th=15424#msg_108299
I just want to make sure I understand what you said above. Can you access more than 2 I/O cards in a MEC at a time? With the ASIO driver would you be able to have 24 input via 3 of the 8 input cards at 24bit with one EDS card and one MEC? Or 24 input via 3 adat cards with one EDS 1000 card and one MEC? If not now, would it be possible in a multi MEC/EDS system in the future?
Thanks
James]]>excelav2014-07-07T15:25:26-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108300&th=15424#msg_108300
unfortunately, there are a fixed number of physical lines (I2S) that connect the IO modules to the EDS card. You can have two input banks and two output banks plus the I/O built into the MEC.
Sorry!
Mike]]>mikeaudet2014-07-07T15:38:38-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108301&th=15424#msg_108301
That's okay, that's the way it has always been. I was just wondering if the ASIO driver could change that.
Thanks
James]]>excelav2014-07-07T15:52:23-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108376&th=15424#msg_108376
I am very curious ! Do you have any news to share?
Best Regards
Lasse]]>anfallszonen2014-09-01T21:58:41-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108378&th=15424#msg_108378
I have the GUI to finish, which I will be able to work on next week when my daughter starts kindergarten. There is a bug on a beta tester's system to track down that I haven't personally been able to reproduce yet. It's almost done.
All the best,
Mike ]]>mikeaudet2014-09-01T23:42:13-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108382&th=15424#msg_108382
Looking forward to the releaseparty!
Best Regards
Lasse]]>anfallszonen2014-09-02T19:18:01-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108384&th=15424#msg_108384
Many thanks Mike .]]>Dcbite2014-09-03T09:05:02-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108385&th=15424#msg_108385
Richard Kelley2014-09-03T16:06:28-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108425&th=15424#msg_108425
any new update or news to share on how everything is going with the ASIO Driver???
Can't wait!!]]>Studio1112014-10-08T00:26:42-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108426&th=15424#msg_108426
A lot has been happening, but never as much as I wish was happening.
I've been working with a couple of beta testers who have been very generous with their time in helping me track down bugs. Together, we have found and fixed a bunch of them.
I also had a breakthrough last week and re-wrote a major section of how the driver works. The original ASIO driver would schedule what's called a voice event at every buffer switch. This scheduling takes time and had a bad habit of falling behind. I found a way to schedule three voice events at the start of playback, and two of them just point to each other in a loop. This has improved the performance and reliability of the driver immensely.
So far, we've got the ASIO driver working in Reaper, Adobe Audition 3, the ASIO plugin for Windows Media Player, Sony Sound Forge and Sony ACID Pro 7.
I bought a copy of Harrison Mixbus last week trying to figure out why it doesn't work in that app yet. I'm still working on a fix.
I've also ordered a copy of Pro Tools 10/11 because I have reports that the driver doesn't currently work in Pro Tools 10. It hurts a little playing Avid and Pace money again, but it's for the greater good. The driver will not initially work with 64 bit hosts, so Pro Tools 11 will be a future target, after I re-write the PSCL and integrate it into kernel mode. That's a few years away. But, I'm planning to fix whatever is keeping the driver from working with Pro Tools 10.
I've done some work on the control panel, but most of the effort has been directed to fixing bugs and improving performance/compatibility.
I have a couple of other PARIS things that I'm planning on that I'm not ready to talk about yet in case they don't work out. Rest assured, though, that things are happening.
Thanks so much for being patient. It really is harder getting things done with a growing family. I'm also taking a linear algebra course right now hoping to get my math skills up to better understand the effects algorithms. It's been much more time consuming than I expected, but I'm learning a lot.
There's a lot going on!
All the best,
Mike
]]>mikeaudet2014-10-08T00:45:57-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108427&th=15424#msg_108427
Looking forward to many more years of using Paris
Don]]>Studio1112014-10-08T00:52:27-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108428&th=15424#msg_108428
mikeaudet2014-10-08T01:09:13-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108429&th=15424#msg_108429
don t forget to sleep
laurent]]>laurent2014-10-08T22:09:17-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108431&th=15424#msg_108431
I did, actually, stay up last night working on the driver. The coffee is extra good this morning!
Currently, the PARIS ASIO driver works with Pro Tool 10.3 in 16 bit mode, but not 24 bit mode. I have an idea of how to change things that might make it work in 24 bit mode, too. It all depends on how the firmware in the EDS cards works, and I have no control over that, unfortunately.
I'll post in a few days after I can make changes as to whether it worked.
All the best,
Mike]]>mikeaudet2014-10-11T14:40:13-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108432&th=15424#msg_108432
you are the paris driver
you are in all eds 1000 cards
thank s
laurent]]>laurent2014-10-11T14:54:22-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108437&th=15424#msg_108437
I just played and recorded 24 bit audio in Pro Tools 10.39 through my MEC.
I had to redesign/rewrite the way buffers are handled in the driver to do it, but its working here. Hopefully, there will be no weird system dependent bugs to track down.
I can hardly believe it.
All the best!
Mike
]]>mikeaudet2014-10-23T02:14:49-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108438&th=15424#msg_108438
Studio1112014-10-23T02:19:24-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108439&th=15424#msg_108439
This sounds very promising, even though I'd be happy with just 16 bit.
I still love the Paris software, but it is very picky with some plugins, which can crash Paris. I am using WIN7 64bit, but these issues existed with XP 32bit as well.
Looking forward to trying the ASIO driver with my next favourite DAW, Samplitude. (Native inserts on submixes would be joyous!!)
I'd stick with the Paris software if I could even do something as simple as strapping an external compressor, or even better a native plugin, on one EDS submix, (not just the global mix..)but alas this is a hard wired limitation.
Keep us posted.
Kim
]]>Kim W.2014-10-26T07:15:33-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108440&th=15424#msg_108440
I'm working really, really hard on this driver. Pro Tools is giving me the gears. I have it working, but there are stability issues when changing buffer sizes. It's driving me crazy trying to track the cause down. It works perfectly everywhere else, except for Harris Mixbus, which is a whole other adventure to be had.
But, I'll get it. I won't give up until this bug is dead.
All the best!
Mike]]>mikeaudet2014-10-26T13:25:26-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108442&th=15424#msg_108442
I just wanted to give an update. Getting the PARIS hardware to work with Pro Tools 10 reliably has been really challenging, and I'm still working on it.
I had to re-write the buffering engine to work at all because even though the ASIO spec has a mechanism for asking the driver what it's buffer sizes are, Pro Tools only allows 64/128/256/512 etc. The PARIS hardware requires buffer sizes that are a multiple of 10 for 24 bit transfers. So, I had to change things quite a bit to get it working.
The next two hurdles were because of bugs I created. Those bugs are my fault, but Pro Tools closes as soon as it detects a debugger attaching to its process. This is probably done to make it harder to crack the PACE copy protection. In my case, it just makes it harder for me to fix things.
I had a bug that didn't manifest in other hosts because they always initialized the buffers in the order the driver presented them to the app. Pro Tools changes the order, and that reveled a mistake I had made. It lead to not being able to record audio in Pro Tools. It's fixed.
The second bug I've been trying to track down is a crash that sometimes happens when the buffer size is changed. It seems to happen more when the buffers are at 128 samples, but I've seen it at higher buffer sizes, too. Because I can't use a debugger and the problem hasn't manifested in other apps, this has been really, really hard to track down. I've literally spent days and days coming up with new theories and trying to prove or disprove them. I think I've finally found the problem, and I hope to have it fixed in about a week.
As long as the buffer sizes are not changed, Pro Tools works perfectly right now. So, we're not too far away.
I'll post when I finally have this resolved.
I just wanted to let you guys know what is happening, and that I'm still working really hard on this.
I have to give an extra special thanks to the beta testers who have helped us get to this point. You guys rock!
All the best!
Mike
]]>mikeaudet2014-10-28T14:46:17-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108443&th=15424#msg_108443
]]>Dcbite2014-10-28T15:55:40-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108461&th=15424#msg_108461
Another update:
The good:
I've replaced the timer code and I'm getting 64 sample buffer sizes in Reaper with 12 inputs and 10 outputs working reliably. I am so excited bout that!
Also,I found out why I couldn't get as small buffer sizes in Pro Tools, and I've fixed it. I'm now getting 128 samples buffer size reliably in Pro Tools 10. 64 seems to be too small for that app. I still have to do a bit of testing to see if MIDI timing in Pro Tools is affected by what I've done, but I think it will be fine.
To do:
For some reason at the newer smaller buffer sizes I can now get, playback is garbled for the first playback. If I reset the driver, it's perfect from then on. I'm not sure if the sample position that is reported by the hardware is inaccurate when the MEC is still finishing its initialization, or if something in the PSCL is creating a race condition, or something else I haven't thought of. I'm working on it.
All the best!
Mike
]]>mikeaudet2014-11-15T13:17:32-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108462&th=15424#msg_108462
Sounds like you are making great progress, can't wait to try it out.]]>Will The Weirdo2014-11-16T13:57:51-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108464&th=15424#msg_108464
I think I found the bug I've been chasing. I discovered last night that the top 8 bits of project time are filled in by a helper thread in the PSCL, while the other 24 bits are read directly off the card. I think what has been happening is that I schedule the buffers before this thread is running, so I'm setting some things based on 24 good bits and 8 bits of garbage. If I stop the ASIO driver, the PSCL keeps running, so the helper thread is already running on the second attempt, and this second try always works.
I'm going to have to rewrite a bunch of stuff in the PSCL, but I should have this fixed by the weekend.
The Pro Tools problem was caused by something called dynamic priority boost in Windows. It boosts a thread's priority if it was waiting on an I/O operation or is involved in mouse input to the main window. This was causing mundane threads to preempt my timing loop and causing under-runs. I turned it off, and things worked so much better. I'm pretty sure reaper turns this off itself, which is why everything worked so well under reaper before.
All the best!
Mike
]]>mikeaudet2014-11-17T16:54:08-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108465&th=15424#msg_108465
Things just keep getting better and better because of all your hard work!
Don]]>Studio1112014-11-17T17:15:59-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108467&th=15424#msg_108467
Keep up the awesome work and keep us posted on your progress.
Rob]]>mani11472014-11-17T18:34:13-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108471&th=15424#msg_108471
Does this also work for output cards / external effects processing from within PARIS?
Any chance for a beta / preview? Interested even if I have to pay up... ]]>casshern2014-11-23T04:27:43-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108472&th=15424#msg_108472
The completely separate Reaper PAF import functionality mentioned above, written for us by a Reaper contributor, is pretty much flawless within its limitations - because it depends on libsndfile, our main library for PAF's compatibility with the outside world, it's hampered by a lingering bug in libsndfile that makes gibberish out of 24-bit files generated by the Mac version of PARIS only, but all PC-PARIS generated PAFS should import as easily as you'd import a wav.
Strongly doubt there will be any ability to access PARIS effects, but it may be possible one day! Fully accessing I/O cards though, I would imagine yes, since that's always been a core goal.
As far as paying up - this is all entirely new work by Mike, and even if every existing PARIS user chucked in a far bigger chunk than what I suspect he'll ask it would pay him pennies per hour for this labour of love, so I will be first in line with my cash in hand asking why I can't pay more!
]]>kerryg2014-11-23T04:40:33-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108473&th=15424#msg_108473
I use the Reaper PAF extension all the time these days, as PARIS is my core A/D source. Recording nearly daily. I just love the functionality and sound. ASIO drivers bring amazing news to the table for people like myself.]]>casshern2014-11-23T04:54:14-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108474&th=15424#msg_108474
I'm so excited about this, too!
I've been working as hard as I can on this. I was hoping to avoid making too many changes to the PSCL because it then has to be tested to make sure it didn't break the PARIS app, but I'm going to have to make a bunch of changes. The kind of locking the PSCL uses to guard shared resources are too slow for the kind of buffer sizes I'm targeting. So, they have to be replaced. I'm also working on a new way to read project time and start and stop playback.
A big thing I'm working on now is getting the voice events that point at themselves to be reliable. The problem is that there is no way to tell them when to start playing/recording. They start the instant the EDS card is told about them. I may have to go back to scheduling voice events on the fly, but that 's a bit messy now that Pro Tools has required a circular buffer that doesn't line up with the buffer switches. It also adds more overhead to the buffer switches, which could affect how low we can get the buffer sizes.
We're getting there. It's just been harder than I thought it would be.
All the best,
Mike]]>mikeaudet2014-11-23T12:53:04-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108475&th=15424#msg_108475
Will The Weirdo2014-11-23T14:10:53-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108476&th=15424#msg_108476
I actually don't want to criticize ID over this. There is a lot of good stuff in their work that I'm learning from. I don't think Ensoniq really had the money they needed to get this done right. We can certainly criticize ID over how they have handled the PACE thing, though.
I think just had a breakthrough - maybe there is a way to get these immediate buffers time aligned. I just loaded up a pro tools session at 128 samples, and it played back properly the first time, twice in a row. I'll have to do a bunch more tests to make sure all is well, but it's worked twice, and those are the only times it's ever worked.
I still have to fix the locking, and I have to make changes to the helper thread in the PSCL. It runs every 256 samples and does a bunch of housekeeping. But it touches resources my timer thread needs, and there is no time for contention at 64 sample buffer sizes. I'll need to make changes so that a special version runs when the ASIO thread attaches,
This is going to be so cool!
All the best!
Mike
]]>mikeaudet2014-11-23T14:29:16-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108477&th=15424#msg_108477
Sweeeet!
Mike]]>mikeaudet2014-11-23T16:11:06-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108478&th=15424#msg_108478
Unbelievable work by Mike.
Thank you Mike!!
Don]]>Studio1112014-11-23T17:29:02-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108479&th=15424#msg_108479
Will The Weirdo2014-11-24T03:46:47-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108480&th=15424#msg_108480
There is code to detect this kind of thing in the PSCL. I was hoping it was a leftover from an earlier firmware or simply covering for other mistakes in the PSCL. Keep in mind, the PSCL is huge, and the whole thing is built around the assumption that the time is checked every 256 samples. This was the first time I tried to bypass the code there to check the project time directly.
This issue was easier to deal with in the PARIS app, when the sample event fired every 256 samples (an IRQ fires every 256 samples), and the buffers were 3000 samples long. If the project time reported by the EDS card looked crazy, just report 256 samples more than the last time. It will be close enough. That isn't good enough at 64 sample buffer sizes.
I'm going to have to do a bunch of profiling to see exactly how this goes wrong and for how long. Then, I can interpolate by using the windows high resolution timer.
What a mess.
Just keeping everyone in the loop.
All the best,
Mike
]]>mikeaudet2014-11-25T19:20:25-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108481&th=15424#msg_108481
Will The Weirdo2014-11-25T20:54:35-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108482&th=15424#msg_108482
eds transfert = --,-- ??
le pere noel est bientot la
super mike
laurent]]>laurent2014-11-25T22:58:46-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108483&th=15424#msg_108483
That firmware issue seems a really annoying one to have to deal with...hope you manage to find an elegant solution.
Anyway, like everyone else reading this thread - very excited about the new developments - way to go!]]>justcosmic2014-11-25T23:01:11-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108484&th=15424#msg_108484
So far so good.
I'll keep you guys posted.
Mike
]]>mikeaudet2014-11-25T23:53:00-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108485&th=15424#msg_108485
Also, small question re your planned implementation of Control 16 in the Asio driver:
Will it likely work with more than one C16 for those with multiple EDS cards or is it more likely that it will only work with one at a time?
Reason I ask is that I may sell off one.
]]>justcosmic2014-11-26T01:12:59-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108486&th=15424#msg_108486
I sure hope so I've got it solved. I don't have access to the microcode on the card, so I have to do a lot of guessing. It's possible that it was something else causing the glitches. I really hope I didn't malign whoever wrote that code or mislead you guys. But, the glitches seem to have aligned with when the top 8 bits changed, and there is all kinds of stuff in the PSCL that seems to imply others thought this was happening. I hope I got it right and its fixed. I've been running my 27 track Pro Tools session for the better part of tonight at 64 samples, and it's been solid. I'm not doing anything to interpolate the first 24 bits yet. I'm just reading them. I'm adding one to a counter that acts as the top 8 bits every time the first 24 bits end up significantly smaller than the last check, which means they have wrapped. That happens every 5 or 6 minutes. This works because it is very unlikely we will have no buffer switch for 6 minutes. So far, so good.
As for the c16s, that's a great question! I don't think I had been planning to support more than one, but I just took a look, and the PSCL does send the card number with the callback. So, I'll try to use that to support more than one. I have a few around here to test with, too. I just only use one to save desk space.
All the best!
Mike
]]>mikeaudet2014-11-26T01:41:54-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108487&th=15424#msg_108487
Yes let's hope - it could be a great Christmas for Paris users !
Yes like you I nearly never get more than 1 C16 out for the exact same reason - so maybe I'll let one go anyway, we'll see - but good to know that there's potential for 32 faders anyway!
Thanks again for all the hard work.
]]>justcosmic2014-11-26T01:53:38-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108489&th=15424#msg_108489
Please excuse my ignorance.
Are you suggesting that your asio driver would somehow incorporate c-16 functionality into a completely different DAW app?
If so, how? Would the Paris app have to be open in the background?
I'm excited about the prospect of using the c-16 (preferably two) with Magix Samplitude, which is my other DAW of choice.
Am I dreaming??
Regardless, I will be first on the purchase list of the driver when it hits "prime time".
]]>Kim W.2014-11-29T08:12:03-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108492&th=15424#msg_108492
The new driver takes the C16 input and converts it to MIDI sent out any port you select. There's no need to have the PARIS app open in the background. I've used it to control Reaper, but I haven;t tried it yet with anything else. Getting the core of the driver right while working with Pro Tools at 24 bit has been a struggle. I think I've got it working. Right now, I'm working on dealing with what happens when the 32 bit value that is the basis for project time rolls over to 0 again. It takes around 16 hours, but it happens, and the audio stops. I'm trying to fix it.
All the best,
Mike]]>mikeaudet2014-12-01T19:53:56-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108493&th=15424#msg_108493
I'm adding a new topic on Virtual Via and I'd like to get your take on it.
Wayne]]>Wayne2014-12-01T21:36:42-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108504&th=15424#msg_108504
any chance to sse a wdm 64 bits version ?
would be great to use with asio4all then
i dream of having both my raydat and paris in the same daw.]]>portscan2014-12-10T15:10:48-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108774&th=15424#msg_108774
casshern2015-05-28T20:43:01-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108775&th=15424#msg_108775
Will The Weirdo2015-05-29T19:16:17-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108776&th=15424#msg_108776
I seem to remember a while back you were talking about doing it in stages as it's a HUUUUGE undertaking
Either way, very much looking forward to continuing on with all that makes Paris great...also quite curious about Paris 3.2...
All in all, exciting times ahead in Paris world ]]>justcosmic2015-06-04T00:32:01-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108777&th=15424#msg_108777
Will The Weirdo2015-06-04T00:40:02-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108778&th=15424#msg_108778
All the best,
Mike]]>mikeaudet2015-06-04T10:00:16-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108779&th=15424#msg_108779
justcosmic2015-06-04T11:35:07-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=108780&th=15424#msg_108780
You said ( wrote) something about Paris 3.2 ?????? What is that supposed to be ?
I am still using Paris on XP so if you need any beta tester let me know.
Thanks again my friend for all your efforts!]]>Dimitrios2015-06-04T16:55:04-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=109093&th=15424#msg_109093
I'm sure the PARIS world is waiting for this baby!
So Mike...... what's your plan?]]>Will The Weirdo2016-03-03T22:04:13-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=109095&th=15424#msg_109095
I was getting a fair bit of time in, and then we all got a cold, and I've had two sick kids at home to look after.
I've got the MEC control panel done. I just have to test the +4/-10 controls. It's hard to check that from remote desktop on a laptop in the car with PARIS running in the house.
Last week, I discovered a bug that I though was squashed wasn't. After finishing the MEC control panel, I started testing all sorts of settings, and With 24 streams of audio, I'm getting occasional audio distortion at 64 samples. By streams I mean 24 I/O ports in use transferring audio on my MEC and 442. I took a look through the voice engine code, and I think I've figured out why.
The core of the voice engine that runs on the EDS card is something called the "big loop." It runs every 64 samples. It does all the memory transfers, and then it checks for new streams to add.
I think the work involved in setting up the 24 streams is delaying the loop by a few samples, and it just carries on at that point, every 64 samples, but slightly late. That puts it slightly out of sync with the main loop in the asio driver.
That's my theory, anyway.
So, I've been working on it. I've almost finished a function to change the frequency of the IRQ firing on the cards. Since the big loop fires the IRQ every 4th loop through the big loop, the IRQ is always in sync with the big loop. I think I've figured out how to make it fire every 64 samples instead of every 256. I can then run the ASIO loop from that.
Other than that, I've just got to do a simple dialog for the 442, and make a couple of additions to the C16 code. There are a couple of knobs I haven't wired in, but it's pretty simple stuff.
That's the latest! I'll get it out the second it's done and working perfectly.
I'm starting to think ahead to the next steps. I'm thinking of attacking the PSCL to port it to 64 bits so we can get a 64 bit ASIO. I'm also thinking about the Mac a lot, given the state of Windows. Reworking the PSCL would make it easier to port it to a new OS.
All the best,
Mike
]]>mikeaudet2016-03-03T23:05:00-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=109096&th=15424#msg_109096
Studio1112016-03-03T23:32:04-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=109097&th=15424#msg_109097
Your updates are inspiring to many of us and your work is one of the reasons I'm rebuilding my PARIS rig, on it's own computer.... I'm searching for parts, planning a PARIS re-evolution in my setup.]]>Will The Weirdo2016-03-03T23:40:58-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=109100&th=15424#msg_109100
Not too many people would take on such an endeavor
You are the man!]]>dnafe2016-03-04T10:14:22-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=109101&th=15424#msg_109101
Will The Weirdo2016-03-04T13:39:19-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=109102&th=15424#msg_109102
I'm glad that I've made a contribution, but I'm definitely not an environmental hero, as much as I would like to be.
I've been working on the ASIO driver for the last six months from my 2008 Dodge Caravan while my son has his naps. I have to idle the engine the whole time, partly to keep from freezing (this is Canadian winter) but mostly because if I turn off the car, my son wakes up. The car is the only way I can get him to sleep.
I am completely sick of buying things only to throw them out. But to some degree, I keep doing it. To throw out PARIS hardware takes things too far. Keep in mind that I was burnt by Digidesign on the Session 8, and it wasn't going to happen twice if I could help it.
I bought an Energy Star home, but rather than being an environmental triumph, it left me with no respect at all for the Energy Star program. You should feel the draft that comes through my 2013 Energy Star windows. Natural Resources Canada wouldn't even come out to check them, much less do anything about it.
I have a compost bin, but I don't use it in the winter because it's too cold out. I go outside as little as possible in the winter. I do recycle as much as I can.
I would love to be an environmental hero, and I hope that with the PARIS work, I've helped make up a little for the rest of my life!
All the best,
Mike
]]>mikeaudet2016-03-04T20:06:06-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=109105&th=15424#msg_109105
Have you tried playing white noise to help your son sleep?]]>dnafe2016-03-05T11:18:19-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=109106&th=15424#msg_109106
To sleep, I need white noise. In summer I use a pedestal fan, and in winter I use an FM radio tuned off station.
I cannot sleep without some sort of constant wideband noise. It also helps mask external noises in the middle of the night, which wake me up. (My dogs snoring, possums running on the roof, cocks with loud exhausts etc....)
]]>Kim W.2016-03-05T12:54:35-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=109107&th=15424#msg_109107
I've been working on the ASIO a lot. I've got the main timing loop synchronized with the "big loop" in the EDS firmware. I have to rethink how I handle resynch requests because of missed samples now. I can't just pick any sample position and go anymore. It's tricky because I had to use a larger, circular buffer for the EDS side that is a multiple of ten and two regular buffers for the ASIO side that are powers of two so that Pro Tools could do 24 bit. If Avid could follow the ASIO standard, this would have been done a year ago.
I'll keep you guys posted. This kind of bug is hard because I'm at a play place with my daughter working on the driver from a lap top using remote desktop. I can't hear the output to see if I've fixed anything.
But, I'll check it tonight.
All the best!
Mike]]>mikeaudet2016-03-06T16:44:24-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=109123&th=15424#msg_109123
I just finished the 442 control panel, which, unless I'm forgetting something, makes the driver now feature complete.
I have a bunch of testing to do for the MEC and 442 control panels (because I can't test everything in the car), and I think I can get the ASIO buffer switches timed from the EDS1000 IRQ, which will reduce CPU overhead at lower buffer sizes.
We're very close.
All the best!
Mike
]]>mikeaudet2016-03-30T22:21:17-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=109125&th=15424#msg_109125
Alright that sounds Great to me ! Except I have to admit I am not really sure exactly what that all means. I just appreciate everything done to keep Paris alive and improving. I haven't been recording much lately, I have been doing quite a bit of playing out, but when this new driver is ready to go I will try it. When the driver is ready to try, I would be willing to test drive it a bit, as long as my brain will now how to revert if things to scary. Keep up the GREAT work and keep me in touch, Rich P.S. this is a pix of my new puppy Caesar, I lost my Buddy Samson March 1st. ]]>Richard Kelley2016-03-30T23:23:28-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=109126&th=15424#msg_109126
Thanks!]]>Studio1112016-03-30T23:40:40-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=109127&th=15424#msg_109127
Will The Weirdo2016-03-31T01:23:07-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=109128&th=15424#msg_109128
harry epstein2016-03-31T04:41:26-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=109131&th=15424#msg_109131
imajon2016-04-03T22:07:24-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=109145&th=15424#msg_109145
I have a question and an update.
My question: does anyone know how accurate the Centrance ASIO latency utility is? I just ran it on the PARIS ASIO driver, and it reported 1.45 ms round trip latency. Is this in addition to the 1.45 ms (times two) from the buffers? I've included a screen shot. I hope this is true!
My update: I'm working on OSC support for the C16. I've made further improvements on efficiency since getting the main timing loop driven by the IRQ on the EDS card. I'm down to 3.5% CPU usage with dozens of tracks at 64 sample buffers.
OSC is going to be harder than MIDI because I have to manually map every single control. But, I'm on it. I'm targeting Reaper.
I've also got the ASIO driver loading as Windows MIDI driver to pass data for the C16. I'm not sure if it will just pass simple MIDI control messages or something more. I'm leaning towards some kind or partial HUI compatibility so it can be used in Pro Tools 10.
All the best!
Mike]]>mikeaudet2016-04-25T15:35:46-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=109146&th=15424#msg_109146
Will The Weirdo2016-04-25T21:43:36-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=109155&th=15424#msg_109155
I just sent the first OSC messages from the C16!
The faders are working going from the c16 to Reaper. The next step is getting updates back from Reaper and turning on the up and down LEDs.
If anyone has any requests for how to map the many buttons and knobs on the C16 to Reaper, I could use the help. For example, what should I do with the Monitor Level knob? There is no equivalent in Reaper that I know of.
I'm trying to keep the C16 working in Reaper the same way it does in PARIS. For example, I'm working on having the Channel control knobs and buttons work the same way. I'm also coding to have the mute buttons become solo buttons when the solo button is pressed.
But, what do I do with the data, shuttle, and jog buttons? There are a whole bunch that I'm unsure of.
All the best!
Mike
]]>mikeaudet2016-04-30T00:21:02-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=109157&th=15424#msg_109157
The jog shuttle wheel would be awesome mapped to similar jog/scrub functionality in Reaper and there are assignable actions for it but it's pre-mapped to something called MultiRotate which I can't find any documentation on. Any idea what that is?
]]>kerryg2016-04-30T17:23:23-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=109159&th=15424#msg_109159
It's working well. I've now got Reaper sending back messages and turning on the C16 arrow lights. I have a lot of work to do yet, but the basic building blocks are there.
I'm able to make very slight adjustments to the fader positions. The full 1024 values are definitely being sent.
The only down side is that it is a lot harder to work with than MIDI. I have to parse a bunch of strings in the callback. But, it's going to work.
All the best!
Mike
]]>mikeaudet2016-04-30T21:38:03-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=109160&th=15424#msg_109160
So is this going to be working with reaper with paris in the background?
What's the timeline more or less?
It sounds great. Really great actually. ]]>n0samples2016-05-02T00:57:14-00:00Re: ASIO DRIVER current status ?
https://paris.kerrygalloway.com/index.phpindex.php?t=rview&goto=109161&th=15424#msg_109161
kerryg2016-05-03T01:14:32-00:00