I receive a gstreamer media playback error (detail farther down this message) when I initially start EasyABC and when I attempt to stop a playback by hitting the black "stop" button.
Can you suggest what actions I can take to troubleshoot or fix this problem?
I've added all the info I have below, in hope that it's useful.
I am running from easyabc_source_code_1.3.7.6, which I downloaded from the SourceForge site. (I also tried the 1.3.7.6-rc1.deb downloaded from the ABCPlus site; that version had the same gstreamer problem).
I'm running EasyABC on a Linux Mint 18.2 (which is based on Ubuntu 16.04). I had previously run EasyABC 1.3.7.6-rc1 on LM 17.3 without problems.
Because some dependencies (specifically, wxgtk2.8) are not available in LM 18.2, I adjusted the install instructions in the "using EasyABC in linux" help text:
* installed via apt-get: python-wxgtk3.0 python-wxgtk-media3.0 python-wxtools python-pyparsing abcmidi timidity
* installed from deb: abcm2ps_8.12.4-1_amd64
* installed EasyABC by unpacking the source into my home directory and adding a launcher
(The version of abcmidi in LM 18.2's respository is 20160103-1. I also tried the more recent 20170814-1 available via the ABCPlus site, but with that version audio playback didn't work at all, so I went back to 20160103-1.)
Settings / Midi Settings show "none" (and no menu selection choices) for the input and output devices.
Audio playback works - but apparently due to the error I receive when I hit the black "stop" button, I can't interrupt a playback once it starts, must instead wait for it to end.
Here is the error message detail (the detail screen lists the messages twice, as below):
09:40:34 AM: Media playback error: Resource not found.
09:40:34 AM: Media playback error: GStreamer error: state change failed and some element failed to post a proper error message with the reason for the failure.
09:40:34 AM: Media playback error: Resource not found.
09:40:34 AM: Media playback error: GStreamer error: state change failed and some element failed to post a proper error message with the reason for the failure.
Are you using some kind of virtual machine like VirtualBox? I myself struggled with the same error a few months ago. The cause is not EasyABC itself but the mediaplayer component it uses. Although EasyABC only uses audio part of GStreamer, it seems a display is necessary too and VirtualBox does not provide it somehow. Linux Mint 17.3 worked fine, but since Linux Mint 18 the problem started and I have not been able to solve it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, JW. No, no virtual machine, I'm running the application natively. I ran natively on LM 17.3 and (like you) without difficulty, but now I have the problem on 18.2. Thx, RL
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I run easyABC 1.3.7.7 on Windows 10. Generally speaking , the program is able to do what it is supposed to do. Congratulations and many thanks to the authors.
I would like to enter notes directly with a MIDI keyboard.
so, when I connect my MIDI keyboard (through USB) , it is not recognised and I can't see any change in the midi device settings: Midi device in : none and midi device out none. I do not not see any way to change this. I looked at the settings1.3.dat in my user directory but I don't kow what to do!
A precision:My keyboard is automatically recognised by Finale, Band ina box ...and it appears as working correctly in harware right click on my PC.
Have I to install a specific driver ?
Thank you for any help
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, not solved it, but rather bypassed it (only tested on Windows).
I am currently working on using FluidSynth for playback instead of
GStreamer. Only problem is that fluidsynth version 2 is needed and only
a few Linux distributions have packages for fluidsynth 2 yet. Just
noticed that the next version of Debian/Ubuntu will support it: https://launchpad.net/ubuntu/+source/fluidsynth/2.1.0-1
On 28-12-2019 09:25, Andrew Bernard wrote:
Same issue on Ubuntu 19.04. Has anybody solved this problem with
GStreamer, on Virtualbox 6.0.14?
I receive a gstreamer media playback error (detail farther down this message) when I initially start EasyABC and when I attempt to stop a playback by hitting the black "stop" button.
Can you suggest what actions I can take to troubleshoot or fix this problem?
I've added all the info I have below, in hope that it's useful.
Thanks in advance! Regards, Rob L
=======================================================
I am running from easyabc_source_code_1.3.7.6, which I downloaded from the SourceForge site. (I also tried the 1.3.7.6-rc1.deb downloaded from the ABCPlus site; that version had the same gstreamer problem).
I'm running EasyABC on a Linux Mint 18.2 (which is based on Ubuntu 16.04). I had previously run EasyABC 1.3.7.6-rc1 on LM 17.3 without problems.
Because some dependencies (specifically, wxgtk2.8) are not available in LM 18.2, I adjusted the install instructions in the "using EasyABC in linux" help text:
* installed via apt-get: python-wxgtk3.0 python-wxgtk-media3.0 python-wxtools python-pyparsing abcmidi timidity
* installed from deb: abcm2ps_8.12.4-1_amd64
* installed EasyABC by unpacking the source into my home directory and adding a launcher
(The version of abcmidi in LM 18.2's respository is 20160103-1. I also tried the more recent 20170814-1 available via the ABCPlus site, but with that version audio playback didn't work at all, so I went back to 20160103-1.)
Settings / Midi Settings show "none" (and no menu selection choices) for the input and output devices.
Audio playback works - but apparently due to the error I receive when I hit the black "stop" button, I can't interrupt a playback once it starts, must instead wait for it to end.
Here is the error message detail (the detail screen lists the messages twice, as below):
09:40:34 AM: Media playback error: Resource not found.
09:40:34 AM: Media playback error: GStreamer error: state change failed and some element failed to post a proper error message with the reason for the failure.
09:40:34 AM: Media playback error: Resource not found.
09:40:34 AM: Media playback error: GStreamer error: state change failed and some element failed to post a proper error message with the reason for the failure.
Here are the Internals / Status Settings
abc2abc_path => /usr/bin/abc2abc
abc2midi_path => /usr/bin/abc2midi
abc2midi_path_choices => /usr/bin/abc2midi
abcm2ps_botmargin => 1.00
abcm2ps_clean => False
abcm2ps_defaults => True
abcm2ps_ignore_ends => False
abcm2ps_leftmargin => 1.78
abcm2ps_no_lyrics => False
abcm2ps_number_bars => False
abcm2ps_pageheight => 27.94
abcm2ps_pagewidth => 21.59
abcm2ps_path => /usr/bin/abcm2ps
abcm2ps_refnumbers => False
abcm2ps_rightmargin => 1.78
abcm2ps_scale => 0.75
abcm2ps_topmargin => 1.00
author =>
auto_refresh => True
barfly => False
bassvol => 96
bpmtempo => 120
can_draw_sharps_and_flats => True
chordvol => 96
gchord => default
gs_path => /usr/bin/gs
is_maximized => True
melodyvol => 96
midi2abc_path => /usr/bin/midi2abc
midi_chord_program => 24
midi_device_in => None
midi_device_out => None
midi_intro => 0
midi_program => 0
midi_program_ch1 => [0, 96, 64]
midi_program_ch10 => [0, 96, 64]
midi_program_ch11 => [0, 96, 64]
midi_program_ch12 => [0, 96, 64]
midi_program_ch13 => [0, 96, 64]
midi_program_ch14 => [0, 96, 64]
midi_program_ch15 => [0, 96, 64]
midi_program_ch16 => [0, 96, 64]
midi_program_ch2 => [0, 96, 64]
midi_program_ch3 => [0, 96, 64]
midi_program_ch4 => [0, 96, 64]
midi_program_ch5 => [0, 96, 64]
midi_program_ch6 => [0, 96, 64]
midi_program_ch7 => [0, 96, 64]
midi_program_ch8 => [0, 96, 64]
midi_program_ch9 => [0, 96, 64]
midiplayer_parameters =>
midiplayer_path => /usr/bin/timidity
midiplayer_path_choices => /usr/bin/timidity
nodynamics => False
nofermatas => False
nograce => False
perspective => layout2|name=tb2;caption=Toolbar2;state=67379904;dir=1;layer=10;row=0;pos=0;prop=100000;bestw=1392;besth=34;minw=-1;minh=-1;maxw=-1;maxh=-1;floatx=-1;floaty=-1;floatw=-1;floath=-1;notebookid=-1;transparent=255|name=tune preview;caption=Musical score;state=402655164;dir=1;layer=0;row=0;pos=0;prop=100000;bestw=200;besth=280;minw=-1;minh=-1;maxw=-1;maxh=-1;floatx=-1;floaty=-1;floatw=-1;floath=-1;notebookid=-1;transparent=255|name=tune list;caption=Tune list;state=268437376;dir=4;layer=1;row=0;pos=0;prop=100000;bestw=265;besth=80;minw=-1;minh=-1;maxw=-1;maxh=-1;floatx=-1;floaty=-1;floatw=-1;floath=-1;notebookid=-1;transparent=255|name=abc editor;caption=ABC code;state=134219648;dir=5;layer=0;row=0;pos=0;prop=100000;bestw=196;besth=79;minw=40;minh=40;maxw=-1;maxh=-1;floatx=-1;floaty=-1;floatw=-1;floath=-1;notebookid=-1;transparent=255|name=abcassist;caption=ABC assist;state=67110844;dir=4;layer=1;row=0;pos=1;prop=100000;bestw=300;besth=600;minw=-1;minh=-1;maxw=-1;maxh=-1;floatx=-1;floaty=-1;floatw=-1;floath=-1;notebookid=-1;transparent=255|dock_size(1,10,0)=36|dock_size(1,0,0)=455|dock_size(4,1,0)=302|dock_size(5,0,0)=198|
recentfiles => /media/data/UserData/Music & Dance/ABCs/Reels_Marches.abc|
record_bpm => 70
record_metre => 3/4
reduced_margins => True
score_zoom => 1000
searchfolder => /home/rob/.EasyABC
show_abc_assist => True
tempo => 100
transposition => 0
tune_col_widths => [37, 259]
tuning => 440
typing_assistance_active => True
typing_assistance_add_bar => False
typing_assistance_add_bar_auto => True
typing_assistance_add_note_durations => False
typing_assistance_add_right => True
typing_assistance_auto_case => False
typing_assistance_do_re_mi => False
version => 1.3.6.4
window_height => 1026
window_width => 1680
window_x => -3
window_y => 0
xml_b => 0
xml_c => 0
xml_d => 0
xml_n => 0
xml_p =>
xml_u => 0
xml_v => 0
xmlcompressed => False
xmlmidi => False
xmlunfold => False
zoom => 0
Last edit: Rob L 2017-08-23
Rob,
Are you using some kind of virtual machine like VirtualBox? I myself struggled with the same error a few months ago. The cause is not EasyABC itself but the mediaplayer component it uses. Although EasyABC only uses audio part of GStreamer, it seems a display is necessary too and VirtualBox does not provide it somehow. Linux Mint 17.3 worked fine, but since Linux Mint 18 the problem started and I have not been able to solve it.
Hi, JW. No, no virtual machine, I'm running the application natively. I ran natively on LM 17.3 and (like you) without difficulty, but now I have the problem on 18.2. Thx, RL
I've updated to 1.3.7.7 and (not that it's a surprise) see the same symptoms
I have the same errors using 1.3.3.7 installed with the 64 bits .deb on Devuan Jessie.
I run easyABC 1.3.7.7 on Windows 10. Generally speaking , the program is able to do what it is supposed to do. Congratulations and many thanks to the authors.
I would like to enter notes directly with a MIDI keyboard.
so, when I connect my MIDI keyboard (through USB) , it is not recognised and I can't see any change in the midi device settings: Midi device in : none and midi device out none. I do not not see any way to change this. I looked at the settings1.3.dat in my user directory but I don't kow what to do!
A precision:My keyboard is automatically recognised by Finale, Band ina box ...and it appears as working correctly in harware right click on my PC.
Have I to install a specific driver ?
Thank you for any help
I think that the line that's causing the problem is: self.mc.Load('NONEXISTANT_FILE____.mid')
thanks.
it works.
to solve the problem need to comment this line.
1 in file easy_abc.py find line with code text
2 add # at begin of line
3 save modified file.
sudo needs.
Same issue on Ubuntu 19.04. Has anybody solved this problem with GStreamer, on Virtualbox 6.0.14?
Well, not solved it, but rather bypassed it (only tested on Windows).
I am currently working on using FluidSynth for playback instead of
GStreamer. Only problem is that fluidsynth version 2 is needed and only
a few Linux distributions have packages for fluidsynth 2 yet. Just
noticed that the next version of Debian/Ubuntu will support it:
https://launchpad.net/ubuntu/+source/fluidsynth/2.1.0-1
On 28-12-2019 09:25, Andrew Bernard wrote: