Is DataLine.getMicrosecondPosition() thread-safe?











up vote
0
down vote

favorite












Let's say I use DataLine.write() in one thread and read DataLine.getMicrosecondPosition() in another. Will the reader thread see the updates of the writer thread, or should I synchronize my code to guarantee visibility?










share|improve this question


























    up vote
    0
    down vote

    favorite












    Let's say I use DataLine.write() in one thread and read DataLine.getMicrosecondPosition() in another. Will the reader thread see the updates of the writer thread, or should I synchronize my code to guarantee visibility?










    share|improve this question
























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      Let's say I use DataLine.write() in one thread and read DataLine.getMicrosecondPosition() in another. Will the reader thread see the updates of the writer thread, or should I synchronize my code to guarantee visibility?










      share|improve this question













      Let's say I use DataLine.write() in one thread and read DataLine.getMicrosecondPosition() in another. Will the reader thread see the updates of the writer thread, or should I synchronize my code to guarantee visibility?







      java thread-safety javasound






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 17 hours ago









      Markus Malkusch

      5,3532150




      5,3532150
























          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          Just to be clear:



          write() is a potentially blocking call that puts data into the line's buffer for rendering. I.e. the line may render the data at some time in the future. From the docs:




          The requested number of bytes of data are read from the specified array, starting at the given offset into the array, and written to the data line's buffer.




          getMicrosecondPosition () tells you how many microseconds have already been rendered, docs:




          The microsecond position measures the time corresponding to the number of sample frames captured by, or rendered from, the line since it was opened.




          Both methods should be thread-safe, as there is no warning in the Javadocs.






          share|improve this answer





















            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














             

            draft saved


            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53370948%2fis-dataline-getmicrosecondposition-thread-safe%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            0
            down vote













            Just to be clear:



            write() is a potentially blocking call that puts data into the line's buffer for rendering. I.e. the line may render the data at some time in the future. From the docs:




            The requested number of bytes of data are read from the specified array, starting at the given offset into the array, and written to the data line's buffer.




            getMicrosecondPosition () tells you how many microseconds have already been rendered, docs:




            The microsecond position measures the time corresponding to the number of sample frames captured by, or rendered from, the line since it was opened.




            Both methods should be thread-safe, as there is no warning in the Javadocs.






            share|improve this answer

























              up vote
              0
              down vote













              Just to be clear:



              write() is a potentially blocking call that puts data into the line's buffer for rendering. I.e. the line may render the data at some time in the future. From the docs:




              The requested number of bytes of data are read from the specified array, starting at the given offset into the array, and written to the data line's buffer.




              getMicrosecondPosition () tells you how many microseconds have already been rendered, docs:




              The microsecond position measures the time corresponding to the number of sample frames captured by, or rendered from, the line since it was opened.




              Both methods should be thread-safe, as there is no warning in the Javadocs.






              share|improve this answer























                up vote
                0
                down vote










                up vote
                0
                down vote









                Just to be clear:



                write() is a potentially blocking call that puts data into the line's buffer for rendering. I.e. the line may render the data at some time in the future. From the docs:




                The requested number of bytes of data are read from the specified array, starting at the given offset into the array, and written to the data line's buffer.




                getMicrosecondPosition () tells you how many microseconds have already been rendered, docs:




                The microsecond position measures the time corresponding to the number of sample frames captured by, or rendered from, the line since it was opened.




                Both methods should be thread-safe, as there is no warning in the Javadocs.






                share|improve this answer












                Just to be clear:



                write() is a potentially blocking call that puts data into the line's buffer for rendering. I.e. the line may render the data at some time in the future. From the docs:




                The requested number of bytes of data are read from the specified array, starting at the given offset into the array, and written to the data line's buffer.




                getMicrosecondPosition () tells you how many microseconds have already been rendered, docs:




                The microsecond position measures the time corresponding to the number of sample frames captured by, or rendered from, the line since it was opened.




                Both methods should be thread-safe, as there is no warning in the Javadocs.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered 17 hours ago









                hendrik

                1,422821




                1,422821






























                     

                    draft saved


                    draft discarded



















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53370948%2fis-dataline-getmicrosecondposition-thread-safe%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Cypress Hill

                    what are some tips for doing well in the interview? [on hold]

                    How does a super-power salesman not get shut down for legal reasons?