Jump to content

Lars L

Member
  • Posts

    11
  • Joined

  • Last visited

Lars L's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Collaborator Rare
  • Week One Done
  • One Month Later Rare
  • One Year In Rare

Recent Badges

0

Reputation

  1. Update: this bug was fixed in Logic Pro 10.7.5! 🎉 I've tested it and can confirm that Logic now exports auto-slurs correctly. Thanks Apple!
  2. Oh, I didn't think of doing that. I'll do that the next time though, thanks for the tip.
  3. I submitted my bug report to Apple now and noticed another problem with their form – the maximum character length of the "comments" text box is very short. I had prepared a thorough bug report with valuable information to the developers which I had to cut down severely in order to fit within the character count limit. Luckily I could preserve the entire report in my bug report in this forum!
  4. Version: Logic Pro 10.6.2 OS: macOS 10.15.7 Computer: MacBook Pro Retina, 15 inch, late 2013 Description: Exporting a score to MusicXML will not correctly preserve all auto-slurs. When there are consecutive auto-slurs in the same region, without any notes inbetween the slurs, exporting to MusicXML will merge together the slurs into a single slur, spanning from the beginning of the first auto-slur to the end of the last auto-slur. Steps to reproduce: Create a software instrument and a MIDI region in it. Add four notes in the piano roll or score editor, for example C3, D3, E3, F3 on successive beats (filling each beat). The specific notes or note lengths should not matter, however. In the score editor, add an auto-slur between C3–D3 and an auto-slur between E3–F4. Export to MusicXML. Expected behavior: The exported MusicXML file should preserve the slurs between C3–D3 and E3–F3, so that there are two slurs in the exported file. Actual behavior: The exported MusicXML file has merged the slurs together into a single slur, between C3–F3. Importing the file into Logic or another note editor will therefore not preserve the original slurs. Result after importing: Technical details: Inspecting the MusicXML file shows that the error lies in the export from Logic. The file contains the following data for the notes: <note> <pitch> <step>C</step> <octave>4</octave> </pitch> <duration>1</duration> <voice>1</voice> <type>quarter</type> <stem>up</stem> <staff>1</staff> <notations> <slur number="1" type="start"/> </notations> </note> <note> <pitch> <step>D</step> <octave>4</octave> </pitch> <duration>1</duration> <voice>1</voice> <type>quarter</type> <stem>up</stem> <staff>1</staff> </note> <note> <pitch> <step>E</step> <octave>4</octave> </pitch> <duration>1</duration> <voice>1</voice> <type>quarter</type> <stem>up</stem> <staff>1</staff> </note> <note> <pitch> <step>F</step> <octave>4</octave> </pitch> <duration>1</duration> <voice>1</voice> <type>quarter</type> <stem>up</stem> <staff>1</staff> <notations> <slur number="1" type="stop"/> </notations> </note> Only the first and last note contain elements. These elements should be present in each note, with proper start/stop pairs according to the score. Workarounds: Change the slurs from auto-slurs to manual slurs. Consecutive manual slurs are preserved correctly when exporting to MusicXML.
  5. Exactly – something simple like that would go a long way towards making it more enjoyable to submit bug reports. Edit: Perhaps I should submit that as a suggestion using their form. And then not get a confirmation email about it.
  6. I'm glad to hear that David! It would be nice to get just some response when you leave feedback using that form. Just a confirmation email would make it much more satisfying. It really has that "black hole" feeling right now, like you said des99. Of course, being able to track the issue would be the dream, but I guess we have to stay grounded here.
  7. As you say, it doesn't feel satisfying using the "something else" option so I'll probably just go with the main feedback form. Thanks for taking a second look at it and making sure I didn't miss something obvious.
  8. Thank you for that valuable information. I've been to the Feedback Assistant page and it's possible to create reports there even without being a paying developer. They have a macOS general section, however there is no category for Logic Pro or for pro apps in there which leaves me wondering whether that really is the right place to submit it. They have a "Something else" category which I could potentially use, but it seems a bit strange that they don't have any categories for their pro apps. Maybe it looks different if you have a developer account, though.
  9. Oh, and big thanks for the quick response!
  10. Yeah, thanks David. I knew about that and was planning on writing my report there as well. I'll go with that and the standard form, then.
  11. Hi, I want to submit a bug report to Apple and am wondering if there is some way of doing it via Feedback Assistant or similar, so that I can track the issue myself. I know about this form but that doesn't allow me to track the progress of the report, whether it's a duplicate, etc. I think it might be possible if you are enrolled in the developer program, but I'm looking for a free solution. Based on some searches around the Internet it seems to have been possible previously, but I can't find it anymore. Thanks, Lars
×
×
  • Create New...