04-27-2020, 12:33 AM
Presonus Firestudio doesn't let program start Windows 10, 7 (compatibility)
Presonus Firebox - Too much latency, but will kindof work.
Presonus Firebox - Too much latency, but will kindof work.
List of Audio Interfaces
|
04-27-2020, 12:33 AM
Presonus Firestudio doesn't let program start Windows 10, 7 (compatibility)
Presonus Firebox - Too much latency, but will kindof work.
04-27-2020, 02:13 AM
(04-27-2020, 12:33 AM)myucka Wrote: Presonus Firestudio doesn't let program start Windows 10, 7 (compatibility) Hi there, I use a Presonus Firestudio Mobile. A few years back it had worked (Win 7) but now it does not. Whenever I have it pluged in, JamKazam CLient won't start. Once I unplug it the Prg starts and I can see my Realtek built-in Audio. So then I plug in the Presonus and all is gone: "Asio generic-low latency driver unavailable or corrupt". I tried almost everything and am at the end of my wisdom. Has anyone any further ideas of what I might have not seen? Any help is greatly appreciated. Cheers Tom
I am using a RME Fireface 800 (FireWire via express card) with an old HP Probook 4530s (Windows 10) at 5.9ms latency. Also using an ESI UGM96 on the same laptop (Usb 2.0) at 4.4ms latency. Both have been stable enough to jam with guys in my city and halfway across the country.
04-27-2020, 09:39 PM
Myucka - thanks for the info! I’ve updated the list. Hope you can get the latency down on your Firebox.
DeadNZ - thanks for the info! I’ve updated the list, and hope you’re able to get your FireStudio Mobile work. Guyfi - thanks for the info! I’ll add the info fo the Fireface 800 and move the UGM96 to the “Working” category.
Kevin
05-01-2020, 03:24 PM
Thank you Kevin for this comprehensive List!
In the last section (AI mentioned, but not yet determined working ...) I could find my TASCAM US-1641. Just recently I bought a used one and it is working with JK. Drivers and a fairly good documentation can be found here on an official TASCAM-Site . I operate it on a Windows 10 OS using TASCAMs ASIO-Driver (not the WDM thing). I'm still testing a lot with my bandmates and we're still in the phase of talking more about the klicks and technics instead of jamming together. Basically the TASCAM is doing it's job. If it can be recommended as working good or very good I cannot say yet. The latency which the JK-system shows me has never been better than fair and the IO-Rates vary from fair to good. So the TASCAM US-1641 definitely can be moved to the section AI confirmed working with JK . Keep on listing! Best regards, Joern
05-01-2020, 05:02 PM
(04-23-2020, 06:40 PM)geobrick Wrote: I'm new to JamKazam and haven't done much trouble shooting yet but I have not been able to launch JamKazam with my TC Studio Konnekt48 (firewire interface). I'm using Windows 10 (x64). I have a separate thread asking for some help to get it working. That thread has an image of the error message. If I can get it to work, I'll report back.I still haven't got the JamKazam app (on Win10 x64) to work with my TC Studio Konnekt-48 audio interface. When the interface is turned on, JamKazam will either freeze with a white screen (not responding) or will display this error: I think this audio interface should be added to the list in the "Mentioned, But Not Yet Determined If Working" section for now. If you have any suggestions for me, I have a separate post here: https://forum.jamkazam.com/showthread.php?tid=514
05-01-2020, 06:02 PM
Saw M-Audio M-Track 2 2 above working on Windows, I have it working well on Mac 10.14.5
05-01-2020, 07:01 PM
Working fine for me with an older M-Audio AudioPhile 24/96 PCIe card in a Windows 7 64-bit box. About 4 ms audio system latency using ASIO.
05-01-2020, 09:42 PM
Joern, you’re welcome! Hope it helps. Thank you for the information - I’ve updated the TASCAM US-1641 to be in the “confirmed working” section.
Thanks, Rob Adams! I’ve added the macOS 10.14.5 to the M-Track. Seiseuneer, thanks for the info! I’ve updated the list with that M-Audio interface.
Kevin
05-02-2020, 12:23 AM
I use an UR44 and it basically works on Windows 10/64 bit but it shows up with a WDM driver only, not with Steinbergs low latency ASIO Driver. So JK is measuring a much to high latency of 20 msec instead the expected 5 msec for input and 4 msec for output.
But I just noticed that Steinberg has released a new driver 2 weeks ago. I will check tomorrow and come back if new driver is detected by JK and provides better latency. |