My first time trying to use the Java Interop features and I’m hitting some issues using the Java Sound API It’s just the beginning part of a little GUI I’m trying to make that will take audio input and display the waveform. The problem code is a bit mixed up with the GUI code, but it’s here: https…

I would recommend making a minimal example of the error. You should be able to get it down to a handful of isolated lines. This is a good general debugging tactic but one specific reason I recommend it is that the only sexp calling getLine relies (via line-info and mixer-info) on a fn get-current-mi…

Is it possible that you’re using a newer version of Java (9+)? According to StackOverflow, [t]hese classes are proprietary and internal, they are not intended for public use. They are also a subject to change in the future. Close your eyes, don’t look at them and never use them. […

Oh yikes. I pushed a bug… That’s really embarrassing The REPL state drifted away from the file state :S I need to remember to rerun the program from scratch before pushing. It’s fixed now The reason I don’t have a small working example is because the mixer and line needs to be chosen at run time …

This sounds likely. You’re right that they are hidden classes, but they’re being returned by non-hidden methods - so it’s all a bit strange. I’m pretty much following the logic flow presented in the official tutorial : https://docs.oracle.com/javase/tutorial/sound/sampled-overview.html You get a l…

I don’t know about Java 9+, but in general, when I get a no matching method of arity exception, it is because there’s some ambiguity and Clojure can’t reflectively figure out what to call, so you have to type hint.

Actually, are you sure you are calling getLine with a Line.Info ? It looks like maybe you’re just passing a string? getLine takes this https://docs.oracle.com/javase/9/docs/api/javax/sound/sampled/Line.Info.html

These are good ideas :smirk:, but I’m pretty confident I’m passing in a LineInfo So I guess you figured out that the line that’s blowing up is in get-current-line (.getLine (get-mixer (:mixer-info mixer-info)) (:line-info line-info)))) And if you look at the state map, the lines have maps that l…

Turns out that the code is correct in the sense that you were calling .getLine with the right types of arguments, but Clojure had a hard time finding the right method implementation for some reason. Once you add type hints it works. [plexus] Add type hints by plexus on 0…

My assumption was always that adding type hints is a performance optimization and should never affect behavior. As the docs say Clojure supports the use of type hints to assist the compiler in avoiding reflection in performance-critical areas of code. Normally, one should avoid the use of type hin…

Wow, thank you so much for the patch @plexus . I seem to have a knack for choosing not very beginner friendly projects. Not sure I would have been able to dissect this problem without community help :slight_smile:

ClojureVerse

Weird Java Interop issues

Questions & Help Troubleshooting

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled