BASH open file from variable: The file <xxx> does not exist - bash

Question

Description of Task & problem
I have dumped a list of files which match certain criteria to a text file. The command i used is:
find . -name "*.logic" | grep -v '.bak' | grep -v 'Project File Backup' > logic_manifest.txt
Filenames with spaces in are proving difficult to automatically open, such as :
./20160314 _ Pop/20160314 _ Pop.logic
I have replaced the spaces with '\ ' to escape them but the open command complains:
The file /Users/daniel/Music/Logic/20160314\ _\ Pop/20160314\ _\ Pop.logic does not exist.
When I copy that parsed path, type open in the terminal and paste it in, the file opens successfully.
My BASH script:
#!/bin/bash
clear
# file full of file paths, gathered using the find command
#logic_manifest.txt
# For keeping track of which line of the file I'm using
COUNTER=0
it=1
while IFS='' read -r line || [[ -n "$line" ]]; do
# Increment iterator
COUNTER=`expr $COUNTER + $it`
# replace spaces with a black-slash and space
line=${line// /<>}
line=${line//<>/'\ '}
# print the file name and the line it is on
echo "Line: $COUNTER $line"
#open the file
open "$line"
# await key press before moving on to next iterator
read input </dev/tty
done < "$1"
Encapsulating the filename in speech-marks has not helped
line=${line// /<>}
line=${line//<>/'\ '}
line="\"$line\""
The file /Users/daniel/Music/Logic/"./20160314\ _\ Pop/20160314\ _\
Pop.logic" does not exist.
Nor did passing "\${line}" to open
Question
What do I need to do to enable the open command to launch the files successfully?
Renaming the directories and filenames is not a viable option at this time.
Spaces in filenames are bad, I know, I put it down to moments of madness

Answer 1

There is absolutely no need whatsoever to replace any characters in line.
This simpler loop should open files just fine:
while IFS='' read -r line; do
((COUNTER++))
echo "Line: $COUNTER $line"
open "$line"
read input </dev/tty
done < "$1"
That's it. Moreover:
Spaces in filenames are bad, I know, I put it down to moments of madness.
There's nothing wrong with spaces in filenames.
You just have to use proper quoting, that's all.
That is, if the file names didn't have spaces and other special characters in them, then you could write open $line and it would work.
Since they contain spaces, you must enclose the variable in double-quotes, as in open "$line".
Actually it's strongly recommended to enclose variables in double-quotes when used in command line arguments.