Mon 08 Nov 2010 09:58:07 AM UTC, comment #18:
Marking this bug as fixed, the next stable Traverso release now properly supports portaudio and it's available drivers!
Thanks for all the feedback!
Remon
|
Sat 30 Oct 2010 09:59:16 PM UTC, comment #17:
I've compiled the Traverso git version, and created an installer whic can be downloaded here: http://traverso-daw.org/download/binaries/next/windows/
Please test if the different driver options (mme, direct sound and asio) work as expected, or if something is missing in the device selection dropdown boxes.
It's a first version, it needs improvement, for example, the sample rates that are supported by the device and showing the default device if none was selected before.
Note that the development version has known bugs, but we still like feedback on the windows installer, if Traverso runs fine, plays/records.
Rendering (export) is broken atm.
|
Sat 21 Aug 2010 03:20:06 PM UTC, comment #16:
Hello Peter,
Do I understand it correctly that you have a working compilation environment on Windows to compile Traverso on ?
In that case, I would love to work on the current git version so that it'll work with the portaudio dll you found.
I would suggest to join irc channel #traverso on freenode so we can discuss this directly if you want too!
Thanks for your input, much appreciated!
/me looks to get portaudio working in git again :)
Remon
|
Sat 21 Aug 2010 01:35:00 PM UTC, comment #15:
sorry .. correct:
if (hostapi == "asio" && inf->type == paAsio ) {
|
Sat 21 Aug 2010 01:34:09 PM UTC, comment #14:
Hello Remon,
today I looked into traverso-0.49.2.tar.gz
PADriver.cpp / int PADriver::setup(..) (line 111)
There's no code allowing PortAudio.dll
to initialize with ASIO, .. as for example should be :
if (hostapi == "asio" && inf->type == paDirectSound ) {
...
}
.. so even if the DLL does support ASIO,
Traverso does not allow to use it.
Cheers,
Peter
|
Fri 20 Aug 2010 08:38:17 AM UTC, comment #13:
Hello Remon,
in the Linrad project http://www.sm5bsz.com/linuxdsp/linrad.htm I found another precompiled DLL (has a different name but I renamed it to PortAudio.dll successfully, working). (Please see screenshot)
It successfully opens the ASIOFORALL driver and I hope it will then also run with my Alesis device which will be the next thing to test ..
I also tested this DLL with Traverso Windows, but Traverso still says "PADriver: hostapi asio was not found by Portaudio!"
So this is a bug or just Unimplemented in the Windows version of Traverso. Would be nice to make Traverso Windows work with ASIO.
Cheers, Peter
(file #21263)
|
Thu 19 Aug 2010 08:35:00 AM UTC, comment #12:
Hello Remon,
yesterday I have copied the PortAudio DLL build 1899
into the TRAVERSO folder and Traverso still works.
So the DLL interface seems to be - in general - compatible
to that of the DLL delivered with TRAVERSO (Windows).
With FPC wrapper files I tested this "build 1899"
portaudio DLL under LAZARUS and it successfully
reports the ASIO driver on my PC.
(It's the ASIOFORALL "bridge" driver).
But TRAVERSO says (after selecting ASIO in settings):
"PADriver: hostapi asio was not found by Portaudio!"
I checked Audacity, and the Portable Version does
also not recognize the ASIOFORALL driver. (It also uses
Portaudio in it's sources, probably without ASIO ?)
On the other side Steinberg Wavelab, Nuendo and
DarkwaveStudio do see the ASIO driver and do work with it.
What is left to test is creating a example program
which opens the ASIOFORALL driver and plays some audio
so I can seriously say that this Portaudio.dll
really works correctly - and Traverso does not ?
Thanks,
Peter
(file #21255)
|
Mon 16 Aug 2010 03:16:19 PM UTC, comment #11:
Hello Remon,
does TRAVERSO probably work with this DLL:
PortAudio precompiled Win32 binary v0.19 build 1899 with MME DS and ASIO on http://code.google.com/p/portaudiosharp/
or does TRAVERSO expect another V0.xx of Portaudio ?
(I ask because of the ASIO support under Windows ..)
Thanks,
Peter
|
Sat 22 May 2010 10:13:01 PM UTC, comment #10:
Hm, yes, possibly Jack2 would be a temporary workaround.
But what's about this:
PortAudio precompiled Win32 binary (v0.19 build 1899 with MME, DS and ASIO)
http://code.google.com/p/portaudiosharp/downloads/detail?name=PortAudio.dll&can=2&q=
Probably this is only a source of inspiration because
it requires .NET 2.0 - and I don't like
having NET on my PC. NET looks to me it's
the next useless overhead on my PC !
Okay, I would also expect that compiling portaudio.dll
with ASIO support requires more work to be done
on the Windows version of Traverso.
So thanks up to now and I look forward to hearing from you.
And Jack.
Cheers,
Peter
|
Sat 22 May 2010 11:40:15 AM UTC, comment #9:
OK, that's great news!
So now compile Traverso git with jack support on Windows, set it's driver to jack, connect Traverso's master out via qjackctl to your hardware output ports and voila :D
Seriously, if jack2 works on windows, and getting the windows build to also build with jack support requires far less work to have asio support for Traverso on the short term!
Thanks for testing this out!
|
Sat 22 May 2010 11:31:13 AM UTC, comment #8:
Hello Remon,
I'm now member here, probably makes things easier ..
Cheers,
Peter
|
Sat 22 May 2010 11:23:09 AM UTC, comment #7:
Hello Remon,
today I installed the binary of Jack-1.9.5 on my notebook
and I append a screenshot of which Audio Devices Jack detects.
I suggest TRAVERSO behaves as follows under Windows:
- MME = Standard Device (which can be selected in the Windows System Settings)
=> so there's a dropdown menu missing where I can select a specific MME Driver / Device
- DirectX = does not work atm
- ASIO = does not work atm
For users this is a time consuming trap that ASIO and DirectX are selectable - but do not work. The connection error is not shown as a MessageBox but only in the bottom line, and this only for a very short time .. :-(
Unfortunately I was not able to find out how to connect TRAVERSO or other applications with Jack .. But You can see that Jack does recognize the Alesis Device with PortAudio selected.
Cheers,
Peter
(file #20585)
|
Fri 21 May 2010 10:34:07 PM UTC, comment #6:
Hello Peter,
Hehe, it's later here too, about 12:30 ... I think we're in the same time zone.
It's indeed not about usability but to test if we can make Traverso work with asio right now, using jack as it's driver. (note that the current windows executable does not have jack driver support build in)
So if jack2 works, we have a good starting point to have the next version of Traverso have asio support on Windows :)
Remon
|
Fri 21 May 2010 10:25:28 PM UTC, comment #5:
Remon,
sorry, this time I write Your name correctly.
On this side of the earth it's after midnight now.
So I will test Jack2 tomorrow .. ;-)
Cheers,
Peter
|
Fri 21 May 2010 10:20:21 PM UTC, comment #4:
Hello Ramon,
I would prefer to have portaudio.dll compiled with
ASIO support as described on the portaudio website.
I see no additional usability with Jack,
but probably more latency ? Every millisecond counts ... ;-)
Cheers,
Peter
|
Fri 21 May 2010 09:56:43 PM UTC, comment #3:
Traverso's portaudio doesn't include asio, so it won't work with Traverso on windows.
So what I'd like to know is, does it work with jack2 on Windows.
If so, it means a direct solution is to compile Traverso with jack support or re-using jacks portaudio implementation to get asio working for Traverso on windows.
Hope I made the issue clear.
Remon
|
Fri 21 May 2010 09:43:11 PM UTC, comment #2:
Hello Ramon,
>I at least know the portaudio configuration of jack2
>works on Windows, so I can give a try on
>merging the relevant bits of jack2 directly
>into Traverso (long live open source :) )
I checked again Traverso on my notebook and
it does not work with ASIO and DirectX.
To both types of drivers Traverso says
host driver not found.
I am sure Jack is not (really) required on Windows.
As Jack also uses portaudio.dll Traverso should also
be able to open the ASIO drivers with portaudio.
On my notebook there are actually 4 ASIO drivers
but missing in Traverso-Windows-Version (Traverso
Preferences Dialog.PNG) there is a possibility
to choose one of several drivers for
- MME
- ASIO
- please see screenshot for selectable ASIO drivers as example -
Thanks,
Peter
(file #20576)
|
Fri 21 May 2010 02:07:22 PM UTC, comment #1:
Hello,
Nice you like it, we would be pleased if you introduce yourself and your expectations of Traverso in our forum: http://traverso-daw.org/forum/
We don't get much feedback from windows users, probably due the lack of good driver support :)
Ehm, as you've read in that other bug report, I don't have a windows install/development environment and even less experience on that platform. This isn't a big deal, except it makes it harder to debug on Windows or implement Windows specific features.
I recently discovered that jack (the sound server for pro-audio targeting linux/mac os x) has a windows port, using portaudio including asio support, as far as I understand it from their website: http://jackaudio.org/download
It would be of great help if you install the jack2 sound server on windows, including the asio bridge (I recall they have an asio bridge) and see if with the application qjackctl you can select your asio driver / sound device, and get the jack server started from qjackctl.
If that works, it basically boils down to have Traverso compiled on Windows with support for the jack audio server, and you can hook in any asio device/application to Traverso :)
For that you'll have to compile the git version of Traverso on Windows....
If you need help on that, just ask on irc channel #traverso or in the forum
If using jack on Windows is too cumbersome in real use, I at least know the portaudio configuration of jack2 works on Windows, so I can give a try on merging the relevant bits of jack2 directly into Traverso (long live open source :) )
Greetings,
Remon
|
Fri 21 May 2010 07:30:42 AM UTC, original submission:
Hello,
yesterday I found this excellent piece of software in the german HEISE magazine software download area - and I'm really impressed ! I immediately installed it on the next available PC and with the onboard soundcard it worked fine. I today also tested ASIO4ALL and this also works in TRAVERSO.
But my ASIO multichannel device "Alesis I/O 26" (firewire)
is not recognized. TRAVERSO error message:
- ASIO host not found -
Please also see bug #27448
I can't help that much, as a delphi developer I can just read C a little bit, but I try to avoid writing anything .. If You could point me to the bug related files in the source code I could give it a try to find - together with a developer - the reason why TRAVERSO misbehaves with multichannel ASIO devices under windows.
Please do not point me to LINUX - I like Linux and I
have two machines running - but my ALESIS IO 26
is not supported under LINUX - please see http://www.ffado.org/?q=node/30
Cheers,
Peter
|