Audio overload v2.2.112/21/2023 I've noticed that when using the speech synth to "read aloud" text I've written in SimpleText, as well as previewing the synth in system settings, that it is very choppy as well. VocalWriter uses the (MacOS) system's built-in General MIDI synthesizer for its instruments, and the (MacOS) system's built-in speech synthesizer for vocals. I read somewhere that the CPU clock speed is dependent on the host machine, so this shouldn't be a problem (if that's the case). I meet and even exceed all of these requirements, except for one I'm not too certain about, which is the CPU clock speed. I looked in the ReadMe file that came with the software, and came across a list of system requirements: Yet I'm still getting the error message above. My preferences are set to the lowest number of polyphony possible, and I only ever have one or two notes in a single channel/track sequence. The audio is delayed and very choppy when previewing single notes, and whenever I try to play anything (even if there are no notes programmed) I get this error message: I'm sending a pull request in case you think everything is fine as is.I've been having problems with VocalWriter in SheepShaver to the point where it's next to impossible to use. There may be better ways to test than what I did, in which case I'd appreciate any feedback. discussion #17įinished writing the specs for the overloads and everything works fine. The patch worked and now I'm running the tests. Sorry, read your other comment afterwards. I'll try to apply the fix (at least temporarily) in order to write the specs. Somebody there apparently was able to come up with a fix and they're now writing tests for it. I just found a thread on this problem, which indeed seems to be a win-only issue. Gem "jruby-openssl", "~> 0.7.2" if RUBY_PLATFORM = "java"īefore replacing the Gemfile, could you please run rake -trace and paste in the full trace (preferably in a Gist)?Īlso, what version of bundler are you using? discussion #15ĭidn't work. Try replacing the Gemfile with: source "" I reckon this is a problem with my configuration only: I tried running yard:doc against a clean master and I have the same problem. Just cloned my branch from my laptop, with Ruby 1.9.2p0, and I'm still getting the same error messages. Is that an option?įWIW, I can't reproduce in the problem using Ruby 1.9.1p378 in Mac OS X. I just asked about this in #carlhuda on. No, its there, twitter.gemspec discussion #10 I assume you haven't deleted the gemspec from the root directory? discussion #9 No such file or directory - twitter.gemspecĬ:/ruby/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2383:in `raw_load_rakefile' discussion #8 What happens if you change line 2 of your Rakefile to: Bundler::GemHelper.install_tasks, :name => 'twitter' (I finished with the changes, only thing left would be writing the specs) discussion #6 Use :name => 'gemname' in #install_tasks to manually set it.Ĭ:/Ruby/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2383:in `raw_load_rakefile' Unable to determine name from existing gemspec. I'm using Ruby 1.9.1 on windows 7, and already run bundle install. I'm getting an error when trying to run bundle exec rake doc:yard. This is the only major feature I had in mind for 1.1, so unless any new feature requests come in before then, we should be able to release 1.1 shortly after you finish. I'd love to see specs that cover each way of calling the method (with and without a screen name passed). Thanks for starting to tackle this problem! Your approach looks good to me. UPDATE: A link with a diff, for your convenience: discussion #3 I'd like to know if you think I'm headed in the right direction though. discussion #2ĭon't know if anybody has been addressing this yet but I've made some advances. I've added for all the methods to which this change can be applied. This value should be cached in the configuration after the first request. It should allow implicit fetching of an authenticated user's screen name from configuration.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |